Context

I have finished this ticket only by making the backend Strapi type for the project requirements. There is no frontend implementation yet, because we want to implement the front end through the Project Details type coming up in a future ticket.
This will remove the need for making redundant code, as the whole Project Details Strapi type is necessary to get each section of the Project Details page.

This Project Requirements Type will be used in the Project Details type, then from there, we can code up the HTML for the Requirements section of the Project Details. This change will allow us to display one or multiple project requirements associated with each project in the project details page. Flexibility is important for future WDCC Execs who will be changing the content of the website, so I believe this will be a vital change for future-proofing. Overall, this allows site visitors to clearly see the problems and intricacies involved with making WDCC projects.

What Changed?

Just added a project requirement type via Strapi, which has three parts:

• Title: A description of the requirement in a few words
• Description: Detailed list or paragraph of the sub-requirements
• Image: Optional image or video showcasing the requirement in action

How To Review

Just check that you are able to add project requirements via Strapi. Make sure to add a title and description.

Testing

N/A

Notes

Would love to be merged, so that we can start using this type in actually displaying the project details.