Setting up a Share Subtree
To publish a section of your grimoire:- Tag the Share Root: Go to the note or folder you want to share and attach the label
#shareRoot. - Access the URL: The share will be served at
http://your-core-ip:8080/share/noteId(or via custom slugs).
Share Configuration Labels
You can fine-tune how shared trees behave by adding these canonical labels to your notes:| Label | Value | Description |
|---|---|---|
#shareRoot | (none) | Designates the selected note and all of its sub-notes as a public share. |
#shareAlias | slug-string | Creates a custom, human-readable URL slug (e.g. #shareAlias = "blackstone" serves the note at /share/blackstone). |
#shareCredentials | user:password | Sets Basic HTTP Authentication. Visitors must enter this username and password to view the share. |
#shareIndex | (none) | Marks the selected note as the default home/landing page of the share. |
#shareHiddenFromTree | (none) | Keeps the note accessible via direct link, but hides it from the sidebar navigation tree. |
#shareDisallowRobotIndexing | (none) | Injects noindex headers to prevent Google and search engines from indexing your campaign wiki. |
Hiding Secret GM Content
You don’t have to maintain separate “player” and “GM” wikis. AllCodex allows you to mix player-safe lore and GM secrets in the same notes, using two gating mechanisms:Note-Level Gates
#draftTag: If you add#draftto a note, it will be completely hidden from the public share navigation, even if it lives inside a shared folder.#gmOnlyTag: If you add#gmOnlyto a note, it will return a404 Not Foundto any public visitor, keeping your secrets secure.
Section-Level Gates (HTML Classes)
If you want players to read a note’s general description but hide specific spoilers, you can gate individual paragraphs, lists, or tables:- Wrap your secrets in a container with the CSS class
.gm-only. - The Core share renderer automatically parses note HTML at output time and strips out any element containing the
.gm-onlyclass before sending it to public visitors.