Composer
Composer is the editor for one post or page. Use Content to find and manage collections of saved entries, drafts, moderation submissions, and Trash.
Write and preview
The Write tab contains the title and Markdown source. The local toolbar can insert common Markdown, links, emoji, and images without changing the stored source format. Preview renders the current unsaved text through the same Markdown and sanitization rules used for published content.
Use an internal link when the destination is existing tinymash content. Use an external link for another site. Links opened in a new tab receive the required safety attributes when rendered.
Composer modes
All modes edit the same entry:
- Simple keeps the title, writing surface, photos, preview, destination summary, Save draft, and Publish or Update action.
- Focused adds the normal content type, status, and common Options controls.
- Full adds ownership, slug, page ordering, root aggregation, presentation metadata, SEO, and plugin tabs.
Switching modes does not clear fields hidden by the new mode. The site default is copied to a new account; after that, the account’s last selected mode is retained. Composer mode is not stored on the post, page, or author space.
Options
Available controls depend on the content type, role, active plugins, and current mode. Common options include:
- summary
- publish date and time
- tags
- featured image
- page parent and navigation placement
- post listing placement
Full mode also exposes the scope, author owner, slug, page sort order, root-stream aggregation, fallback cover presentation, SEO fields, and plugin-owned authoring controls.
Drafts and autosave
A draft is private and separate from the saved entry. Opening saved content with an active draft normally opens the draft. Use the saved-version action when the draft should be bypassed.
Autosave uses the site setting and any profile override. It does not publish content. Save draft creates or updates the private working copy; deleting a draft does not delete the saved entry.
Revisions
A real change to a saved entry can create a revision snapshot when revision retention is enabled. History appears when snapshots exist. Opening a revision loads it into Composer; saving it makes that version current and creates the normal revision trail.
Unchanged saves and status requests do not create redundant revisions.
Leaving Composer
Use Save, Save and return, Save and new, or Duplicate according to the intended result. Cancel keeps unsaved-change protection in place. Use the Content link to return to collection management.