Logseq Tutorial: 5 Tips to Improve Your Logseq Database

Everybody loves 'tips and tricks'. Look, I can't promise they will be life-changing - but hopefully they'll help to improve your work in Logseq just a little bit
📚 COURSES
───────────────────────────────────────────────────────────
LOGSEQ MASTERY: www.logseqmastery.com
UNLOCK TANA: www.unlocktana.com
LOGSEQ MASTERY + UNLOCK TANA BUNDLE: combiningminds.lemonsqueezy.c...
🔍 RESOURCES
───────────────────────────────────────────────────────────
CUSTOM CSS: www.logseqmastery.com/blog/ad...
JOURNAL PAGE ADVANCED QUERIES: github.com/dario-ds/logseq/bl...
⏱️TIMESTAMPS
───────────────────────────────────────────────────────────
00:00 Introduction
01:14 Using backticks to remove links
01:55 Code mirror
02:54 Page icons
03:52 Advanced queries in the daily journal
06:10 Using VS Code for bulk edits
08:23 Conclusion

[@CurlysCurated]

FYI markdown has a function to ignore rendering symbols, i.e to prevent # from creating a tag. You simply need to add \ in front of the symbol. So, in your example: "to indicate inline code #10" would be typed as "to indicate inline code \#10". The \ will disappear it will read as intended and you won't have the code block around the word in the way that you do when you use a backticks.
The \ can be used to negate all markdown symbols like # _ * etc. But it must go in front a each symbol.
Say for instance you want to render *idea* as is with the asterix both showing. Typed as is this will render idea as italic so to avoid this you would use \. But you must use a backslash for each asterix.
If you only type \*idea* you will get "*idea" and everything after that will now be italic. So you need to type \*idea\* to get "*idea*" to render.

[@CombiningMindsPKM]

Thanks for this write-up 🙏🏼

[@soerenrumpf]

Thank you for the valuable tips - especially the one for the queries in the journal!
Regarding the tag and the hash-sign: If you don't like the text being displayed as inline-code, you can prepend a "\" before the "#", to escaped it and still being rendered as normal text.

[@CombiningMindsPKM]

Oh cool, that's clever! I find the inline code display to be a helpful visual reference though :)

[@RikusLategan]

Here is another for you as well. ||Disclaimer: I was told that nesting page names is not officially supported.|| TODO [[Upgrade [[Computer]]]] creates an interesting emergent useful feature that even beautifies the UI, as long as your OS filesystem isn't a crybaby like ext2

[@MariusZierold]

Your audio setup works perfect for me. Thanks

[@CombiningMindsPKM]

Good to hear :)

[@MrHugomesquita]

Thanks for another great video! Keep it up!

[@tsampa]

The audio is very good. Thank you for your tuts they are invaluable. Cheers.

[@CombiningMindsPKM]

Thanks!

[@chrisvaniersel617]

Great tips! Audio is fine.

[@CarloLobrano]

Your audio looks just fine 👍

[@timbushell8640]

Audio 'looks' shit, sounds fine though. : ))))))

[@petermarin]

Hi man! Love your Logseq content!! Can you make a video on your Hugo pipeline? Super interested about how you streamlined your article publishing

[@CombiningMindsPKM]

Will add it to the "maybe" backlog :)

[@GalinaWalls]

The audio is good!

[@CombiningMindsPKM]

Thanks!

[@user-my6hl7my4z]

Thanks for the tips 🙏 where can I find the code for the Journal Page - definitely want to try that one 😊

[@CombiningMindsPKM]

Pleasure! Silly me... here's the link: github.com/dario-ds/logseq/blob/main/journal-page-advanced-queries

[@user-my6hl7my4z]

All good, thank you 🙏😊

[@daleholden]

HI you mentioned about adding the code for Advanced queries in the daily journal and css code but there are no links ?

[@CombiningMindsPKM]

The perils of uploading a few days after editing... here are the links
- github.com/dario-ds/logseq/blob/main/journal-page-advanced-queries
- www.logseqmastery.com/blog/adding-custom-css-to-logseq

[@davidak_de]

Thanks for the video! The microphone quality itself seem good. No need to buy another one. It sounds like you speak directly into it most of the time, but sometimes not (e.g. at 1:47 you move the hand between mic and mouth?), so it sounds less direct and a bit quieter. Maybe you could position the microphone better, always speak in the mic. direction or do some post-processing like compressor. That might make it 10% better, but it's already good. You could close the eyes to focus on audio when reviewing it. I'm not an audio professional. Maybe check out some tutorials if you want improve audio quality more.

[@CombiningMindsPKM]

Awesome, thanks for the tips 🙏🏻

[@user-ek2cp4uu1m]

Sound is very good - compared to earlier

[@CombiningMindsPKM]

Thanks 🙏🏼

[@AnarchySane]

2:10 with / and command code block much better

[@CombiningMindsPKM]

Ah, much better!

[@MariaRachelPintop]

haha, that 'renew Portuguese passport' reminder totally crushed my theory that you might have some Brazilian roots

[@CombiningMindsPKM]

Close :)

[@voldefox]

When I paste the css to change the tags' appearance, the tags just...disappear

[@CombiningMindsPKM]

There was an issue with one of the versions. Instead of `.tag{ }`, you need to use `a.tag{ }`

[@YisraelDovL]

:( Icon's don't work for me ...

[@CombiningMindsPKM]

Hmmm, not sure what could be wrong... It's best to ask on the forum for technical issues like this.

[@77m3]

the page icon not working :(

[@silky_y]

does not work for me either...😕

[@CombiningMindsPKM]

That's strange - all working fine on my side.

[@agentbabs_yt]

audio is much louder in this video of yours for sure.

[@CombiningMindsPKM]

Thanks 🙏🏻

[@fkxfkx]

Your appearance is vastly improved. Thank you for cleaning yourself up.

[@CombiningMindsPKM]

Wait till you see the new look for Mo-vember 😉