When I was pushing to Git, I kept making mistakes on the README.md file and had to keep repeating the process of git add, git commit and git push. I have now gotten it to read the way I want it to. The problems originated from using the wrong file paths for the README.md file and my project's screenshot initially.
Kamran Kiani
@kaamiikAll comments
- @subjectiverealityySubmitted 26 days agoWhat challenges did you encounter, and how did you overcome them?P@kaamiikPosted 25 days ago
Hi. Some notes for your code:
HTML
- A proper page structure inside
<body>
should look like this:
<body> <header>...</header> <main>...</main> <footer>...</footer> </body>
Since this is a card component, we only need the
<main>
element.
- For
<img>
tag you need alt text to describe the image. Although for decorative and avatar images You need to add an emptyalt=""
because there is no information in the photo. The point is you have to usealt
.
- Follow proper heading hierarchy:
- Each page should have one
<h1>
- For components that are part of a larger page, use
<h2>
instead - This maintains proper document structure while reflecting component hierarchy
- Each page should have one
- You do not need to wrap the person name into a
<span>
. Simply use ap
tag.
CSS Best Practices
- Start with a proper CSS reset (Andy Bell or Josh Comeau resets are recommended)
-
Use viewport height properly:
/* Instead of: */ body { height: 100vh; } /* Use: */ body { min-height: 100vh; }
This ensures content can expand beyond viewport height
- Avoid fixed widths and height for text containers:
- Remove
width: 384px
andheight: 522px
from.wrapper
- Use
max-width
for better text container adaptability
- Remove
- Use relative units:
rem
forfont-size
andmax-width
instead ofpx
- Learn more about this here
- Follow mobile-first approach:
- Start with mobile styles as the default
- Use
min-width
in media queries - Use
em
units for breakpoints
Example media query:
@media (min-width: 40em) { /* Desktop styles */ }
1 - A proper page structure inside
- @evitakatrinaSubmitted 25 days agoP@kaamiikPosted 25 days ago
Hi. I see some issues in your code I wanna mention:
HTML
- A proper page structure inside
<body>
should look like this:
<body> <header>...</header> <main>...</main> <footer>...</footer> </body>
Since this is a card component, we only need the
<main>
element.
- For decorative and avatar images, use empty alt text:
alt=""
- Avoid using words like image, picture, or photo in alt descriptions
- The "Learning" text should not be a
<span>
- it should be a<p>
tag. The person name is a<p>
tag too.
- Elements with hover effects are considered interactive
- If an element with hover effects navigates to a new page, wrap it in an
<a>
tag. Here yourh2
is interactive too. So you need to wrap it inside thea
tag:
<h2><a href="#">Title Text</a></h2>
CSS Best Practices
- Start with a proper CSS reset (Andy Bell or Josh Comeau resets are recommended)
-
Use viewport height properly:
/* Instead of: */ body { height: 100vh; } /* Use: */ body { min-height: 100vh; }
- Avoid fixed widths for text containers:
- Remove
width: 300px
from.card
- Use
max-width
for better text container adaptability
- Remove
- Use relative units:
rem
forfont-size
andmax-width
instead ofpx
- Learn more about this here
0 - A proper page structure inside
- P@YonerfySubmitted 26 days agoP@kaamiikPosted 26 days ago
I have some notes for your code which may help improve your code:
HTML
- For single-component pages, use a minimal semantic structure:
<body> <main>...</main> </body>
This provides proper document outline while keeping markup minimal. Remember the
main
tag is necessary.
-
Image descriptions should be meaningful and descriptive:
- Use alt text that explains the purpose:
alt="QR code to Frontend Mentor website"
- Use alt text that explains the purpose:
- Follow proper heading hierarchy:
- Each page should have one
<h1>
- For components that are part of a larger page, use
<h2>
instead - This maintains proper document structure while reflecting component hierarchy
- Each page should have one
CSS
- Start with a proper CSS reset (Andy Bell or Josh Comeau recommended)
- This ensures consistent styling across browsers
- You don't need
min-width
onbody
. Also no need formax-width
on#root
. You only need amax-width
on.card
withrem
unit.
- Keep image styling minimal and responsive:
img { max-width: 100%; display: block; }
This ensures:
- Images scale properly
- No unwanted whitespace below images
- Content adapts to different screen sizes
CSS Units Best Practices
- Use relative units for better accessibility and scaling:
- Convert
font-size
andmax-width
values frompx
torem
- This allows text and layout to scale with user preferences
- Read more about unit best practices here
- Convert
This improves:
- Accessibility for users who adjust browser text size
- Consistent scaling across devices and zoom levels
- Code maintainability and flexibility
1 - @Z3ra33Submitted 28 days agoP@kaamiikPosted 28 days ago
Hi. I have some notes for your code which may improve it.
GitHub
- Use one repo for each project. Adding all in one repo consider as a bad practice.
HTML
- For single-component pages, use a minimal semantic structure:
<body> <main>...</main> </body>
This provides proper document outline while keeping markup minimal.
- Follow proper heading hierarchy:
- Each page should have one
<h1>
- For components that are part of a larger page, use
<h2>
instead - This maintains proper document structure while reflecting component hierarchy
- Each page should have one
CSS
- Start with a proper CSS reset (Andy Bell or Josh Comeau recommended)
- This ensures consistent styling across browsers
- For
img
usemax-width: 100%;
This ensures:
- Images scale properly
- Content adapts to different screen sizes
CSS Units Best Practices
- Use relative units for better accessibility and scaling:
- Convert
font-size
andmax-width
values frompx
torem
- This allows text and layout to scale with user preferences
- Read more about unit best practices here
- Convert
This improves:
- Accessibility for users who adjust browser text size
- Consistent scaling across devices and zoom levels
- Code maintainability and flexibility
- Use
min-height
instead of fixedheight
for viewport-height elements
- You do not need media query for this challenge and also remember in most of the times It's better to code mobile first.
Marked as helpful0 - @rohit7318Submitted 28 days agoP@kaamiikPosted 28 days ago
Hi. Some notes for your code:
HTML
- The address is a
p
tag not aspan
- For social links, use semantic list tags like
ul
andli
:
<!-- Use: --> <ul class="social-links"> <li><a href="#">GitHub</a></li> <li><a href="#">Frontend Mentor</a></li> <li><a href="#">LinkedIn</a></li> </ul>
This provides better semantics and accessibility for related links
- Never nest two interactive elements in each other.
- For decorative and avatar images, use empty alt text:
alt=""
- Avoid using words like image, picture, or photo in alt descriptions
CSS
- Start with a proper CSS reset - both Andy Bell and Josh Comeau provide excellent options
- Using a CSS reset helps ensure consistent styling across browsers
- Use
rem
units instead ofpx
for better accessibility and scaling:- Use
rem
formax-width
- This allows text and containers to scale with user's browser settings
- Learn more about unit best practices here
- Use
- Use
min-height: 100vh
instead ofheight: 100vh
to prevent overflow issues:
This ensures your container will expand if content exceeds viewport height.
0 - The address is a
- @JasonPBurkeSubmitted 29 days agoP@kaamiikPosted 28 days ago
First I strongly suggest get feedback on every challenge and refactor your code before you start a new challenge.
HTML Structure
- For decorative and avatar images, use empty alt text:
alt=""
- For the avatar image use the
img
tag in html. You don't need to usebackground
on CSS. header
is for repeatable contents like nav items and page logo on the top of your website that repeats in every page. You need to usep
here.- Your
h1
is ana
tag too. So inside theh1
wrap the text inide ana
tag too. You don't needtabindex
attribute here.
CSS Best Practices
- Start with a proper CSS reset (Andy Bell or Josh Comeau resets are recommended)
- Use viewport height properly: This ensures content can expand beyond viewport height
- Avoid fixed widths:
- Remove
width: 350px
from.card
- Use
max-width
for better text container adaptability
- Remove
- Use relative units:
rem
forfont-size
andmax-width
instead ofpx
- Learn more about this here
0 - For decorative and avatar images, use empty alt text:
- @shaheerahmedkhan11Submitted 29 days agoWhat are you most proud of, and what would you do differently next time?
I am proud that i successfully deployed my site and also wrote my first markdown file. I also improved my CSS skills. Next time I would like to push even harder and make my solution more efficient.
P@kaamiikPosted 29 days agoHello. Congratulations on completing this project. I think there was a misunderstanding in viewing the design images. The whole page should be light blue, and there's no need for the edges to be white. By the way, I have some notes for your code:
HTML Structure & Semantics
-
For your
h1
you need something like.visually-hidden
or.sr-only
class. This is good for screen readers and also not show it to the users. You can search on the internet to find the styles. -
Image descriptions should be meaningful and descriptive:
- Use alt text that explains the purpose:
alt="QR code to Frontend Mentor website"
- Avoid generic descriptions like "image" or "picture"
- Use alt text that explains the purpose:
-
The bold text needs to be
h2
because is a heading. -
The
.attribution
needs to be ap
tag because It contains a text andp
tag is the most proper tag here.
CSS Best Practices
-
Start with a proper CSS reset (Andy Bell or Josh Comeau recommended)
-
This ensures consistent styling across browsers
-
Avoid fixed dimensions for text containers:
Your
figure
contains text and you should not limit width and height. -
Do not use ID for css. Only use class. ID is suitable for JS and link two or more html tags together.
0 -
- @faruqshehuSubmitted 29 days agoWhat are you most proud of, and what would you do differently next time?
The fact that i'm getting better as days goes by, i will like to improve in java script and become better overall.
What challenges did you encounter, and how did you overcome them?adding a shadow to the blog post, i had to seek help to complete.
P@kaamiikPosted 29 days agoHi. I have some notes for your code:
HTML Structure
-
Use a proper title in your head of html like Blog Preview Card.
-
Add your fonts locally with
font-face
on CSS or withlink
tag on your html head. -
You need a proper HTML structure. After your
main
, first wrap all of your code into thediv
with something like.container
class and add abox-shadow
andmax-width
and other properties that is needed. You don't need a<div class="shadow"></div>
for shadow.
Text Elements and Semantics
- The
<h1>
has hover effect so you should wrap it inside aa
tag too. You can do it like this:<h1> <a>...</a> </h1>
CSS Best Practices
- Start with a proper CSS reset (Andy Bell or Josh Comeau resets are recommended)
- Avoid fixed widths:
- Remove
width: 400px
frommain
- Use
max-width
for better text container adaptability - Remove unnecessary
width: 100px;
and usepadding
instead
- Remove
- Use relative units:
rem
forfont-size
andmax-width
instead ofpx
- Learn more about this here
Marked as helpful0 -
- @big-hero-devSubmitted about 1 month agoWhat are you most proud of, and what would you do differently next time?
I completed the challenge as expected. Next time, I might explore more styling options.
P@kaamiikPosted about 1 month agoCongratulation for doing this challenge. Some notes for your code:
HTML Structure & Semantics
-
Image descriptions should be meaningful and descriptive:
- Use alt text that explains the purpose:
alt="QR code to Frontend Mentor website"
- Avoid generic descriptions like "image" or "picture"
- Use alt text that explains the purpose:
-
Follow proper heading hierarchy:
- Each page should have one
<h1>
- For components that are part of a larger page, use
<h2>
instead - This maintains proper document structure while reflecting component hierarchy
- Each page should have one
-
Keep HTML and CSS in separate files
CSS Best Practices
Reset & Base Styles
- Start with a proper CSS reset (Andy Bell or Josh Comeau recommended)
- This ensures consistent styling across browsers
CSS Units Best Practices
- Use relative units for better accessibility and scaling:
- Convert
font-size
andmax-width
values frompx
torem
- This allows text and layout to scale with user preferences
- Read more about unit best practices here
- Convert
Height Units Best Practices
- Use
min-height=: 100vh
instead of fixedheight
for viewport-height elements:
Image Handling
- Keep image styling minimal and responsive:
img { max-width: 100%; display: block; }
This ensures:
- Images scale properly
- No unwanted whitespace below images
- Content adapts to different screen sizes
- No need to wrap image in a div.
Marked as helpful1 -
- @x-147Submitted about 1 month agoWhat are you most proud of, and what would you do differently next time?
any feedback on css appreciated, thanks!
P@kaamiikPosted about 1 month agoYour HTML structure is good. Congrats! Some notes to improve your code:
HTML Structure & Semantics
- For single-component pages, use a minimal semantic structure:
<body> <main>...</main> </body>
This provides proper document outline while keeping markup minimal.
-
Image descriptions should be meaningful and descriptive:
- Use alt text that explains the purpose:
alt="QR code to Frontend Mentor website"
- Avoid generic descriptions like "image" or "picture"
- Use alt text that explains the purpose:
-
Follow proper heading hierarchy:
- Each page should have one
<h1>
- For components that are part of a larger page, use
<h2>
instead - This maintains proper document structure while reflecting component hierarchy
- Each page should have one
CSS Best Practices
Reset & Base Styles
- Start with a proper CSS reset (Andy Bell or Josh Comeau recommended)
- This ensures consistent styling across browsers
Modern Layout Techniques
- Center content using modern flexbox:
body { min-height: 100vh; display: flex; justify-content: center; align-items: center; padding: 1rem; }
Container Sizing
- Avoid fixed dimensions for text containers:
/* Instead of: */ .container { width: 280px; height: 390px; } /* Use: */ .container { max-width: 18.75rem; /* or appropriate rem value */ }
Image Handling
- Keep image styling minimal and responsive:
img { max-width: 100%; display: block; }
This ensures:
- Images scale properly
- No unwanted whitespace below images
- Content adapts to different screen sizes
Marked as helpful1 - @aayushduwalSubmitted about 1 month agoP@kaamiikPosted about 1 month ago
Some notes for your code:
- A proper page structure inside
<body>
should look like this:
<body> <header>...</header> <main>...</main> <footer>...</footer> </body>
Since this is a card component, we only need the
<main>
element.Images
- For decorative and avatar images, use empty alt text:
alt=""
- Avoid using words like image, picture, or photo in alt descriptions
- The address is a
p
tag not ah6
.
- For social links, use semantic list tags:
<!-- Instead of: --> <div class="social-links"> <a href="#">GitHub</a> <a href="#">Frontend Mentor</a> <a href="#">LinkedIn</a> </div> <!-- Use: --> <ul class="social-links"> <li><a href="#">GitHub</a></li> <li><a href="#">Frontend Mentor</a></li> <li><a href="#">LinkedIn</a></li> </ul>
This provides better semantics and accessibility for related links
CSS Reset
- Start with a proper CSS reset - both Andy Bell and Josh Comeau provide excellent options
- Using a CSS reset helps ensure consistent styling across browsers
- Use
min-height: 100vh
instead ofheight: 100vh
to prevent overflow issues:
This ensures your container will expand if content exceeds viewport height
Container Sizing
- Avoid fixed dimensions on text containers:
- Never set fixed
width
andheight
for elements containing text - Use
max-width
for better adaptability
/* Instead of: */ .container { width: 300px; height: 50px; } /* Use: */ .container { max-width: 18.75rem; }
This allows text to flow naturally and prevents content overflow issues:
- Text can wrap properly on smaller screens
- Content remains readable at different viewport sizes
- Container adapts to different text lengths and font sizes.
- Use
rem
units instead ofpx
for better accessibility and scaling:- Convert
font-size
values frompx
torem
- Use
rem
formax-width
and spacing values - This allows text and containers to scale with user's browser settings
- Learn more about unit best practices here
- Convert
Example:
/* Instead of: */ .text { font-size: 16px; } /* Use: */ .text { font-size: 1rem; }
0 - A proper page structure inside
- @SyedYeasin-CoderSubmitted about 1 month agoWhat are you most proud of, and what would you do differently next time?
Hello, everyone! This is my 3rd solution. This challenge was pretty easy but fun to do.
I would like to know if there's any way to improve my code. Thanks in advance :)
P@kaamiikPosted about 1 month agoHi. Your HTML is really good. I have some points for your CSS:
CSS Reset
- Start with a proper CSS reset - both Andy Bell and Josh Comeau provide excellent options
CSS Units
- Replace
px
units withrem
for better accessibility and maintainability:- Use
rem
forfont-size
instead ofpx
- Convert
max-width
values torem
units - Learn more about unit best practices here
- Use
Flexbox Properties
- Remove
align-content: center
as it has no effect in this flex context
Container Sizing
- Avoid fixed dimensions on text containers. You should not limit the text container:
/* Instead of: */ .bottom-container ul li { width: 300px; height: 3rem; } /* Use: */ .bottom-container { width: 100%; }
This allows content to adapt naturally while maintaining container boundaries
Marked as helpful1 - @Jaykins1Submitted about 1 month agoWhat specific areas of your project would you like help with?
All feedback are welcome.
P@kaamiikPosted about 1 month agoHTML Structure
- A proper page structure inside
<body>
should look like this:
<body> <header>...</header> <main>...</main> <footer>...</footer> </body>
Since this is a card component, we only need the
<main>
element.
Images
- For decorative and avatar images, use empty alt text:
alt=""
- Avoid using words like image, picture, or photo in alt descriptions
Text Elements and Semantics
- The "Learning" text should not be a
<button>
- it should be a<p>
tag since it has no interactive behavior - If it needs to be clickable/navigational, use an
<a>
tag instead - The
<h6>
text is incorrectly used - this should be a<p>
tag - The person name should also be a
<p>
tag
Interactive Elements
- Elements with hover effects are considered interactive
- If an element with hover effects navigates to a new page, wrap it in an
<a>
tag - If it triggers an action, wrap it in a
<button>
tag
Heading Hierarchy
- Do not skip heading levels (e.g. from
<h1>
to<h6>
) - Headings should follow a logical order:
<h1>
→<h2>
→<h3>
- Use CSS to adjust visual appearance if needed
CSS Best Practices
- Start with a proper CSS reset (Andy Bell or Josh Comeau resets are recommended)
- Avoid fixed widths:
- Remove
width: 350px
from.box
- Use
max-width
for better text container adaptability - Remove unnecessary
width: 20%
and usepadding
instead
- Remove
- Use relative units:
rem
forfont-size
andmax-width
instead ofpx
- Learn more about this here
Responsive Design
- Follow mobile-first approach:
- Start with mobile styles as the default
- Use
min-width
in media queries - Use
em
units for breakpoints
Example media query:
@media (min-width: 40em) { /* Desktop styles */ }
0 - A proper page structure inside
- @zahraabelluSubmitted about 1 month agoP@kaamiikPosted about 1 month ago
سلام. تبریک میگم بابت انجام این پروژه! کارتون خوبه، ولی چند نکته هست که میتونن به بهبود کدتون کمک کنن. نکات رو به انگلیسی مینویسم تا دقیقتر بیان بشن:
HTML Structure
- Form Structure: The structure of your HTML is crucial for this challenge. You should wrap the question and numbers inside a
<form>
tag, which includes a submit button. This ensures proper functionality and accessibility. - Fieldset and Legend: To group the question and numbers semantically, use
<fieldset>
and<legend>
. The question can be placed inside the<legend>
tag. This improves accessibility and structure. You can learn more about these elements on MDN. - Radio Buttons and Labels: The numbers should be a group of radio buttons, each with a corresponding
<label>
. This makes the interface more user-friendly and accessible. The current button implementation is incorrect and should be replaced.
Accessibility and Images
- Decorative Images: For decorative images, the
alt
attribute should be empty (alt=""
). This ensures screen readers skip over them, improving accessibility.
Fonts and Styling
- Font Importing: It’s recommended to host fonts locally or include them directly in your HTML. The current method of importing fonts isn’t ideal for performance and reliability.
- CSS Reset: Consider using a CSS reset at the beginning of your stylesheet. Both Andy Bell and Josh Comeau provide excellent CSS resets, which you can easily find online. This helps ensure consistent styling across different browsers.
Layout and Sizing
- Text Container Sizing: The use of
width: 25rem;
andheight: 24rem;
for text containers is incorrect. Instead, usemax-width
withrem
units to allow the content to flow naturally while maintaining a reasonable maximum size. - Button Sizing: For buttons, avoid fixed dimensions like
width: 50px; height: 50px;
. Instead, usepadding
to control the size, which makes the button more flexible and responsive. - General Width Usage: All instances of fixed
width
in your code are unnecessary. Replace them withmax-width
where needed, usingrem
units for better scalability.
Final Suggestion
I strongly recommend refactoring the code based on these suggestions before moving on to the next challenge. This will help you build a stronger foundation and improve the overall quality of your work.
Marked as helpful0 - Form Structure: The structure of your HTML is crucial for this challenge. You should wrap the question and numbers inside a
- P@VirginiaPatSubmitted about 1 month agoWhat are you most proud of, and what would you do differently next time?
I liked the fact that I had to change the grid for different screen sizes. I also added another break point between tablet and desktop screen and adjusted the layout accordingly. Next time I will try to use sass. I am still learning but I think it will make things much easier and cleaner.
What challenges did you encounter, and how did you overcome them?Trying to keep the dimensions analogy as shown in the figma file especially while changing the grid layout. Using grid-template-columns: auto; solved it.
What specific areas of your project would you like help with?Please any feedback will be much appreciated.
P@kaamiikPosted about 1 month agoHi. Some notes for your code:
- In each
.testimonial
, The person name can be ah2
tag as a heding.
- Also you have two blockquote. So you can structure like this:
And for your css you can add this too:<blockquote> <p>Bold text</p> <p>Regular text</p> </blockquote>
This CSS does not allow the " select when you wanna select the text with your mouse.blockquote > p.regular::before { content: "" "; } blockquote > p.regular::after { content: " ""; }
- Profile images do not need
alt
text. You can set it toalt=""
. Avoid using words like image, picture, or photo in alt descriptions.
- For your CSS, There is lots of files and honestly It's really hard for me to find the problems. I think If you are using vanilla CSS It's better to wrap all of your code in one file or two file.
- Generally from your preview I can say you only need a
max-width
on your section tag. You do not needmin-width
. And for your grid, You only need four columns and two rows and there is no need to define the rows height in your code. It's not true. Take this very simple and do not over complicate the code for your self.
Marked as helpful0 - In each
- @reemdalabSubmitted about 1 month agoP@kaamiikPosted about 1 month ago
Hi. Some notes for your code:
-
A proper page structure inside
<body>
should look like this:<body> <header>...</header> <main>...</main> <footer>...</footer> </body>
Depending on the design, you may not need a
<header>
or<footer>
, but a<main>
element is essential.
- Maintain a logical heading hierarchy; do not jump from
<h1>
to<h4>
. Headings should grow one by one (<h1>
→<h2>
→<h3>
), regardless of desired font size. Use CSS to adjust the visual appearance if needed. Here afterh1
you only needh2
but one of them has a different style.
- It's recommended to use a proper CSS reset at the beginning of your styles. Both Andy Bell and Josh Comeau provide excellent CSS resets, which you can easily find online.
- Your
font-size
andmax-width
should be inrem
units instead ofpx
. Read more about this here.
- Do not use percentage like
width: 50%;
because It allows the container grow. Just use amax-width
inrem
unit.
- In most cases try to style mobile first then go for the desktop. Also using fixed positioning is completely wrong. You do not need it.
- Work more on your styles.
0 -
- @timothyho512Submitted about 1 month agoWhat specific areas of your project would you like help with?
Would appreciate any feedback! Personally, I found sizing the most struggling thing. Especially getting the feeling of it. Thank you.
Also, how does that box-shadow works for this?
P@kaamiikPosted about 1 month agoSome notes for your code:
-
A proper page structure inside
<body>
should look like this:<body> <header>...</header> <main>...</main> <footer>...</footer> </body>
Depending on the design, you may not need a
<header>
or<footer>
, but a<main>
element is essential.
- A better alt text can be
QR Code to frontend mentor website
.
- Each page should have an
<h1>
heading. However, in some cases (like a QR code component), an<h2>
is more appropriate because is not a page and is a card only.
- It's recommended to use a proper CSS reset at the beginning of your styles. Both Andy Bell and Josh Comeau provide excellent CSS resets, which you can easily find online.
- Use
min-height: 100vh;
instead ofheight: 100vh;
to prevent overflow issues.
- You should not limit
width: 320px;
andheight: 499px;
for a text container. You only needmax-width
here.
- Your
font-size
andmax-width
should be inrem
units instead ofpx
. Read more about this here.
- You do not need these margins in your
h1
. Just add a padding to your.card
and that's enough.
Marked as helpful1 -
- @Mathieu-310Submitted about 1 month agoP@kaamiikPosted about 1 month ago
Some notes for your code:
- For each project only use one repo.
- Decorative images do not need alt and It should be like
alt=""
.
- This
<button>Learning</button>
is not abutton
. It's ap
tag because inside the design there is no hover effects for this but If you see this interactive you should usea
tag instead ofbutton
. Learn when to usea
and whenbutton
.
- Profile images also do not need
alt
text. Avoid using words like image, picture, or photo in alt descriptions.
- Your CSS code is really good.
Marked as helpful0