@jacobsorme is attempting to deploy a commit to the Docsify Team on Vercel.

A member of the Team first needs to authorize it.

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docsify-preview	Ready	Preview	Comment	Nov 24, 2025 2:22am

Can you all please add an example to the docs? It isn't clear from the update doc what exactly this does. The explanation is too simple.

Sure thing, will look into example + better formulated explanation.

This is the look ATM

In your code file you need to surround the fragment between /// [demo] lines (before and after the fragment). Alternatively you can use ### [demo]. By default, only identifiers are omitted. To omit the entire line containing the identifier in the fragment output, you can add the :omitFragmentLine option.

The use case for me is specifically this - I want to both use a HTML file for a Docsify snippet, and be able to render the file stand-alone. Neither<!-- /// [demo] --> nor /// [demo] solves both these cases, the first gives me a --> in Docsify and the latter a /// [demo] in the stand-alone page.

In your code file you need to surround the fragment between /// [demo] lines (before and after the fragment). Alternatively you can use ### [demo]. By default, only identifiers are omitted. To omit the entire line containing the identifier in the fragment output, you can add the :omitFragmentLine option. This is useful if your code fragment is e.g. HTML and you want to hide the Docsify fragment identifier from your HTML output. With :omitFragmentLine the trailing --> of the comment <!-- /// [demo] --> won't be included in the Docsify fragment.

How about something like that + a short HTML example & Docsify markdown embed line?