Content

The Content section holds what you write: the pages of your space's website, the posts in its feed, and the bodies of the emails it sends. It has three tabs — Pages, Posts and Emails — and opening the section lands you on Pages. Seeing it needs permission to read content.

Pages and posts are different things

They differ in how a reader arrives at them.

A page is addressed by a path and takes its place in the structure of your site — rules, contacts, a schedule, an about page. It has a title, it sits at a URL you choose, and it does not appear in any feed.

A post stands on its own in the space's post listing with a publication date, an author, votes and a comment thread. It has no title field at all: the title, the cover image and the excerpt are read out of the content itself. Posts are the right shape for news and articles, pages for anything permanent.

What is edited elsewhere

Three things look like content and are not managed here:

Contest pages are the same kind of object edited from inside a contest — see Contest pages.
Newsletters, the bulk mail you send to members, live under Members and are not email templates — see Newsletters.
Post types, the categories you file posts under, are defined in Settings — see Post types.

Writing the content

Pages, posts and email bodies are all written in the same two-pane editor: the form on the left, a live preview of the rendered result on the right, and Save pinned to the bottom of the form. On a narrow screen the two swap with Preview and Back.

The content field has a format selector:

Format	Where you can use it
Markdown	Pages and posts.
LaTeX	Pages and posts.
Rich text	Pages only, with a slash menu for headings, lists, tables, callouts, figures, video and embeds.
HTML	Email templates, and any other content that is already stored as HTML.

Switching between Markdown and LaTeX carries the text across unchanged. Switching to or from Rich text converts between the text and a document tree, and formatting the other side cannot express is lost in the crossing — so pick one and stay with it.

What the markup itself can do is documented once, for everyone who writes on the platform: Markdown and LaTeX. The editor links to the same two pages from its toolbar.

Uploading images and files

The file icon in the content field's toolbar uploads a file, and so does dragging one into the editor or pasting it. The file goes to your space's storage and the editor inserts a snippet pointing at it: an image becomes an image, a PDF becomes an embedded document, a source file becomes a fenced code block with the language guessed from its extension, and anything else becomes a link.

Files over 5 MB are uploaded in pieces, so a large image takes a moment. In rich text mode an image is uploaded before it is inserted, so a saved document never points at a file on your own machine. Upload is not offered while editing HTML.

Translations

Pages, posts and email templates all translate the same way. The object holds the original, and each language holds a complete translation of the fields that can be translated. A reader gets the translation for their language, falling back field by field to the original wherever a translation is missing, so nothing is ever shown empty.

Object	Translated	Not translated
Page	Title, content	Path, labels
Post	Content, labels	Type, Feature on home page, Pin on top of list
Email template	Subject, content	Key
Post type	Name, as a list of language and name pairs	—

Every overview screen has a language dropdown listing Original and the translations that exist, with Add translation at the bottom; a language that already has one is not offered again. Whatever the dropdown shows is what the action button then acts on — Edit edits that translation and Delete translation removes only it. Deleting the object itself takes every translation with it.

Because the non-translatable fields belong to the object rather than the translation, changing a post's type while a translation is selected still changes the post.

The language a visitor sees is chosen by the public site from their own language preference. The dropdown in the console only decides what you are editing.