ARCHE
FamiliesDocsExamplesBlogGitHub ↗
Documentation

Start

  • Getting started
  • Philosophy

Guides

  • First hour
  • Agent context
  • Verification
  • Package managers
  • Scaffold lifecycle
  • Showcase & portfolio

Walkthroughs

  • TypeScript fullstack
  • Convex product
  • Rust API & fullstack
  • Solana family
  • Customize & experiments
  • Automation (JSON/MCP)

CLI

  • Overview
  • Flags
  • Subcommands
  • Generated output

Presets

  • Preset catalog

Stack

  • TypeScript architecture
  • Convex
  • Rust
  • Solana
  • Authentication
  • Prisma store
  • tRPC

Operations

  • Deployment
  • Environment variables
  • Workers & queues
  • CI & testing
  • Scaling
  • Security
  • Troubleshooting

Reference

  • Stack links
  • Capabilities
  • This source repo
  • Code examples
← Documentation

Showcase and portfolio

--showcase, SHOWCASE.mdx, and package.json portfolio metadata for demos and kitsunekode.in sync.

1 min read

--showcase (TypeScript fullstack)

When enabled on typescript-fullstack, the CLI keeps demo-oriented routes and writes SHOWCASE.mdx at the project root for portfolio sync.

terminal
bun run dev:cli -- my-app --yes --preset=typescript-fullstack --showcase --dir=../projects

Use --no-showcase for a lean product tree—template-cleanup removes demo apps, landing pages, and related components (see toolings/scripts/template-cleanup.ts).

This marketing site

/showcase on arche.dev is a dev-only component gallery in the template repo—not the same as generated demo routes. Production builds return 404 for /showcase.

Portfolio metadata

Every serious monorepo scaffold updates root package.json:

terminal
"portfolio": {
  "slug": "my-app",
  "title": "My App"
}

Sync workflow: template repo docs/portfolio-sync.md and apps/cli/CLI-SPEC.md.

Examples on the website

Static snippets that mirror generated wiring live at /examples—useful before you scaffold.

Next steps

  • TypeScript walkthrough
  • Code examples
  • CLI flags