As of right now the full build takes over an hour to run, and this makes cycling for PRs and quick iterative development very difficult.

While the code may live online somewhere forever, an open source project only truly survives if someone maintains it.

I'm still deeply working on it every day, i'm around 1/2 month away for a first preview release.

But I love it, and so I plan to keep it alive.

you honestly don’t have the time to decide which of these options is better.

backstage Issues and merge request related to improvements like refactorings, tests, maintenance etc

However, since problems are only addressed when they arise, maintenance is reactive rather than proactive. Small problems left unaddressed can balloon into major failures due to focus on cost.

Most traditional (monolithic) CMS systems are “coupled”, meaning that the content management application (CMA) and the content delivery application (CDA) come together in a single application, making back-end user tools, content editing and taxonomy, website design, and templates inseparable. Coupled systems are useful for blogs and basic websites as everything can be managed in one place. But this means that the CMS code is tightly connected to any custom code and templates, which means developers have to spend more time on installations, customizations, upgrades, hotfixes, etc. and they cannot easily move their code to another CMS.

Potential for political focus on building new features over technical improvements (such as refactoring)

Using versions is a maintenance burden on the preset, and we made this mistake with Neo. By specifying a version, we are forced to track with React when their version changes, possibly falling behind.

I had to upgrade my other project from Webpack 2 / Angular 5 to Webpack 4/Angular 7 and it was a complete nightmare! I lost a ton of hours and can't really justify charging my client for the weeks worth of time to figure it out.