You should carefully consider how you name your schemas. The name of the schema is visible to all contributors in the CMS, so it should accurately describe how the page, component, or asset will be used in the site.

It's helpful to include a brief note about how the schema ties into the larger context of the site. This is especially important when schemas have similar names. Not only does this provide context when interpreting the spec later, it also serves as a reminder that elements may be required on one schema for use by another schema.

For example, consider a site that needs a profile page for each person profiled, a profile index page to list each person, and a profile rotator component to advertise the profiles throughout the site. When creating the Profile Page schema, it would be helpful to note how it relates to the Profile Index Page and the Profile Rotator Component schemas.