{"id":584,"date":"2026-02-25T10:20:40","date_gmt":"2026-02-25T10:20:40","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/"},"modified":"2026-02-25T10:20:40","modified_gmt":"2026-02-25T10:20:40","slug":"bpmn-flow-direction-issues","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/","title":{"rendered":"Inconsistent Use of Direction and Flow Conventions"},"content":{"rendered":"<p>When I first started working with BPMN, I was handed a diagram that zigzagged across the page\u2014left to right, then top to bottom, then back again. It wasn\u2019t just messy. It felt like reading a story where the narrator jumps between timelines without warning. That\u2019s what inconsistent BPMN flow direction issues do: they break the reader\u2019s mental model and make the process feel unpredictable.<\/p>\n<p>Flow direction isn\u2019t just about layout. It\u2019s a core convention that guides how people interpret sequences, decisions, and handoffs. When teams mix left-to-right and top-to-bottom flows without clear rules, they create diagrams that are technically correct but practically useless.<\/p>\n<p>This chapter is about fixing that. You\u2019ll learn how to identify inconsistent BPMN conventions, apply consistent flow standards, and build team-wide practices that make your models clearer, more reliable, and easier to maintain.<\/p>\n<h2>Why Flow Direction Matters<\/h2>\n<p>Flow direction is not arbitrary. It\u2019s a visual signal. Most readers expect processes to unfold from top to bottom or left to right\u2014much like reading a book. When that expectation is broken, cognitive load increases.<\/p>\n<p>Consider a decision point where one outcome flows right and another flows down. The reader must pause and reorient. That pause becomes a mental hurdle every time. Over a complex diagram, these breaks add up.<\/p>\n<p>BPMN itself doesn\u2019t mandate a single direction. But the <strong>BPMN diagram direction standards<\/strong> set by the OMG and popular in enterprise modeling tools strongly favor top-to-bottom for internal processes and left-to-right for collaboration diagrams.<\/p>\n<h3>Common Patterns of Inconsistency<\/h3>\n<p>Here are the most frequent signs of flow direction issues:<\/p>\n<ul>\n<li>Same decision node sends one branch left, another down.<\/li>\n<li>First flow goes left-to-right, second flow switches to top-to-bottom.<\/li>\n<li>Sub-processes flow in opposite directions from their parent.<\/li>\n<li>Message flows between pools use inconsistent angles or directions.<\/li>\n<\/ul>\n<p>These inconsistencies confuse the reader. Worse, they create ambiguity in execution logic\u2014especially when automated.<\/p>\n<h2>Establishing Team-Wide Flow Conventions<\/h2>\n<p>There\u2019s no one-size-fits-all rule. But there are <strong>standardizing BPMN flow<\/strong> principles that work across most domains.<\/p>\n<p>Start by selecting a primary flow direction:<\/p>\n<ol>\n<li><strong>Top-to-bottom (Recommended for most internal processes):<\/strong> Best for sequential workflows like order fulfillment, case management, or approval chains.<\/li>\n<li><strong>Left-to-right (Recommended for collaboration diagrams):<\/strong> Ideal for cross-functional or multi-pool processes where multiple parties are involved.<\/li>\n<\/ol>\n<p>Once chosen, apply it consistently across all diagrams in your repository. This includes sub-processes, event subprocesses, and embedded decision points.<\/p>\n<h3>Visual Clarity Over Flexibility<\/h3>\n<p>Some modelers argue that \u201cthe diagram should flow naturally.\u201d But natural flow only matters when everyone agrees on what \u201cnatural\u201d means. Without a shared standard, \u201cnatural\u201d becomes personal preference.<\/p>\n<p>Example: A process starts with a \u201cCheck eligibility\u201d task that flows left. But the next step is \u201cApprove application,\u201d which flows down. Why the shift? No reason. It\u2019s just a layout choice\u2014yet it breaks the reader\u2019s mental map.<\/p>\n<p>Here\u2019s a better rule: <strong>Flow direction should be consistent within a single diagram, regardless of complexity.<\/strong><\/p>\n<h2>Before and After: Fixing Inconsistent Flow<\/h2>\n<p>Let\u2019s look at a real-world example.<\/p>\n<h3>Before: Mixed Flow Direction<\/h3>\n<p>A loan approval process starts with a top-down flow but shifts to left-to-right after the \u201cEvaluate Risk\u201d gateway. One branch goes right, another down. The handoff to the \u201cCredit Check\u201d task appears disconnected from the main line.<\/p>\n<p>This design doesn\u2019t break BPMN\u2019s syntax, but it confuses readers. Is the risk evaluation a side activity? Is the credit check dependent on it? The answer isn\u2019t clear.<\/p>\n<h3>After: Unified Top-to-Bottom Flow<\/h3>\n<p>Revised version: All steps now flow top to bottom. The \u201cEvaluate Risk\u201d gateway splits into two paths: one goes down for \u201cLow Risk,\u201d the other down for \u201cHigh Risk.\u201d The \u201cCredit Check\u201d task is now clearly below the decision node.<\/p>\n<p>Now, every step follows the same visual rhythm. Readers can trace the process in one continuous motion. No mental reorientation. No ambiguity.<\/p>\n<p>This is what <strong>standardizing BPMN flow<\/strong> looks like in practice: clear, predictable, and reliable.<\/p>\n<h2>Practical Steps to Fix Your Flow<\/h2>\n<p>Here\u2019s a simple checklist to audit and correct flow direction issues.<\/p>\n<ol>\n<li><strong>Define your team\u2019s flow convention:<\/strong> Choose top-to-bottom or left-to-right as default. Apply to all new diagrams.<\/li>\n<li><strong>Review existing diagrams:<\/strong> Identify any mixed flows. Flag them for refactoring.<\/li>\n<li><strong>Refactor with consistent flow:<\/strong> Realign elements so all major flows move in the same direction.<\/li>\n<li><strong>Document the standard:<\/strong> Add a section in your modeling guide: \u201cAll processes follow top-to-bottom flow unless a collaboration diagram justifies left-to-right.\u201d<\/li>\n<li><strong>Use tooling to enforce:<\/strong> Many BPMN tools (like Visual Paradigm) allow you to set default flow direction. Enable it to reduce manual errors.<\/li>\n<\/ol>\n<p>Don\u2019t underestimate the power of a single rule. A team of 10 modelers, all following the same flow direction, will produce diagrams that feel like parts of the same system\u2014even if they never collaborate directly.<\/p>\n<h2>When to Use Left-to-Right Flow<\/h2>\n<p>Left-to-right flow isn\u2019t just for collaboration diagrams. It works well when:<\/p>\n<ul>\n<li>Modeling a customer journey across touchpoints.<\/li>\n<li>Showing handoffs between departments where direction matters (e.g., HR \u2192 Payroll).<\/li>\n<li>Representing parallel or alternative paths that don\u2019t fit naturally in a vertical stack.<\/li>\n<\/ul>\n<p>But if you switch to left-to-right, ensure consistency. Don\u2019t make one diagram horizontal and another vertical without a strong reason.<\/p>\n<h2>Key Takeaways<\/h2>\n<p>Bad BPMN diagrams don\u2019t just confuse readers\u2014they undermine trust in the entire process model. Consistent flow direction isn\u2019t about aesthetics. It\u2019s about clarity, correctness, and shared understanding.<\/p>\n<p>Remember: <strong>BPMN flow direction issues<\/strong> are avoidable with a simple team agreement and consistent application. The goal isn\u2019t perfection. It\u2019s predictability.<\/p>\n<p>Start small. Pick one diagram. Fix the flow. Show your team. Repeat. Over time, you\u2019ll build a culture where clarity is valued over creativity.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Should all BPMN diagrams use the same flow direction?<\/h3>\n<p>No\u2014but consistency within a diagram is essential. Use top-to-bottom for internal processes. Use left-to-right for collaboration or customer journey models. Stick to one per diagram.<\/p>\n<h3>Can I mix flow directions if it improves readability?<\/h3>\n<p>Not without risking confusion. Even if it \u201clooks\u201d better, mixing directions breaks the reader\u2019s mental model. If a layout feels awkward, restructure it using one consistent flow, not multiple.<\/p>\n<h3>What\u2019s the most common flow mistake in BPMN?<\/h3>\n<p>Mixing top-to-bottom and left-to-right flows without intent. This often happens in larger diagrams when modelers improvise. The result is a fragmented, hard-to-follow process.<\/p>\n<h3>How do I enforce consistent flow in a team with diverse experience?<\/h3>\n<p>Create a lightweight BPMN modeling guide. Include a flow direction rule: \u201cAll processes use top-to-bottom flow unless otherwise specified.\u201d Share examples. Use tool validation features to flag inconsistent flows.<\/p>\n<h3>Do BPMN standards require a specific flow direction?<\/h3>\n<p>No formal standard mandates direction, but top-to-bottom is the de facto default in practice. The OMG\u2019s reference diagrams use vertical flow. Follow that pattern for maximum readability.<\/p>\n<h3>Should I restructure old diagrams to fix flow direction?<\/h3>\n<p>Yes\u2014especially if they\u2019ll be reused or shared. A small investment in restructuring saves time, reduces errors, and strengthens team alignment over time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I first started working with BPMN, I was handed a diagram that zigzagged across the page\u2014left to right, then top to bottom, then back again. It wasn\u2019t just messy. It felt like reading a story where the narrator jumps between timelines without warning. That\u2019s what inconsistent BPMN flow direction issues do: they break the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":578,"menu_order":5,"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-584","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>BPMN Flow Direction Issues: Fix Consistency Now<\/title>\n<meta name=\"description\" content=\"Fix inconsistent BPMN flow direction issues. Learn standardizing BPMN flow patterns, avoid confusion, and ensure your diagrams are readable and consistent across teams.\" \/>\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\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Flow Direction Issues: Fix Consistency Now\" \/>\n<meta property=\"og:description\" content=\"Fix inconsistent BPMN flow direction issues. Learn standardizing BPMN flow patterns, avoid confusion, and ensure your diagrams are readable and consistent across teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/\",\"name\":\"BPMN Flow Direction Issues: Fix Consistency Now\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:20:40+00:00\",\"description\":\"Fix inconsistent BPMN flow direction issues. Learn standardizing BPMN flow patterns, avoid confusion, and ensure your diagrams are readable and consistent across teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Structural, Flow, and Layout Problems\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Inconsistent Use of Direction and Flow Conventions\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Flow Direction Issues: Fix Consistency Now","description":"Fix inconsistent BPMN flow direction issues. Learn standardizing BPMN flow patterns, avoid confusion, and ensure your diagrams are readable and consistent across teams.","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\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/","og_locale":"de_DE","og_type":"article","og_title":"BPMN Flow Direction Issues: Fix Consistency Now","og_description":"Fix inconsistent BPMN flow direction issues. Learn standardizing BPMN flow patterns, avoid confusion, and ensure your diagrams are readable and consistent across teams.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/","name":"BPMN Flow Direction Issues: Fix Consistency Now","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:20:40+00:00","description":"Fix inconsistent BPMN flow direction issues. Learn standardizing BPMN flow patterns, avoid confusion, and ensure your diagrams are readable and consistent across teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-flow-direction-issues\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Structural, Flow, and Layout Problems","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/"},{"@type":"ListItem","position":4,"name":"Inconsistent Use of Direction and Flow Conventions"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/584","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/584\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/578"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=584"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=584"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}