<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>DriftSync Blog</title>
		<link>https://driftsyncwp.com/blog/</link>
		<atom:link href="https://driftsyncwp.com/blog/rss.xml" rel="self" type="application/rss+xml" />
		<description>Release notes and deep dives on safe WordPress configuration sync from DriftSync.</description>
		<language>en-us</language>
		<item>
			<title>Introducing DriftSync: move WordPress config as a reviewable release</title>
			<link>https://driftsyncwp.com/blog/introducing-driftsync/</link>
			<guid isPermaLink="true">https://driftsyncwp.com/blog/introducing-driftsync/</guid>
			<pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
			<description>Stop re-entering settings by hand between staging and production. DriftSync moves WordPress configuration as a reviewable, reversible release — select, dry-run diff, snapshot, apply, audit. Free and complete on WordPress.org.</description>
		</item>
		<item>
			<title>Why DriftSync runs no code: moving data, not commands</title>
			<link>https://driftsyncwp.com/blog/why-driftsync-runs-no-code/</link>
			<guid isPermaLink="true">https://driftsyncwp.com/blog/why-driftsync-runs-no-code/</guid>
			<pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate>
			<description>Config-migration tools that execute shell or PHP steps are a risk on a live site. DriftSync moves data, not code: bundles are human-readable JSON you review in a dry-run diff, secrets are held not blanked, and every apply is reversible.</description>
		</item>
	</channel>
</rss>
