Office Scripts documentation

Welcome to the Office Scripts documentation repository. In this repo, you can find the documentation source files for Office Scripts tutorials and how-to guides. For the best experience, we recommend you view this content on Microsoft Docs.

NOTE: You can find the reference documentation source files for the Office Scripts API in the office-scripts-docs-reference repository. These APIs contain all the potential operations for your scripts.

Give us your feedback

The goal of the repo is to provide developer education about Office Scripts. As such, issues should pertain to that educational content. Please submit an issue for the following scenarios:

• Information needed to succeed in developing Office Scripts is missing or incomplete.
• Information is inaccurate or obsolete.
• You find typos, grammatical mistakes, or other problems with the articles.
• Articles are organized in a confusing or unintuitive manner.

If you are seeing product behavior that differs from the documentation, please provide as much of the following information as is possible and relevant:

• The version and build number of the client you are using.
• Steps to reproduce the issue.
• Console output and error messages.

We also encourage you to fork, make the fix, and do a pull request of your proposed changes. For details, see Contribute to this documentation.

If your issue is not related to the Office Scripts documentation, please post it to one of the following channels instead:

• To ask a question about designing Office Scripts or the Office.js API that runs Office Scripts, post your question to Stack Overflow and tag it with the "office-scripts" tag.
• To report an issue with the Office.js API, create the issue in the OfficeDev/office-js repository, which members of the product team monitor for customer-reported issues.

Copyright

Copyright (c) 2019 Microsoft Corporation. All rights reserved.

Microsoft Open Source Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.