Mike asked me via IM if it makes sense to create assets, including web content via the Asset Publisher portlet. Here are my thoughts on the matter.
Asset publisher portlets allow users to create any of the following asset types (e.g., blogs, bookmark, calendar entry, document, web content) if the portlet is displaying them. I think it is fine to create content from the Asset Publisher for almost anything other than "Web Content". If a community is using Asset publishers to also display web content, then perhaps it is fine to do so from an asset publisher. Otherwise, typically web content is displayed on a page within a web content display, so if a user creates the web content for example within the "What's New" instance of an Asset Publisher they will see the web content within the "What's New" portlet until it scrolls off the list but wouldn't be able to find the content elsewhere in the site (other than through the search).
YMTC is an example of where we use web content within Asset Publishers. The YMTC entries are web content and they are dynamically being displayed within Asset Publisher portlets. In this case it makes sense to publish web content through the Asset Publisher.