How the guides are built

From concept to pattern to revision.

The practical framework used to create and expand topic pages in the writing library.

1. Identify the job

The page begins with the reader’s task: understand a concept, produce a piece of writing, compare patterns, fill a framework, or generate material. Closely related keywords are consolidated when the task is the same.

2. Define the pattern

The guide states what the writing form or concept is, what successful use looks like, and which structural choices matter. This gives the examples a reason to exist.

3. Demonstrate variation

Examples vary subject, audience, purpose, tone, evidence, and sentence shape. Useful examples demonstrate a pattern without pretending one sentence fits every context.

4. Add reusable structure carefully

Templates are intentionally incomplete. They preserve the functional skeleton while requiring the user to supply truthful details and remove irrelevant language.

5. Connect neighboring concepts

Internal links are chosen from shared writing tasks and topic clusters so readers can move from a broad guide to a more specific next question without wandering through unrelated keyword pages.

6. Expand only after depth exists

The engine keeps a private backlog of future topics. A planned topic is not automatically public or indexable. Future content waves can add depth, then the same quality gate determines whether the route joins the sitemap; promoted topics are automatically excluded from the remaining backlog count.