Merged
Conversation
* docs: add Machine Payments (MPP) section Add 6 new pages under guide/machine-payments: - Overview: protocol intro, payment flow diagram, intents, use cases - Client quickstart: fetch polyfill, Wagmi, per-request accounts, manual handling - Server quickstart: framework middleware, manual mode, push/pull, fee sponsorship - Accept one-time payments: charge intent guide with multi-framework examples - Accept pay-as-you-go payments: session intent with payment channel diagram - Accept streamed payments: SSE per-token billing with session vouchers Also adds MermaidDiagram component (from mpp repo) for animated sequence diagrams and sidebar entry under 'Start Building on Tempo'. * fix: use mpp.dev instead of mpp.sh for all links * fix: resolve tsgo build errors and biome warnings in MermaidDiagram * fix(ci): increase Node.js heap to 4GB for vite build OOM
* chore: tweaks * docs: testnet -> mainnet for code examples, network details, etc
* chore: remove thirdweb from developer tools page (#146) Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> * fix(docs): add fee recipient language (#147) --------- Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com> Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com>
Update sidebar structure to surface Building with AI under Changelog Rename, move up Build on Tempo
* add getting funds page, update building with ai cards Amp-Thread-ID: https://ampcode.com/threads/T-019cf8df-2af2-75ef-96cd-c899b6d4230a Co-authored-by: Amp <amp@ampcode.com> * up --------- Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019cf986-a283-7649-8612-6b9cd5d0f478 Co-authored-by: Amp <amp@ampcode.com>
* Add SKILL.md and AI card to homepage Amp-Thread-ID: https://ampcode.com/threads/T-019cfa0d-e023-71d1-a478-bd2f2ce4de3f Co-authored-by: Amp <amp@ampcode.com> * Rename building-with-ai to using-tempo-with-ai and update config Amp-Thread-ID: https://ampcode.com/threads/T-019cfa0d-e023-71d1-a478-bd2f2ce4de3f Co-authored-by: Amp <amp@ampcode.com> --------- Co-authored-by: Amp <amp@ampcode.com>
* chore: remove thirdweb from developer tools page (#146) Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> * fix(docs): add fee recipient language (#147) * feat: add Google Analytics (gtag.js) via static HTML head (#150) * fix(node): prep for mainnet (#144) * fix: revert vocs.config.tsx to .ts to fix Vercel SSR (#151) The Vocs SSR bundle hardcodes an import to dist/server/vocs.config.js. When the source file is .tsx, Vite outputs it differently, causing ERR_MODULE_NOT_FOUND and 500 errors on every page. - Rename vocs.config.tsx back to vocs.config.ts - Replace JSX with React.createElement calls for gtag head config - Update biome.json override to match new filename * fix: load env vars into process.env for vocs.config.ts (#152) Use Vite's loadEnv() to populate process.env with VITE_* env vars before the vocs() plugin initializes. Without this, VITE_GA_MEASUREMENT_ID is not available when vocs.config.ts is evaluated, causing the Google Analytics gtag to be silently skipped. This matches the pattern used in the mpp site's vite.config.ts. * fix: use Vite plugin for Google Analytics (vocs v2 compat) (#153) * fix: use transformIndexHtml for GA instead of vocs.config head Vocs v2 removed the `head` config property — it existed in v1 but is silently ignored in v2. Move Google Analytics injection to a Vite plugin using transformIndexHtml, which correctly injects script tags into the HTML during build. Also keep the loadEnv fix so VITE_* env vars from .env files are available to all plugins. * fix: use React component for GA instead of dead transformIndexHtml Vocs v2 uses Waku (RSC) which bypasses Vite's HTML pipeline entirely. transformIndexHtml is never invoked. Use a client-side React component in _layout.tsx instead, matching the pattern used for Vercel Analytics and PostHog. --------- Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com> Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com> Co-authored-by: Brendan Ryan <brendanjryan@users.noreply.github.com>
* chore: remove thirdweb from developer tools page (#146) Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> * fix(docs): add fee recipient language (#147) * feat: add Google Analytics (gtag.js) via static HTML head (#150) * fix(node): prep for mainnet (#144) * fix: revert vocs.config.tsx to .ts to fix Vercel SSR (#151) The Vocs SSR bundle hardcodes an import to dist/server/vocs.config.js. When the source file is .tsx, Vite outputs it differently, causing ERR_MODULE_NOT_FOUND and 500 errors on every page. - Rename vocs.config.tsx back to vocs.config.ts - Replace JSX with React.createElement calls for gtag head config - Update biome.json override to match new filename * fix: load env vars into process.env for vocs.config.ts (#152) Use Vite's loadEnv() to populate process.env with VITE_* env vars before the vocs() plugin initializes. Without this, VITE_GA_MEASUREMENT_ID is not available when vocs.config.ts is evaluated, causing the Google Analytics gtag to be silently skipped. This matches the pattern used in the mpp site's vite.config.ts. * fix: use Vite plugin for Google Analytics (vocs v2 compat) (#153) * fix: use transformIndexHtml for GA instead of vocs.config head Vocs v2 removed the `head` config property — it existed in v1 but is silently ignored in v2. Move Google Analytics injection to a Vite plugin using transformIndexHtml, which correctly injects script tags into the HTML during build. Also keep the loadEnv fix so VITE_* env vars from .env files are available to all plugins. * fix: use React component for GA instead of dead transformIndexHtml Vocs v2 uses Waku (RSC) which bypasses Vite's HTML pipeline entirely. transformIndexHtml is never invoked. Use a client-side React component in _layout.tsx instead, matching the pattern used for Vercel Analytics and PostHog. * fix: sql editor theme sync (#157) --------- Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com> Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com> Co-authored-by: Brendan Ryan <brendanjryan@users.noreply.github.com>
* mainnet-ready: update developer tools, connection details, and explorer URLs - Add Bridges, Security & Compliance, Orchestration cards to developer tools - Add CoinGecko, Redstone to Data & Analytics - Add Elliptic, TRM Labs to Security & Compliance - Add Bridge (Stripe) to Orchestration - Restructure Wallets with Embedded and Custodial & Institutional subcategories - Add BitGo, Fireblocks to Custodial & Institutional - Add Bridges section with Relay and Squid - Update mainnet/testnet RPC and explorer URLs Amp-Thread-ID: https://ampcode.com/threads/T-019cf98b-501e-7538-8115-cd3039d8ad94 Co-authored-by: Amp <amp@ampcode.com> * add missing providers and update connection tables - Add SonarX, SQD, Zerion to Data & Analytics - Add Pimlico to Smart Contract Libraries - Add Validation Cloud to Node Infrastructure - Move Utila to Custodial & Institutional - Add Across, Bungee to Bridges - Update Tempo Explorer with mainnet/testnet URLs - Make connect-to-wallets tables consistent with connection-details Amp-Thread-ID: https://ampcode.com/threads/T-019cf98b-501e-7538-8115-cd3039d8ad94 Co-authored-by: Amp <amp@ampcode.com> * split Developer Tools into Tempo Ecosystem Infrastructure section - Create /ecosystem/ with individual pages for each category: Bridges, Data & Analytics, Block Explorers, Wallets, Smart Contract Libraries, Node Infrastructure, Security & Compliance, Orchestration - Add collapsible 'Tempo Ecosystem Infrastructure' sidebar section - Add redirect from /quickstart/developer-tools to /ecosystem - Add new providers: Across, Bungee, CoinGecko, Redstone, SonarX, SQD, Zerion, Elliptic, TRM Labs, BitGo, Fireblocks, Pimlico, Validation Cloud, Bridge (Stripe) - Restructure Wallets into Embedded + Custodial & Institutional - Update mainnet/testnet RPC and explorer URLs - Make connection tables consistent across pages Amp-Thread-ID: https://ampcode.com/threads/T-019cf98b-501e-7538-8115-cd3039d8ad94 Co-authored-by: Amp <amp@ampcode.com> --------- Co-authored-by: Uddhav <255779543+letstokenize@users.noreply.github.com> Co-authored-by: Amp <amp@ampcode.com>
Merge 'Tempo Wallet CLI' and 'Tempo SDKs' sidebar sections into 'Tempo Developer Tools' with CLI and SDKs subsections. CLI section now has four pages: - Overview: what the binary does, install, agent setup with tabbed code group (Claude Code / Amp / Codex) - tempo wallet: auth, keys, funds, service discovery, sessions - tempo request: curl-like MPP client with automatic payment - tempo node: node flags grouped by function, plus tempo download Other changes: - Move URL from /wallet to /cli with 301 redirects - Delete troubleshooting page (redundant) - Add CLI cross-links in Using Tempo with AI, Getting Funds, Machine Payments, and Node Installation pages - Upgrade agent setup prompts to tabbed code groups site-wide Amp-Thread-ID: https://ampcode.com/threads/T-019cfda6-a311-765e-8012-69eeeb9129e2 Co-authored-by: Amp <amp@ampcode.com>
* chore: remove thirdweb from developer tools page (#146) Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> * fix(docs): add fee recipient language (#147) * feat: add Google Analytics (gtag.js) via static HTML head (#150) * fix(node): prep for mainnet (#144) * fix: revert vocs.config.tsx to .ts to fix Vercel SSR (#151) The Vocs SSR bundle hardcodes an import to dist/server/vocs.config.js. When the source file is .tsx, Vite outputs it differently, causing ERR_MODULE_NOT_FOUND and 500 errors on every page. - Rename vocs.config.tsx back to vocs.config.ts - Replace JSX with React.createElement calls for gtag head config - Update biome.json override to match new filename * fix: load env vars into process.env for vocs.config.ts (#152) Use Vite's loadEnv() to populate process.env with VITE_* env vars before the vocs() plugin initializes. Without this, VITE_GA_MEASUREMENT_ID is not available when vocs.config.ts is evaluated, causing the Google Analytics gtag to be silently skipped. This matches the pattern used in the mpp site's vite.config.ts. * fix: use Vite plugin for Google Analytics (vocs v2 compat) (#153) * fix: use transformIndexHtml for GA instead of vocs.config head Vocs v2 removed the `head` config property — it existed in v1 but is silently ignored in v2. Move Google Analytics injection to a Vite plugin using transformIndexHtml, which correctly injects script tags into the HTML during build. Also keep the loadEnv fix so VITE_* env vars from .env files are available to all plugins. * fix: use React component for GA instead of dead transformIndexHtml Vocs v2 uses Waku (RSC) which bypasses Vite's HTML pipeline entirely. transformIndexHtml is never invoked. Use a client-side React component in _layout.tsx instead, matching the pattern used for Vercel Analytics and PostHog. * fix: sql editor theme sync (#157) --------- Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com> Co-authored-by: joshitzko <82132285+joshitzko@users.noreply.github.com> Co-authored-by: zhygis <5236121+Zygimantass@users.noreply.github.com> Co-authored-by: Brendan Ryan <brendanjryan@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
8 participants
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.
Merge docs