puck VS formkit

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)!

formkit/drag-and-drop is a relatively new, lightweight library developed by the team behind FormKit, a form framework for Vue. Unlike traditional drag-and-drop libraries that manipulate the DOM directly, this one takes a different approach: instead of physically moving elements around, it updates a underlying reactive data model that you provide. This means that rather than worrying about manually reordering elements, you let the library handle updates to your data structure, making it feel more like a natural extension of reactive frameworks.

The Vue ecosystem is packed with many great form validation libraries, VeeValidate, Vuelidate, and FormKit just to name a few.

if you're going to be dealing with forms then FormKit (not a UI library) is worth your time. It's an architecture-first form framework — can be used with any UI library if you prefer.

I probably say this too often, but I'm fascinated by how much the Vue ecosystem has been thriving lately. Recent releases of such awesome libraries like FormKit or Radix Vue are great examples of how well the Vue ecosystem has matured lately.

FormKit is a library that helps you build complex forms in Vue. It is built on top of Vue 3 and uses the composition API. It is very easy to use and has a lot of features. You can check out Formkit Website for more information.

If you're in the Vue space (and you will be if you're using Nuxt) then I highly recommend checking out FormKit (I'm one of the maintainers). It's not a UI library — it's a framework for managing your form architecture and data. Forms are some of the most complicated front-end work you'll do if you do them well and FormKit will save you many many tears. If you want a quick primer on "why formkit?" here's a 3-minute video that demonstrates how much simpler a FormKit form will be to manage vs one hand-written in Vue.

If your project requires building forms then FormKit can save you a lot of effort.

Starting with Beta 17 — FormKit ships with a new Zod plugin that you can use to validate your forms.

Unironically this, but it's called FormKit. 🥲