Closed jknilans closed 11 months ago
for reference, the card docs guidelines state:
A card features header, body, and footer sections. Those sections should include a limited amount of content to ensure that the card doesn’t become too tall. ... Don’t use too much content in one card, distribute extra content to other cards or somewhere else on the page.
Hey @bennypowers! Thanks for your response. :) I referenced that guideline in the "Additional context" section of my issue, however my content writers want a firm max limit as constraints are helpful to work with and force clarity in writing.
I gave them what I consider to be reasonable max limits, however I'm not sure if my suggestions are more or less restrictive than what the original intention was for each component.
Just bumping this to make note that this has been placed in the next milestone. Next steps:
Thanks for the update!
Making a checklist here to go through:
For each we need to
Added tile
to the list and checked it off because character counts will be there once docs are published.
@nikkimk, these character counts include spaces. Let me know if you need additional copy or info.
Announcement (pulled from the Personalization patterns page)
Card I think this will need a character count because it was given as an example in this issue.
Disclosure
Jump links
Link I don't think an inline link would need a max character count.
Progress steps Step indicator labels: 20 characters (maximum of two words)
Promo
I'm working on the design of inline promo for the Caterpie milestone, and I'll add a character count as part of the docs.
Sticky card
Video player pattern
Since CTA can be added to the footer for both cards and sticky cards, let's use the default CTA's character count.
Card's footer: 55 characters
Sticky card's footer: 55 characters
Yes, the element and pattern versions of card can use the same character count. I'll keep that in mind for other components that are elements and patterns.
Description
There is little guidance for how many characters are acceptable to use in each web component; it would be helpful to provide UX guidance for each component on what the max acceptable character count should be.
For example, since we don't provide suggested character limits, it's not uncommon to see some websites that have upwards of 10 lines of body content in a card, whereas other websites have 4 lines of content per card. By providing content guidance, teams could learn that maybe there is a better component to use to get across the same point, or be more concise in their content writing.
Also, by providing an upward limit on character counts, users may have an easier easier time finding what they're looking for as they scan content for what they're interested in.
Suggested solution
Provide suggested max character limits in the documentation for the following web components:
Example API
No response
Additional context
Our team occasionally uses the web components, and after recently working with a content writer, we were asked about max character limits for the components we're using. We checked with other teams and with the content team found that there doesn't seem to be a consensus on what the max limits should be for the marketing components. For example, in the documentation for cards, the closest suggestion is "A card features header, body, and footer sections. Those sections should include a limited amount of content to ensure that the card doesn’t become too tall." Leaving the user to determine what is "limited" or "too tall" could result in cards that are actually not limited and too tall.