<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Conflicts on Bootstrapping.org</title>
    <link>https://bootstrapping.org/tags/conflicts/</link>
    <description>Recent content in Conflicts on Bootstrapping.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bootstrapping.org/tags/conflicts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Email Templates Customers Rewrite: One Conflict Settled Once, and Legal Text the Product Owns</title>
      <link>https://bootstrapping.org/email-templates-customers-rewrite-one-conflict-settled-once-and-legal-text-the-product-owns/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bootstrapping.org/email-templates-customers-rewrite-one-conflict-settled-once-and-legal-text-the-product-owns/</guid>
      <description>&lt;p&gt;Email templates are the reference data customers change most. A self-hosted product ships a welcome email, a password reset and an invoice notice. Each customer&amp;rsquo;s admin rebrands the subject lines, switches off what they don&amp;rsquo;t use and sometimes edits the small print. Then the product team fixes a typo in a subject the admin already rewrote, and updates the legal footer every email must carry.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://github.com/bootstrapping-engine/bootstrapping/tree/main/examples/templates&#34;&gt;templates example&lt;/a&gt; gives the columns three different owners. The subject and body are merged, so an admin&amp;rsquo;s edit stays unless the seed changes the same value. &lt;code&gt;enabled&lt;/code&gt; is local: on when shipped, the customer&amp;rsquo;s after that. And the footer belongs to the product.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
