Other sections we may want to add?

[jaredwilli]

There is more to frontend development than just the things currently in this doc. Things that get lumped in with what is viewed as HTML5 for example, which we may want to clarify in this, maybe...

Do you suppose it would be worth adding new sections for other things not included or covered yet?

Proposed ideas for new sections:

• DOM (the file exists and has some content with more to add, but is not included in index.php)
• HTML5 (make separate and clarify what it is http://www.ibm.com/developerworks/web/library/wa-webstandards/index.html)
• Canvas
• SVG
• Staying Productive and Efficient from project to project (like choosing things that are best suited to help increase productivity)

Will add others I am forgetting right now. Other suggestions?
Or perhaps combining existing sections?

Just trying to see what others viewpoints are on this.

[rcherny]

We have a recent list of content here that is potentially worth examining ...

[rcherny]

• Test Driven Development
• Build Systems (e.g. Grunt, etc.)
  • Build systems and preprocessors are a tricky one. Should not be heavy content but brief overviews, IMHO

[jaredwilli]

• Command line tools:
  • scaffolding
  • or at least something that mentions the various options. This may be something that Mac users may be accustomed to anyways, but Windows users should be educated about, or whatever. The cmd line on WIndows has only just recently really become necessary to know and use. It can be a difficult transition in workflow. The cmd prompt is not as versatile or capable as Mac's terminal.

I didn't finish this comment, but for now here's what I wrote.

[rcherny]

I think for most automation tools we're probably going to shy away from doing too much of a deep dive other than some pointers to resources. Their availability and discussing some of the merits and pitfalls might be most appropriate as opposed to claiming "best practices" on their usage.
I think more along the lines of various types of tools and how appropriateness and integration with continuous integration tools and deployment processes, might be an example. So, the right tool for the rigt job, for instance.
One thing we've been struggling with a lot is that much of the advice in the doc is dated or doesn't scale, so a "small", "medium", and "large" approach (along those lines, but not literally in many cases) might work.

Scaffolding can provide consistency so that can be a merit that is noted.

[jaredwilli]

yeah that's pretty much what I meant. the best practices of them is really subjective and would be too opinionated to add in this doc. links, or listing without linking even, what kinds of tools can be valuable and may be necessary to get familiar with even. anything that re-enforces the use of cmd line for windows users specifically i think would be valuable to have at very least.