4 ms·
Vercel Visual Editing: Click-to-edit content for headless CMSes
- proxy9 3y agoInline editing is generally a bad idea. I don't see WSJ rocking this anytime soon.
- Rauchg 3y agoIt's both inline editing and the ability to link arbitrary rendered text to its originating CMS and content flow. More detail here of how this scales to any content model complexity: https://twitter.com/rauchg/status/1653800915827310593 https://twitter.com/rauchg/status/1653800915827310593
- cramforce 3y agoThe 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.
- proxy9 3y agoMight be interesting for marketing guys but take it from a guy who’s worked with publishers. They hate inline editors.
- cramforce 3y ago<CTO of Vercel here> - 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.
- o_m 3y agoAre there any plans to make this available to non-enterprise customers?
- advancingu 3y agoHave you considered that content might come from Git? If so, how would content branches fit into this? (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 https://github.com/contentlab-sh/contentlab )
- adoxyz 3y agoSuper 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.