Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 days ago

Pug, SCSS, Vanilla Javascript, Github Pages, i18, Neovim

sass/scss
Hanif Maleki•80
@hanifmaleki
A solution to the Results summary component 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 learned how to use translations instead of hardcoding strings directly in the HTML.

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

In this project I used a very basic translation system. One reason is that I interpreted the Pug files in a simple way, without integrating translation logic directly into them. In the next project, I will explore more advanced ways of compiling Pug templates and add support for translation functions in Pug with JavaScript.

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

Another issue I encountered was that the SCSS watch script did not always work as expected. I plan to debug and improve this setup in my next project.

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 Hanif Maleki'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

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