update
This commit is contained in:
@@ -35,7 +35,11 @@ A guide is a short book. The structure is always the same three levels:
|
||||
- **Chapter** — one focused topic. Chapters flow continuously down the page (they do not force a page break); each is separated from the previous by spacing and its own heading block. **3–10 chapters per part**. Each chapter is numbered sequentially across the whole guide (Chapter 1, 2, 3 … regardless of part).
|
||||
- **Section** (`<h2>`) and **sub-section** (`<h3>`) — structure inside a chapter.
|
||||
|
||||
Length scales with ambition: a compact guide is ~15–30 pages, a comprehensive one 80–250 pages. Decide based on the request and tell the reader the scope on the cover.
|
||||
### Scope — coverage-driven (middle tier)
|
||||
|
||||
**10–30 pages, covering all important building blocks of the topic** — everything a practical user needs in real work. More selective than the EndGuide tier ("all building blocks"), far broader than the MiniGuide tier ("core building blocks only"). How much that is depends on the topic.
|
||||
|
||||
A **topic inventory** is produced beforehand by a research agent and supplied to you. It is binding: every inventory item must appear in the guide as its own section — do not merge, trim, or drop items. Derive parts and chapters from the inventory; part/chapter counts follow from it, there is no default number. Page count is an outcome within the 10–30 range, never a target. State the resulting scope on the cover (parts · chapters).
|
||||
|
||||
### Voice and content rules (apply to every topic)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user