chutney 3.12.2 → 3.12.3

data/{usechutney.com/docs/rules/file-name-differs-feature-name/index.md → usechutney.com.site/site/src/docs/rules/file-name-differs-feature-name.page.md}

@@ -1,8 +1,4 @@
----
-title: "File Name Differs From Feature Name"
-layout: single
-permalink: /docs/rules/file-name-differs-feature-name/
----
+# File Name Differs From Feature Name
 
 The name of a feature file should match the name of the feature it describes. This makes it easier to find the feature file that contains a specific scenario.
 
@@ -34,4 +30,4 @@ Feature: logging in
     Given I have visited the website
     When I log in
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/givens-after-background/index.md → usechutney.com.site/site/src/docs/rules/givens-after-background.page.md}

@@ -1,8 +1,4 @@
----
-title: "Givens After Background"
-layout: single
-permalink: /docs/rules/givens-after-background/
----
+# Givens After Background
 
 If you have a `Background` section in a feaure file and your scenarios still need to do some setup, you should start immediately with an `And` step. This makes it clear that the setup is in addition to the background and makes it obvious that the scenario is not sufficient on its own.
 
@@ -33,4 +29,4 @@ Background:
     And I have logged in
     When I view my profile
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/inconsistent-quoting/index.md → usechutney.com.site/site/src/docs/rules/inconsistent-quoting.page.md}

@@ -1,8 +1,4 @@
----
-title: "Inconsistent Quoting"
-layout: single
-permalink: /docs/rules/inconsistent-quoting/
----
+# Inconsistent Quoting
 
 Use either single or double quotes consistently throughout your feature files. This makes it clear to the reader where your strings and variables are.
 
@@ -26,4 +22,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "username" and "password"
     Then I will see my account
-```
+```

data/usechutney.com.site/site/src/docs/rules/index.page.md

@@ -0,0 +1,43 @@
+# Rules
+
+* [Avoid Colons at Start of Names](/docs/rules/avoid-colons-at-start-of-names)
+* [Avoid Comma in Tags](/docs/rules/avoid-comma-in-tags)
+* [Avoid Full Stops](/docs/rules/avoid-full-stops)
+* [Avoid Outline for Single Example](/docs/rules/avoid-outline-for-single-example)
+* [Avoid Scripting](/docs/rules/avoid-scripting)
+* [Avoid Splat Steps in Background](/docs/rules/avoid-splat-steps-in-background)
+* [Avoid Splat Steps in Scenarios](/docs/rules/avoid-splat-steps-in-scenarios)
+* [Avoid Typographers' Quotes](/docs/rules/avoid-typographers-quotes)
+* [Background Does More Than Setup](/docs/rules/background-does-more-than-setup)
+* [Background Requires Multiple Scenarios](/docs/rules/background-requires-multiple-scenarios)
+* [Bad Scenario Name](/docs/rules/bad-scenario-name)
+* [Empty Feature File](/docs/rules/empty-feature-file)
+* [File Name Differs From Feature Name](/docs/rules/file-name-differs-feature-name)
+* [Givens After Background](/docs/rules/givens-after-background)
+* [Inconsistent Quoting](/docs/rules/inconsistent-quoting)
+* [Invalid Step Flow](/docs/rules/invalid-step-flow)
+* [Invalid File Name](/docs/rules/invalid_file_name)
+* [Missing Example Name](/docs/rules/missing-example-name)
+* [Missing Example Table](/docs/rules/missing-example-table)
+* [Missing Feature Description](/docs/rules/missing-feature-description)
+* [Missing Feature Name](/docs/rules/missing-feature-name)
+* [Missing Scenario Name](/docs/rules/missing-scenario-name)
+* [Missing Scenario Outline](/docs/rules/missing-scenario-outline)
+* [Missing Test Action](/docs/rules/missing-test-action)
+* [Missing Test Verification](/docs/rules/missing-test-verification)
+* [Required Tags Starts With](/docs/rules/required-tag-starts-with)
+* [Same Scenario](/docs/rules/same-scenario)
+* [Same Tag Different Case](/docs/rules/same-tag-different-case)
+* [Same Tag For All Scenarios](/docs/rules/same-tag-for-all-scenarios)
+* [Scenario Names Match](/docs/rules/scenario-names-match)
+* [Tag Used Multiple Times](/docs/rules/tag-used-multiple-times)
+* [Too Clumsy](/docs/rules/too-clumsy)
+* [Too Long Step](/docs/rules/too-long-step)
+* [Too Many Different Tags](/docs/rules/too-many-different-tags)
+* [Too Many Steps](/docs/rules/too-many-steps)
+* [Too Many Tags](/docs/rules/too-many-tags)
+* [Unique Scenario Names](/docs/rules/unique-scenario-names)
+* [Unknown Variable](/docs/rules/unknown-variable)
+* [Unused Variable](/docs/rules/unused-variable)
+* [Use Background](/docs/rules/use-background)
+* [Use Outline](/docs/rules/use-outline)

data/{usechutney.com/docs/rules/invalid-step-flow/index.md → usechutney.com.site/site/src/docs/rules/invalid-step-flow.page.md}

@@ -1,8 +1,4 @@
----
-title: "Invalid Step Flow"
-layout: single
-permalink: /docs/rules/invalid-step-flow/
----
+# Invalid Step Flow
 
 Scenarios should follow the Given-When-Then structure. This makes it clear to the reader what the scenario is doing and what the expected outcome is.
 
@@ -28,4 +24,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "username" and "password"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/invalid_file_name/index.md → usechutney.com.site/site/src/docs/rules/invalid_file_name.page.md}

