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

invoicing app with MessageChannel and Css Print

accessibility
ndimah•300
@jay-ike
A solution to the Invoice app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ndimah•300
    @jay-ike
    Posted over 1 year ago

    thank you for your feedback kent.

    • First of all the technology used is vanilla javascript allthough I've recently refactor it to use Solidjs for a better reactive system than what I've implemented
    • Then I want to say that we have an empty state because in the zip file I had there was no data.json file
  • Kent Ntwari•100
    @kentntwari
    Posted over 1 year ago

    Looks pretty nice once you open the site and create an invoice. The process is nice as well with the way you broke the creation process in steps. My two cents for feedback though would be:

    1. Add some description to your solution. I am curious to know the technology you used to build this site and what you used to persist the invoices. There is a way you can edit your solution and add all this markup for everyone else to see because what you created is really worth it
    2. The screenshot of your solution displays the empty state with the "Nothing to see here" illustration. You should checkout the starter code of this challenge: there is data.json file with some invoices you can prepopulate. Once that's done and all, you scan regenerate the screenshot of your site and it should look pretty good.

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

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.

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