You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to create a new page every quarter for our general meeting. This leads to code bloat on our frontend, as most of the code is the same. The changes that need to be made are the date, time, venue, and the slide deck.
What do we aim for?
Modularize the page to eliminate the need to create new pages every quarter (suggested by @jainsujay02, #670).
One approach could be to parameterize the changes we make every quarter and fetch the required details from a common source such as a sheet that the organizers of the GM could update. This approach would allow for a streamlined method of creating the page and eliminate the need to request relevant information from the required sources.
There could be other ways to implement this idea, and I would encourage open discussion to arrive on the best approach.
The text was updated successfully, but these errors were encountered:
Current State
We need to create a new page every quarter for our general meeting. This leads to code bloat on our frontend, as most of the code is the same. The changes that need to be made are the date, time, venue, and the slide deck.
What do we aim for?
Modularize the page to eliminate the need to create new pages every quarter (suggested by @jainsujay02, #670).
One approach could be to parameterize the changes we make every quarter and fetch the required details from a common source such as a sheet that the organizers of the GM could update. This approach would allow for a streamlined method of creating the page and eliminate the need to request relevant information from the required sources.
There could be other ways to implement this idea, and I would encourage open discussion to arrive on the best approach.
The text was updated successfully, but these errors were encountered: