Skip to content

Conversation

@dancormier
Copy link
Contributor

@dancormier dancormier commented Jan 20, 2026

SPARK-75, Figma


This PR updates the Post Summary to the latest SHINE styles. cc @ycantu

image

Note

See also this PR which includes updated visual regression test images.

Deploy previews

TODO

  • Revisit title line height (should be ~20px)
  • Revisit excerpt line height (should be ~20px)
  • Update gutters for content rows
    • 8px: Usercard/stats to title
    • 4px: Title to excerpt
    • 10px: Excerpt to tags
  • Change tag gap to 8px
  • Change score to votes gutter to 8px
  • Change unaccepted answers color to black-400
  • Docs: Add v-truncate class table
  • Change answer left border color to black-200

Open questions/requests

@dancormier dancormier added the do-not-merge Pull requests that are in progress and should not be merged yet label Jan 20, 2026
@changeset-bot
Copy link

changeset-bot bot commented Jan 20, 2026

🦋 Changeset detected

Latest commit: 85d29f8

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@dancormier dancormier changed the base branch from develop to beta January 20, 2026 23:10
@netlify
Copy link

netlify bot commented Jan 20, 2026

👷 Deploy Preview for stacks processing.

Name Link
🔨 Latest commit 85d29f8
🔍 Latest deploy log https://app.netlify.com/projects/stacks/deploys/69827cf370f964000818963d

@netlify
Copy link

netlify bot commented Jan 20, 2026

👷 Deploy Preview for stacks-svelte processing.

Name Link
🔨 Latest commit 85d29f8
🔍 Latest deploy log https://app.netlify.com/projects/stacks-svelte/deploys/69827cf3ffe01600083a30e3

@dancormier dancormier changed the title Spark 75/post summary feat(post-summary): update to SHINE styles Jan 21, 2026
@dancormier dancormier removed the do-not-merge Pull requests that are in progress and should not be merged yet label Jan 30, 2026
@dancormier dancormier marked this pull request as ready for review January 30, 2026 23:32
Copy link
Contributor

@giamir giamir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I skimmed through it and everything seems in order from a code perspective @dancormier. Thanks for tackling this huge component.

The only thing I observed is that for the Svelte component the readableTimestamp tooltip is somehow not tabbable via keyboard.

&&__minimal {
.s-post-summary--content {
width: 100%;
@psx-container-sm: 28rem;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curiosity: How did we settle on 448px as a breakpoint?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I chose it after some trial and error. I figured we needed a breakpoint that was larger than the sidebar width (21.5rem, 344px). I tried that but felt like it looked pretty cluttered at just above that breakpoint. This image is at with the container right at 345px with the breakpoint at 344px:

image

For that reason, I chose the next defined size up in our library (the 28rem). That said, I could be convinced that this breakpoint should match up with the sidebar size. Any strong opinions on that?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me, it is just not one of our "official" breakpoints meaning that it will change the layout at a custom viewport size compared to other things. I guess it is fine. I wonder though if the sm breakpoint (780px one) could have suffice. In the sense that for viewports below that size we show the compact version even if in theory there is the estate to show more.
Anyway I am good with what we have. This is really a NIT. Thanks Dan.

Copy link
Collaborator

@CGuindon CGuindon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YAY!!! Looking good! I only have small nit picky stuff:

  1. I noticed the line-height on the description and title are 18px — which feels a bit tight. We increased the base line-height to 140% which should put the line-height of the description to around 19.6px (we probably rounded up to 20px as that's what I'm seeing on the typography page for Body1). I think we had the line-height not centralized before so wondering if this is a case if it inheriting the custom old vs new here.
Image
  1. I'm seeing a 6px gutter used as spacing in between each line. Unfortunately (sorry), the spacing here isn't all the same. We have 8px, 4px and 10px amounts between each line. (Note the bottom tags container does have a sneaky 2px margin top if that helps or not with the math).

  2. There should be an 8px gap between each tag (instead of 4).

Image Image
  1. The gutter between the score box and the container with the answer data should be 8px (instead of 6).

  2. The font and icon color for the answer data (when not accepted) should be black-400

Image
  1. Similar to how you have the classes listed out at the top, I think it might be worth listing out all the class options above each example (within each section). For example, showing the truncate classes and the state classes (danger, warning, etc) all listed out in a table between description and code example. I found it a bit hard sometimes to see find the "different" classes within the code examples that show everything.

  1. Border left on answers should be black-200 (instead of 150)
Image

@dancormier
Copy link
Contributor Author

Thanks for the review @CGuindon! I've address everything you mentioned. Let me know if I missed anything!

@CGuindon
Copy link
Collaborator

CGuindon commented Feb 2, 2026

@dancormier Sorry I probably miscommunicate the line-height. It looks good on the description now but still needs that 140% on the title of the post as well. Should be 25px based on our new sizing. Looks like you have 20px for both

@CGuindon
Copy link
Collaborator

CGuindon commented Feb 2, 2026

UPDATE: Ellen preferred above and it won't be as common so leaving as is for now.

For the Responsive (small screen) version of the States (with badges like Review, Draft): I'm tempted to keep the badge in line with the metadata and not make the height of the whole post bigger. (Just want to confirm with Ellen she feels the same). My thinking would be to do something more like the Draft example than what we have now — I also realize we didn't have this in the Figma mocked up. (sorry)
Screenshot 2026-02-02 at 1 42 32 PM

Screenshot 2026-02-02 at 1 42 47 PM

@dancormier
Copy link
Contributor Author

@CGuindon sorry for the oversight! I've updated the title to have a 25px (aka 1.563rem) line height.

Copy link
Collaborator

@CGuindon CGuindon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just the Answer icon missing (should be released now in the icons package) but otherwise LGTM 🙌

Copy link
Collaborator

@CGuindon CGuindon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌

Copy link
Collaborator

@mukunku mukunku left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow this is amazing stuff. Great work, Dan!

Left one small comment below but otherwise flawless 🤌

{% else %}
{% icon "Answer16" %}
{% endif %}
{{ data.answers | default: 1 }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be answerCount? On the smallest page size the answer count gets rendered as [object Object]

Suggested change
{{ data.answers | default: 1 }}
{{ data.answerCount | default: 1 }}
Image

* Update post summary visual test regression images

* Update test images
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants