{"id":1770,"date":"2026-02-25T10:46:00","date_gmt":"2026-02-25T10:46:00","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/"},"modified":"2026-02-25T10:46:00","modified_gmt":"2026-02-25T10:46:00","slug":"splitting-epics-into-stories-at-scale","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/","title":{"rendered":"Splitting Large Epics into Manageable Stories"},"content":{"rendered":"<p>Large systems demand large thinking\u2014but not large stories. The key insight is this: a well-formed epic is not a container of work, but a promise of value. When that promise is broken down, it must remain tied to measurable user outcomes. I\u2019ve led dozens of teams through this exact transformation, and the most common mistake isn\u2019t lack of effort\u2014it\u2019s misaligned decomposition.<\/p>\n<p>Splitting epics into stories isn\u2019t about creating more work. It\u2019s about making value visible at the team level. If your teams aren\u2019t building toward a tangible outcome, you\u2019re not scaling agility\u2014you\u2019re scaling bureaucracy.<\/p>\n<p>Here, you\u2019ll learn proven agile splitting techniques that preserve meaning, flow, and ownership. These are not theoretical patterns. They\u2019re field-tested methods used in global enterprises, with real examples from banking, healthcare, and SaaS platforms. You\u2019ll understand when to use each approach, how to avoid common dependency traps, and how to keep story slicing at scale aligned with business goals.<\/p>\n<h2>Why Decomposition Matters in Large-Scale Agile<\/h2>\n<p>At scale, every story must answer two questions: Who benefits? And how do we know it\u2019s done?<\/p>\n<p>When epics become too large, teams often lose sight of the user. The result? Stories with ambiguous acceptance criteria, unclear ownership, and alignment drift.<\/p>\n<p>Agile splitting techniques are designed to prevent this. They ensure every story delivers a piece of value that can be tested, demonstrated, and measured\u2014regardless of which team or domain owns it.<\/p>\n<h3>The Value Drift Problem<\/h3>\n<p>Consider an epic titled \u201cSecure Online Payment Experience.\u201d Without proper splitting, teams might produce stories like:<\/p>\n<ul>\n<li>\u201cImplement payment gateway integration\u201d<\/li>\n<li>\u201cAdd fraud detection module\u201d<\/li>\n<li>\u201cDesign user interface for payment form\u201d<\/li>\n<\/ul>\n<p>These are technical tasks, not user stories. They don\u2019t start with \u201cAs a user\u2026\u201d and fail to show how value is delivered.<\/p>\n<p>Correct decomposition starts with the user. The real story is: \u201cAs a customer, I want to complete a payment securely so I can finish my purchase without fear of fraud.\u201d That\u2019s the anchor.<\/p>\n<h2>Core Agile Splitting Techniques<\/h2>\n<p>There\u2019s no single way to split an epic. But there are patterns that work across contexts. Use them with intent, not as templates.<\/p>\n<h3>1. By User Flow (Use Case Driven)<\/h3>\n<p>Break the epic by the user journey. This is one of the most reliable methods for story slicing at scale.<\/p>\n<p>Example: \u201cSecure Payment Experience\u201d can be split into:<\/p>\n<ul>\n<li>As a customer, I want to enter my payment details so I can proceed to checkout.<\/li>\n<li>As a customer, I want to verify my identity via 3D Secure so my payment is protected.<\/li>\n<li>As a customer, I want to receive a confirmation email after payment so I know it was successful.<\/li>\n<\/ul>\n<p>These are not features\u2014they are atomic interactions that a user would experience in sequence. Each delivers a piece of value and can be tested independently.<\/p>\n<h3>2. By Business Function (Capability-Based)<\/h3>\n<p>Group stories by the business capability they serve. This works well when multiple teams are involved in a single domain.<\/p>\n<p>Example: \u201cCustomer Onboarding\u201d can be split into:<\/p>\n<ul>\n<li>As a new user, I want to create an account so I can access the platform.<\/li>\n<li>As a new user, I want to verify my email so I can unlock full features.<\/li>\n<li>As a new user, I want to upload my ID so I can pass identity verification.<\/li>\n<\/ul>\n<p>Each story maps to a distinct function. This allows teams to own and deliver independently while still integrating into a full user journey.<\/p>\n<h3>3. By Data or State (State-Based)<\/h3>\n<p>Use this when the epic involves transitions between system states.<\/p>\n<p>Example: \u201cOrder Management\u201d can be split by order lifecycle stages:<\/p>\n<ul>\n<li>As a customer, I want to place an order so I can receive my products.<\/li>\n<li>As a customer, I want to track my order status so I can plan for delivery.<\/li>\n<li>As a customer, I want to return a defective product so I can get a refund.<\/li>\n<\/ul>\n<p>Each story corresponds to a state transition: Order Created \u2192 Order Shipped \u2192 Order Returned. This is ideal for systems with complex workflows.<\/p>\n<h3>4. By Technical Layer (Architecture-Driven)<\/h3>\n<p>Use with caution. This is often a trap for teams that focus on implementation over value.<\/p>\n<p>Example: \u201cSecure Payment Experience\u201d split by layers:<\/p>\n<ul>\n<li>As a developer, I want to implement encryption at rest so data is protected.<\/li>\n<li>As a developer, I want to add JWT token validation so only authenticated users can access the API.<\/li>\n<\/ul>\n<p>These are not user stories. They\u2019re internal technical improvements. They should be in the backlog, but not as primary stories. Instead, they support the real user value.<\/p>\n<h2>Decision Matrix for Splitting Epics<\/h2>\n<p>Use this checklist to evaluate whether a story is truly independent, valuable, and testable.<\/p>\n<table border=\"1\" cellpadding=\"5\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Criteria<\/th>\n<th>Check<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>Starts with \u201cAs a [user]\u201d<\/td>\n<td>\u2705<\/td>\n<td>Ensures user-centric focus<\/td>\n<\/tr>\n<tr>\n<td>Delivers measurable value<\/td>\n<td>\u2705<\/td>\n<td>Prevents invisible work<\/td>\n<\/tr>\n<tr>\n<td>Testable with one acceptance criterion<\/td>\n<td>\u2705<\/td>\n<td>Enables clear Done definition<\/td>\n<\/tr>\n<tr>\n<td>Can be delivered by one team in one sprint<\/td>\n<td>\u2705<\/td>\n<td>Supports flow and predictability<\/td>\n<\/tr>\n<tr>\n<td>Independent of other stories<\/td>\n<td>\u2705<\/td>\n<td>Reduces dependency risk<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Apply this to every story. If it fails more than one criterion, reconsider the split.<\/p>\n<h2>Common Pitfalls in Story Slicing at Scale<\/h2>\n<p>Even with the best intentions, teams fall into traps. Here are the most frequent.<\/p>\n<h3>Over-Engineering the Split<\/h3>\n<p>Some teams believe every story must be \u201csmall.\u201d But size isn\u2019t the only measure\u2014value and independence matter more.<\/p>\n<p>Example: Breaking \u201cOrder Processing\u201d into 20 stories that only cover input validation is not helpful. Focus on end-to-end value, not technical minutiae.<\/p>\n<h3>Creating \u201cEpics by Proxy\u201d<\/h3>\n<p>Teams sometimes split an epic into smaller epics. That doesn\u2019t solve the problem. It just defers it.<\/p>\n<p>Ask: Is this still a user-focused story? If not, it\u2019s an epic in disguise.<\/p>\n<h3>Over-Reliance on Technical Categories<\/h3>\n<p>Splitting by framework, language, or database is not a valid user story. These are implementation details.<\/p>\n<p>Always ask: Does the user care about this? If not, it belongs in the technical backlog or as a non-functional requirement.<\/p>\n<h2>Practical Workflow for Splitting at Scale<\/h2>\n<p>Here\u2019s how I\u2019ve run it in real programs:<\/p>\n<ol>\n<li><strong>Start from the user journey.<\/strong> Map the end-to-end experience. Who is involved? What do they do?<\/li>\n<li><strong>Identify key decision points.<\/strong> Where does the user pause, confirm, or react? Each is a potential story.<\/li>\n<li><strong>Write as a user.<\/strong> Every story must begin \u201cAs a [role], I want\u2026 so I can\u2026\u201d<\/li>\n<li><strong>Validate with acceptance criteria.<\/strong> Can the story be tested? Is there a clear \u201cDone\u201d?<\/li>\n<li><strong>Assign to teams.<\/strong> Ensure ownership is clear. Avoid ambiguous \u201cshared\u201d ownership.<\/li>\n<li><strong>Review for dependency risk.<\/strong> Use a dependency map to flag coupling between stories.<\/li>\n<\/ol>\n<p>This workflow ensures that splitting epics into stories is not just a task\u2014but a collaborative design process.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know when a story is small enough?<\/h3>\n<p>A story is small enough when it can be completed by one team in one sprint without blocking others. If it requires coordination across more than two teams, reconsider the split. Aim for stories that take 1\u20135 days of effort.<\/p>\n<h3>Can a story span multiple teams?<\/h3>\n<p>Yes\u2014but only if it\u2019s a shared capability and the teams are aligned on scope and delivery. Use cross-team story workshops to define common goals, acceptance criteria, and handoff points. Avoid \u201cghost ownership.\u201d<\/p>\n<h3>What if my epic is too complex to split?<\/h3>\n<p>Break it into sub-epics. Then apply the same rules. Never deliver a story that can\u2019t be tested or doesn\u2019t deliver user value. Use story mapping to visualize the flow and find natural breakpoints.<\/p>\n<h3>How do I avoid story bloat in large programs?<\/h3>\n<p>Enforce a story quality audit. Use checklists like the one above. Hold regular refinement sessions with all teams. If a story takes more than 30 minutes to explain, it\u2019s not ready.<\/p>\n<h3>Do I need a central story owner?<\/h3>\n<p>No. Instead, assign story ownership based on domain and delivery responsibility. Use community of practice meetings to align on shared concepts and templates. Avoid top-down mandates.<\/p>\n<h3>How does story slicing at scale affect estimation?<\/h3>\n<p>Smaller, well-defined stories improve estimation accuracy. Teams can use story points or time-based estimates based on past velocity. Avoid estimating at the epic level\u2014only at the story level.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Large systems demand large thinking\u2014but not large stories. The key insight is this: a well-formed epic is not a container of work, but a promise of value. When that promise is broken down, it must remain tied to measurable user outcomes. I\u2019ve led dozens of teams through this exact transformation, and the most common mistake [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1768,"menu_order":1,"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-1770","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>Splitting Epics into Stories at Scale<\/title>\n<meta name=\"description\" content=\"Master agile splitting techniques to break down large epics into measurable, team-friendly stories. Learn story slicing at scale with expert methods that preserve user value and flow.\" \/>\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\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Splitting Epics into Stories at Scale\" \/>\n<meta property=\"og:description\" content=\"Master agile splitting techniques to break down large epics into measurable, team-friendly stories. Learn story slicing at scale with expert methods that preserve user value and flow.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/\",\"name\":\"Splitting Epics into Stories at Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:46:00+00:00\",\"description\":\"Master agile splitting techniques to break down large epics into measurable, team-friendly stories. Learn story slicing at scale with expert methods that preserve user value and flow.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Structuring Large-Scale Backlogs\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Splitting Large Epics into Manageable Stories\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Splitting Epics into Stories at Scale","description":"Master agile splitting techniques to break down large epics into measurable, team-friendly stories. Learn story slicing at scale with expert methods that preserve user value and flow.","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\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/","og_locale":"pl_PL","og_type":"article","og_title":"Splitting Epics into Stories at Scale","og_description":"Master agile splitting techniques to break down large epics into measurable, team-friendly stories. Learn story slicing at scale with expert methods that preserve user value and flow.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"7 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/","name":"Splitting Epics into Stories at Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:46:00+00:00","description":"Master agile splitting techniques to break down large epics into measurable, team-friendly stories. Learn story slicing at scale with expert methods that preserve user value and flow.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/splitting-epics-into-stories-at-scale\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Structuring Large-Scale Backlogs","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/"},{"@type":"ListItem","position":4,"name":"Splitting Large Epics into Manageable Stories"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1770","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1770\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1768"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1770"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1770"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}