Design comparison
Solution retrospective
I had done all the free beginner challenges before starting a Learning Path, so I'm proud of going back to the project and refining it a bit.
What challenges did you encounter, and how did you overcome them?I encountered the challenge of deciding which method to use for creating the links to the user's socials. I don't know which way is most practical or effective but it was interesting to experiment with that section.
What specific areas of your project would you like help with?I don't have any particular areas I'd like help with, but if anyone has critiques and advice I'm completely open to and appreciative of it!
Community feedback
- @MikDra1Posted 2 months ago
Well done, here are some things to review 😊:
-
REM for Units: It's best to use
rem
for all units instead ofpx
, as this ensures scalability and consistency in spacing and font sizes based on the user's root font size. It helps improve accessibility. -
Semantic HTML: Consider ensuring all elements are wrapped in semantic HTML tags like
<main>
,<section>
, and<article>
to enhance the structure and SEO-friendliness of the page. -
BEM/Convention for Class Naming: Apply a class naming convention like BEM (Block Element Modifier) to make the styles modular and more maintainable. For example, use
.card__title
or.card--highlighted
. -
Clamp() for Responsiveness: Use the
clamp()
function for fluid typography and spacing, allowing elements to resize smoothly between a minimum and maximum value based on the viewport size (e.g.,font-size: clamp(1rem, 2vw, 1.5rem)
). -
Responsive Card: To make the card responsive, ensure the layout uses
flex
orgrid
combined with max-width instead of fixed width values. This will make the design more flexible and adapt better to different screen sizes. -
Use max-width/min-width and max-height/min-height: Instead of using fixed
width
andheight
, opt formax-width
ormin-width
to allow the elements to resize smoothly on different screen sizes, improving overall responsiveness.
Hope you found this comment helpful 💗💗💗
Good job and keep going 😁😊😉
0 -
- @StroudyPosted 2 months ago
Awesome job tackling this challenge! You’re doing amazing, and I wanted to share a couple of suggestions that might help refine your approach…
-
The
<hgroup>
tag was deprecated because it caused confusion about how to handle heading semantics, and it wasn't widely adopted by developers. Modern HTML approaches now simply use headings without the need for this grouping tag, while relying on other methods (like CSS or ARIA) to achieve more complex heading relationships. -
float was used for layout, but it's now mostly replaced by CSS Flexbox and Grid, which offer more powerful, flexible, and easier-to-control layout options without the quirks of float.
-
Developers should avoid using pixels (
px
) because they are a fixed size and don't scale well on different devices. Instead, userem
orem
, which are relative units that adjust based on user settings, making your design more flexible, responsive, and accessible. For more information check out this, Why font-size must NEVER be in pixels or this video by Kevin Powell CSS em and rem explained.- Another great resource for px to rem converter. -
Using
max-width: 100%
ormin-width: 100%
is more responsive than justwidth: 100%
because they allow elements to adjust better to different screen sizes. To learn more, check out this article: responsive-meaning. -
For future project, You could downloading 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
You’re doing fantastic! I hope these tips help you as you continue your coding journey. Stay curious and keep experimenting—every challenge is an opportunity to learn. Have fun, and keep coding with confidence! 🌟
0 -
- @Jaydev576Posted 2 months ago
In your README file you wrote about learn to use font files from the assets folder, you can do that with the help of @font-face in css. You just have to add @font-face in css file and in this you can name your custom fonts in font-family like below:
@font-face { font-family: 'customName'; src: url(./assets/fonts/font-file.type) format('font-type'); }
After adding this you can access this fonts with your given custom name!
0
Please log in to post a comment
Log in with GitHubJoin 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