{"id":2450,"date":"2024-05-22T12:54:14","date_gmt":"2024-05-22T17:54:14","guid":{"rendered":"https:\/\/readmeprd.wpenginepowered.com\/?p=2450"},"modified":"2024-08-06T12:26:38","modified_gmt":"2024-08-06T17:26:38","slug":"customize-dx-developer-dashboard","status":"publish","type":"post","link":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard","title":{"rendered":"Customize Your DX With Developer Dashboard"},"content":{"rendered":"\n<p>When considering <a href=\"https:\/\/readme.com\/resources\/why-dx-matters-driving-api-success-with-a-user-first-approach\/\" rel=\"noreferrer nofollow noopener\">what makes a great developer experience<\/a>, we usually break it down into the three stages of your developer lifecycle:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Evaluation &amp; onboarding<\/strong> \ud83e\udd14 Educating users about what\u2019s possible and helping them make their first API call as quickly as possible<\/li>\n\n\n\n<li><strong>Engagement &amp; support<\/strong> \u2764\ufe0f Giving users the tools to build efficiently and helping them debug issues when they run into roadblocks<\/li>\n\n\n\n<li><strong>Retention &amp; growth<\/strong> \ud83d\udcc8 Driving adoption of new API features, increasing usage over time, and ensuring a smooth transition for users to new API versions<\/li>\n<\/ul>\n\n\n\n<p>Supporting this full developer lifecycle \u2014 from the first call through long-term integration \u2014 is what we aim to do here at ReadMe. Creating a great experience for your API users is no different than for any other product: the exact tactics you use may vary, but at the end of the day, you\u2019re helping people with a problem to solve and a job to do.&nbsp;<\/p>\n\n\n\n<p><em>What\u2019s possible with your API? How can your developers start building? And what can they do when things go wrong? <\/em>These are the answers users are looking for in your developer hub, and we\u2019re excited to help you deliver them \u2705<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"introducing-developer-dashboard\">Developer Dashboard: An API console embedded in your ReadMe hub<\/h2>\n\n\n\n<p>API teams talk about \u201cTime to First Call\u201d as a north-star metric for their developer experience: how quickly they can engage and enable a new developer to make their first API call. There are several things that go into this process (and several potential pitfalls along the way), and all of them are important \u2014 which is why we prioritized them when building Developer Dashboard. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"lowering-the-on-ramp-for-new-users\">Lower the on-ramp for new users\u00a0with Personalized Docs<\/h2>\n\n\n\n<p>Give logged-in developers instant access to their API keys in your hub so that they can jump right in to making API calls and see responses in real-time. You\u2019ll first need to deploy the\u00a0<a href=\"https:\/\/docs.readme.com\/main\/docs\/personalized-docs-webhook\">Personalized Docs Webhook<\/a>\u00a0and set up and publish the\u00a0<a href=\"https:\/\/docs.readme.com\/main\/docs\/reference-core-pages\">Getting Started and Authentication pages<\/a>\u00a0in your API Reference. We&#8217;re here to help, with guides to walk you through every step of the way \ud83d\ude0e<\/p>\n\n\n\n<p>After they\u2019re up and running, their API keys are easily accessible in Try It anytime they\u2019re checking out a new endpoint. Server variables or other custom data can be piped in too, so everything they need is at their fingertips:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"2000\" height=\"1088\" src=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1.png\" alt=\"Screenshot of authentication screen inside an API Reference\" class=\"wp-image-2750\" srcset=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1.png 2000w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1-300x163.png 300w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1-1024x557.png 1024w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1-768x418.png 768w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1-1536x836.png 1536w\" sizes=\"auto, (max-width: 2000px) 100vw, 2000px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"getting-on-the-same-page-to-debug-issues\">Getting on the same page to debug issues<\/h2>\n\n\n\n<p>You\u2019ve made it easier for new users to get started \u2014 now what? Inevitably, they\u2019ll run into issues (it happens to the best of us!), so making the debugging experience as efficient and painless as possible is the next priority.\u00a0Your first line of support should always be to give users the tools to try to debug on their own. If they can figure out what\u2019s going on in a few minutes and avoid waiting for a support ticket to be answered, that\u2019s the dream \ud83c\udf20 <\/p>\n\n\n\n<p>Users can see their previous requests for all API keys they have access to on the My Requests page in the API Reference, so they can quickly dig into failing requests and see what\u2019s going on.\u00a0<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"2000\" height=\"1096\" src=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-3.png\" alt=\"Screenshot of My Requests page inside an API Reference\" class=\"wp-image-2752\" srcset=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-3.png 2000w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-3-300x164.png 300w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-3-1024x561.png 1024w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-3-768x421.png 768w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-3-1536x842.png 1536w\" sizes=\"auto, (max-width: 2000px) 100vw, 2000px\" \/><\/figure>\n\n\n\n<p>Using quick filters for endpoints, method, status, and\/or user agent, users can hone in on failing requests (and check to see what\u2019s different about their successful calls). They can also click into any log to reveal even more details related to their request and response. <a href=\"https:\/\/docs.readme.com\/main\/docs\/my-requests\">Head here to learn more about My Requests and how to configure it<\/a>. <\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Give your users direct access to their logs<\/h2>\n\n\n\n<p>Showing your developers their API logs directly in your hub also makes it easier to immediately troubleshoot issues without having to navigate away from your hub. You\u2019ll need to integrate the Metrics SDK first in order to show your users their logs in the hub. Fortunately, setup instructions for that, in various languages, can be found\u00a0<a href=\"https:\/\/docs.readme.com\/main\/docs\/sending-api-logs\">here<\/a>\u00a0\ud83d\uddfa\ufe0f<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"542\" src=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/user-logs-developer-dashboard-1024x542.png\" alt=\"Screenshot of user API logs inside a developer hub\" class=\"wp-image-2748\" srcset=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/user-logs-developer-dashboard-1024x542.png 1024w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/user-logs-developer-dashboard-300x159.png 300w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/user-logs-developer-dashboard-768x407.png 768w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/user-logs-developer-dashboard-1536x813.png 1536w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/user-logs-developer-dashboard-2048x1084.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"supporting-your-users-in-the-long-run\">Supporting your users in the long run<\/h2>\n\n\n\n<p>With the foundations of your API onboarding and debugging experience in place, it\u2019s time to look toward the future \ud83d\udee3 In addition to the vision for your APIs coming from your team, ReadMe gives you valuable insights to help inform these decisions. You can easily track usage metrics, like API adoption over time and API error volume, to see where users are getting stuck. &nbsp;<\/p>\n\n\n\n<p>The Home screen also provides an at-a-glance snapshot of your Docs Metrics where you can see your most popular pages and search terms, and track new users over time. These metrics can inform what pages to prioritize updating, or to see what pages might need to be labeled differently based on high volume keyword searches.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"2000\" height=\"1052\" src=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-2.png\" alt=\"Screenshots of metrics for API documentation\" class=\"wp-image-2751\" srcset=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-2.png 2000w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-2-300x158.png 300w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-2-1024x539.png 1024w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-2-768x404.png 768w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-2-1536x808.png 1536w\" sizes=\"auto, (max-width: 2000px) 100vw, 2000px\" \/><\/figure>\n\n\n\n<p>Together, all of these insights bring a data-driven lens to decisions about where to add features and invest resources to improve your API and documentation. You can also export your metrics data as a .CSV file for further analysis or cross-referencing with other data.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img loading=\"lazy\" decoding=\"async\" width=\"1600\" height=\"828\" src=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image.png\" alt=\"Screenshot of bar graphs displaying API documentation metrics\" class=\"wp-image-2749\" srcset=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image.png 1600w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-300x155.png 300w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1024x530.png 1024w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-768x397.png 768w, https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/image-1536x795.png 1536w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"what%E2%80%99s-coming-next\">Benefits of Developer Dashboard<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">For ReadMe admins<\/h3>\n\n\n\n<p>We designed the Developer Dashboard experience to streamline and unify the onboarding and setup process for all of the key features that make the personalized developer experience for your end developers possible \u2014 Personalized Docs Webhook, Getting Started &amp; Authentication, Metrics (API Logs) SDK. Collectively, these features power the insights ReadMe Admins see in their My Developers page around who\u2019s using their API, when, how, and with what results.<\/p>\n\n\n\n<p>That&#8217;s not all, though:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>No need to start from scratch on API documentation \u201cmust haves\u201d<\/strong>\u00a0\u270d\ufe0f an Authentication page is VIP(age) to have in your docs to help set your developers up for success out of the gate! Now instead of having to start from a blank canvas, ReadMe offers personalized\u00a0<a href=\"https:\/\/docs.readme.com\/main\/docs\/reference-core-pages\">Getting Started &amp; Authentication page templates<\/a>\u00a0that make it super easy to get those pages up &amp; running in a snap!<\/li>\n\n\n\n<li><strong>Faster developer support tools to diagnose issues\u00a0<\/strong>\ud83c\udfc3 Developer Dashboard allows API teams to get on the same page quickly. They can look up users who are encountering errors in My Developers, see their associated API keys, and dig into all their recent logs to figure out what\u2019s happening and debug the issue quickly.<\/li>\n\n\n\n<li><strong>Track trends with your API over time, spot spikes in errors, see who\u2019s a new user, &amp; more<\/strong>\u00a0\ud83d\udd0e get insights into API usage over time to understand your API use cases, e.g., which endpoints are getting the most use and where users are running into issues, and use these insights to inform your future API roadmap and\/or spot bugs and urgent fixes.<\/li>\n\n\n\n<li><strong>Monitor cohorts of users, send comms to specific groups, and create segments with My Developers\u00a0<\/strong>\ud83d\udccb filter your My Developers page by endpoint, method, status, and more. Search for a user by API key, email, or company. See trends in data over a day, week, month, quarter, and year. Plus, create and save segments for easy reference and to better track issues.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">For your end developers<\/h3>\n\n\n\n<p>Surfacing your developers\u2019 API keys in you hub gives your end developers the tools to make their first API call quickly and seamlessly. Additionally, by providing them with personalized access to their API logs, they can use their most recent activity to quickly debug issues.<\/p>\n\n\n\n<p>Other benefits include: <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Provide better engagement and support\u00a0<\/strong>\u2764\ufe0f your developers have what they need to build efficiently, and you\u2019re giving them the necessary info to debug issues when they (inevitably) run into roadblocks.<\/li>\n\n\n\n<li><strong>Lower the on-ramp for new API users and give your end developers access to API keys<\/strong>\u00a0\ud83d\udee3\ufe0f instead of sharing convoluted instructions on how to get an API key from somewhere else, or causing your developer to switch between browser tabs, surface API keys to users front &amp; center once they\u2019re logged in to your hub.<\/li>\n\n\n\n<li><strong>Provide valuable and easily accessible self-serve debugging tools for your developers<\/strong>\u00a0\ud83e\uddf0 instead of needing to write into support, your developers can access their logs in the hub to dig into issues themselves!<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Getting started<a href=\"https:\/\/docs.readme.com\/main\/docs\/developer-dashboard#getting-started-with-developer-dashboard\"><\/a><\/h2>\n\n\n\n<p>In order to enable the full Developer Dashboard experience \u2014 for your team and for your end developers \u2014 and to unlock the full insights available with My Developers, you\u2019ll first need to complete a two-part onboarding flow. <\/p>\n\n\n\n<p>Check out our quick start video below if you want to see this onboarding flow in action:<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-4-3 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<div class=\"ratio ratio-16x9\"><iframe loading=\"lazy\" title=\"Developer Dashboard Quick Start \ud83d\udcca \ud83c\udf31\" width=\"800\" height=\"600\" src=\"https:\/\/www.youtube.com\/embed\/ZUPjQQ-8vIE?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/div>\n<\/div><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">More questions? <\/h2>\n\n\n\n<p>For a full guide to setting up Developer Dashboard, <a href=\"https:\/\/docs.readme.com\/main\/docs\/developer-dashboard\">head over to this page in our docs<\/a>. And of course, if you have any specific questions, feel free to <a href=\"mailto:support@readmeprd.wpenginepowered.com\">reach out to our support team<\/a>! <\/p>\n","protected":false},"excerpt":{"rendered":"<p>When considering what makes a great developer experience, we usually break it down into the three stages of your developer lifecycle: Supporting this full developer lifecycle \u2014 from the first call through long-term integration \u2014 is what we aim to do here at ReadMe. Creating a great experience for your API users is no different [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":2909,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"categories":[37,24],"tags":[45,11],"ppma_author":[48,50],"class_list":["post-2450","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-features","category-readme-journey","tag-developer-experience","tag-developer-metrics"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v23.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Customize Your DX With Developer Dashboard - ReadMe: Resource Library<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Customize Your DX With Developer Dashboard - ReadMe: Resource Library\" \/>\n<meta property=\"og:description\" content=\"When considering what makes a great developer experience, we usually break it down into the three stages of your developer lifecycle: Supporting this full developer lifecycle \u2014 from the first call through long-term integration \u2014 is what we aim to do here at ReadMe. Creating a great experience for your API users is no different [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard\" \/>\n<meta property=\"og:site_name\" content=\"ReadMe: Resource Library\" \/>\n<meta property=\"article:published_time\" content=\"2024-05-22T17:54:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-08-06T17:26:38+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png\" \/>\n\t<meta property=\"og:image:width\" content=\"200\" \/>\n\t<meta property=\"og:image:height\" content=\"200\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Miche Nickolaisen, Rachel Kalt\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Miche Nickolaisen\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard\",\"url\":\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard\",\"name\":\"Customize Your DX With Developer Dashboard - ReadMe: Resource Library\",\"isPartOf\":{\"@id\":\"https:\/\/readme.com\/resources\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#primaryimage\"},\"image\":{\"@id\":\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#primaryimage\"},\"thumbnailUrl\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png\",\"datePublished\":\"2024-05-22T17:54:14+00:00\",\"dateModified\":\"2024-08-06T17:26:38+00:00\",\"author\":{\"@id\":\"https:\/\/readme.com\/resources\/#\/schema\/person\/770bcc036178743133b5ba515195981b\"},\"breadcrumb\":{\"@id\":\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#primaryimage\",\"url\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png\",\"contentUrl\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png\",\"width\":200,\"height\":200},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/readme.com\/resources\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Customize Your DX With Developer Dashboard\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/readme.com\/resources\/#website\",\"url\":\"https:\/\/readme.com\/resources\/\",\"name\":\"ReadMe: Resource Library\",\"description\":\"Making API documentation better for everyone\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/readme.com\/resources\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/readme.com\/resources\/#\/schema\/person\/770bcc036178743133b5ba515195981b\",\"name\":\"Miche Nickolaisen\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/readme.com\/resources\/#\/schema\/person\/image\/a24e32f88df84934c107cef6fa8d3223\",\"url\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/IMG_7151-scaled-e1718387764646.jpg\",\"contentUrl\":\"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/IMG_7151-scaled-e1718387764646.jpg\",\"caption\":\"Miche Nickolaisen\"},\"description\":\"An Austin resident since 2009, Miche grew up in rural southwestern Missouri. When not working on ReadMe's content marketing, you can find them doing a number of hobbies, including (but not limited to) bouldering, martial arts, playing tabletop RPGs and\/or video games, bullet journaling, and making art. They live with a large menagerie of indoor pets and a smaller (outdoor) menagerie of feral cats they take care of (sometimes including a few possums and raccoons, just for good measure).\",\"url\":\"https:\/\/readme.com\/resources\/author\/miche\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Customize Your DX With Developer Dashboard - ReadMe: Resource Library","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:\/\/readme.com\/resources\/customize-dx-developer-dashboard","og_locale":"en_US","og_type":"article","og_title":"Customize Your DX With Developer Dashboard - ReadMe: Resource Library","og_description":"When considering what makes a great developer experience, we usually break it down into the three stages of your developer lifecycle: Supporting this full developer lifecycle \u2014 from the first call through long-term integration \u2014 is what we aim to do here at ReadMe. Creating a great experience for your API users is no different [&hellip;]","og_url":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard","og_site_name":"ReadMe: Resource Library","article_published_time":"2024-05-22T17:54:14+00:00","article_modified_time":"2024-08-06T17:26:38+00:00","og_image":[{"width":200,"height":200,"url":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png","type":"image\/png"}],"author":"Miche Nickolaisen, Rachel Kalt","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Miche Nickolaisen","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard","url":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard","name":"Customize Your DX With Developer Dashboard - ReadMe: Resource Library","isPartOf":{"@id":"https:\/\/readme.com\/resources\/#website"},"primaryImageOfPage":{"@id":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#primaryimage"},"image":{"@id":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#primaryimage"},"thumbnailUrl":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png","datePublished":"2024-05-22T17:54:14+00:00","dateModified":"2024-08-06T17:26:38+00:00","author":{"@id":"https:\/\/readme.com\/resources\/#\/schema\/person\/770bcc036178743133b5ba515195981b"},"breadcrumb":{"@id":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/readme.com\/resources\/customize-dx-developer-dashboard"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#primaryimage","url":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png","contentUrl":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/05\/CustomizeDX.png","width":200,"height":200},{"@type":"BreadcrumbList","@id":"https:\/\/readme.com\/resources\/customize-dx-developer-dashboard#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/readme.com\/resources\/"},{"@type":"ListItem","position":2,"name":"Customize Your DX With Developer Dashboard"}]},{"@type":"WebSite","@id":"https:\/\/readme.com\/resources\/#website","url":"https:\/\/readme.com\/resources\/","name":"ReadMe: Resource Library","description":"Making API documentation better for everyone","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/readme.com\/resources\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/readme.com\/resources\/#\/schema\/person\/770bcc036178743133b5ba515195981b","name":"Miche Nickolaisen","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/readme.com\/resources\/#\/schema\/person\/image\/a24e32f88df84934c107cef6fa8d3223","url":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/IMG_7151-scaled-e1718387764646.jpg","contentUrl":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/IMG_7151-scaled-e1718387764646.jpg","caption":"Miche Nickolaisen"},"description":"An Austin resident since 2009, Miche grew up in rural southwestern Missouri. When not working on ReadMe's content marketing, you can find them doing a number of hobbies, including (but not limited to) bouldering, martial arts, playing tabletop RPGs and\/or video games, bullet journaling, and making art. They live with a large menagerie of indoor pets and a smaller (outdoor) menagerie of feral cats they take care of (sometimes including a few possums and raccoons, just for good measure).","url":"https:\/\/readme.com\/resources\/author\/miche"}]}},"authors":[{"term_id":48,"user_id":4,"is_guest":0,"slug":"miche","display_name":"Miche Nickolaisen","avatar_url":{"url":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/IMG_7151-scaled-e1718387764646.jpg","url2x":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/IMG_7151-scaled-e1718387764646.jpg"},"first_name":"Miche","last_name":"Nickolaisen","position":"Content Marketing Manager","slogan":"","description":"An Austin resident since 2009, Miche grew up in rural southwestern Missouri. When not working on ReadMe's content marketing, you can find them doing a number of hobbies, including (but not limited to) bouldering, martial arts, playing tabletop RPGs and\/or video games, bullet journaling, and making art.\r\n\r\nThey live with a large menagerie of indoor pets and a smaller (outdoor) menagerie of feral cats they take care of (sometimes including a few possums and raccoons, just for good measure). "},{"term_id":50,"user_id":7,"is_guest":0,"slug":"rachel","display_name":"Rachel Kalt","avatar_url":{"url":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/rachelkalt.jpeg","url2x":"https:\/\/readme.com\/resources\/wp-content\/uploads\/2024\/06\/rachelkalt.jpeg"},"first_name":"Rachel","last_name":"Kalt","position":"Product Marketing Manager","slogan":"","description":"A NY native, Ray spent 10 years in the Bay, followed by a year in NYC, only to realize that it was time to see what other places call to her, her partner, &amp; their dog, Theo. Before product marketing, Ray spent nearly a decade in design agencies, and even longer in restaurants. She\u2019s a lifelong dancer, avid home cook, &amp; reader."}],"_links":{"self":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/posts\/2450","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/comments?post=2450"}],"version-history":[{"count":0,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/posts\/2450\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/media\/2909"}],"wp:attachment":[{"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/media?parent=2450"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/categories?post=2450"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/tags?post=2450"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/readme.com\/resources\/wp-json\/wp\/v2\/ppma_author?post=2450"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}