Is your feature request related to a problem? Please describe.
Currently, Next Forge uses the default Clerk authentication page, which includes Clerk branding and watermark. This might not align with projects that require a fully customized user experience or branding. Additionally, using the default page limits design flexibility and user engagement customization.
Describe the solution you'd like
I propose replacing the default Clerk authentication page with a fully custom-built authentication form. The custom form will:
- Eliminate Clerk branding and watermark for a cleaner, more professional look.
- Provide full design flexibility to match the branding of the application.
- Retain Clerk as the authentication provider in the backend while customizing the frontend for better UX.
Describe alternatives you've considered
N/A
Additional context
I believe this feature will greatly enhance Next Forge's appeal to developers and organizations that prioritize a fully branded experience. I am happy to work on implementing this feature if approved.
Is your feature request related to a problem? Please describe.
Currently, Next Forge uses the default Clerk authentication page, which includes Clerk branding and watermark. This might not align with projects that require a fully customized user experience or branding. Additionally, using the default page limits design flexibility and user engagement customization.
Describe the solution you'd like
I propose replacing the default Clerk authentication page with a fully custom-built authentication form. The custom form will:
Describe alternatives you've considered
N/A
Additional context
I believe this feature will greatly enhance Next Forge's appeal to developers and organizations that prioritize a fully branded experience. I am happy to work on implementing this feature if approved.