Repository navigation
Conversation
Pass the user menu feature from pages into a reusable header widget example in the page layouts guide. feature-sliced#217
Gaic4o
self-requested a review
October 31, 2026 14:32
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
Closes #217
The issue asks for a HOWTO on wiring the
UserPopupfeature into the reusable app header example (previously shown in the widgets layer docs). That example is no longer on the site, while the page layouts guide already describes passing feature UI via render props/slots but had no concrete header walkthrough.Changelog
widgets/headerexample that optionally rendersSearchBarandNavigation.<UserPopup />through auserPopupprop so each route controls whether the signed-in user menu appears.UserPopupto mirror headers that differ per route.Note for translators: Only the English page was updated; locale mirrors were not changed (an issue can be opened for translator follow-up if needed).