Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
4
Comments
5
Oscar Echenique D.
@OscarE2D

All solutions

  • Recipe Page Solution


    Oscar Echenique D.•80
    Submitted about 2 months ago

    Improving CSS structure and maintainability for more complex projects: How to integrate ITCSS or CSS Modules without losing simplicity?

    Optimizing project performance and accessibility: What tools and practices would you recommend to audit and enhance both aspects?

    Deepening the use of new CSS features like container queries and functions like clamp(): practical examples to implement them effectively.


    1 comment
  • Social links profile


    Oscar Echenique D.•80
    Submitted about 2 months ago

    I’d like feedback on these specific points:

    Accessibility optimization: Is there anything I could improve in terms of semantic tags, color contrast, or keyboard navigation?
    
    CSS best practices: Is my CSS organization okay, or are there suggestions to make it more scalable or maintainable?
    
    Loading performance: Even though it’s a small project, is there anything that might be negatively affecting its performance?
    

    If you see anything else I missed or could improve—I'm all ears!


    1 comment
  • Blog Preview Card - semantic HTML, modern CSS layout techniques.


    Oscar Echenique D.•80
    Submitted about 2 months ago

    I would appreciate help or resources on best practices for organizing CSS code more efficiently. Also, guidance on advanced CSS pseudo-classes, animations, and transformations would be very valuable as I aim to deepen my skills and create more dynamic UI interactions.


    2 comments
  • responsive QR code component - HTML - CSS - Responsive design


    Oscar Echenique D.•80
    Submitted about 2 months ago

    What I’d Like Help With

    While I’m proud of completing this project independently, there are a few specific areas where I’d really appreciate feedback:

    Responsiveness techniques
    I used clamp() to handle responsive typography without media queries. Does this approach scale well across different resolutions and devices? Are there edge cases I might have missed?
    
    Image performance and security attributes
    I applied several <img> attributes like referrerpolicy, crossorigin, decoding, and loading. Are these the best choices for this type of project, or are there better practices I should consider?
    
    CSS structure and organization
    I wrote my own CSS reset and tried to keep variables and layout code well-organized. Are there any improvements you’d suggest for clarity, maintainability, or scalability?
    
    Accessibility
    I attempted to use semantic HTML wherever possible. Are there accessibility improvements I should implement for a better user experience, especially for screen reader users?
    
    General code quality
    Any recommendations on improving my code readability, file structure, or adherence to modern front-end development standards are more than welcome!
    

    1 comment
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