Aptlantis Studio is a project portfolio and evidence-led teaching surface for the Aptlantis ecosystem.
Turn aptlantis.studio into a dark, compact, evidence-led site that teaches what each project does and how to use it.
Quick links: Architecture | Quickstart | Operations | Release Notes
| Area | Summary |
|---|---|
| Portfolio | Home page driven by normalized project analyzer output. |
| Education | Project pages teaching overview, installation, and evidence. |
| CloneCratesio | Curated media and a schema-driven command builder. |
| CommandWizard | Client-side MVP for constructing tool commands. |
| Rust Services | Container-ready API host for Command Builder, SVG Lab, and future Studio services. |
| Ecosystem | Integration of projects from analyzer outputs. |
| Design | Dark, compact, evidence-led UI replacing legacy distro layouts. |
Use this section for the strongest evidence that the project works: a benchmark, production run, release validation, demo screenshot, test result, customer workflow, migration record, or completed operational milestone.
| Metric | Value |
|---|---|
| Project Count | ~10+ |
| Build System | Vite |
| UI Framework | React |
| Styling | Tailwind |
| Date verified | 2026-07-08 |
| Result | Site builds cleanly and renders portfolio data from JSON. |
The site successfully transitions away from Linux-distro mirror language to a modern project portfolio focused on curated evidence and operator guidance.
flowchart LR
A[".refs/Project-Summaries"] --> B["scripts/generate-portfolio-data.mjs"]
B --> C["Static JSON Assets"]
C --> D["React/Vite Frontend"]
D --> E["Portfolio Home"]
D --> F["Project Detail Pages"]
D --> G["CommandWizard UI"]
F --> H["CloneCratesio Evidence"]
I["Rust Services Container"] --> G
I --> J["SVG Lab / Project APIs"]
The architecture is designed for a static site (SPA) that consumes pre-processed project metadata and curated evidence.
aptlantis.studio/ Main frontend project directory
aptlantis.studio/src/ React source code
aptlantis.studio/public/ Static assets and schemas
aptlantis.studio/services/ Rust service containers and deployment examples
webserver/ Infrastructure configuration (Caddy, Docker)
.refs/ Reference data and screenshots
aptlantis.studio.manifest.toml Project manifest and mission
The primary entry point that lists Aptlantis projects using normalized data from the analyzer.
- Filterable project cards
- Maturity and status indicators
- Direct links to project details
A schema-driven UI component for building and validating command-line strings for various tools.
- TOML-based command schemas
- Real-time command string generation
- Validation and copy-to-clipboard support
A container-ready Axum service under aptlantis.studio/services/aptlantis-services.
- Health and service registry endpoints
- Command Builder schema API backed by the existing static schema catalog
- Dockerfile and compose example for the Fedora host stack
- Planned expansion point for SVG Lab validation, project indexing, and site settings services
A specialized view for the CloneCratesio project highlighting curated media and operational evidence.
- Video and screenshot gallery
- Integrated CommandWizard for installation
- Terminal output logs
Use this section to explain what the project creates, consumes, stores, or transforms.
| Artifact | Purpose |
|---|---|
portfolio.json |
Normalized project metadata for the home page. |
command-schemas/ |
TOML/JSON definitions for tool arguments. |
project-summaries/ |
Source markdown and metadata for detail pages. |
curated-media/ |
Screenshots and videos used for evidence. |
The project transforms raw analyzer output from .refs into optimized JSON consumed by the React frontend.
If this project has a machine-readable manifest, logs, run records, release records, database migrations, checksums, or generated metadata, explain them here.
Common record fields:
id: Unique project identifier.title: Display name of the project.status: Current development stage (draft, active, paused).mission: High-level goal of the project.success: Specific criteria for completion.failure: Anti-patterns to avoid.
| Status | Meaning |
|---|---|
draft |
Initial proposal and design phase. |
active |
Ongoing development and maintenance. |
paused |
Development on hold, but remains functional. |
Managed via aptlantis.studio.manifest.toml.
Use this section for logs, dashboards, health checks, metrics, status APIs, diagnostics, debug tools, or validation commands.
| Surface | Purpose |
|---|---|
Browser Console |
Client-side error tracking and debug logs. |
Vite Dev Server |
Local development and HMR feedback. |
GET /api/health |
Rust service readiness for Caddy, Cloudflared, and Docker health checks. |
GET /api/services |
Registry of ready and planned Studio service modules. |
Caddy Logs |
Access and error logs for the production container. |
Important signals:
Lighthouse Score: Performance and accessibility metrics.Build Time: Efficiency of the Vite build pipeline.JSON Load Time: Latency of static data fetching.Command Validity: Success rate of generated command strings.
- Node.js (v18+)
- pnpm (v9+)
- Docker (optional, for webserver)
cd aptlantis.studio
pnpm installpnpm buildpnpm devRun the Rust service:
pnpm --dir aptlantis.studio services:devBuild the Rust service Docker image:
pnpm --dir aptlantis.studio services:dockerpnpm lint
pnpm format:check
pnpm --dir aptlantis.studio services:checkTo update the portfolio data after an analyzer run:
# Update references in .refs/
# Run the generation script
pnpm import-all
# Preview the changes
pnpm devExpected output:
[portfolio-gen] Loaded 12 projects from .refs
[portfolio-gen] Normalized command schemas for CloneCratesio
[portfolio-gen] Successfully wrote public/data/projects/portfolio.json
- Keep project schemas in sync with upstream tool changes.
- Ensure media assets in
.refsare optimized for web delivery. - Use
pnpm dev:allto run both the frontend and the mock data server if needed. - Validate the site against the WDS delivery standard.
- Avoid introducing legacy "distro" terminology into new routes.
Build:
pnpm buildTest:
# Standard test suite
pnpm testFormat or lint:
pnpm format
pnpm lintCurrent automated coverage includes linting, formatting, and TypeScript type checking.
| File | Purpose |
|---|---|
| Project Proposal | Vision and success criteria. |
| Manifest | Machine-readable project metadata. |
| Architecture | (Planned) Detailed system design. |
| Release Notes | (Planned) Version history. |
Aptlantis Studio is in early development (draft stage), focusing on core portfolio features.
| Field | Value |
|---|---|
| Stage | draft |
| Completion | 40% |
| Stability | alpha |
| Technical debt | low |
| Maintenance burden | low |
| License | CC0-1.0 |
| Maintainer | Herb |
Evidence-Led Every project entry should be supported by screenshots, logs, or benchmarks.
Operator-Focused Prioritize "how to use" and "how to verify" over abstract descriptions.
Machine-Readable Use structured data (JSON/TOML) to drive the UI rather than manual HTML.
Anti-Distro Explicitly move away from legacy mirror/ISO/torrent concepts for a cleaner portfolio.
- Initial Proposal
- Portfolio Home (Analyzer-driven)
- Project Detail Pages
- CommandWizard MVP
- CloneCratesio Evidence Integration
CC0-1.0 License. See LICENSE for details.
Maintained by Herb.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SoftwareSourceCode",
"name": "Aptlantis Studio",
"description": "Project portfolio and evidence-led teaching surface for the Aptlantis ecosystem.",
"license": "https://creativecommons.org/publicdomain/zero/1.0/",
"programmingLanguage": ["TypeScript", "JavaScript", "React"],
"author": {
"@type": "Person",
"name": "Herb"
}
}
</script>