This was my aha! moment where I actually watched someone install and use packages and was like oooh yes, this is both nice and will actually be very helpful. And I have been using emacs since 1998! I find most package pages tell you a lot about the how, but very little about the why on you would want to use them.
I love sites like this. I'm always looking for more apps that let me keep using them even if I stop paying for updates. Adding a $10 monthly subscription will stop me from using most products but I'll gladly pay $100+ for some quality software that I can keep
I've been using Dokku for many years. It's remarkably stable and easy to use. I wrote an extensive tutorial on how to deploy various apps and websites with Dokku in 2018 [1] and I'm sure that following the same steps still works 6 years later.
I'd speculate that their overuse comes from convenience of displaying any message by throwing in a `showToast("Foo!")` opposed to altering each UI component to show the relevant feedback.
That cuts both ways IMO. At least with a toast system I know where feedback appear on a per app basis (or website or whatever). Imagine if every screen, view, list entry, checkbox had its own way of displaying feedback. It would be an enormous amount of overhead.
Toasts should be used if there is no direct relation to or interaction with a visible UI element: notification, heavily asynchronous processes, out-of-view modifications.
ETA: If they actually behaved like that, it would help with OP's issue with them-- pop out of "the toaster", where you clicked to initate the action, so you'd be more likely to notice. Seems his complaint was in large part that they appear somewhere else. (So they're not really "toasts": At least my toaster doesn't have a teleportation function, to make the toast appear wherever the toaster designer has more or less randomly decideded it should. It just pops up the bread in the same old boring position where I know to look for it.)
This looks really well done! I was able to create a simple animation easily even though I don't know anything about animation software.
By the way, your "Features" page is really well made. I would showcase those features on the homepage. I didn't find the list of features until I clicked the link in one of your comments on HN.
You can also make your project more appealing on the homepage by including a looping demo animation (to see what's possible) and a screenshot of the tool.
This is really well made! I know from my experience building Cakedesk [1] that the requirements of invoices vary greatly from country to country and from user to user.
Some things you can add to appeal to more people that are useful to most:
* Keep track of clients and personal info so the user doesn't have to type the address / invoice IDs every time
* Allow users to keep track of which items are paid/unpaid
* Allow users to declare sales tax on the invoices
* Allow users to upload their own HTML-based invoice designs
* Allow users to add subitems to items
Good luck with the project, it looks well-made and it will be useful for many people!
I started similarly. I had built a really simple HTML template for my invoices and I generated them using some CLI scripts and Airtable as a database (to keep track of customer addresses, invoice IDs, etc.).
I didn't want to use a full-on accounting tool where everything is kept in the cloud with expensive monthly subscriptions and using Word or something along those lines also didn't work for me.
