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

Workit Landing Page

react, vite
Aarón Cervantes•20
@SoyAaronCervantes
A solution to the Workit landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Workit Landing Page

Frontend Mentor

This is my second challenge from this site.

The more I do this challenges, the more I learn and relearn about other things, that I don't have the opportunity to use on my daily job.

Description

This project is a landing page for a fictional company called Workit. The challenge is to build out this landing page and get it looking as close to the design as possible.

You can check the challenge here.

It was built with Vite, React, Typescript, Material 3, and pure CSS. Some sections, as I always used to said for each part of the landing page, are split on React components.

All the website is responsive, and the design is fully responsive.

What I learned

I learnt 3 things on this project:

  • Clip-path: Sometimes, you don't have the opportunity to use it, and also, check how does it works, it's kind of weird, but as always, there are some guides, that can help you to understand it.
  • Visibility: This property helps a lot, I reminded just because I wanted to use clip-path, but it's a good property to use. It helps me, to show the image over the curve at the bottom of the first section.
  • Media Queries: I haven't have the opportunity to build a dark mode website yet on my daily job, so I used this opportunity to do it. I have to admit that I used Material 3 Builder to make an idea about what do I want to do, and then try to replicate some rules that they follow for each color variable.

I think on my next challenge, I'm going to look for something that helps to use container queries. I used once, but I want something more challenging, meanwhile I grow my portfolio, personal projects, and improve my Frontend skills.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Aarón Cervantes'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
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.