First Crack Release Notes, October 2019

Again in October, like in September, I spent most of my dev time on an Instapaper-like read later service. I use it every day, and plan to release it sometime soon. I did get a couple things done, though; once again, I did not neglect First Crack entirely.

October Activity #

By “a couple things”, I do mean two: in October, I fixed a reference error that kept the favicon from showing up on all pages, and added a dark mode that uses the neat prefers-color-scheme attribute to detect user preference.

November Plan #

Going forward, I may focus on these areas in October, 2019. I carried most of these over from last month’s update.

Re-Implement "Pretty Print" #

I would still like to re-implement the “pretty print” feature now that First Crack uses a stateful Markdown parser. Low priority, but something I want to get done nonetheless.

Release Markdown Parser #

I still want to release my Markdown parser as its own project. I still have some bugs to work out, though, I want to go public with greater coverage of the spec, and I would like to add the ability to parse multi-line strings and entire files at once.

Publish Implementation of Markdown Spec #

I still want to outline the peculiarities of my implementation of the Markdown spec. This would cover weird edge cases for the most part, but documenting these shortfalls would still have value so that those who use my engine will have some sort of explanation for why their article looks weird, and so that I may one day fix them. I made some progress here this month, but not enough for a finished product.

Improve Documentation #

I did some work on the documentation this month, but as always, I could do more. Again, a few of the ways I think I can improve the README in particular:

  • Performance graphs of First Crack’s back-end performance versus other, similar engines. At less than two seconds to build a website of over one thousand pages, I want to highlight this.
  • Performance graphs of the web pages First Crack builds versus the pages common content management systems build.
  • Screenshots. This site is a live demo of the engine, but I like the idea of having a few pictures in there, too.

As always, I look forward to the work ahead.