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

Fully responsive two page officelite website using CSS and JS only.

Zybartas•480
@ZybartasRingys
A solution to the Officelite coming soon site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Simple two page coming soon website was a true challenge for my layout skills, using only CSS to make it fully responsive from mobile to desktop everything done with CSS and some vanilla JS for form input validation and arrow movement. If you have any improvements to my code write them in feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•2,010
    @AlexKMarshall
    Posted over 3 years ago

    This looks great at desktop size so well done. It's fairly responsive down to a smaller size, but at widths below 400px you're getting horizontal overflow, which makes it a bit off on smaller phones.

    Careful with the alignment. In the mobile layout, the pricing cards aren't centered on the page, there's more space on the right than on the left.

    The colours look good except for the call to action buttons. The colours there don't match the design and the contrast between the background and text is too low and fails accessibility checks.

    For your HTML semantics, make sure that you're using heading levels correctly. Your headings should read like a table of contents if you list them out. At the moment you have multiple h1's, and you skip from h1 to h3 to h5. Headings must always be used in the correct order, never skipping a level. You can size them however you want, using CSS.

    The 'get started' call to action is opening in a new tab. Don't do that, prefer remaining in the same tab, otherwise it's very jarring to users.

    On the second page, the form inputs do not have labels, they really should have them. Placeholders are not sufficient for accessibility. The contrast of the text should be increased too.

    It might also be nice if the count-down dynamically changed with javascript. It seems a little strange having something show the number of seconds til an event, but it stays the same.

    This may seem like quite a lot of points, but there's a lot of really great stuff in this solution.

    Marked as helpful

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub