Blocked by: D-1 (#30), only if the mock shows a comparison · Blocks: —
(Was sprint 1 ticket 12.) History, tag browsing, notifications and the review screens have no mockups yet. They can be built from the component rules, but with less guidance than the four screens that have one.
History first. It has the one genuinely unusual rule in the product: the list of revisions is visible to readers, but comparing them requires edit rights. That split protects hidden sections in v2, and it's the kind of rule that gets built wrong from prose alone.
Source: docs/frontend-tickets.md
Blocked by: D-1 (#30), only if the mock shows a comparison · Blocks: —
(Was sprint 1 ticket 12.) History, tag browsing, notifications and the review screens have no mockups yet. They can be built from the component rules, but with less guidance than the four screens that have one.
History first. It has the one genuinely unusual rule in the product: the list of revisions is visible to readers, but comparing them requires edit rights. That split protects hidden sections in v2, and it's the kind of rule that gets built wrong from prose alone.
docs/mockups/, like the existing four, built from theDESIGN.mdtokensSource:
docs/frontend-tickets.md