<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Documentation on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/documentation/</link><description>Recent content in Documentation on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sat, 17 Jun 2017 00:02:01 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/documentation/atom.xml" rel="self" type="application/rss+xml"/><item><title>Building a Documentation System with Jekyll</title><link>https://www.chenshaowen.com/en/blog/how-to-develop-document-system-using-jekyll.html</link><pubDate>Sat, 17 Jun 2017 00:02:01 +0000</pubDate><atom:modified>Sat, 17 Jun 2017 00:02:01 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-to-develop-document-system-using-jekyll.html</guid><description>For a company that produces technical output, an excellent documentation management and publishing system is indispensable. A documentation system is a kind of content management system; it has high accessibility requirements, a low update frequency per document, and a high publishing frequency. In my opinion, publishing documentation as pure static</description><dc:creator>微信公众号</dc:creator><category>Jekyll</category><category>Documentation</category><category>Design</category><category>Operations</category><category>R&amp;D</category></item><item><title>Apidoc: Practice and Automated Generation</title><link>https://www.chenshaowen.com/en/blog/practice-and-automation-generation-of-apidoc.html</link><pubDate>Wed, 14 Jun 2017 17:22:45 +0000</pubDate><atom:modified>Wed, 14 Jun 2017 17:22:45 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/practice-and-automation-generation-of-apidoc.html</guid><description>In a frontend/backend separated architecture, API documentation changes hands frequently. When third-party interfaces are involved, API and documentation changes can be even faster in multi-party collaboration scenarios. To make maintaining the API and handing over documentation easier, here is a documentation generation tool worth recommending — apidoc. 1. Introduction to</description><dc:creator>微信公众号</dc:creator><category>Django</category><category>Interface</category><category>API</category><category>Documentation</category><category>R&amp;D</category></item></channel></rss>