Separate "static" configuration and "dynamic" configuration

[tossy310]

Currently, build time configuration is loaded from siteconfig.ts and some contest metadata is loaded from contest feed.

What we recently want are:

• Front-end's build time configuration (such as firebase data, Add OGP title and description #71, Make og:image configurable in siteconfig #14, etc)
• Dynamic contest configuration (such as current contest feed, site features)

Thus, proposal is:

• Introduce build time configurable settings.
• Move some siteconfig to build-time configuration.
• Move remaining siteconfig to contest feed
• Remove siteconfig.ts.

[nya3jp]

What are differences you have in mind between "site configs" and "build-time confiurable settings"?

BTW I agree that it's confusing to have build-time settings in src/siteconfig.ts, rather than some setting files outside src/.

[tossy310]

What are differences you have in mind between "site configs" and "build-time configurable settings"?

siteconfig.ts is still dynamically loaded javascript. IIUC, it's not appropriate to configure og:image and friends. They should be put directly in a html.

Note that another motivation of this issue is that site features (such as photo, whether to show first AC, etc) are more like business requirements and can change frequently. I don't want to rebuild and deploy frontend only for these config changes.

[tossy310]

LLM generated prototype is https://github.com/icpcsec/livesite/compare/refactor-configurations

[nya3jp]

Thanks, it makes perfect sense.