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

raya

@rayaattaUganda2,870 points

Hello 👋,I am a passionate frontend developer who is trying to learn something new everyday as I apply it to projects I make to create stunning visuals and functioning webpages.

I’m currently learning...

Js and... Vue js

Latest solutions

  • Testimonials grid section

    #accessibility#progressive-enhancement

    raya•2,870
    Submitted over 1 year ago

    0 comments
  • Results summary component

    #accessibility

    raya•2,870
    Submitted over 1 year ago

    0 comments
  • Huddle landing page

    #accessibility

    raya•2,870
    Submitted over 1 year ago

    0 comments
  • News letter Sign up with success message

    #accessibility

    raya•2,870
    Submitted over 1 year ago

    1 comment
  • Profile card component

    #accessibility

    raya•2,870
    Submitted over 1 year ago

    1 comment
  • Four card feature section

    #accessibility

    raya•2,870
    Submitted over 1 year ago

    0 comments
View more solutions

Latest comments

  • P
    Brian Meinert•360
    @bmeinert8
    Submitted 7 months ago
    What are you most proud of, and what would you do differently next time?

    I'm most proud of figuring out the grid layout on my own this time without and help from GitHub co-pilot or google searching. I'm still fairly new to creating complex layouts with CSS Grid, so this was a big positive for me to be able to figure this one out based on my knowledge from previous documents and projects. I also added my own little hover feature on the desktop display to the cards, just for fun, and to customize the project a bit.

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

    My biggest challenge was getting the testimonial cards laid out on the grid properly. I had to go through a couple times playing with the grid size and which columns / rows the cards span to get the layout to look properly

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

    I'm fully open to any help, tips, suggestions, and constructive criticism, or questioning on any aspects of this project. The more insight the better, in my opinion.

    Responsive testimonial grid challenge

    1
    raya•2,870
    @rayaatta
    Posted 7 months ago

    Hello @bmeinert8, Congratulations on completing this challenge🎉. I have some few suggestions though:

    1. Personally I don't think it's relevant to separate your css file for the media queries since this reduces performance when dealing with large scale websites

    2 It's not really a good idea to use css id's for styling since this creates specifity issues. It's much better to use classes instead.

    3 Your project is epic.

    Ciao ✌️

    Marked as helpful
  • P
    Davy•320
    @DavyZane
    Submitted 7 months ago
    What are you most proud of, and what would you do differently next time?

    Just a little training.

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

    None.

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

    Nothing special. If you have some comments please share.

    huddle-landing-page-with-single-introductory-section-master

    1
    raya•2,870
    @rayaatta
    Posted 7 months ago

    Congratulations on completing your project. The link to your GitHub report isn't right though. You probably mistyped it or your repository is saved as private. All in all,project looks cool

  • P
    Øystein Håberg•13,260
    @Islandstone89
    Submitted 10 months ago
    What are you most proud of, and what would you do differently next time?

    I'm proud of figuring out all the complexities, layout-wise. I'm also happy that I used container queries in practice! I used it on the "mechanical wireless keyboard" section, where I changed the flex-direction from column to row when its wrapper equals 500px or more.

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

    The layout was a bit challenging, with some of the images reaching either the left or right edge. This meant that I had to write a lot of rules for the padding on elements. I also had to google how to create the dark orange overlay on one of the images.

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

    I'm always open for feedback :)

    Typemaster Landing Page

    1
    raya•2,870
    @rayaatta
    Posted 9 months ago

    Hey there👋.

    The only thing I think needs updating is the pre-order link. Elements that behave as buttons but are built using other tags such as span, div, a or others, should include a role attribute that equals to button just to improve on accessibility. Other than that impressive solution✌️.

  • dkaffes•160
    @dkaffes
    Submitted over 1 year ago

    Order summary component - Flexbox, responsive and hover state

    1
    raya•2,870
    @rayaatta
    Posted over 1 year ago

    Hello 👋dkaffes, congratulations on completing this challenge 🎉

    I have some suggestions for you.

    1 Divs do not carry any semantic value. You should replace

    <div class="c-order-summary">
    

    With

    <article class="c-order-summary">
    

    2 The illustration hero image is decorative. You should leave it's alt attribute empty i.e alt=""

    3 I noticed that you used <h2 class="summary-title"> .since it is the only heading in the document you should replace it with <h1 class="summary-title">.

    Here's a quick guide on how to use them:

    The <h1> to <h6> tags are used to define HTML headings. <h1> defines the most important heading. <h6> defines the least important heading. Only use one <h1> per page - this should represent the main heading/subject for the whole page. Also, do not skip heading levels - start with <h1>, then use <h2>, and so on. You can then style them in you css.

    Unlike what most people think, it's not just about the size and weight of the text It is about maintaining a clear and consistent hierarchy through out the document

    Lastly,concerning your question.

    A button element would be better choice because,if this was a real site.the cancel order would invoke JavaScript to cancel the order and proceed to payment would also call some jscript. But the anchor element is for linking pages or sections of an element so it shouldn't be here

    I hope this helps 🙃

    Otherwise your solution is neat👍

    Happy coding ✌️

    Marked as helpful
  • RassTa-00•50
    @RassTa-00
    Submitted over 1 year ago

    Blog Preview Card

    1
    raya•2,870
    @rayaatta
    Posted over 1 year ago

    Hello 👋, congratulations on completing this challenge 🎉

    I have some suggestions to make your code much more responsive.

    1 You used width: 380px; On the .container This is okay but in case a screen is less than 380px wide then the card overflows the view port. You can make it more responsive by using max-width:min(90%,380px) This means it is 380px but on smaller screens it only covers 90% of the width.

    After making this adjustment your image will overflow because you set it to a fixed width of 370px. It is a bad practice to set a fixed height or width of an image. The most recommended practice is giving it a max-width.Usually

    img {
    display:block;
    max-width:100%;
    }
    

    This would be a more responsive approach

    2 In order to center the card on any screen add this code snippet to body.

    min-height:100vh;
    display:flex;
    align-items: center;
    justify-content: center;
    
    

    Then remove the margin properties from .container

    I hope this helps 🙃

    Otherwise your solution is neat👍

    Happy coding ✌️

    Marked as helpful
  • Shubham Rawat•60
    @shubham00111
    Submitted over 1 year ago

    qr code challenge solution

    1
    raya•2,870
    @rayaatta
    Posted over 1 year ago

    Hello Shubham Rawat👋, congratulations on completing your first FED challenge 🎉

    I have some suggestions you might find useful.

    1 Try to make your html more Semantic by wrapping the main page content inside a <main> tag . Replace <div class="container"> With <main class="container">. This changes nothing visually but Using it makes all the difference. Using semantic markup improves

    SEO

    And user experience (accessibility) for people using assistive technology such as screen readers.

    2 The qr code should have text inside the alt attribute stating what it is and where it leads i.e alt="qr code leading to frontendmentor.io

    3 I noticed that you used h2 .since it is the only heading in the document you should replace it with <h1>.

    Here's a quick guide on how to use them:

    The <h1> to <h6> tags are used to define HTML headings. <h1> defines the most important heading. <h6> defines the least important heading. Only use one <h1> per page - this should represent the main heading/subject for the whole page. Also, do not skip heading levels - start with <h1>, then use <h2>, and so on. You can then style them in you css.

    Unlike what most people think, it's not just about the size and weight of the text It is about maintaining a clear and consistent hierarchy through out the document

    I hope this helps 🙃

    Otherwise your solution is neat👍

    Happy coding ✌️

    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

Mentor of the Week - 2nd Place

This badge is awarded to the 2nd placed community member on the weekly Wall of Fame.

Fun fact

Keypunches were used in early computing to punch precise holes in stiff paper card. The punched cards were then used for data input, output, and storage. No code linters or auto-complete suggestions to help out back then! 😅

Mentor of the Week - 3rd Place

This badge is awarded to the 3rd placed community member on the weekly Wall of Fame.

Fun fact

The Hansen Writing Ball shown in the badge was the first commercially produced typewriter. It was put into production in 1870 with its unique ergonomic design. It was overtaken in the market in 1873 by the Sholes and Glidden typewriter which was the first keyboard to utilise the QWERTY layout we now use today.

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