Invert concept of nesting divs

[Brixy]

Hi all,

This is not a proposal, but rather a suggestion or question.

Nesting divs (and later maybe arbitrary html tags) using different numbers of colons is already possible.

I have the gut feeling that inverting this makes more sense, e.g.

:::
content

::::
content
::::

:::::
content
:::::
::::
:::

Some reasons come to my mind:

1. It has the same feeling as indenting other elements like

* Item

	* Nested item

or asciidoctor.

* Item
** Nested Item

2. It relates to headings with more #s having a lower priority.

# Heading level 1

## Heading level 2

### Heading level 3

3. It’s easier to write when you don’t know man many nesting levels will be required. You just always start with :::.

4. Using sidemarks would have the same logic as lists.

: Item

:: Nested item

::: Nested at a third level

Hope this makes sense.

---

Thanks again for djot. I have written an SSG (deno, vento, djot) which is used professionally although not yet being public. We could drop

markdown-it
markdown-it-anchor
markdown-it-attrs
markdown-it-deflist
markdown-it-footnote
markdown-it-…

Only problem is that definition lists don’t allow multiple descriptions for a single term (and vice versa). But this has been discussed intensively here.

[jgm]

Those are all great points. I think the main arguments for the current system (longer fences on outer divs, shorter on inner) is consistency with the rules for fenced code (which must end with a fence as long as the starting fence; hence, you need bigger fences to include code with a string of backticks on a line by itself). But that argument might be outweighed by the considerations above.