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

Carlos Al

@crsaele200 points

Thank you for visiting my profile friend i love front-end and my dream is to be one of the very best front-end developers see you at the top

Latest solutions

  • Advice generator app built with HTML CSS JS API


    Carlos Al•200
    Submitted 7 months ago

    Any feedback or response would be greatly appreciated


    0 comments
  • Ping coming soon page master built with HTML CSS and Javascript


    Carlos Al•200
    Submitted 7 months ago

    I welcome any suggestions or feedback regarding my HTML structure, CSS, or JavaScript. Your insights would be greatly appreciated


    0 comments
  • Profile card component built with HTML and CSS


    Carlos Al•200
    Submitted 8 months ago

    I would appreciate any guidance on resources or methods to deepen my understanding of background images and their positioning techniques. Thank you.


    0 comments
  • Newsletter sign-up form with success msg built with CSS and Javascript


    Carlos Al•200
    Submitted 9 months ago

    Any feedback is welcome, thank you so much.


    1 comment
  • Responsive huddle landing page section master with HTML and CSS


    Carlos Al•200
    Submitted 9 months ago

    I would greatly appreciate any feedback on potential improvements or recommendations that could have simplified the process.


    0 comments
  • Stats preview card component with HTML and CSS


    Carlos Al•200
    Submitted 10 months ago

    I would appreciate any constructive feedback or suggestions on how to further optimize and enhance this solution, particularly with regards to HTML and CSS best practices. I am committed to ongoing learning and improvement, and I am eager to explore opportunities to refine my approach and deliver even more effective and efficient solutions. If you have any recommendations or insights, I would be grateful to hear them and incorporate them into my future work.


    0 comments
View more solutions

Latest comments

  • Arthur•70
    @drk-Arthur
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    It is my first project using JS here, even if it was something small i'm pretty happy with how it turned out.

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

    Had problems with the sizing of the icons at the FAQ.

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

    There is a problem when all the topics are shown, the FAQ card increases it's size and the top part disappears. Had no idea how to fix it.

    FAQ Accordion

    1
    Carlos Al•200
    @crsaele
    Posted 8 months ago

    It looks like the answers to questions 2, 3, and 4 are missing from the display. Could you please add them so we can review the complete set of answers?

  • Thibault•110
    @Thibs13
    Submitted 10 months ago

    Responsive Product Card

    1
    Carlos Al•200
    @crsaele
    Posted 10 months ago

    Hey there, fellow developer!

    When it comes to building websites, it's easy to get caught up in the excitement of creating something new and just use a bunch of <div> and <section> elements to get the job done. But, trust me, taking the extra step to write semantic HTML is totally worth it!

    So, what's the big deal about semantic HTML? Well, let me break it down for you:

    Search Engine Optimization (SEO)

    Search engines like Google love semantic HTML because it helps them understand the structure and content of your website. By using specific elements like <header>, <nav>, <main>, and <footer>, you're giving search engines a clear picture of your website's layout and content. This can improve your website's visibility and ranking in search results!

    Accessibility

    Semantic HTML is a game-changer for accessibility. Screen readers and other assistive technologies can better interpret your website's content when you use specific elements like <button>, <label>, and <table>. This means that users with disabilities can more easily navigate and understand your website.

    Code Readability and Maintenance

    Let's face it, code can get messy quickly! Semantic HTML helps keep your code organized and easy to read. When you use specific elements, you can quickly identify the purpose of each section of code. This makes it easier to maintain and update your website over time.

    Future-Proofing

    As web development continues to evolve, new technologies and features are being added all the time. By using semantic HTML, you're future-proofing your website for upcoming advancements. For example, when new accessibility features are introduced, your website will be better equipped to take advantage of them.

    In conclusion, writing semantic HTML is an important part of building a website that's not only functional but also accessible, search engine friendly, and easy to maintain. So, take the extra time to learn and use semantic HTML elements – your users (and search engines) will thank you!

    Happy coding!

    @crsaele

  • Kiran Pillai•80
    @DetonatedSkull1722
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    The amount of effort i put into this was really too much, I got too bored even, but i kept going i am honestly just proud about that

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

    The table thing in the bottom, it was really brain boggling because you can just use a normal table for that

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

    nothing at the moment

    Responsive Recipe page

    1
    Carlos Al•200
    @crsaele
    Posted about 1 year ago

    When displaying tabular data, using the <table> element and its related elements (<td>, <th>, <tr>, etc.) is better than using generic <div> elements for several reasons:

    *Accessibility: Screen readers and other assistive technologies can identify and interpret table structures, making it easier for users with disabilities to understand and navigate the data.

    *Semantic meaning: Table elements provide clear semantic meaning to the content, allowing search engines and other machines to understand the data's structure and relationships.

    *Easier styling: Table elements have built-in styling and layout rules, making it easier to create visually appealing and consistent table designs with less CSS.

    *Improved readability: Table elements help to create a clear and organized presentation of data, making it easier for users to scan and understand the information.

    Using <div> elements to create a table-like structure can lead to confusing and inaccessible content, so it's best to use the right tool for the job – the <table> element and its friends!

  • mahmoud17-cmyk•300
    @mahmoud17-cmyk
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    that I am quickly growing accustomed to writing code and becoming more adept at handling it

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

    Once you get used to the challenges, they become less difficult.

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

    CSS properties that align items

    frontend mentor proj-3

    1
    Carlos Al•200
    @crsaele
    Posted about 1 year ago

    You might want to use more semantic html tags to enhance your structure.

    Using semantic HTML tags (like <header>, <nav>, and <main>) instead of generic <div> elements is a game-changer for accessibility and SEO.

    It helps screen readers and search engines understand the structure and meaning of your content, making it easier for everyone to find and use your website.

  • polinagusakova•250
    @polinagusakova
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    I used Javascript to solve the problem.

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

    How to change color in element, when click on different item.

    Blog preview page

    1
    Carlos Al•200
    @crsaele
    Posted about 1 year ago

    Great work it looks really good on different screen sizes 👌

  • Divyam Sharma•160
    @Divyamsharma-18
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    I'm just proud of doing it so effortlessly, next time I'll do it with time boundation.

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

    None

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

    None tbh.

    Divyamsharma-18 / QR-code-component-Responsive-challenge-

    2
    Carlos Al•200
    @crsaele
    Posted about 1 year ago

    I congratulate you for your efforts 😊

    If anything i would say try to write more semantic html.

    It is highly recommended to utilize semantic HTML elements, such as <main></main>, instead of generic <div></div> tags, to provide a clear structure and meaning to your content. This approach not only enhances code readability but also improves accessibility and search engine optimization (SEO).

    Writing semantic HTML is important for accessibility, SEO, code readability and maintainability, cross-browser compatibility, and future-proofing.

    By using appropriate HTML elements, you can create a clear and consistent structure for your content, making it easier for users, search engines, and other developers to understand and interact with your website.

    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