johnagl / shortlist

Shortlist

Link: https://shortlistt.herokuapp.com/

Description

• Who is it for?

  • Shortlist is for job seekers who want to keep track of their job applications and progress with their job search.

• What does it do?

  • Users have the ability to track the details of all of their job applications without having to use cluttered spread sheets and/or a complicated local file folder system. They will be able to add and update specific job information such as which stage a particular job application is in (Not yet applied, applied, phone screen, on site interview etc). Users also can keep track on interview dates for each job with an in-app calender and manage documents related to their job search.

Prototypes

shortlist's Issues

Scrum 4

These past two weeks I have worked on learning how to integrate meteor with our previous project relying on react and redux and making changes accordingly so actions we make on the front-end persist in the database. I also implemented the counter feature on top of each category and helped redo the css. In the next two weeks I will be focusing on how we have users and the ability to log in and sign up and access their own data. The last two weeks were challenging with making changes and integrating meteor and mongo, I think the hardest was getting started and adding jobs to our collection but then also in the front end and how to fetch the jobs from the server. Our group also decided to refactor our data and make two different collections.

Scrum 5

These past two weeks I worked on adding the login and register feature to the project using Meteor. One major struggle was that I was trying to use meteors built in blaze components which are hard to change. Switching to making my own components for login and register and then making meteor login and register calls was much better. I also started looking into how we might be able to have a document upload feature so that users can store their files. Going forward I am going to try and make document upload work and also add on atlas to the project and look into how we are going to be deploying (research galaxy deployment).

Scrum 2

These past two weeks, I have been working on the login and sign up components. Together as a group we’re going to work on getting actions and redux working so that we can have the functionality where we can click add and be able to listing details and those appear on the dashboard in an individual job card. I will be looking into the login/password storage API that Daniel our speaker today mentioned and see if I can implement that. In the last two weeks, I spend a significant amount of time trying to learn react and redux. I got very confused and stuck with redux and hopefully this time applying it now to the project will help piece things together for me.

Scrum 1

With my group, I worked on creating our project idea Shortlist. I worked on developing the user dashboard interface including the prototype for the “full” view.

One of the major challenges I came across was determining the feasibility of some of our project ideas, given the time constraint and that we have yet to learn most of the technologies we are going to use for the project.

For the upcoming iteration I plan on setting up our project repository’s meteor, react and redux structure as well as creating react components for the job stage categories (wishlist, applied, phone screen etc).

Scrum 3

The last two weeks, I worked on implementing Redux properly, as well as implementing the layout, styling, and functionality of the job cards. A challenge I faced was figuring out how to structure our initState data in a way that would be best suited for use with MongoDB. I also had to overcome issues with default formatting on Reactstrap, which I finally figured out. This week, I am responsible for continuing on the job cards: adding an edit menu to job cards when clicked, colouring by status, updating the UI to a less 1985 ski jacket/Baskin Robbins palette, and integrating company logos on job cards via the external Clearbit API.