Content Rendering Stack

Content Rendering Stack

Tanstack Start

Pros

• Full static-site generation support
• Built with TypeScript for type-safety and developer experience
• Rich plugin ecosystem to extend functionality
• Good performance optimizations out of the box
• Active community and ongoing development

Cons

• At time of writing, still relatively new and evolving rapidly (in RC stage)

Outstanding Questions

• At the moment, it's not entirely clear how this solution will be able to target my (eventual) wasmcloud hosting environment.
  • Fortunately, Tanstack Start is built on top of Vite and Nitro, and those appear to have some level of support for cloudflare workers as a build target. Based off of my familiarity with the wasm ecosystem, these disparate deployment targets are working to unify around WASI as a common runtime target.

Content Collections

Pros

• Failry straightforward to define content collections using
• Richly developed ecosystem for markdown content processing that it integrates with
• Type-safe content models for compile(generation)-time validation
• Less opinionated creates more flexibility

Cons

• Less opinions means more decisions to make and more custom code to write