Due to issues with export etc, I started exploring other ways to have a permanent silo of my notes while still harnessing the wonderful features that Remnote offers.
I have also moved on from my earlier zettlekasten workflow with Diigo.
My current workflow is this:
- Select content I like from webpages and get the markdown for that using extension like MarkDownload or Obsidian Clipper.
- Create a zettlekasten note in an Obsidian vault. Paste the markdown there with the source url.
- Create a link to this zettlekasten to other parent note.
- Inspired by Remnote’s content descriptor framework, I rewrite the content where possible into many short paragraphs with a small question preceding it (that will in course become Remnote’s frontend card).
- When I’m ready to transfer the content to Remnote, I replace, (either through a script or through a word processor) the question marks after each heading with question mark and double colon.
I also remove any preceding hash symbols from headings. - I import this into remnote.
- I now just have manually indent where needed. Also put code into codeblocks as that doesn’t seem to happen automatically in remnote (whether import from a markdown or from jupyter notebook).
- I further personalize the content in Remnote with Remnote specific features like image occlusion or portals. (As of now, it is concerning that I am unable to export backup with these changes, but it gives me peace of mind that my main raw content is siloed elsewhere locally until the issues with Remnote export are ironed out.)
- I continue to use my earlier workflow of voice dictation and pencil writing in iPad to make any changes.
- I then proceed to use the spaced repetition tool on these zettlekasten rems.
I eagerly invite comments, feeback or recommendations for my nascent evolving workflow.
What I’d like in the future is to have a IFFT-esque way of automatically updating my local markdown silo with any content changes in corresponding Remnote Rems, and possibly vice versa.
I’d also like to directly import from my jupyter notebooks (as Markdown) which currently has unresolved issues with fenced code blocks not being created.