[wp-meta] [Making WordPress.org] #7782: Add block-variation detection

[Making WordPress.org]

#7782: Add block-variation detection
------------------------------+---------------------
 Reporter:  carstenbach       |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by carstenbach):

 Replying to [comment:2 dufresnesteven]:
 > I don't know if there's a logical server side way of doing this for
 variations on core blocks.
 >
 > Variations for your custom block, we could easily parse them:
 > https://developer.wordpress.org/block-editor/reference-guides/block-api
 /block-metadata/#variations otherwise ...

 I think and hope we're on the same track here as mentioned in [comment:3
 my previous comment].

 Please help me understand, why you differentiate between variations of
 core blocks and variations of custom blocks? Does this make any difference
 to the user, to the parsing or to the preview? Sorry, I don't understand
 that.

 > I think if we can get users ''into the plugin'' more easily to preview
 using something like playground we can expose these blocks/variations
 directly in the editor. The readme can list the blocks in simple terms,
 and the interactive experience could highlight the blocks and their
 functionality...?

 I like Playground and do & experiment a lot using it, so yes this might be
 a path to go.

 Given that this would need a lot more clicks and loading bars to get to
 the "final" block-variations; this idea should – ''from my opinion'' –
 considered last, if nothing else worked.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7782#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org