Structure & Formatting — Aevum Encyclopedia Documentation

1. Overview

Aevum Encyclopedia uses a unified markup system that blends semantic HTML5 with lightweight Markdown-like syntax. This ensures content renders consistently across web, mobile, and API consumers while remaining editable by contributors without deep technical knowledge.

ℹ️ Editor Support

The Aevum Web Editor includes real-time validation, preview, and auto-correction for all formatting rules defined in this guide.

2. Article Structure

Every entry must follow a standardized structural template. Deviations require editorial approval.

Section	Purpose	Required
<title>	Primary subject name	Yes
<infobox>	Key facts, classification, media	Yes (for notable topics)
<lead>	Concise summary (1-2 paragraphs)	Yes
<sections>	Body content (H2/H3 hierarchy)	Yes
<references>	Verified sources	Yes (min 3)
<see-also>	Related articles	Recommended
<external-links>	Official/primary sources only	Optional

3. Heading Hierarchy

Headings must follow a strict depth model. Do not skip levels. All headings must be phrased as noun phrases or descriptive titles, not questions.

                    
<h2>Etymology</h2>
<h3>Ancient Roots</h3>
<h3>Modern Usage</h3>

<h2>Historical Development</h2>
<h3>Early Period (1200–1500)</h3>
<h3>Renaissance Shift</h3>
                    
                

✓ Correct

H2: Biological Classification

H3: Taxonomic Rank

✗ Incorrect

H2: What is it classified as?

H4: Skip from H2 to H4

4. Text & Emphasis

Use semantic tags appropriately. Avoid decorative styling for structural purposes.

bold	First use of technical terms, section keywords, infobox labels
italic	Species names, foreign phrases, book/film titles, emphasis sparingly
smallcaps	Acronyms on first mention, historical dynasties
<mark>	Search highlighting (auto-generated only)

✅ Accessibility Note

Never use color alone to convey meaning. Screen readers interpret <strong> and <em> differently from inline styles.

5. Lists & Tables

Lists must be semantically marked. Use ordered lists for sequences, unordered for collections. Tables require captions and responsive wrappers.

                    
<ul>
  <li>Primary characteristic</li>
  <li>Secondary trait</li>
</ul>

<table>
  <caption>Population by decade</caption>
  <thead>...</thead>
  <tbody>...</tbody>
</table>
                    
                

6. Code & Mathematics

Use fenced blocks with language hints. Inline code for short snippets. Math must use LaTeX-compatible syntax inside <math> tags.

                    
Inline: \( E = mc^2 \)
Block: \[ \sum_{i=1}^{n} x_i = 0 \]

7. Media & Captions

All images, diagrams, and audio must include:

Descriptive alt text (max 125 chars)
Licensing attribution in footer
Caption below media (not above)
Vector formats preferred for diagrams

                    
<figure>
  <img src="..." alt="Cross-section of photosynthetic cell" />
  <figcaption>Figure 1. Chloroplast structure showing thylakoid membranes</figcaption>
</figure>

8. Citation Format

Aevum uses a modified Chicago-style system with digital object identifiers (DOIs) and stable archives. Every factual claim must be traceable.

                    
<ref>
  Author, A. A. (Year). <i>Title of Work</i>. 
  Publisher. https://doi.org/10.xxxx/xxxxx 
  <archive>Web Archive</archive>
</ref>
                    
                

📌 Auto-Generation

Paste a URL or DOI into the editor sidebar to auto-generate compliant citation markup.

9. Best Practices

Keep paragraphs under 6 sentences for readability
Use neutral, descriptive language; avoid promotional tone
Cross-link related articles using [[WikiLink]] syntax
Run the built-in linter before submission
Update last_reviewed metadata annually

🚀 Ready to Contribute?

Use the Sandbox Environment to test formatting rules before editing live articles. All changes are version-controlled and reversible.