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

Sign up site

nikolajseverin•60
@nikolajseverin
A solution to the Ping single column coming soon page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

probraly just how good it looks, and also the hover modes, looks nice!

What challenges did you encounter, and how did you overcome them?

I’m currently facing a challenge with making my site responsive after going live with my HTML and CSS project. I’ve built the layout for desktop screens (1440px), and it looks good at that size. However, I’m not sure how to approach making it work for mobile devices (like 375px width).

When I open my live site and try to resize the window, I can’t get it to show how it would look at 375px unless I use Chrome’s developer tools and switch to mobile view manually. This makes it hard for me to understand what the proper workflow or strategy is for developing a responsive site that works well on both desktop and mobile.

I know that media queries are involved, but I’m confused about: • When and how to test mobile views effectively (especially after going live). • How to set up a proper development process for building mobile responsiveness after the desktop version is done. • Whether I should rely on the Chrome inspector tools for mobile views, or if there’s a better approach.

Any advice or guidance on how to structure the development and testing for responsiveness would be super helpful!

What specific areas of your project would you like help with?

I’m currently facing a challenge with making my site responsive after going live with my HTML and CSS project. I’ve built the layout for desktop screens (1440px), and it looks good at that size. However, I’m not sure how to approach making it work for mobile devices (like 375px width).

When I open my live site and try to resize the window, I can’t get it to show how it would look at 375px unless I use Chrome’s developer tools and switch to mobile view manually. This makes it hard for me to understand what the proper workflow or strategy is for developing a responsive site that works well on both desktop and mobile.

I know that media queries are involved, but I’m confused about: • When and how to test mobile views effectively (especially after going live). • How to set up a proper development process for building mobile responsiveness after the desktop version is done. • Whether I should rely on the Chrome inspector tools for mobile views, or if there’s a better approach.

Any advice or guidance on how to structure the development and testing for responsiveness would be super helpful!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on nikolajseverin'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.