<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: schnell.technology</title>
    <description>The latest articles on DEV Community by schnell.technology (@schnelltechnolo).</description>
    <link>https://dev.to/schnelltechnolo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F328797%2F9ece6282-6f69-4d01-aa25-905bddce301d.jpg</url>
      <title>DEV Community: schnell.technology</title>
      <link>https://dev.to/schnelltechnolo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/schnelltechnolo"/>
    <language>en</language>
    <item>
      <title>How to create release-notes, your users will read. #releasebox.io</title>
      <dc:creator>schnell.technology</dc:creator>
      <pubDate>Sun, 02 Feb 2020 12:45:58 +0000</pubDate>
      <link>https://dev.to/schnelltechnolo/how-to-create-release-notes-your-users-will-read-releasebox-io-3p0i</link>
      <guid>https://dev.to/schnelltechnolo/how-to-create-release-notes-your-users-will-read-releasebox-io-3p0i</guid>
      <description>&lt;p&gt;Hey everyone 🙌,&lt;/p&gt;

&lt;p&gt;i'm Patrick - founder of schnell.technology. In the last few years, i developed applications for different customers and tools for power-users and developers.&lt;/p&gt;

&lt;p&gt;In this history, i tripped always over one part of my work - writing good release-notes, which your customers will actually read. &lt;/p&gt;

&lt;p&gt;Creating informative but not too techy releasenotes for your customers is key. A lot of developers spent either no time in creating release-notes or a lot of time, describing detailed changes for each release. The problem on this — most customers won’t read them. Either they are too common to be helpful or they are filled with a lot of technical informations, the most users don’t care.&lt;/p&gt;

&lt;h2&gt;
  
  
  releasebox.io
&lt;/h2&gt;

&lt;p&gt;So a new project was born - releasebox.io. With this tool, you’re able to create powerful, beautiful release-notes and keep the users in touch. Manage your releases including pre-releases, descriptions via Markdown or technical informations (and links to your project-/ticket-management) for your team-members.&lt;/p&gt;

&lt;p&gt;The focus is to provide simple release-notes for your customers, but more technical on the other hand for your team-members. With a simple drag-and-drop-oriented user-interface you can make changes to your releases on the fly (check the demo at &lt;a href="https://releasebox.io/acme-monitoring"&gt;https://releasebox.io/acme-monitoring&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Try &lt;a href="https://releasebox.io"&gt;releasebox.io&lt;/a&gt; and find out how easy it is to:&lt;br&gt;
🚀 inform users about your incredible work&lt;br&gt;
🎨 customize your beautiful project release-notes&lt;br&gt;
⏱️ manage your changes with simple drag and drop&lt;br&gt;
🔒 show technical informations only for those who are interested in&lt;br&gt;
📢 spread the message and like us on twitter, facebook and other social-media&lt;br&gt;
🎆 prepare your release-notes for the 2020ies right now&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>productivity</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
