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

Implement a link to Status Help center on https://status.app/help #21992

Closed
jorge-campo opened this issue Jan 28, 2025 · 6 comments · Fixed by #22177
Closed

Implement a link to Status Help center on https://status.app/help #21992

jorge-campo opened this issue Jan 28, 2025 · 6 comments · Fixed by #22177
Labels
feature feature requests qa-reviewed settings App settings
Milestone

Comments

@jorge-campo
Copy link

Feature Issue

[comment]: # As described in the Status Planning release, the Status Mobile app should include a link to the Status Help support site (https://status.app/help).

User Story

As a user, I want to open the Status Help site from the Status Mobile app so that I can search for the information I need.

Description

[comment]: # Implement a link to the Status Help website at https://status.app/help under the "Help" menu. The label for this link should be "Status Help".
[comment]: # Remove the link to the "Glossary" section. This glossary comes from Status app 1.0 and is no currently maintained by anyone in Status.

Image

Acceptance Criteria

[comment]: # When the user clicks the "Help" option in the Status mobile app, a link to the Status Help website (https://status.app/help) with the "Status Help" text is presented. The user can tap on this link, which opens the Status Help website.
[comment]: # The user doesn't see any link to the Status Glossary.

Notes

[comment]: # Status Help website supports the mobile view.
[comment]: # Status Help documentation content is dynamic and changes several times between releases with new documents and updates to existing documents. For this reason, the Status Help link should open the live https://status.app/help website and not a local copy of the Help website delivered with the binary.

@jorge-campo jorge-campo added the feature feature requests label Jan 28, 2025
@jorge-campo jorge-campo added this to the 2.33.0 milestone Jan 28, 2025
@churik churik added the settings App settings label Feb 4, 2025
@israr002
Copy link
Collaborator

@jorge-campo just wanted to confirm if this is the expected behavior?

status-help.mov

@jorge-campo
Copy link
Author

@jorge-campo just wanted to confirm if this is the expected behavior?

Hi @israr002 - Yes, this is the desired behavior. Thank you!

@israr002
Copy link
Collaborator

@jorge-campo I`m trying to raise a PR, but I'm getting a permission denied error. The documentation doesn't mention the need to create a fork. Do I need to fork the repository for raising the PR?

@jorge-campo
Copy link
Author

jorge-campo commented Feb 17, 2025

@jorge-campo I`m trying to raise a PR, but I'm getting a permission denied error. The documentation doesn't mention the need to create a fork. Do I need to fork the repository for raising the PR?

Hi @israr002 - If you're talking about the status-im\status-website where Status Help exists, it's a private repo, but I guess the web team can give you access if you need it. Why do you need to create a PR? 🤔 (feel free to DM me, @campo4171)

@israr002
Copy link
Collaborator

israr002 commented Feb 17, 2025

@jorge-campo I’m trying to contribute to status/status-mobile for this task as a external contributor, but when I try to push my branch, I get a permission denied error. How can I create a PR for this task? Do I need to fork the repository first? Thanks!

@jorge-campo
Copy link
Author

Got it, @israr002 ! Yes, in that case, you need to fork the repo first. Please let me know if this doesn't work for you. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature feature requests qa-reviewed settings App settings
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants