I received a ton of great feedback from visitors about my MailMate love-fest earlier this month. Most people didn’t know the app existed. So, here’s a few more details around how I have my setup configured along with the hidden preferences I’ve enabled.
Here’s my copy of MailMate:
On the left is your typical macOS source list with all of my mailboxes and smart folders. I’ll describe those later. But first, the three-pane main view.
At the top, outlined in red, is the message list. When Gmail came on the scene in 2004 and introduced email threading to the masses, it was a revelation. And I stuck with a threaded inbox view even after I switched my personal email account to Fastmail.
But maybe a year ago? I was digging through my archives trying to find a specific conversation with a customer, and I found it easier to do my research when I reverted back to a standard, chronological list of my messages. After fifteen years of only looking at threaded conversations, this “new” view just sort of…stuck? And it’s been my default MailMate view ever since.
Don’t get me wrong, MailMate has excellent support for organizing by threads. It even offers an amazing feature I’ve never seen in any other email client – showing the total number of messages in a thread and then allowing you to sort by that count. For example, here’s my threaded customer support archives sorted by longest conversation.
The right-most column shows the number of emails in each thread. Apparently one customer and I exchanged 57 replies!
Going back to the first screenshot, the bottom area outlined in green is the currently selected email. Even though MailMate is optimized for sending plain text (and HTML using Markdown) emails, it renders HTML messages just as well as any other client. Unlike most iOS email apps I’ve tried (as well as a good number of macOS apps), I’ve never encountered any significant HTML rendering bugs – even from the most ridiculously formatted mailing lists or advertisements.
As I said above, I prefer a chronological inbox with one email per row. However, I do find it incredibly helpful to see – at a glance – previous correspondence with the sender. All modern email clients offer threads, which is great, but MailMate offers an instant correspondence view (what I call a “history” view) that shows every email you’ve ever exchanged with that person – regardless if it’s part of the current conversation. And that’s the area outlined in blue.
I have a pretty good memory for my customers, but I find it invaluable to instantly see previous conversations I’ve had when someone reports a bug or has a question. The correspondence view also (accidentally) gives me an ad-hoc view into their order history. Because I bcc myself on every order receipt and serial number lookup, when I select their support email, the history view shows an email for every order they’ve placed, etc. It’s a crazy-useful feature.
Next up, the sidebar.
Inboxes are inboxes, so I’ll skip those. But the purple folders are smart mailboxes. And MailMate has by-far the smartest and most powerful search and filtering capabilities of any email client I’ve used. Here are the four main smart folders I’ve added to my top-level view:
Bills
This mailbox simply searches for the word “bill” in the subject or body of the email. I know, that’s a stupid simple rule. But, it works!
Newsletters
I have a secret email address that I only use for subscribing to newsletters and mailing lists that I actually want to read. This smart mailbox filters on that as well as for a number of From: senders that I signed up for long ago before I started using a dedicated newsletter email address.
I really like having all of these emails organized into a single view. I get too many to read everything. But, when I have time, I can quickly dip into the recent stream of updates and then jump back out – almost like a lower priority and less urgent RSS reader.
Notifications
I mentioned above that every email my backend system sends to a customer is automatically BCC‘d to me just so I can keep an eye on things. For branding reasons, many of those emails come from different addresses based on what product they’re concerning or the reason for the email. This mailbox has smart rules defined to collect all of those.
Orders and Receipts
Finally, my Orders mailbox gathers all online orders, receipts, etc. It does this by searching for the keywords “order”, “receipt”, and “invoice”.
Again, it’s a really simple search to setup, but it works wonderfully for my needs.
MailMail Hidden Preferences
The MailMate manual has an entire section on hidden preferences that aren’t exposed through the GUI. Feel free to read through everything that’s available. Some of them are so useful, but also so esoteric, that I keep an updated shell script in Dropbox with all of my customizations that I can re-run if I ever need to setup a new computer.
I keep my Dock resized to be pretty small on screen, and I find the default badge sizes hard to read when I’m leaning back from my screen. Bumping up the font size is a nice touch for my fast-approaching-forty eyes.
Attachments Up Top
I never understood why MailMate defaults to showing an email’s list of attachments at the bottom of the message – offscreen if the message has to scroll. This bool makes them up appear at the top of the message view.
Close Window after Move
Does just what it says. If you’re viewing an email in a separate window, when you file away the message into a folder, MailMate will also close the extra window.
Give Composer Initial Focus
When you set this preference, pressing ⌘N to create a new email will focus the body of the message so you can begin typing right away – as opposed to focusing the To field.
So that’s a bit more about my MailMate setup. There’s a ton of additional tweaks, customizations, and power features you can set to bend the app exactly to your liking.
To my future self ten years from now: this post is for you.
Late last year I shipped the biggest update to my flagship app in its thirteen year history. If you’re not familiar with the app or my tiny software company, don’t worry about it. Those details aren’t important.
In my announcement to my customer mailing list, I promised that more important than the immediately available updates, was that this release laid the groundwork for many more significant future improvements and new features. I even went so far as to make the biggest mistake a developer can make: I promised a ship date for the next round of improvements.
The reason I put that date out there was because I felt guilty. Despite this release being the culmination of nearly a year’s worth of work – and an insane seventy-one hours spent coding during the final four days leading up to the Black Friday launch, I still felt like it wasn’t enough.
So I basically said “Upgrade today, and I’ll deliver even more in forty-five days”.
That deadline came and went in mid-January. Sure, I’ve shipped eight app updates since then, but they’ve all been minor releases. Bug fixes and some nice improvements, plus a bit of polish. But certainly not what I was aiming for.
I’m happy to say, though, that now I’m finally in the home stretch of delivering that first big round of improvements that all of 2019’s foundational changes made possible. It’s not complete yet, but I can see the end goal.
But that’s not the point.
Getting to the Point
The above 250 words were just to provide context for the rest of this post.
Since August 27, 2007, my little app has seen
142 releases
2,200 commits (that I’m aware of)
and the currently shipping version has 54,501 lines of code (according to SLOCCount).
And despite all that work, all of those updates, and all of the bug fixes and new features they contained across thirteen years, there is a single, twelve year-old ticket that I’ve never closed.
Call it a bug. Call it a new feature or an improvement. Whatever. But it relates to a critical piece of my app’s infrastructure that literally allows the app to do its job. (I’m purposely being vague about the technical details because I don’t want them to be the focus of this post.)
My current way of making things work is an incredible hack that relies on a system framework deprecated in OS X 10.8. Over the years, I’ve migrated to slightly different (but not really better) approaches, but they’ve all been stopgaps, half-measures, and so very clearly the wrong way of doing things.
And it’s remained that way because I’ve been afraid.
Obviously the focus of my career has been building for Apple’s platforms, but I’ve worked with so many different tech stacks, languages and frameworks over that time. And for the most part, I’ve been fortunate enough to get up to speed quickly and find success with each.
But always, always in the pit of my stomach, deep down in the back of my lizard brain, there’s this nagging voice when it comes to the low-level work, the real work, the type of code that real developers write
You’re not good enough. You can’t make it work. You’re not smart enough to figure it out.
So I keep punting on the work. I keep pushing that bug fix further and further out and just hope that my code keeps working and that a random macOS point release doesn’t bring it all crashing down.
I’ve made a few false starts at writing the code the correct way. I first learned Objective-C and the Cocoa frameworks from the Hillegass book seventeen years ago.
And then shortly after moving to Cupertino in 2007, I vividly remember browsing the computer books section in the Barnes & Noble on Stevens Creek Blvd and finding this:
I bought it, and took it back to the economy, extended-stay hotel I was living in and spent the evening browsing through every topic.
I don’t know why I was so in awe of the book. It may have simply been that it was titled Advanced Mac OS X Programming. Or maybe just that so much of what it covered was so far above my head at the time.
But then, right there in the middle of that book, was a section on the right way to approach the problem I’m still struggling with in my app today. (Well, what was the right way back then. Things have changed, but the new APIs are in a similar ballpark.)
So it hasn’t been that I’ve been unaware of what to do for the past decade and a half. I’ve mostly known how to go about solving the issue. And as I’ve dug into the sample code I’ve been able to find online over the years, I’ve built a mental model of how all the pieces fit together, but the technical underpinnings still elude me.
And I guess that’s OK. That’s the point of system frameworks and APIs, right? To an extent, they’re made available to paper over the low level details and give developers an easier interface to work with.
But there’s just something about this particular stack and area of the system that has become a permanent roadblock in my head. It’s so far outside of my expertise that my normal willingness to dive in and learn something new takes a back seat and is blocked by fear, worry, guilt, shame, and so many other awful unnamed emotions that whenever I even think about attempting to work on this feature my self-confidence vanishes, I shut down, and turn to adjusting font sizes and margins to distract myself into feeling better.
For me at least, it’s my ultimate expression of imposter syndrome.
And goddamn it sucks.
Light
But.
I have a deadline.
Not just a self-imposed release date, but an actual contractual obligation to get all the work I’ve been focused on since the last big release in November done, tested, and shipped next month.
The third week of May is going to be a huge opportunity to reach a new market and acquire new customers. And I want to put my best foot forward. The app is feature complete as far as the new stuff I want to ship. My focus now and over the next seven to ten days is smoothing out the workflow of the app and just making it better and easier – especially for new customers. It needs to Just Work.
And so two nights ago I sat down in my office. And just fucking did it. I told myself “no” was not an acceptable answer and dove into every arcane, unmaintained bit of Apple documentation I could find. Searched old Cocoa mailing lists for sample code, and finally, finally have a working solution.
For forty-eight hours, I was knee-deep in UNIX sockets and C code, exercising programming muscles that I haven’t flexed since I was an undergrad almost twenty years ago.
What I’ve built is nothing novel. It’s exactly the same solution that every other system-level Mac app or utility is using.
The difference though, is that after thirteen years I finally got past my own shit and mental demons and made it happen. I guess I was just fed up with myself constantly ducking out of doing the hard work. That, plus a looming deadline I have to meet, finally held my feet to the fire on this particular feature in a way that has never been done before.
I reached the light at the end of this particular tunnel. So many features. So many bug fixes. Thousands of customer emails and replies. Brainstorming sessions. UI mockups on the back of napkins at bars or doodling on a notepad while at my real job. But this one damn bug was always out of reach. And now it’s done.
So, to my future self ten years from now and anyone else reading this post, I’ll leave you with this picture.
I don’t know where that picture came from or who originally made it. My former therapist gave it to me six years ago. I printed it out, and it’s been hanging on the wall above my desk ever since. I need to remember to look at it more often.
I keep looking through my archives of old, private coding projects – the ones that I built just for myself to solve a particular need – to see if I can find any that other folks might find useful. So, here’s another one I spent a few hours cleaning up recently.
Fastmail is the greatest email service in the world. (Fight me.) I assume they picked that name at random because it sounded nice and then kind of painted themselves into a corner and were forced to live up to it by making their IMAP backend literally the fastest email service I’ve ever used. If you think IMAP is just a broken and awful protocol (it is), then you’ve probably only ever tried Gmail’s horrible, bastardized implementation in recent years. Fastmail IMAP absolutely sings.
And their web interface (particularly the latest revision) is truly spectacular and also lives up to their name. It’s hands down one of the best non-trivial web apps I’ve ever had the pleasure of using.
So, despite primarily living in MailMate, I did build this simple macOS wrapper around fastmail.com a while back and occasionally do still use it over MailMate.
The app supports
Multiple Fastmail accounts.
Native macOS notifications (and sounds).
Customizable Dock icon badges.
Keyboard shortcuts (⌘1 – ⌘9) to quickly open specific accounts.
Never, ever does anything with your Fastmail credentials. The only network traffic is between the app and the Fastmail website.
It also has the dumbest macOS Preferences window ever for configuring your accounts because I’m too lazy to spend an evening doing it the right way.
I’d post screenshots showing what the app looks like, but I’m not going to because 1) it’s literally just fastmail.com inside a window and 2) I don’t want the internet to see my Inbox.
Instead, here’s the app’s Dock icon showing multiple unread badges.
You can assign each account’s unread count to a specific corner of the Dock icon. If you assign multiple accounts to the same corner, their counts will be summed together and displayed.
Of note: the app monitors your inbox for new messages by injecting JavaScript into the webview. Early on I realized that if you navigate away from certain screens within fastmail.com, the JavaScript will break. (Obviously, because the DOM elements it’s looking for are no longer available.)
To fix this, I did the first and most incredibly hackish thing that came to mind, which is to keep a hidden webview open in the background that the app maintains control over and can parse for new messages.
I would like to fix this by doing smarter DOM scraping, but I don’t think it’s worth the effort because the HTML source can change at anytime.
Rather, if someone would like to tackle this feature for me, it would be amazing if the app just spoofed the website’s JMAP credentials and checked for new email the real way.
Anyway, I hope all you handsome Fastmail customers out there find this little project useful.
If there’s one thing I’m good at, it’s reinventing wheels. So here’s Roland – an open source, blog-aware, static website generator written in Swift that also uses PHP under the hood because PHP is still the best template language.
You’re probably thinking to yourself
Oh, god. Why?
You’re probably also asking
Isn’t “blog-aware, static website generator” literally the purpose of Jekyll?
I’ll answer those questions and many more below. But first, here’s why I moved this blog off WordPress for the first time in thirteen years. (Other than two months last Summer when I experimented with Ghost.)
Why leave WordPress?
First of all, WordPress is great. If you want to build a personal website – or maybe even a company website – just use it. It’s a capable, featureful, well-maintained, open source success story that is stewarded by an amazing team. But I kept running up against two problems.
Control
Performance
I’m an old-school web nerd who likes to maintain complete control over my website – from the design down to the raw HTML. And despite twenty years of experience with PHP, every time I looked under-the-hood to see how WordPress worked or to tinker with a plugin, the coding style and way things were organized gave me hives. (That’s not meant to be real criticism. What Automattic has built is awesome. I’ll certainly never create anything that rivals WordPress.) It’s just to say that years ago I gave up attempting to work within the lower layers of their framework and turned to using plugins for everything.
Of course plugins present their own problems – namely, I’d lose control over the HTML being generated and when and where all the various scripts and static assets were injected. It just made everything a mess. Sure, for a while I used a completely custom template that prevented plugins from doing anything on their own unless I allowed it, but then that defeats the purpose of using plugins at all.
And then the more plugins you install, the slower WordPress becomes – and it’s already not that fast to begin with. For ten years, this blog was hosted on the same VPS as my business website and mostly worked fine. But every now and then I’d get a spike in traffic and the server would fall over. (For reference: a 4GB / 2 CPU VPS with Linode.)
I’d take the necessary precautions like using WP Super Cache, keeping all static assets offsite on a CDN, and an unexpectedly popular blog post would still bring things crashing down. If it were just this dumb blog, I wouldn’t care. But it would also take down my online store with it, which costs me money and annoys my customers.
So a year ago I moved this blog to its own DigitalOcean droplet and even took the time to (finally) setup Varnish in front of it. It’s been great having it isolated from all of my other web properties, but a Hacker News or Daring Fireball link will still cripple it. The only thing that has truly worked for those traffic spikes has been to also put Cloudflare in front. And that’s great, kudos to them for the amazing free service, but that means holy crap I’ve got three caching layers (not counting my CDN) where new posts, edits to existing posts, and template changes can get hung up.
Yes, yes. The droplet this blog is (was) running on was DigitalOcean’s lowest-tier $5/month box, so I’m well aware of what I was paying for. But I’m not willing to pay (a lot) more just to support an occasional burst in traffic – at least not when I think there are other ways to find a solution. There are some wonderful, dedicated WordPress hosts out there that I’ve worked with for client websites in the past. But even with WP Engine, I would have blown past their $115/month plan five months in the last calendar year.
So the idea of moving to a static website that can withstand bursts of traffic has been percolating in the back of my head for a few months now.
I’m perpetually afraid to touch any of the software on my server for fear of breaking Jekyll’s dependencies. I’m sure it was my fault, but at one point I was unable to do a build of my company website after an unattended Ubuntu security update broke something related to Jekyll and Redcarpet and Kramdown. It took me two weeks of off an on tinkering before I could get back to a working state.
Jekyll is written in Ruby, which is so, so far removed from the ecosystems I normally work in that I don’t even know where to start when something goes wrong.
So I crossed Jekyll off my list. The next obvious choice seemed to be Hugo. Everyone who has ever mentioned Hugo to me has raved about how wonderful it is. And my surface-level investigations into the framework seemed to confirm that. But, again, like Ruby, Go is not a native language for me. And switching would also mean having to learn an entirely new template system as well.
And, hey! I know Swift (mostly). That solves concern #3 above. And being a Mac and iOS developer, I feel pretty confident about being able to resolve any build or dependency issues that come up, so that fixes #2 as well. I guess that means I just need to look into how easily I can use Publish to generate the traditional blog-style website I’m going for.
But, first. What is a traditional blog?
For me, that means the type of personal websites (née web logs) that I came of age reading in late high school and early college. A home page with a reverse-chronological list of entries that you can then click through to read the author’s post history. Every post can also appear within dedicated category archives and date-based archives (typically by month).
It’s a simple, classic structure geared towards content that requires more attention than a tweet.
And reading the Publish documentation and examples leads me to think it would be possible to build. But then I got to the section on theming, which uses Plot.
Plot enables you to write HTML using native, fully compiled Swift code, by modeling the HTML5 standard’s various elements as Swift APIs. The result is a very lightweight DSL that lets you build complete web pages in a highly expressive way.
The first example on the Plot project page is:
let html = HTML(
.head(
.title("My website"),
.stylesheet("styles.css")
),
.body(
.div(
.h1("My website"),
.p("Writing HTML in Swift is pretty great!")
)
)
)
Technically impressive? Absolutely. Type-safe? Both intriguing and appealing. But just, no. Gonna nope right out of there.
I love the foolishness, malleability, hackability, and pragmatism of HTML. And hats off to John if he can make a framework like Plot work for him – maybe I’m just not taking enough time to fully understand the benefits – but I ran screaming when I saw that’s how you theme your website in Publish.
Wheel, meet your new inventor
But the idea of using Swift as the engine of the static generator – if not the templating language – really piqued my interest. So, over the course of a long weekend, fueled by a healthy dose of not invented here syndrome, I decided to take a stab at writing my own system. My calculus being
If I can knock this out in a weekend, that will be faster than the time it would otherwise take to learn the ins-and-outs of another framework. And while whatever I come up with is guaranteed to not be as robust or flexible as a Hugo or Jekyll, it is guaranteed to meet my needs without compromising on the design or structure of the website.
But let’s be honest. It also sounds like a whole lot of fun for an old web nerd like myself.
So, that’s why I built Roland. And if you’re reading this post, that means the DNS switch was successful and everything you see was generated by the roland command line tool, dumped into git, and sent to Netlify for static hosting – and sped up by the amazing folks at BunnyCDN.
One command to run against a folder of web assets and build a website – just like Jekyll.
Fast enough to be useable during a typical edit → compile → test workflow session.
Clear separation between the Swift business logic that dictates the site’s structure and the layout of the HTML.
A flexible templating system.
Simple
Unlike Sundell’s Publish project, I didn’t want every website I build with my framework to be tightly coupled with the Swift code that generates the HTML output. His is a unique approach, but not for me. I like the Jekyll method, which is a simple command line tool you pass a folder of source files (Markdown, HTML, images, other static assets) and it outputs your generated web site.
Performance
One of Hugo‘s biggest selling points is how damn fast it can build your website. Their website claims, on average, \< 1ms per generated page. I have no hopes of achieving compilation times like that. Instead, I just want my tool to be performant enough to where I don’t hate my life every time I make a copy change or tweak my website’s theme.
This blog has over 200 posts – written in Markdown. And then when you add in pages for categories, monthly archives, and other static pages, it totals closer to 400 pages that need to be generated along with all of the other static website assets and over a decade’s worth of wp-content uploads. Here’s how a full build works on my laptop:
36 seconds.
Yes, that’s definitely not fast. It’s on the order of 10 pages/second. I know Hugo would be way more performant. I don’t know for sure how it compares to Jekyll, but clickontyler.com – with considerably less pages to build – still takes a full 9 seconds. So I feel like 36 seconds for a website of this size is likely in a similar ballpark.
(Roland was written in a mad dash over three days, so I know there are many places that can be optimized. Again, my initial goal was for it to be useable – optimizations can come later.)
That said, there’s no way in hell I’d wait that long between every build when I’m iterating on basic HTML changes. So, roland has a number of command line options that lets you specify exactly which parts of your website to build or not build.
USAGE: roland [--config ] [--output ] [--posts] [--pages] [--home] [--dates] [--categories] [--rss] [--no-public] [--no-clean]
OPTIONS:
-c, --config The build configuration .plist to use.
If omitted, "config.plist" in the current directory will be used.
-o, --output
The build output directory.
If omitted, "_www" in the current directory will be used.
If the output directory does not exist, it will be created.
--posts Only build posts.
--pages Only build pages.
--home Only build home archives.
--dates Only build date archives.
--categories Only build category archives.
--rss Only build RSS feed.
--no-public Don't copy "_public" directory.
If set, the contents of the "_public" directory will not be copied into the output directory.
--no-clean Don't clean the output directory.
If set, the contents of the outpupt directory will not be deleted prior to building.
-h, --help Show help information.
The content of your website is written in Markdown, while the HTML templates are, uh, HTML.
Static, one-off web pages are placed in the _pages directory. The format of a page looks like:
title: About
path: about/index.html
---
[Tyler Hall](https://twitter.com/tylerhall) is a Mac, iOS, and (former) web developer from Nashville, TN.
After spending three years as an engineer working for Yahoo! in San Francisco, I'm now working on my own apps under my tiny software development company, [Click On Tyler](https://clickontyler.com). We make productivity software for web developers and designers. Our flagship apps, [VirtualHostX](https://clickontyler.com/virtualhostx/), [Hostbuddy](https://clickontyler.com/hostbuddy/), and [Hobo](https://clickontyler.com/hobo/), are loved by over fifty-thousand web developers.
You can stalk me further on [Twitter](https://twitter.com/tylerhall), [GitHub](https://github.com/tylerhall), and [LinkedIn](https://www.linkedin.com/in/tylerhall). Here's a small collection of my [past projects](/portfolio/) - both commercial and open source - as well as [what I'm currently working on]({{site_BaseURL}}now/).
The front matter of the page is loosely based on what Jekyll does. The only required properties are title and path. You can add additional info (one per line) and those key value pairs will be made available to Swift and the template language for you to do something with.
Blog posts are similarly stored in _posts and look like:
title: MailMate
date: 2020-04-06 11:48:18
slug: mailmate
categories: macOS,Reviews,Apps,Favorite Things
---
MailMate is a glorious, configurable, ultimate-nerd-dream of an email client built just for macOS. I use it every day in conjunction with Fastmail and SaneBox to give me email super powers.
But the killer feature? It just fucking works.
And believe me. I've tried every single email client for Mac and iOS – paid apps, free apps, subscription apps, apps from small companies, and apps from giant corporations.
I don't know what else to say except that I love this app so much. And unless I'm horribly mistaken and there is secretly a giant corporation hiding behind MailMate and slurping up all of my private data, MailMate is built by a single developer, which is even more awe inspiring.
---
It took me a few days longer than I had hoped to get started, but here's the first post in a new [Favorite Things](https://tyler.io/category/favorite-things/) category celebrating [#IndieSupportWeeks](https://mobile.twitter.com/search?q=(%23IndieSupportWeeks)). First up, is the incomparable [MailMate](https://freron.com) by [Benny Kjær Nielsen](https://freron.com/about/). It's "the email client for the rest of us".
The front matter requires a title, slug and date. (path is not a thing because it is automatically derived by your blog’s naming structure as you’ll see later.) categories are optional and are a comma delimited list. Category names may contain spaces and other special characters. Only commas are not allowed.
The next section (after the ---) is an optional post excerpt that may be used in your templates. If you don’t want to provide an explicit excerpt, you can leave it blank.
Everything after the second --- is the post’s body written in Markdown according to the CommonMark spec. (HTML is allowed to be interspersed within the Markdown.)
The contents of the _public directory will be copied verbatim into your chosen output folder. This is where you’d store your images, stylesheets, JavaScript, etc.
Flexible Templates
Finally, the HTML templates that are used to built your website are in the _templates folder.
I can hear what you’re thinking.
PHP?
That’s right. I realized early on that I’d need at least some minimal templating language to build the design I wanted. I couldn’t (didn’t want to) put all that logic in Swift. I certainly had no intentions of writing my own templating language, so I turned to Google and found Ink (also by John Sundell!), Tuxedo, and Stencil.
The last three days have been a bit of a blur building Roland, so I may have my wires crossed. But the reason I didn’t stick with any of those projects – even after getting proof of concepts working with all three – was they ranged from being a little too inflexible with how sub-templates were included to being really, really slow. I’m talking on the order of 1 second per page to generate. And I also realized that no matter how advanced or how much effort their authors put into the syntax and features of their template language, it would never be as flexible and powerful as…
PHP.
So, yes, Roland uses PHP to render your templates. I’ve long thought this and my work this weekend once again confirmed it for me, but PHP has always been the ultimate templating language for the web. I feel like every other template language I’ve ever used has always boiled down to a less-capable subset of PHP’s features aimed at people who don’t want to use a programming language. And that’s totally cool. There’s definitely use cases for that. But as a long-time PHP developer, I wanted the ease of use and power that a real language affords.
So, Roland (by way of Swift) runs your templates through the system PHP binary and outputs the results. It even allows for full use of include statements so you can structure your templates any way you want.
And while I realize how insane doing it this way may seem, Roland injects the data for your posts, pages, website metadata, and configuration settings into PHP’s global scope, so that your templates can use all that information to render your website exactly as you want. Doing that live on a real web server would be nuts. But this is all pre-compiled and saved statically to disk ahead of time. When served to your visitors, there’s no PHP being executed. So the security (and performance) implications aren’t a thing.
Here’s a sample template that renders the page for an individual post.
The post’s properties like title, date, permalink, content, etc. are exposed natively to PHP like $post_title. You can easily create dynamic layouts by doing things like
<?PHP if(isset($post_previous_post_id)) : ?>
to decide if a link to the next post should be shown or not.
Having all of this data available to each page and exposed to PHP means I can finally make some interesting choices and optimizations that I’ve long been putting off because it would have otherwise meant mucking around with WordPress plugins. For example, all of the video content for this blog is hosted with BunnyCDN and played with VideoJS. Unfortunately, even minified, the JavaScript and stylesheets for rendering video are my largest static assets. But now, at build time, I only include those assets in the HTML on pages that specifically contain video elements. If a visitor browses this blog and never encounters a page with video on it (which is the vast majority), then that’s an additional 350 KB they don’t need to download. That’s nothing on a modern connection. But on mobile? Every byte adds up.
Miscellany
Categories
I mentioned earlier that categories are placed in the post’s front matter. That works fine, but it doesn’t allow you to define a hierarchy of categories – just a flat list.
So, Roland will look for a categories.txt file in your project directory that allows you to define parent categories and subcategories.
The first category on each line is a parent. Any additional, comma delimited catogries that follow the parent on the same line will become children.
I’m not overly thrilled with the dumbness of how that file is structured, but, hey, it solves the problem for now.
Global Settings
And because I’m an Apple developer, the global configuration settings for your website are stored in a .plist file.
This contains settings such as
Base URL of the website
Title of the website
Posts per page
Whether or not to show post excerpts or the full post on every page
etc.
You can also define your own custom key pairs which are exposed to your templates in PHP. For example, I’ve added
My CDN’s base URL which is prefixed in front of all static assets
Default post author
Title of the generated RSS feed
etc.
By default, when you run roland, it will look for config.plist to build your website.
But you can also include multiple property lists – one for testing locally, another with settings for a staging server, and one for production. Then, just tell roland which one to use at build time using the --config flag like
roland --config production.plist
Project Status
As I’ve said a few times now, Roland was built over a three-day weekend. It’s pretty opinionated in the type of website it will currently output – namely, a blog.
I don’t overly love the way the Swift side of things is structured. Don’t get me wrong, it totally works! (For my purposes.) But there’s certainly some tidying and cleaning up to do. I also want to make it a bit more general purpose so I can move clickontyler.com off Jekyll in the near future as well. Overall, I consider it a first draft.
I’d love any feedback folks can offer. Jekyll is the only real-life experience I’ve had with static website generators and has obviously influenced how I approached this project. On the other hand, maybe I’m just an idiot WordPress user and all of my pain points could have been avoided with one weird trick.
In any case, whether not it was worth the effort to build Roland from a technical point of view is certainly up for debate. But it sure was a fun distraction to hack away on. And it feels amazing to finally have complete control over my primary web presence.
It took me a few days longer than I had hoped to get started, but here’s the first post in a new Favorite Things category celebrating #IndieSupportWeeks.
First up, is the incomparable MailMate by Benny Kjær Nielsen. It’s “the email client for the rest of us”.
Anyone out there remember Email init? Which then became Letters.app? It was a project started by Brent in January 2010 to be
an email client that actually meets the needs of developers and professionals who rely on email, folks who type for a living.
If memory serves, and if Twitter would get their dumb act together and just show me this timeline in damn-chronological-not-algorithm-optimized-order, it looks like Gruber took over leading the project along with Gus as technical lead. (And Brent being the honorary drink-buying chairman.)
I’m not sure when exactly the project died. The last tweet was February 23 of that same year. And the last real web mention about the project I’ve been able to find is Brent doing a mighty good deed by auctioning off the domain name for App Camp For Girls.
We can all dream about what could have been: a truly Mac-native email client for power users. Or, you could just use MailMate right now.
MailMate is a glorious, configurable, ultimate-nerd-dream of an email client built just for macOS. I first discovered it back in 2013 when Benny did an Indiegogo campaign to fund full-time development of the app. I was more than happy to throw in for a license key of my own to help keep the project moving forward.
I’m thrilled to say that six years later, MailMate is still going strong. I use it every day in conjunction with Fastmail and SaneBox to give me email super powers.
Why is MailMate so great? A lot of folks I’ve recommended it to (ok, forced upon, really) said “Eeeewwwww” when they tried it. And I’ll be the first to admit it’s not the prettiest app, but it does feel at home and serviceable on macOS. And then, of course, it does have a hell of a learning curve for an email client compared to most others. But the killer feature?
It just fucking works.
And believe me. I’ve tried every single email client for Mac and iOS – paid apps, free apps, subscription apps, apps from small companies, and apps from giant corporations. There are exceptions, of course, but most are mediocre. Nice to look at, a few clever features maybe, but they all almost universally fall apart when dealing with 15+ years of emails unless they rely on a server-side component to do the bulk of the work. And in 2020, is asking a piece of software to handle a few gigs of text and a ridiculously complicated networking protocol really that difficult?
So I have the utmost respect and amazement for just how incredible a job Benny has done with MailMate. In a single app, he has
Built the most stable email client I’ve ever used
Built the fastest email client I’ve ever used
Built the most powerful email client I’ve ever used
Built the nerdiest email client I’ve ever used
If you can just get past the initial configuration and learning curve and join the Religion of Plain Text Email Composition, you’ll find a desktop email app that wipes the floor with the usual competition.
The whole modus operandi of MailMate is its use of smart folders / searches / filters / etc for reading your email and plain text for composing messages.
MailMate only allows emails to be written using a plain text editor. It is important to understand that this is a feature of MailMate. It might even be its most defining feature.
Plain text is whatever text you can write with your keyboard. This means that you cannot visually emphasize words, create outlines, create links, and insert images within the text editor itself, for example, by clicking buttons. Instead, you can (optionally) use the simple Markdown syntax. This is then automatically converted by MailMate to HTML which is the (unofficial) standard for rich text emails. MailMate automatically shows you a preview of the email and this is what most recipients of your emails are going to see.
I’ve always been a nerd about the emails I write and have adamantly refused to send HTML email unless absolutely necessary. I totally understand the need for businesses (like mine) to send styled advertisements (I hate it, but I get it), but for a normal person just writing emails there’s no need. Plain text FTW.
As for smart mailboxes
MailMate encourages the use of so-called “smart” mailboxes. These are virtual mailboxes which show messages which belong to a specified set of mailboxes and which match some set of conditions. When handling a new message in the Inbox, the basic decision to make is whether it should be archived or trashed. The rest should be handled by smart mailboxes.
And those conditions can be layered on-top of one another and combined with powerful search strings to create the perfect smart mailbox that you refer to frequently or just to help find a long lost email from a decade ago. Just look at this beautiful example from the help manual:
foo f !smith t (smith or joe)
This means:
Message contains "foo" and From does not contain "smith" and (To contains "smith" or "joe")
And as for searching and filtering by date, holy crap:
And just like best-of-breed Mac apps, MailMate supports a plethora of keyboard shortcuts that let you plow through and triage your email without reaching for the mouse. You can do the usual commands such as archive, flag, delete, mark as read, mark as junk, etc. But then you can also hit ⇧⌘M to bring up a filterable list of all your mailboxes and effortlessly move the current message (or messages). And ⌘T will similarly let you go to another mailbox.
And the keyboard shortcuts don’t stop there. You can also assign them to any of the plugins or 3rd party scripts you’ve installed.
Whoa, whoa, whoa. Did I just say plugins and scripts? Yep, MailMate is wide open for you to run custom actions and perform tasks.
I’ve installed plugins for sending emails to OmniFocus as new tasks, archiving into DEVONthink, and editing replies with TextMate. I even wrote my own plugin that grabs the sender of the current email and opens a browser window showing me that customer’s order history and previous support requests in my backend system.
For each mailbox (not just account, but any mailbox) you can decide to show a Notification Center alert, a count in the menu bar, or a Dock badge. MailMate supports showing four different dock badges at once (one per corner). You can also choose what information is shown in Notification Center alerts and pick a custom sound. Or any of those in any combination.
I don’t know what else to say except that I love this app so much. And unless I’m horribly mistaken and there is secretly a giant corporation hiding behind MailMate and slurping up all of my private data, MailMate is built by a single developer, which is even more awe inspiring.
I try to keep this blog on topic. That being the business side of software development, or productivity, or the various ways I try to bend macOS to fit my odd workflows, or just griping about technology in general. My assumption is I’ve been writing about those topics here for thirteen years, and those of you kind enough to spend a few minutes with me every week keep coming back because they overlap your interests, too.
So, I do my best to keep other topics at bay – especially ones concerning the world outside our tech bubble. But at the same time, writing has always been therapeutic for me. It helps me organize my thoughts and stay centered. For the three or four hours I spend writing each week, the familiar pattern of brainstorm → write → edit → post → react lets me escape.
And we could all use an escape right now.
I’ve been working on a much larger piece recently. My working title for it is American Virus. It’s my take on the events shaping our new world in 2020, and why my country is attempting to out-America itself like never before. How my family is coping. How I see my friends (from a distance) dealing with life. And how technology blends into everything.
I don’t know if I’ll ever finish writing it or ever even post it. It just seems to get longer and longer each day as I think of more and more to add and document about this time period.
I think the most important thing is that I am writing. Number one, it’s good for me. And, number two, I think we should all be documenting our shared experiences. At some point in the future, it will be over – in one way or another.
And when the other side is reached, I hope we can look back on the things we did and how we were feeling in this moment and learn from that.
And so with no real conclusion in mind for a post that doesn’t really fit with the things I normally write about, I’ll just leave you with a link to the place where I do go to to write about stuff not made of ones and zeroes.
With all that’s going on in the world, it may not surprise folks to learn that small developers are starting to feel the economic crunch along with everyone else. In an email exchange I had earlier today, another owner of an indie software company told me:
It’s been an awful couple of months. [The city] is mostly locked down until May 4th. My kids look like they are going to be home for the foreseeable future. Their schools have gone full remote learning. So far, [my company] is weathering the storm. We have been giving out a few more complimentary extensions and refunds. But we have always given that to anyone that asks so it’s hard to see the change. How are you doing?
Their sentiments go on to echo what I’ve heard both publicly and privately from other folks in our little world of apps and services. I’m extraordinarily lucky that I have a full-time job (for now?) in addition to my app business. Don’t get me wrong – my app sales sure as hell help a whole lot, but I’m in a much better position to come out the other side of all this in one piece than folks who truly do depend on the whims of consumers for their 70% App Store cut.
…that I wanted to do something for our community’s indies.
Normally, this site (and all of my other work) is funded by sponsorships through non-tracking, privacy-focused (and JavaScript-free) ads that I run on a weekly basis. But for the next two weeks there will be no ads on this site. Instead, each day, I’ll promote a new indie app whose developer has been financially impacted by the current pandemic. For free, with no strings attached.
He’s taken it a step further than his own blog and started a GitHub project to coordinate the effort. The project has a growing list of folks helping out to promote our favorite indie apps. It’s a wonderful idea, and I’ve started brainstorming my own list of must-have apps from independent developers that I can’t wait to write about in the coming days and weeks.
