{"id":967,"date":"2026-02-25T10:33:24","date_gmt":"2026-02-25T10:33:24","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/"},"modified":"2026-02-25T10:33:24","modified_gmt":"2026-02-25T10:33:24","slug":"c4-component-diagram-detailing-internal-logic","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/","title":{"rendered":"Component Diagrams: Detailing Internal Logic"},"content":{"rendered":"<p>After establishing your system context and container diagrams, the next leap is understanding how components interact within a single container. This is where the C4 component diagram shines\u2014revealing internal structure, responsibilities, and hidden dependencies that can derail maintainability.<\/p>\n<p>Think of this level as the architectural equivalent of a floor plan. It\u2019s not just about what\u2019s inside, but how those parts work together. A well-structured component diagram turns architectural ambiguity into clear ownership, boundaries, and communication flow.<\/p>\n<p>You\u2019ve likely run into situations where code works but feels tangled\u2014dependencies cross-cutting, responsibilities blurred, testing blocked. That\u2019s where the C4 model component level tutorial becomes essential. It\u2019s not about code, but about how the system is designed to be built.<\/p>\n<h2>What Is a C4 Component Diagram?<\/h2>\n<p>The C4 component diagram is Level 3 in the C4 model\u2019s hierarchy. It breaks down containers into meaningful, reusable components\u2014collections of code that encapsulate a specific responsibility.<\/p>\n<p>Unlike code-level diagrams, components are high enough to stay independent of implementation details yet specific enough to reveal design intent.<\/p>\n<p>Each component should have a single, well-defined responsibility. If it doesn\u2019t, you\u2019re likely missing a layer or misdefining the scope.<\/p>\n<p>Key elements include:<\/p>\n<ul>\n<li>Components (boxes with labels)<\/li>\n<li>Dependencies (arrows indicating runtime or compile-time relationships)<\/li>\n<li>Responsibility descriptions (often in a legend or inline)<\/li>\n<li>Clear boundaries (dashed lines or grouping)<\/li>\n<\/ul>\n<h3>Why This Level Matters<\/h3>\n<p>Too many teams skip this step, assuming that container-level diagrams are enough. But without component-level clarity, you\u2019re left with:<\/p>\n<ul>\n<li>Shared responsibility confusion<\/li>\n<li>Unplanned circular dependencies<\/li>\n<li>Difficulty in testing, deployment, and refactoring<\/li>\n<\/ul>\n<p>Consider this: a \u201cUser Service\u201d container might contain a \u201cUser Authentication,\u201d \u201cUser Profile,\u201d and \u201cUser Notification\u201d component. Each has a single responsibility. Mislabeling one as \u201cUser Management\u201d can lead to a monolithic mess.<\/p>\n<h2>How to Model Components in C4<\/h2>\n<p>Creating a C4 component diagram isn\u2019t about drawing the most boxes. It\u2019s about making design decisions visible.<\/p>\n<p>Start with a single container\u2014say, a web application. Ask: What are the major functional areas? Each area becomes a potential component.<\/p>\n<p>Use the <strong>Single Responsibility Principle<\/strong> as your filter: can this component be changed for only one reason? If not, split it.<\/p>\n<h3>Step-by-Step Process<\/h3>\n<ol>\n<li><strong>Identify functional domains<\/strong>\u2014e.g., \u201cPayment Processing,\u201d \u201cOrder Management,\u201d \u201cInventory Tracking.\u201d<\/li>\n<li><strong>Group related classes or modules<\/strong> into logical units.<\/li>\n<li><strong>Give each a clear, concise name<\/strong>\u2014avoid ambiguous labels like \u201cUtils\u201d or \u201cHelper.\u201d<\/li>\n<li><strong>Draw components as rectangles<\/strong> with a short label and a description from the legend.<\/li>\n<li><strong>Map dependencies<\/strong> with arrows\u2014where the arrow points is the dependent component.<\/li>\n<li><strong>Check for circular dependencies<\/strong>\u2014they signal design issues.<\/li>\n<\/ol>\n<h3>Patterns That Help<\/h3>\n<p>Some common patterns help structure components effectively:<\/p>\n<ul>\n<li><strong>Hexagonal (Ports and Adapters)<\/strong>\u2014separate core logic from external frameworks.<\/li>\n<li><strong>Event-Driven Components<\/strong>\u2014when components communicate via events, not direct calls.<\/li>\n<li><strong>Layered Architecture<\/strong>\u2014components in a dependency direction (e.g., UI \u2192 Service \u2192 Repository).<\/li>\n<li><strong>Microkernel<\/strong>\u2014core component that delegates to extension points.<\/li>\n<\/ul>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even experienced modelers make mistakes. Here are the most frequent errors and how to correct them.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Issue<\/th>\n<th>Why It\u2019s Bad<\/th>\n<th>Solution<\/th>\n<\/tr>\n<tr>\n<td>Overlapping responsibilities<\/td>\n<td>Leads to tightly coupled changes<\/td>\n<td>Refactor into smaller, single-purpose components<\/td>\n<\/tr>\n<tr>\n<td>Circular dependencies<\/td>\n<td>Breaks modularity and testing<\/td>\n<td>Re-evaluate component boundaries; introduce interfaces<\/td>\n<\/tr>\n<tr>\n<td>Too many components<\/td>\n<td>Creates noise, hides the forest for the trees<\/td>\n<td>Group related components; use subcomponents or layers<\/td>\n<\/tr>\n<tr>\n<td>Using implementation names<\/td>\n<td>Breaks abstraction<\/td>\n<td>Focus on responsibility: \u201cOrder Processor\u201d not \u201cOrderServiceV2\u201d<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>One rule I\u2019ve learned: if you can\u2019t explain a component\u2019s purpose in one sentence, it\u2019s not well-defined.<\/p>\n<h2>Real-World Example: E-Commerce Platform<\/h2>\n<p>Let\u2019s say we have a \u201cShopping Cart\u201d container. The initial sketch might show:<\/p>\n<ul>\n<li>Cart Service<\/li>\n<li>Checkout Service<\/li>\n<li>Payment Gateway<\/li>\n<li>Inventory Service<\/li>\n<\/ul>\n<p>But a deeper look reveals that \u201cCart Service\u201d depends on \u201cInventory Service\u201d to check stock. If the inventory is out-of-date, the cart might allow invalid purchases.<\/p>\n<p>By modeling this dependency, we expose a risk: <em>the cart is not resilient to inventory delays<\/em>.<\/p>\n<p>So we refactor: introduce a \u201cStock Validation\u201d component that sits between the cart and inventory. Now the dependency pattern is clearer, and we can add fallbacks or delay handling.<\/p>\n<h3>Before and After<\/h3>\n<p><strong>Before:<\/strong> Cart \u2192 Payment \u2192 Inventory \u2014 this implies the cart waits for inventory, which isn\u2019t ideal.<\/p>\n<p><strong>After:<\/strong> Cart \u2192 Stock Validation \u2192 Inventory; Cart \u2192 Payment<\/p>\n<p>The new structure shows that payment doesn\u2019t depend on inventory, only stock availability does. That\u2019s a major improvement in resilience and clarity.<\/p>\n<h2>Tools That Make C4 Modeling Easier<\/h2>\n<p>You don\u2019t need to draw by hand. Modern tools like Visual Paradigm support C4 notation with built-in templates and libraries.<\/p>\n<p>What I\u2019ve found useful: use color coding to group related components (e.g., red for payment, blue for inventory), and always include a legend that defines the notation.<\/p>\n<p>Also, keep component diagrams lightweight. No more than 10\u201315 components per diagram. If you exceed that, consider breaking into sub-diagrams or using a layered approach.<\/p>\n<h2>When to Use a C4 Component Diagram<\/h2>\n<p>Use this level when:<\/p>\n<ul>\n<li>Planning a major refactor or feature rollout<\/li>\n<li>Onboarding new developers to a project<\/li>\n<li>Reviewing architecture decisions in a team<\/li>\n<li>Identifying hidden dependencies that block deployment<\/li>\n<\/ul>\n<p>It\u2019s not for every conversation. But when you need to show how parts of a system fit together without diving into code, this is your go-to.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between a container and a component in C4?<\/h3>\n<p>A container is a deployable unit\u2014like a web app, mobile app, or database. A component is a logical piece of code within that container. For example, a web app container might have a \u201cUser Service\u201d component and a \u201cPayment Processing\u201d component.<\/p>\n<h3>Can I have multiple component diagrams for one container?<\/h3>\n<p>Yes. If the container is complex, split it by domain or layer. For example, one diagram for \u201cOrder Management,\u201d another for \u201cInventory.\u201d This keeps each diagram focused and readable.<\/p>\n<h3>How do I decide component boundaries?<\/h3>\n<p>Use responsibility. Ask: \u201cWhat problem does this part solve?\u201d If two components solve the same problem, they may be over-split. If one component has more than one reason to change, split it.<\/p>\n<h3>Should I include data access components like repositories?<\/h3>\n<p>Yes\u2014especially if they\u2019re independent of the business logic. A \u201cUser Repository\u201d component that handles database access is valid. But avoid naming it after the database (e.g., \u201cMySQLUserDAO\u201d). Use \u201cUser Data Access\u201d or \u201cUser Repository.\u201d<\/p>\n<h3>How do I represent asynchronous communication in a C4 component diagram?<\/h3>\n<p>Use a dashed arrow with a label like \u201cevent,\u201d \u201casync,\u201d or \u201cmessage.\u201d For example: <code>Order Service \u2192 Notification Service [event: order-placed]<\/code>. This makes event-driven flows visible.<\/p>\n<h3>Can I model a component as a library or external SDK?<\/h3>\n<p>Yes. If the component is not part of your codebase but is used by your system, label it as \u201cThird-Party\u201d or \u201cExternal.\u201d For example: <code>Payment Gateway (External)<\/code>. This helps avoid confusion with internal components.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After establishing your system context and container di [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":964,"menu_order":2,"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-967","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>C4 Component Diagram: Mastering Internal Logic<\/title>\n<meta name=\"description\" content=\"Learn how to create effective C4 component diagrams that reveal internal responsibilities, dependencies, and design patterns. A practical C4 model component level tutorial for beginners.\" \/>\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\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"C4 Component Diagram: Mastering Internal Logic\" \/>\n<meta property=\"og:description\" content=\"Learn how to create effective C4 component diagrams that reveal internal responsibilities, dependencies, and design patterns. A practical C4 model component level tutorial for beginners.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/\" \/>\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\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/\",\"name\":\"C4 Component Diagram: Mastering Internal Logic\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:33:24+00:00\",\"description\":\"Learn how to create effective C4 component diagrams that reveal internal responsibilities, dependencies, and design patterns. A practical C4 model component level tutorial for beginners.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From Zero to C4: Beginner Modeling Blueprint\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Mastering the Four Levels of C4\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Component Diagrams: Detailing Internal Logic\"}]},{\"@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":"C4 Component Diagram: Mastering Internal Logic","description":"Learn how to create effective C4 component diagrams that reveal internal responsibilities, dependencies, and design patterns. A practical C4 model component level tutorial for beginners.","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\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/","og_locale":"zh_CN","og_type":"article","og_title":"C4 Component Diagram: Mastering Internal Logic","og_description":"Learn how to create effective C4 component diagrams that reveal internal responsibilities, dependencies, and design patterns. A practical C4 model component level tutorial for beginners.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/","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\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/","name":"C4 Component Diagram: Mastering Internal Logic","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:33:24+00:00","description":"Learn how to create effective C4 component diagrams that reveal internal responsibilities, dependencies, and design patterns. A practical C4 model component level tutorial for beginners.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/c4-component-diagram-detailing-internal-logic\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"From Zero to C4: Beginner Modeling Blueprint","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/"},{"@type":"ListItem","position":3,"name":"Mastering the Four Levels of C4","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/from-zero-to-c4-beginner-modeling-blueprint\/mastering-the-four-levels-of-c4\/"},{"@type":"ListItem","position":4,"name":"Component Diagrams: Detailing Internal Logic"}]},{"@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\/967","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\/967\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/964"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=967"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=967"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}