Add DANG footer badge#70
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.
Original request
Add one more badge in the footer for dang.ai using the provided light and dark theme variants, use
$pr-workflow, and do not add a blog post.Summary
Adds a DANG.ai verified badge to the public landing page footer badge group so visitors can follow the footer badge to DANG.ai.
What changed
apps/web/components/landing-page.tsxwith the provided light and dark hosted badge image URLs.DangBadgefooter component that switches between the light and dark badge images using the existing Tailwind dark-mode pattern.FooterBadgesgroup after EarlyHunt and before OpenHunts.apps/web/components/landing-page.test.tsxto verify the DANG link, rel attributes, image URLs, dimensions, and light/dark visibility classes.Reasoning
The implementation follows the existing hosted footer badge pattern instead of introducing a new badge abstraction for a one-off addition. The link uses
rel="dofollow noopener noreferrer"to preserve the requested dofollow intent while matching the repository's external-link safety convention used by other dofollow badges.Blog post
Skipped. The user explicitly requested that no blog post be added for this badge update.
Validation
npm test -- apps/web/components/landing-page.test.tsxnpm run lintnpm run typechecknpm testLint and testDeploy PR environmentPlaywright e2ehttps://xpenser-pr-070.cleverbrush.comxpenser-web-pr-70: recent trace sample present and no recent error traces found.service.namevalues forxpenser-web-pr-70were available in those signals, so there were no service-specific log/metric records to inspect.Screenshots / Preview
Preview QA confirmed:
Verified on DANG!linking tohttps://dang.ai/.https://assets.dang.ai/badges/dang-verified-light.png,width="260",height="94",block ... dark:hidden.https://assets.dang.ai/badges/dang-verified-dark.png,width="260",height="94",hidden ... dark:block.Screenshots captured during agent-browser QA:
/tmp/dang-footer-qa/dang-footer-light.png/tmp/dang-footer-qa/dang-footer-dark.pngChecklist