Team up with vcpkg
Related: microsoft/vcpkg#6154

Sync/verify port descriptions (vcpkg <-> awesome-cpp)
Sync/verify port license information (vcpkg <-> awesome-cpp)
Library Homepage (vcpkg <- awesome-cpp)
Vcpkg availability, operating system support, version, build status (vcpkg -> awesome-cpp)
Dependency level; level0=no deps; level1=depends on any level0; ... (vcpkg -> awesome-cpp)
field; eg ,science,engineering,gaming,... (missing; vcpkg <- awesome-cpp)
major application group (vcpkg <- awesome-cpp)
minor application group (missing; vcpkg <- awesome-cpp)
library siblings; meaning redundant libraries (missing; vcpkg <- awesome-cpp)

One approach to keep information synced would be to use vcpkg as database:

1. vcpkg: choose which information belongs into the port file
2. vcpkg: choose a way to store additional information (eg: build status)
3. port existing information to vcpkg
4. awesome-cpp: sync data for existing ports in vcpkg from vcpkg