[x] Include a description of your pull request and instructions for the reviewer to verify your work.
[x] Link to the issue if this PR is issue-specific.
[x] Create/update the corresponding story if this includes a UI component.
[ ] Create/update documentation. If not included, tell us why.
[x] List the environments / browsers in which you tested your changes.
[x] Tests, linting, or other required checks are passing.
[x] PR has an informative and human-readable title
PR titles are used to generate the change log in releases; good ones make that easier to scan.
PRs will be broadly categorized in the change log, but for even easier scanning, consider prefixing with a component name or other useful categorization, e.g., "BaseButton: fix layout bug", or "Storybook: Update dependencies".
A lot of the changes pair with corresponding changes to www, but you can test visual changes to BlockLinkCard in storybook (line clamping, placement of date, line separating items).
Checklist
Description
Address the following feedback:
Instructions to test
A lot of the changes pair with corresponding changes to www, but you can test visual changes to
BlockLinkCard
in storybook (line clamping, placement of date, line separating items).make vue-storybook
Tested in the following environments/browsers:
Operating System
Browser