It's typically recommended to store the content in page types, and to use widgets for presenting the content. So, you might have a page type that allows you to store some content, including your URL, and then a widget that allows you to pick the page that has the content you want to display. The widget could also have properties that are used to control how the content is rendered, but not to store the content itself.
This will help you achieve a separation of concerns in the design, so that the content is separate from the website layout. There are several benefits:
- The content is reusable. It can be used in more than one place in your website.
- You can change how the content is displayed, even use a different widget to display the content, without having to re-enter it.
- The content can survive a redesign. If you keep the structure of the content semantic, you could create a new set of views and widgets for the same content, without having to re-enter or migrate the content.
This has been the general recommendation with Kentico long before Kentico 12 MVC. It reminds me of one of the most memorable posts by Brenden.
This is my most favorite approach and most recommended by Kentico and any developer/partner who knows what they are doing with Kentico. Kentico is built around document/page types. If you look at how the content tree and navigation are setup you'll see this approach is not much different than using a static or editable text webpart on a page.
I hope this helps.