add task solution

README.md

@@ -1,71 +1,24 @@
-# Dia landing page
-Implement landing page according to [Figma design](https://www.figma.com/file/7qwsWggv9BAxMi2VPhBuPr/Air-(formerly-Dia)?node-id=9138%3A35) - Use BEM and SCSS
+# Air
 
-Adapt the page to the following screens:
-- Large screens 2560px
-- The design 1600px
-- Desktop 1280px
-- Small desktop 1024px
-- Tablet 640px
-- Mobile (> 320px)
+### Description
 
-1. Implement the header with `nav`.
-1. Implement `Strategic agency` block.
-1. Implement slider (You may start with a single picture).
-    - implement slider block as absolutely positioned element with `right: 0` and `bottom: 0` position inside the black container
-    - on large screens limit the width of black container to 1600px, so that left outer space have a standart grey background color
-3. Implement `Who we are` block.
-4. Implement `Our expertise` block with the card reused 3 times.
-5. Implement `Process` block with 4 process cards.
-    - use `trasnlateY(-50%)` to move cards up
-6. Implement `Testimonials` block.
-     - each card should have a fixed width and on the small screens the whole block should switch to column layout
-8. Implement `Vision, Passion, Results` block.
-    - use https://github.com/mate-academy/layout_dia/blob/master/src/images/Shapes.png as background picture
-9. Implement `Send us  a message` block.
-10. Implement `Contact us` block.
-11. Implement the footer.
+- Created a landing page
 
-## Checklist for preparing a portfolio project for HR review
+### Stack
 
-1. Don’t forget to add the title “Air” for the whole web page
-2. A landing page is implemented strictly according to the design in Figma
-4. Links in the header and footer menus should lead to the corresponding blocks of the landing page
-5. The speed of animations is the same throughout the landing page (for example, increasing when hovering or moving blocks when scrolling)
-6. 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
-7. Make sure everything looks neat on mobile and without horizontal scrolling
-8. Add favicon
-9. Add a smooth scroll for the whole page
-10. 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
-11. The form shouldn’t submit empty
-12. The "Learn more" button should lead to the closest block (Our expertise)
-13. The "Hire Us" button in the header menu should lead to the contact form
-14. In the PROCESS section add a hover effect to cards (for example, let them increase in size a little)
-15. Inside the cards in PROCESS sections, make a link out of the "Learn More" text, so that it hovers simultaneously with the arrow button on the left
-16. In the Vision, Passion, Results section, the “Apply” button also should lead to the contact form
-17. In the Testimonials and Our expertise section add hover effects for each review
-18. After clicking the menu buttons, the landing page will scroll exactly to the beginning of the desired block (exactly where its section begins)
-19. The arrows at the bottom of the first block should not respond slowly to pressing (this is possible if the pictures are too large)
-20. When a user clicks on Address Google Maps is opened in a new tab
-21. The user must have the opportunity to conveniently write 2-3 lines of text in the message field
-22. OPTIONAL: After everything is done, you can implement the slider on the hero page (you can find images for it on Unsplash)
+- HTML (BEM)
+- CSS (SCSS)
+- JS
+- Adaptive
 
+### Tools
 
-## 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](https://<your_account>.github.io/layout_dia/).
-14. Copy `DEMO LINK` to the PR description.
+- ESlint
+- Jest
+- Prettier
+- Parcel
 
-> To update you PR repeat steps 7-11.
+## Demo Links
+
+- [Demo](https://AndriiZakharenko.github.io/air/)
+- [Figma](https://www.figma.com/file/7qwsWggv9BAxMi2VPhBuPr/Air-(formerly-Dia)?node-id=9138%3A35)