|
|
|
|
|
by chrisvxd
1024 days ago
|
|
Thanks! It’s possibly I’m misunderstanding, but I believe Puck is a different problem space to the other solutions you’ve mentioned - Puck enables content teams to produce web pages using existing React components produced by their React developers in a fixed and predictable manor that keeps them within the brand guidelines. You can’t inject arbitrary blocks and can only interact with components that are defined by your developers. You can render fully fledged pages or even, in theory, applications. Regarding content, Puck supports inline editing or pulling in data via an API adaptor (such as from a headless CMS). We don’t have a rich text field type currently, but I’m not opposed to adding it. (Internally, we’ve added a markdown component to enable some basic formatting and longer form content: https://github.com/measuredco/measuredco-site/blob/02fc908b8...) |
|