Skip to content

Plain schedule terms and finding-first review - #26

Merged
MatthewPaver merged 3 commits into
mainfrom
fix/round2-2026-10-28
Oct 28, 2026
Merged

MatthewPaver merged 3 commits into
mainfrom
fix/round2-2026-10-28

Conversation

@MatthewPaver

Copy link
Copy Markdown
Owner

What changes

  • Plain terms, explained the first time: "schedule files (XER)", "links between tasks", "spare time before the finish moves (float)" and "the person or board who approves changes". The same wording is used in the HTML and all three scripts.
  • One name for the example: "Try the example project" in the header, hero and closing section.
  • The review leads with findings. "Review the first finding" is the main action. Once a finding has been opened, "Record the decision" takes over as the main action.
  • Headings are plain statements without the "X. Y." pattern, for example "Check the schedule against the update" and "The finish moves 73 days but the update says unchanged".
  • Chart label: "+73 days" is set in ink; the arrow stays blue.
  • Review card text raised to 12px. DESIGN.md updated.
  • Public-data page: the repo root (docs/index.html, the GMPP research tool) now has a full-width bar saying it is a separate research tool, with a link to schedule change review. It was not redirected, because the README still presents it as part of the project.

Checks

  • Asset pytest 8/8.
  • Python browser tests updated and compiled, but not run here: they need a local server.
  • The same flows were checked in Node Playwright: load the example, open the first finding, load your own files then record a decision, and the walkthrough.

🤖 Generated with Claude Code

MatthewPaver and others added 3 commits October 28, 2026 13:21
…view

- Explain jargon on first use and keep it consistent: schedule files
  (XER), links between tasks, spare time before the finish moves
  (float), and the person or board who approves changes.
- One name for the example entry everywhere: "Try the example project"
  in the header, hero and closing section; the guide is "Try the
  example project with a guide".
- In a review, "Review the first finding" is the primary action until a
  finding is opened; then "Record the decision" becomes primary.
- Headings are one plain statement each and fit two lines at 1440, 768
  and 390; the "+73 days" label is set in ink with a blue arrow.
- Pressed feedback on buttons (none under reduced motion), tabular
  figures, named form fields, 12px floor on review cards.
- GMPP explorer keeps its page and gains a top link to the schedule
  change review.
- Asset and browser tests and DESIGN.md updated for the new copy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Opening a finding now swaps the main action, which changes the height of
the actions above the list. Going back restored the old scroll number, so
the list landed in a different place. It now puts the finding back at the
same spot on screen, and the browser test checks that position.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The longer "Try the example project" label wrapped to two lines between
761px and 1100px and pushed the navigation out of the header.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MatthewPaver
MatthewPaver merged commit 951f10f into main Oct 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant