|
|
|
|
|
by mateomorris
1297 days ago
|
|
The problem you're describing is exactly why I'm working on https://primo.so. WordPress makes content editing easier, but damages the developer experience. So devs reach for JS frameworks in search of more productivity, but then the content editing experience suffers. I found the solution was to embed a code editor in the CMS itself. As strange as it sounds, removing the distance between the content and code means that devs can build and modify components and whole sites (which are made of both) in a tenth of the time while giving content editors the page-building powers they love. |
|