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

Articles Preview Component

why-not-phoenix•330
@why-not-phoenix
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 is one for the future tbh. It is definitely incomplete. Too long and unnecessarily complicated codes, buggy Js, I'm very displeased with myself and the only reason I am submitting this is cos I am tired of looking at it and I want to clear my head before coming back. Am I the only one that feels Bootstrap might be restrictive especially here cos we're trying to style to fit something rather than creating our own from scratch? Nothing went well here and I am not happy but I'll take solace in the fact that this is my first Js challenge. Can only get better from here right? I'll update this in the future when I am sure this will all look so basic to me. For now, enjoy this mess and please point me in the right direction. Thanks!

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

Everything!!! Read Above.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gwen-lego•270
    @Gwen-lego
    Posted 6 months ago

    Hi there,

    I want to congratulate you of acknowledging the fact that you were stuck with the project, and that is was time to let go and move on: "I am tired of looking at it and I want to clear my head before coming back". I realize that sometimes unfinished projects, means we need to learn more or something else, so better moving on that getting stuck in this bad relationship :)

    You submitted something that looks good to me. I haven't learn bootstraps or any library yet and find it easier to stick with pure JavaScript only, as it's easy to get confused especially on the first project.

    Question? do you think using your function applyclass() is easier using bootstraps than sticking with CSS.

    Good work, stay positive, as you said, yo will do it again eyes closed in couple months.

    Gwen

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