@@ -1,8 +1,4 @@
----
-title: "Invalid File Name"
-layout: single
-permalink: /docs/rules/invalid-file-name/
----
+# Invalid File Name
 
 The name of the feature file should be in `snake_case` and end with `.feature`. It should not be in `mixedCase` or contain spaces. This makes sure that the feature file can easily be found on different types of operating system which have different file naming conventions.
 
@@ -16,4 +12,4 @@ The name of the feature file should be in `snake_case` and end with `.feature`.
 ## Good
 
 {: .notice}
-`logging_in.feature`
+`logging_in.feature`

data/{usechutney.com/docs/rules/missing-example-name/index.md → usechutney.com.site/site/src/docs/rules/missing-example-name.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Example Name"
-layout: single
-permalink: /docs/rules/missing-example-name/
----
+# Missing Example Name
 
 If you have more than one example table in a scenario, you should give each example a name. This makes it easier to understand what each example is testing.
 
@@ -46,4 +42,4 @@ Feature: logging in
       | username | password |
       | admin1   | pass1    |
       | admin2   | pass2    |
-```
+```

data/{usechutney.com/docs/rules/missing-example-table/index.md → usechutney.com.site/site/src/docs/rules/missing-example-table.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Example Table"
-layout: single
-permalink: /docs/rules/missing-example-table/
----
+# Missing Example Table
 
 You have a scenario outline without an example table. You should add an example table to the scenario outline to show what the scenario is testing, or convert the scenario outline to a scenario if you do not need to test multiple examples.
 
@@ -31,4 +27,4 @@ Feature: logging in
       | username | password |
       | user1    | pass1    |
       | user2    | pass2    |
-```
+```

data/{usechutney.com/docs/rules/missing-feature-description/index.md → usechutney.com.site/site/src/docs/rules/missing-feature-description.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Feature Description"
-layout: single
-permalink: /docs/rules/missing-feature-description/
----
+# Missing Feature Description
 
 You should write a description for your feature in the form of a value-statements. This makes it clear to the reader what the feature is doing and why it is important.
 
@@ -22,4 +18,4 @@ Feature: logging in
   As a user,
   I want to log in to the website,
   so that I can access my account.
-```
+```

data/{usechutney.com/docs/rules/missing-feature-name/index.md → usechutney.com.site/site/src/docs/rules/missing-feature-name.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Feature Name"
-layout: single
-permalink: /docs/rules/missing-feature-name/
----
+# Missing Feature Name
 
 Your `Feature` should have a name that describes what the feature is doing. This makes it clear to the reader what the feature is doing and why it is important.
 
@@ -16,4 +12,4 @@ Feature:
 
 ```gherkin
 Feature: logging in
-```
+```

data/{usechutney.com/docs/rules/missing-scenario-name/index.md → usechutney.com.site/site/src/docs/rules/missing-scenario-name.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Scenario Name"
-layout: single
-permalink: /docs/rules/missing-scenario-name/
----
+# Missing Scenario Name
 
 Your `Scenario` and `Scenario Outline` should have a name that describes what the feature is doing. This makes it clear to the reader what the feature is doing and why it is important.
 
@@ -16,4 +12,4 @@ Scenario:
 
 ```gherkin
 Scenario: logging in
-```
+```

data/{usechutney.com/docs/rules/missing-scenario-outline/index.md → usechutney.com.site/site/src/docs/rules/missing-scenario-outline.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Scenario Outline"
-layout: single
-permalink: /docs/rules/missing-scenario-outline/
----
+# Missing Scenario Outline
 
 You have a `Scenario` with an example table, but you should use a `Scenario Outline` instead. This makes it clear to the reader that the scenario is a template for multiple examples.
 
@@ -36,4 +32,4 @@ Feature: logging in
       | username | password |
       | user1    | pass1    |
       | user2    | pass2    |
-```
+```

data/{usechutney.com/docs/rules/missing-test-action/index.md → usechutney.com.site/site/src/docs/rules/missing-test-action.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Test Action"
-layout: single
-permalink: /docs/rules/missing-test-action/
----
+# Missing Test Action
 
 You have a `Scenario` or `Scenario Outline` without a `When` step. You should add a `When` step to show what the scenario is testing.
 
@@ -25,4 +21,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "<username>" and "<password>"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/missing-test-verification/index.md → usechutney.com.site/site/src/docs/rules/missing-test-verification.page.md}

@@ -1,8 +1,4 @@
----
-title: "Missing Test Verification"
-layout: single
-permalink: /docs/rules/missing-test-verification/
----
+# Missing Test Verification
 
 You have a `Scenario` or `Scenario Outline` without a `Then` step. You should add a `Then` step to show what the scenario is testing.
 
@@ -25,4 +21,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "<username>" and "<password>"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/required-tag-starts-with/index.md → usechutney.com.site/site/src/docs/rules/required-tag-starts-with.page.md}

@@ -1,8 +1,4 @@
----
-title: "Required Tags Starts With"
-layout: single
-permalink: /docs/rules/required-tags-start-with/
----
+# Required Tags Starts With
 
 This is a rule which you can configure to enforce a naming convention for tags. This rule will check that all tags on a feature start with a specific prefix.
 
@@ -28,4 +24,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "<username>" and "<password>"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/same-scenario/index.md → usechutney.com.site/site/src/docs/rules/same-scenario.page.md}

@@ -1,8 +1,4 @@
----
-title: "Same Scenario"
-layout: single
-permalink: /docs/rules/same-scenario/
----
+# Same Scenario
 
 You have a `Scenario`, or a `Scenario Outline` which appears to be duplicated. This probably means you have a redundant test. You should probably make sure you only have one copy of your steps to be consitent and efficient.
 
@@ -20,5 +16,4 @@ Feature: Test
   Scenario: Scenario B
       When I do a thing
       Then A thing happens
-```
-
+```

data/{usechutney.com/docs/rules/same-tag-different-case/index.md → usechutney.com.site/site/src/docs/rules/same-tag-different-case.page.md}

@@ -1,8 +1,4 @@
----
-title: "Same Tag Different Case"
-layout: single
-permalink: /docs/rules/same-tag-different-case/
----
+# Same Tag Different Case
 
 Cucumber tags are case-sensitive. Be careful when using tags that are the same but have different cases, you might not get the results you expect if you use tags to select scenarios.
 
@@ -39,4 +35,4 @@ Feature: logging in
     Given I have visited the website
     When I log out
     Then I will see the login page
-```
+```

data/{usechutney.com/docs/rules/same-tag-for-all-scenarios/index.md → usechutney.com.site/site/src/docs/rules/same-tag-for-all-scenarios.page.md}

@@ -1,8 +1,4 @@
----
-title: "Same Tag For All Scenarios"
-layout: single
-permalink: /docs/rules/same-tag-for-all-scenarios/
----
+# Same Tag For All Scenarios
 
 You have the same tag for all scenarios. This is not recommended because it makes it difficult to filter scenarios by tags. Instead, set the tag at the \`Feature` level.
 
@@ -39,4 +35,4 @@ Feature: Login
     Given I am on the login page
     When I enter invalid credentials
     Then I should see an error message
-```
+```

data/{usechutney.com/docs/rules/scenario-names-match/index.md → usechutney.com.site/site/src/docs/rules/scenario-names-match.page.md}

@@ -1,8 +1,4 @@
----
-title: "Scenario Names Match"
-layout: single
-permalink: /docs/rules/scenario-names-match/
----
+# Scenario Names Match
 
 This is a rule which you can configure to enforce a naming convention for scenarios. This rule will check that all scenario names match a regular expression.
 
@@ -27,4 +23,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "<username>" and "<password>"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/tag-used-multiple-times/index.md → usechutney.com.site/site/src/docs/rules/tag-used-multiple-times.page.md}

@@ -1,8 +1,4 @@
----
-title: "Tag Used Multiple Times"
-layout: single
-permalink: /docs/rules/tag-used-multiple-times/
----
+# Tag Used Multiple Times
 
 Avoid using the same tag at both the feature and scenario level. If it is used at the feature level it is redundant at the scenario level. This rule will check that tags are not used multiple times in the same feature file.
 
@@ -29,4 +25,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "<username>" and "<password>"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/too-clumsy/index.md → usechutney.com.site/site/src/docs/rules/too-clumsy.page.md}

@@ -1,8 +1,4 @@
----
-title: "Too Clumsy"
-layout: single
-permalink: /docs/rules/too-clumsy/
----
+# Too Clumsy
 
 Avoid having very long or wordy scenarios. They are difficult to read and maintain and are often a sign that the scenario is doing too much or there is scripting involved. This rule will checks the total number of character in a scenario.
 
@@ -75,4 +71,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "validusername" and "validpassword"
     Then I will see my account details
-```
+```

data/{usechutney.com/docs/rules/too-long-step/index.md → usechutney.com.site/site/src/docs/rules/too-long-step.page.md}

@@ -1,8 +1,4 @@
----
-title: "Too Long Step"
-layout: single
-permalink: /docs/rules/too-long-step/
----
+# Too Long Step
 
 Avoid having very long or wordy steps. They are difficult to read and maintain and are often a sign that the step is doing too much or there is scripting involved. This rule will check that steps are not too long. Having an 'and' inside the step is often a clue that you have a compound step that should be broken down into smaller steps.
 
@@ -27,4 +23,4 @@ Feature: logging in
     And I have logged with credentials "validusername" and "validpassword"
     When I view my profile
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/too-many-different-tags/index.md → usechutney.com.site/site/src/docs/rules/too-many-different-tags.page.md}

