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

Interactive comments section

accessibility, bootstrap, react, sass/scss
Okogbo Faith•140
@faithandjs
A solution to the Interactive comments section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What did you find difficult while building the project? I had to write a lot of functions and it was really complex and confusing at a point and linking the forms together and to their respective comments was challenging at first. This project taught me to comment on my code because I couldn't work on it for about a month and when I came back to it, it was really hard to read and remember anything. Which areas of your code are you unsure of? The part where I used a lot of functions. Do you have any questions about best practices? Not really, i would like to see other solutions though

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Prabhash Ranjan•2,540
    @besttlookk
    Posted over 3 years ago

    Hi, Just completed this challenge. There are few things i like to point out about yours .

    1. You did not gave max-width to the contnet area. I have ultra wide screen and whole card is stretched out. I always do this make responsive
      width: 90vw;
      max-width:460px;
    
    1. For voting a user should not vote numerous times. At max one upVote and one downVote.
    2. Give cursor:pointer for delete on edit link.
    3. On reply. there is bug with username.

    Here is my solution. I tried to thoughof all possible scinaros . if i missed anything do let me know. Also if you need any help in any part, feel free me ask. I am no expert but always happy to help.

    https://www.frontendmentor.io/solutions/full-feature-comment-section-using-next-styledcomponents-rJbb4W5Gq

    Good Luck #happyCoding

    Marked as helpful
  • Okogbo Faith•140
    @faithandjs
    Posted over 3 years ago

    Hi, thank you for your comment. I'll fix up the bugs and make necessary changes.

    I was trying to make the webpage scroll to the form and auto focus when a new form is presented but I couldn't. I see that you did not do that, was that intentional and do you know how I can do that?

    Thanks

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.

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