Completed Plans
All completed plans and investigations, sorted by date. Kept for reference.
| Plan | Goal | Completed |
|---|---|---|
| Steady-state flowchart v2 — Developer outside DCT + browser | — | 2026-04-17 |
| ArgoCD setup flowchart — design preserved, implementation deferred | — | 2026-04-17 |
| Deploy flowchart — for manual editing | — | 2026-04-17 |
| Plan: Update Contributor Documentation | Update all contributor documentation to reflect the unified template system. | 2026-04-17 |
| Plan: Unified Template System — TMP Phase 1 | Migrate template metadata from bash TEMPLATE_INFO + TEMPLATE_CATEGORIES to YAML (template-info.yaml + template-categories.yaml), generate a unified template-registry.json, and update Docusaurus to consume it. | 2026-04-17 |
| Plan: Transfer urbalurba-dev-templates to helpers-no (rename to dev-templates) | Transfer this repo from terchris/urbalurba-dev-templates to helpers-no/dev-templates with zero downtime. | 2026-04-17 |
| Feature: Add TEMPLATE_TOOLS to all TEMPLATE_INFO files | Add TEMPLATE_TOOLS field to every template's TEMPLATE_INFO so the DCT template installer can automatically install required devcontainer tools. | 2026-04-17 |
| Plan: TEMPLATE_README, PURPOSE→ABSTRACT Rename, and README Revision | Add TEMPLATE_README field, rename TEMPLATE_PURPOSE to TEMPLATE_ABSTRACT, and revise all template READMEs to follow a standard structure. This unblocks the DCT template installer from displaying the correct README path. | 2026-04-17 |
| Plan: Full Template Metadata and Docusaurus Generation Pipeline | Add all remaining metadata fields to TEMPLATE_INFO files, create generation scripts (adapted from UIS), and build the Docusaurus pipeline to auto-generate template pages, category pages, and plan indexes from metadata. | 2026-04-17 |
| Feature: Template-Info Schema Harmonisation | Clean up template-info.yaml field redundancy, align with Backstage patterns, and enable yaml-driven template documentation pages. Net result: remove dead fields, add new structured fields, render more content from yaml instead of README prose. | 2026-04-17 |
| Plan: Files Dropdown on Template Pages | Add a collapsible Files dropdown to every template's documentation page, listing the template's tracked files as a tree. Each file entry links to its GitHub blob URL; folder labels are plain text. The dropdown lives inside the Getting Started card between Prerequisites and Related templates. | 2026-04-17 |
| Plan: Template-side Dependabot Triage | Clear the 9 remaining template-side Dependabot alerts and 4 open Dependabot PRs by merging the safe ones, verifying the templates still build, and documenting any that we intentionally defer. | 2026-04-17 |
| Feature: Per-Template Architecture Diagram (Mermaid) | Render an auto-generated ## Architecture section on every non-overlay template documentation page, containing a Mermaid flowchart (steady-state) and a Mermaid sequence diagram (configure-time flow), derived from existing template registry data. | 2026-04-17 |
| Plan: Repository Cleanup and README Rewrite | Remove obsolete files, preserve valuable content for future Docusaurus site, and rewrite the README to accurately describe the repo. | 2026-04-17 |
Plan: Consolidate Script Documentation into project-scripts.md | Ship a single canonical document — website/docs/ai-developer/project-scripts.md — that documents every script under scripts/ for both human contributors and AI assistants. Add a scripts/README.md pointer so anyone browsing the source tree finds the doc. Redirect the existing contributors/scripts-reference.md to preserve the contributor-docs nav entry without duplicating content. | 2026-04-17 |
| Plan: Phase 1 — TMP fixes for templates with UIS services | Ship the TMP-side Phase 1 work from INVESTIGATE-improve-template-docs-with-services.md. Fix the bugs real-user testing surfaced in python-basic-webserver-database and postgresql-demo, plus the cross-cutting MDX generator and template hygiene issues. | 2026-04-17 |
| Feature: Environment Card on Template Detail Pages | Replace the current <TemplateGetStarted> card with a richer <TemplateEnvironment> card that surfaces everything a template sets up — devcontainer tools, cluster services, generated credentials, K8s secrets, port-forwards, and the database init schema (inlined and expandable). This plan is website-only. No changes to templates, template-info.yaml schema, DCT, or UIS. | 2026-04-17 |
| Plan: Environment Card Improvements | Ship four improvements to the Environment card on per-template doc pages: fix the ④ numbering bug, decouple the configure command from hardcoded text, rewrite the Configure sub-section intro, and auto-generate the "Expected output" sample block from registry data. | 2026-04-17 |
| Plan: Redesign Docusaurus Template Pages | Redesign the generated template detail pages and the /templates overview page to show full README content, logos, install commands, and better navigation — following UIS component patterns with CSS Modules and MDX. | 2026-04-17 |
| Plan: Add Contributors Section to Docusaurus Site | Add a minimum viable "Contributors" section to the Docusaurus site with guides for creating templates, metadata reference, naming conventions, scripts reference, and basic rules. | 2026-04-17 |
| Feature: Architecture Diagram v2 — Two-Diagram Split | Replace the v1 monolithic architecture diagram (single flowchart + single sequence) with two focused diagrams per template: Local development (how a developer sets up and runs the template) and Deployment (how code flows from git push to running pod). Each diagram has a flowchart + sequence pair. ArgoCD setup is documented as a third diagram type in mermaid-setup-argocd.md but suppressed for v2 until UIS implements the registration command. | 2026-04-17 |
| Plan: Architecture Diagram Display — Collapsible + Zoomable + Extensible | Ship the three changes locked in by the upstream investigation: | 2026-04-17 |
| Plan: Create ai-templates Content for plan-based-workflow | Create the ai-templates/plan-based-workflow/ folder in this repo with all template content, ready for dev-template-ai.sh (in DCT) to consume. | 2026-04-17 |
| Investigate: Update Contributor Documentation | Update all contributor documentation to reflect the unified template system — YAML metadata, template-registry.json, unified dev-template command, and the new template types (app, overlay, stack). | 2026-04-17 |
| Investigate: Unified Template System with Multiple Template Folders | Investigate merging dev-template and dev-template-ai into a single command that can handle multiple template folders (app templates, AI workflow templates, infrastructure templates, documentation templates, etc.). | 2026-04-17 |
| Investigate: Template Metadata System and README Standardisation | Design and implement a complete template metadata system — aligned with DCT and UIS patterns — that serves the Docusaurus website, template deployment, CLI tooling, and standardised READMEs. This includes enriching TEMPLATE_INFO with mandatory metadata fields, renaming fields for DCT consistency, revising READMEs to a standard structure, and creating the generation scripts (adapted from UIS) that populate the Docusaurus site. | 2026-04-17 |
| Investigate: Template-Info Schema Harmonisation with Backstage | Harmonise template-info.yaml with Backstage's catalog-info.yaml patterns so that our ODP (Open Developer Portal) feels familiar to Backstage users and migration between the two systems is simple. Clean up field redundancy (kill dead fields, clarify overlapping ones). Lay the groundwork for yaml-driven template documentation pages. | 2026-04-17 |
| Investigate: Files Dropdown on Template Pages | Add a collapsible list of a template's files to its documentation page, with each entry linking to the corresponding file on GitHub. Gives readers a quick overview of what a template actually contains, plus a one-click path from the docs to the source. | 2026-04-17 |
| Investigate: Per-Template Architecture Diagram (Mermaid) | Determine the best way to render an auto-generated architecture diagram on each template's documentation page that visualises what gets set up and the systems involved, using data the website already has (template-info.yaml, manifests/deployment.yaml, vendored DCT/UIS registries). | 2026-04-17 |
| Investigate: Repository Cleanup and README Update | Clean up obsolete files, remove the terchris/ folder, and update the README to accurately reflect the current state of the repository. | 2026-04-17 |
| Investigate: Improve Template Docs for Templates with UIS Services | Fix documentation, bugs, and rough edges for templates that depend on UIS services, in a way that actually ships. Real-user testing of python-basic-webserver-database surfaced concrete problems. This investigation scopes the minimum viable fix and defers speculation. | 2026-04-17 |
| Investigate: Housekeeping — Docusaurus upgrade and clearing open PRs | Decide how to clear the backlog of open Dependabot PRs and security alerts, primarily by upgrading Docusaurus from 3.9.2 to 3.10.0 (which should resolve most npm transitive vulnerabilities). Determine what to do with template-side dependency updates that the upgrade won't address. | 2026-04-17 |
| Investigate: GitHub Actions Node.js 24 Migration | Migrate GitHub Actions workflows from Node.js 20 actions to Node.js 24-compatible versions before the forced migration on June 2nd, 2026. | 2026-04-17 |
| Investigate: GitHub Pages Setup with Custom Domain | Enable GitHub Pages for this repo and configure tmp.sovereignsky.no as the custom domain. | 2026-04-17 |
| Investigate: Environment Card Improvements | Determine the right scope, design, and implementation approach for four improvements to the Environment card on per-template documentation pages: fix the ④ numbering bug, decouple the configure command from hardcoded text, rewrite the Configure sub-section intro, and auto-generate the "Expected output" sample block from registry data. | 2026-04-17 |
| Investigate: Improve Docusaurus Template Pages | Redesign the generated template detail pages in Docusaurus to show the full README content, template logo, install command, and better navigation — making each page a complete reference for the template. | 2026-04-17 |
| Investigate: Docusaurus Branding and Visual Identity | Add proper branding, logo, colors, and homepage design to the dev-templates Docusaurus site, following the UIS visual identity. | 2026-04-17 |
| Investigate: Dependency Vulnerabilities | Address 10 open Dependabot alerts across the website and template dependencies. | 2026-04-17 |
| Investigate: DCT Template Metadata Update | Update the DCT template installer scripts (dev-template.sh, dev-template-ai.sh) to work with the finalised template metadata fields from dev-templates. | 2026-04-17 |
| Investigate: Add Contributors Section to Docusaurus Site | Add a "Contributors" section to the Docusaurus site that explains how to create new templates, follow naming conventions, and contribute to the project. Start with a minimum viable structure — detailed content will be written later. | 2026-04-17 |
| Investigate: Architecture Diagram v2 — Three-Diagram Split | Redesign the per-template architecture diagrams from a single monolithic flowchart into three focused diagrams (local development, ArgoCD setup, CI/CD deployment), each paired with a sequence diagram. Determine how to auto-generate all six diagrams from existing template-info.yaml and registry data, and how to place them on the Docusaurus template page. | 2026-04-17 |
| Investigate: Architecture Diagram Display — Collapsible + Zoomable | Restructure the auto-generated ## Architecture section so it's discoverable (headings visible as signposts so readers know diagrams exist) but not imposing (each individual diagram collapsed behind a dropdown so readers who just want to run the template aren't confronted with a wall of SVGs). Also add click-to-zoom so diagrams remain readable when a developer DOES open one. Also design the data model now so adding a third or fourth diagram per sub-section later is additive, not a rewrite. | 2026-04-17 |
| Investigate: Create ai-developer Setup as an AI Template | Create AI workflow templates that can be installed into any project via a new dev-template-ai.sh command, following the same pattern as dev-template.sh for app templates. | 2026-04-17 |