<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Documentation on Sergio Comerón Blog</title>
		<link>https://sergiocomeron.com/blog/en/tags/documentation/</link>
		<description>Recent content in Documentation on Sergio Comerón Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://sergiocomeron.com/blog/en/tags/documentation/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>From README to a bilingual documentation site with MkDocs Material</title>
				<link>https://sergiocomeron.com/blog/en/posts/mkdocs-documentacion-bilingue/</link>
				<pubDate>Mon, 01 Jun 2026 00:00:00 +0200</pubDate>
				<guid>https://sergiocomeron.com/blog/en/posts/mkdocs-documentacion-bilingue/</guid>
				<description>&lt;p&gt;The Jitsi plugin for Moodle I maintain, &lt;code&gt;mod_jitsi&lt;/code&gt;, had all of its documentation in one place: the &lt;code&gt;README.md&lt;/code&gt;. And it wasn&amp;rsquo;t just any README — it was &lt;strong&gt;over 600 lines&lt;/strong&gt; covering installation, server options (GCP, JaaS, self-hosted), JWT mode, recordings, attendance, permissions… A good README, but a README nonetheless.&lt;/p&gt;&#xA;&lt;p&gt;The problem with a long README is that &lt;strong&gt;it doesn&amp;rsquo;t scale as documentation&lt;/strong&gt;. Nobody reads 600 lines top to bottom on GitHub. There&amp;rsquo;s no search. No sidebar navigation. No clean way to link to &amp;ldquo;the JWT configuration section&amp;rdquo;. And if you want to translate it, you end up with two giant files that drift out of sync the moment you touch them.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
