There are optimisations that can be made with Gulp. For example, we may want to introduce a file structure such as:
| app
| src
| all app contents from previously discussed dir structure (issue #55)
| dist
//Contents of public folder, only output what the client will see
| js
| img
| css
Everything from src gets ran through gulp and is optimised and minified ready to be used in production in dist. This is something that is vital when it comes to scaling as it makes running an expanding code base far more efficient if any processing is being done on the client end. It is also good industry standard to optimise code before serving to a user.
Doing this also allows us to version track our output files appropriately
There are optimisations that can be made with Gulp. For example, we may want to introduce a file structure such as:
Everything from
srcgets ran through gulp and is optimised and minified ready to be used in production indist. This is something that is vital when it comes to scaling as it makes running an expanding code base far more efficient if any processing is being done on the client end. It is also good industry standard to optimise code before serving to a user.Doing this also allows us to version track our output files appropriately
@PandelisZ to review proposed structure.