written by Jian Huang, 5. March 2012
Generally, there are two ways to generate a breadcrumb
<%!! Navigation:OutputArea(Breadcrumb) !!%>
<!IoRangeBreadCrumb><%anc_breadcrumb%> » <!/IoRangeBreadCrumb> <%hdl_title%>
Instead of using rendertag, it is best practice to use native placeholder to generate the breadcrumb for the following reasons:
Hilmar March 7, 2012 at 7:52 AM
I like the RenderTag solution more because in most projects there is a function "Do not show in display" or something similar. If you use the placeholder instead of the RenderTag solution, you will have to set that option plus "Do not use for breadcrumb".
However, if you have a simple project that doesn't need that function it could be a good idea to use the placeholder solution.
Jian Huang March 7, 2012 at 11:00 AM
Thank you for taking an interest in this topic.
Here is my take on project structure and navigation structure. If the page is configured to "do not show in display" in navigation structure, then it should not be in the navigation structure at all. This way, only pages that do show up in navigation are in navigation structure. Size of navigation structure negatively impacts project performance. Also, number of navigation areas negatively impacts project performance.
For example, links to article pages do not get displayed in navigation. With the rendertag approach, user would have to configure "do not show in display" after page creation. This becomes usability and project performance issue as the number of article pages increases. It is a lot simpler to make the content class of the article page not a master page, so it is not added to navigation structure by default, hence making the project scalable.
From my experience, using breadcrumb placeholder over breadcrumb rendertag makes the project much more scalable since it is not tied to navigation structure.
Please feel free to further the discussion in reply.
Source: Breadcrumb: RenderTag Vs Placeholder
© copyright 2012 by Jian Huang