I recently discovered the power of custom CSS in Logseq and have found it to be an invaluable addition to my database. The visual changes not only make it more aesthetically pleasing, but also provide subtle cues that encourage interaction with the information in your database.
I've shared my custom CSS here as a quick start reference. To install this CSS, follow these steps:
Copy the code from the GitHub page linked above
Open your 'Settings' menu in Logseq (this can be accessed using the shortcut 't s')
Click the 'Edit custom.css' button
Paste the code into the code editor
Voilà, you're all set!
For those interested in making updates to the CSS, I'll delve into more detail below, as it's useful to understand what you're working with.
The first step is know the type of element you want to modify in Logseq. In this post, we'll examine two simple elements: #tags and [[page references]].
To update the appearance of #tags, use the following:
To update the appearance of [[page references]], use the following:
You can further refine the elements that you want to change by specifying text in the [data-ref] parameter.
If you have a tag, #target, or page reference, [[target]], you would use the following code:
You can also define different positions of target text in the [data-ref] parameter. In the examples below, we will look at some patterns which will work for the word "target":
To target an element that begins with specific characters, use the ^ sign. For example, if the element value is "target", use:
To target an element that ends with specific characters, use the $ sign. For example, if the element value is "target", use:
To target an element that contains a substring of certain characters, use the * sign. For example, if the element value is "target", use:
CSS allows you to alter the visual appearance by modifying different properties, such as colours, spacing and font-size. Some common properties are listed below, but if you're looking for a comprehensive guide, the Mozilla Developer Network (MDN) Web Docs is the place to go.
If you refer to this this handy CSS reference, also from the Mozilla Developer Network, you'll notice that my approach doesn't follow best practices. I've condensed all my CSS parameters onto a single line, rather than using multiple lines. However, I'm satisfied with the outcome for my purposes, and it simplifies editing my work.
Best practice would suggest that instead of this:
I should use this
Visual enhancements to your personal knowledge management tool of choice should not be taken for granted. If it improves your experience, it will likely improve your utilisation of the tool too. Now it's your turn to experiment with custom CSS and unleash your inner artist in your Logseq database. Happy customising!
If you found this post helpful, you might enjoy the full Logseq Mastery course. The course has a wealth of videos, detailed write-ups and diagrams to quickly master Logseq and save you plenty of time and headaches.
Want to browse the course outline first?
Click below to see the user guide for Logseq Mastery and to view the latest updates.