Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

๐Ÿ’•Animated News homepage Bootstrap๐Ÿ’•

Saad Hishamโ€ข1,770
@Saad-Hisham
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there๐Ÿ™‹โ€โ™‚๏ธ i really enjoyed solving this feedback is welcome

Code
Couldnโ€™t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted over 1 year ago

    Hey there! ๐Ÿ‘‹ Unfortunately, there are countless things that need to be improved that I would not expect at this challenge level...

    For example:

    • This should be a header element and not a div.
    • Company logo alt descriptions should NEVER โŒ be "logo"; it should always state the company's name.

    • Your nav button is inaccessible โš ๏ธ. This because you built it using a div (<div class="open-nav-div">) when it should off been built using a button.

    • The list items inside the nav menu should be wrapped inside an anchor element in order for them to be interactive.

    These are just a few things that need to be fixed... there are a whole lot more things that need improvement.

    I strongly recommend checking out https://web.dev/learn/html/ to enhance your web development knowledge. This resource can be instrumental in helping you avoid the types of mistakes that may arise in your future projects.

    Upon reviewing your profile, I've noticed that you appear to be rapidly tackling various challenges, with near-daily postings. It seems that your primary emphasis is on animation rather than the quality and accessibility of your code.

    As a web developer, it's crucial to make quality code (error free, semantically correct, proper usage of elements, etc...) and accessibility your top priorities. These aspects are what distinguish an average developer from an outstanding one.

    If you have any questions or need further clarification, feel free to reach out to me.

    Happy Coding! ๐Ÿ‘พ

    Marked as helpful
  • Mascud Abdiwahabโ€ข170
    @mesutabdiwahab
    Posted over 1 year ago

    liked it, mate.

  • mihapehlicโ€ข70
    @mihapehlic
    Posted over 1 year ago

    Teach me Sensei!

  • CodeBotโ€ข200
    @Emperor-Shadow
    Posted over 1 year ago

    Amazing as always

  • Amirhosein Fallahanโ€ข240
    @PartialTruss
    Posted over 1 year ago

    fantastic๐Ÿ˜๐Ÿ˜๐Ÿ˜๐Ÿ˜๐Ÿ˜๐Ÿ˜

  • Paul Ogbonnaโ€ข100
    @AcerNg548
    Posted over 1 year ago

    Love the animation

    What package did you use please?

  • saddamjonโ€ข610
    @saddamjon1
    Posted over 1 year ago

    Hello, Saad Hisham, make it a little lower, the rest is great

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

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