Contributors
Thank you to everyone who has contributed to this project! Whether through code, design, illustrations, bug reports, or content suggestions, your help makes this tutorial better.
Contribution Types
| Icon | Type | Description |
|---|---|---|
| 🎨 | Interface Design | UI/UX design, visual optimization |
| 🖼️ | Illustrations | Tutorial diagrams, architecture diagrams, flowcharts |
| 🐛 | Bug Reports | Reporting errors via Issues, WeChat, QQ, email, etc. |
| 📝 | Content Suggestions | Providing content improvement ideas, learning path optimization |
| 🔍 | Review | Content review, technical proofreading |
| 🌍 | Translation | English translation or other language translations |
| 💡 | Code Examples | Providing code examples or improvement suggestions |
| 📢 | Promotion | Helping to spread the word about the project |
Contributor List
About anonymous contributors
Some contributors have chosen to remain anonymous or use pseudonyms for privacy reasons. We are equally grateful to them.
The main maintainers are as follows:
A huge thank you to these friends for their PRs and various forms of support! Your help is making this project better and taking it further! (A deep 90-degree bow!)

UI Design Guidance & Feedback
🎨 📝
Guided the UI design of this documentation site and provided important suggestions for improving the reading experience

Content Fixes
🐛 💡
Fixed typos in the shared pointer and variant chapters, improving content accuracy
The valuable feedback from these folks is equally worth recording. It is your feedback that allows this project to identify real issues and pushes us to improve! (Another deep 90-degree bow!)

Bug Reports
🐛
Reported 404 page issues and text display anomalies

Bug Reports & Content Suggestions
🐛 📝
Raised questions and discussions regarding C++ character literal types

Bug Reports
🐛 💡
Reported compilation failure in the expected example

Bug Report · Content Errata
🐛 💡
Reported an inconsistency between the example and explanation in Vol.1 "Cache and Memory Hierarchy" (#67), leading to a units fix
How to Become a Contributor
We welcome contributions in all forms! These include, but are not limited to:
- Submitting Issues: Spotting errors or inaccuracies
- Content Suggestions: Topics you would like to see added or improvement ideas
- Interface Design: UI/UX optimization proposals for the documentation site
- Illustrations: Creating diagrams and flowcharts for the tutorial
- Translation: Helping to translate tutorial content
- Code Examples: Providing better code examples
Please reach out to us through any of the following channels:
See the Contributing Guide for details.
