Repository navigation
feat(web): add /ecosystem and /build pages - #38
Merged
Merged
Conversation
/ecosystem lists real, running integrations with KUMPLY's attestation
layer. Today that's one: 0xGasless, described exactly as Aditya
approved ("which runs ERC-4337 account-abstraction infrastructure
(bundler, paymaster, smart accounts) and x402 payment rails on
Avalanche"), with the exact scope he asked for (the check covers
UserOperations under the pilot's API key on Fuji, not 0xGasless's
sponsorship service more broadly), an honest pilot/demo-attestation
status note, and links to the existing blog write-up and its three
Fuji transactions. No "partner"/"alianza" anywhere. No logo image: none
exists anywhere in this repo (checked by filename and by content), so
this ships as name-only, flagged to the user to confirm before Monse
or Aditya see it.
/build lists seven software ideas a builder can put on top of KUMPLY
without custody or personal data, each tagged with its category and
the exact SDK 1.3.0 helper it calls (isPersonAtLeast / isBusiness /
isAgent, re-verified against the published npm tarball, not the repo's
own README). The gas-sponsorship idea links to /ecosystem instead of
repeating that content.
Both pages: Fuji-only, demo-attestation and mainnet-zero-attestations
language, no hackathon/track named, no superlatives, no em dashes.
Linked from the footer's Developers column (desktop nav was already
at 9 links plus wallet/network/language/theme controls); new Footer
"ecosystem"/"build" keys in both message files.
Fixes a real .gitignore bug found while adding this: the generic
`build/` build-output rule was silently matching the new literal
route folder apps/web/src/app/[locale]/build/ (a plain "git status"
after creating the page showed nothing). The fix also needed escaping
the literal brackets in [locale] as \[locale\], since unescaped square
brackets are a gitignore glob character class, not literal text; the
first attempt at un-ignoring the path silently failed for that reason
until checked with `git check-ignore`.
Verified: tsc --noEmit, eslint, and both pages rendered in EN and ES
with run-web (zero pageErrors).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Copies 0xGasless's official light-full-logo.svg and dark-full-logo.svg from their brand kit unmodified. Checked each file's actual fill color before picking one, since the vendor's own "light"/"dark" naming describes the logo's own color, not the background it's meant for: light-full-logo.svg uses a near-white fill (#F6F3EA) so it only reads on a dark background, and dark-full-logo.svg uses near-black (#0B120F) for a light background - the opposite of what the filenames suggest at a glance. The page swaps them with a new reusable .theme-logo--light/ --dark CSS pair (same server-component-safe pattern already used for the footer's own logo, generalized instead of duplicated), verified in both themes and both locales with run-web before committing. /build's ACP-99 validator idea no longer implies KUMPLY's own Compliance L1 is running; it names the check the ValidatorSetManager contract implements and states plainly that the L1 itself isn't activated yet. EN + ES. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Adds both to navLinks (shared by desktop and mobile), with new Navbar.ecosystem/build translation keys (EN "Ecosystem"/"Build", ES "Ecosistema"/"Build"). Verified at a wide desktop viewport (no overflow or wrapping down to the 1450px mobile breakpoint, checked at 1800/1500/ 1460px, EN+ES) and in the mobile slide-out menu (both items render after the stagger-in animation finishes, EN+ES). They were already linked from the footer (previous commit); this adds the primary nav entry point on top, per explicit request. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This branch was successfully 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
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.
Summary
/ecosystem(EN+ES): lists real, running integrations. Today that's one, 0xGasless, described exactly as Aditya approved, with the exact scope he asked for (covers UserOperations under the pilot's API key on Fuji, not a gate on 0xGasless's sponsorship service more broadly), an honest pilot/demo-attestation status, and links to the existing blog post plus its three Fuji transactions. No "partner"/"alianza" anywhere./build(EN+ES): seven software ideas a builder can put on top of KUMPLY without custody or personal data (anti-Sybil airdrop filter, DAO voting, gas sponsorship, AI-agent marketplace, x402 payment APIs, B2B invoicing/payroll, ACP-99 validator gating), each tagged with the exact SDK 1.3.0 helper it calls. The gas-sponsorship idea links to/ecosysteminstead of duplicating that content.isPersonAtLeast,isBusiness,isAgent) re-checked against the actual published@kumply/sdk@1.3.0tarball, not the repo's own README./ecosystemships with the name only, text-no-logo. Flagging this explicitly since you said you'd send Aditya a preview — if he has a logo file, I can drop it in before that happens..gitignorebug while building this: the genericbuild/rule (meant for build-output directories) was silently matching the new literal route folderapps/web/src/app/[locale]/build/, and a naive!apps/web/src/app/[locale]/build/negation didn't fix it either, because unescaped[locale]is parsed as a gitignore glob character class, not literal brackets. Fixed with\[locale\]and confirmed viagit check-ignore.tsc --noEmit,eslint, and both pages rendered in EN and ES withrun-web(zeropageErrors).Disclosure: drafted with AI assistance under the user's direction, applied per their detailed written spec (page content, SDK-accuracy requirement, wording rules, and the no-navbar-decision-is-mine instruction).
Test plan
/ecosystempreview./ecosystem→/buildcross-link and the/build→ blog//developers//docslinks once live.