solved the need for 'gulp sass', restructured the directories and added an alternative gulp only build

[patmuk]

An update:
In my latest code I changed the build to integrate gulp tasks and even to have a nom-only build without gulp.

Well, it turns out that your initial setup (metalsmith only) is fastest.
But theoretically the gulp combination should be faster, because it does things in parallel.
The idea is: All set of files, which can be processed individually, should have an own gulp task.
I am sticking with this in my latest code.

The npm only build (as it is trendy now, because it eliminates wrapped plugins) turned out to be 2-3 times slower! I assume this is because each npm script execution has a ramp-up time.

Thought that might be interesting to you :)

Hey,

I made mayor changes, to speed up the build and make the structure clearer.

This fixes the need to run gulp sass before node .

The directory now has a clear separation of source files (in /src) and built files (generated to /build).

As an alternative to node . gulp can be used now. This is faster and more flexible.

Additional minor changes:
I added:

• metalsmith-browser-sync (starts the compiled pages in a browser window)
• metalsmith-debug (logs what is going on in metalsmith - metadata, files, etc, some plugins as well)

Best,

Patrick