-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Topic Card link list for Product Homepages #2042
Comments
Started work here: https://github.com/smithellis/kitsune/tree/module-topic-list |
Questions: |
@smithellis - I think having the "View All" link lined up at the bottom across modules/boxes would look better, BUT in my experience, it's always a pain in the you-know-what to code it that way. My instinct is to have it placed at the bottom of the list of links for now until we identify any (potential) issues with doing it that way. I'm not 100% clear on your second question, but I would keep the font size and spacing between boxes consistent. If we made anything variable, I'd make the width of each box variable up until a set max-width based on Wide/Ultra-wide screen sizes. |
Ah - yes, my second question was whether I should force these boxes to be square boxes, or if I can allow them to have longer widths. So I think you answered me. |
@smithellis - Went through the existing SUMO UI Design Library to assign some icons to the new taxonomy topics. I found suitable icons for everything except "Accessibility." I went ahead and made a new one for that according to standard examples I found on other sites. I've exported SVGs for each icon and uploaded them to the CX Google Drive (path: Design > SUMO Icons > Taxonomy Icons). Below is a screenshot of each icon with its corresponding Tier 1 topic. |
@smithellis - Adding a few more screenshots to document what we discussed last week:
|
Lookin' good! Is it possible to dynamically calculate how many articles are within a topic so that number can be displayed in the "View All" text? One more thing I don't think we nailed down was how we were determining which three articles were displayed in the preview list. My initial idea was to reference page view data (over a long enough time frame to avoid it possibly changing too often) to pick the three most visited articles. However, we could also work with the Content team to manually pick "keystone" articles and use those instead. |
Right now this is "three articles" but we do/should create another PR to alter after follow up with Content Team. |
Since this work has been backed out from |
Create more informative and useful topic blocks that provide quick access to common needs.
Figma here.
The text was updated successfully, but these errors were encountered: