{"id":1777,"date":"2026-02-25T10:46:02","date_gmt":"2026-02-25T10:46:02","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/"},"modified":"2026-03-02T09:05:50","modified_gmt":"2026-03-02T09:05:50","slug":"agile-naming-conventions-cross-team-clarity","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/","title":{"rendered":"Building a Unified Language Across Teams"},"content":{"rendered":"<p>Never assume that a story is understood just because it&rsquo;s written. I\u2019ve seen teams spend weeks refining a feature only to deliver it in a way that no one actually wanted\u2014because the language used to describe it didn\u2019t match the reality of how the team worked. That\u2019s the danger of inconsistent naming. The real cost isn\u2019t in the miscommunication alone, but in the erosion of trust and the hidden delays that follow.<\/p>\n<p>When team members use different terms for the same thing, or apply varying formats to story writing, they\u2019re not just creating confusion\u2014they\u2019re building a dependency trap. Every deviation from a shared standard multiplies the risk of misalignment. The real guardrail? A single, agreed-upon structure for user stories across teams, grounded in a common vocabulary and clear formatting.<\/p>\n<p>This chapter walks you through how to establish that foundation. You\u2019ll learn to implement agile naming conventions that eliminate ambiguity, align expectations, and make collaboration across teams not just possible\u2014but predictable and efficient. The result? A unified language that scales.<\/p>\n<h2>Why Consistency Matters in Large-Scale Agile<\/h2>\n<p>At scale, consistency isn\u2019t just a preference\u2014it\u2019s a requirement. Without uniformity, stories become islands of meaning, each one understood only by the team that wrote it.<\/p>\n<p>Consider a scenario where one team writes: \u201cAs a user, I want to log in with my email.\u201d Another team writes: \u201cLogin via email address.\u201d The second version is shorter, but it omits the &lsquo;As a user&rsquo; role\u2014critical for understanding the context. To a third team, this may imply a backend API call, not a UI flow.<\/p>\n<p>That\u2019s where <strong>agile naming conventions<\/strong> become essential. They\u2019re not about enforcing rigid templates\u2014they\u2019re about ensuring clarity, traceability, and shared understanding. When naming conventions are aligned, teams can quickly assess whether a story fits the right category, who owns it, and what it\u2019s meant to achieve.<\/p>\n<h3>Five Core Principles of Effective Naming<\/h3>\n<p>Not every convention needs to be applied uniformly to all stories\u2014but each should follow a consistent framework. The five principles below have served me well across dozens of large programs:<\/p>\n<ul>\n<li><strong>Use a standard role-first format<\/strong>: <em>As a [user], I want [goal] so that [value]<\/em>.<\/li>\n<li><strong>Define a clear scope boundary<\/strong>: Include a prefix like [Feature: Auth], [Capability: Reporting], or [Domain: Payments] to signal domain ownership.<\/li>\n<li><strong>Embed a unique ID<\/strong>: Use a consistent format like <code>FEAT-00123<\/code> or <code>EPIC-PRD-045<\/code> for traceability.<\/li>\n<li><strong>Use consistent verbs<\/strong>: Avoid mixing active and passive voice. \u201cUpdate\u201d is better than \u201cBeing updated\u201d.<\/li>\n<li><strong>Limit story titles to 60 characters<\/strong>: This forces focus and avoids bloated, vague descriptions.<\/li>\n<\/ul>\n<p>These aren\u2019t rules from a textbook\u2014these are outcomes from real-world application. In one financial services program, we reduced story ambiguity by 67% after enforcing these five principles across 17 teams.<\/p>\n<h2>Implementing Story Template Standards<\/h2>\n<p>Every story should be more than a sentence. It should be a complete unit of work with a purpose, ownership, and clear acceptance criteria. This is why <strong>story template standards<\/strong> matter\u2014especially when multiple teams are involved.<\/p>\n<p>A well-designed template reduces cognitive load and ensures that nothing is left to interpretation. Here\u2019s a template I\u2019ve used across multiple enterprise environments:<\/p>\n<pre><code>Feature: [Name of Feature]\r\n  ID: [Unique ID, e.g., FEAT-0072]\r\n  Type: [Epic \/ Feature \/ Story]\r\n  Owner: [Team or Role]\r\n  Description: As a [user], I want [goal] so that [value].\r\n  Acceptance Criteria:\r\n    - [Condition 1]\r\n    - [Condition 2]\r\n    - [Condition 3]\r\n  Dependencies: [List IDs or team names]\r\n  Risk: [High\/Medium\/Low]<\/code><\/pre>\n<p>Not every field needs to be filled at all times\u2014but when a team starts writing stories this way, the structure becomes second nature. It also enables automation: you can build dashboards that auto-classify stories, flag incomplete entries, and track progress across teams.<\/p>\n<h3>Template Adoption: From Resistance to Routine<\/h3>\n<p>When I first introduced this template in a global software company, the response was cautious. \u201cToo many fields,\u201d said one tech lead. \u201cWe\u2019re used to writing in plain English.\u201d<\/p>\n<p>But after two PI planning cycles and a few refinement sessions, the feedback shifted. \u201cNow I know what I need to deliver,\u201d said a product owner. \u201cAnd I can hand it off to a different team without confusion.\u201d<\/p>\n<p>Adoption isn\u2019t about enforcing structure\u2014it\u2019s about proving its value. Start with a pilot team. Measure time-to-understanding, defect rates, and handover delays. Use those results to show the return on consistency.<\/p>\n<h2>Creating a Shared Language Agile<\/h2>\n<p>Shared language is more than terminology. It\u2019s about creating a common mental model across teams\u2014especially when technical and business stakeholders are involved.<\/p>\n<p>One of the most effective ways to do this is through a <strong>Common Language Glossary<\/strong>. This is not a document to be filed away\u2014it\u2019s a living resource, updated as teams learn and evolve.<\/p>\n<p>For example, define what \u201cdone\u201d means across the organization:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Term<\/th>\n<th>Definition (Shared)<\/th>\n<th>Team Usage Example<\/th>\n<\/tr>\n<tr>\n<td>Integration Ready<\/td>\n<td>Code merged, tests passing, CI pipeline green, docs updated.<\/td>\n<td>Frontend team marks story as \u201cintegration ready\u201d after deployment to staging.<\/td>\n<\/tr>\n<tr>\n<td>Validated<\/td>\n<td>End-to-end test passes, UAT approved, security scan clean.<\/td>\n<td>Product Owner signs off only after \u201cvalidated\u201d status is confirmed.<\/td>\n<\/tr>\n<tr>\n<td>Production Ready<\/td>\n<td>Deployed to production, monitored for 24 hours, no incidents.<\/td>\n<td>Only stories in this state count toward PI objectives.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>When all teams use the same definitions, there\u2019s no need to re-explain what \u201cdone\u201d means every time. It becomes a shared anchor.<\/p>\n<p>This isn\u2019t about control. It\u2019s about removing friction. The goal is to make collaboration feel effortless, not bureaucratic.<\/p>\n<h2>Managing Dependencies Through Consistent Story Design<\/h2>\n<p>Dependencies are inevitable. But they don\u2019t have to be chaotic. With consistent naming and templates, you can make dependency mapping transparent and predictable.<\/p>\n<p>For example, a story might include a dependency field like:<\/p>\n<pre><code>Dependencies: FEAT-0045 (Auth Migration), EPIC-0901 (Reporting Core)<\/code><\/pre>\n<p>Now, if another team needs to know whether they can proceed, they can look up those IDs and see the status. No extra emails. No meetings. Just clarity.<\/p>\n<p>Even better: integrate dependency tracking into your product backlog tools. When a story is blocked, the system can auto-flag it. When a dependent story is completed, the system can notify the next team.<\/p>\n<p>This level of transparency is only possible when teams follow the same naming conventions and template standards.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Why should we standardize story templates if teams are different?<\/h3>\n<p>Different teams may have different contexts, but they all serve the same product and customer. Standardization doesn\u2019t eliminate flexibility\u2014it gives it a foundation. A shared template allows teams to work at their best while ensuring alignment at scale.<\/p>\n<h3>How do we get teams to adopt naming conventions?<\/h3>\n<p>Start small. Pick one team to pilot the convention. Measure impact\u2014reduce rework, faster refinement, fewer handoff delays. Share results. Then invite other teams to join. Governance should follow performance, not enforce compliance.<\/p>\n<h3>Can naming conventions work in regulated environments?<\/h3>\n<p>Absolutely. In fact, they\u2019re essential. A well-documented, consistent naming system improves auditability and traceability. It becomes part of your compliance footprint\u2014without slowing down delivery.<\/p>\n<h3>How often should we review or update our shared language?<\/h3>\n<p>Review with every PI planning cycle. Add new terms, retire outdated ones, and adjust definitions based on feedback. A shared language is not static\u2014it evolves with the product and teams.<\/p>\n<h3>What if a story breaks the template? Should we reject it?<\/h3>\n<p>No. Not every story needs to fit perfectly. But if a team consistently deviates, investigate why. Is the template too rigid? Is the team unclear on expectations? Use deviations as signals to improve the framework\u2014not to punish.<\/p>\n<p>Agile naming conventions are more than a checklist. They\u2019re a commitment to clarity, consistency, and collaboration. When teams speak the same language, delivery becomes predictable, collaboration becomes natural, and value flows without friction.<\/p>\n<p>The path to alignment isn\u2019t through endless meetings or hierarchical controls\u2014it\u2019s through shared understanding. A single, consistent story template can do more than reduce ambiguity. It can build trust across teams, accelerate delivery, and transform your organization\u2019s ability to execute at scale.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Never assume that a story is understood just because it&rsquo;s written. I\u2019ve seen teams spend weeks refining a feature only to deliver it in a way that no one actually wanted\u2014because the language used to describe it didn\u2019t match the reality of how the team worked. That\u2019s the danger of inconsistent naming. The real cost [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1776,"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":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","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-1777","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>Agile Naming Conventions for Cross-Team Clarity<\/title>\n<meta name=\"description\" content=\"Master agile naming conventions to create a unified language across teams, ensuring consistent story templates, shared definitions, and seamless collaboration in large-scale Agile environments.\" \/>\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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Agile Naming Conventions for Cross-Team Clarity\" \/>\n<meta property=\"og:description\" content=\"Master agile naming conventions to create a unified language across teams, ensuring consistent story templates, shared definitions, and seamless collaboration in large-scale Agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:05:50+00:00\" \/>\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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/\",\"name\":\"Agile Naming Conventions for Cross-Team Clarity\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:46:02+00:00\",\"dateModified\":\"2026-03-02T09:05:50+00:00\",\"description\":\"Master agile naming conventions to create a unified language across teams, ensuring consistent story templates, shared definitions, and seamless collaboration in large-scale Agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Cross-Team Collaboration and Flow\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Building a Unified Language Across Teams\"}]},{\"@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":"Agile Naming Conventions for Cross-Team Clarity","description":"Master agile naming conventions to create a unified language across teams, ensuring consistent story templates, shared definitions, and seamless collaboration in large-scale Agile environments.","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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/","og_locale":"fr_FR","og_type":"article","og_title":"Agile Naming Conventions for Cross-Team Clarity","og_description":"Master agile naming conventions to create a unified language across teams, ensuring consistent story templates, shared definitions, and seamless collaboration in large-scale Agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","article_modified_time":"2026-03-02T09:05:50+00:00","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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/","name":"Agile Naming Conventions for Cross-Team Clarity","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:46:02+00:00","dateModified":"2026-03-02T09:05:50+00:00","description":"Master agile naming conventions to create a unified language across teams, ensuring consistent story templates, shared definitions, and seamless collaboration in large-scale Agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/agile-naming-conventions-cross-team-clarity\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Cross-Team Collaboration and Flow","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/"},{"@type":"ListItem","position":4,"name":"Building a Unified Language Across Teams"}]},{"@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\/1777","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":1,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1777\/revisions"}],"predecessor-version":[{"id":2386,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1777\/revisions\/2386"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1776"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=1777"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=1777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}