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
This POC currently supports attr-inline however I fear this gives to much power to the end user. We want to be restrictive and ensure the resulting HTML is always uniform. How much should we support?
How do we want to position our docs-builder ?
A pure Myst compatible documentation tool
Myst as baseline with a few directives from sphinx
Myst and subset of Sphinx as baseline with grids from Sphinx-Design ?
I am personally leaning to the latter.
The text was updated successfully, but these errors were encountered:
Our
markitpy-samples
includes several extensions overmyst
itselfsphinx
includes additional directives (see also) [meta] Supported Directives #2Which ones do we port over that are not listed on the meta issue?
sphinx-design
includes its own directives for grids e.g compare:For reference this POC implements the sphinx-design way of doing grids.
This POC currently supports
attr-inline
however I fear this gives to much power to the end user. We want to be restrictive and ensure the resulting HTML is always uniform. How much should we support?How do we want to position our
docs-builder
?Myst
compatible documentation toolMyst
as baseline with a few directives from sphinxMyst
and subset ofSphinx
as baseline with grids fromSphinx-Design
?I am personally leaning to the latter.
The text was updated successfully, but these errors were encountered: