[
{
"path": ".github/pull_request_template.md",
"content": "\n"
},
{
"path": ".github/workflows/main.yml",
"content": "name: Main CI\n\non:\n push:\n branches:\n - master\n tags:\n - v[0-9]+.[0-9]+.[0-9]+\n - v[0-9]+.[0-9]+.[0-9]+-alpha.[0-9]+\n - v[0-9]+.[0-9]+.[0-9]+-beta.[0-9]+\n - v[0-9]+.[0-9]+.[0-9]+-rc.[0-9]+\n pull_request:\n branches:\n - master\n\njobs:\n lint:\n name: Lint code\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - name: Use Node.js\n uses: actions/setup-node@v4\n with:\n node-version: lts/*\n cache: 'yarn'\n - run: yarn install --frozen-lockfile --prefer-offline\n - run: yarn lint\n deploy:\n name: Deploy to GitHub Pages\n runs-on: ubuntu-latest\n needs:\n - lint\n if: github.ref == 'refs/heads/master'\n steps:\n - uses: actions/checkout@v4\n - name: Deploy to GitHub Pages\n uses: JamesIves/github-pages-deploy-action@4.0.0\n with:\n branch: gh-pages\n folder: website\n"
},
{
"path": ".gitignore",
"content": "node_modules/\n.eslintcache*\n.DS_Store*\nyarn-debug.log*\nyarn-error.log*\n"
},
{
"path": ".prettierignore",
"content": "node_modules/\n"
},
{
"path": ".prettierrc.json",
"content": "{\n\t\"jsxSingleQuote\": true,\n\t\"printWidth\": 120,\n\t\"singleQuote\": true,\n\t\"trailingComma\": \"es5\",\n\t\"useTabs\": true\n}\n"
},
{
"path": "CONTRIBUTING.md",
"content": "# How to contribute\n\nFirst of all, thanks for your willingness to help improve this project! 🎉\n\nWe strive to make contributing to our open source projects easy, in part by following industry standard conventions and workflows, and by making testing and code formatting simple.\n\n_If you’ve never contributed to an open source project before, check out [this project](https://github.com/firstcontributions/first-contributions), which guides people through their first contribution._\n\n## A high-level overview\n\nFrom a high-level, here’s what the contribution process looks like:\n\n1. Choose something to contribute\n1. Fork this repository\n1. Prepare your local environment\n1. Make the proposed changes\n1. Test your changes\n1. Update the docs/README\n1. Format the code\n1. Commit your changes\n1. Open a PR\n1. Iterate through the review cycle\n1. Changes are accepted 🚀\n\nIt looks like a lot of steps, but it’s actually pretty easy. If you’ve contributed to open source projects before, it’s probably a familiar process. Let’s go over each step in more detail…\n\n## 1. Choose something to contribute\n\nCheck out the issues tab if you don’t already have something in mind. We usually keep ideas for future improvements in there.\n\nChoose one cohesive thing to work on per PR, rather than lumping together unrelated changes.\n\n## 2. Fork this repository\n\nThis one is pretty straightforward. If you’re not a designated collaborator on this project (usually reserved for Sparksuite engineers), you won’t be able to create a new branch inside _this_ repository. But, by forking the repository (making a copy in your own account or organization), you’ll be able to create a new branch in the forked repository and commit your proposed changes there.\n\n## 3. Prepare your local environment\n\nStart by cloning the forked repository, then create a new branch off of `master`. Check out that new branch, then hop over to your favorite terminal. At the root of the repository, run `yarn dev` to prepare the repository for local development.\n\n_Note: good branch names are usually succinct phrases that describe the change. So, for example, if a change fixes a typo in the README file, the branch name might read `fix-typo-in-readme`._\n\n## 4. Make the proposed changes\n\nUsing the IDE of your choice, code your changes into existence. Try to follow the conventions and patterns already established in this codebase, particularly when it comes to commenting, spacing, naming, etc. Also, code readability and maintainability are very important; try to avoid “clever” code. During the review process, we’ll help catch anything that doesn’t look quite right.\n\n## 5. Test your changes\n\nYou can do this by running `yarn test` at the root of the repository using your favorite terminal. All PRs have to pass every test before they can be accepted.\n\nIf you’ve introduced functionality that isn’t already covered by a test, which is often the case, you should add appropriate test(s). If you don’t know where or how to add test(s), just skip this step for now and let us know you need help with this part when you open the PR.\n\n## 6. Update the docs/README\n\nMany, but not all, changes will require updates to the documentation and/or README. Take some time to update those as necessary so that they remain accurate and up-to-date.\n\n## 7. Format the code\n\nTo standardize the code’s stylization into our preferred format, run `yarn format` at the root of the repository. Most problems can automatically be fixed, but if some can’t, go ahead and address those manually.\n\n## 8. Commit your changes\n\nCommit your changes to the new branch you created in your forked repository. For organization, you may want to break up your work into multiple commits. Try to use descriptive and succinct commit messages.\n\n_Note: if your commit messages are low quality, we’ll probably end up squash-merging your changes so that your commit messages don’t pollute the `master` branch’s commit history._\n\n## 9. Open a PR\n\nVisit your forked repository and open a new pull request. Make sure the source branch is the new branch you created, and the target branch is the `master` branch on this repository (not the `master` branch on your forked repository).\n\nTry to describe the changes as best as you can in the description, including why you think the change is needed, how to take advantage of the change (if applicable), your design rationale, etc.\n\nIf your PR closes one or more issues, write `Closes #X` for each in the PR description (`X` being the issue number).\n\n_Note: If your implementation or tests are incomplete, we recommend opening the pull request as a draft. This helps indicate there’s still more work left to be done._\n\n## 10. Iterate through the review cycle\n\nOpening a PR will notify Sparksuite’s engineers on Slack, and one of us will review your proposed contribution. If it’s not a good fit for our project, we’ll let you know why and will close the PR. Otherwise, we’ll leave feedback as necessary to help ensure the contribution meets our high standards of quality. Make any requested changes and then let us know when you want us to take another look.\n\n## 11. Changes are accepted 🚀\n\nEventually, the PR will reach a point where we’re satisfied with the quality and we’ll incorporate your work into our project! The changes will usually be deployed with the next published release.\n"
},
{
"path": "LICENSE",
"content": "MIT License\n\nCopyright (c) 2021 Sparksuite\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n"
},
{
"path": "README.md",
"content": "#
Simple HTML Invoice Template
\n\n
\n\n\n\n
\n\nA modern, clean, and very simple responsive HTML invoice template, because sometimes you just need something quick and simple.\n\n- ✨ Simple design\n- 📱 Responsive\n- 🔧 Easily customizable\n- 🌍 RTL support\n\n## Demo\n[Find a demo here](https://sparksuite.github.io/simple-html-invoice-template/)\n\n## How to use\nOpen the [invoice.html](https://github.com/sparksuite/simple-html-invoice-template/blob/master/invoice.html) file and use its HTML and CSS in your application.\n\n## Printer-friendly styling\nBy default, the appearance of the invoice when printed is the same as when viewed on a screen. If the invoice is the primary or only element on the page, you may want to consider removing the box-shadow and border, and letting the invoice extend the full width of the page. That can be accomplished with this CSS:\n```css\n@media print {\n .invoice-box {\n max-width: unset;\n box-shadow: none;\n border: 0px;\n }\n}\n```\n\n## RTL support\nReplace `
` with `
`\n\n## Preview\n\n\n\n## Contributing\nWe love contributions! Contributing is easy; [learn how](https://github.com/sparksuite/simple-html-invoice-template/blob/master/CONTRIBUTING.md).\n\n"
},
{
"path": "invoice.html",
"content": "\n\n\t\n\t\t\n\t\tA simple, clean, and responsive HTML invoice template\n\n\t\t\n\t\n\n\t\n\t\t
\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t
\n\n\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\tInvoice #: 123 \n\t\t\t\t\t\t\t\t\tCreated: January 1, 2023 \n\t\t\t\t\t\t\t\t\tDue: February 1, 2023\n\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\tSparksuite, Inc. \n\t\t\t\t\t\t\t\t\t12345 Sunny Road \n\t\t\t\t\t\t\t\t\tSunnyville, CA 12345\n\t\t\t\t\t\t\t\t
\n\n\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\tAcme Corp. \n\t\t\t\t\t\t\t\t\tJohn Doe \n\t\t\t\t\t\t\t\t\tjohn@example.com\n\t\t\t\t\t\t\t\t
![\"W3C](\"https://img.shields.io/w3c-validation/default?targetUrl=https%3A%2F%2Fsparksuite.github.io%2Fsimple-html-invoice-template%2F\")
\n![\"license\"](\"https://img.shields.io/badge/code_style-prettier-ff69b4.svg\"){kind=icon}
\n![\"license\"](\"https://img.shields.io/github/license/sparksuite/simple-html-invoice-template\")
\n![\"Company](\"./images/logo.png\"){kind=logo}
\n\t\t\t\t\t\t\t\t