diff --git a/_data/patcher-landing-page-tabs-terraform-upgrade.yml b/_data/patcher-landing-page-tabs-terraform-upgrade.yml new file mode 100644 index 000000000..4768b0e84 --- /dev/null +++ b/_data/patcher-landing-page-tabs-terraform-upgrade.yml @@ -0,0 +1,7 @@ +- id: pr + title: Example Pull Request + content: https://s6.gifyu.com/images/tf92e8ec56f233ce68.gif + +- id: patch + title: tf-14-to-15.patch + content: https://i.imgur.com/mxEkeHw.png diff --git a/pages/landing/patcher/index.html b/pages/landing/patcher/index.html index d6dc614c4..8cfc894c5 100644 --- a/pages/landing/patcher/index.html +++ b/pages/landing/patcher/index.html @@ -3,6 +3,10 @@ type: landing slug: index-page +extra_nav_links: + - name: Use Cases + url: /patcher/use-cases/ + title: "Keep your code up to date, even with breaking changes." excerpt: Patcher automatically creates pull requests to keep your dependencies up to date, updating not only the version numbers, but also patching your code to handle backwards incompatible changes. permalink: /patcher/ diff --git a/pages/landing/patcher/pricing/index.html b/pages/landing/patcher/pricing/index.html index cf5254148..c203e37ff 100644 --- a/pages/landing/patcher/pricing/index.html +++ b/pages/landing/patcher/pricing/index.html @@ -3,6 +3,10 @@ type: landing slug: pricing +extra_nav_links: + - name: Use Cases + url: /patcher/use-cases/ + title: Pick a plan excerpt: Pick the plan just right for your team. permalink: /patcher/pricing/ diff --git a/pages/landing/patcher/use-cases/_hero.html b/pages/landing/patcher/use-cases/_hero.html new file mode 100644 index 000000000..34a6c6c80 --- /dev/null +++ b/pages/landing/patcher/use-cases/_hero.html @@ -0,0 +1,10 @@ +
+
+
+

{{ page.title }}

+

+ {{ page.excerpt }} +

+
+
+
diff --git a/pages/landing/patcher/use-cases/_use-cases.html b/pages/landing/patcher/use-cases/_use-cases.html new file mode 100644 index 000000000..82701e2ff --- /dev/null +++ b/pages/landing/patcher/use-cases/_use-cases.html @@ -0,0 +1,182 @@ +{% for item in page.use_cases %} +
+ {% if item.tab_block %} +
+
+ {% for tab in site.data.patcher-landing-page-tabs-terraform-upgrade %} +
+ +
+ {% endfor %} +
+
+ {% for tab in site.data.patcher-landing-page-tabs-terraform-upgrade %} +
+ +
+ {% endfor %} +
+
+ {% endif %} + {% if item.image %} +
+ +
+ {% endif %} +
+

{{ item.heading }}

+

{{ item.body }}

+
+ {% for logo in item.logos %} +
+
+ {{ logo.title }} +
+ {{ logo.title }} +
+ {% endfor %} +
+
+
+{% endfor %} + + + + diff --git a/pages/landing/patcher/use-cases/index.html b/pages/landing/patcher/use-cases/index.html new file mode 100644 index 000000000..79bb6d2ac --- /dev/null +++ b/pages/landing/patcher/use-cases/index.html @@ -0,0 +1,75 @@ +--- +layout: landing +type: landing +slug: index-page + +extra_nav_links: + - name: Use Cases + url: /patcher/use-cases/ + +title: Patcher Use Cases +excerpt: Some examples of scenarios where Patcher can be useful +permalink: /patcher/use-cases/ + +use_cases: + - heading: "Use case 1: Update to Terraform 1.0 automatically" + tab_block: site.data.patcher-landing-page-tabs-terraform-upgrade + body: | + + + - heading: "Use case 2: Automatically patch a severe security vulnerability in Ruby on Rails" + image: https://rubyonrails.org/images/rails-logo.svg + image_width: 379px + image_side: left + body: | + + + - heading: "Use case 3: Update to a new version of an internal utility" + image: https://upload.wikimedia.org/wikipedia/de/thumb/e/e1/Java-Logo.svg/1200px-Java-Logo.svg.png + image_width: 200px + body: | +
    +
  1. Let's say you are the maintainer of a security.jar library that is used by 300 microservices (300 other teams) within your company.
  2. +
  3. When you open a pull request with some changes to security.jar, Patcher automatically finds all the services that depends on security.jar, runs their tests with your updates, and shows you the results, so you know if you made breaking changes.
  4. +
  5. If you did make breaking changes, you can create a Patch File to patch those services, and Patcher will show you the results of both applying your Patch File and executing the tests of each service.
  6. +
  7. Once all tests are passing, you merge, release a new version of security.jar, and Patcher opens pull requests against all those services to update them to the new version.
  8. +
+ - heading: "Use case 4: Update to React 17.0 automatically" + image: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9Ii0xMS41IC0xMC4yMzE3NCAyMyAyMC40NjM0OCI+CiAgPHRpdGxlPlJlYWN0IExvZ288L3RpdGxlPgogIDxjaXJjbGUgY3g9IjAiIGN5PSIwIiByPSIyLjA1IiBmaWxsPSIjNjFkYWZiIi8+CiAgPGcgc3Ryb2tlPSIjNjFkYWZiIiBzdHJva2Utd2lkdGg9IjEiIGZpbGw9Im5vbmUiPgogICAgPGVsbGlwc2Ugcng9IjExIiByeT0iNC4yIi8+CiAgICA8ZWxsaXBzZSByeD0iMTEiIHJ5PSI0LjIiIHRyYW5zZm9ybT0icm90YXRlKDYwKSIvPgogICAgPGVsbGlwc2Ugcng9IjExIiByeT0iNC4yIiB0cmFuc2Zvcm09InJvdGF0ZSgxMjApIi8+CiAgPC9nPgo8L3N2Zz4K + image_side: left + image_width: 379px + body: | + + +footer: + heading: Keep your code up to day, even with breaking changes + body: | + + cta: Request early access! +--- + +
+
+ {% include_relative _hero.html %} +
+
+
+ {% include_relative _use-cases.html %} +
+
+