Naw, this title will always be exactly 3 words long. No exceptions. Yep.
Talking about design systems as something apart from content strategy is setting us back *years*—how can a product team choose appropriate components without clearly understanding content requirements (and the "why" behind them)?
-
-
-
A title doesn't line wrap. EVER.
- Show replies
New conversation -
-
-
Who is doing this well? Often see “content requirements” really treated only as “visual limitations the design system places on the content”, like character length or heading levels - which are important, but there’s so much more to consider.
- Show replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is totally a thing in that 1996 book. Silos kill organizational and industry memory.
-
Was just thinking silos.
End of conversation
New conversation -
-
-
Yes I wrote about this a while back, it’s just crazyhttps://link.medium.com/z21lL9B5F3
-
oh I know it sister
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
Oof, that's a tough question. I think the more you can document content guidelines and requirements EARLY in the process—and get alignment by making a case for your recommendations—the better.
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.