Skip to content

feat: header facelift #1662

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

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

feat: header facelift #1662

wants to merge 9 commits into from

Conversation

katzino
Copy link
Contributor

@katzino katzino commented Jul 2, 2025

closes https://github.com/apify/apify-web/issues/4926

  • updates desktop/mobile header menu
  • also syncs layout for footer

@katzino katzino added this to the 118th sprint - Web Team milestone Jul 2, 2025
@katzino katzino self-assigned this Jul 2, 2025
@katzino katzino added the t-web Issues with this label are in the ownership of the web team. label Jul 2, 2025
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Navbar Height Issue Causes SubNavbar Overlap

The dynamic calculation for --ifm-navbar-height was removed, hardcoding it to 68px. This causes layout issues when the SubNavbar component renders (which previously increased the height to 123px), leading to the SubNavbar overlapping with main content due to insufficient allocated space.

apify-docs-theme/src/theme/Layout/index.jsx#L6-L19

export default function LayoutWrapper(props) {
const baseUrl = useBaseUrl('/');
const currentPath = useLocation().pathname.replace(new RegExp(`^${baseUrl}`), '');
return (
<div style={{
margin: 0,
padding: 0,
boxSizing: 'border-box',
}}>
<Layout {...props} />
</div>
);

Fix in Cursor


Comment bugbot run to trigger another review on this PR
Was this report helpful? Give feedback by reacting with 👍 or 👎

@apify-service-account
Copy link

Preview for this PR was built for commit 85f13f4 and is ready at https://pr-1662.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 6ad0111 and is ready at https://pr-1662.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 8175151 and is ready at https://pr-1662.preview.docs.apify.com!

@katzino
Copy link
Contributor Author

katzino commented Jul 2, 2025

Cursor complains about overlapping header logic that I removed but I couldn't find such occurrence 😅

Copy link
Member

@hanatsai hanatsai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!! Thank you :)

@B4nan
Copy link
Member

B4nan commented Jul 2, 2025

Cursor complains about overlapping header logic that I removed but I couldn't find such occurrence 😅

The bigger space for navbar is because of pages with the submenu, I guess we are not getting rid of that?

e.g. https://docs.apify.com/academy but also many others, basically everything except landing pages and API docs

@B4nan
Copy link
Member

B4nan commented Jul 2, 2025

This looks completely broken on my end, not sure if it can be some caching issue (I did reload the cache).

image

@B4nan
Copy link
Member

B4nan commented Jul 2, 2025

Also, I am personally not very happy with the decision to move the discord link only to the footer, I'd keep it in the navbar and have a link in the footer.

@B4nan
Copy link
Member

B4nan commented Jul 2, 2025

There are other small issues I see when clicking the preview, just to name a few:

  • layout shift on the sidebar spacing
  • sidebar vertical spacing too huge
  • no animation when toggling the sidebar sections
  • no hover effect on links inside toggled sections in sidebar (only on nested sections, not on the direct links)
  • the whole website was wider, making it smaller is quite a downgrade to me - we actually planned to add another larger breakpoint to show more content when there is enough space

@B4nan
Copy link
Member

B4nan commented Jul 2, 2025

You surely still need the dual value for the navbar height. Just try to scroll on the academy page a bit to see why.

image

vs current version

image

@apify-service-account
Copy link

Preview for this PR was built for commit f90c4d27 and is ready at https://pr-1662.preview.docs.apify.com!

@katzino
Copy link
Contributor Author

katzino commented Jul 2, 2025

I fixed (at least I hope) all pending stylistic issues. For the overall design overhaul I synced with @hanatsai before implementing and those changes were based on unifying the interface across platforms (web, crawlee etc.)

@apify-service-account
Copy link

Preview for this PR was built for commit 5028d01b and is ready at https://pr-1662.preview.docs.apify.com!

@B4nan
Copy link
Member

B4nan commented Jul 2, 2025

it looks like the layout shift on the sidebar is still there. when you open the page, its smaller, then it gets bigger, then if you open one section (with the arrow), it shrinks again. and i'd say its still quite high even in the shrunk form (but i might get used to that 🙃)

Zaznam.obrazovky.2025-07-02.v.16.21.52.mov

@B4nan
Copy link
Member

B4nan commented Jul 2, 2025

also the mobile version has a different menu component, it looks fine except the background on the arrow on click (could be just how it works in chrome, havent tested on actual mobile)

image

@hanatsai
Copy link
Member

hanatsai commented Jul 2, 2025

so we agreed we'll keep wider layout in the documentation and the Discord icons. Here is the Figma file.

@apify-service-account
Copy link

Preview for this PR was built for commit 76af1ee4 and is ready at https://pr-1662.preview.docs.apify.com!

@katzino
Copy link
Contributor Author

katzino commented Jul 3, 2025

All pending issues should have been fixed 🤞

@B4nan
Copy link
Member

B4nan commented Jul 3, 2025

looks good, one more thing, the theme switcher in the footer seems to be positioned weirdly, is that expected?

image

similar change was introduced in the crawlee docs, there we have it on the left side under the logo and it looks much cleaner:

image

@katzino
Copy link
Contributor Author

katzino commented Jul 3, 2025

In designs it looks better with more narrow columns. I don't think we can you the same setup as with crawlee since more than 3 columns wouldn't just fit it. @hanatsai what do you think?
Screenshot 2025-07-03 at 11 17 58

@hanatsai
Copy link
Member

hanatsai commented Jul 3, 2025

yes, I think the position is not a big problem here. Because documentation has more items.

@B4nan
Copy link
Member

B4nan commented Jul 3, 2025

It's not a big deal, but I also think this will end up reported in #bugs channel eventually 🙃

In designs it looks better with more narrow columns.

In that screenshot, the columns don't have the same width, that also doesn't sound like a good practice to me.

Copy link
Contributor

@webrdaniel webrdaniel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just found two nits for the mobile menu.

  • There is a double scrollbar
  • When searching the menu does not close
Screen.Recording.2025-07-03.at.11.59.19.mov

@katzino
Copy link
Contributor Author

katzino commented Jul 3, 2025

@webrdaniel both should be fixed now, good catch 💪

@apify-service-account
Copy link

Preview for this PR was built for commit 4b260820 and is ready at https://pr-1662.preview.docs.apify.com!

@katzino
Copy link
Contributor Author

katzino commented Jul 4, 2025

@B4nan I was wondering - when this is merged, do I need to manually bump theme version in apify-cli and apify-client-*? 🤔

@B4nan
Copy link
Member

B4nan commented Jul 4, 2025

Nope, it's all automated.

Co-authored-by: Martin Adámek <[email protected]>
@apify-service-account
Copy link

Preview for this PR was built for commit ecf78187 and is ready at https://pr-1662.preview.docs.apify.com!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t-web Issues with this label are in the ownership of the web team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants