I might miss something but I don't get why people always see the content editor as part of the "headless" back-end and not as a part of the front-end ?
What prevent us from integrating our own editor in the front-end, protected by the usual permission system ? If an headless back-end can deliver content it also can ingest it.
Of course you can still deliver a basic content edition experience on the back-end to kickstart everything but separating the edition from the display seems counter intuitive and not supported by any technical limitation.
Am'I oblivious to something or is it just a general bias ?
This is great and it is indeed the direction we are taking with ReactBricks: the Admin is inside the Next.js or Gatsby project. This way we also solve the problem of "sharing bricks components between admin and frontend": they are the same project! 😊
always nice to learn I'm not completely out of my mind :-) I'll follow your project hoping to see it kickstart a new "path" for the modern content stack.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.