<?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 Sulprobil</title>
    <link>https://www.sulprobil.de/tags/documentation/</link>
    <description>Recent content in Documentation on Sulprobil</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 03 Jun 2026 03:43:00 +0100</lastBuildDate>
    <atom:link href="https://www.sulprobil.de/tags/documentation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IT Documentation</title>
      <link>https://www.sulprobil.de/it_documentation_en/</link>
      <pubDate>Wed, 03 Jun 2026 03:43:00 +0100</pubDate>
      <guid>https://www.sulprobil.de/it_documentation_en/</guid>
      <description>&lt;p&gt;&lt;strong&gt;&amp;ldquo;When explaining a command, or language feature, or hardware widget,&#xA;first describe the problem it is designed to solve.&amp;rdquo; [David Martin, Norristown, Pennsylvania]&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;&#xA;&lt;p&gt;From my point of view the minimum requirement of an IT documentation is having a proper&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;System Handbook&lt;/strong&gt;, telling an IT savvy third person how to install and to configure your application,&#xA;and a proper&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;User Handbook&lt;/strong&gt;, telling one or more users with specified knowledge how to use your application.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
