HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
markdown-it
markdown-it-container
JavaScript2017–2022
markdown-it / markdown-it-container

markdown-it-container

Fenced container plugin for markdown-it markdown parser

3Distinct people
3Mentions
0Explicit recommenders
589GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fenced container plugin for markdown-it markdown parser

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2017-03-17 14:45:43 UTC to 2022-02-22 04:02:48 UTC.

0122017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

3 sources
I've been exclusively using Markdown for all docs for several years which I've found to be the most productive format for writing docs. My preferred setup now being to use VS Code with a browser running a local instance of https://vitepress.vuejs.org which instantly live reloads content on each save and renders our custom server components exactly as it looks when published. Its biggest benefit is its extensibility which lets you embed interactive Vue Components directly in the docs, which we've made liberal usage of in our latest product release with tabbed components & online project creator embedded directly in the release notes, e.g: https://docs.servicestack.net/releases/v6#todos-mvc A lighter weight extensibility option is to extend it [1] with custom block-level custom containers using markdown-it-container [2] which lets you creat
Read the rest
e custom markup like this: ::: nuget `<PackageReference Include="ServiceStack.OrmLite.PostgreSQL" Version="6.*" />` ::: ::: sh x mix postgres ::: Which gets rendered into custom copy widgets as seen in: https://docs.servicestack.net/ormlite/installation Source: https://raw.githubusercontent.com/ServiceStack/docs/master/d... Markdown all text things! Basically if it needs to capture text content, I'll look for the Markdown version if it exists, which extends into my preferred TODO App: https://notable.app - a beautiful little App that manages a static directory of *.md files. My first TODOs replacement of using notepad.exe that's stuck. [1] https://vitepress.vuejs.org/guide/markdown.html#advanced-con... [2] https://github.com/markdown-it/markdown-it-container
In Thoughts on Markdown
Look like you are correct. I had thought the `::: section` syntax was a recommended approach (if not yet part of the formal spec). In the past, I have used various home grown solutions to this, but recently I have been using markdown-it and the accompanying plying markdown-it-container. On the CommonMark forums, I see that the ::: syntax is a leading contender, but that CommonMark itself will not address extensions to basic markdown until after the spec reaches 1.0 https://github.com/markdown-it/markdown-it-container
In Netlify CMS – An open-source CMS for Git workflows

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.