Skip to content

doc(review)athon #244

Description

@egamma

Goals

  • check the doc for accuracy
  • add missing tips
  • add new contents if appropriate

Guidelines from @gregvanl

  • 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.

Coverage

Editor

Customization

Languages

Runtimes

Extensions

Extensbility Reference

Tools

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions