<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Docglow Blog</title><description>Notes from the Docglow team on dbt documentation, model lineage, and what data teams actually need from their docs.</description><link>https://docglow.com/</link><language>en-us</language><item><title>The state of dbt documentation in 2026: why nobody reads your docs</title><link>https://docglow.com/blog/dbt-docs-2026-state-of-documentation/</link><guid isPermaLink="true">https://docglow.com/blog/dbt-docs-2026-state-of-documentation/</guid><description>Six years, 43 comments, still open. A look at what analytics engineers have been asking dbt-docs for, and what an alternative looks like.</description><pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate><category>dbt</category><category>documentation</category><category>open-source</category><author>Josh Moore</author></item><item><title>Why we built Docglow</title><link>https://docglow.com/blog/why-we-built-docglow/</link><guid isPermaLink="true">https://docglow.com/blog/why-we-built-docglow/</guid><description>dbt docs serve was built for the analytics engineer who wrote the model. We built Docglow for everyone else who has to use it.</description><pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate><category>dbt</category><category>documentation</category><category>product</category><author>Docglow team</author></item></channel></rss>