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

Orlando Guevara

@coding-tomatoVenezuela220 points

A bit of an empirical loser. Web developer/game developer.

Latest solutions

  • Mobile first, response, Flex, no libraries


    Orlando Guevara•220
    Submitted almost 3 years ago

    0 comments
  • HTML and CSS using BEM and Flex


    Orlando Guevara•220
    Submitted about 3 years ago

    0 comments
  • Testimonials Grid Section - Vanilla HTML and CSS


    Orlando Guevara•220
    Submitted almost 4 years ago

    0 comments
  • Social Proof Section - Vanilla HTML and CSS


    Orlando Guevara•220
    Submitted almost 4 years ago

    0 comments
  • Four card feature section - Vanilla HTML and CSS


    Orlando Guevara•220
    Submitted almost 4 years ago

    1 comment
  • 3 Column preview card component - Vanilla CSS and HTML


    Orlando Guevara•220
    Submitted almost 4 years ago

    2 comments

Latest comments

  • Mostafa Karem•80
    @Mostafa-Alfiky
    Submitted almost 3 years ago

    QR Code component

    3
    Orlando Guevara•220
    @coding-tomato
    Posted almost 3 years ago

    Hello!

    Regarding your question about tips to write clear code, I highly recommend to study the BEM convention to write CSS. Can't state how much more predictable, debuggable and reusable my code now is thanks to it.

    https://css-tricks.com/bem-101/

    The concepts to implement it are rather simple and although they increase boilerplate due to more classes being created (which can be reduced with a preprocessor such as Sass), I found the benefits to outweigh any cons it might have.

  • Benjamin Mancuello•40
    @Mancux2premium
    Submitted almost 3 years ago

    utilice HTML y CSS base.

    #cube-css
    3
    Orlando Guevara•220
    @coding-tomato
    Posted almost 3 years ago

    I think the HTML is fine! Good work.

    Seems like the font-weight for the description is off. Other than that it looks good!

    If you wished to work further on it, you could add some responsiveness by making the width of the card have a max-width and a min-width, and have the width be 100%, so it stretched a bit depending of the phone's screen width.

    {
        min-width: 200px;
        width: 100%;
        max-width: 300px;
    }
    

    A similar approach would be to instead use clamp, to clamp the width between a set of values:

    {
        width: clamp(200px, 100%, 300px);
    }
    

    To make these changes effective you'd need to make some adjustments on the padding of the card, among other things.

    Marked as helpful
  • Kipo•80
    @rezokip
    Submitted almost 3 years ago

    social-proof-section-master

    1
    Orlando Guevara•220
    @coding-tomato
    Posted almost 3 years ago

    Hello! If you have trouble organizing your CSS to be more readable, I highly recommend to learn about BEM.

    It's a way to structure CSS code in a way that's more predictable, readable and contained.

    Reference: https://css-tricks.com/bem-101/

    Marked as helpful
  • Renan Costa•70
    @RenanCosta2
    Submitted almost 3 years ago

    Expenses chart component

    1
    Orlando Guevara•220
    @coding-tomato
    Posted almost 3 years ago

    Hello! Good work, I structure the HTML in a very similar way.

    Thinking of making it responsive? To adjust for the mobile view.

  • Kipo•80
    @rezokip
    Submitted almost 3 years ago

    3-column-preview-card-component-main

    1
    Orlando Guevara•220
    @coding-tomato
    Posted almost 3 years ago

    Hey! I was fiddling a bit with your website to add the clamp functionality you desired.

    I added a little bit of padding in the body tag so the component wouldn't crash against the edges.

    body {
      display: grid;
      place-content: center;
      min-height: 100vh;
      padding: 2rem;
    }
    

    And of course, I made the main container's width responsive by adding clamp to its width. I used the values shown as an example.

    main {
        width: clamp(920px, 100%, 1200px);
        display: flex;
    }
    

    You can set something lower like 500px but you'd need to adjust the media query too.

    Now, this breaks the site, because now everything is aligned to the left, but you just need to center items in the X axis by adding:

    main {
        width: clamp(920px, 100%, 1200px);
        display: flex;
        justify-self: center;
    }
    

    Overall very good work! Making things responsive can be tricky, as you can very easily break other elements.

    Marked as helpful
  • Aung Khant Hein•80
    @AungKhantHein314
    Submitted almost 3 years ago

    Expenses chart component

    3
    Orlando Guevara•220
    @coding-tomato
    Posted almost 3 years ago

    Hello!

    Maybe instead of using media queries for different pixel sizes, you could use this line of code

    width: clamp(375px, 100%, 450px)
    

    There would need to be some adjustment, but it could help you reduce boilerplate code.

    Marked as helpful
View more comments

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