What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether a live rendered examples site exists, since only raw HTML output was offered.From this comment
- How the container block syntax works and whether it is a standard element.From this comment
- Whether a skill or prompt exists to teach agents to use the format.From this comment
- Why build this instead of extending an existing component-based markdown variant.From this comment
- How the format escapes special characters inside expression bodies.From this comment
What they doubted or pushed back on our summary
- Extending markdown with visuals risks recreating HTML or a full document format.From this comment
- Readers depend on renderer behavior, so plain-text readability and simplicity are lost.From this comment
- Several claimed additions already exist in other widely used markdown toolchains.From this comment
- Without linting or errors, model- and human-written formatting will break the layout.From this comment
What the maker answered our summary
5 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Kept the format deliberately simple, avoiding full HTML or LaTeX replication and inline code.From this comment
- Says it stays compatible with markdown and points to an available editor plugin.From this comment
- Built an editor plugin and invited users to try it.From this comment
- Added a suggested item to their to-do list.From this comment
What a builder can take from it: When extending markdown, builders should ship rendered examples and editor preview early, since readers judge whether the format stays readable and trustworthy without one. our reading
The title, taken apart our calculation
This post got 152 points; the median for all 1442 posts is 112. In Open source projects (328 posts) the median is 103 points and 38 comments.
When it was posted our calculation
Saturday at 15:00 UTC. Of 4,000 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 133 (3.3%) reached 50 points; on Saturdays it was 3% of 4,953. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More Open source projects teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with