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

Abhijit Sarode

@AbhijitSarodeIndia90 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

  • Built using Component Design System


    Abhijit Sarode•90
    Submitted over 3 years ago

    1 comment
  • Order Summary Component - Using Flex Box


    Abhijit Sarode•90
    Submitted over 3 years ago

    1 comment
  • Finally finished Profile Card Component


    Abhijit Sarode•90
    Submitted over 4 years ago

    2 comments

Latest comments

  • Nicolas Eiriz•50
    @NicolasEiriz
    Submitted over 3 years ago

    html css

    1
    Abhijit Sarode•90
    @AbhijitSarode
    Posted over 3 years ago

    Hi Nicolas,

    Your code looks pretty good for your very first submission.

    <header> and <footer> tags are usually used for header and footer of the page not the component as it may create confusion if someone is using accessibility settings

    You can use responsive measuring units like rem, em, vh, vm, ch etc instead of px but be aware of the additive nature of some of the responsive units

    I'll suggest you look into BEM for future submissions. Plenty of people here use good BEM, you can read their code to get better idea about it

    Hope this helps

    Marked as helpful
  • Farzeen Kistnareddy•60
    @FarzeenKist
    Submitted over 3 years ago

    Stats Preview Card Using Utility Classes and semantic HTML

    1
    Abhijit Sarode•90
    @AbhijitSarode
    Posted over 3 years ago

    Hi Farzeen,

    Your code seems well written but since there is just one component I think <main> would suffice instead of <article>

    You are already using global variables for colors so instead of just mentioning the values of colors you can mention them as hsl, RGB or hex colors, It becomes little easier to use especially when intellisense doesn't work as expected

    When it comes to setting values for three different scenarios(or screen sizes) I think 'clamp()' gets the job done that way you don't have to mention it separately in media query

    Btw you have <body> tag declared at two different places, I don't think it's a good practice to redeclare <body> tag so do look into it.

    Instead of using precise percentage on width you can use 'calc()' and let CSS do the calculation work for you

    Hope this helps

  • ِAbdullah•730
    @9dorgham
    Submitted over 3 years ago

    four-card-feature-section-master

    1
    Abhijit Sarode•90
    @AbhijitSarode
    Posted over 3 years ago

    Hi Abdullah,

    Your code seems to be well written, but I would suggest 'grid-template-areas' to layout elements in your grid.

    While using measurement units go for responsive units like rem, em, %, vh, vw, ch etc instead of px or pt but be aware of the additive nature of some responsive units.

    It's a personal choice but when using colors you can opt for global root variables so that in future if you ever need to change color then it becomes very easy to do so.

    Try to be specific when it comes to images 'alt' descriptions

    Hope this helps

    Marked as helpful
  • Aneta•180
    @anetaanette
    Submitted over 3 years ago

    Profile Card Component

    #accessibility#sass/scss
    4
    Abhijit Sarode•90
    @AbhijitSarode
    Posted over 3 years ago

    Hey Aneta 👋

    As Maqsud mentioned above its hard to utilise full power of BEM in small projects nonetheless code is well written. I'll suggest more use of the responsive measurement units (e.g rem, vh, vw, ch, %, em etc but also be aware of its additive properties). You can also use functions like minmax(), max-width(), min-width(), clamp(). One more thing, you can use resets in your projects as it makes life easier in the end. You can read more about resets here https://piccalil.li/blog/a-modern-css-reset

    Hope this helps Abhijit

    Marked as helpful
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