Repository navigation
Conversation
|
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.
Use the same filled U+25BE triangle as durable-workflow.com for the SDK switcher. The smaller icon inherits the label color and weight, sits vertically in the middle and follows one normal text space. The label uses the same soft gray and regular weight as adjacent navigation links.
Browser previews in both themes verify the character, color, weight, smaller size, normal space and opening dropdown. The portal build passed and all 18 generated portal pages use the new indicator. The complete portal validation also needs its separately generated API tree; that check was not claimed from the partial local build.
Delivery: Publication is blocked by the shared PHP bootstrap archive returning HTTP 404 before the required hosted documentation and PHP checks can run. The existing repair is tracked in central #400 / #404. No failing check was bypassed; the live site has not changed.