Feature Request: Add “About StablePay” Page with Navbar Integration

[Peehu1308]

Description
Currently, the application does not have a dedicated About page explaining what StablePay is, its purpose, and how it is used. This makes it difficult for new users and contributors to quickly understand the project.
This issue proposes adding a new About StablePay page that clearly explains the platform using information from the official StablePay repository:
https://github.com/DjedAlliance/StablePay
The page will be accessible via a new “About” item added to the navbar.

Proposed Solution
Add a new About page describing:
What StablePay is
Its core use cases and benefits
High-level overview of how it works
Add a new About option in the navbar.
Configure routing so clicking About navigates to the About page.
Use content derived from the official StablePay repository to ensure accuracy.
Ensure the page is fully responsive across devices.
Maintain consistency with the existing UI design and theme.

Expected Outcome
Users can easily learn about StablePay directly from the application.
Improved onboarding experience for new users and contributors.
Better project clarity and documentation through the UI.

Scope of Work
Frontend UI implementation of the About page
Navbar update and route configuration
Responsive layout for mobile, tablet, and desktop
Theme alignment with existing design system

Impact
Enhances user understanding of StablePay
Improves project professionalism and accessibility

[vrushabhxpawar]

Hi
I went through the StablePay repository and the issue description.

My understanding is that this issue aims to improve onboarding by introducing a
dedicated About page that explains what StablePay is, its core use cases, and a
high-level overview of how it works, while staying aligned with the existing UI
and routing structure.

My proposed approach:

• Draft content derived from the official StablePay repository
• Add an About route and corresponding navbar item following current patterns
• Ensure responsiveness and theme consistency across breakpoints

Before starting implementation, I wanted to confirm:

• Is there a preferred structure or content outline for the About page?
• Should the content live purely in the UI, or be reusable (e.g., via markdown or constants)?

If this aligns with the maintainers’ expectations, I’ll start with a small PR
covering routing and navbar changes and iterate based on feedback.
Thanks!