Repository navigation
feat(footer): use @profullstack/footer - #271
Merged
Merged
Conversation
Replaces the hand-written footer / ring nav with the shared @profullstack/footer, rendered on the server so the ring verifier sees it and a package release updates the footer without a redeploy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan95 finding(s) HIGH/CRITICAL: 11 | MEDIUM: 29 | LOW: 55
…and 45 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Replaces the hand-written footer with
@profullstack/footer("latest"), server-rendered.components/layout/site-footer.tsx: the package footer (links: Contact Us mailto, Terms, Privacy, GitHub; ring nav +© Profullstack, Inc.from the package).webring.tsxremoved.MainLayoutis a client component used by ~40 pages, so it cannot render the async server component. The root layout (server) renders<SiteFooter />once and hands it down throughSiteFooterProvider(client context);MainLayoutrenders it withuseSiteFooter(). The Launchpadly badge is kept below it./invite-only(where/307s while the site is invite only) renders<SiteFooter />directly in its server layout, so the ring verifier still sees it.tsc --noEmit, eslint, site-offline tests pass; pnpm 9.15.1 (the Dockerfile version) lockfile,--frozen-lockfileOK.🤖 Generated with Claude Code