Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
6
Comments
4

Ahmed Aziz

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

  • Responsive testimonials-grid-section

    #sass/scss#semantic-ui

    Ahmed Aziz•90
    Submitted 8 months ago

    1 comment
  • Responsive Four Cards Page

    #sass/scss#accessibility

    Ahmed Aziz•90
    Submitted 9 months ago

    Any enhancements to the code.


    2 comments
  • Responsive preview item page

    #bootstrap#sass/scss

    Ahmed Aziz•90
    Submitted 9 months ago

    breakpoints and layout structure


    2 comments
  • QR Code Component

    #sass/scss

    Ahmed Aziz•90
    Submitted 9 months ago

    image responsive


    2 comments
  • blog-preview-card's solution Accessibility Friendly

    #accessibility#sass/scss

    Ahmed Aziz•90
    Submitted 9 months ago

    "The use of rem and accessibility I think I did not use them the right way."


    1 comment
  • Normalize CSS Library, HTML5, Plain CSS, Breakpoints from Bootstrap


    Ahmed Aziz•90
    Submitted 9 months ago

    1 comment

Latest comments

  • LAZUR•80
    @Lazur05
    Submitted 8 months ago
    What specific areas of your project would you like help with?
    • In my desktop breakpoint, the cards seem to be too big and compressed, and I don't know exactly how to deal with it
    • Any advice is welcome

    Testimonials grid section

    #sass/scss#bem
    2
    Ahmed Aziz•90
    @Abo3bazez
    Posted 8 months ago

    it would be better if you but height : fit-content on the cards

  • Hamza Masmoudi•180
    @HamzaMasmoudi
    Submitted almost 2 years ago

    Four Card Section (With CSS Grid)

    #sass/scss#accessibility
    1
    Ahmed Aziz•90
    @Abo3bazez
    Posted 9 months ago

    Awesome Code

  • LAZUR•80
    @Lazur05
    Submitted 9 months ago
    What challenges did you encounter, and how did you overcome them?

    The first challenge was adding a distance between list markers and text. I found a solution in Stack overflow page.

    The second challenge was a nutrition table, where I couldn't make an underline below the nutrition value. I decided to add 4 tables for every single nutrition value and add div with underline class under every of the tables.

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

    In the instructions section, the wrapped text is under the list number, which shouldn't be there, but I can't find a solution for this problem

    Recipe page

    #sass/scss
    2
    Ahmed Aziz•90
    @Abo3bazez
    Posted 9 months ago

    You have done a good job with the challenges you have faced. I have some advice to offer:

    1.Nutrition Table Problem

    • You don’t have to create 4 separate tables, or even a table for the nutrition facts. Instead, you can use a layout like this and style it using Flexbox:
    html
    <div class="table">
        <div class="box border-1">
            <div class="key">Calories</div>
            <div class="value">277kcal</div>
        </div>
        <div class="box border-1">
            <div class="key">Carbs</div>
            <div class="value">0g</div>
        </div>
        <div class="box border-1">
            <div class="key">Protein</div>
            <div class="value">20g</div>
        </div>
        <div class="box">
            <div class="key">Fat</div>
            <div class="value">22g</div>
        </div>
    </div>
    

    Then, use Flexbox to style it:

    css
    .table .box {
        display: flex;
        justify-content: space-around;
    }
    

    2.Wrapped Text Under the List Number

    • To prevent the text from wrapping under the list number, wrap the entire text in <p> tags like this:
    html
    <ul>
        <li>
            <p><span>Total: </span>Approximately 10 minutes</p>
        </li>
        <li>
            <p><span>Preparation: </span>5 minutes</p>
        </li>
        <li>
            <p><span>Cooking: </span>5 minutes</p>
        </li>
    </ul>
    
    Marked as helpful
  • Sultan Farrel•110
    @SultanFarrel
    Submitted over 2 years ago

    Responsive landing page using Bootstrap

    #bootstrap
    1
    Ahmed Aziz•90
    @Abo3bazez
    Posted 9 months ago

    Using rem and em instead of pxin CSS offers significant advantages, especially when it comes to responsive design, accessibility, and maintainability. Here’s some feedback on the benefits of adopting rem and em units:

    Advantages: 1.Responsive Typography:

    remand em are relative units, making it easier to create scalable layouts. When users adjust browser settings (e.g., zoom or base font size), designs based on rem/em scale appropriately, whereas px-based designs remain fixed.

    2.Accessibility:

    Relative units like rem and em respect user preferences, especially for those with visual impairments who adjust their base font size for better readability. Designs using px ignore such user-defined settings, potentially causing readability issues.

    3.Consistency Across Devices:

    rem and em units ensure consistent rendering across various devices and screen sizes. For example, using rem for layout dimensions allows elements to scale based on a user’s default font size, creating a more fluid and adaptable design.

    4.Easier Scaling of Elements:

    By using rem for root-level elements and em for nested elements, you can control the scaling of individual components more effectively. This flexibility is helpful for modular design systems, where you want components to be flexible and adapt to their context.

    5.Maintaining Proportions:

    Using relative units helps maintain proportions between text sizes and other layout elements (like padding, margins, etc.), which becomes crucial for responsive designs. This eliminates the need to manually adjust pixel values for different breakpoints.

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