<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sphinx on Bernat's Portfolio</title><link>https://mrbmp33.github.io/tags/sphinx/</link><description>Recent content in Sphinx on Bernat's Portfolio</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mrbmp33.github.io/tags/sphinx/index.xml" rel="self" type="application/rss+xml"/><item><title>Write awesome documentation for your projects using sphinx.</title><link>https://mrbmp33.github.io/posts/document_your_code/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://mrbmp33.github.io/posts/document_your_code/</guid><description>&lt;h2 id="why-this-guide"&gt;Why this guide?&lt;/h2&gt;
&lt;p&gt;Documentation is one of those things every developer &lt;em&gt;knows&lt;/em&gt; they should do… until the project grows, deadlines hit, and the README becomes a fossil from three months ago.&lt;/p&gt;
&lt;p&gt;If you are reading this, you probably already understand the importance of documenting your code — not just for others, but also for your future self trying to remember why you wrote something at 2AM six months ago.&lt;/p&gt;
&lt;p&gt;I’ve done this in the past for personal projects, and getting everything working can be somewhat complicated at first. This guide is a practical walkthrough for anyone wanting to set up clean, maintainable documentation for Python code using Sphinx.&lt;/p&gt;</description></item></channel></rss>