Project Atlas AetherDev project hub
Atlas project development

Project Atlas

Project Atlas is the documentation hub for AetherDev systems. Atlas and Showcase sections with canonical project schema. Taxonomy views for pipeline, domains, patterns, types, and lifecycles. Content updates flow through Markdown bundles under `content/atlas/projects/`. Hugo builds the site into static assets for deployment.

Type
System
Lifecycle
Active
Last touched
2026-01-04
Visibility
Public

Purpose

Project Atlas is the documentation hub for AetherDev systems. Atlas and Showcase sections with canonical project schema. Taxonomy views for pipeline, domains, patterns, types, and lifecycles.

Current state

Atlas and Showcase sections created with new templates and navigation. Canonical Atlas schema implemented for all seeded projects. Taxonomy views enabled for pipeline, domains, patterns, types, and lifecycles. Lightweight Atlas filtering implemented with local JS. Last touched: 2026-01-04. Functionality and completeness: Project Atlas rename aligned across site content and documentation; build/deploy workflow is active.

Next step

Add baseline automated tests to cover critical flows; Add CI pipeline for build/test/lint; Document deployment/runtime environment (or add Dockerfile); Document interfaces (CLI flags, API endpoints, file formats); Add structured logging and basic health checks.

Interfaces

Inputs
  • Markdown content, Hugo front matter, data files
  • TOML config
  • data/*.toml
Outputs
  • Static HTML/CSS/JS assets

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Contributes in this stage.

Automation Engines

Contributes in this stage.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Artifacts

  • Canonical Atlas front matter schema

Operational notes

Constraints and scars

  • Keep Atlas entries accurate and avoid embedding secrets or PII in content.

Reliability posture

Failure modes and safe behavior: Build errors halt deployment; existing site remains unchanged. Idempotency / retries / batching behavior: Rebuilding yields deterministic output for identical content.

Observability

  • Logs: Hugo build output and CI deploy logs
  • Metrics/health checks: None documented

Security and privacy

Atlas content may include internal operational details; keep internal content separate from public visibility.

Dependencies

Upstream
  • CI/CD deploy pipeline

Ownership

Owners

Josh Barton

Users

Josh Barton (owner)

Project Atlas (repo: pages-aether)

Architecture & Major Components

  • High-level diagram (text):

    • Entry/trigger -> core logic -> outputs (details per docs below)

  • hugo.toml - Site configuration, menus, and taxonomies.

  • content/atlas/projects/ - Canonical Atlas project entries.

  • content/showcase/ - Curated showcase index.

  • content/patterns/ - Pattern library and taxonomy index.

  • content/playbooks/ - Operational playbooks and runbooks.

  • layouts/ - Hugo templates and partials.

  • Entry points: Hugo templates and content bundles

  • Top-level folders: archetypes, assets, content, data, layouts, resources, static

  • Key abstractions: Content bundles, Hugo templates, taxonomy pages, and Atlas schema

Setup / Build / Run

  • Build system(s): Hugo.
  • Local development: run hugo server from the repo root.
  • CI builds with Hugo and deploys the static output to the web server.