{"id":87836,"date":"2025-05-14T09:00:00","date_gmt":"2025-05-14T16:00:00","guid":{"rendered":"https:\/\/github.blog\/?p=87836"},"modified":"2025-05-15T08:09:46","modified_gmt":"2025-05-15T15:09:46","slug":"documentation-done-right-a-developers-guide","status":"publish","type":"post","link":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/","title":{"rendered":"Documentation done right: A developer\u2019s guide"},"content":{"rendered":"<!DOCTYPE html PUBLIC \"-\/\/W3C\/\/DTD HTML 4.0 Transitional\/\/EN\" \"http:\/\/www.w3.org\/TR\/REC-html40\/loose.dtd\">\n<html><body><p class=\"wp-block-paragraph\">With all the work involved in creating and maintaining a project, sometimes writing documentation can slip through the cracks. However, good docs are a huge asset to any project. Consider the benefits:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Better collaboration<\/strong>: Clear, consistent documentation ensures everyone&rsquo;s on the same page, from your immediate team to outside stakeholders. Additionally, docs promote independent problem solving, saving core contributors the time and effort of answering every question.<\/li>\n\n\n\n<li><strong>Smoother onboarding<\/strong>: By providing ways to get started, explaining core concepts, and including tutorial-style content, good documentation allows new team members to ramp up quickly.<\/li>\n\n\n\n<li><strong>Increased adoption<\/strong>: The easier it is to understand, set up, and run your project, the more likely someone will use it.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">With these benefits in mind, let&rsquo;s take a look at some important principles of documentation, then dive into how you can quickly create effective docs for your project.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-key-tenets-of-documentation\">Key tenets of documentation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There are three key principles you should follow as you document your project.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-keep-it-clear\">Keep it clear<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use plain language that&rsquo;s easy to understand. The goal is to make your documentation as accessible as possible. A good guideline is to ask yourself if there are any acronyms or technical terms in your documentation that some folks in your target audience won&rsquo;t understand. If that&rsquo;s the case, either swap them for simpler language, or make sure they&rsquo;re defined in your document.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-keep-it-concise\">Keep it concise<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Document only necessary information. Trying to cover every possible edge case will overwhelm your readers. Instead, write docs that help the vast majority of readers get started, understand core concepts, and use your project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Additionally, keep each document focused on a particular topic or task. If you find yourself including information that isn&rsquo;t strictly necessary, move it into separate, smaller documents and link to them when it&rsquo;s helpful.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-keep-it-structured\">Keep it structured<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Consider the structure of each document as you write it to make sure it is easy to scan and understand:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Put the most important information first to help readers quickly understand if a document is relevant to them.<\/li>\n\n\n\n<li>Use headings and a table of contents to tell your readers where to find specific information. We suggest using documentation templates with common headings to quickly and consistently create structured content.<\/li>\n\n\n\n<li>Use text highlighting like boldface and formatting elements like bulleted lists to help readers scan content. Aim for 10% or less text highlighting to make sure emphasized text stands out.<\/li>\n\n\n\n<li>Be consistent with your styling. For example, if you put important terminology in bold in one document, do the same in your other content.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-organizing-your-documentation\">Organizing your documentation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Just as there are principles to follow when writing individual documents, you should also follow a framework for organizing documents in your repo.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There are many approaches to organizing documentation in your repo, but one that we&rsquo;ve used for several projects and recommend is <a href=\"https:\/\/diataxis.fr\/\">the Di&aacute;taxis framework<\/a>. This is a systematic approach to organizing all the documents relevant to your project.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Applying a systematic approach to documenting your repositories can make it easier for users to know where to go to find the information that they need. This reduces frustration and gets folks contributing to your project faster.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Di&aacute;taxis divides documents based on their purpose into four categories:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Tutorials<\/strong>: Learning-oriented documents<\/li>\n\n\n\n<li><strong>How-to guides<\/strong>: Goal-oriented instructions for specific tasks<\/li>\n\n\n\n<li><strong>Explanation<\/strong>: Discussions providing understanding of the project<\/li>\n\n\n\n<li><strong>Reference<\/strong>: Technical specifications and information<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Each document in your repository should fit into one of these categories. This helps users quickly find the appropriate resource for their current situation, whether they need to learn a new concept, solve a specific problem, understand underlying principles, or look up technical details.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can also be a helpful guide to identify which documentation your repository is missing. Is there a tool your repository uses that doesn&rsquo;t have a reference document? Are there enough tutorials for contributors to get started with your repository? Are there how-to guides to explain some of the common tasks that need to be accomplished within your repository?&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Organizing your documentation according to this framework helps ensure you&rsquo;re taking a holistic approach to building and maintaining key content for your project.<\/p>\n\n\n\n<aside data-color-mode=\"light\" data-dark-theme=\"dark\" data-light-theme=\"light_dimmed\" class=\"wp-block-group post-aside--large p-4 p-md-6 is-style-light-dimmed has-global-padding is-layout-constrained wp-block-group-is-layout-constrained is-style-light-dimmed--2\" style=\"border-top-width:4px\">\n<h2 class=\"wp-block-heading h5-mktg gh-aside-title is-typography-preset-h5\" id=\"h-documenting-your-project\" style=\"margin-top:0\">Documenting your project<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Want to test out this framework and guidelines for yourself? Check out <a href=\"https:\/\/github.com\/github\/internal-documentation-example\">this example repository<\/a> with a docs folder structure and documentation templates that you can copy into your own project.<\/p>\n<\/aside>\n<\/body><\/html>\n","protected":false},"excerpt":{"rendered":"<p>Learn why and how you should write docs for your project with the Di\u00e1taxis framework.<\/p>\n","protected":false},"author":2299,"featured_media":85979,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_gh_post_show_toc":"yes","_gh_post_is_no_robots":"","_gh_post_is_featured":"yes","_gh_post_is_excluded":"","_gh_post_is_unlisted":"","_gh_post_related_link_1":"","_gh_post_related_link_2":"","_gh_post_related_link_3":"","_gh_post_sq_img":"","_gh_post_sq_img_id":"","_gh_post_cta_title":"","_gh_post_cta_text":"","_gh_post_cta_link":"","_gh_post_cta_button":"","_gh_post_recirc_hide":"","_gh_post_recirc_col_1":"","_gh_post_recirc_col_2":"","_gh_post_recirc_col_3":"","_gh_post_recirc_col_4":"","_featured_video":"","_gh_post_additional_query_params":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false,"_links_to":"","_links_to_target":""},"categories":[3298],"tags":[],"coauthors":[3531,3689],"class_list":["post-87836","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-developer-skills"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.7 (Yoast SEO v27.7) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentation done right: A developer\u2019s guide - The GitHub Blog<\/title>\n<meta name=\"description\" content=\"Learn why and how you should write docs for your project with the Di\u00e1taxis framework.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentation done right: A developer\u2019s guide\" \/>\n<meta property=\"og:description\" content=\"Learn why and how you should write docs for your project with the Di\u00e1taxis framework.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/\" \/>\n<meta property=\"og:site_name\" content=\"The GitHub Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-05-14T16:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-05-15T15:09:46+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/github.blog\/wp-content\/uploads\/2025\/03\/github_logo_invertocat_dark_3.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Brittany Ellich, Sam Browning\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Brittany Ellich, Sam Browning\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/\"},\"author\":{\"name\":\"Brittany Ellich\",\"@id\":\"https:\\\/\\\/github.blog\\\/#\\\/schema\\\/person\\\/e60f8645e0750138873c1343e325ef15\"},\"headline\":\"Documentation done right: A developer\u2019s guide\",\"datePublished\":\"2025-05-14T16:00:00+00:00\",\"dateModified\":\"2025-05-15T15:09:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/\"},\"wordCount\":738,\"image\":{\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/github.blog\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/github_logo_invertocat_dark_3.png?fit=1200%2C630\",\"articleSection\":[\"Developer skills\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/\",\"url\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/\",\"name\":\"Documentation done right: A developer\u2019s guide - The GitHub Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/github.blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/github.blog\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/github_logo_invertocat_dark_3.png?fit=1200%2C630\",\"datePublished\":\"2025-05-14T16:00:00+00:00\",\"dateModified\":\"2025-05-15T15:09:46+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/github.blog\\\/#\\\/schema\\\/person\\\/e60f8645e0750138873c1343e325ef15\"},\"description\":\"Learn why and how you should write docs for your project with the Di\u00e1taxis framework.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/#primaryimage\",\"url\":\"https:\\\/\\\/github.blog\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/github_logo_invertocat_dark_3.png?fit=1200%2C630\",\"contentUrl\":\"https:\\\/\\\/github.blog\\\/wp-content\\\/uploads\\\/2025\\\/03\\\/github_logo_invertocat_dark_3.png?fit=1200%2C630\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/documentation-done-right-a-developers-guide\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/github.blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Developer skills\",\"item\":\"https:\\\/\\\/github.blog\\\/developer-skills\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Documentation done right: A developer\u2019s guide\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/github.blog\\\/#website\",\"url\":\"https:\\\/\\\/github.blog\\\/\",\"name\":\"The GitHub Blog\",\"description\":\"Updates, ideas, and inspiration from GitHub to help developers build and design software.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/github.blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/github.blog\\\/#\\\/schema\\\/person\\\/e60f8645e0750138873c1343e325ef15\",\"name\":\"Brittany Ellich\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/898c7098afd46e9e72a15974036000713038f02811949b44f887f464c688bcdb?s=96&d=mm&r=gb24070c4c5165a92feefb185827d649a\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/898c7098afd46e9e72a15974036000713038f02811949b44f887f464c688bcdb?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/898c7098afd46e9e72a15974036000713038f02811949b44f887f464c688bcdb?s=96&d=mm&r=g\",\"caption\":\"Brittany Ellich\"},\"description\":\"Brittany is a software engineer at GitHub, working in Platform and Enterprise.\",\"url\":\"https:\\\/\\\/github.blog\\\/author\\\/brittanyellich\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentation done right: A developer\u2019s guide - The GitHub Blog","description":"Learn why and how you should write docs for your project with the Di\u00e1taxis framework.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/","og_locale":"en_US","og_type":"article","og_title":"Documentation done right: A developer\u2019s guide","og_description":"Learn why and how you should write docs for your project with the Di\u00e1taxis framework.","og_url":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/","og_site_name":"The GitHub Blog","article_published_time":"2025-05-14T16:00:00+00:00","article_modified_time":"2025-05-15T15:09:46+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/github.blog\/wp-content\/uploads\/2025\/03\/github_logo_invertocat_dark_3.png","type":"image\/png"}],"author":"Brittany Ellich, Sam Browning","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Brittany Ellich, Sam Browning","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/#article","isPartOf":{"@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/"},"author":{"name":"Brittany Ellich","@id":"https:\/\/github.blog\/#\/schema\/person\/e60f8645e0750138873c1343e325ef15"},"headline":"Documentation done right: A developer\u2019s guide","datePublished":"2025-05-14T16:00:00+00:00","dateModified":"2025-05-15T15:09:46+00:00","mainEntityOfPage":{"@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/"},"wordCount":738,"image":{"@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/#primaryimage"},"thumbnailUrl":"https:\/\/github.blog\/wp-content\/uploads\/2025\/03\/github_logo_invertocat_dark_3.png?fit=1200%2C630","articleSection":["Developer skills"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/","url":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/","name":"Documentation done right: A developer\u2019s guide - The GitHub Blog","isPartOf":{"@id":"https:\/\/github.blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/#primaryimage"},"image":{"@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/#primaryimage"},"thumbnailUrl":"https:\/\/github.blog\/wp-content\/uploads\/2025\/03\/github_logo_invertocat_dark_3.png?fit=1200%2C630","datePublished":"2025-05-14T16:00:00+00:00","dateModified":"2025-05-15T15:09:46+00:00","author":{"@id":"https:\/\/github.blog\/#\/schema\/person\/e60f8645e0750138873c1343e325ef15"},"description":"Learn why and how you should write docs for your project with the Di\u00e1taxis framework.","breadcrumb":{"@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/#primaryimage","url":"https:\/\/github.blog\/wp-content\/uploads\/2025\/03\/github_logo_invertocat_dark_3.png?fit=1200%2C630","contentUrl":"https:\/\/github.blog\/wp-content\/uploads\/2025\/03\/github_logo_invertocat_dark_3.png?fit=1200%2C630","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/github.blog\/developer-skills\/documentation-done-right-a-developers-guide\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/github.blog\/"},{"@type":"ListItem","position":2,"name":"Developer skills","item":"https:\/\/github.blog\/developer-skills\/"},{"@type":"ListItem","position":3,"name":"Documentation done right: A developer\u2019s guide"}]},{"@type":"WebSite","@id":"https:\/\/github.blog\/#website","url":"https:\/\/github.blog\/","name":"The GitHub Blog","description":"Updates, ideas, and inspiration from GitHub to help developers build and design software.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/github.blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/github.blog\/#\/schema\/person\/e60f8645e0750138873c1343e325ef15","name":"Brittany Ellich","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/898c7098afd46e9e72a15974036000713038f02811949b44f887f464c688bcdb?s=96&d=mm&r=gb24070c4c5165a92feefb185827d649a","url":"https:\/\/secure.gravatar.com\/avatar\/898c7098afd46e9e72a15974036000713038f02811949b44f887f464c688bcdb?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/898c7098afd46e9e72a15974036000713038f02811949b44f887f464c688bcdb?s=96&d=mm&r=g","caption":"Brittany Ellich"},"description":"Brittany is a software engineer at GitHub, working in Platform and Enterprise.","url":"https:\/\/github.blog\/author\/brittanyellich\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/github.blog\/wp-content\/uploads\/2025\/03\/github_logo_invertocat_dark_3.png?fit=1200%2C630","jetpack_shortlink":"https:\/\/wp.me\/pamS32-mQI","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/posts\/87836","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/users\/2299"}],"replies":[{"embeddable":true,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/comments?post=87836"}],"version-history":[{"count":4,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/posts\/87836\/revisions"}],"predecessor-version":[{"id":87937,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/posts\/87836\/revisions\/87937"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/media\/85979"}],"wp:attachment":[{"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/media?parent=87836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/categories?post=87836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/tags?post=87836"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/github.blog\/wp-json\/wp\/v2\/coauthors?post=87836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}