Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This work-in-progress PR introduces the concept of a “page loader”, which is like a data loader for pages: it allows you to generate a page dynamically rather than being limited to static Markdown. The purpose of page loaders is two-fold. First, it serves as a foundation for server-side rendering #931. Second, it allows pages to be written in languages other than Markdown, such as JSX/MDX #971.
There’s still quite a bit to figure out here, but the general idea is to replace this sort of code:
with something more generic:
whereby the user can write whatever logic they like to generate the page.
TODO
hello-world.page.js
?)Presumably this could be extended to support patterns or parameterized paths, like data loaders, so maybe there would be a generic way to register support for
.mdx
,.html
, or.jsx
extensions for the entire project rather than each page having a distinct loader (such asindex.page.js
).