{"id":685,"date":"2026-02-25T10:22:47","date_gmt":"2026-02-25T10:22:47","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/"},"modified":"2026-02-25T10:22:47","modified_gmt":"2026-02-25T10:22:47","slug":"user-stories-vs-use-cases-confusion","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/","title":{"rendered":"Confusing Use Cases and User Stories"},"content":{"rendered":"

One of the most frequent missteps I\u2019ve seen in Agile teams isn\u2019t about formatting or acceptance criteria\u2014it\u2019s mistaking use cases for user stories. The confusion breeds wasted effort, misaligned priorities, and stories that fail to deliver value because they\u2019re built on a foundation of analysis rather than user-centered conversation.<\/p>\n

As someone who\u2019s worked with over 200 product teams across industries, I\u2019ve watched teams spend hours writing detailed use case descriptions only to realize they\u2019re describing system behavior, not user-centered outcomes. The irony? The very tool meant to capture user needs ends up becoming a technical specification.<\/p>\n

This chapter will clarify what each artifact truly is, when to use which, and how to avoid the hidden trap of requirements confusion agile. You\u2019ll learn to distinguish between what drives user behavior and what drives system logic\u2014and how to keep your backlog focused on people, not processes.<\/p>\n

What\u2019s the Real Difference Between Use Cases and User Stories?<\/h2>\n

At first glance, both user stories and use cases seem to answer: \u201cWhat does the user want?\u201d But they serve different purposes and live in different domains.<\/p>\n

Use Cases: The System\u2019s Perspective<\/h3>\n

Use cases are rooted in traditional requirements engineering. They describe a sequence of actions a system performs in response to a user\u2019s goal. They\u2019re detailed, structured, and often include: actors, preconditions, main flow, alternate flows, and post-conditions.<\/p>\n

They\u2019re useful when you need to model complex, multi-step interactions\u2014especially when different system states, error handling, or external dependencies are involved. But this level of detail makes them heavy and rigid.<\/p>\n

User Stories: The User\u2019s Perspective<\/h3>\n

User stories are lightweight. They\u2019re written in plain language: \u00ab\u00a0As a [role], I want [goal] so that [benefit].\u00a0\u00bb They\u2019re placeholders for conversation\u2014not specifications. Their purpose is to start a dialogue, not to document every edge case.<\/p>\n

They\u2019re best used for breaking down features into small, testable, deliverable pieces. They focus on user value, not system behavior.<\/p>\n

Key Differences in Practice<\/h3>\n\n\n\n\n\n\n\n
Aspect<\/th>\nUser Stories<\/th>\nUse Cases<\/th>\n<\/tr>\n
Primary Focus<\/td>\nUser goal and value<\/td>\nSystem behavior and interaction<\/td>\n<\/tr>\n
Level of Detail<\/td>\nHigh-level, conversational<\/td>\nGranular, structured<\/td>\n<\/tr>\n
Best For<\/td>\nFeature breakdown, backlog refinement, sprint planning<\/td>\nComplex workflows, system integration, stakeholder validation<\/td>\n<\/tr>\n
Change Resistance<\/td>\nLow \u2014 easily adapted<\/td>\nHigh \u2014 difficult to modify after specification<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Use cases are not wrong. But they\u2019re not a substitute for user stories. Confusing one for the other leads to requirements confusion agile.<\/p>\n

When Should You Use Each?<\/h2>\n

Understanding when to use each isn\u2019t about preference\u2014it\u2019s about context and intent. Here\u2019s how to decide.<\/p>\n

Use User Stories When:<\/h3>\n
    \n
  • The goal is to understand user need, not system logic.<\/li>\n
  • You\u2019re in early discovery or backlog grooming.<\/li>\n
  • Stories will be broken into tasks and developed incrementally.<\/li>\n
  • Your team values speed, adaptability, and collaboration.<\/li>\n<\/ul>\n

    They\u2019re the right tool for the daily workflow in Agile. A well-written story opens the door to conversation, not the end of it.<\/p>\n

    Use Use Cases When:<\/h3>\n
      \n
    • You\u2019re modeling complex, multi-actor interactions (e.g., payment processing with bank, user, and system).<\/li>\n
    • You need to identify and document error-prone flows (e.g., failed login attempts, transaction rollbacks).<\/li>\n
    • You’re aligning stakeholders on a high-level view of functionality before sprint development.<\/li>\n
    • System integration or compliance demands traceability.<\/li>\n<\/ul>\n

      Use cases shine as validation artifacts in complex domains. But they should never replace stories\u2014they should support or inform them.<\/p>\n

      Common Pitfalls: How Teams Confuse the Two<\/h2>\n

      Even experienced teams fall into traps when blending user stories and use cases. Here are the most common patterns I\u2019ve observed:<\/p>\n

      1. Writing Use Case Flows as Stories<\/h3>\n

      Example:<\/p>\n

      As a customer, I want to log in so that I can access my account.\n- The system prompts for username and password.\n- User enters credentials.\n- System validates against database.\n- If valid, redirect to dashboard.\n- If invalid, display error message.<\/pre>\n
      This reads like a use case. It\u2019s not a story\u2014it\u2019s a technical specification. It fails the \u201cSo that\u201d test<\/strong>: the benefit isn\u2019t clear. Is it access? Security? Control? The story should be about the user\u2019s goal, not the system\u2019s job.<\/p>\n
      2. Using Use Cases to Replace Acceptance Criteria<\/h3>\n
      Teams often write use case flows as acceptance criteria. But acceptance criteria must be testable, outcome-based, and written in behavior-driven language. Use cases are too broad and procedural.<\/p>\n
      Bad:<\/p>\n
        \n
      • System validates credentials before login<\/li>\n
      • User sees error message if password is wrong<\/li>\n<\/ul>\n
        Good:<\/p>\n
          \n
        • Given I\u2019m on the login page, when I enter a wrong password, then I should see an error message<\/li>\n
        • Given I\u2019m logged in, when I navigate to my profile, then I should see my name displayed<\/li>\n<\/ul>\n
          3. Over-Engineering Stories with Use Case Detail<\/h3>\n
          Stories like:<\/p>\n
          As a bank customer, I want to transfer money to another account so that I can pay bills.\n- Transfer must be completed within 24 hours.\n- Minimum amount is $1.\n- Maximum daily limit is $5,000.\n- Funds must be available in the account.<\/pre>\n
          isn\u2019t a user story\u2014it\u2019s a use case in disguise. It\u2019s too detailed, too prescriptive. The \u201cSo that\u201d clause<\/strong> is buried under constraints. The real value? Probably \u201cso that I can manage my finances without stress.\u201d That\u2019s the user\u2019s real need.<\/p>\n
          When Both Are Needed: A Hybrid Approach<\/h2>\n
          There\u2019s no rule saying you can\u2019t use both. But the key is separation of concerns<\/strong>.<\/p>\n
          Think of user stories as the value layer<\/strong>, and use cases as the behavior layer<\/strong>.<\/p>\n
          Here\u2019s how to use them together:<\/p>\n
            \n
          1. Start with a user story: \u00ab\u00a0As a user, I want to transfer money so that I can pay my bills.\u00a0\u00bb<\/li>\n
          2. Use a use case to model the flow: Who\u2019s involved? What steps? What happens if it fails?<\/li>\n
          3. Extract acceptance criteria from the use case, but rewrite them in plain, testable language.<\/li>\n
          4. Use the story for backlog prioritization and sprint planning.<\/li>\n
          5. Use the use case to guide technical design and stakeholder review.<\/li>\n<\/ol>\n
            This way, the story stays focused on value, while the use case supports complexity without cluttering the backlog.<\/p>\n
            Decision Flow: When to Use Which?<\/h2>\n
            Use this simple flow to decide:<\/p>\n
              \n
            • If the goal is to capture user value<\/strong> and start a conversation<\/strong> \u2192 use a user story.<\/li>\n
            • If the goal is to model complex system behavior<\/strong>, validate edge cases<\/strong>, or ensure traceability<\/strong> \u2192 use a use case.<\/li>\n
            • If both are needed, keep them separate but linked<\/strong>.<\/li>\n<\/ul>\n
              This prevents requirements confusion agile and ensures your backlog stays lean and user-focused.<\/p>\n
              Frequently Asked Questions<\/h2>\n
              What\u2019s the difference between use cases and user stories in Agile?<\/h3>\n
              User stories are lightweight, user-centered narratives that capture what a user wants and why. Use cases are detailed, formal descriptions of system behavior in response to user actions. Use stories for backlog items and conversations. Use cases for modeling complex workflows.<\/p>\n
              Can I use use cases instead of user stories in Agile?<\/h3>\n
              Not effectively. Use cases are too detailed and rigid for Agile. They slow down planning and adaptability. Use them as a tool to inform stories, not as replacements.<\/p>\n
              Why do teams confuse use cases with user stories?<\/h4>\n
              Because both describe user goals. But use cases focus on system logic, while stories focus on user value. Teams often confuse \u00ab\u00a0user needs\u00a0\u00bb with \u00ab\u00a0system responses.\u00a0\u00bb The key is asking: Is this about the user\u2019s goal, or the system\u2019s behavior?<\/p>\n
              When should I use a use case instead of a user story?<\/h3>\n
              When modeling complex interactions involving multiple actors, error conditions, or system states. Use cases are ideal for validating system behavior before development begins\u2014especially in regulated or high-risk environments.<\/p>\n
              Are user stories and use cases the same thing?<\/h3>\n
              No. User stories are brief, value-driven, and conversational. Use cases are formal, detailed, and behavior-focused. They serve different roles: stories for delivery, use cases for analysis.<\/p>\n
              How do I avoid requirements confusion agile?<\/h3>\n
              Ask three questions: (1) Is this about the user\u2019s goal? (2) Is it testable? (3) Does it open a conversation? If it answers \u201cno\u201d to any, it\u2019s likely a use case mislabeled as a story. Keep them separate, and use one to inform the other.<\/p>\n","protected":false},"excerpt":{"rendered":"
              One of the most frequent missteps I\u2019ve seen in Agile teams isn\u2019t about formatting or acceptance criteria\u2014it\u2019s mistaking use cases for user stories. The confusion breeds wasted effort, misaligned priorities, and stories that fail to deliver value because they\u2019re built on a foundation of analysis rather than user-centered conversation. As someone who\u2019s worked with over […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":682,"menu_order":2,"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-685","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUser Stories vs Use Cases Confusion<\/title>\n<meta name=\"description\" content=\"Resolve the difference between use cases and user stories. Learn when to use each, avoid requirements confusion agile, and prevent scope creep in Agile delivery.\" \/>\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\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Stories vs Use Cases Confusion\" \/>\n<meta property=\"og:description\" content=\"Resolve the difference between use cases and user stories. Learn when to use each, avoid requirements confusion agile, and prevent scope creep in Agile delivery.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/\",\"name\":\"User Stories vs Use Cases Confusion\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:22:47+00:00\",\"description\":\"Resolve the difference between use cases and user stories. Learn when to use each, avoid requirements confusion agile, and prevent scope creep in Agile delivery.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Strategic and Conceptual Errors\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Confusing Use Cases and User Stories\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Stories vs Use Cases Confusion","description":"Resolve the difference between use cases and user stories. Learn when to use each, avoid requirements confusion agile, and prevent scope creep in Agile delivery.","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\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/","og_locale":"fr_FR","og_type":"article","og_title":"User Stories vs Use Cases Confusion","og_description":"Resolve the difference between use cases and user stories. Learn when to use each, avoid requirements confusion agile, and prevent scope creep in Agile delivery.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/","name":"User Stories vs Use Cases Confusion","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:22:47+00:00","description":"Resolve the difference between use cases and user stories. Learn when to use each, avoid requirements confusion agile, and prevent scope creep in Agile delivery.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/user-stories-vs-use-cases-confusion\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Strategic and Conceptual Errors","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/strategic-and-conceptual-errors\/"},{"@type":"ListItem","position":4,"name":"Confusing Use Cases and User Stories"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/685\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/682"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=685"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}