The beta repo was a temporary solution to get the new company pages out.
It would be nice to merge the beta repo into the klimatkollen repo. Probably best way to do this is to merge the repos when we have re-implemented the website in the beta repo, at which point we can remove old content in the klimatkollen repo, and then merge the beta repo into a subdirectory of the main klimatkollen repo.
Description
The beta repo was a temporary solution to get the new company pages out.
It would be nice to merge the beta repo into the klimatkollen repo. Probably best way to do this is to merge the repos when we have re-implemented the website in the beta repo, at which point we can remove old content in the klimatkollen repo, and then merge the beta repo into a subdirectory of the main klimatkollen repo.
Some ideas for merging git repositories while preserving the history: https://stackoverflow.com/questions/13040958/merge-two-git-repositories-without-breaking-file-history
Motivation
Simplify development and make it easier to contribute to the project.
Definition of Done
When the new website has replaced the current one, and it lives in the klimatkollen repo rather than the beta repo.
When have updated the deployment config and made sure that it works - replacing vercel with the dedicated hosting.
When should it be done?
This is likely an alternative solution to #491
Contact person
@Greenheart