Logseq Tutorial: How To Get Started - Using Paper to Show How Pages, Blocks & Links Work

[@davidak_de]

This is maybe the most helpful video to understand the structure of information in logseq. I learned how to use the tool in other videos, but did not know how to actually start. Thanks a lot!

[@CombiningMindsPKM]

Glad it helped, thanks for the feedback

[@Greb99]

Thank you for the effort with the analogue representation. It helped me to decide that most likely Obsidian is better suited for me than Logseq is, coming from Notion and being unsatisfied with a few issues there.

[@CombiningMindsPKM]

Glad to hear :) One of my best friends also decided on Obsidian and it's a great choice 👍🏻

[@pault.juckniess7265]

This is a very helpful video and is one of the first that people need to view to understand what it going on. Very well done!!!

[@CombiningMindsPKM]

Thanks Paul - I appreciate the feedback.

[@han-pinghuang3653]

Such a amazing explanation of logseq based on so considerate analogue model! Thanks for your work : )

[@CombiningMindsPKM]

My pleasure. I'm glad it was helpful :)

[@cleanclothes]

Dario, thank you so much this. I have been using Logseq for over a year and have benefited greatly from your videos. That said, this one is even more remarkable since seeing the physical representation of multiple pages at the same time and of different colors makes it feel like you see the whole forest. I'm sure this video must have taken ages for you to plan, film, and edit. A grand salute to your contribution! PS: Also, a big fan of your keys to happy life!

[@CombiningMindsPKM]

Thanks for the kind words 🙏🏽 Executing was a lot more difficult than planning for this video, so glad the reception has been positive.

[@johankallum]

Wow, I have just started out and was very intimidated, as you said. Now I got the hang of it and can take my first baby steps. Thanks!😀

[@CombiningMindsPKM]

Glad to hear :)

[@tffsnyder]

That was really cool. I'm gonna save that video in my files so that when I switch from craft to Logseq I can remind myself of the structures.

[@CombiningMindsPKM]

Thanks! Interesting positioning there 😅 ('when' not 'if')

[@gost]

You are a great teacher. My respect.

[@CombiningMindsPKM]

Thanks so much 🙏🏼

[@MelodicMethod]

i didn't notice any quality issues in the video. Thanks for making this.

[@CombiningMindsPKM]

Thanks for the feedback :)

[@evanstewy]

Thank you for making this video. It will be great to share this video with others so they can understand the power of Logseq. I just started using it myself and was blown away that you can drag and drop blocks like that. I've been copying and pasting. Amazing!

[@CombiningMindsPKM]

My pleasure :) Dragging and dropping is a serious win.

[@espaciosafines]

Thank you Dario. This video is superuseful when you have been using logseq for a few days and you start to feel a bit messy.

[@CombiningMindsPKM]

Glad it helped 🙂

[@visog]

Outstanding clarity.💡

[@CombiningMindsPKM]

Thank you!

[@RobertoFelloni]

not only a beautiful guide, clear and simple, but also a long and complex job. Many many thanks.👍

[@CombiningMindsPKM]

Thank you 🙏🏽

[@andrese.4999]

Wow Great Job, I’m a visual person and I am so thankful for this 🤩

[@CombiningMindsPKM]

Glad it was helpful :)

[@connysh2781]

Great idea to explain it this way - thanks so much !

[@CombiningMindsPKM]

Thanks Conny :)

[@shashi_kamal_chakraborty]

Nicely explained! Impressed by your analog approach to make us understand the Logseq workflow. I mean what more can a person do? I understood it. Thank you so much.

[@CombiningMindsPKM]

Thanks for the feedback 🙏🏽

[@ChrisGrenfell-q2o]

Wow - this was a brilliant video. Thanks so much for all your efforts!

[@CombiningMindsPKM]

Thanks for the feedback 🙏🏻 Much appreciated :)

[@tonyatlas5653]

Very useful! Thank you!

[@CombiningMindsPKM]

Glad to hear :)

[@fabriziocolista]

My compliments the idea of analog view of how logseq works is great. With one video I jump in the App and I able to begin using it. Very good and thks.👌

[@CombiningMindsPKM]

Great to hear 🙂 Thanks for the feedback

[@etoilyas]

One of the best videos I have seen on PKM generally and the reason is simple - instead of going the "47 new plugins of this month" you went the "what is the idea/model" way. I use Obsidian, but now I finally get the difference between the two

[@CombiningMindsPKM]

Thanks 🙏🏽

[@couldntbeproved1392]

What would you say is the difference? Would really like to hear that, as I've used Obsidian for a couple of months and don't really see difference apart from little interface details.

[@etoilyas]

@@couldntbeproved1392 well the difference is exactly that - “logging sequence” split into paragraphs that are the minimal entity being managed (with tags, links etc). In Obsidian the minimal entity is a file/note. Obviously, the LogSeq approach can be implemented in Obsidian and vice-versa with plugins and/or programming.

[@couldntbeproved1392]

@@etoilyas Thank you very much. I am currently working on making Logseq my second nature, what you said is helpful.

[@etoilyas]

@@CombiningMindsPKM do you think the explanation I gave in my previous comment is correct? Curious about your opinion on this matter

[@1rkrause]

Dario, I've benefited greatly from all of your videos, so thought it was about time I let you know that. In this case, low-tech meets high-tech and your physical representation of the digital workflow was excellent. Thanks for sharing your Logseq expertise. (NB: You might want to mention in your notes beneath the video that the date under Linked References on the lower right hand yellow page should have been Sep 29, not Sep 28.)

