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

T23harms

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

  • Room Homepage


    T23harms•540
    Submitted 3 months ago

    I had problems with the responsiveness and don't know how to fix it.


    1 comment
  • Loopstudios Landing Page


    T23harms•540
    Submitted 3 months ago

    1 comment
  • NFT-Preview-Card


    T23harms•540
    Submitted 3 months ago

    1 comment
  • Ecommerce product page


    T23harms•540
    Submitted 3 months ago

    The Lightbox, i just don't get it how to do it with JS.


    1 comment
  • News-Homepage


    T23harms•540
    Submitted 4 months ago

    1 comment
  • contact-form


    T23harms•540
    Submitted 4 months ago

    1 comment
View more solutions

Latest comments

  • P
    thawit•820
    @tacesept
    Submitted 3 months ago

    Room Homepage using React and Scss

    1
    T23harms•540
    @T23harms
    Posted 3 months ago

    The transitions and animations on the slides are really well done, including the arrow on 'Shop now'. However, I noticed that the pages aren’t fully responsive — on smaller screens, everything gets squished together. But that’s something I often struggle with as well. Other than that, it’s great!🚀

    Marked as helpful
  • AndresOreVel•370
    @AndresOreVel
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    I'm proud of having learnt some of sass. It definitely gives you the ability of structure your css code even more. Next time I will take the next step to do it better.

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

    In the images section, I saw that I had quite a bit of code. Then I checked the Sass documentation and simply applied a loop to minify the CSS.

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

    About sass, because I'm sure there are many things I've left undone that I could have simplified.

    main-studio

    1
    T23harms•540
    @T23harms
    Posted 3 months ago

    Your HTML and CSS code for the Loopstudios landing page demonstrates a solid structure and good use of semantic elements. The layout is well-organized with BEM-style class naming, which helps keep the styles modular and easier to maintain. The use of @media queries shows that you're thinking about responsiveness, and the background images adapt nicely between desktop and mobile.

    A few suggestions for improvement: You’ve included the same Google Fonts import multiple times—this is redundant and should be cleaned up to improve performance. Also, in your HTML, the <ul> element inside the footer is mistakenly written as <u>, which should be corrected for proper HTML semantics.

    Overall, great work—just a few small refinements would take it to the next level!🚀

    Marked as helpful
  • P
    HamzehAlayan01•100
    @HamzehAlayan01
    Submitted 4 months ago

    NFT Preview Card Component

    1
    T23harms•540
    @T23harms
    Posted 3 months ago

    The structure is clean and semantic, with clear class naming and good use of BEM conventions. The visual hover effect on the image (with a preview icon and translucent overlay) is nicely implemented and adds a polished touch.

    Your layout is well centered using Flexbox on the body, and the color scheme is consistent with good variable usage. The animation on the image gives it life and enhances the user experience.

    One thing to consider: the fixed vw and vh values in the main element make it less responsive on smaller screens. It seems this card is optimized for desktop viewing, but for mobile, it may appear too narrow or cramped. Adding media queries or using more fluid layout units (like % or max-width) could improve responsiveness.

    Overall: Great attention to visual details and interactivity – just keep responsiveness in mind for future iterations.🚀

    Marked as helpful
  • Sylvain Web•380
    @SylvainPS78
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?
    • Learned overlay
    What specific areas of your project would you like help with?

    Any comments will be welcomed. My code isn't cleaned yet, I have to improve responsive design and improve accessibility.

    E-Commerce Page

    1
    T23harms•540
    @T23harms
    Posted 3 months ago

    The HTML structure of the e-commerce product page is well-organized and semantic, making it easy to understand and maintain. The use of meaningful alt attributes, accessible SVG elements, and clearly separated sections like header, main, and footer demonstrates good attention to accessibility and code readability. External assets and fonts are efficiently linked, and the cart and overlay components show thoughtful UI structuring. Overall, the code reflects solid foundational HTML skills and provides a great base for styling and interactivity.

    The CSS is well-organized, with clear use of flexbox for layout and proper use of media queries for responsiveness. The styling ensures a modern and clean look for the design. Some selectors could be more specific to avoid potential conflicts, and it might be helpful to add a bit more spacing between sections for improved readability on smaller screens.

    The JavaScript code is well-structured and efficiently handles interactive elements on the e-commerce page. Functions such as addToCart and deleteCart ensure a smooth shopping experience, while displayCart and displayDesktopOverlay manage visibility. To improve readability and scalability, the functions could be further modularized for easier maintenance as more features are added.

    But overall great work, keep it going🚀

  • Pai-Kai Lee•320
    @PaiKai-Lee
    Submitted 4 months ago

    News homepage solution

    2
    T23harms•540
    @T23harms
    Posted 4 months ago

    I had a look at your code and overall it's very clean and well-structured! One thing I noticed is that the three bottom images appear slightly stretched or distorted, especially on larger screens. This might be due to the use of w-full and basis-1/3 without setting a fixed aspect ratio or controlling the image height. Apart from that, everything looks great and works smoothly!🚀

    Marked as helpful
  • P
    Jonatan Samuelsson•540
    @jonatan-samuelsson
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    Form validation became unneccessarily complicated, as I set out to do it with HTML and CSS only. I got it working to 90% but I couldn't make it the final stretch. I could have left it and it would have been working fine, but it would not have been able to differentiate missing from incorrectly provided inputs. In the end, I scrapped it and implementet an all out JS solution in stead, which all took way too long and didn't exactly end up DRY.

    On the accessibility side of things, the provided articles on accessible forms wer super helpful and well-curated. Implementing error messages and validation really makes you have to think about how it all comes accross to AT:s.

    Accessible contact form | Semantic HTML, vanilla JS & CSS

    1
    T23harms•540
    @T23harms
    Posted 4 months ago

    The code appears to be a clean, well-structured contact form with proper HTML, CSS, and JavaScript integration. The form is responsive, and CSS variables are well-organized for easy adjustments. The JavaScript uses event listeners to handle form validation and user interactions, ensuring that required fields are validated and users get real-time feedback.

    A few things to note:

    It’s good that validation functions are modular, making it easy to add or modify rules. However, make sure to check for edge cases like special characters in names that might not pass the current regex.

    The use of ARIA attributes is a good accessibility practice, but adding labels for all interactive elements would further improve accessibility.

    The success message has a nice animation but ensure it doesn’t interfere with form usability on slower devices.

    Overall, it's a well-implemented solution that prioritizes user experience and responsiveness.🚀

    Marked as helpful
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