Pradyun Gedam
Pradyun Gedam
Strong +1 for calling it sphinx-components. Meta question: How do we figure out the final decision/concensus here?
I'd start by reserving the PyPI name and RTD name, to avoid any pain around name retention policies.
Given that this package includes the bootstrap CSS by default (which can interfere w/ other Sphinx elements + theme styling for non-bootstrap themes), I'm inclined to suggest that we avoid...
> doesn't a project need to exist already in order to get the name? Yea. "reserving" to me is basically creating a barebones skeleton and upload it as a `0.1.0.dev0`...
Well, what all do we want to provide? Looking at the bootstrap component list, we have: - Alerts (basically admonitions) - Badge (covered by rST's GUI labels + already implemented...
> Well the main issue with bootstrap and sphinx is that pesky `container` class that sphinx adds to all container nodes This specific issue can be worked around with a...
> "role=main" It selects any elements on the page that are like: ``. Within any decent Sphinx theme, that's the element containing the "authored contents" of the page. It's basically...
> what are these out of interest, I don't recall coming across them? I recently came across them on https://sphinx-rtd-theme.readthedocs.io/en/latest/demo/demo.html#inline-markup (see the paragraph starting with "GUI labels"). They're not strictly...
I'll bring in the note from #39 -- regarding changing the "default" style uses when none are specified. :)
What do you want these for?