Build playgrounds for gh-pages #755
Conversation
Sets up the necessary structure in the gh-pages directory to run the uncompressed playgrounds. Deploy the gh-pages directory to the gh-pages branch after publishing to NPM.
|
How about instead of copying the current playground create a compressed playground that uses the dist importable modules to make the playground more compact. |
| # Publish to gh-pages as most recent committer | ||
| git config --global user.email $(git log --pretty=format:"%ae" -n1) | ||
| git config --global user.name $(git log --pretty=format:"%an" -n1) | ||
| npm run --silent deploy -- -x -r https://${GH_TOKEN}@github.com/${TRAVIS_REPO_SLUG}.git |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
|
@TheBrokenRail: the playgrounds attached to Scratch 3.0 repositories are intended for a few purposes: they demo the project or module, but they also offer a place to debug and learn about that module through live tinkering. Your suggestion would potentially benefit people who are interested in using the playground as a demo, especially if they're in an environment where downloads are slow or expensive, but would likely make debugging and learning about the module more difficult. |
Rebuild Blockly.
Sets up the necessary structure in the gh-pages directory to run the uncompressed playgrounds. Deploy the gh-pages directory to the gh-pages branch after publishing to NPM.
Adds a landing page at the root to go to the horizontal and vertical playgrounds. Everything in
testsis available under/playgrounds/tests/though.