I have done some reading about Scrum and Extreme Programming and have decided to incorporate some of that into completing my projects. That means the previous post I wrote that detailed where I am planning to go with the Lifelong Learning site has changed. Instead of the previous plan, I will organize my work into sprints and write a short blog post at the start of each sprint as well as at the end of each sprint (a sprint is a short timeframe to accomplish specified goals). In a future blog post, I will be writing about what else I am going to incorporate into my development workflow and why, but here I will be describing the work I will be doing for my first sprint.
I want to have a complete set of tests that will cover all possible pages on the website and make sure they are loading correctly. There are many reasons for this, and the main one is to save time. When I have no tests created, I will try everything manually before I upload it to the server, and that is very time-consuming. While I find writing tests very time consuming themselves, it is a plus to be able to type one command into the terminal and have the entire website check through thoroughly.
At the moment, many admin views have to be typed manually into the search bar to be navigated to. For myself, that is fine, but I am trying to convince some friends of mine also to use the site, and they may not want to deal with trying to remember all the different possible pages. The admin page will have all the possible pages to edit, delete, and add to the database in an easily accessible page. When logged in, the admin page will show up on the navbar of the website.
There is currently no way to edit a worksheet when one has already been added to the database. If you add a worksheet to the database and want to change its category or video link, you have to delete the worksheet and re-enter it. That is not an excellent way of dealing with things, so I am planning to have a new view that will allow the user to edit an existing worksheet. To accomplish this, I am going to research more of the options available in Flask to deal with Files and map out the logic needed carefully and then code it.
At the moment, my “SECRET_KEY”, and database login are stored in plain text in my code, because that is the case I cannot safely share the code publicly. I plan to eliminate these variables from the code and move them to environment variables that have to be set on the machine or server running the website. While it is slightly more inconvenient to remove the secrets from the code, it is better to share the code. I may write a blog post documenting how I do this because it is new to me, and maybe others are also interested.
I am giving myself till next Friday (June 5, 2020) to complete these goals. During that time I will be doing some content creation for the site so please keep tabs on https://lifelonglearning.rocks to see that content and add yourself to the email list on that site if you want.
Any questions or comments can be sent to kodyrogers21@gmail.com.
Thanks for reading!