-
Notifications
You must be signed in to change notification settings - Fork 10
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
Progressive Enhancement ("RedactJS") #354
Labels
Milestone
Comments
thescientist13
added
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
RFC
Proposal and changes to workflows, architecture, APIs, etc
labels
May 31, 2020
5 tasks
This was referenced Jul 19, 2020
5 tasks
5 tasks
Should create issue for additional enhancements like:
|
Looking to re-incorporate this as part if #355 because now that we are starting from scratch, we should figure out how to use progressive enhancements (via plugins) to see how we can accomplish this. Should figure out how to enable:
Additional thoughts from #418
Should create issues for additional enhancements like:
|
16 tasks
16 tasks
22 tasks
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of Change
Summary
As part of exploration into #305 and conversations during our recently weekly meetings, it seems like there was something we might have overlooked along the way on this project, and that we designed it SPA first, rather than SSG first. (IMO)
I would like to open this issue to evaluate how efficiently we are shipping / bundling the output of Greenwood. I would like to see if there are ways the minimum bundle size could be mitigated even further. A website shouldn't really need all this fancy SPA magic, at least not by default and in the final bundle.
As much as possible a Greenwood site by default should work without all the JS needed to render the site, and otherwise make it fall back gracefully. JavaScript should be seen as a progressive enhancement opted-into by the user.
Details
We should have at least two modes
HTMLElement
for our core templates?async
/defer
.Vite it a good examples of a project aiming for similar goals
https://twitter.com/youyuxi/status/1265680831625998342
Also this quote I found from somewhere, which I can confirm...
The text was updated successfully, but these errors were encountered: