Align with upstream Docsy

[sftim]

This is a Feature Request

What would you like to be changed

• Identify areas where this site has behavior different from Docsy
• From those areas, pick a subset where the differences are either unhelpful or do not add value
• One by one, change the site to omit those unwanted differences (adopting the behavior from upstream Docsy)

Why is this needed
We adopted Docsy, originally with a change that left the site looking similar to how it was the day before the switch.
If we can get our site closer to how Docsy usually works, it will be easier to maintain.

Comments
Inspired by #41151 (comment)

/area web-development

[sftim]

Duplicated by #44002

[reylejano]

/triage accepted

[sftim]

/lifecycle frozen

We'd like to ensure that this happens.

[sftim]

I plan to send in some PRs that lay the groundwork for this.

[chalin]

Now that #48721 for Docsy 0.3.0 has been merged, here are some relevant Docsy 0.4.0 resources:

• Changelog#v0.4.0, for tag v0.4.0
• google/docsy@v0.3.0...v0.4.0

Actually, we need to skip to 0.5.1 to be able to use Docsy via an NPM module:

• Changelog#v0.5.1
• google/docsy@v0.3.0...v0.5.1

[sftim]

Relevant to #49451

[sftim]

Next item (but others can land first): #48258

[seokho-son]

Hi @sftim,

I have reviewed the screens from a Korean localization perspective. (reviewed on Feb. 12, 2025)

On the Korean page, there is an issue where the menu is not displayed correctly. Additionally, when resizing the window, the menu shifts, making the content inaccessible.

On the English page, there is also an issue where the language selection option in the menu moves to the bottom left when the browser window is resized.

You may already be aware of these issues, but I wanted to share my findings.
Apart from these, I haven’t found any other issues related to Korean localization yet.

Hope this helps!

[sftim]

@seokho-son can you add this comment to PR #48363 as well?