The Enchiridion is a fascinating book, an easy read filled with valuable insights. Unfortunately—even with multiple public domain translations—reading it can often be a bad experience.
Between old and sometimes confusing terms, hard to find and even harder to download files, and outdated websites, the barriers between an interested reader and this content are monumental. So, why not make a website that solves these problems?
- I focused my efforts on design. While the content is the reason I built this site, it's user experience that solves the problems listed above. The way we allow you to interact with the Enchiridion is why this is the best way to read it.
- Even though some translations aren't the best for everyone, they might be my favorites, so instead of pushing for one or another, I made it easy to read the one that works for you.
- Books are hard to share, and with multiple file types that work for different devices with different applications, a project like this can grow out of control fast. That's why I took a step back and decided to serve the content from each translation in a way that's easy to read and share; nothing more, nothing less.
Becoming glazingly fast
Dealing manually with the hundreds of markdown files was out of the table as soon as I defined the project’s scope, but if I’m not cropping, formatting, and naming every file, how would they be ready for the app? Enter automation, it’s no secret developers love to automate mundane tasks so I felt this was the perfect opportunity to scratch an itch I had for months and learn a Blazingly fast™ general-purpose language. Of all of the options, one stood out as an easy yet powerful contestant: Golang has an easy typescript-like syntax and would chew through my use case as if it was nothing.
With a poorly written first Go script, the Twitter thread that documents this project’s creation was born, and another one followed suit as I needed to bulk edit the files once more during the process. While using a new language was unnecessary and all the tasks could be done with Typescript, the feeling of learning something from scratch to solve problems is unmatched and honestly, a lot of fun!
13200 dom elements in a page,
straight 100s in Lighthouse,
build times on vercel?
- Epictetus Version from el.wikisource.org
- Elizabeth Carter Translation from mit.edu
- George Long Translation from wikisource.org
- P.E. Matheson Translation from letsreadgreek.com
- Stephen Walton Translation from ideonautics.net
- T.W. Higginson Translation from tufts.edu
- T.W. Rolleston Translation from letsreadgreek.com
- William Abbott Oldfather Translation from en.wikisource.org
I took eight markdown files from Tasuki's website, then updated their metadata and divided them into 424 files for the individual chapters. My versions of the files are available on Github.
Type of work
- FrontEnd Developer,
- UX/UI Designer