
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>matthelam Sitecore Blog</title>
      <link>https://matthelam-sitecore-blog.vercel.app/blog</link>
      <description>A blog documenting my trials and tribulations during my circumnavigation of the Sitecore-sphere.</description>
      <language>en-us</language>
      <managingEditor>matthewlam@aceik.com.au (Matthew Lam)</managingEditor>
      <webMaster>matthewlam@aceik.com.au (Matthew Lam)</webMaster>
      <lastBuildDate>Wed, 04 Feb 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://matthelam-sitecore-blog.vercel.app/tags/development/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://matthelam-sitecore-blog.vercel.app/blog/The Leading Slash That Breaks Your Page Static vs Dynamic Placeholders in Sitecore</guid>
    <title>The Leading Slash That Breaks Your Page, Static vs Dynamic Placeholders in Sitecore</title>
    <link>https://matthelam-sitecore-blog.vercel.app/blog/The Leading Slash That Breaks Your Page Static vs Dynamic Placeholders in Sitecore</link>
    <description>A critical Sitecore behavior uncovered during a bulk content migration — why dynamic placeholders often require a leading slash, how this impacts rendering resolution, and a practical tip for locating DynamicPlaceholderId values.</description>
    <pubDate>Wed, 04 Feb 2026 00:00:00 GMT</pubDate>
    <author>matthewlam@aceik.com.au (Matthew Lam)</author>
    <category>sitecore</category><category>xm cloud</category><category>sitecore ai</category><category>renderings</category><category>placeholders</category><category>content migration</category><category>development</category>
  </item>

    </channel>
  </rss>
