And Introduction and History sections #60
Conversation
Avoid each term being a separate ToC entry in the sidebar, and make the whole section more compact.
|
|
||
| ## History | ||
| .. note:: |
There was a problem hiding this comment.
how is this doc built? does the tool support rst syntax in markdown?
There was a problem hiding this comment.
It was meant to, but this is the one thing that didn't work. The doc is built by installing the reqs in requirements.txt and then make html in the spec/ dir.
I bet on recommonmark back when I set this up, and should have gone all-reST or used Myst instead. My plan is to do a wholesale conversion to reST as the last step after all PRs we want to include in the first release are merged. Doing a conversion with a bunch of open PRs is a pain, so I left it till last.
Then this note will look like https://bashtage.github.io/sphinx-material/additional_samples.html?highlight=admonition#admonitions
|
Merging this. Thanks for having a look @szha |
No description provided.