Skip to content

MaksimusCRS/layout_KateVR

 
 

Repository files navigation

KateVR landing page

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. 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
  10. The video should work. If it is not working, it can confuse the recruiter/user, because then it is not clear why it is on the landing page.
  11. The Next button is active and clickable and leads to the next block
  12. “Buy now” buttons are active and clickable and lead to the contact form
  13. The form shouldn’t submit empty
  14. 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

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.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • SCSS 46.8%
  • HTML 31.5%
  • JavaScript 21.7%