Repository navigation
Description
This was generated by AI during triage.
Current status (2026-09-29)
Inspected baseline: main@b64bb2f.
Status: public marketing site not shipped; hosting, domain, and design decisions remain.
Topocode's CLI is now public as @jdylanmc/[email protected]. The generated per-repository storybook and repository README are not the public marketing site requested here.
Acceptance
-
Explain Topocode as the Storybook for architects, its intended users, value, and actual current capabilities.
-
Link prominently to the public documentation, GitHub repository, and real npm package/install entry point.
-
Publish a responsive, accessible static landing site after the owner chooses hosting, domain, and visual direction.
Marketing/information only: not the generated repository storybook, an authoring service, authentication, or a new deployment platform. Coordinate documentation links with #75 without inventing an already-live documentation site. npm publication is delivered and is not a remaining blocker.
Evidence: public package, product specification, and repository guidance.
Previous issue text and original requirements (historical; current disposition is above)
Outcome: A public static landing site that explains Topocode as the Storybook for architects and directs visitors to the documentation and GitHub repository.
Acceptance:
- Clearly explain what Topocode is, who it is for, and its core value.
- Provide prominent links to the documentation and https://github.com/jdylanmc/topo-code.
- Publish as a responsive, accessible static site.
Scope: Marketing/information site only; not a replacement for the generated in-repository storybook. Hosting, domain, and visual design remain to be decided.
Related: #13 (npm packaging/distribution); do not make npm publication a hard dependency.
Activity
jdylanmc commentedon Sep 29, 2026
Backlog reconciliation (2026-09-29)
Updated marketing scope to the real published npm entry point. Hosting/domain/design choices and the marketing site itself remain undelivered; generated repository output is not being counted as this site.
Evidence and preserved historical requirements are in the updated issue body. Baseline:
main@b64bb2f. No repository source or credential changes.jdylanmc commentedon Oct 1, 2026
Confirmed direction
Use this issue as the anchor for Topocode's public static marketing site.
so its links and assets work both under the initial Pages path and the later
custom domain.
This is the public product website, separate from the per-repository diagram
Home created by
topo init. Existing requirements remain unless explicitlychanged. This update records direction; it does not start implementation or
select/purchase a domain.
jdylanmc commentedon Oct 1, 2026
Owner-requested launch scope (2026-10-01)
Use this existing issue as the public static website anchor; coordinate documentation delivery with #75 rather than creating a duplicate.
Explicitly requested:
Implementation is not started or authorized by this scope capture. Owner requested clarifying questions first. Outstanding choices: visual direction/navigation, static-site tooling and documentation coverage, roadmap curation/update policy, demo depth/refresh behavior, and deployment/review gates. Preserve existing responsive/accessibility requirements and distinction from the per-repository Home.
jdylanmc commentedon Oct 1, 2026
Owner answers — launch decisions
These answers settle the requested clarification round. No implementation, merge, or deployment has been performed by this update.
jdylanmc commentedon Oct 1, 2026
Demo scope refinement — owner approved
Build the planned public website now, but leave the demo as an empty, functional Topocode Home. We will curate meaningful maps collaboratively, one at a time, in later work. Do not author automatic showcase maps or copy the existing repository stories into the public demo. Preserve those existing stories unchanged.
The initial demo is an honest unscanned scaffold, not proof of architectural coverage. Stale-source validation becomes a publication gate as source-backed public stories are deliberately added; no empty-demo check should be described as evidence that maps are accurate.
Implementation worktree:
topo-code-public-site, branchjdylanmc/public-site, base1fcf2a1. No merge or deployment has occurred.jdylanmc commentedon Oct 2, 2026
Delivered via PR #87, merged to main as 7ed048e. Public site is live at https://jdylanmc.github.io/topo-code/ with the approved Blueprint/Contour look, live diagram-only homepage demo, curated roadmap, docs, and eight source-backed stories. Automatic GitHub Pages deployment from main passed: https://github.com/jdylanmc/topo-code/actions/runs/36966900170. Verified the live homepage/viewer, docs, roadmap, and module drilldown/return in Chromium with no page errors. Repository website link updated. AGENTS.md now requires affected docs/diagrams in the same PR, without blind hash refresh or a new scheduled process. No npm release performed.