{"id":1140,"date":"2026-02-25T10:36:44","date_gmt":"2026-02-25T10:36:44","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/"},"modified":"2026-02-25T10:36:44","modified_gmt":"2026-02-25T10:36:44","slug":"scalable-dfd-hierarchy-design","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/","title":{"rendered":"Designing Level Hierarchies That Scale"},"content":{"rendered":"

When I began working on large enterprise systems, I quickly learned that a flat, monolithic DFD structure fails under pressure. The real challenge isn’t just breaking down processes\u2014it’s ensuring every level remains coherent, traceable, and logically connected. A scalable DFD hierarchy isn’t about adding more levels; it\u2019s about organizing them so that each layer serves a clear purpose and supports system evolution.<\/p>\n

Many confuse DFD hierarchy design with simple decomposition. But decomposition without structure leads to chaos. A scalable DFD hierarchy is modular by design\u2014each level isolates functionality, reduces coupling, and enables independent validation. This is where DFD scalability becomes not just a goal but a necessity.<\/p>\n

Over two decades of modeling across banking, government, and SaaS platforms taught me one truth: the most robust systems emerge from hierarchies built on clarity, consistency, and foresight. This chapter gives you the principles, patterns, and practical insights to create a DFD hierarchy that scales with your system\u2014without sacrificing accuracy or readability.<\/p>\n

Core Principles of Scalable DFD Hierarchy Design<\/h2>\n

1. Start with a Clear System Boundary<\/h3>\n

Before any decomposition, define the system boundary precisely. The external entities must be unambiguous. If they\u2019re not, your entire hierarchy risks drifting into ambiguity.<\/p>\n

Ask: What data enters and exits the system? Where is the boundary drawn between internal and external control? A well-defined boundary keeps flows focused and prevents over-inclusion.<\/p>\n

2. Prioritize Functional Modularity<\/h3>\n

Each child diagram should represent a coherent functional module\u2014not just a random subset of processes. Think in terms of business capabilities, not just technical operations.<\/p>\n

For example, in a payment processing system, decompose into: Payment Authorization<\/strong>, Transaction Settlement<\/strong>, and Reporting & Audit<\/strong>. Each becomes a distinct DFD level, ensuring maintainability as new features are added.<\/p>\n

3. Enforce Naming Discipline<\/h3>\n

Use consistent naming across levels. Avoid phrases like \u201cProcess 1\u201d or \u201cStep 2.\u201d Instead, use imperative verbs: Validate Payment<\/em>, Generate Receipt<\/em>.<\/p>\n

Names must reflect both function and scope. For instance, Process Payment (Customer Tier A)<\/em> signals both function and business context\u2014ideal for traceability in multi-tier systems.<\/p>\n

Step-by-Step Framework for DFD Hierarchy Design<\/h2>\n
    \n
  1. Define the Level 0 Context Diagram<\/strong> \u2013 Identify all external entities and primary data flows.<\/li>\n
  2. Break Down by Functional Domain<\/strong> \u2013 Group processes into core business functions.<\/li>\n
  3. Assign Unique Level Numbers<\/strong> \u2013 Use hierarchical notation: Level 1.1, Level 1.2, etc.<\/li>\n
  4. Ensure Data Flow Consistency<\/strong> \u2013 Every input and output in a child diagram must be traceable to the parent.<\/li>\n
  5. Validate with a Cross-Level Checklist<\/strong> \u2013 Confirm inputs, outputs, data stores, and processes align.<\/li>\n<\/ol>\n

    Following this framework ensures that your DFD hierarchy grows not just in layers, but in purpose.<\/p>\n

    Key Patterns for DFD Scalability<\/h2>\n

    Pattern 1: The Layered Abstraction Model<\/h3>\n

    Design your hierarchy as a progression from broad to specific:<\/p>\n

      \n
    • Level 0<\/strong>: High-level system overview (context diagram).<\/li>\n
    • Level 1<\/strong>: Major functional modules (e.g., Order Management, Inventory, Billing).<\/li>\n
    • Level 2+<\/strong>: Detailed processes within each module.<\/li>\n<\/ul>\n

      This model mirrors how teams naturally understand systems\u2014starting broad and drilling down.<\/p>\n

      Pattern 2: Reusable Sub-Systems<\/h3>\n

      Identify recurring components such as:<\/p>\n

        \n
      • User authentication workflows<\/li>\nTransaction logging<\/p>\n
      • Notification dispatchers<\/li>\n<\/lidata-flow><\/ul>\n

        Model these once as a reusable DFD sub-system. Reference them in multiple diagrams using clear labels like [Reused: Auth Flow v2.1]<\/em>. This reduces redundancy and enhances consistency.<\/p>\n

        Pattern 3: Data Store Localization<\/h3>\n

        Don\u2019t scatter data stores randomly. Group them by domain:<\/p>\n

          \n
        • Customer Data<\/strong>: Customer database, customer logs<\/li>\n
        • Transaction Data<\/strong>: Payment logs, settlement tables<\/li>\n
        • System Metadata<\/strong>: Audit logs, configuration files<\/li>\n<\/ul>\n

          Localizing data stores improves readability and simplifies auditing and maintenance.<\/p>\n

          Common Pitfalls and How to Avoid Them<\/h2>\n\n\n\n\n\n\n\n
          Pitfall<\/th>\nImpact<\/th>\nSolution<\/th>\n<\/tr>\n
          Decomposing too early<\/td>\nCreates unnecessary complexity and inconsistency<\/td>\nComplete Level 1 before diving into Level 2<\/td>\n<\/tr>\n
          Missing data flow traceability<\/td>\nBreaks balancing, leads to audit failures<\/td>\nUse a data dictionary and cross-reference flows<\/td>\n<\/tr>\n
          Overlapping or ambiguous boundaries<\/td>\nCreates ghost flows and data duplication<\/td>\nDefine boundaries in collaboration with stakeholders<\/td>\n<\/tr>\n
          Ignoring modularity<\/td>\nHard to maintain, impossible to scale<\/td>\nDesign each level around a single functional responsibility<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

          These aren\u2019t theoretical risks\u2014they\u2019re lessons from real projects where poor DFD hierarchy design led to rework, delays, and compliance gaps.<\/p>\n

          Integrating DFD Scalability with Modern Tools<\/h2>\n

          Modern modeling tools like Visual Paradigm automate much of the validation, but they can\u2019t replace sound design. Use them to:<\/p>\n

            \n
          • Automatically flag missing or unexplained data flows<\/li>\n
          • Generate cross-referenced data dictionaries<\/li>\n
          • Visualize traceability between parent and child diagrams<\/li>\n<\/ul>\n

            But don\u2019t rely solely on automation. Manual review remains essential\u2014especially for complex multi-level data flow diagrams where logic can slip through automated checks.<\/p>\n

            Always pair tool assistance with a structured review process. A checklist is not a luxury\u2014it\u2019s a necessity for maintaining DFD integrity at scale.<\/p>\n

            Final Checklist: Validating Your Scalable DFD Hierarchy<\/h2>\n
              \n
            • Each child diagram has a clear, unique purpose tied to a business function.<\/li>\n
            • All data flows in child diagrams are traceable to the parent level.<\/li>\n
            • No new external entities appear in lower levels without justification.<\/li>\n
            • Data stores are localized and consistent across levels.<\/li>\n
            • Names follow a standardized, descriptive format.<\/li>\n
            • Modular components are reusable and clearly labeled.<\/li>\n<\/ul>\n

              Use this checklist after each major update. It\u2019s the difference between a model that evolves and one that collapses under its own weight.<\/p>\n

              Frequently Asked Questions<\/h2>\n

              What is the ideal number of levels in a scalable DFD hierarchy?<\/h3>\n

              There\u2019s no fixed number. A small system might need only Level 0 to Level 2. A complex enterprise system could require up to Level 4 or more. The key is not how many levels you have, but whether each level serves a distinct functional purpose and maintains consistency.<\/p>\n

              Can I reuse the same DFD across different parts of my system?<\/h3>\n

              Yes\u2014but only if it represents a self-contained, reusable component. Always label it clearly and document its scope. Reuse is powerful, but misapplied reuse leads to confusion. For example, a user authentication flow can be reused, but only if the context (e.g., mobile vs. web) is accounted for.<\/p>\n

              How do I handle data flows that span multiple DFD levels?<\/h3>\n

              Every data flow must be traceable. If a flow appears in a lower level but not the parent, it\u2019s a red flag. Either it\u2019s a missing input\/output, or the parent diagram is incomplete. Always verify with your data dictionary and cross-reference using unique flow IDs.<\/p>\n

              Should I decompose by process or by data type?<\/h3>\n

              Decompose by functional responsibility, not data type. A process like \u201cProcess Payment\u201d should be broken down by function, not by whether it handles credit card or bank transfer data. Data type drives structure; function drives decomposition.<\/p>\n

              How does a scalable DFD hierarchy support regulatory compliance?<\/h3>\n

              Clear traceability between levels makes it easy to audit data movement. In systems governed by GDPR or SOX, regulators need to see exactly where data originates, where it goes, and how it\u2019s stored. A well-structured DFD hierarchy provides that visibility\u2014without guesswork.<\/p>\n

              What if two teams are responsible for different levels of the DFD?<\/h3>\n

              Assign a central steward to oversee consistency. Use shared data dictionaries, standardized naming, and collaborative review sessions. Ensure both teams agree on boundaries, flows, and data store logic. This prevents \u201cislands of design\u201d that break the model.<\/p>\n","protected":false},"excerpt":{"rendered":"

              When I began working on large enterprise systems, I quickly learned that a flat, monolithic DFD structure fails under pressure. The real challenge isn’t just breaking down processes\u2014it’s ensuring every level remains coherent, traceable, and logically connected. A scalable DFD hierarchy isn’t about adding more levels; it\u2019s about organizing them so that each layer serves […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1138,"menu_order":1,"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-1140","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nScalable DFD Hierarchy Design<\/title>\n<meta name=\"description\" content=\"Learn how to design a scalable DFD hierarchy that ensures traceability, modularity, and long-term maintainability in complex system models. Master DFD hierarchy design and scalability with expert guidance.\" \/>\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\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scalable DFD Hierarchy Design\" \/>\n<meta property=\"og:description\" content=\"Learn how to design a scalable DFD hierarchy that ensures traceability, modularity, and long-term maintainability in complex system models. Master DFD hierarchy design and scalability with expert guidance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/\",\"name\":\"Scalable DFD Hierarchy Design\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:36:44+00:00\",\"description\":\"Learn how to design a scalable DFD hierarchy that ensures traceability, modularity, and long-term maintainability in complex system models. Master DFD hierarchy design and scalability with expert guidance.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering Data Flow Diagram Levels and Balancing\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Techniques for DFD Leveling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Designing Level Hierarchies That Scale\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Scalable DFD Hierarchy Design","description":"Learn how to design a scalable DFD hierarchy that ensures traceability, modularity, and long-term maintainability in complex system models. Master DFD hierarchy design and scalability with expert guidance.","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\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/","og_locale":"pl_PL","og_type":"article","og_title":"Scalable DFD Hierarchy Design","og_description":"Learn how to design a scalable DFD hierarchy that ensures traceability, modularity, and long-term maintainability in complex system models. Master DFD hierarchy design and scalability with expert guidance.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/","name":"Scalable DFD Hierarchy Design","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:36:44+00:00","description":"Learn how to design a scalable DFD hierarchy that ensures traceability, modularity, and long-term maintainability in complex system models. Master DFD hierarchy design and scalability with expert guidance.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/scalable-dfd-hierarchy-design\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Mastering Data Flow Diagram Levels and Balancing","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/"},{"@type":"ListItem","position":3,"name":"Techniques for DFD Leveling","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/mastering-data-flow-diagram-leveling-and-balancing\/dfd-leveling-techniques\/"},{"@type":"ListItem","position":4,"name":"Designing Level Hierarchies That Scale"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1140\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1138"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1140"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}