puck VS react-page

See the full changelog for all changes via the GitHub release.

If you’re starting from scratch, you can also use one of the Puck recipes to spin up a new project:

⭐ Support us on GitHub by dropping a star

Puck is an embeddable, modular, open-source visual editor for React with built-in support for complex drag-and-drop page building. While GrapesJS provides a barebones page building experience, and tools like Builder.io and Storyblok offer fully-fledged CMS platforms, Puck aims to bridge the gap. It combines an extendable ready to use page editor with a fully decoupled page export model—giving you flexibility without locking you into a specific backend or proprietary ecosystem.

That would be wonderful, but will require some further work. Puck doesn't provide a grid, but it supports user grid implementations.

To support something like you're suggesting would likely require an official Grid component, which I'm now tracking here: https://github.com/measuredco/puck/issues/843

The official next recipe now uses Next 15.1 and React 19 by default. If you're using the recipe and want to upgrade, make sure you also upgrade to React 19 as required by Next 15 when using the App Router. See the official Next.js upgrade guide for more info.

I was using another great library called puck, which is basically a very customisable editor, that can create sites/newsletters/pdfs (something visual) and came to the next step which was turning the output of the editor into a PDF.

We're grateful for the community's support and contributions. Join the conversation on GitHub and Discord.

Hello fellow hackers!

We launched Puck in September [on Hackernews](https://news.ycombinator.com/item?id=37391848) after building it for our clients, and had a wild ride to the front page!

I wanted to share a little update on what's happened since:

1. 3.7k starts [on GitHub](https://github.com/measuredco/puck)!

This is really slick! A really fluid and intuitive interface.

We use https://react-page.github.io/ (also MIT licensed) extensively at my startup; it attacks the same problem, and it's been incredibly effective (and hackable!).

Generally speaking, owning your own CMS data, in your own database, with a well-documented JSON data format, and adding the ability to take any React component you've written (that itself may interact with your own data) and make it not only reusable as part of a content editing system but also WYSIWIG, opens up a huge number of opportunities - including adding your own logic to transform content before display.

https://builder.io is another alternative that's very effective at the adapting-custom-components-to-WYSIWIG side of things, but does keep the data in its own cloud storage.

I'm really excited to see innovation in this space, and I'll be following Puck closely!

A few days ago someone posted a link in an answer to a similar library to https://react-page.github.io/.

https://github.com/react-page/react-page is fully open source with a simple JSON data model and multi-language support; we’ve built various utilities for auto-generating content. Invest a few days in customizing CSS and you have a world-class WYSIWYG for your own design language. Highly recommend.

I maintain https://react-page.github.io/

If its just some rich content you want to edit, you can also use https://github.com/react-page/react-page which is a rich content editor, that i am maintaining. You can use it to edit and display content. The data itself can be stored as a json string and can be saved in your api, your firebase or your headless cms. I also tried to pair it with strapi, where I would share ReactPage‘s config and cell plugins both with a nextjs frontend and strapi admin panel. This is extremly powerful and flexible.

I came across react-page[1] the other day, it seemed like a reasonably powerful block editor but was too much for our purpose so I haven't actually used it.

[1]: https://github.com/react-page/react-page

a quick search turned up React Page — can anyone vouch for this or recommend anything else?