-
Notifications
You must be signed in to change notification settings - Fork 163
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃摎 Documentation: Incorrect Hyperlink Destination in Storage Documentation #326
Closed
2 tasks done
Labels
documentation
Improvements or additions to documentation
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃挱 Description
Description
In the Documentation of Storage, there is an issue with the hyperlink labeled "Learn about file input."
Although the link text indicates that it should point to "https://appwrite.io/docs/storage#file-input," it actually redirects to "https://appwrite.io/docs/storage" without the expected "#file-input" anchor identifier.
The problem is that the "#file-input" section does not exist in the destination page, which leads to a broken link and could potentially confuse users looking for information about file input in the Storage documentation.
This issue should be addressed by either fixing the link to correctly point to the intended section with the "#file-input" anchor or by ensuring that the section is added to the Storage documentation to match the link's target.
Steps to reproduce the issue:
Visit the page with the hyperlink: Storage Documentation.
Click on the "Learn about file input" link.
Expected result:
The link should navigate to the "file-input" section within the Storage documentation.
Actual result:
The link redirects to the general Storage documentation page without the "#file-input" section.
This issue impacts the user experience and should be resolved to ensure accurate and consistent navigation within the documentation.
-> And I want to work on this
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: