StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Item Rendering</strong></p> <p>This is a way to ask a piece of content (an item) to render itself. The content carries information about how it should render.</p> <p>To the best of my knowledge this is not widely used and not well documented - but I believe the feature itself to pre-date Sitecore MVC.</p> <p>See more here: <a href="http://www.sitecore.net/unitedkingdom/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2012/06/MVC-Item-Renderings-in-the-Sitecore-ASPNET-CMS.aspx">http://www.sitecore.net/unitedkingdom/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2012/06/MVC-Item-Renderings-in-the-Sitecore-ASPNET-CMS.aspx</a></p> <p><strong>View Rendering</strong></p> <p>Basically this is a Razor view. Sitecore provides a default controller and model for the view. The model can be customised by changing the mvc.getModel pipeline.</p> <p>Use this when you want to render item content that does not require any significant business or presentation logic.</p> <p><strong>Controller Rendering</strong></p> <p>With a controller rendering you supply controller, model and view. On your rendering definition item you specify what action Sitecore should use to render the component.</p> <p>Use this when you need to render content that relies on external data and/or requires significant business or presentation logic. Anything to do with form submission would probably also fall in this category.</p> <p><strong>Method Rendering</strong></p> <p>Will output the return value of a call to a static method.</p> <p>To the best of my knowledge this is not widely used and not well documented - I suppose it could be used for integrating legacy content.</p> <p>See more here: <a href="http://www.sitecore.net/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2012/03/More-Than-Anyone-Ever-Wanted-to-Know-About-Method-Renderings-in-the-Sitecore-ASPNET-CMS.aspx">http://www.sitecore.net/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2012/03/More-Than-Anyone-Ever-Wanted-to-Know-About-Method-Renderings-in-the-Sitecore-ASPNET-CMS.aspx</a></p> <p><strong>XSLT Rendering</strong></p> <p>Renders a Sitecore XSLT on a Sitecore MVC page. This rendering type fills the same space as the View Rendering just using XSLT as the template engine (rather than Razor).</p> <p>Use this if you have a library of existing Sitecore XSLT components that you don't want to rewrite. Personally I think View Renderings for doing no/low logic components are more appropriate if starting from scratch.</p> <p><strong>Url Rendering</strong></p> <p>Renders the response of a HTTP GET request onto the current page.</p> <p>Use this if you need to screen scrape HTML of another system. Again this could be used as a transition tool when migrating a legacy site. Can be used in some cases to avoid the embarrassing iframe syndrome.</p> <p>See more here: <a href="http://www.sitecore.net/unitedkingdom/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2012/03/All-About-URL-Renderings-in-the-Sitecore-ASPNET-CMS.aspx">http://www.sitecore.net/unitedkingdom/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2012/03/All-About-URL-Renderings-in-the-Sitecore-ASPNET-CMS.aspx</a></p> <p><strong>Rendering Parameter</strong></p> <p>This is not a rendering type and does not provide a facility for rendering anything on its own. Rendering Parameters are used to control the behaviour of renderings. Applies to all of the above rendering types.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload