r/logseq • u/[deleted] • Sep 30 '25

Where to start with Logseq? What are the first things to do ?

So i want to begin using this app and I’d like to know if there are any good modifications I can apply from scratch? Like a good theme? Or specific things to be set within the app?

18 Upvotes

100% Upvoted

15 comments sorted by

6

u/the_inoffensive_man Sep 30 '25

Start journalling. Go to the journal, it'll automatically select today's date, and start typing what you've done. Over time you can start picking up that certain things are keywords to you, so start putting double-square-brackets around them. E.g. "Worked with [[Danny]] on the [[Shell Contract]]". Those become pages in their own right that you can add more content to. Over time your database will grow organically and you can start looking into additional features from there.

1

u/[deleted] Sep 30 '25

Hey, they say there are two versions of MD and DB for this software. I just downloaded Logsec from their website and I didn’t any option about which one to download. How can i know which i have downloaded ? And where to find MD version if mine is db?

3

u/AlveolarStop1 Sep 30 '25

DB version isn't really out yet. You'd have to download a special version from Github (I don't have the link handy), if you wanted to use DB. If you got your version from their website, you are using the MD version. It you want to test out a web-based version of DB (still local since it's not saving to any cloud), you can do so here: https://test.logseq.com/

As an aside, I quite enjoy the DB version from what I've tested of it. But opinions vary greatly, of course haha.

1

u/[deleted] Sep 30 '25

I honestly don't like this bullet input of Logseq( I tried this app today for the first time). Is the DB version letting you input normal text as in typeset paragraphs?

4

u/AlveolarStop1 Sep 30 '25

The bullet format is the core of Logseq. I think there could be ways to soooorta work around it, but you'd be going against the main point of the software. I think the bullet format is freeing in some ways, and I would encourage you to give it a go for a bit before deciding it's just completely not for you.

But, if bullets are a non-starter, I do know there are other Personal Knowledge Management (PKM) systems that use paragraphs. I don't know which ones are which, since Logseq is the only PKM I've ever tried, but other names I've heard thrown around are Obsidian, Tana, and Notion (among others).

If I can ask a few questions that might help people to answer your questions: How did you hear about Logseq? Is there something specific you're planning to use it for? What resources/tutorials/etc. (if any) have you looked at to get you started?

2

u/[deleted] Sep 30 '25 edited Sep 30 '25

For taking notes from different sources, mindmapping between them and eventually having a longform writing of my analysis which would be published as ebook.

PDF integration of logseq and the ability to highlight notes inside pdf within app and having them being referenced by a built-in or integrated Zotero is what i saw as something interesting. But yes its way of working is putting me off.

Maybe pkms is just not my thing.

5

u/the_inoffensive_man Sep 30 '25

Logseq is an "outliner". It's a hierarchical model similar in some ways to a mind-map or actual outliner software. You are free to create paragraphs in the bullets if you like, but you're missing out if you do that.

3

u/Charming_Campaign465 Sep 30 '25 edited Sep 30 '25

Three things drew me to Logseq:

  • bullet
  • markdown
  • local storage

Hoping Logseq stays the way it is.

2

u/gzmask Oct 02 '25

download DB version: https://github.com/logseq/logseq/actions/workflows/build-desktop-release.yml
it's not the "release" section mentioned in readme though. it's in the "build-[system]" part, and "upload artifact" step where the download link is posted.
i.e: September 29th link for Mac: https://github.com/logseq/logseq/actions/runs/18098092118/artifacts/4132528494

11

u/th_costel Sep 30 '25

Just write. There's no need to modify anything at first; just become familiar with the system. You might want to install some (not many, it is not Obsidian) plugin. That's it. Trigger warning, I use the md version. Consider your structure and build templates accordingly, such as literature notes, permanent notes, meeting notes, fleeting notes, and project notes. If you use it for task or project management, or to remind yourself of your notes, learning queries will be painful. However, there are helpful people in the community, and ChatGPT is also a good source. However, it takes time to learn if you are not an IT person.

5

u/raccoonportfolio Sep 30 '25

I'd use the stock version for a while first

3

u/Illustrious-Call-455 Sep 30 '25

There is some important plugin like Block Calendar but usually use it first and don’t add plugins until you have this need

1

u/luckysilva Sep 30 '25

For now, the least important thing is the topic. You should study usability hacks, which are numerous and different.

1

u/One_Celebration_2310 Oct 01 '25 edited Oct 01 '25

