Skip to content

Build a public Topocode marketing site #74

Open

Description

@jdylanmc

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/topo-code@0.1.0. 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

  1. jdylanmc commented on Sep 29, 2026

    @jdylanmc
    OwnerAuthor

    This was generated by AI during triage.

    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.

  2. jdylanmc commented on Oct 1, 2026

    @jdylanmc
    OwnerAuthor

    Confirmed direction

    Use this issue as the anchor for Topocode's public static marketing site.

    • Host the initial site on GitHub Pages, using the GitHub-provided address.
    • Support moving to a custom domain later, after the owner purchases one.
    • A domain purchase is not a prerequisite for the initial launch. Plan the 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 explicitly
    changed. This update records direction; it does not start implementation or
    select/purchase a domain.

  3. jdylanmc commented on Oct 1, 2026

    @jdylanmc
    OwnerAuthor

    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:

    • Marketing content explaining what Topocode does and why it exists.
    • Clear installation and usage instructions matching the released product (currently 0.2.0).
    • Navigable documentation generated from repository documentation.
    • Prominent link to the GitHub repository.
    • A roadmap outlining the backlog.
    • Topocode’s own topology as a public demo; no PR-Sniper proof-of-concept content.
    • Generate a static site and deploy it automatically to GitHub Pages through CI.
    • Keep later custom-domain adoption possible; no domain purchase required to launch.

    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.

  4. jdylanmc commented on Oct 1, 2026

    @jdylanmc
    OwnerAuthor

    Owner answers — launch decisions

    • Navigation: Home, Docs, Roadmap, Demo, and a prominent GitHub link; cohesive Topocode branding.
    • Provide a temporary theme selector with seven distinct color themes so the owner can explore and select a favorite. Apply the selected theme consistently across the site and embedded demo. Final palette selection remains owner-owned; do not remove the selector before that choice.
    • Tooling: agent may choose appropriate static-site tooling after repository inspection.
    • Documentation: generate from repository Markdown without duplicate sources; cover installation, quickstart, agent workflow, story authoring, CLI/configuration, Rust/Tauri support, and current limitations.
    • Roadmap: curated Now / Next / Later with issue links, maintained in the repository; no promised dates.
    • Demo: interactive curated Topocode self-demo with architecture/key workflows and a full-screen link. Commit authored stories; CI validates and bundles them, fails on stale evidence, and never silently rewrites explanations.
    • Delivery: automatic GitHub Pages deployment from main, without a separate visual-review gate. Retain PR build/link/accessibility/browser checks. Initial project Pages URL, with later custom-domain compatibility.

    These answers settle the requested clarification round. No implementation, merge, or deployment has been performed by this update.

  5. jdylanmc commented on Oct 1, 2026

    @jdylanmc
    OwnerAuthor

    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, branch jdylanmc/public-site, base 1fcf2a1. No merge or deployment has occurred.

  6. jdylanmc commented on Oct 2, 2026

    @jdylanmc
    OwnerAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestneeds-triageMaintainer evaluation needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions