Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
10
Comments
10

brukmg

@brukmg230 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • Time tracking dashboard using HTML5, CSS3 and JavaScript


    brukmg•230
    Submitted 8 months ago

    1 comment
  • Newsletter sign-up form solution using HTML5, CSS3 and JavaScript


    brukmg•230
    Submitted 8 months ago

    2 comments
  • Article preview component solution using HTML5, CSS3 and JavaScript


    brukmg•230
    Submitted 9 months ago

    1 comment
  • Testimonial grid section using HTML5 and CSS3 grid


    brukmg•230
    Submitted 9 months ago

    1 comment
  • Four card feature section using HTML5 and CSS3


    brukmg•230
    Submitted 9 months ago

    1 comment
  • Product preview card component usinf HTML5 and CSS3


    brukmg•230
    Submitted 9 months ago

    1 comment
View more solutions

Latest comments

  • P
    nimrodEDE•270
    @nimrodEDE
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    Handling JavaScript ! , not watching any tutorial and figuring it out by my self ! :)

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

    Working with the Json Data was the most difficult challange so far. Used fetch .

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

    Help me write cleaner code ! Thanks (;

    time-tracking-dashboard-main

    2
    brukmg•230
    @brukmg
    Posted 8 months ago

    Hey, awesome job on using CSS variables! 🎉 It's great to see you applying them so well it makes your code cleaner and more maintainable. Keep up the good work, you're definitely getting the hang of this! Just a few small tweaks here and there, and you'll be on your way to writing even more efficient code. Well done!

    • It is best practice to put styles and script files in their own directory
    • Using semantic HTML elements(i.e Main, Section, Footer) is best practice For better SEO and readability.
    • alt attribute in image tag should not be empty. It is important for accessibility and SEO.
    • There is only one media query, how about the remaining screen sizes?
  • Jimmy Hoang•870
    @JimmyHoang296
    Submitted 8 months ago

    plain html css newsletter sign up

    1
    brukmg•230
    @brukmg
    Posted 8 months ago

    Just appreciating your job, no comment

  • Sherzod•330
    @SherzodToshpulatov
    Submitted 9 months ago
    What challenges did you encounter, and how did you overcome them?

    This first time using JS so I spent a lot of time.

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

    Any best practices for using JS.

    Article-preview-component. responsive. mobile first workflow.

    1
    brukmg•230
    @brukmg
    Posted 9 months ago

    Hey good work, you're definitely getting the hang of this! Just a few small tweaks here and there, and you'll be on your way to writing even more efficient code. Well done!

    • There are hard-coded colors in your code. Using variables for colors is best practice. Maintainability and readability will be improved
    • Instead of using section as the main container, it would be more semantic to use main tag.
    • You did well on the share bubble but you forgot the bubble arrow
    Marked as helpful
  • Extendo99•110
    @Extendo99
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    I am proud of the use of grid area, which makes the layout responsive and looks great.

    Next time when designing a grid I will start with grid area, which makes the layout faster

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

    I had a problem with the grid but after reading a few guides I discovered the grid area feature which makes the cards look even and nice

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

    I'm asking for general advice on design, code readability, and responsiveness.

    Testimonials Grid

    1
    brukmg•230
    @brukmg
    Posted 9 months ago

    Hey, awesome job on using CSS variables! 🎉 It's great to see you applying them so well it makes your code cleaner and more maintainable. Keep up the good work, you're definitely getting the hang of this! Just a few small tweaks here and there, and you'll be on your way to writing even more efficient code. Well done!

    • Starting with the folder structure, it would be better to place styles.css in its own folder.
    • Focusing on semantic elements like main and footer improves your site’s readability, accessibility, and SEO-friendliness.
    • It's not necessary select elements picture, video, canvas, svg, input, button, textarea, select, h2, h3, h4, h5 and h6 there are no such elements.
    • Only one media query is implemented. What about the other screen sizes?
    Marked as helpful
  • P
    İsmail Hasır•120
    @ismailhasir
    Submitted 9 months ago

    Four Card Feature Section

    2
    brukmg•230
    @brukmg
    Posted 9 months ago

    Hey, awesome job on using CSS variables! It's great to see you applying them so well it makes your code cleaner and more maintainable. Keep up the good work, you're definitely getting the hang of this! Just a few small tweaks here and there, and you'll be on your way to writing even more efficient code. Well done!

    • Starting with the folder structure, it would be better to place styles.css in its own folder.
    • Focusing on semantic elements like header, main, and footer improves your site’s readability, accessibility, and SEO-friendliness.
    • There's no need to set a width for the body element since it fills the viewport by default.
    • The color #f2f2f2 is being used as the background-color, but it's not part of the design.
    • There are redundant styles for the card’s top border; you could use border-top: 3px solid in .card and apply a different color for each card.
    • For better visual impact, increase the blur of the card shadow.
    • Only one media query is implemented. What about the other screen sizes?
  • Ejiro Frances•390
    @Ejiro-Frances
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    I am most proud of the responsiveness of the page.

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

    One of the challenges I encountered was the difference in the mobile view and desktop view images. I used the visibility:hidden property to switch the images between screen sizes.

    Another challenge was getting the image to fit within the image-container. I used em units and this worked.

    Another challenge I faced was adjusting the width of the desktop view.

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

    I would like feedback on best practices to achieve responsiveness on this component.

    Product Preview Card Component

    1
    brukmg•230
    @brukmg
    Posted 9 months ago

    You’ve done a great job! I love that you used semantic HTML elements it’s awesome for both readability and SEO optimization.

    In the HTML section, the main element is used as a card, but there should be an additional div to act as the product container. For images, it's better to use a single img element and apply styling for various screen sizes as needed. Also, the 'Add to cart' element should be a button, not a div. Additionally, it would be more appropriate to wrap the container div with the class attribution in a footer element.

    For CSS, using 62% for the font size is too large, it’s recommended to use units like px for better control. The property display: flex on the body element is unnecessary. Instead, apply flex to the main element if you're centering the product card. To make the code more maintainable, consider using CSS variables for colors instead of hard coding them multiple times, which will make updates easier. Lastly, you've only implemented a media query for one screen size, but it would enhance responsiveness if you added queries for screen sizes like 768px, 1024px, 1140px, and more.

    Lastly, it's not best practice to place the CSS file in the assets folder, as it's a core part of your web app's program files and not just an asset.

View more comments
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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub