Simple Block "No Further Development" about example-drops-8-composer HOT 6 CLOSED

Totally get it... I don't know the reason "why" they decided to abandon it yet. I personally don't need another project :p just thought I would flag this JIC

from example-drops-8-composer.

Ah, bother. I was using this as an example because the way it stores blocks as config made it much easier to manage static blocks than the Drupal core code, which stores some info in the database and some in config. That makes it more difficult to do the "push config up, pull database down" dev/test/live workflow.

If anyone has a suggestion for a better way to manage blocks (esp wrt block configuration), a PR would be most welcome.

from example-drops-8-composer.

Assigning to myself to remove simple_block

from example-drops-8-composer.

See #221

@greg-1-anderson I think it makes sense for some sites to do Block content as config (rather than content) but I don't think that's a preference we need in this example repo since it goes against what Core does.

from example-drops-8-composer.

Core is doing it wrong, though. It would be better if we provided a solution rather than just let everyone run into this core limitation. I won't stand in the way of removing the unmaintained module, though.

from example-drops-8-composer.

Merged! Thanks for the reviews @greg-1-anderson.

from example-drops-8-composer.