@@ -1,8 +1,4 @@
----
-title: "Too Many Different Tags"
-layout: single
-permalink: /docs/rules/too-many-different-tags/
----
+# Too Many Different Tags
 
 Avoid a tag soup by using too many different tags in a feature file. It suggests that redundant tags have been left in the feature file and have not been cleaned up.
 
@@ -29,4 +25,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "<username>" and "<password>"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/too-many-steps/index.md → usechutney.com.site/site/src/docs/rules/too-many-steps.page.md}

@@ -1,8 +1,4 @@
----
-title: "Too Many Steps"
-layout: single
-permalink: /docs/rules/too-many-steps/
----
+# Too Many Steps
 
 Avoid having too many steps in a scenario. Scenarios should be concise and focused on a single behavior. This rule will check that scenarios do not have too many steps.
 
@@ -76,4 +72,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "validusername" and "validpassword"
     Then I will see my account details
-```
+```

data/{usechutney.com/docs/rules/too-many-tags/index.md → usechutney.com.site/site/src/docs/rules/too-many-tags.page.md}

@@ -1,8 +1,4 @@
----
-title: "Too Many Tags"
-layout: single
-permalink: /docs/rules/too-many-tags/
----
+# Too Many Tags
 
 Avoid a tag soup by using too many tags in a feature file. It suggests that redundant tags have been left in the feature file and have not been cleaned up.
 
