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

Character Counter (HTML, CSS, JS)

P
Alec•70
@AlecVCodes
A solution to the Character counter 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 very proud with my design specifically. I'm happy I was able to make the design fluid across all different screen sizes by using modern css such as clamp and min/max.

I'm also very happy with how effectively I was able to think through each section of the project and I really feel like I'm improving my problem solving skills.

Something I would change however is to organise better from the start. I did find that I had to re-write parts of my project because I didn't think of potential issues right from the beginning. This lead to some headaches...

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

A couple issues I came across was repeating lines of code way too much. I saved lines of code by making reusable functions to use throughout the project.

I also found it hard to order certain elements within arrays. Especially when it came to showing which letter had the most density and ordering them accordingly. I found that by using the filter and sort methods I was able to overcome this challenge.

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

I would like more feedback in regards to how to make my code cleaner and more readable for others. I think the design/functionality looks fine but I don't think the code is as clean as I'd like it to be.

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 Alec'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.