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

PastaSus

@PastaSus320 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

  • Faq accordion

    #accessibility#pure-css

    PastaSus•320
    Submitted 6 days ago

    i think there can still be improvements to be made, recommendations/feedback are more than welcome!


    0 comments
  • Interactive rating component


    PastaSus•320
    Submitted 9 days ago

    none for now, but feedbacks are welcome!


    1 comment
  • Tip calculator app


    PastaSus•320
    Submitted 20 days ago

    I'm not sure whether there are problems since its working fine, but feedbacks are much appreciated!


    1 comment
  • Time tracking dashboard main


    PastaSus•320
    Submitted 26 days ago

    None for now since i understand the code


    1 comment
  • newsletter sign up with success message main(no api's used)


    PastaSus•320
    Submitted about 1 month ago

    none, for now since it works properly


    1 comment
  • Article preview component


    PastaSus•320
    Submitted about 1 month ago

    my design is not as accurate actually so i need some feedback to maybe fix that later


    1 comment
View more solutions

Latest comments

  • Nitiema Allassane•380
    @NitiemaAllassane21
    Submitted 9 days ago

    FAQ accordion in HTML & CSS

    #accessibility
    1
    PastaSus•320
    @PastaSus
    Posted 6 days ago

    damn, didn't know you can do this with only html,css pretty cool to know! but anyways heres some things i think you should fix: Avoid Using <hr> Excessively or for Layout:

    -<hr> is for thematic breaks in content, not layout separation. Styling with borders or spacing is better.

    -Missing alt Text for Icons in Summary:

    -The comment suggests adding icons (+ and –) but doesn’t specify their alt text. If used, they should have appropriate alt text (like "Expand answer" / "Collapse answer") or aria-hidden="true" if redundant.

    -BEM Naming Not Consistently Applied:

    Some classes (like first__detail) are not BEM. Use faq__detail faq__detail--first instead.
    
    Marked as helpful
  • P
    JeronimoCardu•460
    @JeronimoCardu
    Submitted 11 days ago

    Responsive Interactive Rating Component

    1
    PastaSus•320
    @PastaSus
    Posted 9 days ago

    Good job

  • P
    Johnnie-Boy•250
    @Capt-Rong
    Submitted 22 days ago

    Tip Calculator

    2
    PastaSus•320
    @PastaSus
    Posted 20 days ago

    Good job on finishing the challenge, i think the code could be refactored into something better.

  • AndresOreVel•370
    @AndresOreVel
    Submitted 27 days ago
    What are you most proud of, and what would you do differently next time?

    Mobile design is the best. Next time I might make a different design for the tablet.

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

    At first, I didn't know how to do the desktop layout because there were some aspects of the grid I didn't understand, especially for the profile card.

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

    In the tablet design, the cards shrink or stretch, any help to prevent this from happening is welcome.

    Time Tracking Machine

    1
    PastaSus•320
    @PastaSus
    Posted 26 days ago

    you need to use the proper tags here it since the readability of the code is kinda bad. Instead of using divs only try to use the proper markup to make the code more readable and accessible. Other than that good job on finishing the challenge

  • shrikanth-dev•110
    @shrikanth-dev
    Submitted 6 months ago

    HTML, CSS, JavaScript

    1
    PastaSus•320
    @PastaSus
    Posted about 1 month ago

    bg color should be the lighter one, and darker color for the text.

    you dont really have to use inline svg tag here just use the <img src="svg.svg"> tag its much cleaner and more performant.

    the error message should be at the end also space-between here would be a good solution to that problem :)

    The semantics can also be better by adding a <section> tag and <main> tag

  • Alexandre•810
    @Stanex96
    Submitted 5 months ago

    Article Preview Component Master

    1
    PastaSus•320
    @PastaSus
    Posted about 1 month ago

    theres a lot of things that are wrong here(eg. html semantics, how you did your article preview component from mobile to desktop, bg color for links on mobile should be showing as grey) i think you should go through the learning paths here in frontendmentor to really help you progress better

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