Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

CSS grid

Vasile Cosmin•160
@VasileCosmin
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feel free to tell me what i did wrong. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Travolgi 🍕•31,300
    @denielden
    Posted over 3 years ago

    Hi Vasile, good job!

    To center the elements on the page try using Flexbox, it can help you better: give the flexbox and height properties to the body and remove margin from the main tag.

    Read the guide -> Flexbox

    Note: Flexbox aligns to the size of the parent container.

    You can use the vh measurement for the height... Viewport Height handles the sizing of an element in relation to the height of the browser window.

    Tip of graphic design: With font-family:" Big Shoulders Display ", cursive the browser will use the Comics Sans font when it doesn't find the first font indicated (you can seen during loading) ... for the designer it's a really awful font!

    I would rather replace it with a font-family:" Big Shoulders Display ", sans-serif much more similar to the primary font.

    Hope this help ;) And keep it up!

    Marked as helpful
  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted over 3 years ago

    Hello VasileCosmin,

    I have some suggestions:

    • For any decorative images, each img tag should have empty alt="" and aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images.
    • You can add a <h1> with class="sr-only"(Hidden visually, but present for assistive tech).
    .sr-only {
    	border: 0 !important;
    	clip: rect(1px, 1px, 1px, 1px) !important; /* 1 */
    	-webkit-clip-path: inset(50%) !important;
    		clip-path: inset(50%) !important;  /* 2 */
    	height: 1px !important;
    	margin: -1px !important;
    	overflow: hidden !important;
    	padding: 0 !important;
    	position: absolute !important;
    	width: 1px !important;
    	white-space: nowrap !important;            /* 3 */
    }
    

    This fairly modern technique will hide or clip content that does not fit into a 1-pixel visible area. Like off-screen content, it will be visually hidden but still readable by modern screen readers. -You can replace the <h1 > by <h2>. (the heading should uppercase)

    • Swap the buttons for anchor tags. Clicking those "learn more" buttons would trigger navigation not do an action so button elements would not be right.

    • To make the card perfectly in the middle of the page, you can make the< main> element as a flexbox container .

    • border-radius and overflow hidden to the container that wraps all the cards so you don't have to set it to individual corners.

    • Let the content inside the card element dictate the height of it.

    I recommendnot:

    • use pixel for font-size.

    • A general point - try to put classes directly on anything you want to style. Then you won't need as many nested css selectors.

    Hopefully this feedback helps.

    Marked as helpful
  • Luka•320
    @lukakavtarra
    Posted over 3 years ago

    hey =) looks like text max-width on your solution is more than it's on the given design. i don't see any problems there good work

    Marked as helpful
  • darryncodes•6,350
    @darryncodes
    Posted over 3 years ago

    Hi Vasile,

    Nice work on this one - well done!

    You could add transition: ease .3s; to your .btn class to make the hover effect slightly smoother.

    Happy coding!

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

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