<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/tools/</link><description>Recent content in Tools on Lead DevOps</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>MkDocs: Project Documentation from Markdown</title><link>https://lead-devops.blackdevhub.online/en/posts/mkdocs-quick-start/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/mkdocs-quick-start/</guid><description>&lt;p&gt;Documentation in a repository ages faster than anyone reads it: README links lead nowhere, sections are scattered across &lt;code&gt;docs/&lt;/code&gt;, &lt;code&gt;wiki/&lt;/code&gt;, and Confluence, and site search doesn&amp;rsquo;t work. MkDocs solves this predictably — it takes a folder of &lt;code&gt;.md&lt;/code&gt; files and builds a static site. One config, one command for the deploy, familiar Markdown.&lt;/p&gt;&#10;&lt;h2 id="what-is-mkdocs"&gt;What is MkDocs&#10;&lt;/h2&gt;&#10;&lt;p&gt;MkDocs is a static site generator for documentation written in Python. Input: a directory of Markdown files and a YAML config. Output: a ready &lt;code&gt;site/&lt;/code&gt; directory with HTML, served by any web server or hosted on GitHub Pages, GitLab Pages, S3. MkDocs core handles rendering; the theme defines look and features. The de-facto standard is &lt;a href="https://squidfunk.github.io/mkdocs-material/"&gt;Material for MkDocs&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>