universityofnottingham / gulp-boilerplate Goto Github PK

As with the CSS standards, add the javaScript coding standards to this repo so they can be evaluated alongside an eslint config and a sandbox to test.

Make an SVG sprite from a folder of individual SVGs to be used in place of an icon font.

Include browsersync on the watch task, with examples of proxying local urls and injection of assets as they're built or updated.

Suggest keeping this open for a bit so we can add inconsistencies, and then review what we do about it once we have a decent picture.

Stuff I've found so far:

• VS defaults to 4 spaces for tabs in .scss files
• Resharper prefers double quotes to single quotes

• Build JavaScript from modules using Browserify
• Uglify JavaScript
• Use eslint to enforce coding standards

The paths won't work as is, so we'd be reconfiguring per-project (but the same everytime)?

I suppose the easiest (but a faffy) way would be to leave everything as is and add a task to copy the built files to an asp.net core output path after? e.g. wwwroot/css

But obvs it'd be less silly to just set the output to that instead of copying afterwards.

It'd also be preferable to have a difference source path - while we can put our sass in ./src/sass relative to the gulpfile, there will be other source outside ./src so it seems a bit disingenuous to me.

Is there a nice way the paths can be more configurable?

There are cases where it's necessary to use responsive breakpoints in JavaScript as well as in CSS media queries.

In this case it makes sense to keep these in a JSON file and use a gulp task to create a SASS map from this data.

Once JavaScript coding standards have been agreed, add linting to enforce them.