Maybe i misunderstand the problem you are trying to solve. But from what i understand you want a simple container with a dynamic content where the staff members dont have their own site, but is rendered all on the page?

Every time you have a template you have a new page. My approach would be to create a document type with no template. Then (like it sounds like you already did) make the Document Type hierarchy so you can add the staff members to a page. The parent page that should hold the staff members should have a template, and be allowed to have child items of the staff Document type.

In the staff members template simply traverse all the children (the staff) and output the HTML that renders the layout of the staff member. You can do this with a Partial View if needed where you pass the Staff node.

Hi Chriztian,

Thanks for the quick reply - This extension is pretty awesome. Just installed it and have it working nicely. 

I really liked the idea of being able to expand the "Staff Members" content item and see all the Staff with an appropriate icon. Really great for the client to understand, but oh well this works really great for a small amount of staff members and maybe it's best not to clutter up the tree anyway :)

I will say that their PDF rendering example didn't work

var items = Model.GetPropertyValue<IEnumerable<IPublishedContent>> ("staffMembersList");
       
    foreach(var item in items) {
        <h3>@item.GetPropertyValue("firstName")</h3>
    }

This simply doesn't work (from inside a Razor master anyway), so I changed it to this

var items = CurrentPage.GetPropertyValue<IEnumerable<IPublishedContent>> ("staffMembersList");
       
    foreach(var item in items) {
        <h3>@Umbraco.Field(item, "firstName")</h3>
    }

And all works - even obeys the sort order.

Brian,

I really appreciate your comment as well, that is essentially what I was trying to do... Just out of curiosity, does this Doc Type structure look ok to you as far as what I'm trying to do?

+ Base Page

     - Content

     - Content - Staff Item

     - Home Page

+ Staff Item  (has no template, yet i am still able to view Staff items http://xyz.com/staff-members/jack-nicholson ) 

For my approach to work you need a container with a template (the staff members page is this container). Like this:

+ Front page

+ About page

+ Other page

+ Staff members (Doc type + template that loops children)

-- Jack Nicholson (no template, data is rendered in parent)

-- Tom Cruise (no template, data is rendered in parent)

-- John Doe (no template, data is rendered in parent)

-- Jane Doe (no template, data is rendered in parent)

The code in the staff members should be something like this (sry from memory so it wont compile)

<h2>All staff Members</h2>

@foreach(var staffMember in Model.Content.Children)

{

  <p>@staffMember.GetPropertyValue("StaffName", "")</p>

}

Ahh brilliant - I think Umbraco was just caching the template before, it all makes sense now.. Thanks so much Brian/Chriztian. I now have your suggested approach as well as Chriztian's working great.. Hard to say which will be easier on the client, but I now I get a 404 page for http://xyz.com/staff-members/jack-nicholson with your approach which is music to my ears!

Lastly, to prevent them from showing in the navigation, I'm checking TemplateId .. Is that an accepted approach? Below snippet for a general bootstrap nav/sub nav

It works - just want to make sure it's "OK"

@{  // I keep this at the top of my Templates
    var homeNode = CurrentPage.AncestorsOrSelf(1).Last();
}

                  @foreach (IPublishedContent node in homeNode.Children.Where("Visible"))
                    {
                        <li>
                            @if (node.Children.Any(a=>a.TemplateId > 0))
                            {
                                <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">@node.Name<span class="caret"></span></a>
                                <ul class="dropdown-menu" role="menu">
                                    @foreach (var subNode in node.Children.Where(a=>a.TemplateId > 0))
                                    {
                                        <li><a href="@subNode.Url">@subNode.Name</a></li>
                                    }
                                </ul>
                            }
                            else
                            {
                                <a href="@node.Url">@node.Name</a>
                            }
                        </li>
                    }

is working on a reply...