[@CombiningMindsPKM]

Thanks for the kind words, Rick. Ah - sharp eyes, thanks! 🤓 I will add a little note in description...

[@sbuu]

Before watching this video, I was a bit "meh" about using logseq. But you showed it in a very clear and clever way that kind of clicked for me. Thanks! Also I learnt about the Baker-baker paradox and the word "schlep", thanks! 😀

[@CombiningMindsPKM]

Haha, glad to hear you enjoyed it - thanks for the feedback

[@AlessandroScaltritti]

this explanation is awesome! it really clarify what I was just figuring out, thanks ❤

[@CombiningMindsPKM]

Thanks Alessandro 🙂

[@burpsan]

Excellent!

[@CombiningMindsPKM]

Glad you liked it 🙏🏽

[@epictrundling4639]

16:49 KEYS TO A HAPPY LIFE, Linked References, Sep 29th NOT Sep 28th? I'm following along,,, :) Just saw your note... :)

[@mageprometheus]

Great video as always. I wrote a few simple apps in Clojure and studied Datalog and advanced queries to put Logseq through its paces. The way blocks work and the inheritance model is great. A few things that I don't like are the creation of pages from tags and the creation of pages from property values. (both of these should be my choice with [[]]). The accessibility of tools like Dataview, Templater and Excallibrain in Obsidian means I will be running with both of them for now. If I took the best (in my opinion) of all the different apps and created my own version in super fast Rust without needing Electron, it still wouldn't please many people, so it's great we have so much choice. It wouldn't please me either as I'd have to support it!

[@CombiningMindsPKM]

Thanks 🙏🏽 Interesting observation on the creation of pages from property values... now that I'm used to it it doesn't really bother me, but requiring more manual control with [[]] makes a lot of sense (and I do this anyways to ensure future interoperability with Obsidian etc). And yes - building it in Rust would be amazing (from my limited knowledge I've heard that Rust is super fast) but then supporting it would be a nightmare, and you'd have to deal with the ungrateful masses if you open-sourced it 😅

[@kotgc7987]

Nice and very helpful high level overview, to understand the structure and beginning use. 16:47 would it be possible to add a KZbin text over, correcting Sep 28th, 2022 to Sep 29th 2022 please, it's confusing when learning. 23:19 audio fades out, could you add text to the words missed there?

[@CombiningMindsPKM]

😑

[@lazut273]

thanks a lot

[@CombiningMindsPKM]

My pleasure :)

[@enghhb]

is this aftermath of the "hair appointment" todo you had on francesco's channel? cheers, and thx for the videos mate.

[@CombiningMindsPKM]

Haha, not actually - now my appointments are walk-ins at the barber 🙂 Thanks 🙏🏼

[@KS-in3mg]

Dario, how would you approach glossary's? Each glossary entry as a page or block? Is there another way of structuring glossary information instead of having just a single "1 to many" relationship or indexing by alphanumeric? (Glossary Title to Glossary Entry)

[@CombiningMindsPKM]

Hmmm, not 100% sure exactly what you're trying to achieve with your glossary, but I think I would go with a block based approach. i.e. have every word as a separate block. You could also tag blocks in other pages of your database with #glossary, and they would show up in Linked References. Or you could do a combination, e.g. - [[word]] - definition A couple of different ways to approach it :)

[@MuhammadArnaldo]

how do you manage your pages? is it enough just using "all pages" menu? or do you create MOC?

[@CombiningMindsPKM]

I have some MOCs that I then save as favourites. It took some time to figure out what structures I needed, but it works well for me now.

[@losource]

I think the new haircut is a big improvement

[@CombiningMindsPKM]

I agree 😋

[@bobbyjames5260]

No one is here to hear about your personal preferences on hairstyles

[@JohnLunney]

This was a lot of work, but I think will help many people.

[@CombiningMindsPKM]

I hope so :)

[@wilsont1010]

How do you keep photos or images in logseq?

[@CombiningMindsPKM]

I upload them using the '/' command, or just use screenshots.

[@yojham88]

🤔: Plugins can access your graph and your local files, issue network requests. They can also cause data corruption or loss. We're working on proper access rules for your graphs. Meanwhile, make sure you have regular backups of your graphs and only install the plugins when you can read and understand the source code. Do you have videos recommending safe plugins?

[@CombiningMindsPKM]

I don't unfortunately. For the most part I only use plugins that have been recommended in the community. There's also a handful of creators who are well regarded in the Logseq community. Bas (Tools on Tech channel) recently released a video on plugins - might be some info there.

[@yojham88]

@@CombiningMindsPKM thanks for the recommendation ✌🏻

[@nickderrett8293]

Sep 28th, 2022... my daughter's 8th birthday. How could you not make a card for that?? :)

[@CombiningMindsPKM]

whoops - missed the message across the airwaves 😏

[@musham6295]

So we cannot create a folders or books in logseq ?

[@CombiningMindsPKM]

You can create it in your folder hierarchy, but it won't appear in folders in Logseq.

[@Dieterbe]

30:00 why do you say it's bad practice to put a block on the inbox page that links to the happy life article page ? If it's an idea that comes up and needs to be processed further later, that seems fine. I don't see how this is any worse than putting it on a journal and tagging with both inbox and the article

[@CombiningMindsPKM]

I agree that if you're tagging it, it's definitely the equivalent. But from a process perspective, I find consistency in writing in the daily journal is good practice. Things sometimes fall through the cracks (i.e. are not tagged). I always review my journal pages to clean them up, and that means I catch those stray blocks. If, however, I've entered it in another page, that block will remain a stray.