23 lines
2.3 KiB
HTML
23 lines
2.3 KiB
HTML
|
{% extends "base.html" %}
|
||
|
|
{% block title %} Development {% endblock %}
|
||
|
|
{% block content %}
|
||
|
|
<h1>Development</h1>
|
||
|
|
<p>
|
||
|
|
I started work on the first version of this personality quiz over a year ago, when I decided to teach myself programming. The original version ran on JavaScript and was rendered and evaluated entirely by the browser. This version runs entirely on the server, and the quiz results are evaluated by the server rather than the client.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
The back-end runs on Python 3.10, using the Flask framework. The web pages are templated using Jinja. The web site is rendered using html and the Bootstrap CSS framework. There have been some elements of the interface enhanced using rudimentary JavaScript, including the jQuery library. Of all of these programming languages, Python has proved to be a far more intuitive language to learn, and generally programming this has been a lot more enjoyable and a lot less frustrating than the earlier iteration that used JavaScript.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
The quiz runs by rendering a form with all of the questions and options on the browser. The browser then submits the responses via a POST request to the server. The server evaluates the responses and renders the results accordingly. There is no information stored on the client.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
All data transacted between the client and the server is stored as a Flask session for the duration that the user is on the web site. If the user closes the site, the session data is deleted and all answers submitted are lost.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
There are, of course, some considerable inefficiencies in the way I have set up the templating. I have written the text for all the various web pages in the templates of the respective pages. Ideally, I would have preferred having a single template for all of the web pages or views, and then have the content served on those pages render dynamically based on the URL query. But that was a level of programming that was gratuitous at this point, as really most of the pages were serving static content anyway so it did not matter just now.
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
In addition, this is the first time I am storing the code of the quiz <a href="" title="Link to the code on my Git Repo">on my Git repo</a>, and having a much more streamlined version control process.
|
||
|
|
</p>
|
||
|
|
{% endblock %}
|