I mentioned what I think is the same idea a while back, it’s similar to something Coda can do, and Michael said it should be “easy” to implement, so hopefully it comes around!
I know Michael addressed this, but in case there is remaining confusion, my understanding is that Blocks will be arbitrary units of content/functionality, and will not have to be consistent from entity to entity, thus they do not involve creating “fields”. They are a more “lightweight” solution than formalized Type modifications, i.e. new Fields. Perhaps that is a more direct/succinct answer to the root of your question/concern.
Think of them like blocks in Notion, simply individually manipula…
Also possibly related (read through the thread, hopefully you’ll see the connection):
This is obviously related to the [IN DEV] Migrate Entity View to Blocks but thought it might be worth it to keep it separate.
One of the things that I hope would be baked into the foundation of the blocks is ability to define inputs and outputs into a block. I assume the block types in the first iteration would be very basic and probably static (text, bullets, views with hardcoded filters, etc.) . However, in the long run, I would hope that we will have more dynamic blocks available (perhaps so…
3 Likes