Repository navigation
refactor(config): use header align instead of spacer - #17
Merged
Merged
Conversation
Scalar Docs PreviewProject Commit Status Preview Updated (UTC): Aug 20, 2026, 10:03 PM To edit notification comments on pull requests, go to your Scalar project settings |
hanspagel
self-requested a review
August 21, 2026 10:08
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
2 participants
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.
The header
spaceris on its way out in favour ofalign: start | center | end. The starter is what new users copy, so it shouldn't be teaching the old API.align: "end"on both header links, spacer droppedscalar-docsskill's header section to matchNeeds https://github.com/scalar/scalar-org/pull/5976 deployed first — until that renderer ships
alignis ignored and both links fall to the left of the header instead of the right