4 ms·
The details html tag works fine on GitHub; or did you mean you’d like a new syntax that’s more markdownesque? EDIT: Definite +1 for the stable headers id sugge
by mstade 5y ago
The details html tag works fine on GitHub; or did you mean you’d like a new syntax that’s more markdownesque?
EDIT: Definite +1 for the stable headers id suggestion. I implemented something similar in a proof of concept app a while back, but it was a suffix rather than a prefix, in brackets, like so:
# About this project { #about }
It worked really well, and the syntax allowed for additional properties like css like class syntax. Thouh we referred to them as tags because they were used to tag sections, paragraphs etc., so we could do some interesting aggregation later on.
- c-smile 5y agoI would rather define some MD rule for <DL><DT><DD> and ask viewers to use collapsing ### Properties + #### innerHTML Get/set inner HTML content + #### innerText Get/set content as text ### Methods
- mstade 5y agoWe did something similar to this, but used ~ instead, like so: ~ Definition title The definition data should be indented at the same level as the title. This let's you nest definitions also: ~ Like this Here's a nested definition. We also allowed : instead of ~ but most people seemed to prefer the latter. We didn't collapse anything in rendering though, but it's not a bad idea. The resulting markup when rendered to HTML was actual definition lists (<dl>) though, not details, so that'd either have to be done by nesting details or css magic I suppose.