C++

Contribute to bigcpp

bigcpp.com is open-source. The content is CC-BY-SA 4.0 — you can read it, use it, and improve it. All contributions are reviewed and credited.

Source code is on GitHub

Content lives in content/ as MDX files. The site is Next.js 15 + Velite. See CONTRIBUTING.md for the full workflow.

github.com/ibencherouten/bigcpp

Ways to contribute

Fix an error or improve an explanation

5–30 min

Found a mistake, outdated information, or an explanation that's harder than it needs to be? Open an issue or a pull request.

  1. 1.Click "Edit on GitHub" at the bottom of any page
  2. 2.Fix the MDX file directly in the GitHub editor
  3. 3.Submit a pull request with a one-line description

Add a code example

15–60 min

Missing a working example for a concept? Add a fenced code block with the C++ standard version and a short comment explaining what it demonstrates.

  1. 1.Find the relevant MDX file in content/reference/
  2. 2.Add a ```cpp block with a self-contained example
  3. 3.Mark the code block with the standard it requires: cpp20, cpp23, etc.

Write a new reference page

2–8 hours

C++ has hundreds of features and library types that aren't covered yet. If you're an expert on a concept, writing the definitive page is the highest-impact contribution.

  1. 1.Open an issue first to confirm the page doesn't already exist
  2. 2.Use the MDX page template (see CONTRIBUTING.md)
  3. 3.Include: overview, syntax, examples (beginner + advanced), pitfalls, and related links

Content standards

These aren't style preferences — they're what makes a C++ reference worth trusting.

Accurate

Every claim must be verifiable against the ISO standard, cppreference, or a compiler explorer output.

Complete

Cover the most important cases. A page that's 80% complete causes confusion for the 20% edge case it doesn't cover.

Tested

All code examples must compile. Mark the standard version they require. We prefer examples that run on Compiler Explorer.

No opinion

Factual claims only. "X is better than Y" requires a citation. This is a reference, not a blog.

Consistent style

Follow the existing page structure: overview → syntax → examples → pitfalls → related. Check CONTRIBUTING.md for details.

Page structure (MDX template)

content/reference/language/your-topic.mdx
---
title: "std::your_type"
description: "One sentence description for SEO and previews."
category: language    # language | library | idiom | tooling
difficulty: 3         # 1=beginner 5=expert
since: 17             # C++ standard that introduced it
tags: ["tag1", "tag2"]
updated: "2025-05-25"
---

## Overview
What it is and why it exists. 2-4 sentences.

## Syntax
```cpp
// Minimal declaration/usage
```

## Examples

### Basic use
```cpp
// Self-contained example that compiles
```

### Advanced use
```cpp
// A non-trivial real-world pattern
```

## Common pitfalls
- **Pitfall 1**: explanation
- **Pitfall 2**: explanation

## See also
- Related concept A
- Related concept B

License & attribution

All content contributions are licensed under CC-BY-SA 4.0. Code examples are MIT. Contributors are credited in the git history and, for major contributions, on the page itself. By submitting a pull request you agree to these terms.