Flesh out 'join' user flow

This commit splits the user flow when sending in an application to join
the guild into three staged:

1. Intro text
2. HTML form
3. Form submission feedback (aka. "yay it went through")

1 files changed, 9 insertions, 3 deletions

diff --git a/app.py b/app.py
index c64c280..de7a1d3 100644
--- a/app.py
+++ b/app.py
@@ -43,11 +43,15 @@ def callback():
 
     return f'Access token: {token_response.get("access_token")}'
 
[email protected]("/join.html")
[email protected]("/join_intro.html")
+def join_intro():
+    return template("join_intro")
+
[email protected]("/join_form.html")
 def join_form():
-    return template("join")
+    return template("join_form")
 
[email protected]("/join.html", method="POST")
[email protected]("/join_form.html", method="POST")
 def join_submission(db):
     name = request.forms.get("name")
     preferred_role = request.forms.get("preferredRole")
@@ -64,6 +68,8 @@ def join_submission(db):
 
     db.execute(f"INSERT INTO applications(name, role, motivation) VALUES ({name}, {preferred_role}, {motivation})")
 
+    return template("join_success")
+
 @app.route("/<type:re:styles|images>/<filename>")
 def server_static(type, filename):
     return static_file(filename, root=f"./static/{type}/")