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

Caaspita

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

  • Stats preview card with HTML and CSS


    Caaspita•170
    Submitted over 1 year ago

    1 comment
  • Tip Calculator with HTML, CSS and JS


    Caaspita•170
    Submitted over 1 year ago

    1 comment
  • Age Calculator with HTML, CSS and JS


    Caaspita•170
    Submitted over 1 year ago

    0 comments
  • Newsletter SingUp with HTML, CSS and JS


    Caaspita•170
    Submitted over 1 year ago

    0 comments
  • FAQ Acordion Page with HTML, CSS and JS


    Caaspita•170
    Submitted over 1 year ago

    0 comments
  • Interactive rating component with HTML, CSS and JS


    Caaspita•170
    Submitted over 1 year ago

    0 comments
View more solutions

Latest comments

  • mrnestorramirez•50
    @mrnestorramirez
    Submitted over 1 year ago

    QR-Code

    #bem
    1
    Caaspita•170
    @Caaspita
    Posted over 1 year ago

    Congratulations on a new solution, the code looks very clean. One thing that could be improved as a good practice is to change the <div> to a <section> or <article> to maintain semantic HTML. But honestly, everything looks very neat.

  • jabnakar•20
    @jabnakar
    Submitted over 1 year ago

    Social Links Profile solution with simple HTML and CSS

    3
    Caaspita•170
    @Caaspita
    Posted over 1 year ago

    Congrats for the new solutions, i have some sugestions for you.

    -It would be good to separate the CSS and the HTML into different files to maintain good practice and more organized code.

    -Try to maintain correct indentation in the code so that it is easier to read it for you and other people

    -You could improve good practices by using semantic HTML so that the browser can read your website better. I leave you this page that explains it better. https://www.freecodecamp.org/news/semantic-html5-elements/

    Cheer up and keep programming

    Marked as helpful
  • P
    lkBangar•10
    @lkBangar
    Submitted over 1 year ago

    Tool: Visual Studio Code, Languages: CSS, HTML

    2
    Caaspita•170
    @Caaspita
    Posted over 1 year ago

    The page looks very good, but I have some suggestions for you.

    -It would be good to separate the HTML and CSS code into different files to maintain order. While it may not be much, it is more organized.

    -The <h2> tag could be used as <h1> since it is the main topic, helping the browser better understand the theme of your page and display it to the correct users.

    -As Mark mentioned, the use of semantic HTML is a good practice as it helps the browser better understand your code.

    Congratulations on completing this challenge! Best of luck, and keep improving.

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