@tlohde @hamatti @markllobrera I'm heavily using named sections:

`<!--section:name-->` via filter ` | section: name`

The whole website https://blades.ninja is built using this technique, you can see those sections injected inside .md files: https://github.com/anydigital/blades/blob/main/README.md?plain=1

The filter can be installed via https://github.com/anydigital/eleventy-blades plugin like this:

``` eleventyConfig.addPlugin(eleventyBladesPlugin, { filters: ["section"] });
```

Btw, you might want to use it in pair with https://github.com/anydigital/eleventy-blades/blob/main/src/filters/fetch.js 🥷

Blades | Framework-agnostic, class-light CSS utilities

Framework-agnostic, class-light CSS utilities Use with Tailwind, Bootstrap, Pico, Simple, or any other reset/framework.

@anydigital @tlohde @markllobrera This is great, much more robust solution than my demo!

@hamatti @tlohde @markllobrera it’s same idea/thinking tho!

found it really convenient to organize .md content without rewriting it as a Front Matter yaml

as a super-power you can even fetch remote sections from other .md files using `{{ ‘README.md’ | fetch | section(‘NAME’) }}` https://github.com/anydigital/eleventy-blades/blob/main/src/filters/fetch.js

eleventy-blades/src/filters/fetch.js at main · anydigital/eleventy-blades

Ultimate blade kit for 11ty (Build Awesome) 🥷. Contribute to anydigital/eleventy-blades development by creating an account on GitHub.

GitHub