Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
7
Comments
8
P
Vladimir Damnjanovic
@dovlicio

All comments

  • Lucas Cerri•1,160
    @llKryptonixll
    Submitted over 1 year ago

    Grid Testimonials | HTML | CSS

    #bem
    1
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 4 months ago

    Hi, great work! Congratz

    I suggest adding README.md and editing the template accordingly to describe your solution.

    On mobile screen I found that for some reason spacing in the second testimonial card is not correct, also on mobile, quote icon should be hidden.

    Marked as helpful
  • Mawel Abellana•140
    @maomaoXD
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    I used the BEM methodology and sass architecture.

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

    I used the mobile first approach it's easy to use this in the layout

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

    I'll try to code this using react.

    Mobile first approach w/ SASS folder structure, BEM and Accessibility

    #accessibility#bem#sass/scss
    1
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 4 months ago

    Great job! I can already see by your code that you have more experience than me in web dev. :)

    Looking forward to learn more from your code, your design is responsive, looks good on all screen sizes.

    I would only suggest fixing your README.md file on github as you should edit your readme.md and delete the template file.

    Marked as helpful
  • Olexii Bulhakov•320
    @bulhakovolexii
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    While working on this task, I didn’t encounter any significant difficulties. I decided to use the Sass preprocessor, just like in my previous project, to simplify styling with variables and mixins. However, this time, I moved all the additional code into a separate file, _system.scss.

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

    The only part where I had to refer to the documentation and seek help from Google was transitions. Now I’ll try to remember that the following code won’t work:

    .links__item {
      a {
        transition: background-color color 0.2s ease-in;
        // For some reason, I thought I could list all the
        // properties to apply the animation to.
      }
    }
    

    The correct approach is:

    .links__item {
      a {
        transition: background-color 0.2s ease-in, color 0.2s ease-in;
      }
    }
    
    What specific areas of your project would you like help with?

    I haven’t worked much with animations before, so they haven’t stuck in my memory very well. Hopefully, I’ll have more opportunities to practice in future projects.

    Social links profile

    #sass/scss#bem
    1
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 4 months ago

    Hi, great job! You did excelent work.

    For transition property in your case you could also do something like this:

    transition: all 0.2s

    Marked as helpful
  • uptown_girl•480
    @uptowngirl757
    Submitted 4 months ago

    Product preview card using SCSS

    1
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 4 months ago

    Really interesting solution, I like it :) You did a great job, I never used sass or less yet, BEM convention tho I know, very good! Just one thing I have noticed according to style we got, we should have bold new price and for bigger screens maybe add some more padding around product content but all in all great job and a lot can be learned from your code, thank you!

  • Amar Shrestha•50
    @Sthamar
    Submitted 4 months ago

    recipe page

    1
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 4 months ago

    Hi, congratz, good job:) Pay attention to font sizes for all screens and also there is some bug for smaller screens, your content is cutoff and have scroll, just a little fix and you're good :)

  • VikVas28•30
    @VikVas28
    Submitted 4 months ago

    Social Links Profile

    2
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 4 months ago

    Hi, I like transition effect on hover, totally forgot about it for my solution :) One thing I see is that your design breaks for smaller screens (mobile), so you should work on it and fix it, for bigger screens you did a great job.

  • givanim•100
    @givanim
    Submitted 4 months ago

    Blog preview page

    1
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 4 months ago

    Hello, great job, I think the card looks great. Me personally, I like to change font size for different screens but that's just me :) Learning something from your code, maybe a little bit more semantic HTML and just to fix README.md, you should replace it with edited template. Great work, keep it up. :)

  • P
    Chris•115
    @CKHarrison
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I have been primarily working on back-end hardware facing development using C# and other technologies in my day job for the past two years, so I'm a bit rusty on my fullstack skills, especially my Front-End CSS development. I plan on using Front End Mentor as a way to sharpen my skills back up to the level they were at around two years ago. I used this challenge as a way to work on mobile-first development. Funnily enough, I encountered the same problem I always used to have, how to center the content in the middle of the page! Please let me know about anything you think that could be improved, I'm here to get better, so your feedback is welcome!

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

    Centering the content within the body, I once again had forgotten exactly how to do that, and had to do some research on how to do it. Centering content has always been my nemesis!

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

    Like I have said previously, I'm coming back to Front End Development after a while and am a bit rusty. Any feedback on the problems with the CSS that you see, or any better ways to structure my CSS or content would be greatly appreciated.

    QR Code Solution

    1
    P
    Vladimir Damnjanovic•160
    @dovlicio
    Posted 5 months ago

    Hi there, great work! A few things I would suggest: your card container should not be <main> because the <main> should contain the main content of the page. Since we are building just a card component, you could use <main><div class="card-container"></div></main>. That means your card component should be inside the main area of the page.

    Also, you did a great job centering the items in the body—that's exactly how you do it! Setting the height to 100vh and aligning items horizontally and vertically using display: flex is the right approach.

    One property that isn’t necessary is flex-direction because you only have one element in your <body>, which is the <main> element. :)

    Marked as helpful

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