I’m thinking it may be an interesting experiment, particularly using it in combination with the Webmention plugin to get replies/responses for crosslinking with others’ ideas on the web. This could allow one not only to communicate with other their own slip box, but slip boxes to communicate with each other.
I’m curious if anyone has tried building a digital public zettelkasten on WordPress in general or using using the Slippy plugin in particular?
15 thoughts on “”
Chris Aldrich mentioned this note on boffosocko.com.
May be an interesting experiment using in combination with the Webmention plugin to get replies/responses for crosslinking with others’ ideas on the web. This could allow digital slip boxes to “communicate” with each other.
@chrisaldrich I see the synergies of hyperlinking, webmentions and Zettelkasten. It’s too bad that Slippy plugin is so long out of date, although you could probably get by without it.
I’ve often thought that wordpress would make a great personal knowledge management system especially since it is very extensible.
Really cool idea. Too bad plug-in hasn’t been updated in 2 years.
I use pages in WP as a sort-of wiki. It isn’t a slipbox, more like a few indexes, but it could be. Biggest hurdle likely is my hesitance in exposing my personal KM notes to the public.
The set-up I use is just WordPress pages, with a plugin to allow categories and tags for pages (separate from the postings cats and tags). This allows having a separate navigational structure for my wiki.
My pages are enabled for webmention.
I (can) use Micropub to publish pages from my Obsidian notes and from my feedreader. It would be interesting in the context of your question to also have an automated way from WP to my Obsidian notes. Perhaps through RSS would be enough.
you would think WordPress could do this.
I installed slippy on a test blog. As far as a quick look showed it would not be useful for a public slip box. There is no published url that I could easily find. The repeated slips appear in the editor.
Brad mentioned this note on cyberzettel.com.
I’ve been using WP as visible part of my zettel, which I keep in Obsidian. The only inconvenience is that I don’t know how to make visible backlinks on pages that has links to and from.
You can look how it works for yourself. Half of my WP is in Russian the section with books is fully in English. Browse there to see how it all works. Post your thoughts what you think about it.
I know that a few people have been using the Webmention and the Semantic Linkbacks plugins for WordPress together to show the backlinks in the “comments” section of their posts/pages. Perhaps this may work for your purposes?
A recent example I’ve seen someone put together on WordPress that does something similar (though not using Slippy) is https://cyberzettel.com/.
In a similar vein, though not with WordPress, Kevin Marks mocked up a UI for an incoming/outgoing links in the mode of a Memex that also leverages Webmentions for part of the functionality: https://www.kevinmarks.com/memex.html.
Here is a sketch of how I’d approach setting up a zettelkasten in WordPress:
– Use Pages instead of posts so you can have the hierarchical parent/child relationship and use built-in features like the Page list for an index and the Query Loop block.
– Use Taxopress to enable tags on pages, and to make tags hierarchical if you’d like. Also turn on Taxopress’s autotagging.
– Semantic linkbacks / trackbacks / pingbacks for external backlinks
– For internal backlinks: Schedule a recurring job for newly published posts to scan content for links on the same domain, then save post IDs of posts mentioning that post in the mentioned post’s meta. In the post template, loop over the mentions meta and output them.
– Output published date and last modified date for the post.
– In the sidebar for a post, show the parent/child relationship of each card. Output the entire ancestry if possible.
– If using the Gutenberg editor, you can use [[this format]] to manually reference other posts. Built in!
– Modify tag archive pages to be sortable/filterable by various meta parameters.