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

Interactive Comments Section Using Vue 3

vue
Aaron Romanick•270
@aaron-romanick
A solution to the Interactive comments section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is another project I used Vue 3 with the Composition API on. I didn't implement too many new tricks, but I did make a conscious effort to utilize grid a lot in my CSS.

  • While there is some animation, there could be a few more ("delete", "updated" actions)
  • If I do a similar project, I think it'd be nice to implement a "View more comment"-type link if the comments get too nested (similar to Reddit).

If you have any feedback/comments on areas I could improve, that would be great too!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Wendy•2,130
    @wendyhamel
    Posted about 3 years ago

    Nice one!

    I like the transitions. smooth, not jarring and helpful for the user to see what's going on. Maybe you can add some subtile transitions on the appearing and disappearing of the modal too.

    I only found small issues. On screens above 770px -> if you edit a comment, the textarea only spans half the width of the card. (it only occupies one grid column)

    And you can hide the resize handle in the bottom right corner of the textarea with resize: none;

    Have fun coding!

    Marked as helpful

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