Use this handbook to understand the approved patterns.
Calm operational craft, carried through everything.
White and cool-gray surfaces. Charcoal and navy ink. Restrained Red Cross red. Clear hierarchy. Map and data first. The same decisions repeat until the work is unmistakably yours.
Experiment safely in the playground without changing the standard.
Export a proposal and decide which changes should become real.
Codex or Claude updates the repo, tests it, and carries it forward.
The family resemblance
The goal is not identical screens. It is consistent judgment: restrained color, disciplined type, strong information hierarchy, and familiar controls.
Inter carries the message.
Body copy, headings, labels, buttons, and editable prose stay in the UI family.
- Pure white and cool-gray—not cream, beige, or parchment.
- Red means brand, primary, urgent, or selected—not decoration.
- One UI family and one mono family.
- Approved logo assets only; never draw a substitute cross.
- Six-pixel controls, eight-pixel panels, restrained shadows.
Institutional, clear, and unmistakably related
Documents use the same system with more breathing room: pure-white interior pages, cool-gray cover canvas, charcoal/navy ink, restrained red, compact running headers, clean tables, and explicit sources and limitations.
Facility Closure
Decision Guardrails
A disciplined framework for evaluating access, continuity, risk, and mission impact.
Protect service continuity before optimizing the footprint.
Lead with the decision, then show the evidence, caveats, and operational implications.
| Guardrail | Status |
|---|---|
| Access continuity | Pass |
| Capacity | Review |
| Data confidence | Pass |
Readers should understand the decision before studying the method.
Sources, dates, limitations, and partner attribution are part of the design.
White plot surfaces, charcoal boundaries, navy context, red emphasis.
Warm beige, serif headlines, and editorial nostalgia are retired.
Operational meaning outranks decoration
Interface icons and map symbols are different systems. Controls use a coherent line-icon family. Operational map features use the supplied Red Cross DRO symbols when one exists.
Home and Zoom top-left, Basemap Gallery bottom-right, Scale Bar bottom-left, Search top-right when useful.
Suppress default Esri popups. A feature click opens the formatted app-owned right rail.
A deliberately configured Map Viewer popup may use validated HTML and Arcade.
No raw fields, system identifiers, access secrets, private contacts, or implementation details.
Filter, then fit.
Every filter that changes mapped results automatically fits the extent of all authoritative matches. The visible count, summaries, features, and camera must describe the same result set.
- One match
- Use a useful capped scale
- Zero matches
- Keep the camera; show zero results
- Clear filters
- Fit the full or governed initial extent
- Open rails
- Include every rail and header in padding
Red Cross feature and status symbols
Exact embedded graphics extracted from the supplied Portal guide—not CSS reproductions.
Portal guide pp. 3, 5-7 · SADS guide pp. 6-7Loading symbol catalog...
Configured inside the web map
- Population
- 55,478
- Chapter
- Northern New England
The same facts become a detail rail
Make the next decision obvious
Whenever a map contains shelters or wildfires, use these recognizable content profiles. Preserve the information order and general visual language; map the real source fields into it instead of copying an old schema.
Identify the selected feature and write its state in text.
Clients for shelters; acres and containment for wildfire.
Show only the facts that change interpretation or action.
Every operational value needs provenance and freshness.
Crystal River Community Center
- Address
- 100 Community Way
Crystal River, FL 34429 - Site
- Congregate shelter
- Managed by
- Partner organization
- Event
- DR 0000 · Example
The current client count is the decision measure. Location and management provide operational context without competing with it.
Name and written status · current clients and count time · address · site/management type · event context · source and freshness.
Contacts and shelter IDs appear only in authorized internal views—not by default.Williams Mine Fire
Skamania County, Washington
- Discovered
- July 14 · 7 days ago
- Residences destroyed
- 2
- Personnel
- 462
- Fire behavior
- Moderate
Growth has slowed, but active fire behavior continues along the northern perimeter. Values remain tied to the incident update below.
Name and location · acres and containment · discovery date · three to seven verified impacts or management facts · source and freshness.
Do not infer null casualties, damage, cause, containment, or evacuation status.Compact configured popup
Use validated fields and one Add content > Arcade block that returns the complete text element. Keep it narrow and scannable.
Persistent right detail rail
Suppress the Esri popup and present the same content order in the app-owned rail, with selection, close, loading, stale, null, and error states.
Popup Codes.pdf
Shelters pp. 8-9 · wildfire incidents pp. 10-13 · perimeters pp. 14-17. Reuse the content logic, not the old styling or field schema.
Visible for beginners. Fast for experts.
A click, shortcut, command-palette result, and touch control invoke the same command. Shortcuts supplement visible controls; they never replace them.
Close the topmost temporary surface, then exit selection or drill level.
Focus or open the primary search without firing while the user types.
Open the searchable command palette when the app has one.
Show the live command registry when more than three shortcuts exist.
Toggle the left rail in command-enabled two-rail applications.
Toggle the right rail without colliding with Shift+R reset.
- One command registry and one global dispatcher.
- Inactive while typing, composing text, repeating a key, or viewing a modal.
- Collision tests fail instead of silently choosing a winner.
- Help renders from the same registry that executes commands.
- Tooltip
- Short label or shortcut hint
- Popover
- Nearby choices
- Modal
- Focused temporary task
- Detail rail
- Persistent selected-object information
- Toast
- Brief confirmation or recoverable failure
Small decisions that repeat
Components stay compact, rectangular, accessible, and purposeful. Every control has a visible hover, focus, selected, and disabled state.
One coherent outline family. Custom operational glyphs live in one registry. Emoji are not production icons.
Explore a change without changing the standard
These controls affect only the preview below and this browser. Export a proposal when you find something worth considering; Codex or Claude can review, apply, test, and commit it.


