- The "Save" icon is tiny and hard to find in some layouts (right hand gutter, near the top and far away from your linear text entry flow). It's a floppy disk! Navigating away does not warn you that you have unsaved edits.
- Issues can be converted to Stories after review. Great. But there is no indication that the Issue has been converted, and reporters can continue to edit Issues, and the changes are not synced to the new Story item. This was very confusing for some people, and created way more friction than could be reasoned away.
- Information density was OK with a small quantity of items/comments/etc, but too sparse for a confident view with large quantities.
We moved this project over to test GitHub Projects, which is an improvement but also lacking in some important (different) areas.
...
All of these tools have always sucked on some or several dimensions. It's probably impossible to not suck.
JIRA can be made to work, though I will never do so again.
Pivotal Tracker is solid but overwhelming for reporters/casual users, and requires custom code to integrate with GitHub (but API is decent).
Sometimes I miss Trac and Redmine, if only because anything that bothered me enough could be fixed in our self-hosted instance.
Would be interested to hear some opinions from people who have used it.
This is true at first. I can see it being pretty daunting to come into an existing project and trying to understand the styling of components. Starting from scratch and easing it into an existing project is much easier imo. That's what I did for a personal website. Now that I understand it and have converted the entire website to Tailwind, I don't want to switch to anything else going forward.
Here's a Prettier plugin that sort the classes to keep everything consistent across components: https://github.com/tailwindlabs/prettier-plugin-tailwindcss
Tailwind combined with classnames (https://github.com/JedWatson/classnames) makes it really easy to have conditional styling based on component state.
I understand there's the Rust Book, Rustlings, and Rust By Example at https://www.rust-lang.org/learn. Are there other good resources? Does anyone have a strong suggestion on which of those official resources I should start with?
It definitely took some time and learning but now I have 6 Rust API microservices, a few scheduled/queue-reading services, and a shared library for common models/utils/providers.
Traefik can read labels applied to Docker containers (easily done with docker-compose) and setup the proxy for you as containers come and go. Even maintains the Lets Encrypt certificates seamlessly.