Reading these docs
What these pages are for and how they're organized.
These pages are field notes on the engine — short, opinionated walkthroughs of the subsystems that carry Command & Conquer: Generals Remastered. They're not API reference and they're not a tutorial. Each page tries to answer three questions about one thing:
- What is it?
- How does it work?
- What are the quirks — the stuff that tripped us up?
How the site is laid out
The navigation tree on the left groups articles by subsystem: rendering, pathfinder, netcode, audio, and so on. Click any entry to load it in place — the video backdrop and the footer stay mounted across navigation, so moving between articles feels instant.
The toolbar at the top shows a breadcrumb trail so you always know where you are. On narrow viewports the nav collapses into a drawer at the top.
Contributing a new doc
A doc is a single Markdown file under
Web/GeneralsRemastered.Web/Docs/Content/. The file path becomes the URL,
lowercased — so Content/rendering/d3d11-backend.md lives at
/docs/rendering/d3d11-backend.
Every file opens with a YAML frontmatter block:
---
title: D3D11 Rendering Backend
description: How the DX11 port replaces the original D3D8 pipeline.
order: 10
author: Sonnet
updated: 2026-04-15
---
title is the display name (falls back to the filename). order is a sort
key within its folder — lower values come first. A folder can optionally
carry a _meta.yml that sets its section title and order in the parent nav.
In development the content directory is watched: save a file and refresh — the nav tree rebuilds in place.
House style
- Short sentences. Shorter than you think.
- Concrete over abstract. Name the function, name the file, name the line.
- Own the quirks. If something is weird, say so plainly and explain why. The goal is a reader who walks away with calibrated expectations, not a marketing pitch.