Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use staged website urls #7941

Open
3 tasks
rezbyte opened this issue Nov 14, 2024 · 0 comments · May be fixed by #7942
Open
3 tasks

Use staged website urls #7941

rezbyte opened this issue Nov 14, 2024 · 0 comments · May be fixed by #7942
Labels
improvement nice-to-haves that are not impeding usage of any features

Comments

@rezbyte
Copy link
Contributor

rezbyte commented Nov 14, 2024

The InfoLinks and FAQ entries should link to the appropriate stage of the website. I.e. the test app shows links to the test website.
See the 'Later' section in #7336.

Test notes

Test on local, test, prod (mobile, web, desktop):

  • All links to FAQ entries in the app use the correct staging level, e.g. links from the settings to more information.
  • In the FAQ search in the app the images in the FAQ entries are loaded from the correct website staging environment.
  • Building with the "host" argument uses the prod domain links.
@rezbyte rezbyte added the improvement nice-to-haves that are not impeding usage of any features label Nov 14, 2024
@rezbyte rezbyte linked a pull request Nov 14, 2024 that will close this issue
armhub added a commit that referenced this issue Dec 20, 2024
Also replaces the website URL in faq entries according to client stage

Co-authored-by: Jat
Co-authored-by: armhub <[email protected]>
armhub added a commit that referenced this issue Dec 20, 2024
Also replaces the website URL in faq entries according to client stage

Co-authored-by: Jat
Co-authored-by: armhub <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement nice-to-haves that are not impeding usage of any features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant