I just figured out that my new #LogSeq powered site is just one big index file, and that it’s 18MB.
LOL, no wonder it is slow to load!
And: this is just like #TiddlyWiki in default mode, but TW has static publishing built in.
I guess the personal site #yakshaving continues!
@boris publish is being looked into with some exiting features coming up. Nor sure when but it is in the roadmap
Not sure of what you mean, but even though it currently has rough edges, Logseq publishing feature is meant to ship the whole Logseq that runs entirely in the browser: it loads a DB, read data from it and update the content of the page accordingly. This enables feature like search and queries being evaluated live.
If you are looking for exporting content as many HTML pages and a bit of JavaScript, that would be a totally different thing, perhaps desirable for some use cases, but it would be a huge effort.
At the moment there are plugins to export content to other platforms like Hugo, maybe this approach could be gradually improved by supporting more and more Logseq features and plugins without Logseq core.
@post @ednico yes exactly. The needs for static publishing are different than “non editable LogSeq in the browser”.
And of course, for my own graph, an 18MB index file makes it unusable as a website.
Not such a huge effort — LogSeq already exports nice structured data in JSON that could easily be parsed for other systems.
The Schrödinger plugin is fine, just adds one more system. It’s next on my list to explore.