doc - Competitive Programming Handbook
Role
cp4cpp.com/doc is the Competitive Programming Handbook.
It is the canonical final form for reusable competitive-programming knowledge: algorithms, data structures, proofs, implementations, variants, and references.
Mermaid preview
Annotation preview
Code preview
Highlighter preview
Diagram preview
Purpose
- Teach how algorithms, data structures, and patterns work through structured technical articles.
- Combine code, diagrams, annotations, and visual blocks into readable handbook pages.
- Turn scattered editorials into cleaner, reusable, long-term references.
Lineage
| Project | Meaning | Time | Form |
|---|---|---|---|
| ACES | All-encompassing Competitive Editorial Slayer | Mar 2023 | MkDocs Material on es.ac.vn |
| ES | Editorial Slayer | Nov 2020 | LQDOJ / VNOJ |
| HAT | Hunter and Tracer | Dec 2022 | Discord |
References
| Short | Project | Use |
|---|---|---|
| CP-ALGO | CP-Algorithms | Generated algorithm docs and code references. |
| KACTL | KTH Algorithm Competition Template Library | ICPC copy-paste team reference. |
| ACL | AtCoder Library | Official contest library docs from AtCoder. |
| OI-WIKI | OI Wiki | Maintained OI/ICPC wiki. |
| PEG-WIKI | Programming Enrichment Group | Older wiki-style CP explanations. |
| CSES-BOOK | Competitive Programmer’s Handbook | Classical handbook and problemset with learning intent. |
Learning Style
BFS-like learning: users jump by topic for coverage, lookup, variants, and references without needing a fixed prerequisite path.
Strengths To Preserve
- Static docs are familiar, trusted, easy to revisit, and cheap to preserve.
- Strong handbook projects offer breadth, reusable implementations, and problem-set coupling.
- Docs scale when structure and contribution flow are consistent.
Weaknesses To Fix
- Docs often explain what a thing is, but not when to learn it, what comes before it, or what to solve after it.
- Topic relations, prerequisites, and variant links are usually shallow or writer-dependent.
- Article quality drifts without review rules.
CP4CPP Rules
- Each problem should use the
taghierarchy for consistent taxonomy and navigation. - Each page must include practice problems and references to related blogs or wikis.
docis the canonical final form of knowledge;eduhandles teaching order.- Handbook pages should connect to neighboring topics and must not behave as isolated islands.