Developers have validated and created the Pub Type for “Pages” (Legacy & Responsive Journal)

[gabestein]

Following from the relationships card, pages are a pub type that have a sibling relationship to sites.

Why

• Support the KF website!
• Support eLife contract
• Support Legacy to Platform migrations

Open Questions

• Are pages and collections actually the same and this is just a generic type? E.g. is a "book" actually what we want to use as a page? How do we tell a site builder to render the contents of something that has a type "chapter"?
• How do we query for pubs within page blocks? Do you need to create relationships to do this or is there some special pub-querying pub field?
• How do we structure blocks? Two options, both of which aren't perfect are:
  • Blocks are fields with complex schemas that have custom editors. This requires us to invent a way to have repeated fields on Pubs. Maybe a thing we need anyway?
  • Blocks are child pubs with less complex schemas. This potentially makes our ability to build custom editors harder, but preserves a simpler schema structure.