• Make use of NameSpace Templates.
  • Create a c_template page under the namespace after your first competition of a page under a namespace.
• Hints on good style and content.
• Setting up interwiki shortcuts can help with linking to common resources.
• Don't link images from external sites, unless when allowed to do so explicitly.
• Use indexmenu sparingly. Describe the indexed namespace.

GDoc and Dokuwiki conventions may not translate. Consider building new conventions specifically for doku.

Quotations are indented by > and the source is indicated by a bullet point outside of the quotation immediately after it.

• Like this.

• Use full names: The_[insername] for proper nouns.
• Try not to use a page with the same name as the namespace. However, if you do, you must use the page name (instead of start for the namespace) it should be for the following reasons:
  • The page will introduce the namespace as a portal to its namespaces and/or pages (as a start page).

1. Copy into posemirror editor.
2. Toggle back to default editor.
3. Copy into a better editor (vscode) and replace the non-edit syntaxes

(i.e. %%, //, \\)

1. Copy back into the default editor and save.

Must separate prescriptive and descriptive writing. Separate advice (guides) in appendixes to classifications (study) of the main body. The derivative and generative contents (product) will exist under their own context as a project.

• Always began a project writing in small, segregated documents that carry a distinct
  • Aim: add a subtitle summary to supplement the title. Merge the documents before publishing.
• Always use section breaks.
• Always complete/perfect ONE piece of content to establish a writing style before writing another similar piece of content.
• Never edit while writing, Edit in one week.
• Never revise until a document is completed.

Italic and indent for examples and quotes.

• Bold for signposting.
• Underline for emphasis.
• Hyphens — Used to make extended points and extrapolation of loaded terms.
• Square Brackets highlight previous defined [Concepts].
• Braces for {mathematical expressions}.
• Italic Bold for recurring key terms.
• Always construct an Aim statement for a piece of document and a summative subtitle.

Use generic terms where possible. A good convention is to look at the name and see if you can deconstruct the name into a composition of terms suppose you are explaining English to someone who is learning it. If you can, use the basic lexicon that you would use to explain the term to that beginner.

• Scripture of Alice → Book of Alice
• Chronicles of Maple → Book of Maple
• Tome of Marowlyth → Book of Marowlyth

However, the specialised terms will be retained in the Thematic Term Library.

• Incisive
• Restraint:
  • Informed
  • Specific
  • Precise
• Usable: Is this usable in an actual play of a game?

Assuming play session conditions at a table, read through the following activities and practice it:

• Querying for Reference: After writing, come back after at least a week. Open it up, read and with no more than 30 sec, try to find out as much of the following queries:
  • You ran into a (inavoidable) cross-road confrontation with an urchin with stolen bread.
    • Character: Construct at least three conversation chains detailing an internal response and an external response accurate to their characteristics in attitude and disposition.
    • Location: Construct a scene description with at least three features that you may immediately recite to the table accurate to the location's characteristics in theme and mood.

The page content of this wiki loosely follows the entity template scaffolding principle.

• Lore is freeform.
• Characters, Locations and Events/Stimuli fall under the entities principle.

• Idols instead of deities.
• Devotees refer to followers, believers etc.