EtherPK is a PKMS (Personal Knowledge Management Tool). But more than that, it's pretty close to the best personal knowledge tool I can imagine (and I intend to get better than 'close to' in the coming months - I hope to make it the best personal knowledge management tool I can imagine). Obviously what counts as 'best' here, aligns with my personal preferences, and I am aware that PKMS tools evoke strong opinions about what the best way to do things is.
EtherPK is a markdown based editor. Two of the most important features of EtherPK (and to be honest, the main drivers for me building it) are robust nested wikilinking (e.g. [[[[Nested]] Wikilinking]] ), and the ability to easily switch between standard prose (paragraphs and headings) like Obsidian and outliner blocks like Logseq or Roam Research. Given the choice of one or the other, I've preferred outliner blocks - this format lends it's self the ability to quickly capture and link ideas really well, and build a true 'Knowledge Graph'. But this isn't what I want all the time - if I'm writing for an audience (e.g. technical documentation or a blog post - EtherPK does static site publishing too), I want standard markdown - headings, paragraphs. EtherPK can have both in the same document, and while not as robust for linking concepts as blocks, EtherPK infers links between ideas from heading levels (H1, H2, H3 etc) in standard prose.
EtherPK is a PKMS (Personal Knowledge Management Tool). But more than that, it's pretty close to the best personal knowledge tool I can imagine (and I intend to get better than 'close to' in the coming months - I hope to make it the best personal knowledge management tool I can imagine). Obviously what counts as 'best' here, aligns with my personal preferences, and I am aware that PKMS tools evoke strong opinions about what the best way to do things is.
EtherPK is a markdown based editor. Two of the most important features of EtherPK (and to be honest, the main drivers for me building it) are robust nested wikilinking (e.g. [[[[Nested]] Wikilinking]] ), and the ability to easily switch between standard prose (paragraphs and headings) like Obsidian and outliner blocks like Logseq or Roam Research. Given the choice of one or the other, I've preferred outliner blocks - this format lends it's self the ability to quickly capture and link ideas really well, and build a true 'Knowledge Graph'. But this isn't what I want all the time - if I'm writing for an audience (e.g. technical documentation or a blog post - EtherPK does static site publishing too), I want standard markdown - headings, paragraphs. EtherPK can have both in the same document, and while not as robust for linking concepts as blocks, EtherPK infers links between ideas from heading levels (H1, H2, H3 etc) in standard prose.
...
EtherPK servers and data reside in the EU.
Full introduction:
https://blog.etherpk.com/introducing-etherpk
Please feel free to get in touch with any questions or feedback at mail@appsoftware.com