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

Responsive recipe page using HTML, CSS and Bootstrap

bootstrap
GabrielRenan11•10
@GabrielRenan11
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?

Well, i'm happy for everthing, even though it's simple, i believe it's the first project that i truly made by myself, (with some AI and friend help), and i am happy to see that i can make the project similar to its standards, but anyways, im not ignorant on the fact that the fonts aren't properly setted up, altough it looks similar; i tried to correct this, but i didn't know how to attribute it (i just linked); and also the lines in the tabble are not in the correct width, anyways, just to contextualize, i wanted to train bootstrap more, and maybe by this reason i couldn't customize the elements so much, but i insisted because i really wanted to train my knowledge on this, also, the styles are sometimes in the elements, sometimes inside the style tag; i think i have used the style tag to more general stylishment, for me this is a good programming practice, but i'm open to feedback.

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

The first was with the colors, how to declare them as variables (i've never used HSL pattern), in wich i used AI, i also used AI to see how to attribute the linked fonts to certain elements (it didn't help), and the most difficult thing was the image responsivity, in wich i used AI to respond me a question on how to make the image addapt to the screen size, and also asked to a friend on how to make the "@media" work properly.

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

I would like to know how to attribute the fonts that i linked to an element, and the limits of customization on bootstrap, because my friend told me that we cant customize some elements aspects when using bootstrap; and for last, but not less important (okay, a tiny bit less), know a little more about HSL color pattern.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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