Self-hosted jira is prone to death by a thousand cuts making it a much worse alternative to the hosted version.
- The typical mom & pop business: Squarespace
- Any company without in-house technical leadership: Wordpress + Simply Static
- Any engineering-focused company: Sanity
These recommendations account for common requirements each tier of company typically has - engineering permission to use sensible tooling (typescript, openapi type generation, etc)
- strong / focused product team (stable roadmap for project requirements)
- modern ux designers (able to design a component library & can easily communicate changes (Figma))
I've noticed that companies that get this right tend to have healthier work cultures & deliver on expectations without stress. - api for creating pages from remote data
- developer experience
- build speed
But if you plan on using a headless CMS, your must prioritize decoupling the authoring from build times. - use client side rendering for page previews. (i.e. use a js-based framework)
- containerize your project & run the framework's dev mode as a preview server (i.e. you might as well have not used a SSG) - being miscast as the villain by a stranger with a hero complex
- a neighbor reports you as vagrant that “doesn’t belong here”
- matching a generic description of a random suspect (white t-shirt and jeans)
- a late night traffic stop with a visibly nervous police officer
Even during these rather tame scenarios, there is no room for hesitation. You put on your best acting face and try making strangers comfortable with your existence.