Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Pod Request Access Landing Page

Igor•230
@For1207
A solution to the Pod request access landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Igor•230
    @For1207
    Posted almost 2 years ago

    Hello, While working on the project, I ran into a problem when trying to follow component sizes in the Figma design file, the proportion between components in the browser looks different. The component sizes in my CSS file are very close to the Figma ones. I couldn't find the reason for this behavior, so I used Figma's dimensions to create a picture in Photoshop. The proportions in Photoshop and in the CSS file are very similar. I can't attach the pictures to this message, so below is a link to the folder with a short video of Figma dimensions and Photoshop picture:

    https://drive.google.com/drive/folders/1rI0qTzxAD8FZcVZnsFFbUzlGTtXuwUok?usp=drive_link

    Thank you!

  • meccoi•160
    @meccoi
    Posted almost 2 years ago

    You're doing well, but your webpage could be more flexible. When I started web development, I used 'position: absolute' a lot too. Over time, I learned that it's better to wrap your content in divs and use 'display: flex' or 'display: grid' for layout. I'm not an expert, but I want to help other developers. just don't over do it yourself, you will get headache..xd

    try chatgpt when coding, it's always helpful when you are having trouble with your code, I used chatgpt alot.

    when using chatgpt it's important to understand the code. you can copy paste as long as you understand the code

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

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

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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