Review existing content to make sure all topics are covered

[vansimke]

This reference guide article should describe the tools that are available to streamline the developer experience and how to work with them. Examples of topics are source maps, introspection, ....

[vansimke]

There is a reference to this article in the fifth tutorial

[devpaul]

This is separate from #112 and #13 in that it focuses on the developer tools used by dojo and tools that can make development easier. Tools and topics worth mentioning are:

• typing (@types, local ambient declarations)
• build tools (dojo-cli, webpack, postcss, TypeScript)
• debugging (source maps)
• testing (intern)
• dev server (webserv)
• code coverage (intern/istanbul)
• CI (travis/appveyor)

dojo-cli tools are covered in previous tutorials so their mention should be in relation to how the cli tools work w/ other tools.

[vansimke]

@devpaul this is exactly what we need with this article. The only thing I would caution is to not go too deeply into the testing topic. We will have a tutorial on that later (you can put in a "comingsoon" for now). Maybe put a small example in that section and point to the dedicated tutorial for learners that want more information.

[devpaul]

Perfect. I'll focus on Intern features more and less on concrete examples. I plan to mention it can handle unit, functional, integration, a11y, visual regression, and benchmarking as a nudge to "hey, maybe check out Intern" :)

[devpaul]

WIP https://github.com/devpaul/dojo.io/blob/dev-tools/site/source/_drafts/Development-tools.md

[morrinene]

Updated task topic, changed goal

• Review the existing content, make sure it's covered
• Create new issues for topics not covered yet
• Add additional information (or submit PRs) for existing tutorials/articles

[kitsonk]

Let's figure out what it will take to close down this issue.