trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The settings and origins pages' numbered steps draw §5's stack and muted text, and .steps leaves the markup
- The apps and origins pages' filters draw §5's filters, and .filters leaves their markup
- The browse and org pages' filters draw §5's filters, and .filters leaves their markup
- MCP `issue`: a sealed issue the caller may not see is not found, and a pull's number says to use `pull`
- The map's empty state and list sections draw §5's empty and stack, and .map-empty, .map-list leave the markup
- A repository's new issue, make-it-yours, report and toolbar pages name their Server-Timing phases and answer under 50 ms
- An issue, change or comment's origin link draws §5's link and muted text, and .origin-link leaves the markup
- A repository's app, answers, now and state pages name their Server-Timing phases and answer under 50 ms
- The chart frame becomes a §5 component: .chart-box, .chart and .big are named in §5's table and leave §5d
- The map's pillars section draws §5's row and badge, and .map-pillars leaves the markup while its id stays
- .act's rules, which no page draws any more, leave the stylesheet and docs/DESIGN.md §5d
- The map's zoom tools draw §5's bar and btn, and .map-tools, .map-tool leave the markup
- The map's counts line draws §5's badge, .map-counts leaves the markup, and the limbs test reads the count, not the old markup
- /settings/cloud/audit, /organizations/new and /apps/open name their Server-Timing phases and answer under 50 ms
- /verify, /recover and /claim name their Server-Timing phases and answer under 50 ms
- /settings/keys, /settings/tokens and /settings/password name their Server-Timing phases and answer under 50 ms
new above
offline