Repository navigation
Rebrand as TendUI and share navigation across hosted pages - #1
Merged
Merged
Conversation
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.
TendUI now exposes its renamed Go module, embedded stylesheet and CSS namespace, with migration notes preserving historical release tags. The updated brand kit supplies README logos and the mascot.
Adds the supplied SiteHeader component: consistent navigation, grouped native menus, a compact mobile sheet and icon-only theme actions. AppShell accepts a custom header, and example-handler options let a host website share its navigation, head assets and default theme across demos. The catalog contains 37 compiled recipes.
Validation: local race tests, vet, API/dependency/CSS-budget checks, reproducible templ generation, all 37 recipes, and a clean versioned consumer install passed. Browser and native OS/toolchain verification run in CI. Existing release tags are unchanged; the renamed module is documented as development on main.