README

File Structure

.
├── back-end
│   ├── app.js
│   ├── controllers
│   │   └── authController.js
│   ├── models
│   │   └── UserModel.js
│   ├── package.json
│   ├── package-lock.json
│   ├── README.md
│   ├── routes
│   │   └── authHandling.js
│   ├── service
│   │   ├── database
│   │   │   └── db.js
│   │   └── security
│   │       └── authentication.js
│   └── utils
│       └── helper.js
└── web-front-end
    ├── index.html
    ├── js
    │   └── scripts.js
    ├── pages
    │   ├── profile.html
    │   └── register.html
    ├── README.md
    └── styles
        └── styles.css

13 directories, 16 files

The directory structure for the code of Quest 1 follows this scheme. Each directory has a README.md (some not shown in the tree) explaining the purpose and the rationale for each code.

Important

It is recommended to read through each README.md file as they contain information that you might need for further understanding of the campaign.

Where to read first?

There is no given order to read through each directory. However, we do recommend this flowchart to know how interconnected they are.

flowchart RL
subgraph g1[back-end]
service --> database
service --> security
security <-.-> controllers
utils <--> database --> models
controllers .-> routes
end
subgraph f1[web-front-end]
index.html --> pages
pages <-.-> js
index.html <-.-> js
end
routes <--> js

Loading

---