This is the official Deno documentation repository powering docs.deno.com. It is a static documentation site built with Lume (Deno-native static site generator), with a custom server middleware stack (redirects, Google Analytics, API content-type routing, LLM file serving, markdown source access) deployed on Deno Deploy. The content corpus spans the Deno runtime CLI, Deno Deploy, Subhosting, Sandbox, Deno KV, lint rules, 100+ runnable code examples with structured JSDoc metadata, tutorials, and generated API references for Deno, Web, and Node.js APIs. The build pipeline includes multiple code-generation stages: API reference pages generated from TypeScript type definitions via deno doc with a content-hashed incremental cache, Orama search index generation with a clean FileSelector → MarkdownIndexer → Output pipeline, and LLM-friendly file generation (llms.txt, llms-full.txt, llms.json) with relevance scoring. CI enforces link validity, frontmatter freshness (last_modified), and sidebar constraints via Deno test suites.
This repository contains the source documentation for the Cloud Foundry Developer Guide, published at https://docs.cloudfoundry.org/devguide/. It consists of Markdown files with ERB templating (.html.md.erb) that generate static HTML documentation covering Cloud Foundry application deployment, management, and troubleshooting topics. The documentation is organized into sections such as deploy-apps, services, and capi, detailing workflows like cf push, manifest usage, service binding, routing, logging, and deployment strategies. The architecture relies on ERB templating for reusable components (partials) and follows a static site generation model. Key entry points include index.html.md.erb and section indexes like deploy-apps/index.html.md.erb. The documentation references external dependencies such as the Cloud Foundry CLI, CAPI V3 API, and BOSH properties, but does not contain executable code itself. It serves as a reference for developers interacting with the Cloud Foundry platform-as-a-service. While the documentation exhibits good organizational patterns and reuse of templated snippets, it shows signs of maintenance lag. The repository appears stale with no evidence of recent commits (last commit date provided is implausibly future-dated), and content risks drifting from the active Cloud Foundry platform due to version-specific references (e.g., cf CLI v8, deprecated stacks) and experimental features. However, the source structure demonstrates solid documentation engineering practices through modular partials and consistent formatting.