Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
13
Comments
210
Alex
@Alex-Archer-I

All solutions

  • Testimonials section build with grid

    #react#vite#bem

    Alex•3,130
    Submitted 12 months ago

    If someone could give me a tip about dynamic generation layouts such this (especially without knowing a quantity of items at advance I would be more than happy =)

    And, as always I open for every type of comments.


    1 comment
  • Features cards section build with grid

    #react#vite#oocss

    Alex•3,130
    Submitted 12 months ago

    I'm open for every suggestion =)


    2 comments
  • Product page

    #vite#tailwind-css

    Alex•3,130
    Submitted 12 months ago

    Open for any comments, as always.


    2 comments
  • Advice app

    #vite

    Alex•3,130
    Submitted 12 months ago

    "If you want happiness for a year, inherit a fortune. If you want happiness for a lifetime, help someone else."

    Confucius


    2 comments
  • Ecommerce product page build with React

    #react#vite

    Alex•3,130
    Submitted about 1 year ago

    As always I'll be more than happy to receive some critics, advices and just random comments =)


    1 comment
  • Notification page

    #vite

    Alex•3,130
    Submitted about 1 year ago

    This project got me thinking how to make those notifications more accessible. How can I inform tools like screen readers about unread notifications? Should I add tag like "aria-label" to unread notification? Or, maybe to badge which display their number? I'm interested in any suggestions and opinions.

    I didn't add aria tag for now cos as Aristotle said, "No ARIA is better than bad ARIA" (or it was Newton?).

    Beside that any suggestions are welcomed.


    1 comment
  • Result summary page

    #vite#oocss

    Alex•3,130
    Submitted about 1 year ago

    Open for any suggestions =)


    1 comment
  • Newsletter sing-up form


    Alex•3,130
    Submitted about 1 year ago

    Any suggestions welcomed and accepted =) Especially advice about code organization and forms accessibility.


    1 comment
  • FAQ page


    Alex•3,130
    Submitted about 1 year ago

    I'm glad to read any comments.


    0 comments
  • Recipe page


    Alex•3,130
    Submitted about 1 year ago

    I always have troubles with the neat organization. In this project I tried to use BEM. I backed off a little from naming convention - I know - but did I gasp the main idea? Besides any suggestion accepted.


    1 comment
  • A responsive social links page


    Alex•3,130
    Submitted about 1 year ago

    Nothing special for this challenge, but I always up for advises, criticism, comments, small talks and deep conversations.


    1 comment
  • Responsive blog preview card


    Alex•3,130
    Submitted about 1 year ago

    Well, since "font" already word of the day for this challenge, it'll be good to hear an advise about best practices of using fonts. But I'm really open for any kind of comments.


    1 comment
  • A QR-code card using flex for centering.


    Alex•3,130
    Submitted about 1 year ago

    I'm open for all kind of comments and criticism, but I always wonder whether I am using the best practices on the code, file organization and stuff.


    2 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