Good going, aforementioned “yet another person.”
I’ve also converted my existing Hugo-based version of the Eleventy repo (i.e., the one from which Vercel builds this site) to being another starter set. (Why two Hugo starter sets? I’ll explain that shortly.)
Starter vs. non-starter
First, let me deal with one even more salient question: what exactly is a starter set where SSGs are concerned?
In my starter sets’ cases, at least, the term refers to a site repo that has been pared down to a sufficiently minimal set of content and configuration so that, while someone new to the SSG can load and run it, he or she then can also customize it without having to delete a ton of unneeded stuff.
A few months back, I made public the Hugo and Gatsby versions of this site’s repo. This was a follow-up to my having made my Eleventy repo public last December (the webpack-based version I had for a while) and two months ago (the current, non-webpack version). I thus hoped the choice among the three repos I’d used would be as helpful to me as I have found it to see others’ repos.
The problem with that approach was, as I noted in the repos’ README files, each definitely wasn’t a starter set although it could be used as one—if, of course, one was willing to go through and carve away all my content. (Yeah, right.)
Then, more recently, I pared back both the Hugo and Gatsby versions to a very small number of posts, hoping that would simplify things. Still, the posts that did remain were the actual content rather than more generic (and very short) posts, and thus the repos remained not truly “starter-ish.”
In addition to that, I had no reduced-size repo for helping folks interested in Eleventy, and that really griped my cookies because that’s the SSG in which I most want to spur newbies’ interest.
So, I spent the better part of this weekend fixing this problem, resulting in those three new starter repos (well, two new starter repos and a third repo repurposed as a starter repo).
Each of the three repos has only a small number of posts, each with pretty generic front matter and content, but with a few tips of how to include things like images and code blocks. I have “generic-ized” each repo so that it doesn’t come with my name, logo, and site URL all over the place; it also doesn’t have webmentions support so you won’t have to worry about all the code involved with that.
Two for Hugo . . .
Repeating the earlier question: why do I have two Hugo starters?
. . . and none for Gatsby
And now, we get to the elephant in the room.
Where’s the Gatsby version of all this?
Well, um, there isn’t one.
I did try to create one but, as has been my usual experience with Gatsby (as recounted here), it didn’t go all that well. Let’s just say Gatsby in dev mode was its usually finicky and glitchy self. Fortunately, with many Gatsby starters out there already, the lack of one more isn’t going to hurt anybody.
(I will keep the current Gatsby repo up there for the curious, but plan few or no changes to it going forward. I’ve decided that the wisest thing I can do with that repo is to, quoting the perhaps unintentionally sad sign stenciled on the launch pad where the Apollo 1 astronauts were killed in 1967, ABANDON IN PLACE.)
Plenty of good choices out there
Gatsby isn’t the only SSG blessed with numerous starter sets out there for your learning pleasure. There are tons for the considerably more venerable Hugo, and a decent and growing number for the much younger Eleventy.
In any event, I hope that my new little efforts in this regard will help anyone who, as was true for me not all that long ago, is trying to find the path to a better website-management experience that I believe either Eleventy or Hugo will provide.
Update, 2020-08-07: Each starter set now has its own online demo on Netlify, linked from its repo.
For those who do want to add webmentions, you may want to check out my recent five-part series on doing just that, beginning with Part 1. If you’d already seen those posts when I first issued them, please note that—given the changes I’ve made since then to various repos to which I’d linked from those posts—I have now moved the linked files to their own repo for archival purposes, as is now explained at the start of each of the five posts in the series. ↩︎