What changed, what matters, what happens next.
The visual proposal should make the hierarchy clearer without turning the work into a new brand.
Both agents read the same authority
There is no separate Codex aesthetic and Claude aesthetic. The repository's agent files route both systems to the same visual, interaction, map, and document rules.
Use the Franzen standard in /Users/jefffranzen/dev/franzen-app-standards. Read this repo's DESIGN.md, then apply the canonical visual, interaction, map-symbol, popup/detail, and accessibility rules. For every map filter, follow references/FILTER_TO_EXTENT_STANDARD.md. For every shelter or wildfire map, follow references/SHELTER_AND_WILDFIRE_DETAIL_STANDARD.md. Preserve the current product's purpose and verify the real UI at desktop and mobile sizes.Follow /Users/jefffranzen/dev/franzen-app-standards as the design and interaction authority. Read the target repo's CLAUDE.md and DESIGN.md. For every map filter, follow references/FILTER_TO_EXTENT_STANDARD.md. For every shelter or wildfire map, follow references/SHELTER_AND_WILDFIRE_DETAIL_STANDARD.md. Use the supplied Red Cross operational symbols where applicable, keep custom-app feature details in the app-owned rail, and test every changed state before committing.node /Users/jefffranzen/dev/franzen-app-standards/scripts/install-app-standard.mjs /path/to/repoKnow what is authoritative
Canonical standards
DESIGN_SYSTEM.md, interaction references, tokens, agent rules, and templates in the private repository.
Red Cross evidence
Supplied Portal/Org, SADS DRO, and popup-code PDFs are archived privately and interpreted in the map-symbol reference.
Working exemplars
Lives Saved supplies the shell, GeoMenu the map-as-menu model, and ROP the command registry and operational icon language.
Playground proposals
Browser experiments are not standards until reviewed, applied to the repository, tested, committed, and published.
Keep code and standards in GitHub, use this site to understand and preview them, and use Codex or Claude to propagate approved changes.