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

Mobile First Responsive Web Page using CSS Flex Box

Jillian Lemsanes•30
@jillianlemsanes
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Questions I have:

  1. How to make my buttons responsive? I ended up just making a media query at small screen sizes that allowed the buttons to not "break" at smaller screens. The buttons looked great until about 350 px and smaller. I could not find a great way to make the button proportionally shrink with the screen. In the media query, I ended up changing my padding and font size which ended up working great...but is this good practice?

  2. Any good tips on making spaces between sections of code? I got the web page to look how I needed it, but I ended up using so many margins and padding that I am sure there is a better way to do this. If you take a look at my code, you will see lots of "margin-bottom" and properties like this, and I want to know if there is a better and cleaner way to get spacing right.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sahand Masoleh•1,210
    @sahand-masoleh
    Posted almost 3 years ago

    Hi there!

    You don't need to concern yourself with view widths smaller than 250px in my opinion, a lot of major websites are already broken at that point.

    1. For your buttons, I would put the button styling on the container around the anchor tag, that way it could grow and shrink naturally without breaking. Get used to using wrappers, they result in ugly code but are the solution to many problems.

    2. If you use flex-box or grid layouts, you can use the gap property to put spaces between your elements and reduce the use of margins. With grid, you can also set your track sizes and sometimes move the spacing login to the container that way.

    Marked as helpful

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