Skip to content

docs: group browser API pages into a Browser APIs section#5647

Draft
mcollovati wants to merge 4 commits into
mainfrom
refactor/browser-features-section
Draft

docs: group browser API pages into a Browser APIs section#5647
mcollovati wants to merge 4 commits into
mainfrom
refactor/browser-features-section

Conversation

@mcollovati

Copy link
Copy Markdown
Contributor

The Flow Advanced Topics section had grown into a catch-all of ~31 unrelated pages, making cohesive browser/web-platform API references (Clipboard, Geolocation, Page Visibility, Wake Lock, History, Fullscreen, Web Storage) hard to find.

Move those seven pages into a new Browser APIs section placed right after Forms & Data Binding, ordered alphabetically by title, and update the History API cross-reference in Updating URL Parameters to point at the new location.

The Flow Advanced Topics section had grown into a catch-all of ~31 unrelated pages, making cohesive browser/web-platform API references (Clipboard, Geolocation, Page Visibility, Wake Lock, History, Fullscreen, Web Storage) hard to find.

Move those seven pages into a new Browser APIs section placed right after Forms & Data Binding, ordered alphabetically by title, and update the History API cross-reference in Updating URL Parameters to point at the new location.
@github-actions

github-actions Bot commented Jun 10, 2026

Copy link
Copy Markdown

Preview Deployment

This PR has been deployed for preview.

URL: https://docs-preview-pr-5647.fly.dev

Built from 041a505

Pages under the new Browser APIs section repeated "API" in their navigation titles (Clipboard API, Geolocation API, and so on), duplicating the section name.

Shorten each subsection title to just the feature name (Clipboard, Geolocation, History, ...). The in-page headings and SEO page titles keep the full "... API" name for clarity and search.
The main heading on each Browser APIs page still repeated "API" (Clipboard API, Geolocation API, and so on), duplicating the section name.

Shorten each page heading to the feature name, preserving the version badges on Fullscreen and Page Visibility.
These three Browser APIs pages lacked the version badge that Fullscreen and Page Visibility already had, even though all were introduced in the same release.

Add the [since:com.vaadin:[email protected]] marker to their headings for consistency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant