{"id":693,"date":"2026-02-25T10:22:51","date_gmt":"2026-02-25T10:22:51","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/"},"modified":"2026-02-25T10:22:51","modified_gmt":"2026-02-25T10:22:51","slug":"user-story-documentation-traceability","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/","title":{"rendered":"Poor Traceability and Documentation Hygiene"},"content":{"rendered":"<p>When a team starts discussing a story and immediately pulls up a diagram\u2014no hesitation, no explanation\u2014only a shared understanding of the visual model, that\u2019s the signal. You\u2019ve moved from \u201cwriting stories\u201d to \u201coperating from alignment.\u201d That\u2019s the moment when documentation hygiene isn\u2019t a chore, but a shared language. I\u2019ve seen this in teams where the story text, acceptance criteria, and decision tables all evolve in sync. It\u2019s not about perfection. It\u2019s about consistency, and a discipline that prevents stories from becoming disconnected from reality.<\/p>\n<p>What you\u2019ll gain here is not theory. It\u2019s a clear, repeatable method to maintain alignment between story text, visual models, and system documentation. I\u2019ve used this with teams across financial services, SaaS, and government systems\u2014where misalignment meant weeks of rework. This chapter gives you the tools to avoid that, step by step.<\/p>\n<h2>Why Traceability Breaks Down in Agile Teams<\/h2>\n<p>Traceability isn\u2019t a feature. It\u2019s a habit. And habits fail when there\u2019s no enforcement. Too often, teams treat user stories as isolated text blocks, disconnected from diagrams, acceptance criteria, or decision logic.<\/p>\n<p>One team I worked with had a story: \u201cAs a customer, I want to reset my password so I can regain access.\u201d The acceptance criteria were written. The developers built it. Then QA found it didn\u2019t work for users with expired accounts. The story didn\u2019t mention account status. The model didn\u2019t reflect it. The acceptance criteria were silent.<\/p>\n<p>That\u2019s not a bug. That\u2019s traceability failure. A story should reflect decisions made in models\u2014and those decisions should be visible in the story\u2019s text.<\/p>\n<h3>The Cost of Disconnected Artifacts<\/h3>\n<p>When stories live in isolation from models, you get:<\/p>\n<ul>\n<li>Revisions after implementation because the model wasn\u2019t updated.<\/li>\n<li>Repeated rework when a story\u2019s intent diverges from the system\u2019s logic.<\/li>\n<li>Confusion during refinement: \u201cDid we mean this or that?\u201d<\/li>\n<li>Failure to validate logic under edge cases.<\/li>\n<\/ul>\n<p>These are not just technical debt. They are cognitive debt. The team is constantly decoding what was meant, not building what was wanted.<\/p>\n<h2>Building Traceability with Decision Tables<\/h2>\n<p>Decision tables are the glue between story text and system logic. They translate requirements into testable rules. The best ones are built in parallel with the story, not after.<\/p>\n<p>Start with a simple example:<\/p>\n<p><strong>Story:<\/strong> As a user, I want to qualify for a loan so that I can purchase a home.<\/p>\n<p>Now, define the acceptance rules. Use a decision table to map conditions and outcomes.<\/p>\n<table>\n<thead>\n<tr>\n<th>Loan Type<\/th>\n<th>Credit Score \u2265 700<\/th>\n<th>Debt-to-Income Ratio \u2264 36%<\/th>\n<th>Employment \u2265 2 Years<\/th>\n<th>Eligible?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Conventional<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<\/tr>\n<tr>\n<td>Conventional<\/td>\n<td>No<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>FHA<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<td>Yes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This table doesn\u2019t replace the story. It makes the story\u2019s edge cases visible. Now, when someone asks, \u201cWhat if someone has a 690 score but strong income?\u201d\u2014you already have a rule to point to.<\/p>\n<h3>How to Integrate Decision Tables with User Stories<\/h3>\n<p>Use this workflow:<\/p>\n<ol>\n<li>Write the user story first\u2014focus on value.<\/li>\n<li>Identify the key decision points: eligibility, approval, rejection.<\/li>\n<li>Create a decision table in parallel with acceptance criteria.<\/li>\n<li>Link the table directly in the story\u2019s documentation or via a reference ID.<\/li>\n<li>Update both story and table during refinement.<\/li>\n<\/ol>\n<p>This is agile documentation alignment in action. The story and model evolve together.<\/p>\n<h2>Using Visual Paradigm to Enforce Traceability<\/h2>\n<p>Visual Paradigm isn\u2019t just a diagramming tool. It\u2019s a traceability engine. When you model a system, every business rule, every state transition, every condition can be linked directly to a story.<\/p>\n<p>Here\u2019s how:<\/p>\n<ul>\n<li>Model the loan eligibility process in a BPMN or state machine diagram.<\/li>\n<li>Label each decision node with a reference to the story ID or a decision table.<\/li>\n<li>Use the tool\u2019s traceability matrix to map each story to every relevant rule and diagram element.<\/li>\n<li>Mark incomplete or ambiguous links as \u201cpending\u201d until the team resolves them.<\/li>\n<\/ul>\n<p>Teams using traceability visual paradigm tools report 40% fewer story reworks. Not because they write better, but because they see the gaps before coding begins.<\/p>\n<h3>Linking Stories to Models: A Practical Example<\/h3>\n<p>Imagine this story: \u201cAs a customer, I want to apply for a mortgage so that I can buy a house.\u201d<\/p>\n<p>Now, in Visual Paradigm, you create a process model. The first step is \u201cVerify Creditworthiness.\u201d You label that node with:<\/p>\n<pre><code>Ref: US-0012 | Decision Table: Eligibility Rules v2.1<\/code><\/pre>\n<p>When a developer opens the story, they don\u2019t just read text. They open the model, see the logic, and know which rules apply. That\u2019s user story documentation traceability at its best.<\/p>\n<h2>Maintaining Documentation Hygiene<\/h2>\n<p>Traceability doesn\u2019t happen by accident. It requires discipline. Here\u2019s how I\u2019ve seen it work in real teams:<\/p>\n<h3>4 Keys to Documentation Hygiene<\/h3>\n<ol>\n<li><strong>One Source of Truth<\/strong>: Choose one platform for models (e.g., Visual Paradigm), and keep all stories, tables, and diagrams linked to it.<\/li>\n<li><strong>Version Control for Models<\/strong>: Treat models like code. Tag versions. Update them when stories change.<\/li>\n<li><strong>Traceability Checks in Refinement<\/strong>: Add a step: \u201cDoes this story reference a model or decision table? Is the link valid?\u201d<\/li>\n<li><strong>Automated Audits<\/strong>: Use tools to flag stories without linked models or outdated references.<\/li>\n<\/ol>\n<p>These aren\u2019t process overhead. They\u2019re safeguards. They prevent stories from drifting from their original intent.<\/p>\n<h3>Common Pitfalls to Avoid<\/h3>\n<p>Even with the best intentions, traceability breaks. Watch for:<\/p>\n<ul>\n<li><strong>Story-Only Mindset<\/strong>: Assuming the story text is enough. It\u2019s not.<\/li>\n<li><strong>Static Models<\/strong>: Creating diagrams once and ignoring updates. Models must evolve with the backlog.<\/li>\n<li><strong>Over-Engineering<\/strong>: Building complex decision tables for simple rules. Keep it lean.<\/li>\n<li><strong>Disconnected Tools<\/strong>: Using separate platforms for stories, models, and documentation. Unify them.<\/li>\n<\/ul>\n<p>Agile documentation alignment isn\u2019t about how much you document. It\u2019s about how well your documentation reflects reality\u2014and how fast you can update it.<\/p>\n<h2>How to Start Today<\/h2>\n<p>You don\u2019t need to overhaul your tooling. Start small.<\/p>\n<ol>\n<li>Take one story from your backlog.<\/li>\n<li>Create a decision table for its acceptance rules.<\/li>\n<li>Link it to a simple diagram in Visual Paradigm (or any modeler).<\/li>\n<li>During refinement, say: \u201cShow me the model this story references.\u201d<\/li>\n<li>Repeat until it becomes second nature.<\/li>\n<\/ol>\n<p>That\u2019s the path. Not perfection. Progress.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I link a user story to a decision table?<\/h3>\n<p>Use a reference ID. In the story\u2019s description or acceptance criteria, add: \u201cSee decision table: Eligibility Rules v2.1.\u201d Keep the table in a shared location\u2014like a Visual Paradigm project or Confluence page\u2014and update it when requirements change.<\/p>\n<h3>Can decision tables replace acceptance criteria?<\/h3>\n<p>No. They complement them. Decision tables define the logic behind acceptance rules. Acceptance criteria describe the behavior. Use both: criteria for readability, tables for precision.<\/p>\n<h3>How often should I update models and stories?<\/h3>\n<p>Every time the story is refined. If a story changes\u2014new condition, new rule\u2014update the linked model and decision table simultaneously. Use versioning to track changes.<\/p>\n<h3>What if my team resists using diagrams or tables?<\/h3>\n<p>Start with one story. Show how it prevented a misinterpretation. Use real examples. The team will see the return on investment. Then scale.<\/p>\n<h3>Do I need a model for every story?<\/h3>\n<p>No. Only for complex logic, business rules, or systems with multiple states. For simple stories\u2014\u201cAs a user, I want to sign in\u201d\u2014a model may be overkill. But when ambiguity exists, create it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a team starts discussing a story and immediately p [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":688,"menu_order":4,"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-693","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 Documentation Traceability Made Practical<\/title>\n<meta name=\"description\" content=\"Master user story documentation traceability with real-world strategies for agile teams. Align stories, models, and system docs using Visual Paradigm and agile documentation alignment techniques.\" \/>\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\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Documentation Traceability Made Practical\" \/>\n<meta property=\"og:description\" content=\"Master user story documentation traceability with real-world strategies for agile teams. Align stories, models, and system docs using Visual Paradigm and agile documentation alignment techniques.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/\",\"name\":\"User Story Documentation Traceability Made Practical\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:22:51+00:00\",\"description\":\"Master user story documentation traceability with real-world strategies for agile teams. Align stories, models, and system docs using Visual Paradigm and agile documentation alignment techniques.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scaling and Lifecycle Issues\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Poor Traceability and Documentation Hygiene\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Documentation Traceability Made Practical","description":"Master user story documentation traceability with real-world strategies for agile teams. Align stories, models, and system docs using Visual Paradigm and agile documentation alignment techniques.","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\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/","og_locale":"zh_CN","og_type":"article","og_title":"User Story Documentation Traceability Made Practical","og_description":"Master user story documentation traceability with real-world strategies for agile teams. Align stories, models, and system docs using Visual Paradigm and agile documentation alignment techniques.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"6 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/","name":"User Story Documentation Traceability Made Practical","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:22:51+00:00","description":"Master user story documentation traceability with real-world strategies for agile teams. Align stories, models, and system docs using Visual Paradigm and agile documentation alignment techniques.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/user-story-documentation-traceability\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Scaling and Lifecycle Issues","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/"},{"@type":"ListItem","position":4,"name":"Poor Traceability and Documentation Hygiene"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/693","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/693\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/688"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=693"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=693"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}