Submitted about 1 month ago

Responsive Recipe Page

Francisco•210

@antoniomontoia

Preview site View code

This is a solution for...Recipe page

HTML
CSS

1newbie

Design comparison

SolutionDesign

Solution retrospective

What are you most proud of, and what would you do differently next time?

What I'm Proud Of:

Responsive Design: I successfully created a responsive page that adapts well to different screen sizes.

Learning New Elements and CSS Properties: I expanded my knowledge by working with various HTML elements like and , as well as CSS properties such as media queries and pseudo-elements.

Attention to Detail: I made a concerted effort to replicate the original design closely with Chrome Dev Tools always at hand.

What I would do differently next time:

Plan and Prototype: Before diving into coding, I would spend more time on planning and creating wireframes or prototypes (provided I do not have a Pro Subscription).

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

Challenges Encountered:

Table Sizing and Responsiveness: I struggled with figuring out how to size and style the table effectively to ensure it was responsive. Understanding how to use and elements properly, along with setting widths and borders, was initially confusing.

Styling Bullet Points in Lists: I found it challenging to style bullet points in lists to match the design requirements. Using pseudo-elements was a new concept for me, and I had to experiment to achieve the desired look.

How I Overcame These Challenges:

Research and Documentation: To tackle the table styling issue, I spent time researching best practices for table design and responsiveness. I referred to documentation and tutorials that explained how to use CSS properties like width: 100%, border-collapse, and how to apply styles to and elements effectively.

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

Areas for Help:

Code Semantics: I would appreciate a review of my HTML structure to ensure that I am using semantic elements correctly. I want to confirm that I am using tags like , , , , and appropriately to enhance accessibility.

Responsiveness: I would like assistance in evaluating how well my design adapts to different screen sizes. Any suggestions for improving the responsiveness of any of the elements would also be appreciated.

Code Conciseness: I am interested in having my CSS reviewed for conciseness and efficiency. I want to ensure that I am not repeating styles unnecessarily and that I am using best practices for CSS organization.

Community feedback

Steven Stroud•11,910
@StroudyPosted about 1 month ago
Exceptional work! You’re showing great skill here. I’ve got a couple of minor suggestions that could make this stand out even more…

Your heading elements <h1><h3><h2>, Heading elements should be in sequentially-descending order (e.g., <h1>, <h2>, <h3>) to create a clear content structure, improving accessibility and SEO. Skipping levels or using them out of order can confuse screen readers, affect search engine rankings, and make your content harder to understand.

<h1>Simple Omelette Recipe</h1> <h3>Preparation time</h3>

Using a full modern CSS reset is beneficial because it removes default browser styling, creating a consistent starting point for your design across all browsers. It helps avoid unexpected layout issues and makes your styles more predictable, ensuring a uniform appearance on different devices and platforms, check out this site for a Full modern reset

While px is useful for precise, fixed sizing, such as border-width, border-radius, inline-padding, and <img> sizes, it has limitations. Pixels don't scale well with user settings or adapt to different devices, which can negatively impact accessibility and responsiveness. For example, using px for font sizes can make text harder to read on some screens, Check this article why font-size must NEVER be in pixels. In contrast, relative units like rem and adjust based on the user’s preferences and device settings, making your design more flexible and accessible. Use px where exact sizing is needed, but prefer relative units for scalable layouts. If you want a deeper explanation watch this video by Kevin Powell CSS em and rem explained. Another great resource I found useful is this px to rem converter based on the default font-size of 16 pixel.

Line height is usually unitless to scale proportionally with the font size, keeping text readable across different devices. Best practice is to use a unitless value like 1.5 for flexibility. Avoid using fixed units like px or %, as they don't adapt well to changes in font size or layout.

I think you can benefit from using a naming convention like BEM (Block, Element, Modifier) is beneficial because it makes your CSS more organized, readable, and easier to maintain. BEM helps you clearly understand the purpose of each class, avoid naming conflicts, and create reusable components, leading to a more scalable codebase. For more details BEM,

For future project, You could download and host your own fonts using @font-face improves website performance by reducing external requests, provides more control over font usage, ensures consistency across browsers, enhances offline availability, and avoids potential issues if third-party font services become unavailable. Place to get .woff2 fonts

Using rem or em units in @media queries is better than px because they are relative units that adapt to user settings, like their preferred font size. This makes your design more responsive and accessible, ensuring it looks good on different devices and respects user preferences.

@media (min-width: 200px)

I hope you’re finding this guidance useful! Keep refining your skills and tackling new challenges with confidence. You’re making great progress—stay motivated and keep coding with enthusiasm! 💻
Marked as helpful
0
Francisco•210
@antoniomontoiaPosted about 1 month ago
@Stroudy Thanks a lot for taking the time to review my code and provide such a precise feedback! This was exactly what I was looking for and I will keep referring to this piece of advice for the following projects.
1
Steven Stroud•11,910
@StroudyPosted about 1 month ago
Hey @antoniomontoia, No problem, You got this! 💪
0

Please log in to post a comment

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