<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>DEPLOY1 Blog</title>
  <id>https://deploy1.blog/</id>
  <link rel="self" href="https://deploy1.blog/feeds/atom.xml"/>
  <updated>2026-09-21T00:00:00.000Z</updated>
  <entry>
    <title>The DEPLOY1 quality gate dataset: what our checks actually measure</title>
    <id>https://deploy1.blog/posts/quality-gate-dataset/</id>
    <link rel="alternate" href="https://deploy1.blog/posts/quality-gate-dataset/"/>
    <published>2026-09-21T00:00:00.000Z</published>
    <updated>2026-09-21T00:00:00.000Z</updated>
    <summary>Every change to this repository passes the same quality gate: typecheck, workspace manifest check, lint, format, tests and build. This dispatch documents exactly what each gate covers.</summary>
    <author><name>DEPLOY1 Engineering Team</name></author>
  </entry>
  <entry>
    <title>Latency and conversion sandbox: the model behind the homepage slider</title>
    <id>https://deploy1.blog/posts/latency-conversion-sandbox/</id>
    <link rel="alternate" href="https://deploy1.blog/posts/latency-conversion-sandbox/"/>
    <published>2026-09-20T00:00:00.000Z</published>
    <updated>2026-09-20T00:00:00.000Z</updated>
    <summary>The homepage sandbox is a static, transparent model — not a prediction. Here is every formula, constant and assumption behind the numbers it shows, so you can disagree with them.</summary>
    <author><name>DEPLOY1 Engineering Team</name></author>
  </entry>
  <entry>
    <title>Fixed-scope delivery: when productized sprints work — and when they don&#39;t</title>
    <id>https://deploy1.blog/posts/fixed-scope-deployments/</id>
    <link rel="alternate" href="https://deploy1.blog/posts/fixed-scope-deployments/"/>
    <published>2026-09-17T00:00:00.000Z</published>
    <updated>2026-09-17T00:00:00.000Z</updated>
    <summary>Deploy1 runs on fixed-price, fixed-window sprints: $500 in a day, $5,000 in seven days, $20,000 in thirty. This post is the honest version of when that model wins, and where it breaks.</summary>
    <author><name>DEPLOY1 Engineering Team</name></author>
  </entry>
  <entry>
    <title>Server-side lead intake without a form framework</title>
    <id>https://deploy1.blog/posts/server-side-lead-intake/</id>
    <link rel="alternate" href="https://deploy1.blog/posts/server-side-lead-intake/"/>
    <published>2026-09-11T00:00:00.000Z</published>
    <updated>2026-09-11T00:00:00.000Z</updated>
    <summary>How we replaced a direct-to-provider form POST with a first-party endpoint that validates every field server-side, honeypots bots and rate-limits abuse — in a couple of hundred lines.</summary>
    <author><name>DEPLOY1 Engineering Team</name></author>
  </entry>
  <entry>
    <title>A minimal static site generator within a few hundred lines</title>
    <id>https://deploy1.blog/posts/minimal-static-site-generator/</id>
    <link rel="alternate" href="https://deploy1.blog/posts/minimal-static-site-generator/"/>
    <published>2026-09-04T00:00:00.000Z</published>
    <updated>2026-09-04T00:00:00.000Z</updated>
    <summary>This blog runs on a hand-rolled static generator with no framework. Here is how it works: strict frontmatter validation, a constrained Markdown renderer, and plain HTML templates.</summary>
    <author><name>DEPLOY1 Engineering Team</name></author>
  </entry>
  <entry>
    <title>Static-first: why our marketing sites don&#39;t reach for a framework</title>
    <id>https://deploy1.blog/posts/static-first-marketing-sites/</id>
    <link rel="alternate" href="https://deploy1.blog/posts/static-first-marketing-sites/"/>
    <published>2026-08-26T00:00:00.000Z</published>
    <updated>2026-08-26T00:00:00.000Z</updated>
    <summary>For a marketing site, the best runtime is often none at all. A look at the decision framework we use before adding React, Next.js or any build framework to a content site.</summary>
    <author><name>DEPLOY1 Engineering Team</name></author>
  </entry>
</feed>