You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! Love the CV Manager and I wanted to suggest a small UX tweak for the Featured Projects section.
The Current Situation
Currently, project cards are stuck at a fixed width.
When you have fewer than three projects, or a long description, the layout can feel a bit rigid.
Space that could be used for emphasis or breathing room just sits empty.
The Idea
Let users pick a width per card, something like 1/3, 1/2, 2/3, or full-width.
This would
let people create visual hierarchy (bigger card = more important project)
and make better use of the grid when they have fewer than three featured projects.
Not a breaking change. Just a per-card option with that defaults to the current behavior. 🙂
Technical Pointer
For anyone who wants to explore this, a couple of things that might help:
The projects table could use a new column (e.g., card_width); the schema already has migrations in place
The grid is currently auto-fill based, this could mean switching to explicit columns would make spanning more predictable, but there might be cleaner approaches depending on the goal
That's the gist. Happy to help test or give feedback if this gets picked up!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey! Love the CV Manager and I wanted to suggest a small UX tweak for the Featured Projects section.
The Current Situation
Currently, project cards are stuck at a fixed width.
When you have fewer than three projects, or a long description, the layout can feel a bit rigid.
Space that could be used for emphasis or breathing room just sits empty.
The Idea
Let users pick a width per card, something like 1/3, 1/2, 2/3, or full-width.
This would
Not a breaking change. Just a per-card option with that defaults to the current behavior. 🙂
Technical Pointer
For anyone who wants to explore this, a couple of things that might help:
card_width); the schema already has migrations in placeauto-fillbased, this could mean switching to explicit columns would make spanning more predictable, but there might be cleaner approaches depending on the goalThat's the gist. Happy to help test or give feedback if this gets picked up!
Beta Was this translation helpful? Give feedback.
All reactions