<?xml version="1.0"?>

<rss version="2.0">


<channel>
<title>PHPKB Support Knowledge Base - Related Articles</title>
<link>https://www.phpkb.com/kb/article/5-key-benefits-of-a-knowledge-base-246.html</link>
<description>This RSS Feed contains Related Articles of the knowledge base. You can click on the title to view its content. Powered by PHPKB (https://www.phpkb.com)</description>
<div class="widget widget-others phpkb-tree">
									<div><item>
										<guid>https://www.phpkb.com/kb/article/role-of-technology-in-knowledge-sharing-213.html</guid>
										<title>Role of Technology in Knowledge Sharing</title>
										<link>https://www.phpkb.com/kb/article/role-of-technology-in-knowledge-sharing-213.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/why-a-knowledge-base-is-better-than-a-simple-faq-page-407.html</guid>
										<title>Why a Knowledge Base is Better Than a Simple FAQ Page</title>
										<link>https://www.phpkb.com/kb/article/why-a-knowledge-base-is-better-than-a-simple-faq-page-407.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/what-is-anti-concurrent-editing-of-knowledge-base-articles-330.html</guid>
										<title>What is Anti-Concurrent Editing of Knowledge Base Articles?</title>
										<link>https://www.phpkb.com/kb/article/what-is-anti-concurrent-editing-of-knowledge-base-articles-330.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/knowledge-base-software-vs-traditional-documentation-which-is-right-for-your-business-332.html</guid>
										<title>Knowledge Base Software vs. Traditional Documentation: Which is Right for Your Business?</title>
										<link>https://www.phpkb.com/kb/article/knowledge-base-software-vs-traditional-documentation-which-is-right-for-your-business-332.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/efficiently-managing-large-knowledge-bases-a-step-by-step-audit-plan-373.html</guid>
										<title>Efficiently Managing Large Knowledge Bases: A Step-by-Step Audit Plan</title>
										<link>https://www.phpkb.com/kb/article/efficiently-managing-large-knowledge-bases-a-step-by-step-audit-plan-373.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/how-to-manage-negative-feedback-in-a-positive-way-216.html</guid>
										<title>How to manage negative feedback in a positive way?</title>
										<link>https://www.phpkb.com/kb/article/how-to-manage-negative-feedback-in-a-positive-way-216.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/unlock-the-future-of-documentation-with-phpkb-371.html</guid>
										<title>Unlock the Future of Documentation with PHPKB</title>
										<link>https://www.phpkb.com/kb/article/unlock-the-future-of-documentation-with-phpkb-371.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/building-the-perfect-knowledge-base-187.html</guid>
										<title>Building the Perfect Knowledge Base</title>
										<link>https://www.phpkb.com/kb/article/building-the-perfect-knowledge-base-187.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/achieving-a-paperless-office-the-role-of-phpkb-knowledge-management-software-374.html</guid>
										<title>Achieving a Paperless Office: The Role of PHPKB Knowledge Management Software</title>
										<link>https://www.phpkb.com/kb/article/achieving-a-paperless-office-the-role-of-phpkb-knowledge-management-software-374.html</link>
										
									</item>
<item>
										<guid>https://www.phpkb.com/kb/article/why-manuals-go-unread-the-insight-every-documentation-team-misses-417.html</guid>
										<title>Why Manuals Go Unread: The Insight Every Documentation Team Misses</title>
										<link>https://www.phpkb.com/kb/article/why-manuals-go-unread-the-insight-every-documentation-team-misses-417.html</link>
										
									</item>
</div>
								</div>
</channel>

</rss>