Skip to content

Phase 5: Live-features architecture + cutover #6

Open

Description

@neuromechanist

Retargeted (website#498): the NSG connector deliverable is superseded by NEMAR compute (#493, nemarOrg/nemar-cli#2021). website#498 removes the dataset page Compute dialog's link to this issue; that change is live once it reaches production. The other deliverables were closed out or overtaken on 2026-08-03, see the comments.

Part of #1.

Scope

Architecture documents and placeholder UI for the deferred live features, then the cutover plan to switch nemar.org DNS to the new site.

Deliverables

  • Design doc .context/viewer_architecture.md: low-resolution (100 Hz) EEG preview pipeline. Generation during publish (extend nemar-tools), S3 layout (s3://nemar/<id>/preview/<bids-path>.float32), Worker streaming endpoint, frontend canvas-based viewer. Open follow-up issue on nemarOrg/nemar-cli + nemarOrg/website for implementation.
  • Design doc .context/nsg_connector_architecture.md: NSG REST API connector. Worker proxy with NSG OAuth, dataset-level "Compute" launch flow, status polling. Open follow-up issue on nemarOrg/nemar-cli. Superseded by Epic: Website compute surfaces #493 and Epic: Third-party compute: access, user API, nemar compute, partner contract nemar-cli#2021.
  • Wire Vis / Compute placeholder UI to open a "coming soon - track progress on issue #X" modal linking to the follow-up issues (Compute: superseded, see above)
  • Accessibility audit + fixes (keyboard nav, ARIA, contrast)
  • Light/dark theme polish + reduced-motion handling
  • Performance pass: bundle analysis, image optimization, font preload, CDN cache headers
  • DNS cutover plan in .context/cutover_plan.md: switch www.nemar.org to Cloudflare Pages, keep legacy.nemar.org for 90 days, redirect map for old /dataexplorer/... URLs

Out of scope

  • Implementing the viewer or NSG connector (these become their own epics)

Acceptance

  • Two architecture docs reviewed and merged
  • Three follow-up issues created and linked
  • Lighthouse a11y >= 95, perf >= 90, SEO >= 95 on landing + Discover + dataset detail
  • Cutover doc has a concrete date + rollback procedure

Activity

  1. neuromechanist commented on Aug 3, 2026

    @neuromechanist
    ContributorAuthor

    Closing: the phase's purpose was to design the deferred live features and plan the cutover. Both were overtaken by actually building and shipping them.

    • DNS cutover — DONE. The apex cutover landed 2026-07-29 (Apex cutover: ww2 becomes nemar.org, legacy moves to ww1, legacy URLs must keep resolving #190); nemar.org, www, ww2, and app.nemar.org all serve this build, with ww2 deliberately kept alive so persistently-cached 301s land on a working page. The host model is documented in AGENTS.md rather than a one-off .context/cutover_plan.md.
    • Viewer architecture doc + 'coming soon' placeholder — superseded by the real thing. The WebGL EEG viewer is built and shipped (src/lib/eeg-viewer/: traces, montages, topo, DSP, filters, events, all unit-tested), served from zarr.nemar.org. A design doc for a feature already in production is not worth writing.
    • Accessibility, theme, and performance passes — done incrementally across the epic instead of as one phase-end sweep (7953145 design-review a11y fixes, 27ff388 AA contrast, cdac663 dialog a11y, and the cold-paint perf epic Epic: Cold-paint perf + cache hygiene for dataset detail #66, closed).

    The one deliverable with no successor is the NSG connector architecture doc; there is no compute-launch flow today and no open work depending on that document. If NSG compute gets picked up, it should start as its own epic against the current architecture, not from this issue.

    Open follow-ups that came out of this area are tracked on their own: #208 (viewer zarr fetches on unmount), #212 (staging app-host counterpart).

  2. neuromechanist commented on Aug 3, 2026

    @neuromechanist
    ContributorAuthor

    Reopening, narrowed. I closed this a few minutes ago as done-or-superseded, which was wrong on one count: the live product links here. ActionBar.astro:215 renders "Direct compute access is coming soon... tracked on #6" inside the Compute dialog on every dataset page, and that link is live on production right now. Closing it points real visitors at a closed issue.

    Remaining scope is exactly one thing: the NSG compute connector. One-click submission from a dataset page (Worker proxy with NSG OAuth, launch flow, status polling). The Compute dialog today is a good manual fallback (NSG portal instructions, a nemar-cli recipe, direct file access), not the connector.

    Everything else this issue asked for is done or was overtaken, and is out of scope here:

    So: keep open until either the NSG connector is built, or the Compute dialog stops pointing here.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions