Title: Hey hackers, OP here!<p>I&#x27;ve been dipping in and out of this problem space for the last few years with many of my clients.<p>Puck sits somewhere between an old-school WYSIWYG-powered CMS and headless one, allowing content teams to author content using real React components.<p>Traditional CMS solutions were flexible but often resulted in page that completely broke the brand guidelines. Headless CMS solutions are a fantastic way of controlling brand by restricting UI changes to developers, but makes layout changes restrictive and slow as developers often need to get involved.<p>Puck provides a visual editor for React that can sit on top of your existing headless CMS (or act as standalone). We&#x27;ve been dog-fooding it on a few pages at <a href="https:&#x2F;&#x2F;measured.co" rel="nofollow noreferrer">https:&#x2F;&#x2F;measured.co</a> and on <a href="https:&#x2F;&#x2F;wellpaid.io" rel="nofollow noreferrer">https:&#x2F;&#x2F;wellpaid.io</a>. So far, so good<p>The API is built for React, which allows FE devs to quickly integrate their existing component and add some form fields for author input, or connect it to a headless CMS of choice.<p>It&#x27;s open-source under MIT, and pairs nicely with Next.js (check out the demo application). Next in the pipeline: support for multi-column layouts, richer demos, new plugins.<p>Looking forward to hearing your comments!
Upvote: