static-first-routing

Configure static-first routing for Hugo sites with Cloudflare Workers.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/eykd/vance-ts --skill static-first-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: static-first-routing
Source: https://github.com/eykd/vance-ts/tree/main/.claude/skills/static-first-routing
Command: npx skills add https://github.com/eykd/vance-ts --skill static-first-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps configure and understand the routing mechanisms for a Hugo static site integrated with Cloudflare Workers, enabling efficient and secure handling of static and dynamic content.

Core Features & Use Cases

  • CDN vs Worker Routing: Differentiate between CDN-served static files and dynamic content processed by Workers.
  • URL Structure Configuration: Guide on setting up the URL structure for a Hugo + Workers setup.
  • Dynamic Handling: Decide which requests should be processed by Workers for dynamic content.
  • Endpoint Conventions: Implement conventions like /app/_/* for partial HTML content from Workers.

Quick Start

Use the 'static-first-routing' skill to set up routing for your Hugo static site with Cloudflare Workers, ensuring efficient delivery of both static and dynamic content.

Frequently Asked Questions about static-first-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure routing for a Hugo static site with Cloudflare Workers?

Set up static-first routing by serving static Hugo files via CDN and routing dynamic endpoints through Workers. This differentiates content delivery mechanisms to optimize both performance and security for your hybrid architecture.

What is static-first routing and when do I need it for Hugo and Cloudflare?

Static-first routing separates CDN-served static files from dynamic content processed by Workers. You need it when integrating Hugo with Cloudflare Workers to efficiently handle both static and dynamic requests securely.

How do I route dynamic content through Cloudflare Workers while serving Hugo static files via CDN?

Route dynamic content through Workers by implementing endpoint conventions like `/app/_/*` for partial HTML content. This ensures static Hugo assets are served via CDN while Workers handle dynamic processing.

Can I use Cloudflare Workers with Hugo for partial HTML content delivery?

Yes, you can use Cloudflare Workers with Hugo to deliver partial HTML content. Implement endpoint conventions like `/app/_/*` so Workers process dynamic requests while the CDN serves static Hugo files.

What URL structure should I use for Hugo and Cloudflare Workers hybrid architecture?

Use a URL structure that differentiates static and dynamic paths, such as `/app/_/*` for partial HTML content from Workers. This convention helps Cloudflare differentiate CDN delivery from Worker processing.

Why differentiate CDN routing from Worker routing in a static-first Hugo setup?

Differentiating CDN routing from Worker routing optimizes performance and security. It ensures static Hugo assets are cached and delivered efficiently via CDN while dynamic content is securely processed by Workers.