- 🇪🇸Spain manuel.adan 🌌
From the project form about the ecosystem field:
Ecosystem
Use this field to indicate that this project's primary purpose is to provide enhancement for one or more other projects, and thus forms part of an ecosystem around it.This module can be used outside of layout builder, actually it was born when layout builder was not yet in core, so moving it into its ecosystem may bring the false idea that the module cannot be used independently.
In any case, I have added a mention about the convenient use in combination with layout builder on the module page:
"It is particular useful in combination with Layout Builder to create simple markup blocks within any configured display."
- 🇪🇨Ecuador jwilson3
The purpose of suggesting this be added to the LB ecosystem category is for discoverability; ie. surfacing the module into more relevant places.
If you look through the list of modules in the Layout Builder ecosystem → , it becomes clear that:
- modules that are LB specific often are prefixed with "Layout Builder" in the module name. So the fact that this module doesn't do that and instead mentions "Block" is already a good indicator that it may be used without LB.
- There are already several Block-related modules that have been tagged for compatibility with LB and others as well, So adding your module would not be unprecedented, even if not technically following the guidelines perfectly.
I suppose technically you're not wrong, so perhaps we should think of "Ecosystem" to be more of a "Compatible with", and update that description you quoted accordingly.