There is no need to go into settings now.

Any css block of code now has extra buttons. Those buttons include using it as your theme, and clearing your theme.

/s/Themes is the place to explore for those. Any text post or comment can be installed as a theme. Well ideally it should have CSS content to be a theme.

I feel that it is worth mentioning how to make sure the 'Make Theme' button appears when making a theme. You have to make a code block with css as the language. That is start your post with three backticks followed by css.

```css

I've tested it and using the closing backticks at the end seems to be optional with the current engine. It still is more proper to close with three backticks. The whole comment needs to be valid CSS or SCSS to function as a theme, so if you want to add commentary just write a comment in CSS.

Themes can include other themes. To do that use C like syntax of #include url, or #include postid, or #include commentid. Also #import does the same thing.

This means to make a theme you don't need to start from scratch. It also means you can make your theme out of several components as comments and then bring it together in a post. Or you can write multiple versions of a theme as comments and then use the post to import the current version comment sort of like a release tag in git.

If you break down your themes like this it means that users can easily build their own themes selecting what they want and don't want.