[Andy Matuschak's notes](https://notes.andymatuschak.org) will serve as a pretty big inspiration for these. One key difference is brevity.

I'd like to display my notes in more of a "card" format than something that better serves long-form writing. I'm just not good at long-form writing.

I'll probably use [Next.js](https://nextjs.org/) because, as much as I'd like to build my own slim thing - Next is really, really good.


Notes will be markdown, I'll probably use [Marked](https://marked.js.org/) (EDIT: I went with [react-markdown](https://github.com/vercel/next.js/discussions/17088))

Looking around for info on `[[]]`, it looks like this is commonly referred to as "Wiki links" and there are some [nice tools](https://github.com/kortina/vscode-markdown-notes) for using them in VSCode.

Don't know how long I'll be writing notes in VSCode though, so I'll sort of ignore for now. I just wanna see how easily I can parse them.

Some collected notes on progess:

- [Node.js fs promises](/20201017101755)
- [44 minutes in](/20201017104422)
- [Displaying the notes](/20201017122540)
- [Hello, next!](/20201017125622)
- [Links out, links in](/20201017131023)


Building jot

Linking out and in was trivial :) For now I'll display em after the post contents. When I get serious about [Displaying the notes](/20201017122540) I'll figure out how to make cards pretty.

[next/link](https://nextjs.org/docs/api-reference/next/link) is really easy to use. Just `<Link href="...">...</Link>` and you've got client-side routing for free. Continually impressed with Next.

I'd like to deploy to see if it's really that fast. Each time a post is rendered I _might_ be regenerating the database (reading from the filesystem...). Anyway let's see how it holds up.
