https://github.com/jrag-dev/contact-form-main-nextjs
Contact form validations using nextjs, tyepscript, zod and react hook form
https://github.com/jrag-dev/contact-form-main-nextjs
nextjs react-hook-form reactjs tailwindcss typescript zod-validation
Last synced: 2 months ago
JSON representation
Contact form validations using nextjs, tyepscript, zod and react hook form
- Host: GitHub
- URL: https://github.com/jrag-dev/contact-form-main-nextjs
- Owner: jrag-dev
- Created: 2025-04-14T06:13:32.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-04-15T07:15:07.000Z (about 1 year ago)
- Last Synced: 2025-04-15T07:34:46.957Z (about 1 year ago)
- Topics: nextjs, react-hook-form, reactjs, tailwindcss, typescript, zod-validation
- Language: TypeScript
- Homepage: https://contact-form-main-nextjs-3m5ytj6pr-jragdevs-projects.vercel.app/
- Size: 192 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Frontend Mentor - Contact form
## Welcome! 👋
Thanks for checking out this front-end coding challenge.
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects.
**To do this challenge, you need a good understanding of HTML, CSS and JavaScript.**
## The challenge
Your challenge is to build out this contact form and get it looking as close to the design as possible. Pay particular attention to making this form accessible. Building accessible forms is a key skill for front-end developers. So this is a perfect challenge to practice.
You can use any tools you like to help you complete the challenge. So if you've got something you'd like to practice, feel free to give it a go.
Your users should be able to:
- Complete the form and see a success toast message upon successful submission
- Receive form validation messages if:
- A required field has been missed
- The email address is not formatted correctly
- Complete the form only using their keyboard
- Have inputs, error messages, and the success message announced on their screen reader
- View the optimal layout for the interface depending on their device's screen size
- See hover and focus states for all interactive elements on the page
Want some support on the challenge? [Join our community](https://www.frontendmentor.io/community) and ask questions in the **#help** channel.
## Screenshot
## Links
- Solution URL: [Add solution URL here](https://github.com/jrag-dev/contact-form-main-nextjs)
- Live Site URL: [Add live site URL here](https://contact-form-main-nextjs-kn28-n61bcc2v1-jragdevs-projects.vercel.app/)
## Where to find everything
Your task is to build out the project to the designs inside the `/design` folder. You will find both a mobile and a desktop version of the design.
The designs are in JPG static format. Using JPGs will mean that you'll need to use your best judgment for styles such as `font-size`, `padding` and `margin`.
If you would like the Figma design file to gain experience using professional tools and build more accurate projects faster, you can [subscribe as a PRO member](https://www.frontendmentor.io/pro).
All the required assets for this project are in the `/assets` folder. The images are already exported for the correct screen size and optimized.
We also include variable and static font files for the required fonts for this project. You can choose to either link to Google Fonts or use the local font files to host the fonts yourself. Note that we've removed the static font files for the font weights that aren't needed for this project.
There is also a `style-guide.md` file containing the information you'll need, such as color palette and fonts.
## Building your project
Feel free to use any workflow that you feel comfortable with. Below is a suggested process, but do not feel like you need to follow these steps:
1. Initialize your project as a public repository on [GitHub](https://github.com/). Creating a repo will make it easier to share your code with the community if you need help. If you're not sure how to do this, [have a read-through of this Try Git resource](https://try.github.io/).
2. Configure your repository to publish your code to a web address. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, and we provide some recommendations below.
3. Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes to create reusable styles.
4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
5. Write out the base styles for your project, including general content styles, such as `font-family` and `font-size`.
6. Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.
## My process
### Built with
- Semantic HTML5 markup
- Flexbox
- CSS Grid
- Mobile-first workflow
- [React](https://reactjs.org/) - JS library
- [Nextjs](https://nextjs.org/) - JS Framework
- [TypeScript](https://www.typescriptlang.org/) - TypeScript is JavaScript with syntax for types
- [React hook form](https://react-hook-form.com/) - Performant, flexible and extensible forms with easy-to-use validation.
- [Zod](https://zod.dev/) - TypeScript-first schema validation with static type inference
- [Tailwind CSS](https://tailwindcss.com/) - For styles
## Author
- Frontend Mentor - [Jose Alvarado](https://www.frontendmentor.io/profile/jrag-dev)
- Github Profile - [Jose Alvarado](https://github.com/jrag-dev)