Author: jaeyoonc

This week I had several revelations regarding the flow of the project related to scheduling and the work itself.

1. Progress on the webapp is slower than I had anticipated. While we have the basics working for OAuth and various pages, I still haven’t integrated as much of the dynamic AJAX as I would’ve liked by this stage. I’m still struggling with the details of social-django as well, but I’m finding support documents as issues arise.
2. I’m still trying to figure out how to use Bootstrap and perhaps ease the burden of CSS. I’m cognizant that this isn’t a majority component of the capstone, but given my inexperience with CSS I still would rather look into this.
3. I’m realizing in our Gantt chart that we need to account for days when we would have less time to advance the project than we had planned. For example, days that the University gives us off like most recently spring break and the upcoming Carnival; or preparing documents and presentations for the Capstone. While we haven’t fully completed our revamp of the Gantt chart, we definitely need to shift some items and be realistic about our productive abilities on those days.

In the coming week, I hope to have a working version of the wireframes I presented earlier in the semester, perhaps not with live user data but with a set of dummy data.

This week I realized that I let the tail wag the dog, and went back to do the foundational work for the website first.

tl;dr wireframing, Gantt chart, website mods

Harry showed me an interesting website for wireframing called Figma, which automatically generates a CSS given a website style and template. While I’m extremely tempted to look into this further, it’d require a great time commitment and learning curve that I’m not sure would be the best use of my time for now, but I’m glad to know that it’s there if I ever decide to come back to it (perhaps as part of a UI stretch goal). For now, I’m content with the wireframe I made using good-old (digital) pen and (virtual) paper. Alternatively, Bootstrap seems more widely used and with a smaller learning curve, so that could be another option as well.

I also spent a few hours this week creating a copy of this Gantt chart that uses Google Drive, reorganizing the categories and adding more subtasks as I went. Already some tasks are cancelled based on our decision to move forward with cloud computing, and new ones introduced in their stead. So, as a group we also collectively updated tasks, and subdivided and assigned them. For my personal progress, I took an extra day for the wireframing, but otherwise I seem to be on track. 

More minor housekeeping: I got the working on the blog site header, so now our weekly reports correctly display when clicked.

In keeping with my promise from last week, I’ve added (marginally) more commits to the shared github, with the rudimentary framework for the HTML mockup. We also split the task of creating an MVP website into multiple parts, and in keeping with that Harry and I will be working on the website development in parallel. 

Next week I hope to be finished with the HTML mockup by Wednesday, and that way Harry and I can begin concurrently working on the site for an MVP.

This week I’ve been working on getting a rudimentary webapp working with Django. So far the work’s been on my local machine, though I’m realizing now that I should probably push this all to a github repo sometime soon, for no other reason than accountability (as per the Canvas guidelines).

Given that my work is mostly independent of the CV component thus far, I’m hoping timing won’t be too much of a concern. By this week I hope to have a basic UI capable of presenting JSON data and manually interacting with said data (insert, delete, etc.)