Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive Recipe Page using HTML and CSS

FafioluOluwadamilola•50
@FafioluOluwadamilola
A solution to the Recipe 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?

I'm proud that I have gotten better at coding in general

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

Styling it to fit mobile view and adjusting the font width to match perfectly and also determining what font color to use

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

I would love to know how the numbers 1-6 were styled, I tried but I couldn't do it

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Justin Connell•720
    @justinconnell
    Posted over 1 year ago

    Hi @DammyFaffy,

    As per your request regarding making your design responsive you need to use a media query to apply different layouts such as the one below:

      .container {
        max-width: 375px;
      }
      @media (min-width: 768px) {
        .container {
          max-width: 736px;
        }
    
    

    The code above takes a 'mobile first approach' and sets the maximum width for a container - for mobile the max-width is 375px and on screens larger than 768px, the max-width is 736px.

    The key is to use media queries to define styling for specific screen sizes. Starting with the mobile first approach and moving up screen sizes helps to simplify the process.

    You can learn more about mobile first here

    I do have a question for you though, what resources are you currently using to learn web development?

    I hope you find this useful

    Keep on coding and learning! J

    Marked as helpful
  • FafioluOluwadamilola•50
    @FafioluOluwadamilola
    Posted over 1 year ago

    Thanks 👍👍

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 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