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

Article preview component

mina•130
@minahopgood
A solution to the Article preview component 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?

This was my first real, on my own project using JavaScript. I fought for my life the whole time, and it still isn't finished. I am currently trying to play around with JS a bit more before I come back to this project because at the moment it is very unfinished -- no active states, a desktop media query that looks crazy. Between trying to get better at JavaScript, I neglected this project as well as all HTML and CSS I put into it. In summary, I have learned the importance of using comments to explain to your future self what the hell your code does.

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

I am not looking for help so much as words of encouragement that JavaScript gets a little less confusing. Thanks lol

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Stephen Adewale•610
    @stephenworld
    Posted about 2 months ago

    You did well on this although there are few stuffs I think you can improve in. Starting with the article content, you should try centering it to the screen by flexing, aligning and justifying the body tag to the center.

    Since, you have just one element inside your body tag, flexing, aligning and justifying it to the center would enable your article element to be placed at the center.

    Should in case if your article isn't properly aligned to the center, you would have to give assign min height of 100svh to your body thank.

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