Pages UX: story-first showcase, ready-to-explore runs, and collapsible milestone chapters
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, typescript
Research direction
Start with docs/index.html and the checked-in docs/m4-preview.json, docs/m3-preview.json, and docs/run.csv artifacts to trace the current Pages experience and available saved runs. Review the existing M3/M4 rendering and validation contracts before shaping the new explorer and milestone disclosures. Done means the acceptance criteria are met, including responsive browser regressions for selection, disclosure, artifact errors, and the absence of fabricated samples.
Written by the indexing model from the issue text.
Description
Goal
Make the current static GitHub Pages experience welcoming and legible instead of an unstructured wall of charts. Let a new visitor explore meaningful existing deterministic outcomes immediately, with M0–M4 individually expandable as milestone chapters.
Evidence
Owner feedback (2026-10-26): the Pages UI has become unreadable compared with the legacy visualization; each block should convey a useful idea and each milestone should be behind a disclosure. Source docs/index.html currently leads with all M4 small multiples and then the full M3 dashboard; M0–M2 and the legacy viewer share one historical disclosure. Real docs/m4-preview.json, docs/m3-preview.json and docs/run.csv already exist.
Scope
- A coherent, responsive editorial hero and concise scenario explorer on initial load using real, checked-in observation artifacts.
- Show M4 closed economy and M3 market as interactive saved-run timelines; expose the legacy four-city replay as legacy, not the canonical runtime.
- Meaningful headline data, descriptions of what is measured, correct units and explicit separation of measured changes from causal explanation.
- One accessible, normally collapsed native
detailsper milestone M0–M4, and one for the legacy experience. Provide direct buttons to expand and navigate. - Demote bulk plots and exact numeric tables to user-requested detail; retain existing validation, artifact safety and canonical read-only boundary.
- Add responsive/browser regressions for selection, disclosure, artifact behavior and no fake samples.
Non-goals
Not the future M11 Worker runner, new economic engine, new invented scenarios, server APIs, fabricated events/causal attribution, major changes to model equations, rewriting the legacy C# oracle.
Acceptance criteria
- Loading Pages without interacting shows an inviting, nonempty curated example with actual checked-in simulation values and a working tick scrubber.
- Switching from M4 to M3 changes all selected-run summary figures consistently; invalid/unavailable artifacts show honest errors.
- Each M0–M4 and legacy has its own collapsed milestone disclosure. Deep-link/CTA opens the correct one; existing M3 and M4 render semantics remain verifiable.
- Each visible top-level block explains one question; exact-value tables are not initially expanded, and no incompatible units share a plot.
- Keyboard/mobile/reduced-motion layouts work without horizontal overflow. All asset paths remain GitHub Pages compatible.
Verification
Review the diff and published head; Vitest browser checks for Pages and existing M3/M4 contracts; TypeScript/build, retained .NET and Policy Guard CI; independent SLOPSTER exact-head QA prior to any later merge.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 0
- Avg merge
- 7h 21m
- Merged PRs (30d)
- 144
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from drevendev/trade_simulation
-
area:docs priority:normal type:docs
Difficulty 3/5 1-2 days Newbie friendliness 74/100
drevendev/trade_simulation#963 ·
Maintainers usually reply within 1 day
-
qa status:needs-triage
Difficulty 5/5 Over a week Newbie friendliness 8/100
drevendev/trade_simulation#926 ·
Maintainers usually reply within 1 day
-
area:tooling priority:normal status:in-progress type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
drevendev/trade_simulation#829 · 1 comment ·
Maintainers usually reply within 1 day
-
M4 physical stock authority: exact tick overlay, owner-bucket mapping and migration performanceOpenarea:simulation-core priority:normal status:blocked type:feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
drevendev/trade_simulation#800 ·
Maintainers usually reply within 1 day
-
area:market priority:high status:blocked type:feature
Difficulty 5/5 Over a week Newbie friendliness 24/100
drevendev/trade_simulation#799 ·
Maintainers usually reply within 1 day
All issues in drevendev/trade_simulation
Similar issues
-
test-reliability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Azure/azure-sdk-for-js#40672 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
HarperFast/studio#2067 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
liberation-data/drivine#639 · 2 comments ·
Maintainers usually reply within 1 day