Remix.run Logo
solardev 16 hours ago

I've set up many of these sites for individuals (including several elderly folks) and small nonprofits. I'd very strongly advise against self-hosting any sort of stack in a situation like this. Whatever you set up is going to be obsolete in 2-3 years, and the club will have to find some poor soul to migrate it to another framework. I've seen that cycle happen so many times already.

If you build something yourself, it's going to be even worse, because nobody in the club will have any idea how to find help for it once you're gone. They wouldn't even know what to call it, and "stack" means nothing to them. Even if you want to write it in vanilla HTML, even that is a rarer skill in today's dev landscape, and that usually means you have to manage hosting and deployment on your own too... good luck explaining SFTP or SSH or HTTPS to whoever inherits the site.

IMHO Wix is the way to go, especially if the club has someone technical at all. Then you can make that one person the admin (probably whoever pays for it) and use their roles system to assign "blog writer" roles to limit the complexity for everyday users who just need to post new articles (https://support.wix.com/en/article/roles-permissions-overvie...).

Wix also offers a single-vendor experience with support, so if the club has issues with anything, they know who to reach out to. Wix will be able to help them with everything from the user experience to domain issues (register the domain through them too).

As devs we always want to go cheap and easy (for us) and self-host on simple clouds... but that creates a completely unmaintainable situation for the client where they have no single vendor to reach out to and need to hire a web dev to make any changes. That web dev has often been me, and I've migrated a lot of people to Wix and they've stuck with it years later.

Don't overthink and over-engineer this. It's not about what's FOSS, it's about what a bunch of non-techie people have to work with years after you're gone. That requires a relationship with some single vendor who cares about them, not a mishmash of soon-to-be obsolete software and ever-changing deployment schemes.

Even if Wix isn't perfect, two years later, it's going to be a LOT more supported than any self-hosted stack.