<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Markdown Confluence Docker on Roger Welin</title><link>https://rogerwelin.github.io/categories/markdown-confluence-docker/</link><description>Recent content in Markdown Confluence Docker on Roger Welin</description><generator>Hugo -- 0.155.0</generator><language>en-us</language><lastBuildDate>Mon, 15 May 2017 11:43:43 +0000</lastBuildDate><atom:link href="https://rogerwelin.github.io/categories/markdown-confluence-docker/feed.xml" rel="self" type="application/rss+xml"/><item><title>Convert markdown to confluence markup</title><link>https://rogerwelin.github.io/2017/05/15/convert-markdown-to-confluence-markup/</link><pubDate>Mon, 15 May 2017 11:43:43 +0000</pubDate><guid>https://rogerwelin.github.io/2017/05/15/convert-markdown-to-confluence-markup/</guid><description>&lt;p&gt;I recently did some investigations at work on how to keep documentation up to date. I guess we&amp;rsquo;ve all been in the situation that the documentation we have is drifting from how the actual systems/applications look like. I believe that it&amp;rsquo;s easier to keep the documentation close the the actual code, e.g by README&amp;rsquo;s in markdown, than by have them as separate confluence pages that no one remembers to keep up to date. If you are using Confluence you can create/update documentation by using the REST api, however Confluence does not accept markdown so you have two options;&lt;/p&gt;</description></item></channel></rss>