Graph in some more widely consistent format. We could tweak a Markdown processor to handleĮach little variation, but it might be easier by working with an exported copy of the Logseq understands ATX # HEADER syntax, but I’ve found the heading property is a little more flexible when rearranging nodes, increasing or decreasing size appropriate to its new context. Need to keep that in mind when shifting all the way over to my site sources. Images are stored with the vault in the assets/ folder. Probably worth noticing that tags can be nested! Tags can be assigned to a node as properties or as I’ve done here with the conventional hashtag approach. It uses an org-inspired #+BEGIN / #+END syntax for admonitions. Properties can describe tags, heading status, or any arbitrary thing you care to track. Instead, pages and individual nodes (list items) get properties assigned with a property:: value syntax. There’s no frontmatter, YAML or otherwise. The outline structure translates to an unordered list, which can be deeply nested for large pages. I have been using the Markdown format for this graph.Īs the screenshot shows, it’s not quite the Markdown we’re used to. Logseq can store pages in Markdown or org format. The important bit is Logseq directly supports exporting its graph. Not all of it, because there’s work and personal stuff mixed in there with the broad notes. See, my short term goal is publishing some of my pkm graph - what Logseq calls the combined pages, blocks, and metadata - to Random Geekery. And while that’s certainly in the realm of possibility, it’s not strictly necessary. So I was thinking yesterday about parsing Logseq’s Markdown pages. Not for the first time, but I have been more ambitious this time around. The Logseq knowledge management tool has been getting a lot of my attention lately. Keep the outline nodes handy so I can have my tangents and side thoughts, then munge it into a readable post. Won’t make myself go into Document Mode for this one, though. Not a bigĭeal on its own, but it should make publishing the post more interesting. Trying an experiment where I write a post about Logseq in Logseq. Got a comment? A question? More of a comment than a question? Not the biggest graph but still cumbersome to export one by one Posted
0 Comments
Leave a Reply. |