Latest solutions
- Submitted about 2 months ago
Responsive Social Links Profile with Semantic HTML, SCSS, and Dynamic
- HTML
- CSS
- Accessibility Enhancements: Are there additional best practices or tools I could use to ensure the project is fully accessible, especially for users relying on screen readers or keyboard navigation?
- SCSS Organization and Scalability: While the SCSS code is modular, I would appreciate suggestions on further optimizing its structure and improving scalability for larger projects. Are there any specific methodologies (e.g., BEM, ITCSS) that might be useful here?
- Reusable JavaScript Components: Feedback on the structure and maintainability of the dynamic button component would be highly valuable. Are there any techniques or patterns that would make the component more robust and scalable for future extensions?
- Submitted about 2 months ago
Responsive Blog Preview Card using Sass and Semantic HTML
#accessibility#sass/scss#semantic-ui- HTML
- CSS
- Feedback on the organization and readability of the Sass structure.
- Suggestions on improving hover/focus state accessibility.
- Recommendations for optimizing the responsive design further, especially for smaller screens.
- Submitted 2 months ago
QR Code Component Solution using SCSS and Responsive Design
#accessibility#sass/scss#semantic-ui- HTML
- CSS
I would appreciate feedback on how I could further optimize my SCSS structure or improve accessibility for users. Any suggestions for making the layout more adaptive or enhancing the hover effects would also be helpful.
- Submitted 2 months ago
Responsive Contact Form using SCSS and Vanilla JavaScript
#accessibility#sass/scss#semantic-ui- HTML
- CSS
- JS
I would like feedback on:
- Improving accessibility for the form (e.g., proper use of ARIA attributes).
- Optimizing the SCSS structure for better scalability and maintainability.
- Following best practices for JavaScript validation and event handling.
Latest comments
- @kamilkoziol5Submitted about 2 months ago@GeorgePapalazaridisPosted about 2 months ago
Hello mate!
First off, great job on completing the Social Links Profile project! Your implementation shows a strong understanding of CSS basics and styling techniques. I really appreciate the effort you’ve put into achieving a responsive and visually appealing design. Here are some of my thoughts and suggestions that might help refine your project further:
What I Liked:
-
Effort in Making the Layout Responsive: While there are some minor issues with scrollbars on smaller screens, the overall effort to include media queries and adapt the layout for different viewports shows a clear understanding of responsive design principles.
-
Use of Variables: Leveraging CSS custom properties (
--green
,--grey700
, etc.) for consistent colors across the design is excellent for maintainability. -
General Layout Alignment: The overall height and structure of the layout are close to the challenge's prototype, showing a good attempt at replicating the design.
-
Simplified Approach: The codebase reflects a straightforward approach to styling and layout, which can be beneficial for easier debugging and maintenance.
Suggestions for Improvement:
HTML:
-
Semantic Tags:
- Using semantic tags like
<header>
,<section>
, and<footer>
instead of generic<div>
elements can improve accessibility and structure. For example, the social links could be wrapped in a<section>
with an appropriate heading. - Consider adding an
<h1>
andh2
elements for the main title of the card and the content for better semantic hierarchy.
Example:
<section class="social-container"> <h2 class="visually-hidden">Social Media Links</h2> <div class="social">GitHub</div> <div class="social">Frontend Mentor</div> <!-- more links --> </section>
- Using semantic tags like
-
Alt Attribute on Image: The alt text
Jessica Avatar Photography
could better describe the image. For example, "Profile picture of Jessica Randall" might be more appropriate.
CSS:
-
Border Radius and Dimensions for Profile Image:
- The profile image uses
border-radius: 100%;
, which works but might not always render perfectly. Usingborder-radius: 50%;
is the standard for circular images and ensures a consistent look across browsers. - Additionally, the image dimensions are slightly off compared to the Figma design (88px by 88px). Updating the width and height to match the design specification would improve the layout's fidelity to the challenge prototype.
- The profile image uses
-
Padding Between Elements:
- The spacing between elements like the image, title, and social links could be fine-tuned to match the prototype better. For example, the padding/margin between the image and the title feels slightly tight.
-
Button Height:
- The height of the social buttons looks slightly larger than expected. Adjusting the padding or setting a consistent
min-height
(e.g.,2.82rem
or40px
) could help.
- The height of the social buttons looks slightly larger than expected. Adjusting the padding or setting a consistent
-
Flexbox Layout for Social Links:
- While the vertical stack for the social buttons works, exploring
gap
usage within a<ul>
element and leveraging<li>
for individual links could enhance structure and styling flexibility.
- While the vertical stack for the social buttons works, exploring
General Observations:
- Layout Alignment:
- The height of the layout is close to the challenge’s prototype, but there’s some room for improvement in aligning the paddings and spacing between elements to closely match the design.
Overall Feedback:
You’ve done a great job of tackling the key requirements of the challenge. The project is responsive, visually consistent, and demonstrates your understanding of CSS. With a few adjustments, such as improving semantic structure, fine-tuning spacing, and aligning closer to the prototype, this project could be even stronger.
Keep up the fantastic work! 😊
Best regards,
GP0 -
- @GeorgeValentinSubmitted 8 months ago@GeorgePapalazaridisPosted about 2 months ago
Hi George,
Amazing job on completing the Blog Preview Card Component Challenge! I can see the effort and thought you’ve put into this project, and it really shows. Here's some feedback to help you fine-tune your work even further:
What I Loved:
-
File Organization:
- Your file structure is clean and well-organized. Using SCSS partials for globals and reusables demonstrates great foresight—it shows you're thinking about scalability and maintainability.
-
Responsive Design:
- The responsiveness works beautifully! The way the layout adjusts at different breakpoints feels smooth, and you’ve handled font scaling and padding changes thoughtfully.
- I particularly like how you’ve maintained a consistent design from mobile to desktop without losing balance.
-
Challenge Requirements:
- You’ve implemented the challenge prerequisites, like using the Figtree font,
box-shadow
, andborder-radius
, in a way that feels seamless and enhances the design. Even though these were requirements, you executed them with care, making the card visually appealing.
- You’ve implemented the challenge prerequisites, like using the Figtree font,
Suggestions for Improvement:
-
Accessibility:
- While the project is mostly accessible, the
alt
attributes on your images could be more descriptive. For example:
This small tweak ensures better support for screen readers and improves inclusivity.<img class="header-container_img" src="./assets/images/illustration-article.svg" alt="Illustration about HTML and CSS foundations" />
- While the project is mostly accessible, the
-
Semantic HTML:
-
The
div
wrapping the entire blog card (blog-preview-card
) could be replaced with a more meaningful semantic tag like<article>
or<main>
to better reflect the content’s purpose. For example:<main class="blog-preview-card"> ... </main>
Using semantic tags helps screen readers and improves overall code readability.
-
Additionally, using a
<button>
or<span>
instead of adiv
for the "Learning" section would enhance semantics. If this element is interactive, a<button>
would be more appropriate.
-
-
CSS Optimization:
- Switching from fixed units like
px
to relative units likerem
orem
could improve scalability. For example:
This will make your design even more adaptable to user settings.font-size: 1.25rem; /* instead of font-size: 20px */
- Switching from fixed units like
-
Footer Styling:
- Currently, the
footer-container
is positioned absolutely at the bottom, which might cause layout issues if the content grows taller than expected. You could try usingflexbox
on the parent container to create a more flexible layout. Something like this:.blog-preview-card { display: flex; flex-direction: column; min-height: 100vh; justify-content: space-between; }
- Currently, the
-
Mobile-first Approach:
- While your breakpoints are solid, starting with mobile-first styles and adding larger breakpoints as you go would make your CSS more efficient and easier to manage.
Final Thoughts:
You’ve done an outstanding job! The design is clean, responsive, and visually appealing. The SCSS structure makes it easy to maintain and extend, and your work on responsiveness is commendable.
With just a few tweaks—like enhancing accessibility, improving semantic structure, and refining footer behavior—you’ll have a truly polished solution. Keep up the great work, and I’m excited to see more of your projects in the future!
Best regards,
GP0 -
- @emmaezeiruSubmitted 4 months ago@GeorgePapalazaridisPosted 2 months ago
Great job on your solution! 👏 I really like how clean and well-structured your HTML and CSS are. The layout is simple yet effective, and your use of Flexbox to center the content vertically works perfectly for responsiveness.
Things I Liked:
- Semantic HTML: The use of
<h2>
for the title and<p>
for the description is excellent for maintaining a semantic and accessible structure. 👍 - Design Accuracy: The overall design looks very close to the challenge's original design, especially with the proper use of colors and rounded corners.
- Flexbox Centering: The way you used
display: flex
in the body to align items vertically and horizontally is a great choice for responsiveness.
Suggestions for Improvement:
- Alt Attribute: Consider making the
alt
text for the QR code image more descriptive. For example, "QR code linking to Frontend Mentor website" would be more helpful for screen readers. - Box Sizing: Adding
box-sizing: border-box
in your universal selector (* {}
) could improve CSS consistency by including padding and borders in element sizes. - Line Height: Adding a
line-height
to the<p>
text would make it more readable, especially for smaller screens.text p { line-height: 1.5; }
- Viewport Padding: While the design looks good on small and medium screens, consider adding some padding to the body or container to ensure the card doesn’t touch the screen edges on very small devices.
Accessibility Note:
To enhance accessibility, you could use ARIA roles or landmarks to help screen readers navigate the page. For example, wrapping the card in a
<main>
tag instead of a<div>
could be a good improvement.
Overall, this is a strong and well-executed solution. With just a few tweaks, it could become even better. Keep up the great work and happy coding! 🚀 😊
0 - Semantic HTML: The use of