<fvdoc>
<div xmlns='http://www.w3.org/1999/xhtml'>
<div id='message'>
<p>Ensure <code>description</code> precedes <code>content:encoded</code></p>
</div>
<div id='explanation'>
<p>While either the <code>description</code> or the <code>content:encoded</code> elements may contain the full content of an <code>item</code>, the <code>description</code> element is more widely supported than the <code>content:encoded</code> element in the context of an RSS 2.0 feed.</p>

<p>When both elements appear in an RSS 2.0 <code>item</code>, some consumers will simply pick up the last such element.</p>

<p>See the <a href="http://www.rssboard.org/charter">RSS Advisory Board</a>'s <a href="http://www.rssboard.org/rss-profile-1#namespace-elements-content-encoded">Best Practices Profile</a> for additional requirements and recommendations.</p>

</div>
<div id='solution'>
<p>Publishers who employ summaries <span class="rfc2119">should</span> store the summary in <span class="element">description</span> and the full content in <span class="element">content:encoded</span>, ordering <span class="element">description</span> first within the item. On items with no summary, the full content <span class="rfc2119">should</span> be stored in <span class="element">description</span>.</p>
</div>
</div>
</fvdoc>
