The editing functionality is delegated to the CMS. Respectively content changes flow through the exact pipeline as changes originated directly from the CMS would. In fact, we allow the CMS to completely control the actual editing experience.
The main point of this feature is that if an employee does find a typo on some article, they can just fix it rather than going to the CMS, finding the actual place where that text is stored, making the change, etc.
- You can turn this on without changing the code of your site (just need to activate emitting the metadata in the CMS)
- Supports any framework
- We're working on an open content-source mapping standard that makes the underlying tech available to any CMS, e-commerce system, or other content source.
Super cool. While I don't see it being a primary way to create content, being able to make small adjustments, tweaks, typo-corrections on the fly seems like a great UX improvement.
8 comments
[ 3.4 ms ] story [ 15.3 ms ] threadMore detail here of how this scales to any content model complexity:
https://twitter.com/rauchg/status/1653800915827310593
The main point of this feature is that if an employee does find a typo on some article, they can just fix it rather than going to the CMS, finding the actual place where that text is stored, making the change, etc.
- You can turn this on without changing the code of your site (just need to activate emitting the metadata in the CMS)
- Supports any framework
- We're working on an open content-source mapping standard that makes the underlying tech available to any CMS, e-commerce system, or other content source.
(Disclosure: I'm building a library that turns a Git repository into a branch-enabled GraphQL content management API. See https://github.com/contentlab-sh/contentlab )