<?xml-stylesheet type="text/xsl" href="https://uat.community.rws.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Best practices for XML editing experience in Knowledge Center</title><link>/developers-more/tridion-portfolio/tridiondocs-developers/b/knowledge_center_developer_blog/posts/best-practices-for-xml-editing-experience-in-knowledge-center</link><description>Even though Knowledge Center comes with Content Editor preconfigured for the basic topic types, it is worthwhile to try to optimize the experience for people working with the editor. It will depend on your organization and your documentation what DITA</description><dc:language>en-US</dc:language><generator>Telligent Community 12 Non-Production</generator></channel></rss>