From 6c175abb8f104744e2f5b74dece565af4d7cd6d7 Mon Sep 17 00:00:00 2001
From: synocx <62736272+synocx@users.noreply.github.com>
Date: Tue, 28 Apr 2020 15:26:14 +0800
Subject: [PATCH 1/4] Rename panel/0.7/upgrade/1.0.md to
 panel/1.0/upgrade/1.0.md

---
 panel/{0.7 => 1.0}/upgrade/1.0.md | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename panel/{0.7 => 1.0}/upgrade/1.0.md (100%)

diff --git a/panel/0.7/upgrade/1.0.md b/panel/1.0/upgrade/1.0.md
similarity index 100%
rename from panel/0.7/upgrade/1.0.md
rename to panel/1.0/upgrade/1.0.md

From a1412269c494c323f6dd8d8e4dec5255942be775 Mon Sep 17 00:00:00 2001
From: synocx <62736272+synocx@users.noreply.github.com>
Date: Tue, 28 Apr 2020 15:35:28 +0800
Subject: [PATCH 2/4] Update upgrading.md

---
 panel/0.7/upgrading.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/panel/0.7/upgrading.md b/panel/0.7/upgrading.md
index 20a8e1df..18c8575f 100644
--- a/panel/0.7/upgrading.md
+++ b/panel/0.7/upgrading.md
@@ -26,4 +26,4 @@ php artisan queue:restart
 
 * [0.6.X to 0.7.17](/panel/upgrade/0.6_to_0.7.md)
 * [0.7.X series](/panel/upgrade/0.7.md) <Badge text="current" vertical="middle"/>
-* [1.0.X series](/panel/upgrade/1.0.md) <Badge text="alpha release" vertical="middle"/>
+* [0.7.17 to 1.0.X](/panel/upgrade/0.7_to_1.0.md) <Badge text="alpha release" vertical="middle"/>

From 35c6abd56896d697d09f0ed48af53ba0469af30e Mon Sep 17 00:00:00 2001
From: synocx <62736272+synocx@users.noreply.github.com>
Date: Tue, 28 Apr 2020 15:41:45 +0800
Subject: [PATCH 3/4] Add upgrading.md

---
 panel/1.0/upgrading.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 panel/1.0/upgrading.md

diff --git a/panel/1.0/upgrading.md b/panel/1.0/upgrading.md
new file mode 100644
index 00000000..c9d089e5
--- /dev/null
+++ b/panel/1.0/upgrading.md
@@ -0,0 +1,27 @@
+# Upgrading
+Upgrading the Panel is a relatively simple process. Below you will find a list of articles that will walk you through
+the upgrade process for each version of the software.
+
+## Maintenance Mode
+Whenever you are performing an upgrade you should be sure to place your Panel into maintenance mode. This will prevent
+users from encountering unexpected errors and ensure everything can be upgraded before users being encountering
+potentially new features.
+
+``` bash
+# Put the Panel into maintenance mode and deny user access
+php artisan down
+
+# Bring the Panel back up to receive connections.
+php artisan up
+```
+
+## Restarting Queue Workers
+After _every_ update you should restart the queue worker to ensure that the new code is loaded in and used.
+
+``` bash
+php artisan queue:restart
+```
+
+## Version Specific Guides
+
+* [1.0.X series](/panel/upgrade/1.0.md) <Badge text="alpha release" vertical="middle"/>
\ No newline at end of file

From e70b690f438914acf6ebac83209f44128df27bc8 Mon Sep 17 00:00:00 2001
From: synocx <62736272+synocx@users.noreply.github.com>
Date: Tue, 28 Apr 2020 15:43:53 +0800
Subject: [PATCH 4/4] Update config.js

---
 .vuepress/config.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.vuepress/config.js b/.vuepress/config.js
index 57bfdb1b..43421312 100644
--- a/.vuepress/config.js
+++ b/.vuepress/config.js
@@ -146,7 +146,8 @@ module.exports = {
                             status: 'beta',
                             children: [
                                 '/getting_started',
-                                '/webserver_configuration'
+                                '/webserver_configuration', 
+                                '/upgrading' 
                             ]
                         }
                     ]