You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Get Started" button in the navbar is currently not working when clicked. This can confuse users as they expect it to lead somewhere meaningful.
πΉ Identified Issues
β No redirection or functionality assigned to the button.
β Unclear purposeβshould it lead to sign-up, documentation, or a landing page?
β Wasted space in the navbar if it remains non-functional.
β Possible Solutions
πΉ Option 1: Remove the "Get Started" button if it doesnβt have a defined purpose yet.
πΉ Option 2: Redirect it to a sign-up page, allowing users to join the platform.
πΉ Option 3: Link it to a documentation or onboarding page, guiding new users on how to contribute.
πΉ Option 4: Open a modal/pop-up explaining how to get started with HelpOps-Hub.
π‘ Why This Matters?
β Eliminates confusion & improves usability.
β Ensures every button in the navbar has a purpose.
β Enhances user engagement & platform onboarding.
π Letβs decide the best approach and fix this! ππ₯
The text was updated successfully, but these errors were encountered:
π Description
The "Get Started" button in the navbar is currently not working when clicked. This can confuse users as they expect it to lead somewhere meaningful.
πΉ Identified Issues
β Possible Solutions
πΉ Option 1: Remove the "Get Started" button if it doesnβt have a defined purpose yet.
πΉ Option 2: Redirect it to a sign-up page, allowing users to join the platform.
πΉ Option 3: Link it to a documentation or onboarding page, guiding new users on how to contribute.
πΉ Option 4: Open a modal/pop-up explaining how to get started with HelpOps-Hub.
π‘ Why This Matters?
β Eliminates confusion & improves usability.
β Ensures every button in the navbar has a purpose.
β Enhances user engagement & platform onboarding.
π Letβs decide the best approach and fix this! ππ₯
The text was updated successfully, but these errors were encountered: