- Why
- Maintaining a public slipbox as a way to have rougher / quicker notes easily accessible, particularly for myself.
- Logseq is mostly very convenient, just not perfectly stable and occasionally annoying. There's also a lot of programmatically generated information I care about
- eg. what notes did I touch this week
- activity log (like github)
- really old notes
- better outlines / structures for hierarchical notes
- Full(-ish) control over rendering, by using org-html-export + python; orgparse should also be useful.
- Next steps – implementation
copy over files into a staging area without manipulating them first
sort without considering capitalization
Make internal links work properly with the custom backend
Add a default title when there's no explicit one
- add last changed date to the posts using git
add support for visualizing length of note contents to index
Add support for backlinks inside posts
Add support for "collection" links
- Add support for private files
- Skip publishing them publicly?
- Alternatively, make them link into the generated github code
- Make the index smarter
Show recent edits
- Add visualization for length
- Open source the code for generation along with the action
Write up a blog post announcing publishing my slipbox
- Potentially publish the action to market place for others to use easily
- (Low pri, probably not worth the effort)
- Allow customizing the CSS, generated index, etc.
- Announce it somewhere on logseq
- Add a Github action to Tweet every sunday with a summary of updates over the past week
- Handle images correctly
- Next steps – continue consolidating notes
- Set up better hierarchies / eg. "Books" prefix
- Migrate How Tos
- Migrate notion documents
- Migrate google documents
Migrate old collections
- Migrate book notes