{"id":1161,"date":"2026-02-25T10:36:52","date_gmt":"2026-02-25T10:36:52","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/"},"modified":"2026-02-25T10:36:52","modified_gmt":"2026-02-25T10:36:52","slug":"dfd-documentation-sustaining-system-clarity","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/","title":{"rendered":"Using DFDs in System Documentation and Maintenance"},"content":{"rendered":"<p>Most teams start with a DFD because it\u2019s intuitive\u2014something about the flow of arrows and boxes feels like a direct translation of how data moves through a system. But relying on that initial intuition often leads to diagrams that lose meaning over time. I\u2019ve seen projects where the original DFDs were annotated only with initials, with no traceability or version control\u2014and six months later, no one remembers why a flow was drawn or what data it represented.<\/p>\n<p>That\u2019s why DFD documentation must be more than a sketch. It\u2019s a living artifact. As someone who\u2019s guided DFD adoption across financial, healthcare, and government systems, I\u2019ve learned that the real value isn\u2019t in drawing the diagram once\u2014it\u2019s in ensuring it evolves with the system, remains consistent, and supports long-term governance.<\/p>\n<p>This chapter walks you through how to embed DFDs into a structured documentation framework that supports change management, audit trails, and team collaboration. You\u2019ll learn how to define what it means to sustain DFD over time, use consistent naming, and integrate models into documentation repositories that don\u2019t lose momentum.<\/p>\n<h2>Embedding DFDs in a System Documentation Framework<\/h2>\n<p>Think of DFDs not as standalone diagrams, but as components of a larger documentation ecosystem. When done well, they become part of the system\u2019s DNA\u2014visible, verifiable, and traceable.<\/p>\n<p>Start by integrating DFDs into a dedicated documentation repository. Use a version-controlled system like Git with a structured folder hierarchy:<\/p>\n<ul>\n<li>docs\/diagrams\/dfds<\/li>\n<li>docs\/diagrams\/dfds\/context<\/li>\n<li>docs\/diagrams\/dfds\/level1<\/li>\n<li>docs\/diagrams\/dfds\/level2<\/li>\n<\/ul>\n<p>Each level should have its own diagram file and a corresponding metadata file (e.g., <code>level1-finance.json<\/code>) containing:<\/p>\n<ul>\n<li>Author and date of creation<\/li>\n<li>Version number and change log<\/li>\n<li>Reference to the parent DFD<\/li>\n<li>Link to the related requirement or user story<\/li>\n<\/ul>\n<p>These metadata files are what let you sustain DFD over time\u2014not just visually, but contextually.<\/p>\n<h3>Aligning DFDs with Change Management Systems<\/h3>\n<p>Every time a process changes\u2014say, a new approval step is added to a payment workflow\u2014the DFD must reflect that. But it shouldn\u2019t be updated in isolation.<\/p>\n<p>Link each DFD update to a change request (CR) in your system. For example:<\/p>\n<ul>\n<li>CR-405: Add fraud check to payment processing<\/li>\n<li>Impact: Level 1 DFD &#8211; Add process 3.2 \u201cFraud Risk Assessment\u201d<\/li>\n<li>Related DFD: <code>dfds\/level1-payment-process.png<\/code><\/li>\n<li>Approved by: Jane Doe, Lead Analyst<\/li>\n<\/ul>\n<p>This creates a trail. When auditors come through, you can show not just the final DFD, but the evolution of decisions that led to it.<\/p>\n<p>Use a change log table to track updates across all levels:<\/p>\n<table>\n<tbody>\n<tr>\n<th>CR ID<\/th>\n<th>Change Description<\/th>\n<th>DFD Level<\/th>\n<th>Updated File<\/th>\n<th>Date<\/th>\n<\/tr>\n<tr>\n<td>CR-405<\/td>\n<td>Added fraud check<\/td>\n<td>Level 1<\/td>\n<td>dfds\/level1-payment-process.png<\/td>\n<td>2024-03-15<\/td>\n<\/tr>\n<tr>\n<td>CR-412<\/td>\n<td>Renamed \u201cCustomer Info\u201d to \u201cClient Profile\u201d<\/td>\n<td>Level 0<\/td>\n<td>dfds\/context.png<\/td>\n<td>2024-03-18<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Keep this list updated. It\u2019s not just a log\u2014it\u2019s a maintenance roadmap.<\/p>\n<h2>Practical Strategies for Sustaining DFD Over Time<\/h2>\n<p>Over time, DFDs degrade when they\u2019re not reviewed or when team members leave. But these challenges are avoidable with structured habits.<\/p>\n<h3>1. Schedule Regular DFD Audits<\/h3>\n<p>Set a cadence\u2014every 6 months is a good baseline. During the audit, ask:<\/p>\n<ul>\n<li>Are all data flows still valid? (Check with current system logs)<\/li>\n<li>Has any process been removed or replaced?<\/li>\n<li>Are data stores still needed or have they been migrated?<\/li>\n<li>Do input\/output balances still match across levels?<\/li>\n<\/ul>\n<p>Use the DFD balancing checklist from the previous chapter as a foundation. Run the audit with the team that owns the system\u2014don\u2019t hand it off to a junior analyst.<\/p>\n<h3>2. Anchor DFDs to Requirements and User Stories<\/h3>\n<p>Every process, data store, and flow must trace back to a source. When requirements change, the DFD must reflect that.<\/p>\n<p>Use a traceability matrix to map each DFD element to its requirement or user story:<\/p>\n<table>\n<tbody>\n<tr>\n<th>DFD Element<\/th>\n<th>Type<\/th>\n<th>Source Requirement<\/th>\n<th>User Story ID<\/th>\n<\/tr>\n<tr>\n<td>Process 2.1<\/td>\n<td>Process<\/td>\n<td>REQ-FIN-003<\/td>\n<td>US-102<\/td>\n<\/tr>\n<tr>\n<td>Customer Data Store<\/td>\n<td>Data Store<\/td>\n<td>REQ-FIN-005<\/td>\n<td>US-104<\/td>\n<\/tr>\n<tr>\n<td>Payment Approval Flow<\/td>\n<td>Data Flow<\/td>\n<td>REQ-FIN-007<\/td>\n<td>US-106<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This isn\u2019t just for compliance\u2014it\u2019s for clarity. When a stakeholder asks, \u201cWhy is this flow here?\u201d you can point to the requirement and the user story.<\/p>\n<h3>3. Version Control with Meaningful Labels<\/h3>\n<p>Never rely on \u201cv1.0\u201d or \u201cfinal version.\u201d Instead, use semantic versioning:<\/p>\n<ul>\n<li><code>1.0.0<\/code> \u2013 Initial release, approved<\/li>\n<li><code>1.1.0<\/code> \u2013 Added fraud checks, minor changes<\/li>\n<li><code>1.1.1<\/code> \u2013 Minor typo fix in process label<\/li>\n<li><code>2.0.0<\/code> \u2013 Major restructure: redesigned level 1<\/li>\n<\/ul>\n<p>Tag each version in your repository. When a new version is merged, update the <code>README.md<\/code> with the changes and a link to the diff.<\/p>\n<h2>Integrating DFDs into Enterprise Governance<\/h2>\n<p>For organizations with regulatory obligations, DFDs are more than design tools\u2014they\u2019re evidence.<\/p>\n<p>GDPR, SOX, HIPAA: they all require transparency in data movement. DFDs provide a clean, visual audit trail.<\/p>\n<p>When a system is audited, the auditor doesn\u2019t just look at code. They look at how data flows between systems, who has access, and what\u2019s logged.<\/p>\n<p>Include a <strong>DFD Compliance Summary<\/strong> in your documentation package:<\/p>\n<ul>\n<li>System name: Finance Processing Engine<\/li>\n<li>Compliance standards: GDPR, SOX<\/li>\n<li>Key data flows requiring encryption: Payment Data, Customer PII<\/li>\n<li>Approved by: Compliance Officer \u2013 Alex Lin<\/li>\n<li>Last reviewed: 2024-04-01<\/li>\n<\/ul>\n<p>Attach the relevant DFDs (e.g., Level 1, Level 2) and highlight data flows that are subject to regulation.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How often should I update my DFD documentation?<\/h3>\n<p>Update DFDs at least every 6 months, or immediately after any change to the system. Use version control and link updates to change requests. This ensures your documentation reflects reality\u2014and survives team turnover.<\/p>\n<h3>Can DFDs be used in agile environments?<\/h3>\n<p>Absolutely. DFDs are especially valuable in agile for identifying data flows before implementation. Use them during backlog refinement to extract user stories and define system boundaries. Keep them simple and evolve them with each sprint.<\/p>\n<h3>What if team members don\u2019t understand the DFDs?<\/h3>\n<p>Start with a visual glossary. Include icons, labeling standards, and short explanations for each symbol. Run a 15-minute walkthrough during onboarding. The goal isn\u2019t perfection\u2014it\u2019s shared understanding.<\/p>\n<h3>How do I ensure DFDs stay balanced during updates?<\/h3>\n<p>Always validate input and output data flows against the parent diagram. Use the DFD balancing checklist: every incoming flow must be explained, and every outgoing flow must have a source. If a flow is added, verify it\u2019s not duplicating another flow.<\/p>\n<h3>Should I include DFDs in the user manual?<\/h3>\n<p>No. DFDs are for system analysts and developers. For users, use simplified flowcharts or process diagrams. But include DFDs in the technical documentation\u2014this is where they belong.<\/p>\n<h3>How do I handle DFDs when systems are migrated or replaced?<\/h3>\n<p>Document the migration path. Show the old DFDs and new DFDs side by side. Use a migration log that notes what data was moved, transformed, or discarded. This maintains traceability and supports post-migration audits.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most teams start with a DFD because it\u2019s intuitive\u2014something about the flow of arrows and boxes feels like a direct translation of how data moves through a system. But relying on that initial intuition often leads to diagrams that lose meaning over time. I\u2019ve seen projects where the original DFDs were annotated only with initials, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1157,"menu_order":3,"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-1161","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>DFD Documentation: Sustaining System Clarity Over Time<\/title>\n<meta name=\"description\" content=\"Learn how to embed balanced DFDs into long-term system documentation, ensuring traceability, compliance, and sustainable maintenance across evolving projects.\" \/>\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\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DFD Documentation: Sustaining System Clarity Over Time\" \/>\n<meta property=\"og:description\" content=\"Learn how to embed balanced DFDs into long-term system documentation, ensuring traceability, compliance, and sustainable maintenance across evolving projects.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/\",\"name\":\"DFD Documentation: Sustaining System Clarity Over Time\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:36:52+00:00\",\"description\":\"Learn how to embed balanced DFDs into long-term system documentation, ensuring traceability, compliance, and sustainable maintenance across evolving projects.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering Data Flow Diagram Levels and Balancing\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World Application and Governance\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Using DFDs in System Documentation and Maintenance\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"DFD Documentation: Sustaining System Clarity Over Time","description":"Learn how to embed balanced DFDs into long-term system documentation, ensuring traceability, compliance, and sustainable maintenance across evolving projects.","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\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/","og_locale":"pt_PT","og_type":"article","og_title":"DFD Documentation: Sustaining System Clarity Over Time","og_description":"Learn how to embed balanced DFDs into long-term system documentation, ensuring traceability, compliance, and sustainable maintenance across evolving projects.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/","name":"DFD Documentation: Sustaining System Clarity Over Time","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:36:52+00:00","description":"Learn how to embed balanced DFDs into long-term system documentation, ensuring traceability, compliance, and sustainable maintenance across evolving projects.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/dfd-documentation-sustaining-system-clarity\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Mastering Data Flow Diagram Levels and Balancing","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/"},{"@type":"ListItem","position":3,"name":"Real-World Application and Governance","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfgovernance\/"},{"@type":"ListItem","position":4,"name":"Using DFDs in System Documentation and Maintenance"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1161","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1161\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1157"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1161"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}