Change the subtitle of Hero (#39)

* Change the subtitle with GitHub related message.

* Split deployment and rollback

Author: Noah Lee

docs/concepts/deployment.md

@@ -4,9 +4,7 @@ sidebar_position: 3
 
 # Deployment
 
-## Deploy & Rollback
-
-### Deploy
+## How to deploy?
 **Gitploy provides an intuitive UI that allows users to deploy a specific `ref`.** The UI provides three types of `ref`: *commit*, *branch*, and *tag*. The UI shows a list of options for each type. For example, the UI shows the current commit list with information such as SHA, description, committer if the user selects a commit.
 
 When the user selects `ref`, an icon indicating the commit's status appears on the right, and you can check the subset of contexts by clicking the icon. This information can be handy if you use the `required_contexts` field, which specifies a subset of contexts that must be `success`.
@@ -15,17 +13,6 @@ After that, when you click the deploy button, Gitploy sends a deployment request
 
 ![Deploy](../../static/img/docs/deploy.png)
 
-### Rollback
-We generally run `git revert` and merge the code to roll back. But in this process, we must wait for CI for a long time, which causes an impact on users. Therefore, the rollback must be done quickly and accurately.
-
-**Gitploy provides a quick and easy one-click rollback.** The UI shows a list of completed deployments of which status is `success` when the user selects a runtime environment. And the first option is just the previous deployment.
-
-After that, when the user clicks rollback, Gitploy fetches the payload from the previous deployment and sends a deployment request with the payload to Github. The `ref` from the previous deployment is used in this case. *However, if the ref of the previous deployment is a branch, Gitploy uses SHA to prevent the head of the branch from being deployed.* 
-
-*Note that `auto_merge: false` is set internally to avoid merge conflicts when rollback.*
-
-![Rollback](../../static/img/docs/rollback.png)
-
 ## Deployment Status
 Gitploy provides the UI to view the status after deployment. If you click `View Detail` of the deployment history on the Home tab, the link will take you to the page. 
 

docs/concepts/rollback.md

@@ -0,0 +1,16 @@
+---
+sidebar_position: 3
+---
+
+# Rollback
+
+## How to roll back?
+We generally run `git revert` and merge the code to roll back. But in this process, we must wait for CI for a long time, which causes an impact on users. Therefore, the rollback must be done quickly and accurately.
+
+**Gitploy provides a quick and easy one-click rollback.** The UI shows a list of completed deployments of which status is `success` when the user selects a runtime environment. And the first option is just the previous deployment.
+
+After that, when the user clicks rollback, Gitploy fetches the payload from the previous deployment and sends a deployment request with the payload to Github. The `ref` from the previous deployment is used in this case. *However, if the ref of the previous deployment is a branch, Gitploy uses SHA to prevent the head of the branch from being deployed.* 
+
+*Note that `auto_merge: false` is set internally to avoid merge conflicts when rollback.*
+
+![Rollback](../../static/img/docs/rollback.png)

src/components/HomepageDemo.js

@@ -1,4 +1,5 @@
 import React from 'react';
+import Link from '@docusaurus/Link';
 import clsx from 'clsx';
 import styles from './HomepageDemo.module.css';
 
@@ -7,9 +8,13 @@ export default function HomepageDemo() {
     <section className="padding-vert--xl">
       <div className="container">
         <div className="text--center">
-          <h2>BUILD A POWERFUL DEPLOYMENT SYSTEM</h2>
-          <p>Gitploy provides a fast, safe and secure deployment pipeline to your organization. <br/> Build your deployment system in minutes.</p>
+          <h2>TAKE ADVANTAGE OF A POWERFUL DEPLOYMENT</h2>
+          <p>
+            Gitploy provides the way to deploy in the same manner regardless of types of applications<br/> 
+            and to set up a deployment pipeline with a simple configuration file. 
+          </p>
           <img className={clsx(styles.image, 'shadow--md', )} src={require('../../static/img/docs/gitploy-v3.gif').default}/>
+          <p><Link to="/docs">Explore the documents</Link> to see everything Gitploy can do.</p>
         </div>
       </div>
     </section>

src/pages/index.js

@@ -4,7 +4,6 @@ import Layout from '@theme/Layout';
 import Link from '@docusaurus/Link';
 import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
 import styles from './index.module.css';
-import HomepageFeatures from '../components/HomepageFeatures';
 import HomepageDemo from '../components/HomepageDemo';
 import HomepageInstallation from '../components/HomepageInstallation';
 
@@ -19,8 +18,8 @@ function HomepageHeader() {
           </div>
           <div className="col col--8 col--offset-2">
             <p className="hero__subtitle">
-              It enables your organization <strong>to deploy in the same manner</strong> regardless of the type of applications
-              and <strong>to set up a deployment pipeline differently</strong> with a simple configuration file for each application.
+              Deploy <strong>any branch, tag, or commit</strong> to <strong>different runtime environments</strong> with a click. 
+              It doesn't get any simpler than that. 
             </p>
           </div>
         </div>