Repository navigation
I built a side-by-side block editor for Payload. Feedback and testers welcome. #16561
Replies: 3 comments 2 replies
|
This is a genuinely interesting direction for improving Payload’s editing experience, especially for content-heavy projects. One of the biggest pain points with deeply nested block structures is the disconnect between the form representation and the actual rendered page layout. Once pages start using rows, tabs, accordions, reusable blocks, or complex compositions, the default stacked admin form becomes difficult to navigate efficiently. The side-by-side synchronization approach solves a real usability problem rather than just being a visual enhancement. A few things that stand out technically:
One thing that would make this even stronger long-term would be handling performance carefully for very large documents:
because real-world Payload projects can easily reach hundreds of nested fields/blocks. Overall, this feels less like a small plugin and more like a meaningful editor UX layer on top of Payload’s existing admin system. Definitely a promising direction. |
|
Looks really cool! |
|
Do you know if it can be tested on payload 4 beta ? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone,
I spent the last couple of weeks building a new Payload plugin:
payload-better-editor.Quick context: Payload's default edit view is fine for small pages, but once a page grows (lots of blocks, or nested ones like rows, columns, tabs, accordions inside accordions), the form turns into a long collapsed list and you lose track of which row maps to what on the actual page. Live Preview helps, but it only shows you the result.
Back in February I built
payload-better-previewas a first attempt. It synced the admin form and the preview both ways: hover a block to see it highlighted, click a block in the preview to scroll its row in the form, click a row to scroll to the block. Nice for navigation, including nested and Lexical blocks. Still felt like a band-aid, since you were scrolling through the same long form.Eventually I wanted something different: an editing surface where the preview is the canvas and the fields sit in a sidebar next to it. That became
payload-better-editor.What it does
RenderFields, so custom components, validation, access control and conditional logic all just workFeedback is very welcome.
I only tested it on my own projects so far where it ran well, but real-world testing across more varied setups would help a lot. Bug reports, missing features, "why didn't you just X", all welcome. If you find it useful, a star on the repo would be really nice too.
All reactions