<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Confluence on Xianpeng Shen</title><link>https://shenxianpeng.dev/en/tags/confluence/</link><description>Recent content in Confluence on Xianpeng Shen</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>xianpeng.shen@gmail.com (Xianpeng Shen)</managingEditor><webMaster>xianpeng.shen@gmail.com (Xianpeng Shen)</webMaster><copyright>Copyright © 2017–2026 Xianpeng Shen. All rights reserved.</copyright><lastBuildDate>Wed, 14 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://shenxianpeng.dev/en/tags/confluence/index.xml" rel="self" type="application/rss+xml"/><item><title>Still Using Wiki/Confluence? You Might Be Producing Garbage</title><link>https://shenxianpeng.dev/en/posts/2025/docs-and-code/</link><pubDate>Wed, 14 May 2025 00:00:00 +0000</pubDate><author>xianpeng.shen@gmail.com (Xianpeng Shen)</author><guid>https://shenxianpeng.dev/en/posts/2025/docs-and-code/</guid><description>In enterprises, documentation tools like Wiki and Confluence, if lacking unified management and review mechanisms, can lead to information chaos and knowledge sedimentation failure. This article explores how to avoid this situation and draws on the successful experiences of open-source communities.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shenxianpeng.dev/posts/2025/docs-and-code/featured.jpg"/></item></channel></rss>