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

Alin Costea

@CosteaAlin93Germany190 points

SRE looking to bring art in my tech life, thus wanting to change to a Frond End Developer position.

I’m currently learning...

TailwindCSS, Javascript and React

Latest solutions

  • Three column preview card component using tailwind-css

    #tailwind-css

    Alin Costea•190
    Submitted about 2 years ago

    0 comments
  • Interactive rating component using tailwind-css and JavaScript

    #tailwind-css

    Alin Costea•190
    Submitted about 2 years ago

    0 comments
  • Product preview card component using tailwind-css

    #tailwind-css

    Alin Costea•190
    Submitted about 2 years ago

    0 comments
  • Results-summary-component using tailwind-css

    #tailwind-css

    Alin Costea•190
    Submitted about 2 years ago

    0 comments
  • qr-code-component using tailwind-css

    #tailwind-css

    Alin Costea•190
    Submitted about 2 years ago

    1 comment

Latest comments

  • Ananya•10
    @Titli007
    Submitted about 2 years ago

    Rating system

    1
    Alin Costea•190
    @CosteaAlin93
    Posted about 2 years ago

    Hi Ananya :) Very nice work on the design. I would have a few extra hints:

    • you could make the 'submit' button wider to be 1:1 with the design
    • on the functionality:
      • clicking submit while no rating is selected >> this case should show an error message or some hint to the user to click a rating before submitting thus, not allowing the user to go to the next step. To do this, above or below the submit button, create a paragraph element which will contain something like 'Please select a rating!' , and style it to be hidden (display: none;) and only show it when the button is clicked without a rating being selected

    Other than that, all seems fine, congrats for the solution. Let me know if my hints are not clear :)

    All the best,

    Alin

    Marked as helpful
  • Vishal•260
    @vishal-singh5128
    Submitted about 2 years ago

    Interactive Rating Component using Css ,Javascript and jQuery

    1
    Alin Costea•190
    @CosteaAlin93
    Posted about 2 years ago

    Hi Vishal, There could be a better way to do this. First of all, let's define some cases:

    • clicking submit while no rating is selected >> this case should show an error message or some hint to the user to click a rating before submitting. To do this, above the submit button, create a paragraph element which will contain something like 'Please select a rating!' , and style it to be hidden (display: none;) and only show it when the button is clicked without a rating being selected

    • selecting a rating and pressing submit >> this should not point to to index2.html. Rather, use the same trick as above. Consider your content on index.html as the 'rating view' and the content on index2.html as the 'thank you' view. Combine the HTML from the both files in a single one. Now, if you have a rating selected, clicking submit should hide your 'ratingBox' element and in his place, you should display the 'thankYouState ratingBox' element.

    • and one more thing: clicking submit on your solution will give a rating by default. If you fix the first case above, this situation will disappear.

    Marked as helpful
  • Ferney•170
    @FerneyMontoya6
    Submitted about 2 years ago

    3 column preview cards, CSS flexbox

    #accessibility#bem#semantic-ui
    1
    Alin Costea•190
    @CosteaAlin93
    Posted about 2 years ago

    Hi Ferney! Awesome design!! At a very close inspection, I would modify just a few minor things to make it 100% pixel perfect:

    • you need to add just a bit of rounded corners to the content; to do so, I would wrap the 3 article elements into a div or section element and apply the rounded corners to it
    • for the paragraphs, you need to add the Lexend Deca font ;)
    • and add a bit of padding to the y axis (on the vertical) to the learn more buttons so they become a bit more bulkier
    • and yea...make the SUVs text into SUVS

    Once again, congrats for the solution. Hope my hints make sense and are on the point. Drop me a message if anything is not clear.

    All the best,

    Alin

  • meliodas-png•70
    @meliodas-png
    Submitted about 2 years ago

    3 column preview card component

    1
    Alin Costea•190
    @CosteaAlin93
    Posted about 2 years ago

    Hello Meliodas!

    Congrats for your work! The design is almost perfect, except for some very minor things:

    • you need to add some rounded borders to the main element
    • the h2 elements, need to have font-family: Big Shoulders Display, sans;
    • add a bit of thickness to the fonts used in the <p> and <button> elements so you are 1:1 with the design

    Keep up the good work, let me know if you have and doubts about my answer :)

    Marked as helpful
  • jafar-mirzapoor•170
    @jeff-dev0
    Submitted about 2 years ago

    cards using css and html

    1
    Alin Costea•190
    @CosteaAlin93
    Posted about 2 years ago

    Hello Jafar ! Nice work :) A few remarks:

    • start designing with a 'Mobile-first' perspective, this way it's easier to adjust the elements for bigger screens once mobile view is done
    • on the Mobile design, you should reduce the width of the cards, so you are 1:1 with the design and also because once I make my window really small, the p text is not properly visible
    • the h1 font family should be 'Big Shoulders Display'
    • and on the Desktop view, same thing, you should set the width of the <p> element so ~150px, so the text wraps nicely within the container, else it gets 'under' it's neighbour element

    Keep up the good work, let me know if you have and doubts about my answer :)

    Marked as helpful
  • Pulkit saxena•870
    @Pulkit-s21
    Submitted about 2 years ago

    React Product Preview

    #react#tailwind-css#vite
    1
    Alin Costea•190
    @CosteaAlin93
    Posted about 2 years ago

    Hi Pulkit! Overall, it looks good. A few hints for the design:

    • try surrounding the root element into an <main> element so you avoid the 'Document should have one main landmark' error
    • the image-container element, could be a bit smaller in width to keep the proportions as a whole
    • the image is too stretched, perhaps background-size: contain; will fix it looking more like in the solution
    • the font-weight of the h2 could be ticker
    • the span containing 'CHANEL ' text, didn't have to be green
    • a bit ticker font on the price
    • and don't forget the little icon on the 'Add to cart' button :)

    On the Mobile view:

    • image is perfectly set
    • for the content part, you could increase the height a bit, or the spacing between the individual elements

    Considering you are using Tailwind for this, my advice would be:

    • always start designing with the 'mobile-first' design in mind
    • once the above looks on point, start using 'md:flex-direction:row;' etc, for styling for the 'Desktop view'

    Keep the solutions coming! Planning to do your approach once I start learning a bit or React!

    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