{"id":2229,"date":"2018-11-27T23:14:08","date_gmt":"2018-11-28T07:14:08","guid":{"rendered":"https:\/\/developer.microsoft.com\/en-us\/office\/blogs\/?p=2229"},"modified":"2021-10-13T09:17:51","modified_gmt":"2021-10-13T16:17:51","slug":"microsoft-graph-documentation-has-a-fresh-new-look","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-documentation-has-a-fresh-new-look\/","title":{"rendered":"Microsoft Graph documentation has a fresh new look"},"content":{"rendered":"

We’ve heard your feedback over the years that you’d like to see some improvements to the Microsoft Graph documentation experience. Today we are announcing that we’ve moved to https:\/\/docs.microsoft.com\/graph<\/a>, which gives our docs a fresh new look!<\/p>\n

Searchable table of contents<\/h2>\n

The single biggest request we heard was for the ability to find things more easily in the reference documentation. With the new search box above the table of contents, you can now find all operations, resource objects, and more. For example, go type “Message” into the search box and quickly find message operations related to Outlook and Microsoft Teams.<\/p>\n

\"\"<\/p>\n

Separate Learn and Reference docs<\/h2>\n

We heard from you that our table of contents was getting a little unwieldy, so we split our Learn topics from the Reference docs. We know that many of you access the reference docs primarily, so we made sure that important development-related topics\u00a0 (Get auth tokens, Use the API) are included in the reference TOC.<\/p>\n

This makes it so much clearer to see what is supported in v1.0 and beta without lots of scrolling in the left pane.
\"\" \"\" \"\"<\/p>\n

V1.0 and Beta Version switcher<\/h2>\n

Wherever you are on the Microsoft Graph site, you can click the API Reference link in the top navigation. With the new version switcher above the table of contents, you can now quickly switch between the v1.0 and beta reference content.<\/p>\n

\"\"<\/p>\n

Breadcrumbs<\/h2>\n

Whether you are clicking around from page to page or land on a page from your favorite search engine…the new breadcrumbs will help you to navigate to parent pages within the docs. This is super useful if you want to quickly get to a resource object. For example, I am on the Get event beta page<\/a> and want to see all the properties for the event resrouce object, by clicking on the Event link in breadcrumb I immediately get there. You can also get there from the parent node in the navigation too!<\/p>\n

\"\"<\/p>\n

Built-in feedback integrated<\/h2>\n

We’re often asked how you can provide feedback on our docs. For a few years now we have been getting feedback via GitHub Issues, but we haven’t been able to surface the feedback on the pages themselves. Now, you can use the new feedback pane at the bottom of each page to submit your feedback. This will post it in the GitHub issues<\/a>\u00a0list in our repository, and other readers will be able to see it on the page as well. One public user found our pre-live docs 5 days ago and already submitted some feedback for more information.<\/p>\n

\"\"<\/a><\/p>\n

In the feedback pane, we also make it clear that if you have questions about how to use the API, your best approach is to post on\u00a0Stack Overflow with the Microsoft-graph tag<\/a>. If you have a feature request for the API, you should post it on UserVoice<\/a>. GitHub issues should be for correcting or suggesting improvements to the documentation.<\/p>\n

Submit your contributions<\/h2>\n

For a few years now, we’ve been accepting Pull Requests for changes to the docs directly from developers. We appreciate people providing feedback as GitHub issues, but if you’re comfortable with forking the repo, making the change and submitting a Pull Request we are ready for them!<\/p>\n

Browser friendly<\/h2>\n

Many of you out there like to have you tablet beside your keyboard with the reference content open. The existing table of contents and general rendering of the pages was not optimal for iOS and Android. Now that we are on the docs.microsoft.com platform, you’ll be able to surf the docs from your couch without those frustrations!\n
\"\" \"\" \"\" \"\"\n<\/p>\n

Training content built in<\/h2>\n

We’ve had training content for a while, but its been buried in lab.md files within GitHub.com repos. With todays fresh look, we’ve also introduced these training labs directly into the docs! Check out the ASP.NET training lab that takes you from File | New Project all the way through to call your first Microsoft Graph API!<\/p>\n

\"\"\n<\/p>\n

Share the docs!<\/h2>\n

The share button in all the docs pages allows you to tweet out useful content you’ve found. It is quite common usage pattern to send an email reminder to yourself to save it for later too!<\/p>\n

Dark mode<\/h2>\n

For those of you who like like your docs to be easy on the eyes, we also now support Dark mode!<\/p>\n

\"\"<\/p>\n

What’s next?<\/h2>\n

In the coming months, this experience will only get better! Now that we are live on the new docs platform, we will start to work on: localized docs transition to docs.microsoft.com; standardizing all pages to have the same content structure; adding new sections for what OData operations are supported; integrating Graph Explorer directly into each operation page of the graph; showing SDK code snippets as well as HTTP snippets; and much more.<\/p>\n

We really appreciate all the feedback that has driven us to get to where we are today. We welcome your feedback moving forward to\u00a0 help us continue to make the experience better for Microsoft Graph developers!<\/p>\n

 <\/p>\n

Jeremy Thake<\/p>\n

Senior Program Manager, Microsoft Graph<\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

We’ve heard your feedback over the years that you’d like to see some improvements to the Microsoft Graph documentation experience. Today we are announcing that we’ve moved to https:\/\/docs.microsoft.com\/graph, which gives our docs a fresh new look!<\/p>\n","protected":false},"author":69113,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2229","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365-developer"],"acf":[],"blog_post_summary":"

We’ve heard your feedback over the years that you’d like to see some improvements to the Microsoft Graph documentation experience. Today we are announcing that we’ve moved to https:\/\/docs.microsoft.com\/graph, which gives our docs a fresh new look!<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/2229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69113"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=2229"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/2229\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=2229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=2229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=2229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}