<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Webslice's Statamic Starter Made This Site Go</title>
        <link>https://statamicstarter.maxjohns.nz</link>
        <description>A Statamic starter site configured for the Webslice serverless platform.</description>
        <language>en</language>
        <atom:link href="https://statamicstarter.maxjohns.nz/feed.xml" rel="self" type="application/rss+xml" />
        <item>
            <title>What changes when this goes live</title>
            <link>https://statamicstarter.maxjohns.nz/blog/what-changes-when-this-goes-live</link>
            <guid isPermaLink="true">https://statamicstarter.maxjohns.nz/blog/what-changes-when-this-goes-live</guid>
            <pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate>
            <description>The same repository behaves differently on your machine and on Webslice. These are the settings that differ, and what each one does in production.</description>
        </item>
        <item>
            <title>Deploying Statamic to Webslice</title>
            <link>https://statamicstarter.maxjohns.nz/blog/deploying-statamic-to-webslice</link>
            <guid isPermaLink="true">https://statamicstarter.maxjohns.nz/blog/deploying-statamic-to-webslice</guid>
            <pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
            <description>A git push builds the site, swaps it live, then warms the static cache. Here is what each step does, and where to look when one of them fails.</description>
        </item>
        <item>
            <title>What persists between deploys</title>
            <link>https://statamicstarter.maxjohns.nz/blog/what-persists-between-deploys</link>
            <guid isPermaLink="true">https://statamicstarter.maxjohns.nz/blog/what-persists-between-deploys</guid>
            <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
            <description>Form submissions, uploads and generated images each behave differently on a serverless deploy. Two of the three are handled for you.</description>
        </item>
    </channel>
</rss>
