Class 14 HYF Project

0. Introduction
1. Workflow / HYF to-do
2. Installation instructions/User manual

• DO NOT TOUCH
• ANOMALIES

3. Technical details

• Notes
• Structure

4. Version control
5. Project History.
6. Future Development

This README accompanies the Class 14 Project, which was an assignment to update the existing HYF site to automate more, and reduce mistakes in having to make manual entries.

For a TL;DR guide to how to install/initialise and use the website, please go straight to section 2.

This has been an application written in Vue JS ("Vue"), which is a similar language to React. The reason why Vue has been chosen is because of its simplicity for smaller applications such as this.

In Vue, HTML/CSS can be combined. The CSS components are a unique type called scss. This will be expanded upon in greater detail in section 3.

NB: "Backend"/"System" means we have written various functions to enable the system to work automatically given specific input. 😃

NB: Before beginning, it is necessary to initialise the application.

The notes below are based on the steps as enumerated in section 1 above.

DO NOT TOUCH: Generally speaking the backend user of the site does not need to touch any of the functions or code, other than possibly to change the dates in content > en > apply > apply-dates.md.

All the changes, after initialisation, should be handled on the Google sheets themselves. Particular attention is called to steps 1.G. and 1.J., where backend user's manual input is required.

NB: This is based on the steps as enumerated in section 2 above.

                        HOME ------ DONATE
                         |
        -------------------------------------------------------------
        |         |         |         |         |         |         |
      APPLY     TEACH    SUPPORT   CHAPTERS   ABOUT    CONTACT  WOMEN CODING TEASER
                                      |
                                       Map chapters
                                      |
                                      Chapter pages
                                      - Amsterdam
                                      - Brussels 
                                      - Copenhagen
                                      - Malmö 

This README was written by Jason Tan and is correct as of 2 September 2018.

This website was created by Maartje Kruijt and Mauro Mandracchia and was last worked on 2 September 2018 by Class 14:

• A Team (Fadi, Emad, Wael & Hadeel)
• Big Voice Big Team (Sarbast, Sobhi, Rashad & Murat)
• Return 0 (Aya, Isaac & Jason)

In week 1 of the project we had something called an event storm, an example of which may be found here.

The general idea is that the task giver ("TG") talks to a group of developers/engineers ("devs"), telling them what his/her issues are. TG says what the existing processes are, what the pain points are, and what TG wants devs to do.

Each individual dev writes out, on sticky notes, what he/she thinks are:-

1. Every step of the process as it is at the present;
2. Every step of what the process should also be;
3. What the potential issues are.

These go onto a wall, or board, and everyone groups the sticky notes together, re-ordering them as is necessary. Notes bearing the same concepts can thus be dropped, simplifying the wall.

Through this process (called "aggregation"), eventually a common thread is found, and that becomes the workflow which the devs will work on.

In week 2 of the project we finalised the user story, a summary of which is as follows.

As an Admin, I would expect to:-

1. Create new Google sheet as a template.
2. Set a deadline for the registration process.
3. Recieve an auto reply email.
4. Send an email to the candidate asking him/her for his/her CV, and motivation letter.
5. Recieve an email which contains the said documents from the applicant.
6. Store the candidates' data on the Google sheet.
7. Score to each candidate’s CV/motivation letter.
8. Sort the candidates by whether or not they will proceed to the next round based on their CV/motivation letter, with YES or NO.

• In the case of candidates who receive a "NO" answer, I would expect a rejection email to be sent to them.

9. Send an email with two technical assignments to the applicants. As at the present time, it is the Khan Academy link and the Codepen assignment.
10. Set a deadline for the technical assignment.
11. Receive the technical assignment.
12. Score the technical assignment.
13. Combine the scores of the CV/motivation letter with those of the the technical assignment (codepen link and Khan Academy screenshot).
14. Put the selected candidates in a call list.
15. Schedule a 'phone call with the selected candidates.
16. Send the selected candidates a confirmation email for the scheduled 'phone call.
17. Make some notes based on the call.
18. Merge the notes with the previous data.
19. Make a judgment on the notes and the scores.
20. Sort the candidates in categories (YES, NO, MAYBE).

• Send a rejection email to the unsuccessful candidates.
• Send an email to the successful candidates.

23. Put the candidates who was listed as a MAYBE in a waiting list.
24. Choose the candidate(s) with the best scores from the waiting list in a case that the new class is not full.
25. Send an email to all the successful candidates, providing information about the next class.
26. Create a new class.

Have more fun whilst working on this!