3 ms·

Thanks. Spent half an hour playing around with it, and must admit that it seems magical. Implementation aside, the whole idea of splitting information into min

Thanks. Spent half an hour playing around with it, and must admit that it seems magical. Implementation aside, the whole idea of splitting information into minimal parts _and then displaying your whole route_ on one page is a stroke of genius. The hardest part coming from the outside is grokking where the state (/database) lives: I soon found out that you could save everything in a new .html-file, and also got github sync to work, but I missed the option to use a local node-install. This is something I need to look into before comitting, as much of my workflow is centered around scripts modifying notes.

romwell 5y ago
I started with a single .html file, and then moved to Node.js. You don't need to look much into it, since you can import data from the .html file. The only hiccup I've had so far was that I could reference images in the same folder with an [img[relative-path-to-file.jpg]] syntax from the HTML file, but not from the Node.JS version (you need to "import" images first). Wasn't a big deal for me, since I just had to manually update an image or two. Most of my notes in that wiki were just text.