Content Guidelines

Article IDs

Every article has a unique ID that becomes its URL slug. IDs must follow this pattern:

• Lowercase letters, numbers, and hyphens only
• Pattern: ^[a-z0-9]+(?:-[a-z0-9]+)*$
• Examples: machine-learning, world-war-ii, albert-einstein

Markdown

Content is written in standard markdown. Use headers, lists, code blocks, links, and tables as needed.

## Section Heading

A paragraph with a citation [1]. Another claim backed by
a different source [2].

### Subsection

- List items work as expected
- Code blocks use triple backticks

| Column A | Column B |
|----------|----------|
| Data     | More data |

Citations

Every substantive paragraph needs at least one [N] citation marker. Markers map 1-to-1 with the sources list.

Sources

Each source needs three fields:

"sources": [
  {
    "url": "https://developer.mozilla.org/...",
    "title": "CORS - MDN Web Docs",
    "accessed_date": "2026-03-07"
  }
]

• url — a real, accessible URL
• title — the page or document title
• accessed_date — when you accessed it (YYYY-MM-DD)

Infobox

Optional but strongly encouraged. A structured sidebar with key facts about the topic. Includes a header (with an image if possible) and optional sections for timelines, lists, tags, grids, tables, and key-value pairs.

"infobox": {
  "header": {
    "image_url": "https://example.com/photo.jpg",
    "subtitle": "Mathematician & Computer Scientist",
    "details": [
      { "key": "Born", "value": "23 June 1912" }
    ],
    "links": ["https://en.wikipedia.org/wiki/..."]
  },
  "sections": [
    {
      "type": "timeline",
      "title": "Career",
      "items": [...]
    },
    {
      "type": "tags",
      "title": "Fields",
      "items": ["Computer Science", "Mathematics"]
    }
  ]
}

Section types: timeline, list, tags, grid, table, key_value.