-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat(auth): implement initial sign up UI components (draft) #287
Draft
Homvi
wants to merge
44
commits into
dev
Choose a base branch
from
feature/signup-ui
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Updated `<main>` element in `layout.tsx` to use `relative` positioning. This allows child elements to use `position: absolute` for better layout flexibility. Removed unnecessary whitespace inside the child container.
Created `WelcomeChingu` component for the onboarding process. Includes an illustration, a welcome message, and a "Begin" button to start onboarding.
Added `OnboardingContainer` component to manage the onboarding steps. Includes a stepper, navigation buttons, and step-specific content.
…gContainer - Updated step names for better clarity - Added padding to the first name and last name input section - Added padding to the "What features are you most excited about?" section - Adjusted layout and removed unnecessary flex container for "How did you hear about us" - Added padding to the "If you are on LinkedIn, what is your profile URL?" section
Replaced the static UI in step 3 of the onboarding process with the `WhatFeatures` component to improve modularity and maintainability.
Implemented the `WhatFeatures` component to allow users to select up to three features they are most excited about. If the limit is reached, unchecked options are disabled dynamically.
- Replaced "Data Analytics" with "Support" and updated description - Replaced "Custom Integration" with "Challenge" and updated description - Replaced "Team Collaboration" with "Specific Study Groups" and updated description - Replaced "Solidarity" with "Teamwork" and updated description - Replaced "Data Analytics" with "Accountability" and updated description with "Having an "Accountability Buddy" to help me stay motivated" - Replaced "Custom Integration" with "Workshops" and updated description - Replaced "Team Collaboration" with "Pair Programming" and updated description
…nUrl" - Imported and added "HowDidYouHear" component for step 5 - Imported and added "LinkedInUrl" component for step 7 - Replaced static text for "How did you hear about us" with the "HowDidYouHear" component - Replaced static text for LinkedIn URL prompt with the "LinkedInUrl" component
- Added a new "LinkedInUrl" component to prompt users for their LinkedIn profile URL - Included optional text and styling for the component
- Added a new "HowDidYouHear" component to prompt users for how they heard about the service - Included two columns with radio options for various sources (dev.to, FreeCodeCamp, LinkedIn, etc.) - Managed selected option state and event handling for radio buttons
…p` hook - Removed `useState` for step management in `OnboardingContainer` - Integrated `useOnboardingStep` to handle step navigation centrally - Simplified `goToStep`, `handleNext`, and `handleBack` by delegating logic to the hook
- Created `useOnboardingStep` to manage step state and navigation logic - Provides `currentStep`, `goToStep`, `handleNext`, and `handleBack` for reusable step control
…gStepper` - Removed inline stepper status logic and simplified step navigation - Integrated new `OnboardingStepper` component to handle step rendering - Cleaned up code related to stepper condition and status management
- Added `OnboardingStepper` component to manage and display step navigation in onboarding - Utilized Chingu's `Stepper` component for step progression visualization - Conditioned rendering of stepper based on current step
…pply FormWrapper - Moved PersonalInfoForm, WhatFeatures, HowDidYouHear, and LinkedInUrl to a new 'forms' folder for better organization. - Created FormWrapper component to wrap form content and applied it to the form components.
- Extracted OptionalLabel, QuestionHeader, and FormsSpacer into separate components. - Improved reusability and maintainability of the form components.
Refactored the component layout to enhance readability and maintainability. Wrapped elements in structured flex containers with appropriate gaps, improving spacing and alignment.
Updated `FormWrapper` to use a `flex` column layout with a small gap between child elements, improving spacing and structure.
Refactored `HowDidYouHear` to wrap the question header and optional label in separate divs, improving structure and readability.
Refactored `LinkedInUrl` to wrap the question header and spacer in a div, improving structure and consistency with other form components.
Updated the height of `OptionalLabel` from `h-8` to `h-6` for better spacing and alignment with other form elements.
…ility - Merged `optionsDataFirstCol` and `optionsDataSecondCol` into a single `options` array. - Removed redundant `formatOption` function and integrated option formatting directly into JSX. - Improved layout structure by wrapping the header and description inside a container. - Adjusted checkbox styling for better UI consistency.
@Homvi please resolve the merge conflicts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This draft PR introduces the initial changes for the new onboarding flow.
Progress Checklist
Type of change
How Has This Been Tested?
Manual testing
Test Instructions:
http://localhost:3000/sign-up
.Expected Behavior:
TBD: Tests will be added as the implementation progresses.
Checklist:
Feedback on the current UI structure and component naming is welcome!