Merge pull request #927 from microsoft/715305_OSS

updated readme

Author: bharney0

README.md

@@ -1,75 +1,15 @@
-🚨 This project is archived and will no longer be publicly maintained. 🚨
-
 # vscode-docs-authoring
 
-This repo contains code for the Docs Markdown VS Code extension, which provides Markdown authoring assistance for contributing to docs.microsoft.com. The Docs Markdown extension ships in the VS Code Marketplace, either as an [individual extension](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-markdown) or bundled with other useful extensions as part of the [Docs Authoring Pack](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-authoring-pack).
-
-The Docs Authoring Pack also includes [markdownlint](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint), a popular linter by David Anson, and [Docs Preview](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-preview). The Docs engineering team is now extending markdownlint to catch issues in custom Docs Markdown, starting with the `zone` and `monikers` extensions. More custom linting is coming soon!
-
-## Prerequisites and Assumptions
-
-To accurately insert relative links, images, and other embedded content with Docs Markdown, you must have your VS Code workspace scoped to the root of your cloned OPS repo. Some syntax supported by the extension, such as alerts and snippets, are custom Markdown for OPS, and will not render correctly unless published via OPS.
-
-## How to Use the Docs Markdown Extension
-
-To access the Docs Markdown menu, type `ALT+M`. You can click or use up/down arrows to select the function you want, or type to start filtering, then hit `ENTER` when the function you want is highlighted in the menu. The following are available:
-
-|Function     |Command             |Description           |
-|-------------|--------------------|----------------------|
-|Bold         |`formatBold`        |Formats text **bold**.|
-|Italic       |`formatItalic`      |Formats text *italic*.|
-|Code         |`formatCode`        |If one line or less is selected, formats text as `inline code`.<br><br>If multiple lines are selected, formats them as a fenced code block, and allows you to optionally select a programming language supported by OPS.<br><br>If no language is selected, inserts an empty fenced code block.|
-|Alert        |`insertAlert`       |Inserts a Note, Important, Warning, or Tip.<br><br>Select Alert from the menu, then select the alert type. If you have previously selected text, it will be surrounded with the selected alert syntax. If no text is selected, a new alert will be added with placeholder text.|
-|Numbered list|`insertNumberedList` |Inserts a new numbered list.<br><br> If multiple lines are selected, each will be a list item. Note that numbered lists show in the Markdown as all 1s, but will render on docs.microsoft.com as sequential numbers or, for nested lists, letters. To create a nested numbered list, tab from within the parent list.|
-|Bulleted list|`insertBulletedList` |Inserts a new bulleted list.|
-|Table        |`insertTable`        |Inserts a Markdown table structure.<br><br>After you select the table command, specify the number of columns and rows in the format columns:rows, such as 3:4. Note that the maximum number of columns you can specify via this extension is 5, which is the recommended maximum for readability.|
-|Link         |`selectLinkType`      |Inserts a link. When you select this command, the following sub-menu appears.<br><br>`Link to file in repo`: Insert a relative link to another file in the same repo. After selecting this option, type in the command window to filter files by name, then select the file you want. <br><br>`Link to web page`: Link to a web page by URI. Must include "http" or "https".<br>`Link to Docs page bu URL`: Converts an absolute URL to a page on docs.microsoft.com or review.docs.microsoft.com to a relative link. You should use relative links when linking to other Docs pages so that links are validated in build and aren't broken when published to isolated environments. <br>`Link to heading`: Choose a heading in the current file or in another file.<br>`Link to Xref`: Add a cross-reference link by UID, such as a link to API reference documentation.<br>`Generate a link report`: Generates a report of broken links in the current repo.|
-|Image        |`insertImage`     |Type alternate text (required for accessibility) and select it, then call this command to filter the list of supported image files in the repo and select the one you want. If you haven't selected alt text when you call this command, you will be prompted for it before you can select an image file.|
-|Include      |`insertInclude`   |Find a file to embed in the current file.|
-|Snippet      |`insertSnippet`   |Find a code snippet in the repo to embed in the current file.|
-|Video        |`insertVideo`     |Add an embedded video.|
-|Preview      |`previewTopic`    |Preview the active topic in a side-by-side window using the DocFX extension.  If the DocFX extension is not installed or is installed but disabled, the topic will not render.
-
-## How to Assign Keyboard Shortcuts
-
-1. Type `CTRL+K` then `CTRL+S` to open the Keyboard Shortcuts list.
-1. Search for the command, such as `formatBold`, for which you want to create a custom keybinding.
-1. Click the plus that appears near the command name when you mouse over the line.
-1. After a new input box is visible, type the keyboard shortcut you want to bind to that particular command. For example, to use the common shortcut for bold, type `ctrl+b`.
-1. It's a good idea to insert a `when` clause into your keybinding, so it won't be available in files other than Markdown. To do this, open keybindings.json and insert the following line below the command name (be sure to add a comma between lines):
-
-    `"when": "editorTextFocus && editorLangId == 'markdown'"`
-
-    Your completed custom keybinding should look like this in keybindings.json:
-
-    ```json
-    // Place your key bindings in this file to overwrite the defaults
-    [
-        {
-            "key": "ctrl+b",
-            "command": "formatBold",
-            "when": "editorTextFocus && editorLangId == 'markdown'"
-        }
-    ]
-    ```
-
-1. Save keybindings.json.
-
-See [Keybindings](https://code.visualstudio.com/docs/getstarted/keybindings) in the VS Code docs for more information.
-
-## How to Show the Legacy Toolbar
-
-Former users of the extension code-named "Gauntlet" will notice that the authoring toolbar no longer appears at the bottom of the VS Code window when the Docs Markdown Extension is installed. This is because the toolbar took up a lot of space on the VS Code status bar and did not follow best practices for extension UX, so it is deprecated in the new extension. However, you can optionally show the toolbar by updating your VS Code settings.json file as follows:
-
-1. In VS Code, go to File -> Preferences -> Settings (`CTRL+Comma`).
-1. Select User Settings to change the settings for all VS Code workspaces, or  Workspace Settings to change them for just the current workspace.
-1. In the Default Settings pane, find Docs Authoring Extension Configuration, click the pencil icon next to the desired setting, and select `true`. VS Code will automatically add the value to the settings.json file and you will be prompted to reload the window for the changes to take effect.
-
-## Known Issues
+This repo contains the Learn Authoring Pack VS Code extension, which is an extension pack containing multiple Markdown and YAML helper extensions. The main goal is to provide authoring assistance for contributing to learn.microsoft.com. This repo is our feedback mechanism allowing the community to report issues. We are not accepting outside contributions, but would like to continue improving the existing extensions supported in the Learn Authoring Pack.  
 
-- [External bookmarks] Linux: File list is displayed but no headings are shown to select.
-- [Includes] Linux: File list is displayed but no link is added after selection is made.
+# Docs Authoring Pack
 
-## Contributing
+The Docs Authoring Pack provides a series of extensions to help docs.microsoft.com authors work better and more efficiently. You can read more about all of the Docs Authoring Pack features here in the [overview guide](https://docs.microsoft.com/en-us/contribute/how-to-write-docs-auth-pack). The Docs Authoring Pack provides the following extensions to help author content for docs.microsoft.com:
 
-Please see the [Contributors Guide!](contributors.md)
+- [Docs Markdown](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-markdown), which provides Markdown authoring assistance, including support for inserting custom Markdown syntax specific to docs.microsoft.com. The rest of this readme provides details on the Docs Markdown extension.
+- [Docs Preview](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-preview), which uses the docs.microsoft.com CSS for more accurate Markdown preview, including custom Markdown.
+- [Docs YAML](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-yaml), which validates Docs .yml files against the appropriate YAML schemas.
+- [Docs Images](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-images), which compresses and resizes images.
+- [Docs Article Templates](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-article-templates), which allows users to apply Markdown skeleton content to new files.
+- [Docs Scaffolding](https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-scaffolding), which automatically generates Learn modules based on standard patterns and automates renaming, inserting, deleting, and reordering units.
+- [markdownlint](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint), a popular linter by David Anson.