<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Desite Screener</title>
    <link>https://desite-screener.pages.dev/posts/</link>
    <description>Recent content in Posts on Desite Screener</description>
    <image>
      <title>Desite Screener</title>
      <url>https://tse1.mm.bing.net/th?q=desite%20screener</url>
      <link>https://tse1.mm.bing.net/th?q=desite%20screener</link>
    </image>
    <generator>Hugo -- 0.151.1</generator>
    <language>en</language>
    <lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://desite-screener.pages.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mastering your BIM data with a desite screener</title>
      <link>https://desite-screener.pages.dev/posts/desite-screener/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://desite-screener.pages.dev/posts/desite-screener/</guid>
      <description>If you&amp;#39;ve spent more than five minutes working with complex architectural models, you know that a desite screener is pretty much the only thing standing between you and a complete data meltdown. We&amp;#39;ve all been there—you open a federated model, and</description>
    </item>
  </channel>
</rss>
