Existing Post Types:

A "post type" is just a template living in templates/html/components/forms/. Every post picks exactly one of them — it's what the Content Template dropdown selects when you edit a Series.

---

: for $forms -> $form {
• <: $form :>
: }

---

Create a new Post Type:

This writes a new template into the forms directory currently in use (<: $forms_dir :>) along with a matching .json sidecar describing any custom fields, so that the data model knows to keep them when a post is saved.

---

Type Name * — letters, numbers, dash and underscore only

Canned Fields

Most post types reuse the same handful of blocks. Tick whichever ones this type needs.
Wrap output in the standard post <div> />
Post title & permalink (post_title.tx) />
Post tag list (post_tags.tx) />
Title input in the editor />
Preview image upload (preview.tx) />
Visibility selector (visibility.tx) />
ACL selector (acls.tx) />
Tag editor (tags.tx) />
Alias URL editor (aliases.tx) />
Attachment uploader (attachments.tx) />

Title placeholder text

Content Body — this is always the last thing in the editor, and is what carries the post body itself.
>Single page (form_common.tx) >Multiple pages, like presentations (form_multi.tx)

Custom Fields

These become extra inputs in the editor, and are available in your display template below as <: $post.your_field_name :>. Uploads aren't supported here — use the Attachment uploader above for those.
An Another Post field depends on a different post type. Pick one stores a single post's ID, chosen from a dropdown in the editor, and hands you the whole post as <: $post.your_field_name_post :>. All of them stores nothing and simply hands you every post of that type as <: $post.your_field_name :> to loop over.

Add Field

Display Template

Kolon markup for how this post type renders when someone looks at it. Use <: $post.yourfield :> for your custom fields, and <: render_it($post.data) | mark_raw :> for the post body.
<: $display :>
Overwrite it if this type already exists? />