{"id":954,"date":"2026-02-25T10:32:39","date_gmt":"2026-02-25T10:32:39","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/"},"modified":"2026-02-25T10:32:39","modified_gmt":"2026-02-25T10:32:39","slug":"uml-design-principles-designing-with-intent","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/","title":{"rendered":"Conclusion: Designing with Intent, Not Just Structure"},"content":{"rendered":"

Too many developers treat UML class diagrams as a mechanical exercise in notation\u2014checking boxes for associations, multiplicities, and visibility. That\u2019s a trap. The real power lies not in the diagram itself, but in what it represents: a living expression of design decisions rooted in intent.<\/p>\n

After years guiding teams from CRC cards to fully realized class diagrams, I\u2019ve learned this: the best models aren\u2019t those that follow every rule perfectly. They\u2019re the ones where the team can trace every class, method, and relationship back to a clear \u201cwhy.\u201d<\/p>\n

Here, you\u2019ll learn how to move beyond formalism and apply UML design principles with clarity and purpose\u2014anchored in the CRC philosophy and a responsibility-driven mindset. This isn\u2019t about tools. It\u2019s about culture, consistency, and communication.<\/p>\n

Why Structure Alone Isn\u2019t Enough<\/h2>\n

UML is a language. But like any language, it\u2019s not the grammar that conveys meaning\u2014it\u2019s the intent behind the sentence.<\/p>\n

A class diagram can be syntactically perfect: correct visibility, accurate multiplicities, well-structured inheritance. Yet if the team can\u2019t explain why the class exists, or what responsibility it owns, it\u2019s just a facade.<\/p>\n

Consider this: a class named PaymentProcessor<\/code> might have a method process()<\/code>. But if no one can say whether it\u2019s responsible for validation, authorization, or reconciliation, then the method has no behavioral context. The diagram looks complete\u2014but the design is fragile.<\/p>\n

This is why design intent modeling<\/strong> is the critical next step after formalizing CRC cards into UML. It\u2019s not about adding more lines. It\u2019s about asking: What problem is this model solving?<\/em><\/p>\n

The CRC Philosophy as a Foundation<\/h3>\n

When we start with CRC cards, we\u2019re not choosing a notation\u2014we\u2019re choosing a responsibility-driven mindset<\/strong>. Each card is a conversation about behavior, not just structure.<\/p>\n

That mindset must survive the transition to UML. The class Order<\/code> isn\u2019t just a container of data. It\u2019s a participant in a business process\u2014responsible for validating, accepting, and notifying. That responsibility must be visible, traceable, and justifiable in the class diagram.<\/p>\n

Ask yourself: Can I explain the responsibility-driven mindset<\/strong> behind this class in under a minute? If not, the model is missing its soul.<\/p>\n

Translating Intent: The UML Design Principles Checklist<\/h2>\n

Formalizing CRC into UML isn\u2019t about mapping symbols. It\u2019s about preserving intent. Use this checklist to ensure your class diagrams reflect real design thinking.<\/p>\n

    \n
  • Every class must have a single, clear responsibility.<\/strong> If it has multiple reasons to change, it\u2019s probably doing too much.<\/li>\n
  • Each method must stem from a defined responsibility.<\/strong> No hidden behaviors. If a method doesn\u2019t serve a named purpose, reconsider its existence.<\/li>\n
  • Associations must reflect meaningful collaborations.<\/strong> A relationship between Order<\/code> and Customer<\/code> isn\u2019t just \u201cthey\u2019re connected\u201d\u2014it\u2019s \u201cOrder<\/code> depends on Customer<\/code> for shipping details.\u201d<\/li>\n
  • Visibility should reflect encapsulation, not convenience.<\/strong> Use private<\/code> for internal state, protected<\/code> for inheritance, public<\/code> only for contracts with the outside world.<\/li>\n
  • Use inheritance only when behavior is truly shared.<\/strong> Don\u2019t inherit just because two classes look similar. Ask: Is this a is-a<\/em> relationship, or just a has-a<\/em>?<\/li>\n<\/ul>\n

    These principles aren\u2019t optional. They\u2019re the difference between a diagram that documents and one that guides.<\/p>\n

    From CRC to UML: A Step-by-Step Intent Mapping<\/h3>\n

    Here\u2019s how to translate CRC insights into UML while preserving design intent. The goal is to answer: Why is this class here? Why does it work this way?<\/em><\/p>\n

      \n
    1. Start with the CRC class name.<\/strong> Ask: What business role does this represent? E.g., InventoryManager<\/code> isn\u2019t just a data holder\u2014it manages stock levels and alerts.<\/li>\n
    2. Map responsibilities to methods and attributes.<\/strong> A responsibility like \u201ccalculate total value\u201d becomes a method calculateTotalValue()<\/code>. \u201cTrack stock levels\u201d becomes an attribute currentStock: int<\/code>.<\/li>\n
    3. Turn collaborations into associations.<\/strong> If Order<\/code> collaborates with PaymentService<\/code>, the UML association should reflect a dependency, not just a line.<\/li>\n
    4. Label relationships with intent.<\/strong> Don\u2019t just add a name like \u201crelation.\u201d Instead, name it \u201chandles payment validation\u201d to clarify purpose.<\/li>\n
    5. Review every class: Can I explain its intent in one sentence?<\/strong> If not, revise.<\/li>\n<\/ol>\n

      This process turns UML from a static artifact into a living document of design decisions.<\/p>\n

      Common Pitfalls and How to Avoid Them<\/h2>\n

      Even experienced teams fall into traps when moving from CRC to UML. Here are the top three, with real fixes.<\/p>\n\n\n\n\n\n\n
      Pitfall<\/th>\nWhy It Happens<\/th>\nHow to Fix<\/th>\n<\/tr>\n
      Overloading classes with responsibilities<\/td>\nTrying to capture every behavior in a single class<\/td>\nRevisit CRC cards: If a class has more than 2\u20133 responsibilities, decompose it into smaller, focused classes.<\/td>\n<\/tr>\n
      Missing intent in associations<\/td>\nAdding lines without explaining purpose<\/td>\nEvery association should have a navigable role name. E.g., Order<\/code> \u2014> Customer<\/code> (responsible for delivery address).<\/td>\n<\/tr>\n
      Forgetting to model constraints and invariants<\/td>\nAssuming logic is implied by structure<\/td>\nAdd constraints in curly braces: {totalPrice > 0}<\/code> to clarify validation rules.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      These are not syntax errors. They\u2019re design flaws. Fix them early, and your model becomes a shared truth.<\/p>\n

      Building a Culture of Intent-Driven Design<\/h2>\n

      UML design principles aren\u2019t just technical rules. They\u2019re cultural ones.<\/p>\n

      When teams adopt a responsibility-driven mindset<\/strong>, they stop asking \u201cWhat should this class have?\u201d and start asking \u201cWhat should it do?\u201d<\/p>\n

      I once worked with a team who spent weeks refining a ReportGenerator<\/code> class. It had 12 methods, 30 attributes, and 6 associations. But when we asked: \u201cWhat\u2019s your single responsibility?\u201d\u2014no one could answer. We stripped it down to two methods and one core behavior: \u201cgenerate a PDF report from data.\u201d The model became simpler, clearer, and more maintainable.<\/p>\n

      This is the power of design intent modeling<\/strong>. It forces teams to reflect on their choices, not just execute them.<\/p>\n

      How to Foster Intent in Your Team<\/h3>\n
        \n
      • Start every modeling session with: \u201cWhat business problem does this class solve?\u201d<\/li>\n
      • During reviews, ask: \u201cCan you explain this class in one sentence?\u201d<\/li>\n
      • Use the CRC philosophy as a litmus test: \u201cWould this class exist in the real world?\u201d<\/li>\n
      • Encourage naming that reflects purpose: DiscountCalculator<\/code> instead of Calc<\/code> or Helper<\/code>.<\/li>\n<\/ul>\n

        These habits don\u2019t just improve diagrams. They improve communication, reduce rework, and create systems that evolve with clarity.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        How do I know if I\u2019ve captured the correct design intent in my UML model?<\/h3>\n

        Ask three questions: Is every class responsible for one clear purpose? Can you explain its role in simple business terms? Can another developer understand its behavior without reading code? If yes to all, intent is likely preserved.<\/p>\n

        Does the CRC philosophy still matter after moving to UML?<\/h3>\n

        Yes. CRC cards are a thinking tool, not a step. The CRC philosophy\u2014responsibility-driven design, collaboration modeling, lightweight documentation\u2014must persist. Use it to guide every UML decision, especially when naming, structuring, or refining.<\/p>\n

        Can UML design principles be applied to legacy systems?<\/h3>\n

        Absolutely. Start by reverse-engineering the existing model. Identify classes and their behaviors. Then, apply the intent checks: \u201cDoes this class have a single responsibility?\u201d \u201cIs the association meaningful?\u201d Use this as a foundation for refactoring, not just documentation.<\/p>\n

        What if my team insists on following UML rules but ignores intent?<\/h3>\n

        That\u2019s a red flag. Rules without purpose breed brittle models. Introduce a \u201cone-sentence intent\u201d rule: every class must be explainable in one clear sentence. Make it part of your design review checklist. Over time, teams begin to value clarity over compliance.<\/p>\n

        How do I balance UML precision with rapid prototyping?<\/h3>\n

        Use CRC cards for early exploration. Convert only what\u2019s necessary. Focus on core classes and key collaborations. Let the model evolve through feedback, not perfection. The goal is not to \u201ccomplete\u201d the diagram\u2014it\u2019s to build shared understanding.<\/p>\n

        Is UML design principles relevant in agile development?<\/h3>\n

        More than ever. Agile isn\u2019t about skipping documentation\u2014it\u2019s about making it useful. UML design principles help teams create models that evolve with the code, support refactoring, and guide sprint planning. When every diagram is tied to intent, it becomes a living artifact, not a relic.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Too many developers treat UML class diagrams as a mecha […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":950,"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-954","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUML Design Principles: Building Intent, Not Just Structure<\/title>\n<meta name=\"description\" content=\"Master UML design principles by focusing on design intent modeling. Learn how to move beyond syntax to build robust, maintainable systems grounded in responsibility-driven mindset and CRC philosophy.\" \/>\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\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"UML Design Principles: Building Intent, Not Just Structure\" \/>\n<meta property=\"og:description\" content=\"Master UML design principles by focusing on design intent modeling. Learn how to move beyond syntax to build robust, maintainable systems grounded in responsibility-driven mindset and CRC philosophy.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/\" \/>\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=\"7 \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\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/\",\"name\":\"UML Design Principles: Building Intent, Not Just Structure\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:32:39+00:00\",\"description\":\"Master UML design principles by focusing on design intent modeling. Learn how to move beyond syntax to build robust, maintainable systems grounded in responsibility-driven mindset and CRC philosophy.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"From CRC Cards to Class Diagrams\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Extending and Automating the Workflow\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Conclusion: Designing with Intent, Not Just Structure\"}]},{\"@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":"UML Design Principles: Building Intent, Not Just Structure","description":"Master UML design principles by focusing on design intent modeling. Learn how to move beyond syntax to build robust, maintainable systems grounded in responsibility-driven mindset and CRC philosophy.","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\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/","og_locale":"zh_CN","og_type":"article","og_title":"UML Design Principles: Building Intent, Not Just Structure","og_description":"Master UML design principles by focusing on design intent modeling. Learn how to move beyond syntax to build robust, maintainable systems grounded in responsibility-driven mindset and CRC philosophy.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"7 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/","name":"UML Design Principles: Building Intent, Not Just Structure","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:32:39+00:00","description":"Master UML design principles by focusing on design intent modeling. Learn how to move beyond syntax to build robust, maintainable systems grounded in responsibility-driven mindset and CRC philosophy.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/uml-design-principles-designing-with-intent\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"From CRC Cards to Class Diagrams","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/"},{"@type":"ListItem","position":3,"name":"Extending and Automating the Workflow","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/crc-cards-to-class-diagrams\/crc-automation-uml\/"},{"@type":"ListItem","position":4,"name":"Conclusion: Designing with Intent, Not Just Structure"}]},{"@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\/954","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\/954\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/950"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=954"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=954"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}