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

Responsive landing page using Grid, Flexbox, SASS and JavaScript

sass/scss
Alessandra Casole•60
@alessandra-casole
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I hope it will be useful for you! Any feedback is welcome to improve me

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 2 years ago

    Hi

    It's really important at this stage to learn how to do a disclosure pattern properly. By that I mean the mobile navigation toggle. This must be done as follows:

    • inside the nav but before the list of links have a button
    • this button must have the aria-expanded attribute so it's boolean value can toggle on click
    • the button must be accessibly labelled eg "toggle navigation"
    • inside the button you can have two images if you want but these should be treated as decorative and have pty alt as your button is already labelled

    These steps ensure that the nav can be toggles by all users and that state is communicated to screenreaders

    Other suggestions

    • unless a site is called logo, don't use that as alt text on a logo
    • don't use that awful javascript void thing in anchor tags. Clicking a logo link takes you to the homepage so href is /
    • ideally the alt on logo or label on link if using that method should say "name of site - Home" so the destination of clicking the link is communicated too
    • never style on IDs. That's not what they're for! You shouldn't ever increase css specificity either if you can avoid it. Use classes
    • please Indent your code consistently. It is sooooooo hard to read at the moment! Your code editor can even do this formatting automatically for you
    • read more should definitely be an anchor tag
    • as you've not included links on any other articles, how would users Read them?
    • consider using a list for the list of articles in the new section and the list of articles at the bottom
    • the bottom list of articles is even numbered just like an ordered list
    • numbers like 01 make no sense at all as headings. If using an ordered list they become redundant/decorative and can be aria-hidden. Even if not paragraphs would make more sense than headings
    • if images are meaningful they need proper descriptions in the alt attribute. Briefly describe it like you would if someone can't see it. And don't use words like "image" in alt text (its already an image element)
    • the images appear distorted/stretched when I preview this. Consider using the object fit property
    Marked as helpful
  • Adriano•42,870
    @AdrianoEscarabote
    Posted over 2 years ago

    Hi Alessandra Casole, how are you? I really liked the result of your project, but I have some tips that I think you will enjoy:

    I noticed that you used a button in which case the best option would be an a, because in my head when a person clicks on a button written Read more, he is not confirming a form, or something like, it will be redirected to another page, to read more about!

    To resolve do this:

    <a id="btn" type="submit">Read more</a>

    The rest is great!

    I hope it helps... 👍

    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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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