An experiment using Eleventy to publish a static site from Logseq JSON export.
Assuming you have Git, Node.js, Logseq with a graph to export:
- clone / fork this repo
npm install- In Logseq, Export Graph > Export as JSON to somewhere Eleventy can see
- define
GRAPH_NAMEandEXPORT_DIRin a project.envfile npm start- marvel at how little it does
npm build builds a site, but there isn't much there yet.
Since this is an exploratory experiment, the goals are not concrete yet. It's just me wondering how much work it would take to publish my public Logseq graph with Eleventy.
I'm keeping it my version of simple for now, preferring JavaScript, Sass, and Nunjucks building static HTML and CSS over say for example TypeScript, Tailwind, and WebC building dynamic islands of interactivity. Or something. Maybe later.
EXPORT_DIR
: Where Eleventy should expect to see exported graphs
GRAPH_NAME
: the name of your graph; you may need to slugify to match whatever Logseq uses
So if I have a Logseq graph named "my-logseq-brain" in ~/graphs, Logseq names the export something like this:
home_random_graphs_my-logseq-brain_1681759631.json
And my Eleventy project's .env will look something like this:
EXPORT_DIR = "/home/random/Documents/logseq-export"
GRAPH_NAME = "my-logseq-brain"Currently uses a JSON export file and nothing else. I'm still deciding how I want to handle assets. A good first step would just be to copy them over, but that makes a window of opportunity to view sensitive assets if you know what you're looking for.
That's another thing. Since it's a raw export of all notes, you probably don't want to put your export file in the repo.
The current flow focuses on public content: pages and blocks with public:: true. Everything is private by default, but it's a toggle that can be flipped.
If you have a page you'd like to share, mark that page as public.
If you have a block in your journal you'd like to share, mark that block as public. Eleventy will produce a page for that journal entry containing only the public block. Currently only works for top-level blocks, as I wasn't in the mood to do recursive processing of branches.
If you have a note in your public page that's just for you, mark that block with public:: false. Eleventy will not render its content or children. This does work anywhere, because it's checked when rendering any given block.
- Many ideas grabbed from Rickard Natt och Dag's devlog
I'm making the work in this experiment available to the public via the Unlicense. You are free to do whatever you like with the code, templates, and content. That comes with the standard NO WARRANTY disclaimers. See LICENSE.txt for the text.