Asset Publisher

test

test

Blogs

When to add web content from Asset Publisher portlets

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.

More Blog Entries

Requesting a "function" email account

The following describes how you go about requesting a NOAA email account to be used with the...

VLST Jenkins Support - New Jenkins Job

Through the VLab Development Services we support Jenkins continuous integration.  Jenkins...

1 Comments

MC
Michael Churma 11 Years Ago
Ken,

Thanks. My concerns (you touched on at least two of them blog post) with adding assets directly to Asset Publishers deal pretty much with organization. I'm thinking mostly about the "What's New"-configured Asset Publishers, but could these concerns apply to Asset Publishers in other configurations as well:

1. An entry/asset in the Asset Publisher will inevitably queue out of view. While they can be retrieved by searches, it's an out-of-site, out-of-mind issue.
2. If you add web content to a Web Content Display portal, you won't have to worry about it queuing out, AND you can still have that web content posted to the "What's New" Asset Publisher.
3. Similarly, if you add a document to a Document&Media portlet, you can take advantage of folders and other organization tools that the portlet offers. You'll always know where your document is....and, as with #2, that document in the Doc&Media portlet can still be shown in the "What's New" Asset Publisher.

Regards,

Mike
00
Please sign in to reply.