#Config2023 launches bridge the gap between design and development, all in Figma.
→ Dev Mode, a new space for developers
→ Variables
→ Advanced prototyping
→ Auto layout updates
→ Font picker
→ File browser redesign
Plus, we previewed the future of Figma with AI and announced the acquisition of @diagram. https://t.co/RB3qHFSSPz
@jackiechuichui@FonsMans@figma Indeed the overflowing logic seems great, it's the same behavior than code.
I wouldn't need to control number of columns, because I can already do 2 things:
- My items have fixed-widths, with fixed gutters
- My items have "fill-container" widths, with fixed gutters :)
@jackiechuichui@FonsMans@figma My regular use case is:
- I have a grid of elements (see my screenshot) :
- A container verticallly-autolayouted of rows
- Each row is horizontally-autolayouted
Problem: if I want to change the position of one content, it's painful, as it has not a natural "floating" behavior
Using data well is hard.
It's easier to talk up the latest tech or wrap ourselves up in its pretty promises, but those things don't make for better decisions.
Being truly data-informed comes down to internalizing a set of 5 simple yet exceedingly powerful values: 👇
1. Conviction around a purpose, rather than searching for meaning in numbers
Data does not give you a strategy, mission, or values.
“Increasing Metric X” is not a reason for being; a true purpose must relate in some way to creating value for other humans.
Metrics are proxies.
@disco_lu@alexr790 IMO it's separate components. Components are defined by how they mainly work, not how they look like.
But you can have :
- A button component
- A badge component, with 2 variants: one is interactive, the other not.
@efounders Use Tailwind UI as a bootstrap for our Design System. We saved a huge amount of time, and were able to focus on what matters : content, logic and flows (early-stage context)
https://t.co/tCwBlSlTme