Layouts (Templates) and Pages

[thescientist13]

Type of Change

RFC

Summary

Worth thinking about reviewing any DX considerations for Templates and Pages.

Details

Things that come to mind:

1. Templates as custom elements
2. What to do about getTemplate and getBody if anything, now that we HTMLElement SSR support. Does it make sense to have multiple ways to SSR a page?
3. what to do about current API signature ((compilation, page, request)) - Anyway to clean this up?
4. rename getBody -> getPage?
5. rename getFrontmatter -> getMetadata?
6. Should templates be renamed to layouts? Seems more consistent.
7. Evaluate frontmatter and <meta> (a la React helmet)
8. Per evaluate (remove) use of Workers for SSR and prerendering #1088, templates are currently static only for SSR pages, but would be nice to change that - https://github.com/ProjectEvergreen/greenwood/pull/1110/files#diff-036193aa52a1863fc84a1878a4026f259d3605cdc9c0312d3dba861b80b7bb35R199
9. Use <slot> instead of <content-outlet>? Or maybe not?
10. What about custom page extensions, like .ts or .jsx?
11. bundle context plugins for SSR
12. Page level data - in replace of removing getPages / getTemplate along with Data Loading Strategies #952
13. Trailing forward slash (/)
14. APIs in the pages/ directory?
15. refactor Greenwood context, move all things into manifest.json

[thescientist13]

Might be relevant - https://www.reddit.com/r/reactjs/comments/110biur/looks_like_headtsx_is_about_to_be_deprecated_on/