-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] External Data (Graph) Sources #21
Labels
CLI
Content as Data
documentation
Greenwood specific docs
feature
New feature or request
RFC
Proposal and changes to workflows, architecture, APIs, etc
v0.21.0
Milestone
Comments
thescientist13
added
the
RFC
Proposal and changes to workflows, architecture, APIs, etc
label
Mar 27, 2019
I think if we were to get a working example, we could officially consider our project JAMStack friendly, and should probably add that to the README / website home page. |
5 tasks
5 tasks
4 tasks
This was referenced Oct 16, 2019
5 tasks
5 tasks
5 tasks
thescientist13
added
CLI
Content as Data
documentation
Greenwood specific docs
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
labels
May 3, 2020
This was referenced Apr 4, 2021
thescientist13
changed the title
[RFC] External Data Sources
[RFC] External Data (Graph) Sources
Apr 24, 2021
This was referenced Aug 3, 2021
For incoming content / data, not sure if we would want to account for some sort of DOM validation / purification? ex. Or at least make sure user's can apply it themselves through our plugins. |
7 tasks
thescientist13
added
feature
New feature or request
and removed
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
labels
Dec 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CLI
Content as Data
documentation
Greenwood specific docs
feature
New feature or request
RFC
Proposal and changes to workflows, architecture, APIs, etc
v0.21.0
Type of Change
Summary
Need to figure out a way to pull in external data at build time and pull it in a build time. First POC should likely be with Wordpress. (Greenwood blog?)
Details
I think it should be pretty straight forward, expose a "Graph" Plugin type that gets read on build to extract the metadata and then just serves the route as any other would?
From there, other plugins could be built around that in follow up PRs, like for WordPress or Sanity support.
The text was updated successfully, but these errors were encountered: