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

Mr Rabbit

@rabbitmaid1,020 points

I love programming everyday, watching anime and also reading manga! I also enjoy art, graphic design, video editing, and also teaching what i know to others. I love learning new aspects everyday so frontendmentor is just awesome.

I’m currently learning...

PHP

Latest solutions

  • Recipe Page


    Mr Rabbit•1,020
    Submitted 9 months ago

    The best possible way to make use of fonts in CSS. From importing to assigning it to areas of your webpage design.


    1 comment
  • Frontend Mentor - Profile card component solution

    #sass/scss#bem

    Mr Rabbit•1,020
    Submitted over 2 years ago

    0 comments
  • Social media dashboard with theme switcher solution

    #sass/scss#bem

    Mr Rabbit•1,020
    Submitted over 2 years ago

    2 comments
  • Easybank landing page

    #sass/scss#accessibility

    Mr Rabbit•1,020
    Submitted almost 3 years ago

    1 comment
  • Testimonial Grid Section

    #accessibility

    Mr Rabbit•1,020
    Submitted almost 3 years ago

    0 comments
  • Responsive Intro section with dropdown navigation

    #accessibility

    Mr Rabbit•1,020
    Submitted almost 3 years ago

    2 comments
View more solutions

Latest comments

  • Cecilia Leung•30
    @cecilialeung05
    Submitted 2 months ago
    What are you most proud of, and what would you do differently next time?

    This project helped reinforce the importance of:

    Using box-sizing: border-box for consistent spacing Creating fully responsive layouts with max-width and width: 100% Matching Figma shadows in CSS using rgba() and box-shadow Structuring clean, accessible HTML for simple components

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

    N/A

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

    N/A

    QR Code Component - using HTML and CSS

    1
    Mr Rabbit•1,020
    @rabbitmaid
    Posted 2 months ago

    Greeting! Good job with your practice. What i noticed so far is that you did not link the project properly! You need to link a specific project in this case the "QR Code Component Challenge"

  • Oduwole Ayomipo•50
    @oduwole-ayomipo
    Submitted over 2 years ago

    Frontend Mentor | QR code component

    1
    Mr Rabbit•1,020
    @rabbitmaid
    Posted over 2 years ago

    ** It already looks good enough, work now on the background and font**

    Also you can take note of the following

    • HTML5 elements such as <main>, <nav>, <header>, <footer>, <section>, <aside> act as landmarks, or special regions on the page to which screen readers and other assistive technologies can jump. By using landmark elements, you can dramatically improve the navigation experience on your site for users of assistive technology (Users with disabilities) .

    You can use the <div> for sub items within landmarks like <section>. In other words for containers or sections in your HTML you can use the <section> tag if you want to nest in sub items <div>.

    Landmarks such as the <section> may actually require that you specify a heading within. In other words if the section has no heading it may throw an error when checked by an accessibility tool.

    It is advisable that you place all your main site content in a landmark element <main> Here is an Accessibility Evaluation Tool to check your webpage for any errors or warnings related to landmarks.

    There exist an attribution <div> that comes with the frontendmentor starter kit. You will have to wrap this <div> in a <footer> tag

    Read

    • W3schools Accessibility Landmarks Notes for more information.

    • MDN Web docs notes for more information.

    I hope you find the above solution useful! 😄 Nevertheless, the solution you submitted is great! Happy coding!

  • AhmedBdrZanata•40
    @AhmedBdrZanata
    Submitted over 2 years ago

    Resposive QR code component

    1
    Mr Rabbit•1,020
    @rabbitmaid
    Posted over 2 years ago

    Great Job!

    Just a little tip for you!

    • HTML5 elements such as <main>, <nav>, <header>, <footer>, <section>, <aside> act as landmarks, or special regions on the page to which screen readers and other assistive technologies can jump. By using landmark elements, you can dramatically improve the navigation experience on your site for users of assistive technology (Users with disabilities) .

    You can use the <div> for sub items within landmarks like <section>. In other words for containers or sections in your HTML you can use the <section> tag if you want to nest in sub items <div>.

    Landmarks such as the <section> may actually require that you specify a heading within. In other words if the section has no heading it may throw an error when checked by an accessibility tool.

    It is advisable that you place all your main site content in a landmark element <main> Here is an Accessibility Evaluation Tool to check your webpage for any errors or warnings related to landmarks.

    There exist an attribution <div> that comes with the frontendmentor starter kit. You will have to wrap this <div> in a <footer> tag

    Read

    • W3schools Accessibility Landmarks Notes for more information.

    • MDN Web docs notes for more information.

    • Also always remember to put that alternative text for your images. In other words always set the alt attribute. For this helps search engines understand what the image is all about. A short description will do.

     <img src="images/image-qr-code.png" alt="Short Image Description">
    

    I hope you find the above solution useful! 😄 Nevertheless, the solution you submitted is great! Happy coding!

  • Jeremy Flodin•260
    @jeremyoduromanu
    Submitted over 2 years ago

    QR CODE COMPONENT

    #foundation
    2
    Mr Rabbit•1,020
    @rabbitmaid
    Posted over 2 years ago

    Excellent Job checkout the notes below to make your work more perfect

    • HTML5 elements such as <main>, <nav>, <header>, <footer>, <section>, <aside> act as landmarks, or special regions on the page to which screen readers and other assistive technologies can jump. By using landmark elements, you can dramatically improve the navigation experience on your site for users of assistive technology (Users with disabilities) .

    You can use the <div> for sub items within landmarks like <section>. In other words for containers or sections in your HTML you can use the <section> tag if you want to nest in sub items <div>.

    Landmarks such as the <section> may actually require that you specify a heading within. In other words if the section has no heading it may throw an error when checked by an accessibility tool.

    It is advisable that you place all your main site content in a landmark element <main> Here is an Accessibility Evaluation Tool to check your webpage for any errors or warnings related to landmarks.

    There exist an attribution <div> that comes with the frontendmentor starter kit. You will have to wrap this <div> in a <footer> tag

    Read

    • W3schools Accessibility Landmarks Notes for more information.

    • MDN Web docs notes for more information.

    I hope you find the above solution useful! 😄 Nevertheless, the solution you submitted is great! Happy coding!

    Marked as helpful
  • Chris•10
    @Akleodorion
    Submitted over 2 years ago

    First try

    1
    Mr Rabbit•1,020
    @rabbitmaid
    Posted over 2 years ago

    Hello! Good job starting this exercise

    As it is your first try as you indicated, you should try to be patient all through! Do not hurry for this is going to not only give you experience but will also help you understand core concepts in web design.

    How to get the most out of frontend Mentor

    Below are some things you can note during the process of carrying out this exercise

    Firstly you need to understand more about css layouts :- MDN CSS Layout notes

    • Before the Flexbox Layout module, there were four layout modes:

      Block, for sections in a webpage Inline, for text Table, for two-dimensional table data Positioned, for explicit position of an element not counting the margin positioning (Still perfect in some cases)

    The Flexible Box Layout Module, makes it easier to design flexible responsive layout structure without using float or positioning.

    learn Flexbox here

    The CSS Grid Layout Module offers a grid-based layout system, with rows and columns, making it easier to design web pages without having to use floats and positioning.

    learn CSS Grid Layout here

    Also you could checkout the simple guide below that shows different ways of perfect centering in css

    How to

    • Also HTML5 elements such as <main>, <nav>, <header>, <footer>, <section>, <aside> act as landmarks, or special regions on the page to which screen readers and other assistive technologies can jump. By using landmark elements, you can dramatically improve the navigation experience on your site for users of assistive technology (Users with disabilities) .

    You can use the <div> for sub items within landmarks like <section>. In other words for containers or sections in your HTML you can use the <section> tag if you want to nest in sub items <div>.

    Landmarks such as the <section> may actually require that you specify a heading within. In other words if the section has no heading it may throw an error when checked by an accessibility tool.

    It is advisable that you place all your main site content in a landmark element <main> Here is an Accessibility Evaluation Tool to check your webpage for any errors or warnings related to landmarks.

    There exist an attribution <div> that comes with the frontendmentor starter kit. You will have to wrap this <div> in a <footer> tag

    Read

    • W3schools Accessibility Landmarks Notes for more information.

    • MDN Web docs notes for more information.

    I hope you find the above solution useful! 😄 Nevertheless, the solution you submitted is great! Happy coding!

  • arda ilhan•20
    @ardailhn
    Submitted over 2 years ago

    html css

    2
    Mr Rabbit•1,020
    @rabbitmaid
    Posted over 2 years ago
    • HTML5 elements such as <main>, <nav>, <header>, <footer>, <section>, <aside> act as landmarks, or special regions on the page to which screen readers and other assistive technologies can jump. By using landmark elements, you can dramatically improve the navigation experience on your site for users of assistive technology (Users with disabilities) .

    You can use the <div> for sub items within landmarks like <section>. In other words for containers or sections in your HTML you can use the <section> tag if you want to nest in sub items <div>.

    Landmarks such as the <section> may actually require that you specify a heading within. In other words if the section has no heading it may throw an error when checked by an accessibility tool.

    It is advisable that you place all your main site content in a landmark element <main> Here is an Accessibility Evaluation Tool to check your webpage for any errors or warnings related to landmarks.

    There exist an attribution <div> that comes with the frontendmentor starter kit. You will have to wrap this <div> in a <footer> tag

    Read

    • W3schools Accessibility Landmarks Notes for more information.

    • MDN Web docs notes for more information.

    I hope you find the above solution useful! 😄 Nevertheless, the solution you submitted is great! 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

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