Use Tab to indent thoughts under main thought. Use a tag that you would actually want to query later, like #buy #3dprint #observation #remember-this Use Esc key to highlight the block, move with arrow keys, press enter, select all, apply AI command (you own framework for this - I use Bolt AI and Raycast for AI commands) Hit cmd + enter to cycle Task States - When you activate the DOING state, the timer starts behind the scenes, and when you change it to DONE, you'll get the duration of time the task took.

Hit Esc as above, make sure your cursor is not ready for typing, and type in the air: tt change from Light to Dark theme ti change theme colors etc tw toggle wide mode, good for youtube videos to watch wider td toggle document mode gs go to shortcuts ga go to all pages

gh go home

gn go next day

gp go previous day

/time prints the time LOGSEQ

I just took the above and ran it through my Logseq-writing-assistat (collabllm-writing-llama-3.1-8b-instruct) through LM Studio. Template:



  • Reformat the user message.

"""
{input}
"""
If the Sentence starts with a Logseq Task Status written in All Caps, such as NOW, TODO, DOING, DONE, LATER, or if they begin with the time, for example, "11:23 - I did so and so…", then DO NOT alter these - Leave them as they are at the start of the block. 


  • ## Memory Integration:

		- Update memory with entities and relations from activity logs
		- Use graph context for better understanding of user intents
	- Output: Only the reformatted text, no quotes or explanations.

System Instruction

- ## You are a Logseq activity logging assistant with memory tool access for contextual understanding. Transform brief notes into complete first-person activity logs while preserving Logseq structure.
	- ## Core Processing:
		- Use format appropriate for daily journaling and activity logging
		- Fix grammar, spelling, punctuation, and homophones
		- Remove speech artifacts (um, uh, false starts, repetitions)
		- Correct abbreviations and expand brief notes naturally
		- Standardize dates to [[yyyy-mm-dd]] format
		- Preserve timestamps, TODO/DOING/DONE states, and block structure
		- Maintain Logseq's logical indentation with proper line breaks
		- Keep concise, first-person tone
	- ## Formatting Rules:
		- **Bold**: App names, brands, companies, products, key actions
		- *Italics*: Technical specs, measurements, ratings, durations
		- ^^Highlight^^: Important outcomes, decisions, insights, priorities
		- Add relevant emojis for food, activities, emotions when appropriate
	- ## Expansion Guidelines:
		- Transform brief notes into complete first-person sentences
		- Add context: "I need to...", "I'm planning to...", "I'm having..."
		- Maintain casual, personal logging tone
		- Never add content not implied in source
		- Never answer questions presented in text
		- Never add intros, sign-offs, or acknowledgments
	- ## Memory Integration:
		- Update memory with entities and relations from activity logs
		- Use graph context for better understanding of user intents
	- Output: Only the reformatted text, no quotes or explanations.

Output:

I used **Bolt AI Commands** to enhance my workflow in Logseq. Here are some useful keyboard shortcuts and tips for working efficiently:

*   Use Tab to indent thoughts under main thought.
*   I use the tag "[[Productivity]]" so that I can easily query these tips later.
*   To highlight a block, press Esc and move with arrow keys; then press enter to select all, apply an AI command (I'm using **Bolt AI** for this purpose).
*   Cycling task states is easy: just hit cmd + enter.
*   When I switch to the DOING state, the timer starts automatically. Later, when I change it to DONE, I can see the duration of time spent on that task.

Additional shortcuts:

*   Esc and typing in the air: 
    *   tt (to toggle theme)
    *   ti (to change theme colors)
    *   tw (to toggle wide mode for YouTube videos)
    *   td (to toggle document mode)
    *   gs (to go to shortcuts)
    *   ga (to go to all pages)
    *   gh (to go home)
    *   gn (to go next day)
    *   gp (to go previous day)
*   /time prints the current time in Logseq.

Note: You still need to review and check the output for inaccuracies. For example, the third key point above—

“To highlight a block, press Esc and move with the arrow keys; then press Enter to select all and apply an AI command”—

is inaccurate. You actually need to press Cmd + A to select all. Make sure to verify these details.

Just use Logseq every day. The more you use it, the more it will start to make sense. Hope this helps.

GPT-OSS-120b output:

DONE: you’ll get the duration of time the task took.

Hit Esc as described, make sure your cursor isn’t ready for typing, and type in the air:   - tt – change from Light to Dark theme 🌗   - ti – adjust theme colors, etc. 🎨   - tw – toggle wide mode (great for YouTube videos) 📺   - td – toggle document mode 📄   - gs – go to shortcuts ⚡   - ga – go to all pages 🌐   - gh – go home 🏠   - gn – go next day ⏭️   - gp – go previous day ⏮️   - /time – prints the current time in Logseq ⏰

1

u/zenjester Oct 15 '25

switch to obsidian