Hacker News Reader

Comment by anakaine | Hacker News Reader

The thing that kills me with this, is that it must be such a pain in the backside to build, scale, and manage. I'd love to make use of these technologies, and I work for a suitably large organisation - but I'm not a one man army and this requires a serious team with some serious depth to it, invested time and remuneration overheads.

How do I handle users, roles, permissions, application logic, database, forms, content, publishing, etc? Wordpress. It may not be in vogue, but its all there and I can deploy it pretty quick.

Is there a solution I can pick up that will run as a static site, make use of serverless, and not take forever to build out?

View on HN

There are numerous MVC frameworks for any given language. Some even give you admin control panels out of the box if you need a quick and basic admin. Trying to contort Wordpress into some kind of application framework will arguably take longer to build out than using purpose-built frameworks. Even something as basic as routing is quite convoluted in Wordpress.

BTW wordpress can be used as a headless CMS. Your content creators use the wordpress interface and then you use it to build your static site from there. How much this is actually better than just using wordpress with cloudflare plugin, I don't know.

Yeah. Most CDNs and caching plugins deliver a substantially similar result in that regard I suspect. My sites rely a great deal on granular group permissions and contextual display of accessible items. Gut feel is id be coding for days to replicate tick box functionality.

There are some cms solutions up and coming that build on that kind of infrastructure, but I’ve seen nothing yet that can compete (for small teams) with Wordpress.

Wagtail is pretty good on the non static site version of that (there is a thing to make it publish to a static site too).

Maybe Next.js and AWS Amplify fits your bill?

What’s the authoring and workflow side of this? Seems like it would be entirely custom?

Amplify has its own (Rails like) workflow, with its own CLI and it comes with libraries for JavaScript and UI components for React.

Next.js has its own workflow, with its own CLI, etc.

The only thing missing is integrating the two, so it's not "entirely custom".

Investigate JAMStack.

Initial investigation reveals that this is just an index of static site generators and management interfaces that don't really address the points I raised.

Reply on news.ycombinator.com