@@ -29,4 +25,4 @@ Feature: logging in
     Given I have visited the website
     When I log in with "<username>" and "<password>"
     Then I will see my account
-```
+```

data/{usechutney.com/docs/rules/unique-scenario-names/index.md → usechutney.com.site/site/src/docs/rules/unique-scenario-names.page.md}

@@ -1,8 +1,4 @@
----
-title: "Unique Scenario Names"
-layout: single
-permalink: /docs/rules/unique-scenario-names/
----
+# Unique Scenario Names
 
 Avoid duplicating scenario names. Scenario names should be unique within a feature file so that they are meaningful and easy to identify. This rule will check that scenario names are unique within a feature file.
 
@@ -36,4 +32,4 @@ Feature: logging in
     Given I have visited the website
     When I log out
     Then I will see the login page
-```
+```

data/{usechutney.com/docs/rules/unknown-variable/index.md → usechutney.com.site/site/src/docs/rules/unknown-variable.page.md}

@@ -1,8 +1,4 @@
----
-title: "Unknown Variable"
-layout: single
-permalink: /docs/rules/unknown-variable/
----
+# Unknown Variable
 
 You are referencing a variable which does not appear to be defined in the example table. This is probably an accident and your test might not be doing what you expect. This rule will check that all variables used in a scenario are defined in the example table.
 
