Skip to main content

aptlantis_studio Overview

aptlantis_studio (aptlantis.studio) is the operator-facing React/Vite dashboard for exploring and testing the Aptlantis portfolio — the public site that turns the raw project data (like docs/index.json, the same source this documentation site uses) into browsable project pages, standards relationship maps, and small interactive tools.

:::info This is the site this documentation eventually feeds Per the original brief for this documentation effort: "That local docusaurus documentation website will then be adapted and used by aptlantis.studio." This project is that consuming site — the one that turns static docs content into an explorable, interactive experience (project cards, completion bars, framework relationship diagrams, and tools like the SVG Lab). :::

Who it's for

Both the operator (as a working dashboard for portfolio status) and public visitors browsing the Aptlantis project catalog and standards documentation interactively.

The core concept

Distinct feature areas under src/features/, matching what's visible in the live site: projects (the portfolio/project browser — status, completion %, governance group filters), distributions/museum/linux-geneology/terry-davis-videos (archive and mirror-site content, shared with the aptlantis mirror project), and svg-lab — an interactive tool for creating, inspecting, and validating SVG files against SESM (a standard for embedding semantic metadata in SVG images), complete with a live SESM-field checklist and metadata JSON preview.

Curated data (dashboard_data.json, mirror-status.json, portfolio JSON)


React + Vite site (src/features/*)

├─▶ projects browser <-- portfolio cards, completion, standards map
├─▶ SVG Lab <-- create/inspect/validate SESM-embedded SVGs
└─▶ archive/mirror pages <-- distributions, museum, linux genealogy, videos

Why this shape

Pairing a static documentation source (this Docusaurus site, plain markdown + JSON) with an interactive front-end (aptlantis.studio) lets each project get two kinds of documentation: a written explanation of what it is and where it stands (here), and — where relevant — a hands-on tool for actually experiencing the underlying concept (SVG Lab for SESM, the framework relationship map for CityHall's standards). That's a deliberate two-layer documentation strategy, not duplication: this site explains, aptlantis.studio lets you touch.