<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:jf="http://www.dotcms.com/xmlns/rss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

	<channel>
		<title>dotCMS Team Blog</title>
		<link>http://dotcms.com/</link>
        <description>RSS Feed for up to date team blog from dotCMS, Inc.</description>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/dotcms/rss-blog" /><feedburner:info uri="dotcms/rss-blog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><geo:lat>25.730678</geo:lat><geo:long>-80.244107</geo:long><item>
            <title>Spring MVC Support in dotCMS 2.0</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/IkD1gbpQvzU/spring-mvc-support-in-dotcms-2-0</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/spring-mvc-support-in-dotcms-2-0</guid>
            
<description>dotCMS 2.0 now comes with support for the widely popular Spring MVC Web development framework.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/IkD1gbpQvzU" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/spring-mvc-support-in-dotcms-2-0</feedburner:origLink></item>
		<item>
            <title>New in dotCMS 1.9 - Custom Fields and URL Mapping</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/VLQQmB--g8k/new-in-dotcms-1-9-custom-fields-and-url-mapping</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/new-in-dotcms-1-9-custom-fields-and-url-mapping</guid>
            
<description>The dotCMS CTO walks through two new features included in dotCMS, Custom Fields and URL Mapping.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/VLQQmB--g8k" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/new-in-dotcms-1-9-custom-fields-and-url-mapping</feedburner:origLink></item>
		<item>
            <title>Ignore the Spec - CMIS 1.0 is for Web Content Management too</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/L9yk5goaCos/ignore-the-spec-cmis-1-0-is-for-web-content-management-too</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/ignore-the-spec-cmis-1-0-is-for-web-content-management-too</guid>
            
<description>CMIS has been called a glorified wrapper for Document Management. But we are finding that CMIS answers many of web content management integration questions as well.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/L9yk5goaCos" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/ignore-the-spec-cmis-1-0-is-for-web-content-management-too</feedburner:origLink></item>
		<item>
            <title>Rehabilitating the Web With Section 508</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/q2c9cMcncKc/rehabilitating-the-web-with-section-508</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/rehabilitating-the-web-with-section-508</guid>
            
<description>The Rehabilitation Act was amended with section 508 a little over 10 years ago to require Federal agencies to deliver their electronic information in such a way that it is accessible for individuals with disabilities or impairments of some kind (low vision or low hearing for example). Section 508 mandates implementation of the accessibility measures set forth by the Web Accessibility Initiative (WAI).&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/q2c9cMcncKc" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/rehabilitating-the-web-with-section-508</feedburner:origLink></item>
		<item>
            <title>Best Practices with dotCMS Taxonomies</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/0z_0mQYfBog/best-practices-with-dotcms-taxonomies</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/best-practices-with-dotcms-taxonomies</guid>
            
<description>Despite all the fancy plugins, widgets, and fancy macros, the dotCMS really helps your website do just three simple things: store, retrieve, and display website data. Carefully designed wireframes help you plan how to display data but not necessarily how to properly label, segregate, and store it. This article makes some suggestions on how to take advantage of dotCMS taxonomies so that content can be retrieved and displayed easily and efficiently.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/0z_0mQYfBog" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/best-practices-with-dotcms-taxonomies</feedburner:origLink></item>
		<item>
            <title>dotCMS Enterprise: The Journey of a Bug.</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/uVdLC9hE_Zg/dotcms-enterprise-the-journey-of-a-bug-</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/dotcms-enterprise-the-journey-of-a-bug-</guid>
            
<description>Giving support to dotCMS EE clients on dealing with bugs that may restraint the proper behavior of their websites is one of the main goals to be achieved under dotCMS Enterprise model.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/uVdLC9hE_Zg" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/dotcms-enterprise-the-journey-of-a-bug-</feedburner:origLink></item>
		<item>
            <title>dotCMS and Dojo</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/fQt_xq-z0xs/dotcms-and-dojo</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/dotcms-and-dojo</guid>
            
<description>It&amp;apos;s been roughly two months since we  included Dojo as part of the dotCMS core javascript framework.  We chose Dojo after evaluating the most popular frameworks out there including JQuery, mootools, prototype/scriptaculous and YUI.	Each of these frameworks is pretty good but none is perfect. Although none of them met all our requirements, Dojo was clearly the best fit due to its extensive set of rich widgets and form controls.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/fQt_xq-z0xs" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/dotcms-and-dojo</feedburner:origLink></item>
		<item>
            <title>Creating a flash piece that pulls content from dotCMS</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/QXFgMm7fvTM/creating-a-flash-piece-that-pulls-content-from-dotcms</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/creating-a-flash-piece-that-pulls-content-from-dotcms</guid>
            
<description>Updating content in Flash can be cumbersome and time consuming. Thankfully, simply reading content from a simple JavaScript (or XML) file provides an alternative to importing assets and recompiling a flash file for swf.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/QXFgMm7fvTM" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/creating-a-flash-piece-that-pulls-content-from-dotcms</feedburner:origLink></item>
		<item>
            <title>Validating dotCMS Pages</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/_MnoUeQ0zvg/validating-dotcms-pages</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/validating-dotcms-pages</guid>
            
<description>Validating large sites can be a daunting task.  Aside from being aware of HTML best practices, it&amp;#8217;s useful to understand some dotCMS idiosyncrasies and commonly encountered errors.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/_MnoUeQ0zvg" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/validating-dotcms-pages</feedburner:origLink></item>
		<item>
            <title>dotCMS' content Import Tool: Or how to save time on bulk content imports and edits.</title>
            <link>http://feedproxy.google.com/~r/dotcms/rss-blog/~3/34DbLZFrrTk/dotcms-content-import-tool-or-how-to-save-time-on-bulk-content-imports-and-edits-</link>
            <guid isPermaLink="false">http://dotcms.com//blog/post/dotcms-content-import-tool-or-how-to-save-time-on-bulk-content-imports-and-edits-</guid>
            
<description>Anyone can be a content editor in the dotCMS. No need to know any HTML or CSS, just fill in the blanks and select &amp;amp;quot;Save and Publish&amp;amp;quot; and you&amp;apos;re set. This is not only true for the popular form-like &amp;amp;quot;Add/Edit Content&amp;amp;quot; page, but this concept also extends to one of the lesser known out-of-the-box tools of the dotCMS: the CSV import tool.&lt;img src="http://feeds.feedburner.com/~r/dotcms/rss-blog/~4/34DbLZFrrTk" height="1" width="1"/&gt;</description>


        <feedburner:origLink>http://dotcms.com//blog/post/dotcms-content-import-tool-or-how-to-save-time-on-bulk-content-imports-and-edits-</feedburner:origLink></item>
	</channel>
</rss>

