Boilerplate Directory Structure

[BenjaminRCooper]

No description provided.

[BenjaminRCooper]

Want to add that G has asked we do not make any files dependent of the parent directory due to the occasions when we have various versions of landing pages etc.

[markgoodyear]

Any ideas for a directory structure yet?

Currently I'm using:

• project/ — parent
  • dist/ — distribution files, for deploying
  • node_modules/ — node modules for Grunt
  • src/ — source files, such as Sass and JS files to be concatenated + minified
  • .editorconfig
  • .gitignore
  • .jshintrc
  • Gruntfile.js
  • package.json

You'd then deploy dist/ so any src/ files—such as Sass files—aren't uploaded to the server. The stuff in the parent dir is needed in the parent dir (I believe), however these files shouldn't need any changes. If the Gruntfile.js does need to be tweaked for a different version of the project, that should be handled nicely with branches shouldn't it?

[BenjaminRCooper]

Directory structure is basically what you have specified above mate, its within the boilerplate branch.

The Grunt File should not need to change, as long as we don't reference the parent directory.

B

[markgoodyear]

Awesome.

What do you currently do about images? I've got images in the src/ folder, which Grunt then compresses them to the dist/ folder. Is that something to add into the boilerplate at some point?

[BenjaminRCooper]

Exactly that mate was our approach too :)

Just want to take a closer look at some of the compression tools for performance and quality purposes first, but thats a different issue altogether.

B

[BenjaminRCooper]

Reopened to discuss for the boilerplate the Front End team are currently working on

[BenjaminRCooper]

I suggest we change this directory structure slightly, in that we change 'dist' to 'public'.

Just seems like most frameworks these days come with a public directory which files are served from and it makes sense for consistency purposes.

Thoughts?

Ben

[grahammorley]

+1. I like the clarity of 'public'.