Wiki contribution guide

First of all, thank you for contributing to the Post-Self wiki! This guide will help through the process of creating and editing pages.

Types of canon

There are three types of canon that will appear on this wiki:

Canon: information from works that have been actively published. This is largely immutable.
Paracanon: information that actively informs canon, yet which does not appear in the work itself. This may be mutable. You may wish to mark paracanon using the {{Paracanon}} template within the section containing it.
Protocanon: information that is in development, nice to have, or generally accepted within the community, yet which is unrelated to any of the canon. This may not be a wise choice to include on the wiki as a source of truth, yet may provide information for creators to use as a springboard going forward. Please mark protocanon as such using the {{Protocanon}} template within the section containing it.

Things such as headcanon or noncanon information are best kept to community spaces.

Names

Every instance is a complete person, and every cladist deserves to have their individuality recognized. This means that, if an instance changes their identity — for instance, when True Name becomes Sasha — they should each get their own page. This also includes cladists who exist in multiple cases on each of the three Systems, meaning that True Name#Castor and True Name#Pollux get their own pages distinct from the instance of True Name who remains on Lagrange.

Exceptions to this rule are very rare, and involve a change in name without a change in identity, such as E.W., who simply changed his common name and rescinded his clade identity.

Sourcing

Sourcing may be done via citations, within the text, or devoting a section to the work. The goal is not to be super nitpicky about it, but along finer points, it might be worth it to point others in the direction of where to look.

Discussion

While talk pages are handy, talking things out in the Discord server or Telegram group might provide more immediate feedback. All the same, be open to discussion surrounding various points, and work to find a path forward that helps maintain a coherent knowledgebase.