The plan
Serve both our React JS bundle(s) remotely as well as the accompanying CSS. Serving these remotely could speed up the loading of the React bundle on sites, decrease load on hosts, allow for bug fixes without the need for a point release (also decreasing load on hosts), and allow for us to make/undo changes depending on feedback from the people using Jetpack.
Requirements
Project management
We may use one of these new fangled Github projects to manage this. I'll leave that decision up to those assigned to work on this task.
Designs
TBD. We need to design a way for people to opt out (or in). It's probably going to be a setting somewhere. shudder
.
updated Wed Oct 26 17:01:07 PDT 2016
♜ ♞ ♝ ♛ ♚ ♝ ♞ ♜
♟ ♟ ♟ ♟ ♟ ♟ ♟ ♟
… … … … … … … …
… … … … … … … …
… … … … ♙ … … …
… … … … … … … …
♙ ♙ ♙ ♙ … ♙ ♙ ♙
♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
♚'s turn.
The plan
Serve both our React JS bundle(s) remotely as well as the accompanying CSS. Serving these remotely could speed up the loading of the React bundle on sites, decrease load on hosts, allow for bug fixes without the need for a point release (also decreasing load on hosts), and allow for us to make/undo changes depending on feedback from the people using Jetpack.
Requirements
Project management
We may use one of these new fangled Github projects to manage this. I'll leave that decision up to those assigned to work on this task.
Designs
TBD. We need to design a way for people to opt out (or in). It's probably going to be a setting somewhere. shudder
.