Hi Jules

There are a couple of helper methods that you could look at

Umbraco.TypedContentAtXPath accepts an XPath, that could define your document type filter eg:

var matchingPages = Umbraco.TypedContentAtXPath("//Home|//LandingPage");

would find all documents with a document type alias of Home or LandingPage.

However as a site gets larger, and because you mention the quickest way; you should also consider using Examine;

There is an Umbraco.TypedSearch helper that returns an IEnumerable of IPublishedContent that accepts an Examine Search Criteria; so you could filter by the nodeTypeAlias index field eg:

var searcher = ExamineManager.Instance.SearchProviderCollection["ExternalSearcher"];
    var criteria = searcher.CreateSearchCriteria(Examine.SearchCriteria.BooleanOperation.Or);
    var nodeTypeAliasList = new string[] {"Home","LandingPage"};
    var examineQuery = criteria.GroupedOr(new string[]{"nodeTypeAlias"}, nodeTypeAliasList);    
    var examineMatchingPages = Umbraco.TypedSearch(examineQuery.Compile());

In your development site if you have compilation debug set to true; you can access the MiniProfiler by adding ?umbDebug=true on the querystring; if you wrap both these versions of filtering your content in a disposable timer object, you will be able to see in the miniprofiler which is the fastest for your content structure...

eg

var matchingPages = default(IEnumerable<IPublishedContent>);
using (DisposableTimer.DebugDuration<UmbracoTemplatePage>("Measuring Using TypedContentByXPath"))
{   
    matchingPages = Umbraco.TypedContentAtXPath("//Home|//LandingPage");
}

Thanks Marc. Really useful.

Will look at this tomorrow.

J

There is also a helper method which is called "OfTypes()" where you can select the descendens of your home node by document type alias.

Also v useful - I had not noticed that

Thanks

J

is working on a reply...