some pathetic template ideas

README.md

@@ -53,6 +53,7 @@ To-do
 
 **First orders of business**
 
+* how do you make coreqs work? right now it assumes that a coreq has to come first, but that's obviously not how they work
 * The views need a lot of work
 * The templates need a lot of work
 * The student models needs to support the Django User Model

advisor/templates/index.html

 {% extends 'layouts/base.html' %}
 
 {% block title %}
-
+GMU SRCT Advisor
 {% endblock %}
 
 {% block content %}
 
+<h2>Welcome to Advisor, a project of GMU SRCT.</h2></p>
+
+<p><h3>This site automates academic advising.* Just select the classes you've already taken, and follow the instructions to start visualizing the path to completing your degree. Sign in with your GMU student username and password at the top to save your progress or compare multiple trajectories.</h3><p>
+
+<p><h6>Not intended as a replacement for formal academic advising.</h6></p>
+
+<p>Dropdown menus for Courses. Hopefully some fill-in-the-blanksing.</p>
+
+<p>Select your degree(s).</p>
+
+<p>Select your minor(s).</p>
+
+<p>Are you in the Honors College?</p>
+
 {% endblock %}

advisor/trajectories/views.py

@@ -50,6 +50,13 @@ def index(request):
     },
     )
 
+def makeTrajectory(request):
+
+    return render_to_repsonse('maketrajectory.html', {
+    
+    },
+    )
+
 # just displays a page for the course
 def course(request, slug):