Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
14
Comments
8
P

VirginiaPatrika

@VirginiaPatNetherlands230 points

Studied architecture and worked as an architect for 10years. Currently exploring front-end development.

I’m currently learning...

HTML, CSS, Javascript, Sass, Tailwind

Latest solutions

  • Skilled e-learning landing page - Tailwind

    #tailwind-css

    P
    VirginiaPatrika•230
    Submitted 2 days ago

    0 comments
  • Workit-landing page - Tailwind

    #tailwind-css

    P
    VirginiaPatrika•230
    Submitted 7 days ago

    1 comment
  • Suite landing page - Tailwind

    #tailwind-css

    P
    VirginiaPatrika•230
    Submitted 15 days ago

    0 comments
  • Typemaster pre-launch landing page / Tailwind

    #tailwind-css

    P
    VirginiaPatrika•230
    Submitted 24 days ago

    Any feedback is helpful!


    0 comments
  • Art gallery - Responsive Page using HTML, CSS, Flexbox, Tailwind


    P
    VirginiaPatrika•230
    Submitted about 2 months ago

    Any feedback is always helpful!


    0 comments
  • Tech book club landing page - sass/scss

    #accessibility#bem#sass/scss

    P
    VirginiaPatrika•230
    Submitted 2 months ago

    You are welcome to leave any feedback!


    0 comments
View more solutions

Latest comments

  • P
    Schindler Dumagat•340
    @schindlerdumagat
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    In this challenge, I was able to implement everything what I have learned in HTML and CSS. I have implemented semantic HTML, responsive design, Sass and the BEM methodology in styling my elements. I was able to expand my knowledge on CSS and some techniques. I was able to position images in the way I wanted it too. I was able to structure my code for better readability and for separation of concerns.

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

    I found it hard to handle the images in this challenge. I wanted my solution to be as close to the design as possible. Thus, in some breakpoints I wanted my images to appear in the same way as what the design is showing. In some breakpoints, I wanted to hide some parts of the image rather than show the whole image on the page which I have struggled doing. After some googling, I have found some neat tricks to achieve the desired position of the images in a given breakpoint and I was able to implement it in my solution. Though, the footer image is still not the same in the design.

    In the footer background, I overthought about blending the footer's background image and color, I have been finding a way on how to blend it according to the design using CSS blend modes. After some googling, I found out that you only have to use CSS opacity and z-index to implement such background styling.

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

    I wanted to improve the implementation of the images and the number component of the page.

    Listed below are my questions:

    • What is the better way to implement the number component? In my solution, I have a specific class called .number and I just plugged it to an element. Here is my code.
    //CSS
    
    .number {
        display: grid;
        place-items: center;
        position: relative;
        font-family: "Red Hat Display", serif;
        font-weight: 900;
        line-height: 1.5;
        color: #87879D;
        border: 1px solid #D1D1DF;
        border-radius: 9999px;
        width: 56px;
        height: 56px;
    }
    
    .number::before {
        content: "";
        position: absolute;
        top: -80px;
        height: 80px;
        border-right: 1px solid #D1D1DF;
    }
    
    //HTML
    <p class="number main-content__number">01</p>
    
    • What is a better way to handle the hero images? I thought the images in the hero section are decorative, so I have used divs with background images. I could have used img tags with empty alt attribute but I find using divs easier.

    Here is my sample code

    // HTML
    
    <section class="hero">
      <div class="hero__img-mobile"></div>
      <div class="hero__img-desktop--left"></div>
      <div class="hero__text-content">...</div>
      <div class="hero__img-desktop--right"></div>
    </section>
    

    I styled my div images using some CSS background properties and I just hide and unhide some of the images based on the screen width using CSS media queries.

    • What is a better way to implement the footer background image? I have tried to match the footer image based on what's in the design but I wasn't able to achieve that. I think it is because of the provide image assets in the initial codebase provided.

    • How is my folder structure in this challenge?

    Any suggestions and recommendations are also welcome.

    Responsive Meet Landing Page using BEM and Sass

    #accessibility#sass/scss#bem
    1
    P
    VirginiaPatrika•230
    @VirginiaPat
    Posted 3 months ago

    I am not sure I can give you the correct answers to your questions, as I am new in coding but I found your code pretty good. Try to check the 7-1 architecture in Sass for folder and file structure. Well done!

    Marked as helpful
  • abdelrahman ahmed•170
    @a-ahmed151
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    I feel more confident using display flex and display grid. Really proud of the solution I came up with.

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

    This is the 1st time that I add image to a background so I had to learn how to use background image, position and size. It was simple but learn useful tool.

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

    Getting the right text size and line height took some time. Is there a way to find the right text size and line height quickly.

    Frontend-Mentor|Testimonials-grid-section-main

    1
    P
    VirginiaPatrika•230
    @VirginiaPat
    Posted 4 months ago

    Your code looks good, is well structured and responsive. If you are a Pro member you can check the figma file again as it is changed and a tablet layout is also added.You can add another break point as the cards get very narrow while scaling the window.

  • MindOfMine•120
    @MindOfMine
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    I make this one with half baked knowledge about CSS Grid and i think i should learn more.

    Four card feature section solution

    1
    P
    VirginiaPatrika•230
    @VirginiaPat
    Posted 4 months ago

    Your code looks good!

  • P
    Ruben Bardok•180
    @Rubenbard
    Submitted 4 months ago

    responsive product preview card

    1
    P
    VirginiaPatrika•230
    @VirginiaPat
    Posted 4 months ago

    Well written code!

  • Arekpok29•50
    @Arekpok29
    Submitted 5 months ago

    Recipe page project

    1
    P
    VirginiaPatrika•230
    @VirginiaPat
    Posted 5 months ago

    Good work!

  • SPRT-Siomeow•40
    @SPRT-Siomeow
    Submitted 5 months ago

    Social links profile

    2
    P
    VirginiaPatrika•230
    @VirginiaPat
    Posted 5 months ago

    Good job! I would suggest to try using Semantics in HTML(https://developer.mozilla.org/en-US/docs/Glossary/Semantics). It will level your code up.

    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