You are absolutely right. I was too quick to reply there. Sorry @Cajun. In my hopes to point you to where you may find the theme’s css to have a place to start, I was too rushed. And no, @Klaas, you don’t sound pedantic at all. You raised a very legitimate concern.
However, it is still reasonable to proceed with tweaking the css file directly, as long as you take some precautions:
- Write down the name of the template you chose (to make sure you don’t forget it while doing the following steps).
- Change the file name of the original template’s css to a new, custom name.
- Re-install the original template’s css file back into the templates folder.
- Select your new custom-named template from Obsidian’s options window.
- Note: The list of templates in Obsidian’s options window automatically updates to include the newly named template.
- Feel free to make changes to your custom-named css file, while also having the original css file as reference.
CSS Snippets are another equally valid, if not better, approach. I personally use a mix of directly tweaking a template css file and using CSS snippets. I especially use CSS snippets when I’m introducing new functionality that wasn’t present in the original template.
Also @Klaas, my CSS knowledge is actually not very extensive. I’m a product of the internet haha. I still consider myself a beginner, just one that sometimes puts a decent amount of time into tweaking things. I also make frequent use of Ctrl + Shift + I to open obsidian’s developer tools to see what things can be changed and how.
