Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 4 years ago

Responsive two page design using Sass, BEM, CSS grid, vanilla JS

Agata Liberska•4,075
@AgataLiberska
A solution to the Officelite coming soon site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was challenging but I learnt a lot!

  • I had to do some thinking with the pricing cards and how the content is distributed on different screen widths. Decided to go with CSS grid template areas in the end and I'm wondering if there's another solution that's not too difficult?
  • I would love any feedback about the countdown code, never done anything like this before!
  • On the signup page, I decided to stick to one column layout up until 1440px screen width, I felt like going into two earlier made things look very tight - what do you think?
  • For the form, I really wanted to try to make the custom dropdown as the bonus challenge suggested, although I realise that a native select dropdown would be more accessible (or just accessible, full stop). I found an article discussing how to make the markup I used accessible for keyboard and screen reader users, but I didn't want to use it without fully understanding what is going on - so I'm going to continue to study this and revisit this issue later on.
  • This being said, I would appreciate any feedback regarding accessibility across the rest of the project.
  • I've also never done form validation using vanilla JS, anything I could've done better?
  • And finally, I decided to try and divide my sass files into components etc. to make it more reusable - but I did it based on some random articles I found online, so if you have a moment to look through the folder structure I'd be very grateful!

Regarding HTML issues in the report - I added role="list" to the pricing cards after reading about issues in webkit based browsers - that screen readers do not recognise lists as lists after list style is set to none.

And of course any other comments you might have are very welcome! Thank you :)

Update: I finally made the dropdown accessible to screen readers and keyboard users!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Agata Liberska's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License