NEONCORE sign-up with Next.js, Tailwind & a11y

Solution retrospective
I'm most proud of the progressive validation flow and the Operator ID panel that mirrors the form in real time. Getting blur/submit rules, password strength, loading (Transmitting_), and the success state to feel cohesive took the most care.
Next time I'd lock spacing and typography tokens earlier against the design, and build the field/button primitives first so hover, focus, and error states stay consistent with less rework.
What challenges did you encounter, and how did you overcome them?The hardest parts were layout centering across breakpoints and matching interactive states (double focus rings, hover button offset, outline submitting style) from static JPGs.
I fixed centering with a full-height flex container instead of fighting height: 100% on html/body, and treated each design state as a checklist while refining CSS tokens and component variants. Deploying to GitHub Pages also needed a static export with the correct basePath so assets resolved under the project URL.
I'd love feedback on:
- Whether the validation timing (blur → recheck on type; empty errors mainly on submit) matches expected UX/a11y patterns.
- Any gaps between the UI and the design for focus/hover/error states.
- Suggestions to simplify the form state management without losing the Operator ID sync.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Sergio Augusto Moreira Bastos Junior’s solution.
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord