Community Articles

This section hosts articles, notes, source code readings, engineering experiences, and high-quality Q&A summaries contributed by the Tutorial_AwesomeModernCPP community.

Community articles are not automatically merged into the main tutorial volumes. This section provides a more open entry point: contributors can submit Markdown files, maintainers will perform a basic review before publishing them for display, and then decide whether to include them permanently or integrate them into main chapters based on discussion and feedback.

Latest Submission

The newest community submission — a thorough take on why C++ still has no unified, smooth package manager, walking from downloading, ABI, and build-system fragmentation all the way to C++20 modules. By CharlieChen114514.

01Why Is C++ Package Management So Hard?→

Content Status

01Community Submissions (First Issue)→02Reviewed & Included→03Project Development→

Workflow

1. The contributor submits a Markdown file.
2. Maintainers check for basic quality, copyright sources, and obvious technical errors.
3. After passing the basic check, the article enters community/incoming/ and can be displayed on the documentation site and in the TAMCPP weekly newsletter.
4. After community discussion, grammatical revisions, and technical review, the article is moved to community/articles/.
5. If the article is a great fit for the main tutorial, maintainers may further integrate it into the corresponding volume or chapter.

Submission Scope

Contributors can focus on the main content and do not need to understand the complete site structure from the start.

It is recommended to provide:

• Article title and author attribution.
• Body text in Markdown.
• Source attribution for images, code, and referenced materials.
• Target audience or applicable context.
• Permission for maintainers to adjust titles, formatting, placement, and wording.

Maintainers are responsible for:

• Determining whether to place the article in the submissions section, the included section, or the main tutorial.
• Completing necessary frontmatter, navigation, indices, and links.
• Performing basic formatting, terminology standardization, and technical review.
• Determining if an English translation or further thematic organization is needed.

Minimum Inclusion Requirements

While community submissions are not final drafts, they must meet basic requirements before going online:

• Content renders correctly.
• No obvious technical errors.
• Original content or explicitly authorized.
• Sources provided when citing external materials.
• Clear sources for images, code, and extensive materials.
• The author agrees to public display and allows maintainers to make necessary edits.

For learning questions, roadmap discussions, and open-ended suggestions, please use GitHub Discussions first; for specific content proposals or submission topics, please use GitHub Issues.

The project's maintenance rhythm, site iterations, and release metrics are recorded in Project Development.