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

HTML5 for semantic structure , CSS3 for styling and responsiveness

Kama•110
@Kama-ds10
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 most proud of:

Completing the project with clean, organized HTML and CSS.

Properly using Flexbox and media queries to make the page fully responsive across different screen sizes.

Matching the style guide accurately, especially with typography and layout spacing.

Learning how to better structure tables and use semantic HTML for accessibility.

What I would do differently next time:

Spend more time optimizing the CSS by using reusable utility classes to avoid repetition.

Plan the layout with CSS Grid for even more control over the design structure.

Try to implement animations or small transitions to make the page feel more interactive.

Pay even more attention to fine-tuning responsiveness at different breakpoints beyond just 768px.

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

Challenges I faced:

Vertical centering the content: Initially, it was difficult to center the recipe card both vertically and horizontally on the page, especially across different screen sizes.

Responsive layout issues: Making the layout look good on both small and large screens was tricky, particularly getting the nutrition facts table to adjust properly.

Following the style guide exactly: Small details like the correct border-radius, font weight, and spacing required careful checking to match the design.

How I overcame them:

I researched how to use Flexbox for centering, using properties like justify-content: center and align-items: center.

I applied a mobile-first approach with CSS media queries to handle different screen sizes step-by-step.

I continuously compared my project to the original design and made small adjustments until everything looked consistent.

I also referred to the Front End Mentor community tips and documentation when I got stuck on certain CSS properties.

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

I would appreciate feedback on:

CSS structure and organization: Are there ways I can make my CSS cleaner or more efficient (e.g., using reusable classes, better naming)?

Responsiveness: Are there improvements I could make to better handle different screen sizes or devices beyond just using a single media query?

Accessibility: Is there anything I could do to make my HTML more accessible, such as better use of semantic tags or improvements for screen readers?

Visual alignment and spacing: Did I correctly match the design, or are there small visual details I should improve?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • xdarinka•90
    @xdarinka
    Posted about 2 months ago

    good job bro!

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