Report

Serving the site

A portfolio like this one is a set of HTML, CSS, images, and small script files. Cloudflare's Workers Static Assets feature is built for exactly that shape: the files are deployed as part of a Worker and Cloudflare handles caching and serving them to browsers.

The important property for this site is that pages are plain files. There is no application server involved in rendering a page visit.

What requests cost

Not every request through a Cloudflare Worker behaves the same way for billing. The documentation separates requests that resolve to static assets from requests that invoke a Worker script, and prices them differently.

For a purely static site, the asset path is the common case: files are returned directly, and the Worker script is not part of serving them.

Organizing the content

Static does not have to mean unstructured. Astro content collections give each Markdown entry a defined shape: a loader retrieves the content, and a schema validates every entry's frontmatter during the build.

This portfolio uses that mechanism to check project pages, case studies, and experience records before anything is published.

Putting it together

Combining the three points above: the pages can be served as static assets, the content can still be validated at build time, and interactive extras only need small client-side scripts. That is the reasoning behind this site's architecture.

This conclusion is an inference drawn from the sourced claims above rather than a statement taken from a single document.

Claims

Sources

3 sources

  • Cloudflare Workers Static Assets

    developers.cloudflare.com(opens in a new tab) retrieved 2026-10-21

    You can upload static assets (HTML, CSS, images and other files) as part of your Worker
  • Cloudflare Workers Static Assets - Billing and Limitations

    developers.cloudflare.com(opens in a new tab) retrieved 2026-10-21

    Requests to static assets are free and unlimited.
  • Astro - Content Collections guide

    docs.astro.build(opens in a new tab) retrieved 2026-10-21

    An optional collection schema that allows you to define the expected shape of each entry for type safety, autocomplete, and validation