Use Schema.org Blueprints to manage the data architect

[damienmckenna]

The Schema.org Blueprints module is amazing and should be used as the foundation for building the system's data architecture, rather than doing it piecemeal.

[phenaproxima]

Can you elaborate on that, or submit a PR? What did you have in mind?

[damienmckenna]

From the project page:

The Schema.org Blueprints module takes a Schema.org-first approach to building content models and structured data in Drupal that is standardized, easy-to-understand, and maintainable.

Every organization, website, and application has established different ways of structuring, defining, and documenting its content and data, this makes it challenging and difficult for them to share content. The Schema.org Blueprints module builds content models that are standardized, reusable, and easily shareable. The Schema.org Blueprints module uses the public Schema.org specification to create content types, fields/properties, and relationships that machines, developers, and search engines understand.

I thought it would be worthwhile using it as the foundation for building all content types and vocabularies.

[jrockowitz]

There are a few possible approaches for integrating Schema.org into Starshot.

First, we could adopt the approach that the content model should be based on Schema.org types and properties and not use the Schema.org Blueprints module. The Schema.org Blueprints module could be a recommendation for advanced content modeling.

Second, the Schema.org Blueprints is comprised of many submodules and integrations. We could take a subset of the core Schema.org Blueprints module with key integrations for things like Smart Date, Field Group, Pathauto, Type Tray, etc…

Lastly, we could go all-in with the Schema.org Blueprint module and recommend it as the foundation for future websites built in Drupal.

For my organization, we are using the Schema.org Blueprint module as the foundation for our website.

A few challenges with using the Schema.org Blueprints module in Starshot.

• Requires an understanding of and commitment to Schema.org
• There are many default and customizable configuration settings required to integrate Schema.org into Drupal, ensuring that the Schema.org types and properties can be used to create sensible content entities in Drupal. This could be difficult for newcomers to understand.

It could make sense to decide what the OOTB features in Starshot are and then determine what the OOTB content types and use cases are. At that moment, we could discuss the Schema.org Blueprints module.

By the way, I seldom turn down an individual or organization's request for a one-hour demo of the Schema.org Blueprints with Q&A if they want to learn more. For Starshot, I could do a demo, and we can record and post the discussion here.

[simesy]

Can someone demonstrate/screenshot the current standard profile in the language of schema.org? I ask this naively, because a modelling tool should be accessible all people in cross-functional team, so I assume the OOTB drupal content model should be easy.

[simesy]

As for adding a module, I'm skeptical but I would review a PR for sure where i could go in and see a compelling example of the basic model so far.

[sinyayadynya]

It could be super powerful to mix the Schema.org Blueprints with Themr Components and https://www.drupal.org/project/themr.

If never heard of it, please have a loot at this demo: https://www.youtube.com/watch?v=NEtsYDzeq-g