7 docs tagged with "cookbook"

A project recipe — really a family of recipes — for an LLM-backed chat surface, organized along two axes: deployment shape (standalone vs embedded) and implementation path (custom vs prebuilt AI SDK). The target is an LLM-backed chat experience — either a standalone ChatGPT-style app or a third-party-mountable widget — built on the same React/Vite/Cloud Run foundations as the React SPA and React SPA with Firebase recipes. This recipe layers onto those — it does not replace them.

A project recipe for a documentation site built with Astro Starlight, deployed to GitHub Pages via GitHub Actions, with considerations for private repositories. Use this as a blueprint when setting up internal docs, product documentation, or team knowledge bases where the source repository may be private.

Choose who owns scene behavior before choosing an embedding mechanism. This cookbook compares React + React Three Fiber, a React shell with Godot, and a Godot-first application using one bounded editing workflow.

Keep your business and glue logic in Node/TypeScript, and delegate only the small CPU-bound hot kernel to Rust. Three integration approaches connect the two runtimes: an in-process native addon, a WebAssembly module, and an out-of-process sidecar. This cookbook is a decision guide for choosing between them plus a concrete napi-rs recipe for the most common case.

A conceptual recipe for a React application with a Godot-powered scene viewport. Use it to scope a bounded layout editor after evaluating the alternatives in Choosing a Web 3D Architecture.

A project recipe for a React / TypeScript single-page application backed by a REST API, authenticated with Firebase, and hosted on Google Cloud Run. Use this as a blueprint when estimating, scoping, and delivering a typical B2B internal tool or admin panel.

A project recipe for a React / TypeScript single-page application using Firebase as a Backend-as-a-Service. Firestore handles data persistence via the client SDK, Firebase Auth manages identity, Firebase Hosting serves the SPA, and Cloud Run handles backend business logic triggered by Firestore events through Eventarc. Use this as a blueprint when estimating, scoping, and delivering a typical B2B internal tool or admin panel — the serverless BaaS alternative to the React SPA on Cloud Run recipe.