-
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
awareness of JAMstack #175
Conversation
maybe it would be good to wait until we have a guide on Netlify deploy and CircleCI on our website? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So thinking out loud, I wonder if maybe instead of the NodeJS block at the bottom (as it may be a little redundant with the webpack where we could mention NodeJS there?), maybe we could make that third section about JAM Stack instead? Or at least mention the serverless element? It already leans that way already a bit...
Just wondering about how best to use that space. Something to consider anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually might move this to the next Project and merge it as part of the next release that would come out of that, since this language might make more sense in the context of actually better "JAMStack-y" like features being in the project (e.g. data in / data out with #115 and #21 , respectively.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some interesting reading to keep in mind as we work towards this project around data in / data out.
- https://www.gatsbyjs.org/docs/adding-app-and-website-functionality/
- https://twitter.com/mxstbr/status/1198915353809698817
Will keep this around and get it in as the last PR of Project 3 / v0.5.0
closing and letting #268 take priority until closer till the end of this project |
Related Issue
N / A
Summary of Changes