{"id":1096,"date":"2026-02-25T10:35:53","date_gmt":"2026-02-25T10:35:53","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/"},"modified":"2026-02-25T10:35:53","modified_gmt":"2026-02-25T10:35:53","slug":"user-story-format-complete-guide","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/","title":{"rendered":"The Essential Structure: Who, What, and Why"},"content":{"rendered":"<p>Every great story begins with clarity. But too often, teams fall into the trap of writing user stories that sound like technical specs or vague promises. I\u2019ve seen dozens of sprint planning meetings derailed by poorly structured stories\u2014ambiguous, untestable, or missing the user\u2019s real need.<\/p>\n<p>The truth is, the user story format isn\u2019t just a template\u2014it\u2019s a deliberate framework designed to enforce focus on value, collaboration, and outcome. As someone who\u2019s helped over 100 teams refine their story-writing practices, I\u2019ve learned that getting the format right is the single most impactful step toward building the right product.<\/p>\n<p>This chapter walks you through the proven <strong>user story format<\/strong>, not as a rigid rulebook, but as a living tool. You\u2019ll learn how to write stories that spark conversation, clarify intent, and align the entire team around what truly matters.<\/p>\n<h2>Mastering the Core Structure: As a&#8230;, I want&#8230;, so that&#8230;<\/h2>\n<p>The standard format\u2014<em>As a [user], I want [goal], so that [benefit]<\/em>\u2014is deceptively simple. But its power lies in the discipline it enforces.<\/p>\n<p>Breaking it down:<\/p>\n<ul>\n<li><strong>Who<\/strong> is the user? This isn\u2019t just \u201ca user\u201d\u2014it\u2019s a role: <em>customer<\/em>, <em>admin<\/em>, <em>freelancer<\/em>. Be precise.<\/li>\n<li><strong>What<\/strong> do they want? Use active verbs. Avoid technical jargon. Think \u201csave time,\u201d \u201csee data,\u201d \u201csubmit application.\u201d<\/li>\n<li><strong>Why<\/strong> does it matter? This is the value. It answers: \u201cHow does this benefit the user or business?\u201d<\/li>\n<\/ul>\n<p>Let\u2019s look at a real example:<\/p>\n<p><em>As a freelance designer, I want to export my project as a PDF so that I can share it with clients without requiring access to my design tool.<\/em><\/p>\n<p>Notice how every element is clear and grounded in user context. The action is simple, the goal is unambiguous, and the benefit ties directly to a real workflow.<\/p>\n<h3>Why This Structure Works<\/h3>\n<p>It\u2019s not just about grammar\u2014it\u2019s about behavior. This format forces teams to consider three things:<\/p>\n<ol>\n<li><strong>Empathy<\/strong> \u2013 Who is the user? What do they actually need?<\/li>\n<li><strong>Focus<\/strong> \u2013 What action should the system support?<\/li>\n<li><strong>Value<\/strong> \u2013 Why does this matter in the real world?<\/li>\n<\/ol>\n<p>When you write without this structure, you risk falling into the trap of building features no one wants. The format keeps you honest.<\/p>\n<p>Don\u2019t confuse this with a task or requirement. A user story is <strong>not<\/strong> \u201cAdd PDF export button.\u201d That\u2019s implementation. This format keeps the focus on the user\u2019s goal.<\/p>\n<h2>Practical Application: Writing User Story Examples<\/h2>\n<p>Let\u2019s examine how the <strong>user story template<\/strong> applies across different domains.<\/p>\n<p>Here are real-world <strong>writing user story examples<\/strong> I\u2019ve seen in SaaS, e-commerce, and healthcare platforms:<\/p>\n<h3>Example 1: E-commerce Checkout<\/h3>\n<p><em>As a shopper, I want to apply a discount code at checkout so that I can save money on my purchase.<\/em><\/p>\n<p>This captures the user role, core functionality, and personal benefit. The next step? Define acceptance criteria to ensure it works across edge cases\u2014like expired codes or minimum purchase thresholds.<\/p>\n<h3>Example 2: Mobile Banking App<\/h3>\n<p><em>As a customer, I want to view my transaction history for the past 90 days so that I can reconcile my budget and track spending habits.<\/em><\/p>\n<p>Notice the specificity: \u201cpast 90 days.\u201d That\u2019s not just clear\u2014it\u2019s testable. You can verify this story by checking if the UI shows data for exactly 90 days and nothing more.<\/p>\n<h3>Example 3: Project Management Tool<\/h3>\n<p><em>As a team lead, I want to assign a task to a specific team member so that I can track ownership and ensure accountability.<\/em><\/p>\n<p>This one is about process. The benefit isn\u2019t just task assignment\u2014it\u2019s traceability and workflow clarity.<\/p>\n<p>These examples show how the same <strong>user story template<\/strong> adapts to different industries and user types. The format remains consistent; the content shifts based on context.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with the best intentions, stories can go off the rails. Here are the most frequent mistakes I\u2019ve seen\u2014and how to fix them.<\/p>\n<ul>\n<li><strong>Too vague<\/strong>: \u201cAs a user, I want to see data.\u201d \u2192 Fix: Be specific. \u201cAs a sales rep, I want to see daily conversion rates by region so that I can identify underperforming markets.\u201d<\/li>\n<li><strong>Too technical<\/strong>: \u201cAs a user, I want to generate a JSON payload.\u201d \u2192 Fix: Shift focus: \u201cAs a developer, I want to export data in JSON format so that I can integrate it with external systems.\u201d<\/li>\n<li><strong>Missing the benefit<\/strong>: \u201cAs a user, I want to log in.\u201d \u2192 Fix: Add value: \u201cAs a customer, I want to log in so that I can access my order history and track shipments.\u201d<\/li>\n<li><strong>Overloading the story<\/strong>: \u201cAs a user, I want to filter, sort, export, and print data.\u201d \u2192 Fix: Split into smaller stories. Focus on one core action at a time.<\/li>\n<\/ul>\n<p>Each of these issues undermines the goal: building something valuable, testable, and aligned with user needs.<\/p>\n<h2>Checklist: Is Your Story Ready?<\/h2>\n<p>Use this quick checklist to evaluate if your <strong>user story format<\/strong> is effective:<\/p>\n<ul>\n<li>Is the user role specific and realistic?<\/li>\n<li>Does the goal use an active verb?<\/li>\n<li>Is the benefit tied to real user or business value?<\/li>\n<li>Can the story be tested? (Is it verifiable?)<\/li>\n<li>Is the story small enough to fit in a sprint?<\/li>\n<\/ul>\n<p>If any answer is \u201cno,\u201d it\u2019s not ready for the backlog. Refine it.<\/p>\n<h2>When to Deviate\u2014and Why<\/h2>\n<p>Not every story needs the full format. In fast-moving sprints, teams sometimes use shorthand:<\/p>\n<ul>\n<li>\u201cAdd export PDF button\u201d<\/li>\n<li>\u201cSync data every 5 minutes\u201d<\/li>\n<\/ul>\n<p>But this should never be a substitute for real conversation. Shorthand stories are <strong>placeholders<\/strong>, not stories. They must be expanded during refinement.<\/p>\n<p>Never assume the team knows the \u201cwhy.\u201d Even in quick sprints, the <em>so that<\/em> part is non-negotiable. It\u2019s what separates a feature from a valuable outcome.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Is the user story format the same across all Agile frameworks?<\/h3>\n<p>Yes\u2014this format is foundational to Scrum, Kanban, SAFe, and XP. The intent remains the same: prioritize user value and enable conversation. The only difference is how stories are managed and prioritized.<\/p>\n<h3>Can I write a user story without the \u201cAs a\u2026\u201d part?<\/h3>\n<p>Technically yes, but strongly discouraged. The \u201cAs a\u2026\u201d part grounds the story in context. Skipping it increases ambiguity and reduces team alignment. It\u2019s not just convention\u2014it\u2019s a safety net.<\/p>\n<h3>How do I handle multiple user roles in one story?<\/h3>\n<p>Split the story. If two roles need different things, write separate stories. For example:<\/p>\n<ul>\n<li><em>As a customer, I want to view my order status so that I can track delivery.<\/em><\/li>\n<li><em>As a support agent, I want to see order status history so that I can resolve customer inquiries faster.<\/em><\/li>\n<\/ul>\n<p>One story, one user. This keeps value clear and testing manageable.<\/p>\n<h3>Are acceptance criteria part of the user story format?<\/h3>\n<p>No\u2014acceptance criteria are separate, but essential. They clarify the <em>definition of done<\/em>. They answer: \u201cWhen is this story truly complete?\u201d But the format itself doesn\u2019t include them. They\u2019re added during refinement.<\/p>\n<h3>Can a user story be written from a technical perspective?<\/h3>\n<p>Only as a placeholder. If a developer writes \u201cAs a backend system, I want to validate input,\u201d it\u2019s not a user story. It\u2019s a technical requirement. That must be reframed as a user benefit: \u201cAs a customer, I want to receive an error message if I enter invalid data so that I don\u2019t submit a broken form.\u201d<\/p>\n<h3>How do I know if my user story is too big?<\/h3>\n<p>If it takes more than a few days to complete, it\u2019s too big. Use the INVEST criteria: Is it Independent, Negotiable, Valuable, Estimable, Small, and Testable? If not, split it. A good rule of thumb: if the user can\u2019t understand the goal in 10 seconds, it\u2019s too complex.<\/p>\n<h2>Final Thoughts<\/h2>\n<p>The <strong>user story format<\/strong> isn\u2019t a rigid template\u2014it\u2019s a promise. A promise to focus on the user, to value outcomes over features, and to invite conversation.<\/p>\n<p>When done well, it becomes a shared language. A contract between product, development, and QA. Not for documentation\u2019s sake, but because the real work starts when the story is written.<\/p>\n<p>Master this format, and you\u2019re not just writing stories\u2014you\u2019re building trust, clarity, and momentum. The rest of the Agile process flows from there.<\/p>\n<p>Now go write one. Then talk about it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every great story begins with clarity. But too often, teams fall into the trap of writing user stories that sound like technical specs or vague promises. I\u2019ve seen dozens of sprint planning meetings derailed by poorly structured stories\u2014ambiguous, untestable, or missing the user\u2019s real need. The truth is, the user story format isn\u2019t just a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1095,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1096","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>User Story Format: The Complete Guide<\/title>\n<meta name=\"description\" content=\"Master the user story format with expert insights, real-world examples, and proven techniques to write clear, valuable, and testable Agile user stories that drive team alignment and product success.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Format: The Complete Guide\" \/>\n<meta property=\"og:description\" content=\"Master the user story format with expert insights, real-world examples, and proven techniques to write clear, valuable, and testable Agile user stories that drive team alignment and product success.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/\",\"name\":\"User Story Format: The Complete Guide\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:35:53+00:00\",\"description\":\"Master the user story format with expert insights, real-world examples, and proven techniques to write clear, valuable, and testable Agile user stories that drive team alignment and product success.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Building Strong Stories Step by Step\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Essential Structure: Who, What, and Why\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Format: The Complete Guide","description":"Master the user story format with expert insights, real-world examples, and proven techniques to write clear, valuable, and testable Agile user stories that drive team alignment and product success.","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:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/","og_locale":"de_DE","og_type":"article","og_title":"User Story Format: The Complete Guide","og_description":"Master the user story format with expert insights, real-world examples, and proven techniques to write clear, valuable, and testable Agile user stories that drive team alignment and product success.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/","name":"User Story Format: The Complete Guide","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:35:53+00:00","description":"Master the user story format with expert insights, real-world examples, and proven techniques to write clear, valuable, and testable Agile user stories that drive team alignment and product success.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/user-story-format-complete-guide\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Building Strong Stories Step by Step","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/"},{"@type":"ListItem","position":4,"name":"The Essential Structure: Who, What, and Why"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1096","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1096\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1095"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1096"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1096"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}