You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would you be open to adding a configuration option to allow for offsetting of headings?
For example, adding an offset of 2 would map #-><h3> and ##-><h4> and so on.
Why
Hand-editing Markdown levels is often described as a workaround. However, this workaround fails if the same Markdown file gets included by different templates using different nesting levels for headers.
Related Work
For example, this has been implemented in at least one markdown processor; see BlackFriday (GoLang):
// HTMLRendererParameters is a collection of supplementary parameters tweaking// the behavior of various parts of HTML renderer.typeHTMLRendererParametersstruct {
// ... <content snipped by xpe> ... // Increase heading levels: if the offset is 1, <h1> becomes <h2> etc.// Negative offset is also valid.// Resulting levels are clipped between 1 and 6.HeadingLevelOffsetint
}
The text was updated successfully, but these errors were encountered:
Would you be open to adding a configuration option to allow for offsetting of headings?
For example, adding an offset of
2
would map#
-><h3>
and##
-><h4>
and so on.Why
Hand-editing Markdown levels is often described as a workaround. However, this workaround fails if the same Markdown file gets included by different templates using different nesting levels for headers.
Related Work
For example, this has been implemented in at least one markdown processor; see BlackFriday (GoLang):
The text was updated successfully, but these errors were encountered: