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

[roslynwythe]

Overview

We need to refactor the JavaScript that generates the list of meetings on the Events 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 Events page. For testing purposes, a new page events-check will be created that will maintain the behavior of the current events page.

Details

The project pages currently sources meeting data from data/external/vrms_data.json and so elements of that code can be refactored so that functions can be called from the Events page as well.

Action Items

• Copy events.html then rename the copy to events-check.html and change the permalink to /events-check
• Copy events.js then rename the copy events-check.js and update events-check.html to reference the renamed file
• Copy _includes/events-page/right-col-content.html then rename the copy to _includes/events-page/right-col-content-check.html and update events-check.html to reference the renamed file
• Copy assets/js/right-col-content.js then rename the copy assets/js/right-col-content-check.js and modify _includes/events-page/right-col-content-check.html to reference the renamed file
• Confirm that the appearance and meeting data on /events-check are identical to /events
• Open the file assets/js/project.js in your IDE and understand the code used to display project meetings. If there is code that can be shared between the project and events pages, move those elements to a new file assets/js/utility/vrms-events.js.
• If code was moved to assets/js/utility/vrms-events.js, refactor the code in assets/js/project.js to reference function(s) in the new file, and perform testing to confirm that functionality on the Project page¹ is unchanged.
• Refactor the code in assets/js/right-col-content.js and _includes/events-page/right-col-content.html to reference the function(s) in assets/js/utility/vrms-events.js and perform testing to confirm that functionality on the Event page² is unchanged.

Resources/Instructions

Merge Team

• Release dependency on Refactor JavaScript so that Project Meetings page sources meeting data from vrms_data.json #6059, move that issue to New Issue Approval and apply "ready for dev lead" label

Footnotes

1. Project page - sample ↩

2. Events webpage ↩

[github-actions]

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

[pravintargaryen]

@roslynwythe assign this to me