The Executor project maintains a distinct public presence and technical documentation suite separated from the core application logic. This ensures that the high-traffic marketing site (executor.sh) and the comprehensive product documentation can be updated and deployed independently of the core SDK or host applications.
The marketing site is built using Astro and deployed as a Cloudflare Worker apps/marketing/astro.config.mjs29-38 It serves as the unauthenticated landing page for the executor.sh domain, while the cloud application handles authenticated traffic apps/cloud/src/edge/marketing.ts40-47
@astrojs/react integration to power interactive elements like demos and modals within static layouts apps/marketing/astro.config.mjs32/_astro/_ph path apps/marketing/src/layouts/Layout.astro56-62UsefulSoftwareCo/executor repository to display in the navigation bar apps/marketing/src/pages/index.astro9-16AnimatedBeamDemo and ContextBloatDemo to visually explain the value of an integration layer apps/marketing/src/pages/index.astro3-4In production, a middleware layer in the Cloudflare Worker determines whether to serve a request from the marketing worker or the cloud application worker apps/cloud/src/edge/marketing.ts35-59
| Path Pattern | Destination | Purpose |
|---|---|---|
/ (unauthenticated) | Marketing Worker | Landing page |
/blog/* | Marketing Worker | Public blog posts apps/cloud/src/edge/marketing.ts15-21 |
/_astro/* | Marketing Worker | Static assets and JS bundles |
/api/auth/* | Cloud App | WorkOS authentication flows apps/marketing/src/pages/index.astro15 |
/dashboard/* | Cloud App | Authenticated user console |
For technical details on the build process and proxying logic, see Marketing Site Architecture.
Sources: apps/marketing/astro.config.mjs29-38 apps/cloud/src/edge/marketing.ts35-59 apps/marketing/src/layouts/Layout.astro56-62 apps/marketing/src/pages/index.astro3-16
The product documentation is a standalone Mintlify application. It provides the primary onboarding path for users, structured around the different host environments and core concepts of the Executor platform apps/docs/index.mdx10-17
The documentation is reachable via the /docs path on the main marketing site apps/marketing/src/pages/index.astro107-110 It utilizes Mintlify-specific components like <CodeGroup>, <Tabs>, and <Tab> to present multi-platform installation commands (npm, pnpm, bun) clearly apps/docs/local/cli.mdx14-32
For the full documentation map and content guidelines, see Product Documentation.
Sources: apps/docs/index.mdx10-65 apps/docs/local/cli.mdx14-32 apps/marketing/src/pages/index.astro107-110
The following diagram illustrates how the Marketing Site and Documentation interact with the Cloud Application and the user's local environment.
Sources: apps/cloud/src/edge/marketing.ts35-59 apps/marketing/src/middleware.ts1-20 apps/marketing/src/lib/github.ts1-20
This table maps conceptual marketing/docs entities to their primary code definitions.
| Concept | Code Entity / Path | Role |
|---|---|---|
| Hero Demo | AnimatedBeamDemo apps/marketing/src/components/animated-beam-demo.tsx140-146 | Visualizes Agent-to-Tool connectivity. |
| Public Vars | wranglerPublicDefine apps/marketing/astro.config.mjs16-26 | Inlines PUBLIC_ vars from wrangler.toml into the Astro client bundle. |
| Setup Prompt | setupPrompt apps/marketing/src/pages/index.astro23-53 | The "Agentic Onboarding" text shared between site and docs. |
| Global Styles | apps/marketing/src/styles/global.css apps/marketing/src/styles/global.css1-27 | Registry-grade grayscale design system (Tailwind 4). |
Sources: apps/marketing/src/components/animated-beam-demo.tsx140-146 apps/marketing/astro.config.mjs16-26 apps/marketing/src/pages/index.astro23-53 apps/marketing/src/styles/global.css1-27