[lovetocode]

Am I the only one who hates the whole concept of a CMS? I much prefer just working HTML changes into a dev cycle. CMS encourages marketing and sales people to wreak havoc on your web experience. Working in HTML changes into the dev process also helps keep the engineering team aligned with the business/marketing strategy. I use Middleman for generating static html websites and it works great. I would love to see the concept of a webmaster come back.

[pindab0ter]

There’s real value in allowing people with no HTML/CSS knowledge to write content. I also don’t see how writing and publishing content would wreak havoc on someone’s web experience, or am I missing something?

[ThinkBeat]

I think all CMS I have used (aside for one I built of course) Are annoying, and getting pixel perfect results is challenging. I presume that will become easier when we move to headless CMS.

The reason I like he and that often insists on it ,is because my team finds it both tedious and boring to have to make constant changes every time some in marking or legal or content writers which to ”change a few things” It is also far cheaper for them to so it themselves, and my team can can focus on on more important things. And yes there will be times when a developer needs to make changes still.

The company I am at now sends” superusers to pretty tremendously comprehensive training on how to use the CMS tool. Usually, one or two people from each department are chosen to be superusers.

That all works out much better than my team had to do the training. We were frankly not very good at it and it is far cheaper to outsource that for us.

All of that means that our team get magnitudes fewer phone calls or tickets about how to do X or Y since the go to the super users for help. If the superusers are not about to figure it out he or she contacts us.

This is awesome because when the superusers contacts us she can give a much more insightful description that a newbie employee with limited exposure to CMS's. To our tools. And often not that familiar with computers.

People often talk about CMS being too slow in production. We have very few problems with that.

We took a lot of time evaluating and testing the tools we use both for performance and for ease of expanding extending and customizing and developing And superusers how we believe our superusers will like the interface. And yes of course we had focus groups with potential superusers we're they could give us feedback.

[gexla]

I swear nobody making comments on this item has used the software in question.

With both Craft and Wordpress you can do EXACTLY the same output as you would with a static HTML site.

How does a headless CMS solve a problem which you apparently know nothing about?

Are you creating custom content management systems without knowing how the most popular options work? That's not to say you have to know how these work, but I would be skeptical of hiring anyone who didn't know the capabilities of what's already on the market.

[gexla]

> I much prefer just working HTML changes into a dev cycle.

Have you worked with either Wordpress or Craft? With each of these, you control the HTML which gets generated via templates which are files on disk which can be checked into your repository.

The content management element of the CMS allows users to log into the control panel to manage the content. This experience is controlled by the developer. In some cases, you might constrain editing to a simple WYSIWYG experience which is similar to support you might expect from Markdown. In other cases, a developer might allow blocks of HTML which could even include styling.

How would you expect "marketing and sales people" to work with Middleman or any other static site generator?

[chaoticlaw]

I think that love it or hate it, the CMS is a major value add to an organisation. They probably don't want to waste your time (or theirs for that matter) having to go back and forth between their content team and the dev just so they can create/update/delete a page.

[lwhi]

This isn't a sensible approach.

We need experts to develop products from a code PoV.

We need experts to create content.

Not many content creators are great developers and visa versa.