Started out as a smaller change - just to add a button to display & download the Resume results in a nicer way.
That didn't necessarily square that well with our current data architecture.
And as I was playing with the Resume generator (our most complex tool) it became apparent there were still UI & UX issues.
Thinking is - if it's a bit confusing for me, it's probably a lot more confusing for users.
So refactored some UI & UX in a more meaningful way:
the inputs for all tools is now on the left side
the autogenerated, editable output is on the right side
the resume tool builds on that to have separate outputs for each step
the resume tool has a primitive good looking result display; you can even download a .jpg image of your result (no PDF yet; it's a bit more tricky)
Tickets
https://github.com/horia141/auto-perf-review/issues/96 https://github.com/horia141/auto-perf-review/issues/95
Summary
Started out as a smaller change - just to add a button to display & download the Resume results in a nicer way. That didn't necessarily square that well with our current data architecture. And as I was playing with the Resume generator (our most complex tool) it became apparent there were still UI & UX issues. Thinking is - if it's a bit confusing for me, it's probably a lot more confusing for users.
So refactored some UI & UX in a more meaningful way:
Screenshots
Question
If we put a jpg or pdf download button on our free app on Cloudflare, would we be affected by https://news.ycombinator.com/item?id=34639212 https://news.ycombinator.com/item?id=34646208