- 🇨🇦Canada Nathan Tsai
Jacob, this is an incredible system.
Thinking about implementing this for a multi-tenant system we're building.
Let me know if there's any grunt work I can help you with.
- 🇹🇹Trinidad and Tobago xamount
Thanks for this great module! I really appreciate the efforts here! Is there a link to financially donate towards a stable release? Maybe put it on the module's homepage?
- 🇺🇸United States jrockowitz Brooklyn, NY
I will respond to this comment in a way that may one day become a longer blog post.
For the Schema.org Blueprints module, I don't know what the definition of stable will be.
First, one client is sponsoring all my work, and technically, the code base needs to be flexible and stable enough to meet this client's needs. Still, there is a lot of test coverage, and the SchemaDotOrgConfigSnapshotTestBase is intended to help developers catch config changes between releases.
Second, the goal of the Schema.org Blueprints module is simple: build an ideal content architecture based on Schema.org. To do this, we have to keep massaging and rethinking the configuration. Anyone using this module as the foundation for their website needs to be a seasoned Drupal developer who understands that, when installing a free, open-source module, they are responsible for the "cost" of using the free code. Installing an alpha or beta release of software implies that the developer understands the risk and responsibility that they are taking on.
Finally, regarding sponsorship, I am not sure where I stand. With the Webform module, sponsorship is helping me stay and maintain the code. I am unsure if sponsorship with the Schema.org Blueprint module would accomplish the same thing.
I have a secret for those considering using this module while it is in alpha releases. I am writing update hooks to ensure the config and code are in sync to the best of my ability. Furthermore, you can catch any significant changes using the Configuration Synchronizer and the SchemaDotOrgConfigSnapshotTestBase. I encourage you to dive into the code and not be afraid to get your hands dirty. If you are committed to this module and its approach, don't hesitate to reach out in Drupal Slack, ask questions, and even contribute code. Your involvement is crucial to the development and success of this module.