{"id":1800,"date":"2026-02-25T10:46:10","date_gmt":"2026-02-25T10:46:10","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/"},"modified":"2026-02-25T10:46:10","modified_gmt":"2026-02-25T10:46:10","slug":"bdd-gherkin-user-stories-acceptance-criteria","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/","title":{"rendered":"Refining Acceptance Criteria with BDD and Gherkin Examples"},"content":{"rendered":"

When acceptance criteria become opaque or inconsistent across teams, even the most well-crafted user stories lose their power to drive shared understanding. I\u2019ve seen this happen repeatedly\u2014teams align on a feature\u2019s goal, only to disagree on what „done” actually means. The solution isn\u2019t more documentation. It\u2019s precision in language and automation at scale.<\/p>\n

BDD gherkin user stories transform vague requirements into executable, testable, and collaborative artifacts. This isn\u2019t just about syntax\u2014it\u2019s about creating a common language that flows from business intent to automated validation. In enterprise settings, where multiple teams may depend on the same story, this alignment prevents misinterpretation, rework, and delivery delays.<\/p>\n

By mastering BDD gherkin examples, you gain the ability to write acceptance criteria that are not only clear but also directly tied to automated tests. This ensures that every story truly delivers value\u2014verified, not assumed.<\/p>\n

Why Gherkin Works for Large-Scale Agile<\/h2>\n

Gherkin syntax provides a lightweight, domain-driven structure that scales without adding bureaucracy. It\u2019s not a tool for every requirement, but a bridge between business people, developers, and testers when clarity is critical.<\/p>\n

At scale, stories often span teams and involve complex decision logic. Gherkin\u2019s Given<\/code>, When<\/code>, Then<\/code> pattern forces teams to identify preconditions, triggers, and outcomes\u2014exactly what\u2019s needed for cross-team synchronization.<\/p>\n

For example, a story involving payment processing across multiple systems isn\u2019t just \u201cUser pays with card.\u201d Its acceptance criteria must define: what happens on success, on timeout, on invalid input, and how it integrates with fraud detection. Gherkin formalizes this.<\/p>\n

Real-World Example: Payment Processing at Scale<\/h3>\n

The following BDD example is derived from a real financial services system where three teams\u2014Payment, Fraud, and Notification\u2014coordinated on a single user story.<\/p>\n

Feature: Process payment with card\n  As a customer\n  I want to be able to pay using a card\n  So that I can complete my purchase securely\n\n  Scenario: Successful card payment with no fraud flags\n    Given the user has selected a total amount of $120\n    And the card details are valid and not expired\n    And the fraud detection system has no flag for the transaction\n    When the user clicks \"Pay Now\"\n    Then the payment should be processed successfully\n    And the order status should change to \"Paid\"\n    And the customer should receive a confirmation email\n<\/code><\/pre>\n
This scenario is now executable. The automation team can wire it to a test suite that validates each step. All three teams understand exactly what „done” means.<\/p>\n
Structuring Acceptance Criteria with BDD<\/h2>\n
Writing acceptance criteria with BDD begins with the story\u2019s feature. The feature file becomes a living document, reviewed during refinement and updated during PI planning.<\/p>\n
Here\u2019s how to structure it for maximum clarity and scalability:<\/p>\n
    \n
  1. Start with the feature<\/strong>\u2014a high-level description of the business value.<\/li>\n
  2. Use meaningful scenarios<\/strong>\u2014each should represent a distinct variation of the story.<\/li>\n
  3. Keep scenarios focused<\/strong>\u2014one user journey per scenario.<\/li>\n
  4. Use plain language<\/strong>\u2014avoid technical terms unless necessary.<\/li>\n
  5. Link to shared acceptance criteria<\/strong>\u2014ensure consistency across teams.<\/li>\n<\/ol>\n
    When multiple teams work on a story, a shared feature file becomes a critical artifact. It prevents each team from interpreting \u201cpayment successful\u201d in isolation.<\/p>\n
    Managing Multiple Scenarios: The Decision Table Approach<\/h3>\n
    For stories with complex decision logic, decision tables in Gherkin help manage multiple inputs and expected outcomes.<\/p>\n\n\n\n\n\n\n
    Input Condition<\/th>\nExpected Outcome<\/th>\nAcceptance Criteria<\/th>\n<\/tr>\n
    Valid card, no fraud flag<\/td>\nPayment processed<\/td>\nThen the order status should be „Paid”<\/td>\n<\/tr>\n
    Invalid card, expired<\/td>\nError shown<\/td>\nThen the user should see „Card expired”<\/td>\n<\/tr>\n
    Valid card, fraud flag raised<\/td>\nPayment declined<\/td>\nThen the payment should be declined and logged<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    This table maps directly to Gherkin scenarios. It ensures no edge case is missed and supports automated test generation.<\/p>\n
    Scaling Acceptance with Shared Templates<\/h2>\n
    Across enterprise teams, consistency is everything. Without shared templates, teams write acceptance criteria differently\u2014even for the same business function.<\/p>\n
    I\u2019ve seen a retail platform where two teams used different terms for the same concept: \u201corder confirmation\u201d vs \u201cpayment receipt.\u201d This led to integration issues. The fix? A standardized Gherkin template for all payment-related stories.<\/p>\n
    Here\u2019s an example of a reusable template:<\/p>\n
    Feature: [User Action] on [System]\n  As a [User Role]\n  I want to [User Goal]\n  So that [Business Value]\n\n  Scenario: [Short Description of Path]\n    Given [Precondition]\n    When [Trigger Event]\n    Then [Expected Outcome]\n    And [Additional Outcome, if needed]\n<\/code><\/pre>\n
    Adopting this template across teams ensures that every story\u2014no matter which team owns it\u2014follows the same structure. This enables automated validation and eases cross-team collaboration.<\/p>\n
    Automating Acceptance: From Gherkin to Execution<\/h2>\n
    Writing BDD scenarios isn\u2019t just about documentation. It\u2019s about creating executable specs.<\/p>\n
    When a team writes a Gherkin scenario, the next step is to map it to automated tests using tools like Cucumber, SpecFlow, or JUnit with BDD extensions.<\/p>\n
    The key benefit? The test runs automatically with every CI\/CD pipeline. If a story fails, the team knows\u2014no ambiguity.<\/p>\n
    Here\u2019s how this integrates with scaled Agile:<\/p>\n
      \n
    • Scenarios are reviewed during story refinement.<\/li>\n
    • They become part of the Definition of Done.<\/li>\n
    • They\u2019re executed during integration testing, not just unit testing.<\/li>\n
    • Failure triggers a feedback loop to the team.<\/li>\n<\/ul>\n
      This closes the loop between business intent and technical delivery.<\/p>\n
      Common Pitfalls and How to Avoid Them<\/h2>\n
      Even with BDD, teams can fall into traps:<\/p>\n
        \n
      • Overusing scenarios<\/strong>: Too many scenarios bloat the test suite. Focus on the critical paths.<\/li>\n
      • Using technical language<\/strong>: Words like \u201cdatabase\u201d or \u201cAPI call\u201d dilute clarity. Describe behavior from the user\u2019s perspective.<\/li>\n
      • Writing scenarios without automation<\/strong>: If a scenario isn\u2019t linked to code, it\u2019s just documentation.<\/li>\n
      • Ignoring edge cases<\/strong>: High-value stories must cover failure paths.<\/li>\n<\/ul>\n
        My advice: Start small. Pick one story per sprint to write in full BDD. Refactor it with the team. Measure how many scenarios are automated. Gradually expand.<\/p>\n
        Frequently Asked Questions<\/h2>\n
        How do I handle acceptance criteria when multiple teams own the same story?<\/h3>\n
        Use a shared feature file. All teams must agree on the Gherkin scenarios. The owning team leads refinement, but every contributor signs off. This ensures alignment and avoids duplicated or conflicting logic.<\/p>\n
        Can BDD be used in non-technical or business-facing teams?<\/h3>\n
        Absolutely. BDD is not just for developers. Business analysts, product owners, and UX designers can use Gherkin to co-write acceptance criteria. It forces clarity and exposes assumptions early.<\/p>\n
        Is BDD only for automated testing?<\/h3>\n
        No. Gherkin is a communication tool first. It becomes automated only if the team chooses. But in large-scale Agile, automation is essential for speed and consistency. The story is the contract\u2014automation enforces it.<\/p>\n
        How do I avoid \u201cgherkin bloat\u201d in large feature files?<\/h3>\n
        Split large feature files by domain or system. Use tags like @payment<\/code>, @fraud<\/code>, @notification<\/code> to group scenarios. Limit each file to 5\u20138 scenarios. Keep the focus on value delivery.<\/p>\n
        Do I need to write BDD for every story?<\/h3>\n
        No. Use BDD for complex, high-risk, or cross-team stories. For simple tasks\u2014like „Update profile name”\u2014a bullet list of acceptance criteria is sufficient. Apply BDD where alignment is fragile.<\/p>\n
        How does BDD integrate with SAFe or LeSS?<\/h3>\n
        In SAFe, BDD scenarios are part of the Program Increment (PI) acceptance criteria. They\u2019re reviewed in IPM (Integrated Product Management) meetings. In LeSS, BDD is used during sprint reviews to verify value delivery. The principle is the same: clarity through collaboration and automation.<\/p>\n","protected":false},"excerpt":{"rendered":"
        When acceptance criteria become opaque or inconsistent across teams, even the most well-crafted user stories lose their power to drive shared understanding. I\u2019ve seen this happen repeatedly\u2014teams align on a feature\u2019s goal, only to disagree on what „done” actually means. The solution isn\u2019t more documentation. It\u2019s precision in language and automation at scale. BDD gherkin […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1792,"menu_order":7,"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-1800","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nBDD Gherkin User Stories: Acceptance Criteria at Scale<\/title>\n<meta name=\"description\" content=\"Master BDD Gherkin user stories for large-scale Agile projects. Learn how to align automated acceptance criteria with scalable story writing across multiple teams and frameworks.\" \/>\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\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BDD Gherkin User Stories: Acceptance Criteria at Scale\" \/>\n<meta property=\"og:description\" content=\"Master BDD Gherkin user stories for large-scale Agile projects. Learn how to align automated acceptance criteria with scalable story writing across multiple teams and frameworks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/\" \/>\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=\"6 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\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/\",\"name\":\"BDD Gherkin User Stories: Acceptance Criteria at Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:46:10+00:00\",\"description\":\"Master BDD Gherkin user stories for large-scale Agile projects. Learn how to align automated acceptance criteria with scalable story writing across multiple teams and frameworks.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/#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\":\"Advanced Story Patterns for Enterprises\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Refining Acceptance Criteria with BDD and Gherkin Examples\"}]},{\"@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":"BDD Gherkin User Stories: Acceptance Criteria at Scale","description":"Master BDD Gherkin user stories for large-scale Agile projects. Learn how to align automated acceptance criteria with scalable story writing across multiple teams and frameworks.","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\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/","og_locale":"pl_PL","og_type":"article","og_title":"BDD Gherkin User Stories: Acceptance Criteria at Scale","og_description":"Master BDD Gherkin user stories for large-scale Agile projects. Learn how to align automated acceptance criteria with scalable story writing across multiple teams and frameworks.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/","name":"BDD Gherkin User Stories: Acceptance Criteria at Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:46:10+00:00","description":"Master BDD Gherkin user stories for large-scale Agile projects. Learn how to align automated acceptance criteria with scalable story writing across multiple teams and frameworks.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/bdd-gherkin-user-stories-acceptance-criteria\/#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":"Advanced Story Patterns for Enterprises","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/"},{"@type":"ListItem","position":4,"name":"Refining Acceptance Criteria with BDD and Gherkin Examples"}]},{"@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\/1800","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\/1800\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1792"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1800"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}