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

Interactive Comments Section

react, typescript, vite, bem
P
Abouelhouda Iliass•480
@ilyesab
A solution to the Interactive comments section 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?

I'm just proud of being able to complete this project with all the requirements. I used only front end tools. so there is no database. the data is imported from the json file on first run. stored in React State and synchronised to local Storage to have some kind of persistence state.

This is the first project of intermediate level that I tackled and I got a say the difficulty does show. it's close to a functional app. it is essentially a small CRUD app for Comments.

The thing that I'm proud of is managing the state using a reducer function and the useReducer react hook. the state along with the dispatch function provided by the hook. are passed to all components in the tree using a context provider.

Next time I tackle a project of this level I'd like to spend more time thinking about how to design different components to build the app in a simple way.

What challenges did you encounter, and how did you overcome them?

There were a lot. the first one was which components to create.

for that I created the following components:

  • ComponentWithReplies: this component we pass it one comment object and it renders the comment along with it's replies offseted a little bit to the left to indicate ownership.
  • Comment: this is the component used to render comments and replies alike. from the interface there is no practical difference. so I made it work for both of them.
  • AddComment: this is the form under the bottom of the page used to add a comment. but it also shows when the user is replying to a comment.

There are other low level component such as the Vote, PostButton, ActionButton and also the Comment Component is further divided into subcomponents that was a little refactoring because it was getting quite long.

Other challenges that I faced was thinking about the UX. for that I implemented some features that I thought were good from my own experience browsing the web:

such as clicking outside the comment while editing or replying will cancel the editing or replying, when editing or replying the textarea is autofocused and the cursor is at the end. and so on.

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

I'd like help to know if my code is readable, understandable and follows best practices.

Any feedback is of course welcomed!

Thank you for viewing my solution!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Abouelhouda Iliass's solution.

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.