Scaffold Laravel Elixir integration when initializing new sites #10
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.
Still a work in progress, but currently:
package.json
gulpfile.json
.gitignore
main.scss
(andmain.css
so fresh sites have no console errors)gulp watch
watches for all changes in thesource
folder and recompiles the site if anything changesNice to haves:
Currently updating an asset file (likemain.scss
) triggers two recompiles because the Sass file changes, which triggers the CSS file to change. It would be nice to avoid this, but it might only be possible by moving precompiled assets out of thesource
folder.source
folder, and instead only compile them into thebuild
folders, so no compiled assets end up in the raw source files.jigsaw serve
that starts a PHP server pointed atbuild_local
and startsgulp watch
.jigsaw build
command that Gulp runs is hard coded, so you can't disable pretty URLs without editing the gulp file. This may or may not be worth addressing, it's pretty easy to edit that file yourself.