Content Overview

Organization and conventions for the markdown that ships in data-content. Each section below has its own per-content-type page; this one covers the directory layout, file naming, and translation workflow.

Directory layout#

data-content/
├── wiki/                    # encyclopedia entries
│   ├── _index.md            # section index
│   ├── elohim.md
│   ├── raelism.md
│   └── ...
├── timeline/                # precessional ages
│   ├── _index.md
│   ├── age-of-aquarius.md
│   └── ...
├── library/                 # sacred and primary texts
│   ├── _index.md
│   └── ...
├── articles/                # long-form essays (idea-driven, evergreen)
├── news/                    # newsroom dispatches (event-driven, decays)
├── sources/                 # bibliography section index (JSON-driven)
├── de/                      # German translations
├── es/                      # Spanish
├── fr/                      # French
├── ja/                      # Japanese
├── ko/                      # Korean
├── ru/                      # Russian
├── zh/                      # Simplified Chinese
├── zh-Hant/                 # Traditional Chinese
├── he/                      # Hebrew (RTL)
└── i18n/
    └── glossary.json        # term translations

Content types#

Each content type has its own dedicated page in this section:

• Wiki Entry — encyclopedia-style definitions
• Article — long-form, idea-driven, evergreen
• Newsroom Dispatch — short, event-anchored
• Library Book — books with paragraph IDs
• Translations — i18n workflow
• Editorial Passes — what the editorial_pass field means

File naming conventions#

• Lowercase
• Hyphens for spaces: age-of-aquarius.md
• Match URL slugs
• Keep names short but descriptive

Section index files#

Each section needs an _index.md:

+++
title = "Wiki"
description = "Encyclopedia of terms and concepts"
template = "wiki-section.html"
sort_by = "title"
+++

Optional section introduction text.

Sources#

The /sources/ page is JSON-driven — its content comes from data/sources.json, built by scripts/build_sources.py in the www repo. The build also generates per-source detail pages at /sources/{id}/ for English and localized shells at /{lang}/sources/{id}/ from content/sources/_generated/*.md and content/{lang}/sources/_generated/*.md. It also writes a reverse data/sources/cited-by.json index for the Cited by blocks. Those generated stubs are not hand-authored; the underlying source record stays single-sourced in data/sources.json.

Every emitted record carries a licensing_status — merged from the hand-maintained sidecar data/sources/licensing.json (the single authority; never regenerated). Vocabulary: public_domain, licensed, unknown (examined, could not determine), and unverified (never examined — the builder default for any source absent from the sidecar). To record a determination, add the source id to the sidecar’s statuses map and re-run the build; do not edit sources.json directly.

Translations#

Translations mirror the English structure:

wiki/elohim.md           # English source
de/wiki/elohim.md        # German translation
fr/wiki/elohim.md        # French translation

For the full translation workflow, glossary use, and per-language notes, see Translations.

Content guidelines#

Titles#

• Clear and concise
• Under 60 characters for SEO

Descriptions#

• 150–160 characters
• Include primary keyword
• Describe content value

Body content#

• Markdown headings (## for h2)
• Link to related wiki entries
• Include references for claims (six-source minimum on new entries)
• Use shortcodes for special content

See the Frontmatter Reference for the full field list.