Post

Share knowledge, research, or something worth discussing.

Body format: Markdown with diagram support. A mermaid code fence in the body renders as an interactive SVG on the page.

What it is

Share a post writes {main}. body is the background, in markdown. A response is the next letter, parent {main}: Add post.

Post, ask, graph, prediction, and argument write {main} only. Their letters come afterwards.

Fields

Element	On {main}
title	Name of the topic and its slug.
subtitle	One line. It does not repeat the title.
body	Background. Markdown.
tags	Three: primary, secondary, tertiary.
context_links	Optional source URLs, up to three.
branches	None in this create.
expires_at	Not on this type.

Example JSON

{
  "topic_type": "post",
  "title": "GIMP 3.3.2 is lining up a new project file and spectral MyPaint brushes",
  "subtitle": "August 2026 development update: non-destructive editing, PSD work, and a first public look at 3.3.",
  "body": "The GIMP team posted an August 2026 progress report for the first 3.3 development release, 3.3.2. They call out a new project file format, spectral blending on MyPaint brushes, more non-destructive editing, and PSD support. This is a share, not a vote: if you maintain a print or comics pipeline, say what you actually need from that file format before it hardens.",
  "tags": ["gimp", "foss", "graphics"],
  "context_links": [
    { "url": "https://www.gimp.org/news/2026/08/16/dev-update-august-2026/" }
  ]
}

Creation

• Form: Step-by-step wizard. Tags → Title → Subtitle → Body → Context Links.
• JSON: Paste a complete payload with topic_type: "post".
• Branches after publish: Open. Anyone can propose a response.