Repository navigation
Add configurable informational guidance for courts and filing types - #286
Merged
Merged
Conversation
The guidance box was rendered in workflow_base before the page's h1, so a screen reader moving by headings met a level-2 guidance heading before the page title. Include it right after each page's h1 instead, and keep it as an h2 so it is still reachable by heading. Validate the guidance rules once per loaded config rather than on every page render, so an invalid rule logs one warning instead of one per page view. Add a development-only FILING_GUIDANCE_DEMO_FILE setting and a sample file under testing/, so the guidance boxes can be checked locally without putting demonstration messages in a state's config. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
End-to-end check against a local server with On upload, check documents, organize and review, the demo box appears after the page 🤖 Generated with Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jurisdictions can now configure informational filing guidance that appears on selected workflow steps, right after the page heading. Match saved court, case category/type/subtype, filing type, and new/existing-case codes; target a county or division by listing its court codes. Supporting documents participate in filing-type matching, and messages refresh when saved choices are rendered or resumed.
Messages support plain text, HTTPS resource links, and the existing configuration translation workflow. Configuration checks report malformed rules; informational guidance never requires acknowledgment or blocks a filing. Rules are validated once per loaded config, so an invalid rule logs one warning instead of one per page view. The partner guide documents placement, matching, authoring, and translation with a clearly marked placeholder example.
No real local-court instructions are enabled by this PR. Jurisdictions must supply reviewed wording and current court codes. Unsaved dropdown changes do not refresh messages in this first pass.
For local checks, the development-only
FILING_GUIDANCE_DEMO_FILEsetting loads demonstration rules fromtesting/filing-guidance-demo.yaml. Staging and production settings never read it, and its strings stay out of the translation catalog.Accessibility
The guidance box is included after each page's
h1(not inworkflow_basebefore it), and keeps itsh2, so heading navigation reaches the page title first and still finds the guidance.Validation: guidance/workflow/translation tests (including one that every workflow template places guidance after its
h1), full Python and JS suites, and an end-to-end run against a local server with the demo file (see the comment below). The Docusaurus production build passed.Closes #198.
🤖 Generated with Claude Code