From 8933963f7e0e022bdffbe18a979b33d22b27c958 Mon Sep 17 00:00:00 2001 From: Andrew Lisowski Date: Mon, 1 Feb 2021 12:19:14 -0800 Subject: [PATCH 1/2] restructure home page --- docs/plugins/home.js | 449 ++++++++++++++++++++++--------------------- 1 file changed, 234 insertions(+), 215 deletions(-) diff --git a/docs/plugins/home.js b/docs/plugins/home.js index 36c4550a2..fd0a5f92c 100644 --- a/docs/plugins/home.js +++ b/docs/plugins/home.js @@ -73,230 +73,249 @@ const FrequentlyAskedQuestion = ({ question, answer }) => ( ); +const ContentWrapper = (props) => ( +
+); + +const FAQ = () => ( + +
+
+

+ Frequently asked questions +

+ + + + + Do you really release{" "} + every pull + request?! + + } + answer={ + <> + Yup!{" "} + But if you don't want to do that it's up to you. The tools{" "} + auto ships with can be used to{" "} + + fit any workflow + + ! You can also use {" "} + labels or configure auto to only release + with a label. + + } + /> + + + + + Is there a way to hook into auto and + customize my release process? + + } + answer={ + <> + Many of auto's features are{" "} + + built into plugins + + . You can also use this plugin system to do{" "} + + almost anything + {" "} + during your release! + + } + /> + + + + + Does auto support any other types of + releases? + + } + answer={ + <> +

+ Yes! auto has commands for any situation! +

+ +

+ Want a test version? Try a{" "} + + canary + +

+ +

+ Want a prerelease? Try creating a pre-release branch and using{" "} + + next + +

+ +

+ Need to patch an old major release? auto{" "} + can automatically make branches for{" "} + + old major versions + + ! +

+ +

+ Or if you don't want to worry about what command to you need, + just use{" "} + + shipit + + ! This command determines what type of release to make based on + the context it's run in. +

+ + } + /> +
+
+ +); + +const SampleWorkflow = () => ( + +
+ +

+ What does the workflow look like? How easy is it really? +

+ + + + Add a + + } + /> + + +
+ +); + +const Features = () => ( + +
+
+ + Other tools require you to change how any contributor commits to + your project. With auto + leave that baggage behind! + + } + /> + + + + + + +
+ +
+ Changelog example +
+
+ +); + +const Hero = () => ( +
+
+ auto + +

+ Streamline your release workflow and{" "} + + publish constantly! + +

+
+ +
+
+

+ Adding automated releases shouldn't be hard or require changing your + workflow +

+ +

+ auto makes automating releases for your project + as simple adding a to a pull + request. If you're releasing all the time you can be{" "} + + more confident + {" "} + in your releases. And your users might thank you too 😉 +

+
+
+
+); + const Home = () => (
Auto -
-
-
- auto - -

- Streamline your release workflow and{" "} - - publish constantly! - -

-
-
-
-

- Adding automated releases shouldn't be hard or require changing - your workflow -

- -

- auto makes automating releases for your - project as simple adding a to - a pull request. If you're releasing all the time you can be{" "} - - more confident - {" "} - in your releases. And your users might thank you too 😉 -

-
- -
-
- - Other tools require you to change how any contributor - commits to your project. With auto - leave that baggage behind! - - } - /> - - - - - - -
- -
- Changelog example -
-
-
+
+ -
- -

- What does the workflow look like? How easy is it really? -

+ - - - Add a - - } - /> - - -
+ -
-
-

- Frequently asked questions -

- - - - - Do you really release{" "} - every pull - request?! - - } - answer={ - <> - - Yup! - {" "} - But if you don't want to do that it's up to you. The tools{" "} - auto ships with can be used to{" "} - - fit any workflow - - ! You can also use {" "} - labels or configure auto to only - release with a label. - - } - /> - - - - - Is there a way to hook into auto and - customize my release process? - - } - answer={ - <> - Many of auto's features are{" "} - - built into plugins - - . You can also use this plugin system to do{" "} - - almost anything - {" "} - during your release! - - } - /> - - - - - Does auto support any other types of - releases? - - } - answer={ - <> -

- Yes! auto has commands for any - situation! -

- -

- Want a test version? Try a{" "} - - canary - -

- -

- Want a prerelease? Try creating a pre-release branch and - using{" "} - - next - -

- -

- Need to patch an old major release?{" "} - auto can automatically make branches - for{" "} - - old major versions - - ! -

- -

- Or if you don't want to worry about what command to you - need, just use{" "} - - shipit - - ! This command determines what type of release to make based - on the context it's run in. -

- - } - /> -
-
-
+
From 4584f5299c28c42e71a94000cb12092bf8164aff Mon Sep 17 00:00:00 2001 From: Andrew Lisowski Date: Mon, 1 Feb 2021 12:52:47 -0800 Subject: [PATCH 2/2] add more fluff to home page --- docs/plugins/home.js | 49 +++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 46 insertions(+), 3 deletions(-) diff --git a/docs/plugins/home.js b/docs/plugins/home.js index fd0a5f92c..2a63a9e34 100644 --- a/docs/plugins/home.js +++ b/docs/plugins/home.js @@ -191,9 +191,8 @@ const FAQ = () => ( const SampleWorkflow = () => ( -
- -

+
+

What does the workflow look like? How easy is it really?

@@ -264,6 +263,48 @@ const Features = () => ( ); +const ReleaseType = ({ type, description, color = "primary" }) => ( +
+

{type}

+

{description}

+
+); + +const ReleaseTypes = () => ( +
+ +
+

+ A release for any situation! +

+

+ auto can create multiple types of releases. + Each release type guarantees that no matter the situation you'll be + able to publish and consume a release with your changes. +

+ +
+ + + +
+
+ +
+); + const Hero = () => (
@@ -313,6 +354,8 @@ const Home = () => ( + +