doc(review)athon #244

egamma · 2016-03-23T07:40:56Z

Update the docs in vscode-docs vnext branch.
- You can commit directly and don’t need to create pull requests.
- You can be pretty fast and loose and I’ll follow up with an extensive edit and formatting pass afterwards.
Write the content targeting the March release.
- For walkthrough flow, use the new features available in 0.10.12 (e.g. jsconfig.json creation, tasks.json dropdown, jsconfig.json autoload,etc).
- Focus on likely user scenarios and workflows. Corner cases or less used features can be called out in the Common Questions section at the end.
- If you find that you are adding a lot of Tips and Tricks which interrupts a topic’s flow, consider adding a Tips and Tricks section at the bottom of the topic.
Try to use separate commits for separate changes and docs.
- This will make it easier to cherry pick commits that we want to move to master before we merge vnext at the 1.0 release.

Overview
- @egamma
JavaScript
JavaScript example on github https://github.com/jrieken/es6-vscode-sample
- @jrieken - removed the reference to the sample
C#
- @jrieken
JSON
- @aeschli
HTML
- @aeschli
PHP
- @alexandrudima
- @aeschli
Markdown
- @bpasero
- @dbaeumer (generation of HTML using tasks)
TypeScript
- @dbaeumer
- @jrieken
CSS, LESS, SAA
- @aeschli
Dockerfile
- @alexandrudima

gregvanl · 2016-03-30T01:02:16Z

Boxes all checked.

egamma mentioned this issue Mar 23, 2016

March Iteration Plan microsoft/vscode#3555

Closed

82 tasks

egamma added this to the March 2016 milestone Mar 23, 2016

gregvanl closed this as completed Mar 30, 2016

Provide feedback