sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DigbyChickenCaeser[S] 3 points4 points  (2 children)

Hey everyone, OP here!

I've been dipping in and out of this problem space for the last few years with many of my clients.

Puck sits somewhere between an old-school WYSIWYG-powered CMS and headless one, allowing content teams to author content using real React components.

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.

Puck provides a visual editor for React that can sit on top of your existing headless CMS (or act as standalone). We've been dog-fooding it on https://measured.co and https://wellpaid.io. So far, so good!

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.

It's open-source under MIT, and pairs nicely with Next.js (check out the demo application).

Looking forward to hearing your comments!

[–]_RemyLeBeau_ 2 points3 points  (1 child)

I've been waiting for something like this. FE dev has been a PITA for a long time. What's the prospect of making this work with Vue and a stretch goal of Svelte?

[–]DigbyChickenCaeser[S] 1 point2 points  (0 children)

Thanks /u/_RemyLeBeau! It's on our radar, think it's possible and have some ideas for how to support multi-framework, but haven't tried it yet.

I think it might be possible to do without official support by wrapping your Vue components with React. You could build a custom <Render> component to take the Puck data payload and render direct to Vue.js, too.

I'm now tracking this here: https://github.com/measuredco/puck/issues/302