See Microsoft Open Source Code of Conduct.
Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License (see LICENSE), and grant you a license to any code in the repository under the MIT License (see LICENSE-CODE).
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft general trademark guidelines can be found at Microsoft Trademark and Brand Guidelines.
Privacy information can be found at https://privacy.microsoft.com.
Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.
This repo, edge-developer, is the repository for the source Markdown files for the Microsoft Edge Developer documentation. The resulting rendered documentation is hosted at Microsoft Edge documentation. This repo also includes the hub page for the Microsoft Edge Enterprise documentation and the Microsoft Edge Developer documentation. The source files for the Microsoft Edge Enterprise documentation aren't in this repo, but are in the Edge-Enterprise repo.
If you want to include new coverage or have feedback, consider contributing. You can edit the existing content, add new content, or report new issues. The Microsoft Edge team reviews a look at your suggestions and works to incorporate the suggestions into the docs.
For the latest implementation status and future plans for web platform features in Microsoft Edge, see Microsoft Edge Platform Status. For the data that's used to populate the above status site, see https://github.com/MicrosoftEdge/Status.
-
When adding a webpage (an article implemented as a .md file), you must add an entry for the new webpage in toc.yml, for the article to appear in the Table of Contents.
-
A directory can contain more directories or
readme.mdfiles. -
Folder/directory names are dash-separated (for example,
f12-tools) and lowercase. Directories are used in URLs on thelearn.microsoft.comsite. Avoid using underscores, PascalCase, or camelCase.
- Basic writing and formatting syntax - GitHub Flavored Markdown, in GitHub Docs.
- Docs Markdown reference - in Docs Contributor Guide.
This repo uses Markdown image tagging. See Images.