Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

no media query

sass/scss
Alrn•50
@Annabelle-Lrn
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

i don't use media query and almost all sizes are in rem except for the borders.

Next time I will try to use the clamp() function.

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

L'image n'apparait pas au déploiement. Tout est ok en local. Au départ elle était en background de la div, j'ai tenté de l'inclure en HTML avec une balise img mais aucun effet. Si quelqu'un a une idée

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

I'm not sure I used the tags correctly for semantics.

Est ce que j'aurais dû englober les balises dans des div? Est ce qu'il vaut mieux appliquer les classes à une div qui contient la balise ou on peut directement mettre la classe à la balise?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Steven Stroud•11,890
    @Stroudy
    Posted 11 months ago

    Amazing job with this! You’re making fantastic progress. Here are some small tweaks that might take your solution to the next level…

    • Using a full modern CSS reset is beneficial because it removes default browser styling, creating a consistent starting point for your design across all browsers. It helps avoid unexpected layout issues and makes your styles more predictable, ensuring a uniform appearance on different devices and platforms, check out this site for a Full modern reset

    • This does not matter that much at this stage but something to be mindful of for SEO(Search Engine Optimisation), <meta> description tag missing that helps search engine determine what the page is about, Something like this <meta name="description" content="description goes here" />

    • I think you can benefit from using a naming convention like BEM (Block, Element, Modifier) is beneficial because it makes your CSS more organized, readable, and easier to maintain. BEM helps you clearly understand the purpose of each class, avoid naming conflicts, and create reusable components, leading to a more scalable codebase. For more details BEM,

    You’re doing fantastic! I hope these tips help you as you continue your coding journey. Stay curious and keep experimenting—every challenge is an opportunity to learn. Have fun, and keep coding with confidence! 🌟

    Marked as helpful
  • demaxs26•270
    @Demaxs26
    Posted 11 months ago

    Hi, you did a great job!

    To answer your question, The image is not displayed because the address is not correct, you need to remove the first slash. The correct address is therefore:

    src="assets/images/illustrationarticle.webp"

    In terms of semantics, you should not use h2 before h1 and not use h4 without using h3 before.

    You can totally apply a class to a semantic tag.

    I hope I was clear in my explanations. Keep it up!

    Have a good day !

    Marked as helpful
  • P
    MikDra1•7,470
    @MikDra1
    Posted 11 months ago

    If you want to make your card responsive with ease you can use this technique:

    .card {
    width: 90%;
    max-width: 37.5rem;
    }
    

    On the smaller screens card will be 90% of the parent (here body), but as soon as the card will be 37.5rem (600px) it will lock with this size.

    Also to put the card in the center I advise you to use this code snippet:

    .container {
    display: grid;
    place-items: center;
    }
    

    Hope you found this comment helpful 💗💗💗

    Good job and keep going 😁😊😉

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub