A while ago, I rewrote the sitenav component to *just* use the ReadMore
MDX component to generate the navigation tree.
However, sitenav have certain keys that you can set to control the
visibility of hte item to the user, and those filters were not added
to the ReadMore component, thus showing navigation items that should
have been hidden.
Having build a documentation system at my job as well as the frontend
for it, it was rather surprised that a surprisingly large proportion of
my colleagues complained that the text was 'too narrow'.
When reading documentation, the horizontal space is constrained to limit
the amount of characters on a line. Long lines make for very hard to
read text, because each time your eyes dart back from the end of the
line to the beginning of the next line, it becomes harder to stay
vertically anchored on the correct line.
It's best practice to limit the line length like this, and so I've
always been doing it. However, after someone at work asked, I added a
toggle to allow the text to fill the available space.
Much to my surprise, this was hailed like some sort of significant
improvement. I still don't think it makes sense, but I've added a
similar checkbox to the docs pages of both dev and org sites anyway.
This plugin provides the `ringsector` and `rmringsector` plugins.
The Sandy design was adapted to use the `ringsector` plugin instead of
its own method for doing this (that method was the base for this
plugin).
The plugin is also added to the tabbed-example component.
This closes#3865
This applies a number of changes, typically in how inline MDX components
are handled, including properly naming things (replace pattern when what
we really mean is design) and other tweaks.
