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

Responsible Workit landing page using html and css

bem, foundation
Juan•30
@juangtddev
A solution to the Workit landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Built with

  • Semantic HTML5 markup
  • CSS custom properties
  • Flexbox
  • Mobile-first workflow

Project Challenges and Questions

Hello everyone! How are you doing? My name is Juan, and I'm transitioning my career to become a Frontend Developer. I've taken several courses in the field, but I believe it's crucial to put everything into consistent practice. That's why I'm here at Frontend Mentor. In order to achieve this, I've set the following goals for myself:

  • I've gone through the challenge list and arranged them from easy to difficult, and I'll be completing them in that order.
  • For the newbie and junior challenges, I'll be using just HTML, CSS, and JavaScript to build a solid foundation in these subjects.
  • As I progress to more advanced challenges, I'll start incorporating frameworks and different tools that make sense for each project.
  • Build a portfolio to show.

In this first challenge, I've already encountered a few obstacles and areas for improvement where I could use some help or feedback. They are as follows:

Header The initial challenge was positioning the central smartphone image and the side images. I used position, z-index, and screen coordinate placement for the side images. My doubts and possible areas of study for the future are: how can I make everything more responsive and less fixed as the screen size changes? Currently, I've placed the central smartphone image using an <img> tag and positioned it with margins and padding, but I'd like to make it more adaptable to screen resizing.

Footer Similarly, the main challenges in this were related to different positioning techniques and content overlap, and my solution was the same.

Organization I've attempted to follow the BEM (Block, Element, Modifier) methodology and separate my files according to the website sections. As a beginner, my challenge is to discover new ways to refactor this CSS code, making it smaller, more concise, and optimized.

I appreciate the feedback on these mentioned points and any suggestions for improvement.

Juan

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Juan•30
    @juangtddev
    Posted about 2 years ago

    For some reason the screenshot of FrontEnd mentor are not recognizing the fonts of the project, causing a difference.

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