Frontend Mentor challenge - Intro component with sign up form

Contributing to project

Welcome! 👋

 A big welcome and thank you for considering contributing to open source project! Reading and following these guidlines will help us make the contribution process easy and effective for everyone involved. It also communicates that you agree to respect the time of the developers managing and developing these open source projects. In return, we will reciprocate that respect by addressing your issue, assessing changes, and helping you finalize your pull requests.

Quicklinks

• Challenge based on
• Main goal for challenge
• Plan workflow
• We use GitHub flow, so all code changes happen through Pull Request
• Dealing with issues
• Use a consistent coding style
• License
• References

Challenge newbie based on

• HTML (BEM technique)
• CSS (grid layout)
• JavaScript

Main goal for challenge

• View the optimal layout for the site depending on their device's screen size
• See hover states for all interactive elements on the page
• Receive an error message when the form is submitted if:
  • Any input field is empty. The message for this error should say "[Field Name] cannot be empty"
  • The email address is not formatted correctly (i.e. a correct email address should have this structure: name@host.tld). The message for this error should say "Looks like this is not an email"

Plan workflow

• Create drawing from design (structure of design)(1st task)
• Create of repo (2nd task)
• Create HTML layout (3rd task)
• Create CSS layout according style guides (4th task)
• Create grid layout for mobile first (5th task)
• Craete grid layout for desktop (6th task)
• Implement JavaScript (7th task)
• Overview of solution and RWD (8th task)
• Tada it is done. Congratulation you rich your goal.🎉

We use GitHub flow, so all code changes happen through Pull Request

1. Fork the repository (repo) to your own GitHub account
2. Clone the project to your PC (Git)
3. Create a new branch locally with a succinct but descriptive name
4. Make changes (edit, delete, copy, add) on the new brach
5. Commit changes to the branch
6. Following any formatting and testing guidelines specific to this repo
7. Push changes to your fork (repo)
8. Open a Pull Request (PR) in our repository and follow the PR template so that we can efficiently review the changes.
9. Wait when your contribution will be accepted (merged) or declined to fix issues.

Dealing with issues

Write issue reports with detail, background, and sample code

• A quick summary and/or background
• Steps to reproduce
  • Be specific!
  • Give sample code if you can.
• What you expected would happen
• What actually happens
• Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

Use a consistent coding style

• 4 steps for indentation rather than tabs

License

In short, when you submit code changes, you submissions are understood to be under the Frontend_Mentor license that covers the project. Feel free to contact the maintainers if that's a concern.

References

This document was adapted from the open-source contribution guidelines:

• A basic template for contributing guidlines
• A basic template for contributing guidlines
• Fork and Pull Request Workflow
• Working on your first GitHub issue
• Understanding GitHub issues
• Background to deal with Git and GitHub