{"id":960,"date":"2026-02-25T10:33:22","date_gmt":"2026-02-25T10:33:22","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/"},"modified":"2026-02-25T10:33:22","modified_gmt":"2026-02-25T10:33:22","slug":"c4-model-purpose","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/","title":{"rendered":"Understanding the C4 Model’s Core Purpose"},"content":{"rendered":"

Too many architectural diagrams start with good intent but end up as tangled, unexplained visuals that confuse more than clarify. I\u2019ve seen teams spend hours crafting elaborate UML diagrams that no one can interpret after the meeting ends. The real issue isn\u2019t technical \u2014 it\u2019s communication. The C4 model was born from this frustration, not as a new notation, but as a response to a deeper problem: how do we make software architecture understandable across teams, roles, and stages of development?<\/p>\n

When Simon Brown introduced the C4 model around 2014, he wasn\u2019t trying to invent a new standard. He was solving a practical need: creating diagrams that developers, product managers, and stakeholders could all engage with. The model\u2019s purpose is not to replace all other diagrams but to offer a consistent, scalable, and human-first way to visualize systems \u2014 one that evolves with the project, not against it.<\/p>\n

You\u2019re not here to master every icon or edge style. You\u2019re here to understand why the C4 model works, when it applies, and how it helps teams avoid the chaos of misaligned expectations. This chapter focuses on the foundational truth: C4 model purpose<\/strong> is not about tools or syntax \u2014 it\u2019s about clarity, abstraction, and shared understanding.<\/p>\n

The Problem C4 Was Built To Solve<\/h2>\n

Before C4, architectural documentation often relied on UML or custom flowcharts that assumed technical fluency. But not everyone on a project team speaks fluent UML. Product owners, designers, and even junior developers might struggle to interpret a complex class diagram or sequence chart.<\/p>\n

I remember a startup where a senior developer spent two days drawing a component interaction diagram. The team reviewed it, nodded, but still missed key dependencies. The diagram was technically correct \u2014 but not useful. Why? It lacked context. It wasn\u2019t built around people or flows. It was just boxes and lines.<\/p>\n

C4 directly addresses this gap by shifting focus from abstract notation to real-world communication. Instead of asking \u201cDoes this follow UML rules?\u201d it asks: \u201cCan someone not on the team understand what this system does and why it matters?\u201d<\/p>\n

Why Use C4 Model for Software Architecture?<\/h3>\n

Let\u2019s be clear: the C4 model isn\u2019t a silver bullet. But its strength lies in consistency and purpose. Here\u2019s why teams choose it:<\/p>\n

    \n
  • Abstraction-first design<\/strong>: The model\u2019s four levels guide you from high-level context to code-level detail \u2014 not as separate artifacts, but as a natural progression.<\/li>\n
  • Stakeholder-driven clarity<\/strong>: Each level targets a specific audience. A CEO sees the system context; a developer sees component boundaries; a tester sees code-level behavior.<\/li>\n
  • Reduced cognitive load<\/strong>: By limiting detail at each level, C4 prevents diagram overload. You don\u2019t show every class when a component is enough.<\/li>\n
  • Improved collaboration<\/strong>: Because the structure is standardized, team members from different backgrounds can contribute meaningfully to diagrams.<\/li>\n<\/ul>\n

    The real power isn\u2019t in the model itself \u2014 it\u2019s in how it forces teams to think about architecture as a conversation, not a final artifact.<\/p>\n

    C4 Model Core Concepts: The Four Layers of Clarity<\/h2>\n

    The C4 model is built on four hierarchical abstraction levels. Each level answers a different question:<\/p>\n

    Level 1: Context \u2014 What is the system?<\/h3>\n

    Who uses it? What external systems does it interact with? This is the “big picture” \u2014 not technical, but business-focused. A user story like \u201cAs a customer, I want to place an order\u201d starts here.<\/p>\n

    Best practice: Limit to 5\u20137 key elements. Too many actors or systems create noise.<\/p>\n

    Level 2: Containers \u2014 What are the major components?<\/h3>\n

    Here, we break the system into containers: web apps, mobile apps, databases, APIs. This is where technology choices appear \u2014 but only the high-level ones.<\/p>\n

    Example: A banking app might have a React web app, a Node.js API, and a PostgreSQL database. That\u2019s three containers.<\/p>\n

    Level 3: Components \u2014 How does each container work inside?<\/h3>\n

    Now we drill into a container. A “user management” component might include authentication, profile storage, and email services. These are high-level modules that remain stable across sprints.<\/p>\n

    Keep component responsibilities focused. If a component has more than two or three core functions, it\u2019s likely doing too much.<\/p>\n

    Level 4: Code \u2014 Where the rubber meets the road<\/h3>\n

    This level is optional. Use it for critical or complex parts \u2014 like a payment processor or billing engine \u2014 not for every class.<\/p>\n

    It\u2019s not about showing every method. It\u2019s about linking diagrams back to code: \u201cHere\u2019s the component. Here\u2019s the class that implements it.\u201d Tools like Visual Paradigm or PlantUML make this connection seamless.<\/p>\n

    Most teams stop at Level 3. That\u2019s intentional. The goal isn\u2019t to document every line of code \u2014 it\u2019s to understand the structure at a glance.<\/p>\n

    Why C4 Model Core Concepts Work for Real Teams<\/h2>\n

    Let\u2019s compare C4 to traditional modeling methods:<\/p>\n\n\n\n\n\n\n\n\n
    Aspect<\/th>\nC4 Model<\/th>\nTraditional UML<\/th>\n<\/tr>\n<\/thead>\n
    Learning Curve<\/td>\nLow \u2014 intuitive, focused on communication<\/td>\nHigh \u2014 requires mastery of multiple diagram types<\/td>\n<\/tr>\n
    Primary Audience<\/td>\nDevelopers, product owners, business stakeholders<\/td>\nTechnical teams only<\/td>\n<\/tr>\n
    Scalability<\/td>\nNatural abstraction across levels<\/td>\nProne to over-detailing<\/td>\n<\/tr>\n
    Integration with Agile<\/td>\nDesigned for iterative updates<\/td>\nOften treated as static artifacts<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Yes, UML has its place. But in most real-world projects, the C4 model is faster, clearer, and more practical. The key difference? C4 doesn\u2019t ask you to choose the right diagram type. It asks: \u201cWho needs to understand this, and what do they need to know?\u201d<\/p>\n

    Practical Insight: When Not to Use C4<\/h2>\n

    Not every diagram needs the C4 structure. Don\u2019t force it on:<\/p>\n

      \n
    • Simple scripts or one-off tools.<\/li>\n
    • Highly technical runtime behavior (use sequence or activity diagrams).<\/li>\n
    • Legacy systems where documentation is already fragmented.<\/li>\n<\/ul>\n

      But when you\u2019re building a new system, refactoring a monolith, or onboarding a new team \u2014 C4 is the most effective starting point I\u2019ve used in over 15 years of software work.<\/p>\n

      Key Takeaways<\/h2>\n
        \n
      • The C4 model purpose<\/strong> is to make architecture understandable across roles and levels of expertise.<\/li>\n
      • It\u2019s not about rules \u2014 it\u2019s about abstraction, clarity, and communication<\/strong>.<\/li>\n
      • Use C4 model core concepts<\/strong> to build diagrams incrementally, from context to code.<\/li>\n
      • Not every system needs Level 4 \u2014 often, Level 3 is enough.<\/li>\n
      • Choose C4 when your goal is shared understanding, not technical perfection.<\/li>\n<\/ul>\n

        Start with the context. Ask: \u201cWho are the users? What do they need?\u201d Let that guide what you build next. The model will grow with you \u2014 not from the top down, but from the conversation up.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        Why use C4 model for software architecture?<\/h3>\n

        Because it prioritizes communication over notation. It lets non-technical stakeholders understand the system, and developers stay focused on high-level structure without getting lost in code-level complexity.<\/p>\n

        What are the C4 model core concepts?<\/h3>\n

        The four layers: System Context (who uses the system), Containers (major components), Components (internal modules), and Code (specific classes\/methods). Each level serves a different audience and purpose.<\/p>\n

        Do I need to use all four levels of C4?<\/h3>\n

        No. Most teams stop at Level 3. Level 4 is only useful for critical or complex components. Use it only when it helps clarify design decisions or link diagrams to actual code.<\/p>\n

        Is the C4 model suitable for small projects?<\/h3>\n

        Absolutely. In fact, small projects benefit most \u2014 they\u2019re often more vulnerable to architectural drift. C4 provides structure without overhead.<\/p>\n

        How does C4 support agile teams?<\/h3>\n

        Each level can be updated incrementally. A context diagram can be created early, then refined as the system evolves. It integrates naturally with sprint planning, user stories, and retrospectives.<\/p>\n

        Can I combine C4 with other models like BPMN or ArchiMate?<\/h3>\n

        Yes. C4 is complementary. Use it for system design, and integrate BPMN for business process flows or ArchiMate for enterprise-level architecture. But start with C4 \u2014 it\u2019s the most accessible entry point.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Too many architectural diagrams start with good intent but end up as tangled, unexplained visuals that confuse more than clarify. I\u2019ve seen teams spend hours crafting elaborate UML diagrams that no one can interpret after the meeting ends. The real issue isn\u2019t technical \u2014 it\u2019s communication. The C4 model was born from this frustration, not […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":959,"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":"","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-960","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nC4 Model Purpose: Clear Architecture Communication<\/title>\n<meta name=\"description\" content=\"Discover the true purpose of the C4 model: to simplify software architecture communication through structured abstraction, clarity, and developer-friendly diagrams. Learn why use C4 model for software architecture and how its core concepts enable better teamwork and design decisions.\" \/>\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\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"C4 Model Purpose: Clear Architecture Communication\" \/>\n<meta property=\"og:description\" content=\"Discover the true purpose of the C4 model: to simplify software architecture communication through structured abstraction, clarity, and developer-friendly diagrams. Learn why use C4 model for software architecture and how its core concepts enable better teamwork and design decisions.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/\" \/>\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\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/\",\"name\":\"C4 Model Purpose: Clear Architecture Communication\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:33:22+00:00\",\"description\":\"Discover the true purpose of the C4 model: to simplify software architecture communication through structured abstraction, clarity, and developer-friendly diagrams. Learn why use C4 model for software architecture and how its core concepts enable better teamwork and design decisions.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From Zero to C4: Beginner Modeling Blueprint\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Foundations of C4 Modeling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Understanding the C4 Model’s Core Purpose\"}]},{\"@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":"C4 Model Purpose: Clear Architecture Communication","description":"Discover the true purpose of the C4 model: to simplify software architecture communication through structured abstraction, clarity, and developer-friendly diagrams. Learn why use C4 model for software architecture and how its core concepts enable better teamwork and design decisions.","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\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/","og_locale":"pt_PT","og_type":"article","og_title":"C4 Model Purpose: Clear Architecture Communication","og_description":"Discover the true purpose of the C4 model: to simplify software architecture communication through structured abstraction, clarity, and developer-friendly diagrams. Learn why use C4 model for software architecture and how its core concepts enable better teamwork and design decisions.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/","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\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/","name":"C4 Model Purpose: Clear Architecture Communication","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:33:22+00:00","description":"Discover the true purpose of the C4 model: to simplify software architecture communication through structured abstraction, clarity, and developer-friendly diagrams. Learn why use C4 model for software architecture and how its core concepts enable better teamwork and design decisions.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/c4-model-purpose\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"From Zero to C4: Beginner Modeling Blueprint","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/"},{"@type":"ListItem","position":3,"name":"Foundations of C4 Modeling","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/foundations-of-c4-modeling\/"},{"@type":"ListItem","position":4,"name":"Understanding the C4 Model’s Core Purpose"}]},{"@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\/960","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\/960\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/959"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=960"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=960"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}