@@ -35,4 +31,4 @@ Feature: logging in
     Examples:
       | username | password | admin |
       | user1    | password | true  |
-```
+```

data/{usechutney.com/docs/rules/unused-variable/index.md → usechutney.com.site/site/src/docs/rules/unused-variable.page.md}

@@ -1,8 +1,4 @@
----
-title: "Unused Variable"
-layout: single
-permalink: /docs/rules/unused-variable/
----
+# Unused Variable
 
 You have defined a variable in your example table but you are not using it. This is probably an accident and your test might not be doing what you expect. This rule will check that all variables defined in the example table are used in the scenario.
 
@@ -34,4 +30,4 @@ Feature: logging in
     Examples:
       | username | password |
       | user1    | password |
-```
+```

data/{usechutney.com/docs/rules/use-background/index.md → usechutney.com.site/site/src/docs/rules/use-background.page.md}

@@ -1,8 +1,4 @@
----
-title: "Use Background"
-layout: single
-permalink: /docs/rules/use-background/
----
+# Use Background
 
 You have multiple scenarios that all have the same setup steps. This is a sign that you should use a background to define the common setup steps once and reuse them in each scenario. This rule will check that you are using a background when you have multiple scenarios with the same setup steps.
 
@@ -37,4 +33,4 @@ Feature: logging in
   Scenario: logging out
     When I log out
     Then I will see the login page
-```
+```

data/{usechutney.com/docs/rules/use-outline/index.md → usechutney.com.site/site/src/docs/rules/use-outline.page.md}

@@ -1,8 +1,4 @@
----
-title: "Use Outline"
-layout: single
-permalink: /docs/rules/use-outline/
----
+# Use Outline
 
 You have multiple scenarios that are almost identical. This is a sign that you should use a scenario outline to define the common steps once and reuse them with different inputs. This rule will check that you are using a scenario outline when you have multiple scenarios that are almost identical.
 
@@ -36,4 +32,4 @@ Feature: logging in
       | username | password |
       | user1    | password |
       | user2    | password |
-```
+```

data/{usechutney.com/docs/running/index.md → usechutney.com.site/site/src/docs/running.page.md}

@@ -1,8 +1,4 @@
----
-title: "Running Chutney"
-layout: single
-permalink: /docs/running/
----
+# Running Chutney
 
 Once you have [installed Chutney](/docs/installing/), you can run it from the command line.
 
@@ -30,4 +26,4 @@ foo.feature
   MissingScenarioName
     This scenario is unnamed. You should name all scenarios.
     foo.feature:13
-```
+```

data/{usechutney.com/pages/index.markdown → usechutney.com.site/site/src/index.page.md}

