IMPORTANT. PLEASE READ THIS LOGSEQ TEAM (pretty please)
I know this has been asked for in many instances, but I believe now might be a better time.
Could the team please invest some time in writing a (at least small) public ROADMAP?
As a user, I have absolutely no idea what to expect from this project. The latest major features that were developed came with absolutely 0 warning or input of any kind from us users: the last one is the MCP server I believe, and before that it was the Logseq CLI, and before that the Vector search capability (Im not complaining about these features though, they are awesome!).
By looking at the commit history daily, I can see that the team is currently working on RTC and the latest new feature they are polishing seems to be an audio recording and transcribing tool for mobile. But again, this last feature is appearing out of thin air, at least from the perspective of the users, with absolutely 0 community feedback or, at the very least, announcement of any sort.
To conclude, what am I ACTUALLY asking for?
Not much. Just a small checkbox list, maybe on the README file on the Github repo so that the team doesnt have to bother doing anything OUTSIDE their development environment. This list would simply include:
what the team is working on
what the team is planning to work on
Features on (2) should only include anything planned for the IMMEDIATE future, so anything that the team knows they are going to work on. For example, the 1st commits referencing the audio transcribing feature appear on Sep 4 ( feat(mobile): audio record && transcribe by xyhp915 · Pull Request #12105 · logseq/logseq · GitHub ). I imagine that the team knew they were going to work on this new feature at least some days (or weeks?) BEFORE the first commits showed up on Github out of the blue. All Im asking for is that the team adds a new entry to the checkbox list whenever they have decided to work on a new feature, then they can tick it off whenever they feel its finished.
Thank you for reading, and I hope Logseq continues to improve as it is doing now
The one feature that I see as a gap for my long-page use cases is proper support for automatic/dynamic Table of Content generation from markdown headers. All KM tools I used before had it and it’s a pain not having it. There was only one addon that could handle internal links in the TOC for long pages and it disappeared from GitHub a year ago. The only remaining plugin in the marketplace only works for short pages, links work as long as the page is shorter than the “lazy loading" threshold.
Hopefully the DB re-design will embed this or handle plugins and/or lazy loading differently so the TOC links will allow jumping to anywhere in the page
Hi! I am very interested in the calendar integration. What is the rough idea? Capture events created in logseq blocks with properties like start and end or even allow online calendars via calDAV or import via ical?
This is the point I struggle with the most: I want everythin in one place and as of now if there is an event I create it in Logseq as a scheduled task and put it in my calendar bc I need reminders and sync, things I don’t get from Logseq… that really is a hustle!
IMPORTANT. PLEASE READ THIS LOGSEQ TEAM (pretty please)
