Create a styling guide

[KosmosisDire]

Create a short styling guide for people wanting to style the toggle, sidebars, or outline. This would include a breakdown of the different classes and variables that can be modified.

This probably won't be created until I settle on a stable setup for all the html and styles.

[HighPriest]

I propose adding to this goal, a reduction of reliance on classes and overall doc content reduction and cleanup.
Why does it have to look like this?

Why is there both a ton of classes mixed with inline CSS?
Why make collapsible content with a ton of JS and classes, when it can all be done with checkbox and a few lines of CSS?

I get similiar functionality with this and some well organised CSS.

[KosmosisDire]

Hi, Thank you!

I am actually not in control of the document's html much at all, I am exporting it exactly as it is from obsidian with very minimal modification. That way it will look exactly like it does in obsidian. As far as the custom content outside of the document like the table of contents, file explorer, etc: Although I do have full control over them they are modeled after the way the same components are created in obsidian. That said, this is my first ever major project created with html, js, and css so I am sure there is stuff I DO have control over that is much less than optimal.

So, if you have suggestions for ways to simplify the html I would love to hear it! Just keep in mind that all of this html is procedurally generated, not written by hand, and the exported html needs to look and function exactly as it does in obsidian. No exceptions. Thanks again for this feedback, I would love to cleanup and reduce any unneccecary complexity.