Alice Saga

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rules_conventions_and_policies [2022/09/03 23:42] – adminrules_conventions_and_policies [2026/01/03 01:26] (current) – [Linkage & Signposting] admin
Line 4: Line 4:
     * Create a c_template page under the namespace after your first competition of a page under a namespace.     * Create a c_template page under the namespace after your first competition of a page under a namespace.
   * Hints on [[https://www.dokuwiki.org/tips:good_style|good style]] and [[https://www.dokuwiki.org/tips:good_content|content]].   * Hints on [[https://www.dokuwiki.org/tips:good_style|good style]] and [[https://www.dokuwiki.org/tips:good_content|content]].
-  * Setting up [[https://www.dokuwiki.org/interwiki|interwiki]] shortcuts can help with linking to common resources. 
-  * Don't link images from external sites, unless when allowed to do so explicitly. 
   * Use [[https://www.dokuwiki.org/plugin:indexmenu|indexmenu]] sparingly. Describe the indexed namespace.   * Use [[https://www.dokuwiki.org/plugin:indexmenu|indexmenu]] sparingly. Describe the indexed namespace.
- 
-GDoc and Dokuwiki conventions may not translate. Consider building new conventions specifically for doku. 
  
 ==== Linkage & Signposting ==== ==== Linkage & Signposting ====
  
-  * Signpost the important terms such as **[[faction:the_academy|The Academy]] **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).+=== Linking === 
 + 
 +  * 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. 
 + 
 +=== Signposting === 
 + 
 +  * 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__. 
  
 ==== Namespace ==== ==== Namespace ====
Line 24: Line 30:
 ==== Quotes ==== ==== Quotes ====
  
->Quotations are indented by %%>%% and the source is indicated by a bullet point outside of the quotation immediately after it.+>//Quotations are indented by %%>%% , italicised and the source is indicated by a bullet point outside of the quotation immediately after it.//
  
   * Like this.   * Like this.
Line 52: Line 58:
 ===== Note for Writing ===== ===== Note for Writing =====
  
-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.+//GDoc and Dokuwiki conventions may not translate. Consider building new conventions specifically for doku.//
  
-  * Always began a project writing in small, segregated documents that carry a distinct +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.     * **Aim:** add a subtitle summary to supplement the title. Merge the documents before publishing.
   * Always use section breaks.   * Always use section breaks.
   * Always complete/perfect ONE piece of content to establish a writing style before writing another similar piece of content.   * 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 edit while writing. Edit in one week.  
-  * Never revise until a document is completed.+  * Never revise a document until it is complete.
  
 Italic and indent for examples and quotes. Italic and indent for examples and quotes.
Line 66: Line 74:
   * Underline for __emphasis__.   * Underline for __emphasis__.
   * Hyphens --- Used to make extended points and extrapolation of loaded terms.   * Hyphens --- Used to make extended points and extrapolation of loaded terms.
-  * Square Brackets highlight previous defined [Concepts]. +  * Square Brackets highlight previously defined [Concepts]. 
   * Braces for {mathematical expressions}.   * Braces for {mathematical expressions}.
   * Italic Bold for recurring **//key terms//**.   * Italic Bold for recurring **//key terms//**.
   * Always construct an **Aim** statement for a piece of document and a summative subtitle.   * Always construct an **Aim** statement for a piece of document and a summative subtitle.
 +
  
 ==== Notes for Style ==== ==== Notes for Style ====
  
-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.+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   * Scripture of Alice -> Book of Alice
Line 80: Line 89:
  
 However, the specialised terms will be retained in the [[Thematic Term Library|Thematic Term Library]]. However, the specialised terms will be retained in the [[Thematic Term Library|Thematic Term Library]].
 +
  
 ==== Writing Tenets ==== ==== Writing Tenets ====
Line 89: Line 99:
     * Precise     * Precise
   * **Usable: **Is this usable in an actual play of a game?   * **Usable: **Is this usable in an actual play of a game?
 +  * **%%Ambivalence:%%**
 +  * **Apathy:**
  
 === Good Activities to do to test out your entity's quality: === === Good Activities to do to test out your entity's quality: ===
Line 95: Line 107:
  
   * **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:   * **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.+    * 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.       * **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.       * **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.
Driven by DokuWiki
rules_conventions_and_policies.1662262939.txt.gz · Last modified: 2022/09/03 23:42 by admin