Creative Bakery landing page (HARD)

⚠️ Attention: this is a hard landing page for development. We highly recommend choosing this landing page only if you didn't have a lot of troubles with previous homework tasks and if you sent all homework in time (didn't miss deadlines).

Implement landing page according to Figma design - Use BEM and SCSS

• Large screens 2560px
• Full HD 1920px
• The design 1600px
• Notebook 1280px
• Tablet 1024
• Mobile (> 320px)

Checklist for preparing a portfolio project for HR review

1. Don’t forget to add a title for the whole web page (it could be the name of your landing)
2. A landing page is implemented strictly according to the design in Figma
3. Links in the header and footer menus should lead to the corresponding blocks of the landing page
4. The speed of animations is the same throughout the landing page (for example, increasing when hovering or moving blocks when scrolling)
5. Placeholders in the forms suggest what to enter, and if there is a validation of the form, then it is clear in what format to enter the phone number
6. Make sure everything looks neat on mobile and without horizontal scrolling
7. Add favicon
8. Add a smooth scroll for the whole page
9. The “learn more” button leads to the “About us” block
10. It would be more realistic if the arrows in the hero section next to the product photo were clickable (or hide these arrows if there are no other photos for the slider)
11. The "all bakeries" button leads to the BakerShops block
12. In the "Bakershops" block, add a drop-down list with a list of cities and addresses in which this store is located (and when you try to click on "Search" let the form just be cleared)
13. When you try to send the Bakershops search form there is no 405 error and the form is automatically cleared after submit and is scrolled to the top of the page or the page is reloaded
14. Menu footer buttons when clicked should lead to the relevant blocks of the landing page
15. The user must have the opportunity to write 2-3 lines of text in the message field
16. In the form at the end of the page, do not forget to add a placeholder for the message field
17. The form shouldn’t accept incorrect data in a field with a phone number (for example, a number with a letter and there was no error), give this and all inputs a correct input type
18. When you try to send the form there is no 405 error and the form is automatically cleared after submit and is scrolled to the top of the page or the page is reloaded
19. The form shouldn’t submit empty

Github flow

1. Fork the repo.
2. Clone the forked one. (The project link should have your name but not mate-academy)
3. Run npm install (or just npm i).
4. Run npm start.
5. Open one more terminal window for the next steps.
6. git checkout -b develop - to create new branch and switch on it.
7. Write you code in src folder.
8. Run npm run lint and fix code style errors.
9. Run npm run deploy to deploy your solution to gh-pages.
10. git add . && git commit -m 'solution' to save your changes.
11. git push origin develop - to send you code for PR.
12. Create a Pull Request (PR) from your branch develop to branch master of original repo.
13. Replace <your_account> with your Github username in the DEMO LINK.
14. Copy DEMO LINK to the PR description.

To update you PR repeat steps 7-11.