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

Rodrigo Cont Joviano dos Santos

@CjsrodrigoSão Paulo100 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

  • Testimonials grid section


    Rodrigo Cont Joviano dos Santos•100
    Submitted 9 months ago

    On large screens, I faced some problems with the grid, where the card components did not occupy the whole conteiner, resulting on a different solution than expected with the challenge. Probably have to learn some grid techniques/properties.

    Thanks! :)


    1 comment
  • Four card feature section


    Rodrigo Cont Joviano dos Santos•100
    Submitted 9 months ago

    Any feedbacks are welcome


    1 comment
  • Product preview card component solution


    Rodrigo Cont Joviano dos Santos•100
    Submitted about 1 year ago

    I'd like to know If spacing between texts look good compared to the original design, wasn't able to make spacing a little smaller. Also a feedback on code quality is always welcome. Thanks.


    1 comment
  • Recipe page


    Rodrigo Cont Joviano dos Santos•100
    Submitted about 1 year ago

    I would like some help to understand how to stretch the text on my solution, to make it look like the proposed design. Font size/weight looked correct, and using the font-stretch didn't solve the problem. Also, a feedback on code quality would be appreciated! :) Thanks.


    1 comment
  • Social links profile - custom


    Rodrigo Cont Joviano dos Santos•100
    Submitted about 1 year ago

    Element positioning, the spacing between the phrases bothered me and i couldn't find a solution without every element changing position. Social links positioning are fine for me.


    1 comment
  • Blog Preview Card


    Rodrigo Cont Joviano dos Santos•100
    Submitted about 1 year ago

    Still need to improve my learning on making apps for different screen sizes.


    1 comment
View more solutions

Latest comments

  • P
    Michel•80
    @michelcub
    Submitted 9 months ago

    testimonial section

    2
    Rodrigo Cont Joviano dos Santos•100
    @Cjsrodrigo
    Posted 9 months ago

    Hi, Michel!

    That's a great job you did! Solution looks almost identical to the design.

    keep it up!

  • Favio Contreras•260
    @Fulgore33
    Submitted 11 months ago

    Owner avatar four-card-feature-section-master

    1
    Rodrigo Cont Joviano dos Santos•100
    @Cjsrodrigo
    Posted 9 months ago

    Hi,

    Design looks accurate in comparison to the desing, despite the difference in elements proportions. Try looking for the right attributes when structuring your HTML, that probably would bring another outcome to the solution. Maybe would help with texts being in the same line. Great one!

  • Daniel999l•100
    @Daniel999l
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    I developed it from just a screenshot. I'm proud of myself for that.

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

    Widths, height, font sizes are my main challenge. It's obviously due to the lack of figma desgn link.

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

    A figma design file link would really help a lot.

    Responsive card layout

    1
    Rodrigo Cont Joviano dos Santos•100
    @Cjsrodrigo
    Posted about 1 year ago

    Design looks amazing! As of the problem with the lack of the Figma design. Try not to stick with the use of pixel. using em/rem, makes everything work in proportion (and also helps a lot working with responsive layouts) Great job, keep it up!

  • ibnu-jemal•150
    @ibnu-jemal
    Submitted about 1 year ago

    Responsive solution updated last

    1
    Rodrigo Cont Joviano dos Santos•100
    @Cjsrodrigo
    Posted about 1 year ago

    Nice work on completing the challenge!

    Design looks good, try using better suitable elements for certain situations. On the nutrition facts, maybe using a <table></table> element would make it look better and would make it less hard coded. Too many divs will make it harder for you to understand you code and to apply css to it! Great job!

    Marked as helpful
  • Niloy Das•230
    @NiloyDas07
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    This one was pretty simple.

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

    I was pretty smooth.

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

    Nothing particular in this one. Any feedback is appreciated.

    Responsive Page

    2
    Rodrigo Cont Joviano dos Santos•100
    @Cjsrodrigo
    Posted about 1 year ago

    Solution looks perfectly matching the design suggest on the challenge. Congratulation and keep it up!

  • Gianfranco Bordon•30
    @GianBordon
    Submitted about 1 year ago

    Blog Preview Card

    1
    Rodrigo Cont Joviano dos Santos•100
    @Cjsrodrigo
    Posted about 1 year ago

    Solution is looking good, every attribute is where it should be. Just some minor design details would get it to 100% match, but I guess what's more important is that you could get to this solution by yourself. Keep it up!

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