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

Officelite Coming Soon Site | Fluid Space and Fluid Typography

accessibility, lighthouse, sass/scss, bem
Vanza Setia•27,715
@vanzasetia
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 Everyone! 👋

I finally completed another challenge! 🎉

In this challenge, I completed the challenge by using fluid space and fluid typography which by using clamp() functions a lot. I also used CSS logical properties.

Any questions on the technique that I'm using are welcome! Of course, any suggestions on how I can improve are welcome! 😁

Also, if you have finished this challenge and would like me to give feedback on it, please include a link to your solution. I would be glad to help you! 😀

Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Stu Cowley•230
    @frontendstu
    Posted almost 2 years ago

    Hi there Vanza,

    I've had a look at your solution and it looks amazing! I'm wondering if you had any problems with the charts svg not displaying the fonts correctly. I made sure all fonts were converted to shapes and it is still displaying as Times New Roman not Kumbh Sans like in the design. I'm kind of pulling my hair out over this one

  • Alawi Hamed Alaidaros•150
    @Alawihamed
    Posted over 2 years ago

    I have seen your solution and it is tidy and consistent on all screens. Continue to solve a lot of challenges until you develop more and more

  • Hamzat Lawal•560
    @EngineerHamziey
    Posted almost 3 years ago

    😘 Your solution is amazing, I'm just checking it out and remembered a question I have wanted to ask you since a very long time. I have learnt markdown but your markdown skills seems to be on another level 😁. Could you please recommend a markdown tutorial for me? I want to step up to 😊

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.

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

Oops! 😬

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

Log in with GitHub