Live data from Hacker News

Show HN: Puck – Open-source visual editor for React

github.com

71–80 of 105 posts

Re: Show HN: Puck – Open-source visual editor for React

#71

Earlier quoted context omitted.

Framer is a design tool, but Puck is a content tool. We're focused on allowing content teams to create pages using existing on-brand components. Like a WYSIWYG with guard-rails. We built it because we couldn't find something that would let our clients' content teams produce content for their sites without 1) either going off-brand or 2) pestering their devs for layout changes.

Framer also has a CMS and you can import React components [1]. They pivoted because there wasn't much traction in that use case. [1] https://www.framer.com/developers/#overview

your pivot comments seem irrelevant as he is not selling this as a product, he is using it as a white-label solution for his clients.

Re: Show HN: Puck – Open-source visual editor for React

#73

Probably ia cliche now but ... Have you considered integrating an LLM to expand the functionality? Based on some recent experimentation I was able to get some fairly complex React UI and behavior out of a pair programing session ... without having a lot of React experience and skill myself. Seemed ripe with potential.

It’s probably a cliche but yes, we’ve been thinking about this.

Re: Show HN: Puck – Open-source visual editor for React

#74

This looks great. I would love to be able to use this to create UIs if it were to support integration with GraphQL data sources.

You can certainly configure it to work with GraphQL if you need to. See this adaptor for an example on how to integrate with external data sources: https://github.com/measuredco/puck/tree/main/packages/adapto...

Re: Show HN: Puck – Open-source visual editor for React

#75
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!

Re: Show HN: Puck – Open-source visual editor for React

#76

How does this compare to https://www.plasmic.app/ ?

Puck is focused on providing a solution for non technical folk to build on-brand web pages with their team’s existing React components. This enables them to build web pages with guard rails that respect their brand guidelines.

Plasmic is a no-code tool for building websites and applications from scratch. A great solution for a different problem.

Re: Show HN: Puck – Open-source visual editor for React

#77

Earlier quoted context omitted.

Framer is a design tool, but Puck is a content tool. We're focused on allowing content teams to create pages using existing on-brand components. Like a WYSIWYG with guard-rails. We built it because we couldn't find something that would let our clients' content teams produce content for their sites without 1) either going off-brand or 2) pestering their devs for layout changes.

Can you elaborate what you mean by "content" tool? Are your ideal users creating marketing sites, blog posts, or other? In my experience, most of what content teams work with are some forms of CMS, and the design tools usually deal with layout and creating generic sites that work with the data structure inside the CMS.

Typically marketing sites and blog posts etc. It could probably be extended to applications, but that’s not what we built it for.

Re: Show HN: Puck – Open-source visual editor for React

#78

Looks neat! Do you consider adding input elements? (forms,wizards..) if so it will be my goto platform!

Puck is for integrating with your existing component library, so not completely no code.

Having said that, a developer could add any type of form input as a type of component!

Re: Show HN: Puck – Open-source visual editor for React

#80

How does this compare to https://www.plasmic.app/ ?

Puck is focused on providing a solution for non technical folk to build on-brand web pages with their team’s existing React components. This enables them to build web pages with guard rails that respect their brand guidelines. Plasmic is a no-code tool for building websites and applications from scratch. A great solution for a different problem.

Hi! I work on Plasmic. Plasmic's most common use case is actually the same one, letting content editors build pages in your existing website using your React components.

Congrats on this release! We are actually open sourcing Plasmic soon, would love to discuss any possible ways to collaborate.

Post reply on HN