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

Relocate the Edit Button #915

Closed
sedationh opened this issue Oct 19, 2024 · 1 comment
Closed

Relocate the Edit Button #915

sedationh opened this issue Oct 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@sedationh
Copy link
Contributor

sedationh commented Oct 19, 2024

Is this a feature for the backend or frontend?

Frontend

What would you like?

Improve Accessibility of Edit Button for Long Content Pages

Issue:
The current placement of the edit button at the bottom of the page causes significant usability problems, especially for pages with long content.

Current Behavior:
When viewing a page with extensive content, users must scroll to the very bottom to access the edit button. This process is time-consuming and frustrating, especially when frequent edits are necessary.
image

Steps to Reproduce:

  1. Navigate to a page with long content, similar to the example provided
  2. Attempt to locate the edit button
  3. Observe that extensive scrolling is required to reach the button at the bottom of the page

Expected Behavior:
Users should be able to easily access the edit function without the need for extensive scrolling, regardless of the content length.
image

Impact:
This issue significantly hampers user experience and efficiency, particularly for content creators and editors who frequently need to make changes.

Proposed Solution:
Implement a more accessible placement for the edit button. Some potential solutions could include:

  1. A floating button that remains visible while scrolling
  2. Placing the edit button at the top of the page
  3. Adding an edit button to a persistent header or sidebar

Additional Considerations:

  • The solution should work well for both desktop and mobile interfaces
  • Accessibility standards should be maintained in any new implementation

Next Steps:
I would like to discuss the expected outcome and potential solutions . I'm willing to submit a PR once we agree on the best approach. Let's collaborate to find the most effective solution that aligns with our project's design and usability standards.

Please share your thoughts and preferences regarding the proposed solutions or any other ideas you may have. I'm looking forward to contributing to the improvement of our user experience.

Why is this needed?

No response

Other information

No response

@meltyshev
Copy link
Member

Hi!

You're right, the buttons at the bottom aren't very convenient in the example described. It might be worth adding a pencil icon on hover (similar to how it works with attachments), and I also like the idea of a floating button that stays visible while scrolling (probably achievable with position: sticky). It's a bit hard to say which approach will work best without testing, but we can start by ensuring the buttons are accessible.

Thanks for being willing to make a PR, we’d be happy to accept it 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants