GH-38209: [Docs] Reduce width of header items and keep header height default (small) on smaller screens

[AlenkaF]

Rationale for this change

The Sphinx theme we have been using (PyData Sphinx Theme) has been pinned to an older version for a while now and with the #36591 we have updated the code and are now using version 0.14.0 for the dev docs.

This PR fixes bugs we have encountered after the PR updating the theme has been merged.

What changes are included in this PR?

• Have default header size for smaller screens and keep it increased for bigger screens.

• Closes: [Docs] Reduce width of header items and keep header height default (small) on smaller screens #38209

[jorisvandenbossche]

How did you decide on the min width of 950? From doing a quick experiment with the "Responsive design mode" in Firefox, I already see it wraparound (causing a very large header) at a width of around 1380 px

[jorisvandenbossche]

Or this is only for the "mobile" layout? (where there is no header at all anymore, except for the logo and expand buttons)

I indeed suggested on the issue to do this in this case, but, we can maybe also already do it when you are on a normal but small screen, i.e. for the cases where all the header navbar items are visible, but start to wrap around because there is not enough space, like:

[AlenkaF]

I am not sure this will help any as the version switcher and search buttons are already causing issues (see pydata/pydata-sphinx-theme#1493 (comment)), but am trying locally now to see.

[AlenkaF]

Ok, setting the minimum width of the screen to have the bigger header height to 1380px gave me two layouts to compare as the limit for the double header is a bit higher:

• just under 1380px and smaller header height:

• just over 1380px and bigger header height:

I agree the smaller header size is better in this case also (double navbar), but the logo is too small to read it and that is not something I would keep.

I propose to have the bigger header height for 1400px but in the case of default header height I would use a different logo: Chevron-only logo

[AlenkaF]

@jorisvandenbossche I changed "Specifications and Protocol" to just "Specifications" and "Language implementations" to just "Implementations". Then the double header comes up at approx 1170px and that is when we default back to the smaller header size.

I would still change the logo to Chevron-only in the smaller header case as the current one is not readable on smaller screens.

[jorisvandenbossche]

I would still change the logo to Chevron-only in the smaller header case as the current one is not readable on smaller screens.

It's only the "Apache" part that is not readable, right? I agree it doesn't look great with the Apache not being readable, but on the other hand I think it is nice you still see "Arrow" .. (but I suppose having a logo with just Arrow without Apache will violate the rules of how the name should be used)

[AlenkaF]

It's only the "Apache" part that is not readable, right?

Yes, correct.

I agree it doesn't look great with the Apache not being readable, but on the other hand I think it is nice you still see "Arrow" .. (but I suppose having a logo with just Arrow without Apache will violate the rules of how the name should be used)

I do not think it is violating, Apache is still there, it is just very small and I think in that case using only chevron without Apache Arrow would be better. But I understand, Arrow will then not be there, which is a bummer.

No rush to change though. We can decide for 15.0.0 and have the header change included in 14.0.0.

[github-actions]

⚠️ GitHub issue #38209 has been automatically assigned in GitHub to PR creator.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 1cc0f14.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details.