DexterLab Content Rules
Purpose of This Document
DexterLab is built on clarity, rigor, and long‑term maintainability. This document defines the official rules for creating, organizing, and maintaining content across the entire site. It ensures that every new page fits into the structure, follows the same philosophy, and remains consistent with the Lab’s identity.
Anyone contributing to the Lab should follow these rules.
Content Classification
Every new page must belong to one and only one of the following categories:
- Architectures
- Blocks
- Fundamentals
- RTL
- Docs
- Notes
- Workflows
- Paths
- Mindset
- GitHub
- Governance
- Inside DexterLab
- Footer Pages
If a page does not clearly fit into one of these categories, it should not be created.
Section Containers
Each category has a dedicated landing page that acts as its official container:
/architectures//blocks//fundamentals//rtl//docs//notes//workflows//paths//mindset//github//governance//contacts/inside-dexterlab/
Every new page must be placed under the correct parent and linked from the corresponding landing page.
The “Single Nature” Rule
Every technical page must be exactly one of the following:
- an architecture
- a fundamental concept
- an implementation
Never mix these in a single page.
If a page contains both architecture and RTL, it must be split into two separate pages.
GitHub Integration
Technical pages must:
- link directly to the relevant GitHub files
- avoid duplicating code
- avoid embedding long snippets (those belong in Docs → Templates & Snippets)
- avoid mirroring repositories or storing code in WordPress
The DexterLab Library page is the only top‑level entry point to GitHub.
Governance vs. Narrative Content
DexterLab has two types of non‑technical content:
- Governance — rules, processes, contributor guidelines
- Inside DexterLab — playful, narrative, meta content
Governance pages are public but not part of the playful narrative.
Inside DexterLab pages are public and live under Contacts.
These two worlds must remain separate.
Content Hygiene
Before creating a new page, always check:
- whether a similar page already exists
- whether the topic is already covered in Fundamentals, Blocks, or Notes
- whether the content is too short (→ Docs)
- whether the content is too personal or experimental (→ Inside DexterLab)
- whether the content is too operational (→ Governance)
If the answer is unclear, the page should not be created until clarified.
Learning Path Integration
Every technical page should be reachable from:
- its category landing page
- at least one Learning Path (when applicable)
- cross‑links from related content
This creates a coherent learning ecosystem.
Minimum Content Requirements
Every page must include:
- a clear title
- an introduction explaining the purpose
- a structured body
- links to related pages
- a GitHub link when applicable
If any of these elements are missing, the page is considered incomplete.
Naming and Slugs
Slugs must be:
- lowercase
- short
- descriptive
- without spaces
- without underscores
Examples:
/blocks/axi4-stream-fifo//fundamentals/crc-math//governance/content-rules/
Redirects and URL Stability
Whenever a page is moved or renamed:
- create a 301 redirect
- update internal links
- ensure no duplicate slugs exist
URL stability is essential for long‑term maintainability.
Narrative Consistency
All pages must follow the DexterLab tone:
- technical pages → clear, rigorous, structured
- narrative pages → light, playful, human
- governance pages → neutral, precise, operational
Never mix tones within the same page.
Sustainable Growth
When adding new topics:
- check if they fit an existing category
- avoid creating new categories unless absolutely necessary
- update this document if a new category is introduced
The structure must remain stable over time.
The Technical Triangle
Every technical topic should connect to:
- a fundamental concept
- a block
- an implementation (if available)
This creates a stable triangle:
Fundamentals → Blocks → RTL
If a topic does not fit into this triangle, it may not belong on the site.
Periodic Maintenance
Every few months:
- review the structure
- remove obsolete pages
- update links
- verify redirects
- update this document if needed
DexterLab must remain clean, coherent, and scalable.
Final Note
DexterLab is both a technical platform and a human project. These rules ensure that the technical side remains rigorous and maintainable, while the narrative side remains playful and authentic.
Anyone contributing to the Lab is welcome — and encouraged — to follow these principles.
