-
Notifications
You must be signed in to change notification settings - Fork 5
Missing social media links for landing pages #35
Comments
@MikeMcC399 Thanks for pointing this out. |
Do you plan to provide a PR for this? Else I could do it 🙂 |
You're right, I forgot! Enjoy the weekend! |
What are the thoughts about making this change? I believe that the website is only displayed if the user doesn't have the app installed, so probably it will not be seen often. It would however be more consistent to use the same footer as on the main website. |
FYI: I just opened a CR for that and will bring it in production soon. |
Thank you! So you will deploy the |
I have a feature branch right now for testing it on all (4) ENVs but in the end deployment will be done from the main branch, sure. |
@Ein-Tim Hmm, I think I mixed something up here. Sorry. I have an internal branch for our deployment, but not in this repo. This repo here is only used to be part of a Docker image, which will then be deployed by us... But for now, the latest Image represents only the footer year changes as far as I see, not more... So someone needs to accept here the latest PRs and based on that create a new Docker image. Only then am I able to apply them to the Cluster. |
@genericmueller Right, currently this issue from @MikeMcC399 was not addressed with a PR. Currently the last merged PR is #33 (updating the copyright year). So what needs to be done is:
FYI @dsarkar |
I suggest to look at PR corona-warn-app/cwa-website#2284 from cwa-website and pick the changes which apply here. @brifemu was the author. I wasn't planning to submit a PR myself for this. |
@Ein-Tim / @MikeMcC399 |
@genericmueller We can provide and merge PRs. Concerning the social media in the footer, we will try by tomorrow to have a PR ready. Anything else needs to be done? |
@dsarkar Thank you! Sounds good. We can take over after the new docker image is pushed into our registry (MTR)... |
@genericmueller I did add the footer changes to the |
@svengabr Theoretically, I can also build the image, but it is the responsibility of my colleagues. It must first be checked and approved. The image is built through their build pipeline and is then pushed to the registry. After that, a deployment has to be planned and our environments have to go through to production :) Unfortunately, this is the normal way even with these minor adjustments. However, I will inform the colleagues that the image can be rebuilt and tested. |
I will trigger the normal deployment process |
@svengabr |
Noting the comment from @thomasaugsten in #32 (comment) "Deployment is done" the social media links on the footers of:
are now updated and showing as follows: So, now closing this issue as resolved. |
Where to find the issue
Describe the issue
The footers of the websites:
are no longer aligned to the footer of the website:
The footers of https://e.coronawarn.app/ and https://s.coronawarn.app/ are missing the:
Footer of https://e.coronawarn.app/ and https://s.coronawarn.app/
Footer of https://www.coronawarn.app/
Suggested change
Update the footers of the websites:
to display the same as the footer of the website:
including update to the latest Copyright year.
See in particular PR corona-warn-app/cwa-website#2284 "Add social media icons and community section".
The text was updated successfully, but these errors were encountered: