{"id":588,"date":"2026-02-25T10:20:42","date_gmt":"2026-02-25T10:20:42","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/"},"modified":"2026-02-25T10:20:42","modified_gmt":"2026-02-25T10:20:42","slug":"missing-bpmn-annotations","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/","title":{"rendered":"Forgetting Annotations, Descriptions, and Business Context"},"content":{"rendered":"<p>Too many modelers build diagrams using only symbols and flow lines, assuming that the visual structure alone conveys meaning. That\u2019s a dangerous assumption.<\/p>\n<p>Even a correctly drawn BPMN diagram can mislead if its intent isn\u2019t clear. A gateway labeled \u201cCheck status\u201d might mean different things to IT, compliance, and operations teams.<\/p>\n<p>I\u2019ve reviewed hundreds of models where the flow was technically sound\u2014but the intent behind key decisions, rule references, or edge cases was entirely absent. That\u2019s what happens when you skip annotations.<\/p>\n<p>Missing BPMN annotations aren\u2019t just a documentation oversight\u2014they\u2019re a breach of trust with your stakeholders. A diagram without context is a guess, not a plan.<\/p>\n<p>Here\u2019s the truth: Every decision point, every exception path, every business rule that can\u2019t be expressed in the diagram\u2019s symbols needs a textual explanation. And the right place for that is an annotation.<\/p>\n<p>You don\u2019t need to clutter your model with text. A single well-placed annotation can carry the weight of a thousand meetings.<\/p>\n<h2>Why Annotations Are Non-Negotiable in BPMN<\/h2>\n<p>Think of BPMN as a conversation. The symbols are the words. The annotations are the tone, the context, the reasoning.<\/p>\n<p>Without them, you\u2019re leaving your audience to infer intent\u2014which usually leads to mistakes.<\/p>\n<p>Consider this: a gateway with no annotation may imply \u201cif the customer is eligible\u201d\u2014but eligibility is defined by a policy that\u2019s not in the diagram. That rule needs to be captured somewhere.<\/p>\n<p>Annotations are the place to reference external documents, explain business assumptions, and flag edge cases that are critical to compliance or implementation.<\/p>\n<p>When you skip this step, you\u2019re not simplifying\u2014you\u2019re hiding complexity.<\/p>\n<h3>When to Use BPMN Text Annotations<\/h3>\n<p>Not every activity needs an annotation. But the following are strong candidates:<\/p>\n<ul>\n<li>Decisions with multiple conditions or non-obvious logic<\/li>\n<li>Exception paths or alternate flows<\/li>\n<li>Activities that depend on external rules (e.g., legal, policy, or regulatory requirements)<\/li>\n<li>Gateways with ambiguous labels like \u201cReview\u201d or \u201cApprove\u201d<\/li>\n<li>Handoffs between departments or systems where responsibility is not self-evident<\/li>\n<\/ul>\n<p>These are the moments when a simple note can prevent weeks of rework.<\/p>\n<h3>Where to Place Annotations (and Why It Matters)<\/h3>\n<p>Annotations should be placed <strong>adjacent to the element they clarify<\/strong>, not floating in the corner.<\/p>\n<p>Most BPMN tools allow you to attach annotations directly to activities, gateways, or events. Use this feature. The annotation should be visible when the diagram is viewed at normal scale.<\/p>\n<p>A common mistake is placing annotations near the edge of the canvas, where they\u2019re overlooked. They\u2019re not decorative\u2014they\u2019re part of the model.<\/p>\n<p>Think of it like footnotes: they belong close to the point they explain, not at the end of a document.<\/p>\n<p>Use color coding or icons in your annotations to distinguish between types: <strong>\u201cRule Reference\u201d<\/strong>, <strong>\u201cException Handling\u201d<\/strong>, <strong>\u201cBusiness Assumption\u201d<\/strong>.<\/p>\n<h2>How to Document BPMN Diagrams Effectively<\/h2>\n<p>Documenting BPMN diagrams isn\u2019t about writing a manual\u2014it\u2019s about building trust.<\/p>\n<p>When stakeholders see an annotation that says \u201cPer Policy ABC-123, eligibility requires 6 months of residency,\u201d they know this isn\u2019t a guess. It\u2019s a documented decision.<\/p>\n<p>Here\u2019s how to structure your annotations:<\/p>\n<ol>\n<li><strong>Start with the purpose<\/strong>: What is this annotation for? Is it a rule, an assumption, or a process edge case?<\/li>\n<li><strong>Keep it concise<\/strong>: One sentence is enough. Avoid long paragraphs.<\/li>\n<li><strong>Reference externally<\/strong>: Cite the policy, regulation, or system that defines the behavior.<\/li>\n<li><strong>Use consistent formatting<\/strong>: If you use \u201cRule:\u201d or \u201cRef:\u201d prefixes, do so across the entire model.<\/li>\n<\/ol>\n<p>This approach makes your diagrams audit-ready and reusable across teams.<\/p>\n<h3>Real Example: A Decision That Didn\u2019t Need a Gate<\/h3>\n<p>Imagine a process where a customer\u2019s application is reviewed. At the gateway, the label says \u201cEligible?\u201d<\/p>\n<p>Without annotation, a business analyst might assume eligibility means \u201chas a job.\u201d But in reality, it means \u201chas been verified by the compliance system and has no active sanctions.\u201d<\/p>\n<p>Add an annotation:<\/p>\n<pre><code>Rule: Eligibility requires:\n- No sanctions in the past 24 months\n- Verified by Compliance System v3.2\n- Minimum 6 months of continuous employment\nRef: Policy ABC-123, Section 4.2<\/code><\/pre>\n<p>Now the model is not just correct\u2014it\u2019s defendable.<\/p>\n<h2>Adding Business Context to BPMN: Beyond the Diagram<\/h2>\n<p>Annotations are part of a larger ecosystem of documentation. You can\u2019t rely on them alone.<\/p>\n<p>Use the <strong>description field<\/strong> in your BPMN tool to capture high-level context: process purpose, scope, stakeholders, and assumptions.<\/p>\n<p>For example:<\/p>\n<pre><code>Scope: This process covers the end-to-end onboarding of new customers in the EMEA region.\nPurpose: To ensure compliance with GDPR and local data laws during onboarding.\nStakeholders: Customer Service, Compliance, IT Security.\nAssumptions: All customers must provide valid identification documents before approval.<\/code><\/pre>\n<p>This description appears when you open the model in a tool or export documentation.<\/p>\n<p>Pair this with annotations for decision logic. The result? A model that\u2019s not just readable\u2014it\u2019s <strong>actionable<\/strong>.<\/p>\n<h3>Best Practices for Using Annotations<\/h3>\n<ul>\n<li>Use annotations to explain <strong>why<\/strong>, not what.<\/li>\n<li>Never rely on annotations to define core process steps\u2014those belong in the diagram.<\/li>\n<li>Use consistent formatting across all annotations (font, color, label).<\/li>\n<li>Review annotations during model reviews\u2014just like you would with any other part of the model.<\/li>\n<li>Update annotations when business rules change.<\/li>\n<\/ul>\n<p>Annotations aren\u2019t clutter. They\u2019re clarity.<\/p>\n<h2>Common Mistakes When Adding Annotations<\/h2>\n<p>Even with the best intentions, teams make errors.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Mistake<\/th>\n<th>Consequence<\/th>\n<th>Fix<\/th>\n<\/tr>\n<tr>\n<td>Placing annotations far from the element<\/td>\n<td>Readers miss them; context is lost<\/td>\n<td>Attach directly to the element<\/td>\n<\/tr>\n<tr>\n<td>Writing long paragraphs<\/td>\n<td>Overwhelms readers; reduces readability<\/td>\n<td>One sentence max; use bullet points if needed<\/td>\n<\/tr>\n<tr>\n<td>Using vague labels like \u201cImportant\u201d or \u201cNote\u201d<\/td>\n<td>Doesn\u2019t convey content or purpose<\/td>\n<td>Start with: \u201cRule:\u201d, \u201cRef:\u201d, \u201cAssumption:\u201d, \u201cEdge Case:\u201d<\/td>\n<\/tr>\n<tr>\n<td>Forgetting to update annotations after rule changes<\/td>\n<td>Model becomes outdated and misleading<\/td>\n<td>Link annotations to versioned policy documents<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These are not minor oversights. They are design flaws that compromise accuracy.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How many annotations should I add to a BPMN diagram?<\/h3>\n<p>There\u2019s no magic number. Add one annotation for every decision point, exception path, or rule that isn\u2019t self-evident. If you\u2019re asking \u201cshould I annotate this?\u201d\u2014the answer is likely yes.<\/p>\n<h3>Can I use annotations in BPMN tools like Visual Paradigm or Camunda?<\/h3>\n<p>Absolutely. Both support text annotations. Use them to reference external rules, explain complex conditions, and capture assumptions. The tool doesn\u2019t matter\u2014what matters is consistency.<\/p>\n<h3>What if my team resists adding annotations?<\/h3>\n<p>Start small. Pick one problematic process and document it with annotations. Show how it reduced ambiguity in the next meeting. Build trust through results.<\/p>\n<h3>Do annotations affect BPMN validation or automation?<\/h3>\n<p>No. Annotations are purely for human interpretation. They don\u2019t influence flow logic or execution. But they make the model easier to audit, document, and maintain.<\/p>\n<h3>How do I ensure annotations stay up to date?<\/h3>\n<p>Link them to versioned documents. If a policy changes, update the reference in the annotation. Make annotation updates part of your change control process.<\/p>\n<h3>Can I use annotations to explain system behavior?<\/h3>\n<p>Yes, but only if the behavior is not part of the business process. For example: \u201cThis step triggers a background job via API call.\u201d But avoid using annotations to replace business logic\u2014save that for the model.<\/p>\n<p>When you stop treating annotations as optional and start seeing them as essential, your BPMN models transform from visuals into living documents.<\/p>\n<p>They become shared artifacts\u2014not just for IT, but for business, compliance, and governance.<\/p>\n<p>And that\u2019s where real value begins.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many modelers build diagrams using only symbols and flow lines, assuming that the visual structure alone conveys meaning. That\u2019s a dangerous assumption. Even a correctly drawn BPMN diagram can mislead if its intent isn\u2019t clear. A gateway labeled \u201cCheck status\u201d might mean different things to IT, compliance, and operations teams. I\u2019ve reviewed hundreds of [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":585,"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-588","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>Fix Missing BPMN Annotations for Clarity<\/title>\n<meta name=\"description\" content=\"Avoid misinterpretation by adding BPMN text annotations, descriptions, and business context. Learn how to use annotations effectively without cluttering your diagram.\" \/>\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\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fix Missing BPMN Annotations for Clarity\" \/>\n<meta property=\"og:description\" content=\"Avoid misinterpretation by adding BPMN text annotations, descriptions, and business context. Learn how to use annotations effectively without cluttering your diagram.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/\",\"name\":\"Fix Missing BPMN Annotations for Clarity\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:20:42+00:00\",\"description\":\"Avoid misinterpretation by adding BPMN text annotations, descriptions, and business context. Learn how to use annotations effectively without cluttering your diagram.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Naming, Documentation, and Communication\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Forgetting Annotations, Descriptions, and Business Context\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Fix Missing BPMN Annotations for Clarity","description":"Avoid misinterpretation by adding BPMN text annotations, descriptions, and business context. Learn how to use annotations effectively without cluttering your diagram.","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\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/","og_locale":"id_ID","og_type":"article","og_title":"Fix Missing BPMN Annotations for Clarity","og_description":"Avoid misinterpretation by adding BPMN text annotations, descriptions, and business context. Learn how to use annotations effectively without cluttering your diagram.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/","name":"Fix Missing BPMN Annotations for Clarity","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:20:42+00:00","description":"Avoid misinterpretation by adding BPMN text annotations, descriptions, and business context. Learn how to use annotations effectively without cluttering your diagram.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/missing-bpmn-annotations\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Naming, Documentation, and Communication","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-naming-and-documentation-mistakes\/"},{"@type":"ListItem","position":4,"name":"Forgetting Annotations, Descriptions, and Business Context"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/588","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/588\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/585"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=588"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}