-
Notifications
You must be signed in to change notification settings - Fork 76
docs: Some restructuring #997
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Apparently it conflicts with `:::{tab}` breaking the new tab to a different set
It is otherwise ambiguous if it applies to the whole section or individual tabs
|
Colon fencing has to have a blank line, like this: Before
:::
Inside
:::
AfterOtherwise the formatter messes it up. If you use tick-marks, then it is ignored by the formatter, some spell checkers, etc (because it's supposed to be code). |
I tried with various degrees of whitespacing until I was able to confirm that my issue was with the colon fencing in 57fcae1. I.e. if you try to add a new |
|
Ahh, the outer blocks need more |
|
This doesn't affect the reworked docs in this PR, right? |
😅 no those are long moved. Well except the |
I have caught an issue with the colon fencing breaking the set, while tick fencing works fine. But the section still feels off because the tabs are too big and specialized, e.g. it is not clear where
warningapplies orWriting metadatasubsection. I think it would flow more clearly if we move it away to a separate document.