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

Mobile-first-officelite-coming-soon-site

Veronica Orozco•260
@VLOrozco
A solution to the Officelite coming soon site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone! Hope all is well.

Here is my mobile-first solution for the Officelite Coming Soon Site! I used JavaScript for the bonus countdown date & timer and form email validation.

I have some whitespace showing on my sign-up page in different views.

Any tips to make it better would be great. Thanks in advance! ~V

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hello, Veronica! 👋

    It's great that you wrote the CSS with the mobile-first approach. This approach often leads to shorter and better performance code. Also, mobile users won't be required to process all of the desktop styles.

    I have some feedback on this solution.

    • For the background pattern, I recommend creating it with pure CSS. You can choose to use either pseudo-element or background properties. This way, there is no need for decorative HTML elements.
    • It is not valid HTML to make an anchor tag as a child element of the button element. Choose either it is a button or a link element.
    • I recommend reading the MDN documentation for role="complementary". The cards are the main content. So, they are not complementary content.
    • Remove the role="heading" from the heading tags. There's no need to specify the role when you already use semantic HTML.
    • Use single class selectors for styling whenever possible instead of id. id has high specificity which can lead to a lot of issues on the larger project. It's best to keep the CSS specificity as low and flat as possible.
    • Avoid using JavaScript to add styling (unless you have no other option). JavaScript allows you to change the CSS code using the style property. But, to make debugging easier and improve code maintainability, it’s best to avoid it. Use CSS classes instead.
    • Don't use jQuery to do something simple. Use JavaScript instead.
    • The custom select is not accessible with the keyboard and screen reader. I recommend taking a look at the Select-Only Combobox Example from W3C.

    In general, I don't recommend using ARIA attributes when you are already using semantic HTML. Also, if you want to use them, make sure you read the documentation about them to know what is their purpose and how to use them appropriately.

    I hope this helps!

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
Frontend Mentor logo

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.

Oops! 😬

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

Log in with GitHub