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

Responsive page using vanilla js (no frameworks)

vanilla-extract
Nikesh W•170
@randomduckduck
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 could have done the implementation by directly defining in html file and adding classes and work would be done.

What I did was rendered entire html part using vanilla js functions, so that you throw any json data to it and it will work.

That includes zero and 1st level comments, user comment box on click of reply button (which is positioned where required i.e. for zero level comment, clicking reply adds userComment box in zero level, and clicking reply on 1st level comment brings userComment in 1st level ).

Proud of this I believe.

Also I defined work in beginning with estimated times for each part. Turns out it took almost only that amount of time (except the delete modal part....took long time to figure out how to make background darken when modal comes)

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

Delete modal (which requires whole background to darken) was something I never did, and took long time to figure out how to do it on my own. Now that I did it, next time would be pretty easy.

Using vanilla js was a challenge in itself. Though I enjoyed it, and feel much under control than say any framework as i am directly communicating with browser.

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

JS wise - none

CSS wise - feedback appreciated on what could be better.

Help me by figuring out how to make profile icons line up with the vertical bar. For different screen sizes, it offsets. Maybe that.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Nikesh W'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 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.