Boilerplate

[kvaes]

The following needs to be done

Foundation

1. Setup a C# based Azure Function project in the backend folder
2. Setup a VueJS based project in the frontend folder
3. Ensure the CI flow for both is set-up and working
4. The build / CI process of frontend and backend needs to provide a container as output
5. Set up a dependabot files in the .github repo that scans daily and aligns with the package manager for both the backend and frontend
6. Setup a security file in the .github folder that serves as a solid base to start out on a security policy for both the backend and frontend
7. Provide basic error handling for frontend forms and for backend APIs
8. Ensure to include documentation to describe the local development setup
9. Extend the documentation to include how to run both projects from GitHub Codespaces in and end-to-end approach where they connect to eachother and you can have a full test executed from within the Codespaces environment
10. Ensure the data contract folder is populated with the data models to ensure consistency between both frontend and backend
11. Populate the docs folder with the documentation about both projects
12. The azure functions code for the backend needs to have CORS handling directly from the code and not rely for this on the azure functions azure functions server for this
13. The azure function local / codespaces development environment needs to use the Azure Functions Core Tools and not the dotnet commands

Functional - Backend

For the backend, we need APIs that will be able to do the following

1. Add an event
2. Update an event
3. Delete an event
4. Retrieve information on a specific event
5. Retrieve events filtered on data & location
6. For each event, we'll need the name, location, date & start time.

Functional - Frontend

For the front-end, we need an overview page that will provide the following

• A list of events based on the filter criteria
• The ability to go to the details of each of the events
• Visitors need to be able to subscribe to the event
• Visitors need to provide the following information upon registraton ; name, email, pronouns, opt-in for further communication