release/0.4.0 #188
Merged
release/0.4.0 #188
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* init commit of Lerna and Yarn Workspaces * package and workspace READMEs * readme tweak * src directory for CLI package * move CLI package index.js * organize specs per package * make smoke test common * refactor path lookup for CLI in smoke test * misc path refactoring * fix circleci script
thescientist13
added
enhancement
* first draft * hooks working * plugins docs overview and site navigation * document template hooks * TODO cleanup * clean up console log * update documentation example * API rename and error handling tests
* working example with testse * error handling * update GA script and specs and integrated into the website * custom plugins page * finish docs * clean up package.json * anonymous IP tracking * add Google SEO meta tag
* unit tests for supporting a webpack plugin in the Greenwood build * documentation * fix spec description * clear up docs example * clear up docs example
* remove polyfills from index.html and use @babel/preset-env for polyfilling * remove polyfills from index.html and use @babel/preset-env for polyfilling * update comments * how it works documentation * switch to postcss preset env * contributing docs for IE11 * fix unit tests * polyfill plugin and refactor greenwood/cli with it as dependency * pull bundle from npm * remove extra preset * comment TODO * update polyfills README * compilation documentation
* polyfill just puppeteer * decouple plugin from cli * dependency refactoring * add polyfill plugin to website * add polyfill plugin to website * formatting * serlialization refactor
* add support for outbound links * apply getOutboundLink to header link
* fix: amending async tasks to use fs-extra and disabling plugins * task: confirm test works again * task: confirm one last time, tests are consistently working * task: one more test for good measure * fix: scaffold async and organization * fix: remove old async/await * fix: ignore plugin tests * fix: revert analytics test skips, readd analytics plugin * fix: use only one instance of puppeteer for all rendering * fix: readd polyfills plugin * fix: remove polyfill debug log * move fs-extra to cli package * dependency cleanup * fix: resolve review issues * fix: additional async * test: readding additional disabled test * fix: removing changes from issue-212 * naming tweaks * change to console error
thescientist13
added
v0.4.0
hutchgrant
reviewed
Oct 12, 2019
www/pages/plugins/webpack.md
Outdated
| @@ -0,0 +1,37 @@ | |||
| ## Webpack Plugins | |||
|
|
|||
| > This is an expiremental API! [YMMV](http://onlineslangdictionary.com/meaning-definition-of/your-mileage-may-vary) | |||
hutchgrant
reviewed
Oct 12, 2019
www/pages/plugins/index.md
Outdated
| @@ -0,0 +1,92 @@ | |||
| ## Plugins | |||
|
|
|||
| At it's core, Greenwood provides a CLI and some configuration options to enable users to develop and build their projects quickly and simply from markdown. However, more complex sites and use cases there will come a need to be able to extend the default functionality of Greenwood to support additional capabilities like: | |||
There was a problem hiding this comment.
At it's core, Greenwood provides a CLI and some configuration options to enable users to develop and build their projects quickly and simply from markdown.
3 ands in that sentence. Could we restructure that while maintaining the same description?
There was a problem hiding this comment.
Yeah, good call. Will take another pass at this one.
* lock down puppeteer request making * test for unexpected tracking files * loosen check
* misc copy text and documentation tweaks * misc copy / docs tweaks
* use webcomponents loader for delivering polyfills * polyfill documentation * caniuse documentation * refactor puppeteer interceptor * fix tests * documentation tweaks * comment clarification
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related Issue
The minimum needed atomic changeset to deliver / release the initial 'Plugins / Packages work.
As this is a release branch, the following branch maintenance should be followed
Summary of Changes
Performance
So there's more JS now because of Google Analytics, but even supporting IE11 the main bundle size went down about 30KB. Once we can decouple the polyfills, evergreen only projects will have a super small initial payload size! I'm expecting to see some pretty good results though from Alpha Testing the Getting Started repo.
Lighthouse score is about the same, but not bad for all around for full browser support down including IE11. 🎉
BEFORE
AFTER
TODO
Evaluate final plugins API (see [RFC] Extensibility - Basic Scaffold Plugins #179) and documentmade an issue for trackingPerformance TestingAlpha Testingalpha.0alpha.1[RFC] Polyfill feature detection: Polyfills plugin should feature detect polyfills support (using webcomponents loader) #9 * (could easily be done as a post release PR)alpha.2Questions / Thoughts
I don't think browserslist is implemented. Should be done as part of Polyfills plugin should feature detect polyfills support (using webcomponents loader) #9? 😬- DONE!Might be good to create a ticket for PWA / Manifest pluginDone PWA Capabality #194Should we deprecate the 404 page? Maybe make it as a plugin?(defer to 404 page not building and serializing correctly #176 )removedefer to <title></title> element is static #128<title>tag in index.html?