React Portfolio
Implementing "design first", so I didn't run into the coding of the project. I started off with designing most of the details of the site. Understanding that the design would change and have to adapt to limitations and pitfalls of the tech stack during development.
As was a personal project I didn't put huge amounts of work into the Figma design, only enough to have a good idea of what I was aiming for. As I was not presenting this design to a wider team I didn't need to make it look "neat" or professional as I would not need to explain this design to someone else to take forward. This enabled me to get a MVP off the ground very quickly. As you can see, the site has changed loads since this initial design. With many of the features I have yet to add in still on the design. There are also many parts of this design that were modified due to requests and feedback on my Portfolio site. One such change was adding a Github link to see the source code of my project on the site to help people find it and critique it.
This project has four main folders:
A components folder, containing all the folders and .tsx files related to components on each of the pages of the site.
A pages folder, containing the .tsx files related to each of the page roots and accessible pages, utilising dynamic rooting. This also included an api folder which included the .js file to access firebase.
A public folder, initially used to hold the images and pdf files for the site.
And a styles folder, containing all the CSS and SCSS files for the site.
This project used Github and Kanban boards to enforce a from of agile development. This enabled me to show off not just my awareness of this system, but to show off what I think is a strong and suitable use of the method. This enabled me to add Complications and Todo tickets and to keep track on what I had developed and what was next to add/develop. Using Github enabled me to work on parts of the project independently on separate branches. It also enabled integration with Vercel to deploy the project using a production branch.
Redundant
June 5th 2023 - December 2023