How to make editable sitewide content?

Bryan Drenner asked on August 27, 2014 17:05

What's Kentico's best-practice to make editable sitewide or areawide content?

By "sitewide content", I mean the typical header/footer content that's rendered on every page of the site. By "areawide content", I mean content that's rendered to every page of a subsection of the site.

I asked a similar question a while back, but with Kentico 8 introducing so many new features, I wanted to ask again.

Correct Answer

Brenden Kehren answered on August 27, 2014 20:39

Bryan, I don't think there are any new features introduced in v8 will help or change anything from the answers in the post you referenced.

1 votesVote for this answer Unmark Correct answer

Recent Answers

Bryan Drenner answered on August 27, 2014 21:03

Okay, thanks Brenden. I'll go with your answer from my previous question.

1 votesVote for this answer Mark as a Correct answer

Delford Chaffin answered on August 29, 2014 03:43 (last edited on August 29, 2014 03:43)

Coming from a Drupal shop to now working with Kentico more, Drupal Blocks (that do exactly what you are asking) are one of the things I miss the most.

I have thought about replicating them with Kentico by making a "Block" doc type and placing them all in a dedicated folder in the tree and referencing them as necessary. Similar to the solution you posted in the previous post, but with more documents with less fields. I would think this would simplify transformations as you'd really only need one to display any given "Block".

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on August 29, 2014 13:54

Delford,

I've taken that approach before and it works well. In the Marketplace there was a sitewide editable content webpart for v6 but when I tried to use it, it was cumbersome and didn't function as I'd expect. The way editable text and image webparts are used is different than a standard doc type as well so in my opinion a much stronger, robust, reuasable approach is to have a custom doc type that you reference on your master page and then in each area have a folder with your area wide content and use page inheritance.

0 votesVote for this answer Mark as a Correct answer