Default block per core field type

[ssyberg]

Perhaps there's already a solve for this, but would be great to include a ready to go block for each core field type such that it would be trivial to add a richText or text field to blocks

[jmikrut]

Hey @ssyberg — this is a great idea! Within our own Payload blocks we've build just about any block config you can think of. They could definitely be of relevance to be shared publicly.

But for many developers, block configs are typically designed specifically to suit the project design—i.e. in our own projects, our blocks are frequently never as simple as just a richText or text field. Instead, they might have other options, like backgroundColor, columns, or similar.

For example, you could take a look at our walkthrough called Building a Professionally Designed Website with NextJS and TypeScript. The resulting project is open source and shows some of the block configs in use to produce that design and specifically the Content block may be of relevance.

Last note - on our Roadmap, we have an item called Improved Blocks UI, which will give developers a way to completely overhaul the entirety of the blocks UI—at which point, we will absolutely be compiling a list of pre-designed blocks for easy reuse by developers. That is going to be awesome.

Keep an eye out and let me know if this makes any sense!