-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Is your feature request related to a problem? Please describe.
Yes. On long pages, users have to manually scroll all the way back to the top, which can be inconvenient—especially when navigating dense content.
Describe the solution you'd like
Implement a floating “Back to Top” button that:
Appears when the user scrolls down past a certain point (e.g., 100px).
Smoothly scrolls the page to the top when clicked.
Adapts to the light/dark theme mode dynamically.
Is mobile and desktop responsive.
Describe alternatives you've considered
Adding a sticky header with a “Top” link.
Relying on keyboard shortcuts like Home key.
Use Case
Describe the specific use case or scenario where this feature would be beneficial:
- Who would use this feature?
All users, especially content creators or editors navigating long blog posts or logs. - How would it improve the OptiBlogAi experience?
It improves UX by saving time and reducing frustration, allowing seamless navigation and access to header controls. - What problem does it solve?
Eliminates the need for excessive scrolling and enhances accessibility and comfort across devices.
Feature Category
Please select the category that best describes your feature request:
- Content Generation
- SEO Optimization
- Scraping & Research
- Quality Assessment
- API & Integration
- User Interface
- Performance
- Documentation
- Other: [specify]
Implementation Suggestions
If you have ideas about how this could be implemented:
- Technical approach
Use a scroll event listener in JS/TS to toggle visibility.
Add a button styled with Tailwind or CSS modules.
Smooth scroll behavior using window.scrollTo({ top: 0, behavior: 'smooth' }). - Potential challenges
Ensuring performance efficiency (avoiding unnecessary re-renders or scroll events).
Theming alignment (auto-adapting in light/dark mode). - Dependencies or requirements
TailwindCSS or UI library in use
Optional: FontAwesome or Lucide icon for arrow - Compatibility considerations
Works well with the existing FastAPI + LangGraph stack as this is frontend-side only.
Priority
How important is this feature to you?
- Critical - Blocking my use of OptiBlogAi
- High - Would significantly improve my workflow
- Medium - Nice to have
- Low - Minor improvement
Additional context
Related Issues
Link any related issues or discussions:
None
Checklist
- I have searched for existing feature requests
- I have provided clear use cases and benefits
- I have considered implementation challenges
- This feature aligns with OptiBlogAi's goals and scope