[OUDS] feat(docs): added browserslistrc callouts

[duvalale]

Related issues

Closes #3594

Description

Added callout to suggest using OUDS .browserslistrc file to introduction and browsers and devices page, and all components pages using floating labels.

Checklists

• I have read the contributing guidelines
• My change follows the developer guide
• My change follows the page structure defined in [OUDS] Create a component page template for the doc #3045
• Title and DOM structure is correct
• Links have been updated (title change impacts links for example)

Progression (for Core Team only)

• Code review
• Commit on ouds/main following conventional commit

Live previews

• https://deploy-preview-3714--boosted.netlify.app/

[netlify]

✅ Deploy Preview for boosted ready!

Name	Link
🔨 Latest commit	99e6198
🔍 Latest deploy log	https://app.netlify.com/projects/boosted/deploys/6a6b62d676f8ca000812f68c
😎 Deploy Preview	https://deploy-preview-3714--boosted.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR updates OUDS Web documentation to better communicate the recommended target browser list (via the repo’s .browserslistrc) and to warn users about floating-label compatibility issues when using default Browserslist/Autoprefixer settings.

Changes:

• Added a “next steps” link to the Browsers & devices page from the Introduction.
• Added an informational callout on Browsers & devices recommending adoption of the project’s .browserslistrc.
• Added warning callouts to all floating-label components (text input, text area, select input, password input) linking back to Browsers & devices.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
site/src/content/docs/getting-started/introduction.mdx	Adds a navigation link to browser/device support docs.
site/src/content/docs/getting-started/browsers-devices.mdx	Adds a callout recommending use of the repo .browserslistrc for SCSS projects.
site/src/content/docs/components/text-input.mdx	Adds a floating-label compatibility warning pointing to Browsers & devices.
site/src/content/docs/components/text-area.mdx	Adds a floating-label compatibility warning pointing to Browsers & devices.
site/src/content/docs/components/select-input.mdx	Adds a floating-label compatibility warning pointing to Browsers & devices.
site/src/content/docs/components/password-input.mdx	Adds a floating-label compatibility warning pointing to Browsers & devices.

[MaxLardenois]

Nice work, I suggest a toned-down wording ;)

[MaxLardenois]

Actually I would put the inputs callouts after the examples, because as it stands we have a lot of callout one after another and nothing stands out.
wdyt @louismaximepiton

[louismaximepiton]

I fear that having it after the example will be forgotten by many, including us, by I agree that nothing stands out right now. I'll think about a better solution if I have time

[vprothais]

Actually I would put the inputs callouts after the examples, because as it stands we have a lot of callout one after another and nothing stands out. wdyt @louismaximepiton
I agree with you, we often have multiple callout one after another and it doesn't helps for readability. I think having it in the overview here is the good place. I don't know how to enhance this situation globaly. Let's merge like that as the problem is more global than just this callout.

[MaxLardenois]

Actually I would put the inputs callouts after the examples, because as it stands we have a lot of callout one after another and nothing stands out. wdyt @louismaximepiton
I agree with you, we often have multiple callout one after another and it doesn't helps for readability. I think having it in the overview here is the good place. I don't know how to enhance this situation globaly. Let's merge like that as the problem is more global than just this callout.

Approving as is, I will open an issue, maybe we need some designer help on this