Tue, Nov 28
Taglines mentioned in the description are in here.
Mon, Nov 27
Looks good! Thanks @Jdrewniak sorry for all the fiddly-ness!
@Jdrewniak can you show an example of H3s and H4s?
Fri, Nov 24
Thu, Nov 23
Wed, Nov 22
@ovasileva and I jammed on these and put them through a bunch of iterations. Our guiding principles were clarity, translatability, accessible reading level, and carrying over existing labels on similar elements. Here's where we landed:
Tue, Nov 21
Updated logo attatched.
Mon, Nov 20
@Jdrewniak When you're finished reverting this, please assign to me, and I'll work out a design that doesn't break at smaller viewports.
I spoke to @Sarai-WMDE about this this morning, and she mentioned that Codex already has a small option in the scale. I think we just need to spec out which elements take on that style when we implement the new typescale options.
Fri, Nov 17
Draft analysis is here:
Thu, Nov 16
@ovasileva Do we already have a ticket for implementing the skeleton? I will meet with the implementing dev when it's time for implementation. Moving to sign off.
Tue, Nov 14
@KSarabia-WMF @Jdlrobson I had a look at the overflow behaviour of the tools and ToC menu components when the bottom of the menu extends past the bottom edge of the page you can scroll them separately from the main content. In the case of the theme menu, we could apply this behaviour to both the Tools and Theme menus combined. If the combined height of tools plus theme exceeds the total height of the page, you could scroll both as one content area.
Fri, Nov 10
We're hoping to implement a version of this for the type settings interface. See T350612. Here's what that's looking like right now based on the Figma above.
Thu, Nov 9
Mon, Nov 6
RTL illustration here
@Jdlrobson I reviewed this again. The pages referenced above are Foundation-wide legal pages that use of our trademark generally, not the Vector22-specific landscape layout. Those pages are still technically right, even if they don't apply to vector. So If you want to document this, we should do it in a different space. If it's a matter of giving communities guidelines for updating their logos in Vector, it should probably be documented in the design system somewhere with all of the other design specs.
Fri, Nov 3
I looked through the data and visualized it here