About cpp.social

C++'s ecosystem is vast, but somewhat fragmented. The same can be said for the many C++ communities, events, excellent blogs and other C++ related content. cpp.social's goal is to collect everything C++ developers care about - from useful resources, books and other publications to events and communities.

Additionally this site acts as content aggregator for C++ related blogs, YouTube channels and event calendars.

To address the fragmentation of the ecosystem, this site also provides an experimental cross package manager package search. After all, having multiple dependency sources available is vastly more useful if you can easily find the packages you're looking for across package managers.

How the site works

This site is maintained in the public Github cpp.social repository and hosted through Github Pages. All content on this site is curated by actual humans - only metadata (such as the package catalog, icons, some descriptions etc.) is automatically fetched from external sources.

Generated metadata retains its source information so readers and maintainers can verify where it came from. You can view this by clicking the "External Sources" link in the footer of pages with externally sourced content.

The content on this page is meant to help users inform themselves and evaluate the options they have. Maintainers and curators of this site do not endorse any of the content listed on this site, we merely collect whatever exists and seems relevant enough.

Contributing

Projects like this one need community help to stay relevant and up-to-date. We explicitly welcome suggestions, corrections and other improvements through issues and pull requests.

The contributor guide explains what information each content type requires and how content changes are reviewed.

Project governance

This project is not affiliated with ISO/IEC JTC 1/SC 22/WG 21 (the C++ committee) or any other organization.

Project governance is split into two groups:

• Maintainers look after the site and its tooling
• Curators focus on reviewing and maintaining its content

All changes to content (e.g. resource additions) need approval of at least 2 current maintainers or curators.

The roster below is included directly from the repository's MAINTAINERS.md file.

Current Maintainers

Emeritus