> Preview workflows are clunky. Draft modes, toolbar toggles, account requirements just to see what your content looks like before it goes live. Having to add data attributes everywhere to connect front ends with backend fields feels unnecessary. Real friction for something that feels it should be simple.
I was happy to read this part at first, because it highlights what I hate most about Headless CMS. Hearing a company in the industry admit to this problem gave me hope that they are now going to fix it or have better solutions. But no, the rest of this article is just rambling about how 'you don't really know about CMS'. I mean, if you know better than us do, then why can't the experience of using Headless CMS be better? You are here to solve the problem, right?