Skip to content

Conversation

@reidbarber
Copy link
Member

@reidbarber reidbarber commented Nov 25, 2025

  • add component page descriptions (appear in search menu cards)
  • fix markdown script's *.md link conversion to work for URLs with no extension and query/hashes
  • open "Related Pages" external links in a new tab and render LinkOut icon
  • fix missing/incorrect "Related Pages" links
  • fix long page titles in OG image generation (avoid overflowing image)
  • consolidate SearchMenu and MobileSearchMenu logic

✅ Pull Request Checklist:

  • Included link to corresponding React Spectrum GitHub Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exists for this component).
  • Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

@reidbarber reidbarber changed the title docs: S2 docs newest testing fixes WIP: docs: S2 docs newest testing fixes Nov 25, 2025
@rspbot
Copy link

rspbot commented Nov 25, 2025

@reidbarber reidbarber changed the title WIP: docs: S2 docs newest testing fixes docs: S2 docs newest testing fixes Nov 25, 2025
@rspbot
Copy link

rspbot commented Nov 25, 2025

@rspbot
Copy link

rspbot commented Nov 25, 2025

@rspbot
Copy link

rspbot commented Nov 25, 2025


export const section = 'Date and Time';
export const group = 'Internationalized';
export const description = 'Calendar systems for international date calculations.';
Copy link
Member

Choose a reason for hiding this comment

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

Image

Now that we have descriptions for each component, could we have the descriptions start from right beneath the component name?

Copy link
Member

Choose a reason for hiding this comment

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

Also putting here since there isn't a good place to comment this but I noticed that some of the descriptions of the aria utilities just say "Implementing collections in React Aria" which doesn't seem right but is probably existing:

Image

The rest of the descriptions seem ok to me, but just wanted to note that some are different from what we had in https://react-spectrum.adobe.com/react-spectrum/index.html (e.g. TagGroup, Tabs, ActionButton, etc) and are a bit long compared to those (and thus end up being cut off). Happy to keep them as is, but just wanted to note the differences

Image

Copy link
Member Author

Choose a reason for hiding this comment

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

Now that we have descriptions for each component, could we have the descriptions start from right beneath the component name?

I think that makes sense, we'd need to fix this in S2 so we can handle that separately.

Also putting here since there isn't a good place to comment this but I noticed that some of the descriptions of the aria utilities just say "Implementing collections in React Aria" which doesn't seem right but is probably existing:

Will push a fix.

The rest of the descriptions seem ok to me, but just wanted to note that some are different from what we had in https://react-spectrum.adobe.com/react-spectrum/index.html (e.g. TagGroup, Tabs, ActionButton, etc) and are a bit long compared to those (and thus end up being cut off). Happy to keep them as is, but just wanted to note the differences

I was looking at the JSDocs and forgot about those. I'll update some of these to be shorter!

Copy link
Member

Choose a reason for hiding this comment

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

do you have any examples where I could test this one?

Copy link
Member Author

Choose a reason for hiding this comment

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

Comment on lines +412 to +414
function isExternalUrl(url: string): boolean {
return url.startsWith('http://') || url.startsWith('https://');
}
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if we'll need to change this when we have the 2 separate domains with links between each. I guess I'd be fine if it would open a new tab but happy for the team to weigh in. I could see an argument that links pointing to either domain should keep you in the same tab

Copy link
Member

Choose a reason for hiding this comment

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

Yeah we'll need to update this. All links will be absolute after my PR is merged. There is also a similar utility in Link.tsx already (which I updated in my PR).

@rspbot
Copy link

rspbot commented Nov 26, 2025

devongovett
devongovett previously approved these changes Nov 26, 2025
Copy link
Member

@devongovett devongovett left a comment

Choose a reason for hiding this comment

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

We should standardize on whether the descriptions start with "A component name does X" or just "Does X" (I would vote for the latter). Right now it's a mix.

Also would be nice to make the description lengths more uniform. Right now some are longer than others which looks a little strange.

@rspbot
Copy link

rspbot commented Nov 26, 2025

@rspbot
Copy link

rspbot commented Nov 26, 2025

@reidbarber reidbarber enabled auto-merge November 26, 2025 23:42
@reidbarber reidbarber added this pull request to the merge queue Nov 26, 2025
Merged via the queue into main with commit 69864fb Nov 27, 2025
32 checks passed
@reidbarber reidbarber deleted the s2-docs-newest-testing-fixes branch November 27, 2025 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants