Remix

**What use-case(s) is this template for? (e.g. CI, CD, Mobile, ML, Monorepos, etc.)**
CI, CD

**What platform(s) (if applicable) should this template target? (e.g. Docker, Kubernetes, Linux, iOS, etc.)**
Docker

**What language(s) (if applicable) should this template use? (e.g. Go, Ruby, Terraform, etc.)**
TypeScript, JavaScript

**Are there any specific tools this template should use? (e.g. `pip`, `Cypress`, `rails`, etc.)**
Node (does vite fall into this category too?)

As an aside, and for some inspiration, [Epic Stack](https://github.com/epicweb-dev/epic-stack), a Remix starter kit, includes [a deploy workflow for GitHub actions](https://github.com/epicweb-dev/epic-stack/blob/main/.github/workflows/deploy.yml). This kit is very batteries-included, so there’s a lot there and I imagine we’d want a vastly stripped-back pipeline definition by comparison.

Start by reviewing the repository's existing templates and comparing them with the requested Remix use case, Docker target, TypeScript/JavaScript, and Node tooling. Use the linked Epic Stack deploy workflow as inspiration, then define what a stripped-back Buildkite pipeline template must contain and verify that the resulting template covers CI and CD.

Written by the indexing model from the issue text.