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

Officelite website | HTML, CSS, JS

gsap, sass/scss, webpack, typescript
P
Christopher Adolphe•620
@christopher-adolphe
A solution to the Officelite coming soon site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello there!

This is my 1st challenge on Frontend Mentor and I really enjoyed it. I am pretty much satisfied with the final result.

Major challenge(s):

  • The custom-styled select was a bit challenging. I used a list of radio button inputs to mimic the list of options and wired that with JavaScript to handle the events. While I this was a great opportunity to practice my JS skills, I still wonder if some of you have found a simpler approach for this feature.

Unsure of:

  • When I validated the compiled css, I noticed that some of my sass variables went being output as well. I'm not sure if there is an issue with my breakpoint mixin or if it is because I recently switched from @import to @forward and @use in my .scss files. I'd be grateful if you could point out what I'm doing wrong here.
  • The accessibility validation notified me of 3 contrast errors, I chose to ignore them and stick to the design. Would you have done same ?

Bonus features:

  • The signup form shakes to display the invalid state and flips to display a success message when valid.
  • I added some animations using GSAP and the ScrollTrigger plugin.

Your feedback would be much appreciated.

Thanks in advance. 🙏

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ollie•580
    @ohermans1
    Posted about 3 years ago

    Hey Mate

    Just want to say that this is awesome! I really like the shake on invalid for the form - I'm gonna give it an idea in a future project!

    I'm looking forward to seeing what you do next!

    Ollie

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub