<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Begoña Pereda Blog feed</title>
	<subtitle>The latest posts from this Eleventy boilerplate.</subtitle>
	<link href="https://begopereda.com/feed.xml" rel="self"/>
	<link href="https://begopereda.com/"/>
	<updated>2026-02-20T00:00:00Z</updated>
	<id>https://begopereda.com</id>
	<author>
    <name>Andy Clarke</name>
    <email>andy.clarke@stuffandnonsense.co.uk</email>
	</author>
	
    
    <entry>
      <title>Launching a new site with confidence</title>
      <link href="https://begopereda.com/blog/launching-a-new-site-with-confidence/"/>
      <updated>2026-02-20T00:00:00Z</updated>
      <id>https://begopereda.com/blog/launching-a-new-site-with-confidence/</id>
      <content type="html"><![CDATA[
        <p>Start by replacing the sample content in this repository with real project material, not by fighting the defaults. The structure here is meant to be lightweight enough that you can remove sections instead of adapting around them.</p>
<p>Audit the navigation, metadata, legal pages, team profiles, and contact details first. Those are the pieces most likely to leak placeholder content into a launch build if they are left untouched.</p>
<p>Once those foundations are set, the rest of the project becomes routine content work instead of cleanup.</p>

      ]]></content>
    </entry>
	
    
    <entry>
      <title>Designing flexible content models</title>
      <link href="https://begopereda.com/blog/designing-flexible-content-models/"/>
      <updated>2026-02-13T00:00:00Z</updated>
      <id>https://begopereda.com/blog/designing-flexible-content-models/</id>
      <content type="html"><![CDATA[
        <p>A good starter does not force a content model that only works for one client. It gives you a few clear patterns and leaves enough room to adapt them.</p>
<p>In this project, the homepage, standard pages, posts, and team entries are deliberately separate. That makes it easier to reshape the CMS collection by collection instead of rewriting everything at once.</p>
<p>If a content type is not needed, delete it early and remove the navigation link at the same time.</p>

      ]]></content>
    </entry>
	
    
    <entry>
      <title>Keeping a boilerplate clean</title>
      <link href="https://begopereda.com/blog/keeping-a-boilerplate-clean/"/>
      <updated>2026-02-06T00:00:00Z</updated>
      <id>https://begopereda.com/blog/keeping-a-boilerplate-clean/</id>
      <content type="html"><![CDATA[
        <p>Boilerplates decay when project-specific work is added faster than it is removed. The fix is not more features. The fix is disciplined cleanup between projects.</p>
<p>Remove dead scripts, stale redirects, unused dependencies, and content that implies a real business where there is none. That keeps the template honest and reduces the risk of accidental launch mistakes.</p>
<p>Treat the starter as a product. If something is confusing in the first hour of use, it should be simplified now instead of documented later.</p>

      ]]></content>
    </entry>
	
</feed>
