• 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.
• Use indexmenu sparingly. Describe the indexed namespace.

• DON'T link shortcuts can help with linking to common resources.
• Don't link images from external sites, unless when allowed to do so explicitly.

• Signpost the important terms such as the first time it is used with bold and linkage. Subsequent re-formatting, in the same way, is not necessary nor prohibited (but it would be a lot of work).
• If the signposted section is a page header, no need to link.
• ALWAYS try to link child page with ~ (self reference as namespace) where possible. Especially with extensions, as doku wiki's auto link adjustment does not cover extension blocks.

• Use full names: The_[insername] for proper nouns.
• Default start page: should be under the namespace it is under rather than under the parent namespace.
  • Use the page name (instead of start for the namespace) and,
  • Try not to use a page with the same name as the namespace. However, if you do, 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).

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

• Like this.

• Include any thought up quotes as a page under that respective ebooks and include the quoted block with {{page>lore:world_bible:book_of_alice:chapter_0:1&firstseconly&noheader&noreadmore}}.

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.

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

Must separate prescriptive and descriptive writing. Separate advice (guides) in appendices to classifications (study) of the main body. The derivative and generative content (product) will exist within its own context as a project.

• Always begin a project by writing in small, separate documents that focus on a distinct topic.
  • 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 a document until it is complete.

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 previously 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 examine the name and see if you can deconstruct it into a composition of terms, such as when explaining English to someone 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?
• Ambivalence:
• Apathy:

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 an (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.