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

SuiteMel

@SuiteMelUnited States of America170 points

Looking to find joy in coding again. 5 years work experience. 12 years CSS experience.

I’m currently learning...

Svelte and accessibility

Latest solutions

  • Meet Landing Page w/ Tailwind & Svelte

    #tailwind-css#svelte

    P
    SuiteMel•170
    Submitted about 2 months ago

    None really unless something in my work doesn't match the design.


    1 comment
  • Four card feature section w/ Tailwind CSS & Svelte

    #tailwind-css#svelte

    P
    SuiteMel•170
    Submitted 7 months ago

    1 comment
  • Product preview card w/ Tailwind CSS & Svelte

    #tailwind-css#svelte

    P
    SuiteMel•170
    Submitted 7 months ago

    1 comment
  • Recipe page w/ Tailwind CSS and Svelte

    #tailwind-css#svelte

    P
    SuiteMel•170
    Submitted 7 months ago

    Would you write the markup with different semantic html? Is this page sufficiently accessible with the markup currently in place? These are the things I wonder sometimes.


    0 comments
  • Blog Preview Card w/ Tailwind & Svelte

    #tailwind-css#svelte

    P
    SuiteMel•170
    Submitted 7 months ago

    The best way to create a semantically accessible blog card. There are a lot of opinions on how to create cards that are links and make them accessible on screen readers and for various types of users, but I haven't figured out a solution I am happy with that keeps everything working.


    0 comments
  • Stats Preview Card w/ Svelte and Tailwind CSS

    #tailwind-css#svelte

    P
    SuiteMel•170
    Submitted 7 months ago

    0 comments
View more solutions

Latest comments

  • P
    Restu•700
    @masrestu
    Submitted about 2 months ago

    Meet Landing Page

    #tailwind-css
    1
    P
    SuiteMel•170
    @SuiteMel
    Posted about 2 months ago

    Nice touch with the transitions on the hero photos as you resize the page.

  • darkweb•210
    @darkweb907
    Submitted over 3 years ago

    responsive design made using css grid

    #bootstrap#materialize-css#sass/scss#svelte#tailwind-css
    1
    P
    SuiteMel•170
    @SuiteMel
    Posted 6 months ago

    You matched the styles well I think. But I think the background color is wrong. And I'd recommend setting a max width to match the design so the cards don't stretch out as much. Otherwise, good job.

  • Flávia Reis•690
    @flaviare1s
    Submitted over 1 year ago

    Responsive page using Tailwind

    #tailwind-css
    1
    P
    SuiteMel•170
    @SuiteMel
    Posted 7 months ago

    You did a really good job matching design. It was difficult to find anything to recommend improving.

    I did find one thing was related to responsiveness, and that was that as you make the screen smaller the boxes kind of run into each other. Maybe instead of setting a width you set a max-width so that the card can shrink when they run out space? The newer aspect-ratio utility can also help with maintaining their shape as well if that's a concern as the cards potentially get smaller.

  • Edems•20
    @Edems-DEV
    Submitted about 2 years ago

    Product card build using Taiwind and Svelte-kit

    #svelte#tailwind-css
    1
    P
    SuiteMel•170
    @SuiteMel
    Posted 7 months ago

    You did a good job trying to match the layout from the images alone. But, I would highly encourage working on matching colors using a color picker or utilizing colors from the style guide if you aren't sure what the correct color is. Same goes for the font families as well, I believe the style guide in the starter linked to those. Good luck on your CSS journey otherwise!

  • Piêtro Braga Aquino Júnior•100
    @pietroBragaAquinoJunior
    Submitted 10 months ago

    Mentor Recipe Page made with sidebase nuxtjs3 tailwindcss

    #nuxt#tailwind-css#vue
    1
    P
    SuiteMel•170
    @SuiteMel
    Posted 7 months ago

    It looks like this an older project, and when I look at your newer projects I can see you improved your css skills. My biggest critique here and in your other projects is the usage of h1's being on the page multiple times. h1 tags should only be on the page once except in very specific circumstances. With multiple h1's the page isn't semantically correct technically. Otherwise, good luck on your html and css journey!

  • Piyush Solanki•180
    @PiyushSolanki-hub
    Submitted 7 months ago

    Social Links Profile using tailwind css

    #tailwind-css
    1
    P
    SuiteMel•170
    @SuiteMel
    Posted 7 months ago

    The design is fairly close. Though I noted the location text and button text isn't bold like the design. I would also really recommend making the links from the design actual links instead of just list items, practice styling links is really helpful for future projects and if you don't have a link you can also put a dummy link like "#" in the href value.

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