{"id":679,"date":"2026-02-25T10:22:44","date_gmt":"2026-02-25T10:22:44","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/"},"modified":"2026-02-25T10:22:44","modified_gmt":"2026-02-25T10:22:44","slug":"context-missing-user-story","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/","title":{"rendered":"Assuming Everyone Knows the Context"},"content":{"rendered":"<p>It\u2019s common to see a story like \u201cAs a user, I want to save my progress\u201d accepted into a sprint. The team starts coding, only to realize halfway through that \u201csaving\u201d means different things to different users\u2014some want auto-save, others expect manual confirmation, and the backend uses a completely different persistence model.<\/p>\n<p>This isn\u2019t a coding mistake. It\u2019s a breakdown in context. You don\u2019t need to be a product owner to recognize that a story without context becomes a liability. I\u2019ve seen teams waste entire sprints on features no one actually wanted\u2014just because the context was assumed, not documented.<\/p>\n<p>What you\u2019ll learn here isn\u2019t just theory. You\u2019ll get a field-tested framework for diagnosing and fixing context gaps using tangible tools. This chapter gives you practical steps to ensure every user story is a shared understanding, not a guessing game.<\/p>\n<h2>Why Context Matters in Agile Story Writing<\/h2>\n<p>Agile isn\u2019t about replacing documentation. It\u2019s about replacing ambiguity with clarity through collaboration.<\/p>\n<p>Stories are placeholders for conversation, not blueprints. When the context is missing, the conversation dies before it starts. The team guesses. The product owner reworks. The sprint fails.<\/p>\n<p>Here\u2019s what happens when context is assumed:<\/p>\n<ul>\n<li>Developers interpret \u201csave\u201d as auto-saving, but the product owner meant a manual button.<\/li>\n<li>QA tests fail because the expected behavior wasn\u2019t in the story.<\/li>\n<li>UAT reveals the feature doesn\u2019t solve the real user pain point.<\/li>\n<\/ul>\n<p>This isn\u2019t scope creep. It\u2019s a failure to define the environment, constraints, and user intent.<\/p>\n<h3>What Is \u201cContext\u201d in a User Story?<\/h3>\n<p>Context isn\u2019t just background. It\u2019s the shared understanding of:<\/p>\n<ul>\n<li>Who the user really is (not \u201ca user,\u201d but a \u201cretired teacher using a tablet in rural India\u201d)<\/li>\n<li>What environment they\u2019re in (low bandwidth, high stress, mobile-first)<\/li>\n<li>What they\u2019re trying to achieve beyond the feature<\/li>\n<li>What success looks like in real-world terms<\/li>\n<\/ul>\n<p>Without this, every story feels like a puzzle with missing pieces. The team may build it\u2014correctly\u2014but it still doesn\u2019t deliver value.<\/p>\n<h2>How to Fix a Story With Missing Context<\/h2>\n<p>Context isn\u2019t something you add after writing. It\u2019s built in. The best way to fix a context missing user story is to prevent it in the first place.<\/p>\n<h3>1. Use the \u201cThree C\u2019s\u201d Framework<\/h3>\n<p>Every story should be written with three elements:<\/p>\n<ol>\n<li><strong>Card<\/strong> \u2013 The concise story statement.<\/li>\n<li><strong>Conversation<\/strong> \u2013 The dialogue that clarifies it.<\/li>\n<li><strong>Confirmation<\/strong> \u2013 The acceptance criteria that define success.<\/li>\n<\/ol>\n<p>The card alone is never enough. The conversation must include context.<\/p>\n<h3>2. Add a Context Box to Every Story<\/h3>\n<p>Include a \u201cContext\u201d section right below the story. Use this format:<\/p>\n<pre><code>Context:\n- User: A freelance writer using a Chromebook\n- Environment: 4G connection, limited storage\n- Goal: Avoid losing work during unexpected shutdowns\n- Constraints: No access to cloud sync during offline mode\n- Success: Auto-save every 90 seconds, with confirmation toast<\/code><\/pre>\n<p>This transforms a vague story into an actionable, testable task.<\/p>\n<h3>3. Use Story Maps for Visual Context<\/h3>\n<p>Story maps are more than a backlog view\u2014they\u2019re a shared mental model of user journeys.<\/p>\n<p>When you map features by user workflow, you force the team to think in context. A story like \u201cSave progress\u201d only makes sense when placed in sequence: \u201cStart writing \u2192 Type for 10 minutes \u2192 Editor crashes \u2192 Reconnect \u2192 Resume.\u201d<\/p>\n<p>Visual context prevents isolated, disconnected tasks.<\/p>\n<h3>4. Document Context in a Living Artifact<\/h3>\n<p>Don\u2019t rely on memory. Use a shared artifact like a:<\/p>\n<ul>\n<li>User persona board<\/li>\n<li>Customer journey map<\/li>\n<li>Product vision document<\/li>\n<li>Feature decision log<\/li>\n<\/ul>\n<p>These aren\u2019t documentation for documentation\u2019s sake. They\u2019re conversation anchors. When someone asks, \u201cWhy are we building this?\u201d the answer lives here\u2014not in a story.<\/p>\n<p>Example:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Story<\/th>\n<th>Context Documentation<\/th>\n<\/tr>\n<tr>\n<td>As a teacher, I want to save my lesson plan so I don\u2019t lose it during a power outage.<\/td>\n<td>Context: Teachers in rural schools use older devices with unreliable power. They often work offline. Auto-save every 2 minutes is critical.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Shared Understanding Agile: The Real Goal<\/h2>\n<p>Agile isn\u2019t about speed. It\u2019s about alignment. The goal isn\u2019t to write more stories\u2014it\u2019s to write stories that everyone understands.<\/p>\n<p>Shared understanding agile means: every team member can answer, \u201cWhy are we doing this?\u201d and \u201cWho benefits?\u201d without asking.<\/p>\n<p>When context is missing, the team is not aligned. When context is clear, decisions are faster, rework drops, and delivery becomes predictable.<\/p>\n<h3>How to Measure Story Context Quality<\/h3>\n<p>Use this checklist to assess whether a story has sufficient context:<\/p>\n<ul>\n<li>\u2705 Is the user role specific?<\/li>\n<li>\u2705 Are real-world constraints included (e.g., bandwidth, device, access)?<\/li>\n<li>\u2705 Is the success condition tied to a real user outcome?<\/li>\n<li>\u2705 Is this story linked to a journey map or persona?<\/li>\n<li>\u2705 Could a new team member understand this without asking?<\/li>\n<\/ul>\n<p>If you answer \u201cno\u201d to any, the story needs context.<\/p>\n<h2>Real-World Example: The Missing Context in Healthcare<\/h2>\n<p>A hospital\u2019s digital intake system had a story: \u201cAs a patient, I want to submit my forms online.\u201d<\/p>\n<p>It was accepted. The team built a form. But users couldn\u2019t complete it. Why?<\/p>\n<p>Context was missing. The patients were elderly, using smartphones with small screens. The form had 25 fields. No mobile optimization. No help text. No error guidance.<\/p>\n<p>After adding context\u2014specifically, the persona of \u201cEvelyn, 72, uses an Android tablet, lives in a rural area, has mild vision impairment\u201d\u2014the team redesigned the form with larger text, progressive reveal, and voice input.<\/p>\n<p>Completion rate jumped from 18% to 87%.<\/p>\n<p>This wasn\u2019t a technical fix. It was a context fix.<\/p>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li>Assuming context leads to misalignment, rework, and wasted effort.<\/li>\n<li>Context missing user story is a symptom of deeper process gaps.<\/li>\n<li>Use shared artifacts like personas, journey maps, and context boxes to build story context documentation.<\/li>\n<li>Shared understanding agile is achieved not by writing more stories, but by writing clearer ones.<\/li>\n<\/ul>\n<p>Stop assuming. Start documenting. The team you save might be your future self.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What if the team says context is too slow to document?<\/h3>\n<p>Context isn\u2019t a burden\u2014it\u2019s a shortcut. Without it, you spend more time fixing misinterpreted stories than building them. The time saved in rework is always greater than the time spent on context.<\/p>\n<h3>Can I use story context documentation in any Agile framework?<\/h3>\n<p>Absolutely. Whether you\u2019re in Scrum, Kanban, SAFe, or XP, context is essential. The format may vary, but the need remains. Story maps, personas, and context boxes work across frameworks.<\/p>\n<h3>How often should I revisit story context documentation?<\/h3>\n<p>Revisit it during sprint planning, refinement, and retrospectives. If the user base changes, or the product evolves, context updates are essential. Treat it as a living document.<\/p>\n<h3>Do I need a dedicated person to maintain context?<\/h3>\n<p>No. The product owner, team leads, and even developers should contribute. But ownership should be shared. If no one owns context, it dies.<\/p>\n<h3>Can visual tools like story mapping replace written context?<\/h3>\n<p>Not entirely. Story maps show flow and sequence, but written context explains intent, constraints, and user motivations. Use them together.<\/p>\n<h3>What if the product owner doesn\u2019t understand the need for context?<\/h3>\n<p>Bring in real user data. Show the difference between a story built with context and one without. Use metrics: completion rate, usability testing, rework. The data will convince.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It\u2019s common to see a story like \u201cAs a user, I want to save my progress\u201d accepted into a sprint. The team starts coding, only to realize halfway through that \u201csaving\u201d means different things to different users\u2014some want auto-save, others expect manual confirmation, and the backend uses a completely different persistence model. This isn\u2019t a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":676,"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-679","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>Context Missing User Story: Fix Breakdowns in Agile<\/title>\n<meta name=\"description\" content=\"Stop miscommunication in Agile. Learn how to fix context missing user story issues with shared understanding agile, story context documentation, and visual artifacts to ensure every story gets built right the first time.\" \/>\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\/collaboration-issues-in-user-stories\/context-missing-user-story\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Context Missing User Story: Fix Breakdowns in Agile\" \/>\n<meta property=\"og:description\" content=\"Stop miscommunication in Agile. Learn how to fix context missing user story issues with shared understanding agile, story context documentation, and visual artifacts to ensure every story gets built right the first time.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/\" \/>\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=\"6 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\/collaboration-issues-in-user-stories\/context-missing-user-story\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/\",\"name\":\"Context Missing User Story: Fix Breakdowns in Agile\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:22:44+00:00\",\"description\":\"Stop miscommunication in Agile. Learn how to fix context missing user story issues with shared understanding agile, story context documentation, and visual artifacts to ensure every story gets built right the first time.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/#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\":\"Process and Collaboration Pitfalls\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Assuming Everyone Knows the Context\"}]},{\"@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":"Context Missing User Story: Fix Breakdowns in Agile","description":"Stop miscommunication in Agile. Learn how to fix context missing user story issues with shared understanding agile, story context documentation, and visual artifacts to ensure every story gets built right the first time.","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\/collaboration-issues-in-user-stories\/context-missing-user-story\/","og_locale":"fr_FR","og_type":"article","og_title":"Context Missing User Story: Fix Breakdowns in Agile","og_description":"Stop miscommunication in Agile. Learn how to fix context missing user story issues with shared understanding agile, story context documentation, and visual artifacts to ensure every story gets built right the first time.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/","name":"Context Missing User Story: Fix Breakdowns in Agile","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:22:44+00:00","description":"Stop miscommunication in Agile. Learn how to fix context missing user story issues with shared understanding agile, story context documentation, and visual artifacts to ensure every story gets built right the first time.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/context-missing-user-story\/#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":"Process and Collaboration Pitfalls","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/"},{"@type":"ListItem","position":4,"name":"Assuming Everyone Knows the Context"}]},{"@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\/679","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\/679\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/676"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=679"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=679"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}