[airavata-django-portal] branch master updated: Improving the wagtail theme export docs

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

machristie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airavata-django-portal.git


The following commit(s) were added to refs/heads/master by this push:
     new 6f0b0b2  Improving the wagtail theme export docs
6f0b0b2 is described below

commit 6f0b0b26eb12a44d0af22c2e528b2e92d36017d7
Author: Marcus Christie <ma...@apache.org>
AuthorDate: Wed Oct 30 16:47:24 2019 -0400

    Improving the wagtail theme export docs
---
 docs/dev/wagtail_export.md | 64 ++++++++++++++++++++++++++++++++++++----------
 1 file changed, 51 insertions(+), 13 deletions(-)

diff --git a/docs/dev/wagtail_export.md b/docs/dev/wagtail_export.md
index bc609f3..fe5c8a2 100644
--- a/docs/dev/wagtail_export.md
+++ b/docs/dev/wagtail_export.md
@@ -41,25 +41,20 @@ Airavata backend running.
 python manage.py createsuperuser
 ```
 
-4. You can either start from scratch, or start from an existing Wagtail export.
-   If you don't want to start from an export you can start the server, log into
-   <http://localhost:8000/cms> and start creating pages.
-
-5. To start from an existing Wagtail export, first remove the database.
+4. (Optional) To start from an existing Wagtail export, run
+   `python manage.py load_cms_data FILENAME`, where FILENAME is the name of one
+   of the Wagtail exports in
+   [fixtures](https://github.com/apache/airavata-django-portal/tree/master/django_airavata/wagtailapps/base/fixtures)
+   directory. For example, you can run
 
 ```
-rm db.sqlite3
+python manage.py load_cms_data default.json
 ```
 
-6. Run `python manage.py migrate`.
-
-7. Run `python manage.py load_cms_data FILENAME`, where FILENAME is the name of
-   one of the Wagtail exports in
-   [fixtures](https://github.com/apache/airavata-django-portal/tree/master/django_airavata/wagtailapps/base/fixtures)
-   directory. For example, you can run
+5. Start the Django server and log in at <http://localhost:8000/cms>
 
 ```
-python manage.py load_cms_data default.json
+python manage.py runserver
 ```
 
 ## Creating the Wagtail export
@@ -79,6 +74,49 @@ export file.
 
 2. Commit any media files that were added as part of creating the Wagtail pages.
 
+## Resetting your local environment
+
+1. To start over, first remove (or rename) the database.
+
+!!! warning
+
+    db.sqlite3 stores all of the Wagtail changes you have made. Only remove
+    this if you have already exported the wagtail changes to a file. See the
+    previous section.
+
+```
+rm db.sqlite3
+```
+
+2. Migrate the database:
+
+```
+python manage.py migrate
+```
+
+3. Create a superuser account. You'll use this to log into wagtail and edit
+   pages:
+
+```
+python manage.py createsuperuser
+```
+
+4. (Optional) To start from an existing Wagtail export, run
+   `python manage.py load_cms_data FILENAME`, where FILENAME is the name of one
+   of the Wagtail exports in
+   [fixtures](https://github.com/apache/airavata-django-portal/tree/master/django_airavata/wagtailapps/base/fixtures)
+   directory. For example, you can run
+
+```
+python manage.py load_cms_data default.json
+```
+
+5. Start the Django server and log in at <http://localhost:8000/cms>
+
+```
+python manage.py runserver
+```
+
 ## Importing a Wagtail export
 
 You can import a Wagtail export by running the following command on a newly