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

Coming soon page with grid & Constraint Validation API

devusexu•130
@devusexu
A solution to the Base Apparel coming soon page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I try my best to pixel perfect it under 1440 x 800 and do some trade-off(just center some stuff and adjust grid columns actually) for bigger screen size since I don't wanna enlarge the hero image.

I would love to know more about how to layout with grid.

Looking for any comments or sharing of your solution!

References: Client-side form validation

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • IryDev•1,580
    @IryDev
    Posted almost 2 years ago

    Hey @devusexu you really managed to pixel-perfect it I'm impressed 😄.

    Great job on completing the Base Apparel Coming Soon Page challenge. It's clear that you've put a lot of effort into your implementation. Your approach to adjusting the layout for different screen sizes is quite effective. Now, let's discuss your questions about layout with grid and offer some suggestions.

    Firstly, your use of grid for layout adjustment is well-done. By applying a responsive grid layout, you're able to ensure that your page looks good on various screen sizes. Your media queries are properly utilized to adapt the layout based on the screen width, and your grid-template-areas effectively organize the logo, hero, and main sections.

    A couple of points to consider:

    • Grid Area Names: Your choice of grid area names ("logo", "hero", "main") is a good practice as it makes your CSS easier to understand and maintain.

    • Consistent Naming Conventions: Keep up with consistent naming conventions, as you've done with .logo img and other elements. This makes your styles more organized.

    • Centering and Alignment: In your CSS, consider using justify-self and align-self properties for more precise control over centering and alignment within grid cells.

    • Image Accessibility: When using images for important content, such as the logo, it's recommended to provide an alt attribute that describes the image for accessibility.

    • Avoiding Redundant Selectors: You've used multiple body selectors for setting fonts, background, and layout. Consider grouping these properties together to avoid redundancy.

    • Responsiveness: You've effectively used the max-width property for the body element to control the overall width of the content. This helps maintain readability and aesthetics on larger screens.

    • Overall, your approach is solid, and your attention to detail in both design and coding is evident.

    Happy coding!

    I hope you'll find this helpful and your solution is great😁

    Marked as helpful

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

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