@@ -1,39 +1,30 @@
----
-# Feel free to add content and custom Front Matter to this file.
-# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
-
-# layout: single
-layout: splash
-permalink: /
-author_profile: false
-
-feature_row:
-  - image_path: /assets/images/mr_pickle.png
-    alt: "A happy jar of pickles smiling at you"
-    title: "Best Practice Cucumber"
-    excerpt: "Love your documentation, and your documentation will love you back."
-    url: "/docs/installing/"
-    btn_label: "Get Started"
-    btn_class: "btn btn--success"
----
-
-{% include feature_row type="center" %}
-
+<div class="hero-section">
+  <img src="/mr_pickle.png" alt="Chutney mascot Mr Pickle, a friendly cartoon pickle character wearing a bow tie" width="200">
+
+    <h1>Chutney</h1>
+    <p style="font-size: 1.5rem; color: var(--text-muted); max-width: 600px; margin: 0 auto;">Beautiful and tasteful best practice for Cucumber</p>
+    <div style="margin-top: 2rem;">
+      <a href="/docs/installing" class="btn btn-primary">Get Started</a>
+      <a href="/docs/rules" class="btn" style="background: white; border: 1px solid var(--border); margin-left: 10px; color: var(--text-main);">View Rules</a>
+    </div>
+</div>
+
+## Why Chutney?
 You’re trying to follow BDD or ATDD principles, you’re writing executable specifications in gherkin using Cucumber, you’re trying to do the *right thing* but are you doing the *thing right?*
 
-# Tests are your documentation
+## Tests are your documentation
 
 Requirements are your longest-lived asset. Your implementation might change, your tests might change, but your requirements (specifications) continue to exist. They should be clear, concise, and easy to understand. They should be easy to read, easy to write, and easy to maintain. They should be your documentation.
 
 Cucumber makes it easy to write requirements in a human-readable format. It doesn't need any tool other than a text editor to write and read. It's a great tool to write requirements in a way that everyone can understand and that can be versioned and stored in a version control system with the rest of your code.
 
-# When cucumbers go bad
+## When cucumbers go bad
 
 Cucumber specifications can be a great asset, but they can also be a liability. In the exchange between business language and the language of testers and software developers, it's easy to lose the meaning of the requirements. It's easy to write specifications that are hard to read, hard to write, and hard to maintain.
 
 Chutney helps you write better Cucumber specifications. It helps you write specifications that are clear, concise, and easy to understand. It helps you write specifications that are easy to read, easy to write, and easy to maintain. Be kind to your future self and your team. Love your documentation, and your documentation will love you back.
 
-# What is Chutney?
+## What is Chutney?
 
 Chutney is a Ruby tool that reads your Cucumber feature files and tells you how you can make them better. It's a linter for Cucumber. It will help you avoid common pitfalls and anti-patterns in your Cucumber feature files. It will help you write better Cucumber specifications.
 

data/usechutney.com.site/site/templates/_nav.html.erb

@@ -0,0 +1,6 @@
+<nav>
+  <a href="/">Home</a>
+  <a href="/docs">Docs</a>
+  <a href="/docs/rules">Rules</a>
+  <a href="/about">About</a>
+</nav>

data/usechutney.com.site/site/templates/layout.html.erb

@@ -0,0 +1,35 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <title><%= title %> - <%= site_name %></title>
+  <link rel="apple-touch-icon" sizes="180x180" href="/favicons/apple-touch-icon.png">
+  <link rel="icon" type="image/png" sizes="32x32" href="/favicons/favicon-32x32.png">
+  <link rel="icon" type="image/png" sizes="16x16" href="/favicons/favicon-16x16.png">
+  <link rel="manifest" href="/favicons/site.webmanifest">
+  <link rel="stylesheet" href="/styles.css">
+  <link rel="preconnect" href="https://fonts.googleapis.com">
+  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+  <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700&family=JetBrains+Mono&display=swap" rel="stylesheet">
+</head>
+<body>
+  <header class="site-header">
+    <div class="container">
+      <a href="/" class="site-title">Chutney</a>
+      <%= render 'nav' %>
+    </div>
+  </header>
+
+  <main class="container">
+    <%= content %>
+  </main>
+
+  <footer class="site-footer">
+    <div class="container">
+      <p>&copy; <%= Time.now.year %> Chutney. Beautiful and tasteful best practice for Cucumber. GitHub: <a href="https://github.com/BillyRuffian/chutney">BillyRuffian/chutney</a></p>
+      <p>Documentation generated with <a href="https://usejackdaw.com">Jackdaw</a>.</p>
+    </div>
+  </footer>
+</body>
+</html>

data/usechutney.com.site/site/templates/page.html.erb

@@ -0,0 +1,3 @@
+<main>
+  <%= content %>
+</main>