viz: drop the badge override — let the OKFlight brand default through - #31
Merged
Conversation
badge = "OKF viz" predates the wordmark: it labeled the sidebar h1 before the badge became the stage About control + modal brand, so the published page still read "OKF viz" where every fresh okflight workspace shows the two-tone OKFlight mark. Unset, the default supplies it.
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
1 participant
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 published graph at kris.net/dotfiles still shows "OKF viz" in the stage control and About modal: this repo's
[display] badgeoverride predates the OKFlight wordmark. Removing it lets the default brand through; verified locally that the regenerated page embedsbadge: OKFlight. okflight.toml is in pages.yml's trigger paths, so merging redeploys.