Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 days ago

Responsive page using bootstrap

bootstrap
rouhollah-sari•60
@rouhollah-sari
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?

In this practice I tried to write a clean and easy to edit code. I think I learned bootstrap grid a lot in this practice.

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

The most difficult challenge I faced in this practice was the column width in bootstrap. The problem was how to set the column size to avoid extra space and benefit from aligning the lines at the same time.

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

I am a little wonder about the font size and font type in this practice.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • beowulf1958•1,890
    @beowulf1958
    Posted 9 days ago

    Congratulations on completing the project. It looks good. Your code is well organized, with the different sections in the html matching up to the section in CSS. The comments in CSS are super important. You made good use of CSS variables and the page is responsive.

    Great job using Bootstrap! I am also learning Bootstrap. It is easy to see you put in a lot of work. Maybe too much work? Bootstrap allows you style the font-size, font-weight, padding, and margins as you are marking up the html, saving a lot of time on the backend when applying your custom styles. Also, it is best practice to give each class a meaningful name: class="ingredients" instead of class="part_4" and then each element would be class="ingredients-title" and class="ingredients-text"

    The next step would be to make your html more semantic. Every page needs an <h1>. So in this case you would have a structure something like:

    <div class="main">
      <section class="heading"></section>
      <section class="preparation"></section>
      <section class="ingredients">
       <section class="ingredients">
         <h2 class="pt-4 mb-3 fw-semibold">Ingredients</h2>
           <ul>
              <li>2-3 large eggs</li>
              <li>Salt, to taste</li>
              <li>Pepper, to taste</li>
              <li>1 tablespoon of butter or oil</li>
              <li>Optional fillings: cheese, diced vegetables, cooked meats, herbs.</li>
            </ul>
        </section></section>
      <section class="instructions"></section>
      <section class="nutrition"></section>
    </div>
    

    which simplifies the CSS somewhat

    /* Style for the ingredients*/
    .ingredients{
      border-bottom: solid 2px rgba(00, 00, 00,0.1);
      background-color: var(--White);
     }
    
     .ingredients-title{
      font-family:'Young Serif'
      color: var(--Brown-800);
      font-size: 175%;
     }
    
     .ingredients-text{
       font-size: 125%;
     }
    

    Again, great job and keep up with Bootstrap. Once you are familiar with it, it will save you a lot of time.

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