<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>KV on Support Tools</title><link>https://support.tools/tags/kv/</link><description>Recent content in KV on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/kv/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloudflare Pages Build Output Directory and Next.js Settings</title><link>https://support.tools/cloudflare-pages-comprehensive-guide/</link><pubDate>Tue, 02 Dec 2025 09:00:00 -0500</pubDate><guid>https://support.tools/cloudflare-pages-comprehensive-guide/</guid><description>&lt;p&gt;&lt;img src="https://support.tools/images/posts/cloudflare/cloudflare-pages-architecture.svg" alt="Cloudflare Pages Architecture"&gt;&lt;/p&gt;&#10;&lt;p&gt;Most failed Cloudflare Pages deployments come down to one setting: the build output directory. This guide gives the correct build command and output directory for each framework, the current answer for Next.js (static export on Pages, full-stack apps on Workers), and how to create R2 buckets from the API for per-customer storage.&lt;/p&gt;</description></item></channel></rss>