-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Include fixed navbar for anchor position calculation in docs. #52016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
nice. We need to improve the workflow (or at least documentation) for site layout changes. CC: as discussed recently @mik-laj ! |
|
@potiuk was this deployed? I still see the problem. |
|
Not really - it needs to be cherry-picked I think to 3-0-test, because we build documentation from there. |
…ache#52016) (cherry picked from commit d8086e6) Co-authored-by: Josef Šimánek <josef.simanek@gmail.com>
|
Cherry-picked here: #53581 |
|
Let me try to rebuild the site and see :) |
|
OK. there is just one clarification added in 3.0.3 branch - so I can safely rebuild the docs. Let me try. |
|
Ach .. not that easy... Have to fix an error in our workflow :) |
|
PR to fix the workflow here: #53582 |
|
Good luck 🙏. |
|
Seems it works on staging. Rebuilding it on live site. |
|
Nice... It works ! Thank you! I miseed we needed to deploy it :) |
|
I can confirm, all good on my side. 💪 |
During work on some docs changes, I have noticed anchor links are partially broken, since they scroll to content hidden behind navbar.
currently navigating to https://airflow.apache.org/docs/apache-airflow/stable/index.html#workflows-as-code shows
with this fix, it scrolls properly
I have fixed also missing top padding (due to banner). I wasn't able to find out logic behind loading the banner, but it is fixed 40px in all viewports (seems so). I have added it whenever needed for calculations and made clear comments on what's happening. In case of banner is removed, those number should be recalculated, there is probably no simple automated way currently to do that.
This whole problem could be fixed also by making content own scroll context (instead of fixed navbar), but it will involve a lot of layout changes I'm not brave enough to provide (I wasn't able to find out even basic layout setup). This fixes the problem with minimal code changes.