Support for dynamic blocks

[tylercherpak]

Let me start by saying this is amazing! Really digging this. 😄

Have you thought about support for dynamic blocks? I was thinking that if given the correct api endpoint you should be able to pull the markup for the block from the api?

Would love to know what you think! Thanks!

[youknowriad]

Thanks for the kind works.

Yes, so or me, this should remain a static tool without any backend. That said, I think mocking APIs can allow us to support most dynamic blocks. API mocking is easy, we just need to document it properly.

I'd consider this a duplicate of #3

[fabiankaegy]

@youknowriad How do you feel about adding a native way to add your own "Tabs" to the Block page? So that if someone would want to extend the blockbook with their own things like in this case hooking it up to talk to the wp rest api they could use a slot fill system like within Gutenberg to add things to it?

https://github.com/WordPress/gutenberg/blob/bed7e0c6a6dff04409c883a0cf7f00fa6560b2db/packages/components/src/slot-fill/README.md

Or allowing to use filters like when you extend core blocks?

[youknowriad]

How is "dynamic blocks" related to "custom tabs"?

[fabiankaegy]

If this package should remain a static tool. Which I get your reasoning for :) I think it would be really cool if there is the ability to extend the blockbook so people who would want to hook the blockbook up to also show a "Rendered" tab have that possibility.

The custom tabs would be useful for much more that that. This just made me think of it :)

[youknowriad]

My question is what tabs do you want to add there?

Because it's already possible to mock APIs and render dynamic blocks in the current tabs. I want to understand the use-case exactly.

[fabiankaegy]

Honestly one of the use cases I'm thinking of is allowing other developers to try out things before merging into the main package. Allowing extensibility rather than just the ideas you or I can come up with might be cool :)

And the things that come to mind are adding trining / documentation / use case sections in there. Styleguides walkthroughs etc :)

[fabiankaegy]

I can imagine this tool being uses as the main bridge between design, engineering and even clients to share information. So everything that you can think of in that interaction paradigm would be very cool :)