{"id":391,"date":"2011-09-09T05:42:31","date_gmt":"2011-09-09T05:42:31","guid":{"rendered":"http:\/\/www.stuartroberts.net\/?p=391"},"modified":"2011-09-09T05:42:31","modified_gmt":"2011-09-09T05:42:31","slug":"reusable-content","status":"publish","type":"post","link":"http:\/\/www.stuartroberts.net\/index.php\/2011\/09\/09\/reusable-content\/","title":{"rendered":"Reusable Content"},"content":{"rendered":"

I’ve worked on a lot of different SharePoint portals in my time and one of the main features of SharePoint that people seem to overlook, or are not aware of, is the reusable content<\/em> feature that is part of the publishing infrastructure. This post will hopefully help to make some more people aware of this underused feature.<\/p>\n

As mentioned, the reusable content feature relies on your site having the publishing infrastructure enabled. More specifically, the SharePoint Server Publishing Infrastructure<\/em> site collection feature.<\/p>\n

\"\"<\/a>

Publishing Infrastructure Site Collection Feature<\/p><\/div>
\n
\nand the SharePoint Server Publishing<\/em> site feature.<\/p>\n

\"\"<\/a>

Publishing Feature<\/p><\/div>\n

The site collection feature is required to create the Reusable Content<\/em> list in the root of the site and the SharePoint Server Publishing<\/em> site feature to be able to use publishing pages and insert the reusable content.<\/p>\n

Once you activate the site collection feature, you’ll notice a new list in the root of your site called Reusable Content<\/em>.<\/p>\n

\"\"<\/a>

Reusable Content List<\/p><\/div>\n

Using this list you can create plain text or HTML that can be reused throughout the site. This includes not just the root site but any child site as well. Any content added to this list can also be set to automatically update pages that reference it after modification. I’ve seen Portals with custom developed Web Parts that pull information from lists which could just as easily have harnessed this functionality and saved some time, effort and money in the process.<\/p>\n

To add custom content to a publishing page is pretty straight forward. First go to the Reusable Content<\/em> list and create either a new text or HTML item.<\/p>\n

\"\"<\/a>

New Item<\/p><\/div>\n

Create the reusable content, in my example, a simple list based on a HTML item.<\/p>\n

\"\"<\/a>

New Reusable Item<\/p><\/div>\n

Next, go to, or create, a publishing page that contains a page content field and go into page edit mode. In the ribbon, change to the Insert<\/em> tab where you will see an item titled Reusable Content<\/em>. Clicking this displays all items in the Reusable Content<\/em> list that have the Show in drop-down menu<\/em> option set.<\/p>\n

\"\"<\/a>

Insert Reusable Content<\/p><\/div>\n

Save the page and the custom HTML, or plain text, will now be visible on the page. If you set the option for automatic updating to true, any changes made to the item’s content will automatically be reflected in this page (and any others that reference it).<\/p>\n

\"\"<\/a>

Saved Publishing Page<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

I’ve worked on a lot of different SharePoint portals in my time and one of the main features of SharePoint that people seem to overlook, or are not aware of, is the reusable content feature that is part of the … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"jetpack_post_was_ever_published":false,"jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":[]},"categories":[3],"tags":[28,81],"jetpack_publicize_connections":[],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/plx2I-6j","_links":{"self":[{"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/posts\/391"}],"collection":[{"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/comments?post=391"}],"version-history":[{"count":8,"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/posts\/391\/revisions"}],"predecessor-version":[{"id":407,"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/posts\/391\/revisions\/407"}],"wp:attachment":[{"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/media?parent=391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/categories?post=391"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.stuartroberts.net\/index.php\/wp-json\/wp\/v2\/tags?post=391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}