StackExchange / StackExchange/Stacks
Support deletion state for post summary child answers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 672
- Forks
- 107
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
In one part of the Stack Overflow codebase, we're adding .s-post-summary__deleted alongside .s-post-summary--answer to show that the parent is not deleted, but the child is. It happened to work out nicely:

https://codepen.io/kpollardso/pen/wvXPMeY
The documentation on post summary doesn't list this case on the page. There's also some other states that may come up in the future like ignored, watched, or pinned.
Describe the solution you'd like
I'd like this usage to be added to the documentation for post summary so we can document this as official usage. It would also be appreciated if you could review this usage and make any styling changes necessary for this new use case.
Describe alternatives you've considered
I was reaching for a generic Stacks utility that didn't exist, something like how Bootstrap does card backgrounds/color and card borders. It would be nice to be able to have something more top-level that we could use to designate some components as deleted. Something that would combine the font colors, border colors, and background colors all into one utility class so I can put .s-danger or something on a div and have it look like it's deleted.
Additional context
If you want a live example, this appears when you've saved one of your deleted answers into Saves on Stack Overflow, it's using our PostSummary view component thing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the post summary documentation page and compare its documented states with the linked CodePen and live deleted-answer example. Document the child-answer deletion state, then review whether the existing styling supports it and record any necessary styling changes. Done means the official usage and resulting appearance are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- design, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100