Add GitHub Pages/Research Deployment Roadmap

[ggondela1419]

Description

This PR adds a roadmap document for deploying our React + Vite frontend to GitHub Pages. I did some research on what is necessary to successfully deploy our dashboard to the oss-slu.github.io domain without messing up routing, environment variables, or our data flow.

The markdown file covers:

• How GitHub Pages integrates with a Vite-based React app
• The modifications needed in vite.config.js, particularly the base property
• Ways to avoid 404 errors with React Router, which is a common SPA routing issue
• Various methods for handling test_data.json
• How backend workflows can update data on the hosted site

The goal was to provide a clear and organized reference for our Capstone deployment, giving our team a step-by-step guide to follow. There are no external dependencies for this update since it is only documentation.

Fixes #125

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

This is only a documentation change. I checked that:

• The markdown displays properly in the GitHub preview

• The document meets all the requirements mentioned in Issue Github Pages Research #125

• Every section is clearly defined in this file

• Test A - N/A

• Test B - N/A

Test Configuration:

• Language Version: N/A
• Webpage (if applicable): N/A

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshot of Output

[hcaballero2]

Gret work!