Refactor JavaScript so that Project Meetings page sources meeting data from vrms_data.json

[roslynwythe]

Dependency

• [x] #6023
• [ ] #6369

Overview

As developers we need to refactor the JavaScript behind the Project Meetings page, so that it retrieves meeting data from the file data/external/vrms_data.json, in order to reduce the latency and improve the reliability of the webpage.

Action Items

• [ ] For reference, view the code in assets/js/right-col-content.js and understand how the event data is retrieved from assets/js/utility/vrms-events.js
• [ ] Refactor the code in assets/js/project-meetings.js to source data from data/external/vrms_data.json, using function(s) in assets/js/utility/vrms-events.js and perform testing to confirm that functionality on the Project Meetings webpage [^1] is unchanged.
• [ ] Note that events from all projects should be displayed, except for events with the project name "test" or "Hack4LA".
• [ ] Open the file assets/js/right-col-content.js and refactor the code to reference the function(s) in assets/js/utility/vrms-events.js and perform testing to confirm that functionality on the Project pages[^2] is unchanged.

Resources/Instructions

[^1]:Project Meetings webpage

[github-actions[bot]]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing: Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels