Kind replies

 Reply

We've done that too (but don't have kids) so Anna Dodson and I each have profiles and then there's a shared one which doesn't skew our history. But the family mix includes music from all and is quite nice!

 Reply

Hey! Do you mean instead of having my base image downloading each of the gems and the Netlify CLI? Yes I did, but I was a bit lazy so didn't get round to it. I've since moved to Netlify's build https://www.jvt.me/posts/2020/05/27/migrate-netlify-deploy-gitlab/, although I'm wondering about going back to GitLab again to cut costs, and hopefully speed it up a little

 Reply

A fair few of us using static sites use https://webmention.io as our webmention server, and then you have the choice of how you want to display them. I used to do it on site builds, but moved to dynamically doing it with client-side JavaScript for a more up-to-date feel as mentioned in https://www.jvt.me/posts/2019/06/30/client-side-webmentions/

 Reply

This is interesting. I wonder if there is some way to make the error message more clear what the root cause is in this case 🤔

 Reply

What sort of things are you finding most painful with build/dependency management? Out of interest from someone with not a lot of varied language experience

 Reply

Definitely happy to chat more on Slack / at #HomebrewWebsiteClub if you're able to join, but my recommendation is generally Hugo. Templating / documentation is not the best, especially if you're not used to Go's templating. I moved from Jekyll last year https://www.jvt.me/posts/2019/01/04/goodbye-jekyll-hello-hugo/ and have found it a much better experience. It's super quick to build (even for my large multi-purpose site) and has a tonne of stuff built-in to it that makes it fairly batteries included

 Reply

I moved from Jekyll to Hugo cause of speed and massively recommend it. It's a bit painful documentation wise / if Go's templating isn't your cup of tea but I could see it being one of the longer running static site generators

 Reply

So my angle on this is to have a client that is completely auto-populating. It's not necessarily something that will be useful for everyone, I admit (and is a slightly different interaction model than we usually use).

But I think it'd be quite nice to be able to point a Micropub client to a Micropub server, and have it render an editor for all the given post-types, with all the given properties, instead of needing to build the client with some awareness of what is required.