Emanote

Links to this page
  • ๐Ÿ““ Zettelkasten

    For software, see Emanote.

  • Use Neuron, get RSS for free

    On this site, you have three examples: add any of these โ€“ [[Blog]], [[Microblog]], or [[Neuron]] โ€“ to your feed reader, if you want to keep yourself abreast of new content in those zettels. (This website has migrated to Emanote as of June 2021)

  • Philosophy

    Things like tests are not in the template repo, because I personally do not use it in every project created off this repo. Instead, a workflow like โ€œHow to add testsโ€ should be documented (eg.: Adding tests). The same goes for project documentation (which normally would use Emanote).

  • Org Mode

    Although Markdown is good enough for ๐Ÿ““ Zettelkasten, wikis and such (cf. Emanote), for writing outline content Org Mode in Emacs shines the best.

  • Neuron

    Neuron is a note-taking tool written in Haskell and optimized for publishing, based on the ๐Ÿ““ Zettelkasten method. Visit the project website to learn more. Neuron got superceded by Emanote.

  • Haskell

    On GitHub you can find a list of Haskell projects I work on, the notable of which are Neuron, Ema and Emanote.

  • Composability and generic routes in Ema 0.8

    Another key feature of Ema 0.8 is that multiple Ema apps can be combined to produce a new top-level site. Emanote, a note-publishing system, is an Ema app. Say, you want to create a personal website using Ema, but want to delegate publishing of your notes to Emanote. You can combine both your Ema app and the Emanote managed site into a single site, by definining a top-level route like this:

    This release also introduces the Dynamic type to represent type-varying model values. Dynamicโ€™s compose better than LVarโ€™s. The unionmount library, which Emanote uses, has also been updated to be Dynamic-friendly.

  • Announcing Ema - Static Sites in Haskell

    It is worth emphasizing that I designed Ema to facilitate a new model of application development โ€“ one where the data is managed and edited outside of the application itself (such as in text editors, or even a database), but the view of the data is provided by the application. Neuron is a great example of that (and it might well be eventually rewritten on top of Ema; EDIT: indeed it is). Another example is writing a diary / journal view on top of Org Mode daily notes, which is what Iโ€™m exploring in the orgself project that also uses Ema. A third example is to take a OPML file and present a daily-digest view of new content from the RSS feeds; the application would provide only a โ€œviewโ€ into your data, which is a XML file that you may edit however you see fit. I like this model of apps, because the data and the data format remains under my control, all the while yet Iโ€™m not limited when it comes to presentation of that data, and I think the web is a great platform for the later.