Template Files
##Physical templates requirements and action plan
All primary template files require a first pass to initially ensure uniformity of markup where possible
All primary templates require a first pass ID & class token review - removing any obviously bad ones and ensuring those semantic ones that we should keep are replicated where necessary on similar elements.
Review elements attributes where elements are known to feature behavioural action and add provisional date atts data-script-element="" data attributes have been started of by imath, so are in use and examples to follow
do_actions are agreed for review, remove all?
1 Basic first pass cleanup
2 Second pass tokens and do_action review/removal
3 Third pass data atts
Work flow:
First & second passes to be attended to by one developer tasked to do Having completed a initial pass these task to be opened to a one week discussion period for thoughts view on suitability or addition of markup and tokens/data atts.
HTML5 How far do we want to use HTML5?
Whereas many templates, sites, frameworks seemingly use html5, most do so in a very lose fashion and given it is still in very much draft mode with RC not expected until something like 2020, using some elements and atts is not safe, as subject to change.
An example usage thus far is taking the object-nav dir nav instances of ul and converting to be <menu>
While this has been done it's not necessarily feeling right.