Open ojeytonwilliams opened 1 year ago
Thinking about it, since there's a fair bit of site configuration, it might be best to create a dashboard page. It's more effort, but I think it's probably worth it given how many environment variables we would end up with. Also, having to redeploy the site to fix a typo in the description would be frustrating.
People who self-host chapter will need a way to provide their own versions of these.
As @allella mentioned https://github.com/freeCodeCamp/chapter/issues/2373#issuecomment-1438686164 the simplest approach would be to leave them as links, but allow them to be customised.
There are two main tasks
While the best UX is probably to provide a GUI to customise the variables (and persist them in the database) the simplest approach (sufficient for the MVP) would be to store them in environment variables.