Inconsistencies and comments

[jausions]

Interesting read. Couple of comments though:

• Some links aren't working (at least for me): "View Github Repo", "View Front End Testing Strategy Documentation", "View Front End Workflow Documentation", "Download Boilerplate".
• Althought SCSS was selected, almost everywhere else SASS is referenced and/or mentioned.
• I didn't see anything related to semantic, i.e. h1 vs. span class="head-title"
• Chosen BEM syntax needs a bit of clarification in regard to separators that should be used in class names (block nesting, attributes, etc...)
• No mention of preferred JS libraries, except for Modernizr. For instance, forbid Prototype, recommend jQuery, or anything goes?

[BenjaminRCooper]

Hi @jausions

Thanks for your comments, it is much appreciated.

Please find my comments below;

• Apologies for this, I havent updated the links and also some of the documentation which will be linked too is not yet available. If you require any information about any of the sources which the links go too, all can be found in this repo.
• With SCSS being a subset of Sass, I don't feel it is necessary to state SCSS everywhere. Sass encapsulates both the Sass and SCSS syntax. This is a good point and we want to minimise confusion, so I will speak with the guys.
• With regards to semantics, I feel it is too big/controversial of a subject to cover in the standards and this is more suited for another type of document. Using semantic elements is certainly important, but there are occasions where it is unnecessary or elements are used in the wrong way.
• Our BEM approach doesn't really differ from the approach proposed on the BEM site. I think the resources provided are enough to give people an understanding, as well the starting template which we are going to launch as version 1.0 of the boilerplate.
• This will be introduced in a seperate document, these standards are part of a large project in which the Front End Team will produce various documents for workflows, testing strategy and others in order to have a streamlined process which we can use across the organisation.

With regards to this process, if you would like to get involved, please let me know and it is fantastic to get feedback from yourself.

Thanks,

Ben

[BenjaminRCooper]

Closing as no reply has been received and all detail has been added