Files
RenewCMS/docs/design/screens/localization-publishing.md
T

27 lines
1.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Publishing and deletion
Visual reference: `RenewCMS Screens Localization.dc.html`, group "L8 Publishing and deletion".
Read [localization.md](../localization.md) first. Its integration decisions supersede conflicting board annotations. These states describe target behavior, not shipped behavior.
Route: `same as editor`
### Publishing and deletion (group "L8 Publishing and deletion", 10 states)
| # | State | Trigger | Stable ID | Frame selector |
|---|---|---|---|---|
| 1 | Publish French | Confirm, English untouched | `loc.l8.publish` | `pd:publish` |
| 2 | Save and publish French | Unsaved edits: one action saves first, then publishes | `loc.l8.saveAndPublish` | `pd:saveAndPublish` |
| 3 | Save failed, nothing published | Toast; edits kept and retryable | `loc.l8.saveFailPublish` | `pd:saveFailPublish` |
| 4 | Unpublish French | Confirm | `loc.l8.unpublish` | `pd:unpublish` |
| 5 | Delete French version | Confirm | `loc.l8.delete` | `pd:delete` |
| 6 | Delete a source version | Warns about review reference | `loc.l8.deleteSource` | `pd:deleteSource` |
| 7 | Delete last version | Deletes the story | `loc.l8.deleteLast` | `pd:deleteLast` |
| 8 | Delete story blocked | Neutral, no version named | `loc.l8.deleteStory` | `pd:deleteStory` |
| 9 | Published | Toast | `loc.l8.done` | `pd:done` |
| 10 | Publish failed | Toast | `loc.l8.fail` | `pd:fail` |
Exact rendered copy and geometry are in `source/LocaleFrame.dc.html` for the selector above. Use Nuxt UI mappings in `components.md`; the frame markup is a visual reference, not production component code.
The standard captures are 1440×900 and 390×844 in light and dark. The narrow reference state also uses 1024×768. The visual harness must support these sources and sizes before this screen can pass its gate. No visual exceptions or new clock-sensitive skips are approved.