I find this sort of thing a lot easier using the more strongly typed IPublishedContent instead of the dynamics because I get to use LINQ. I'd do something like this

@{
    var currentPage = Model.Content;
    var root = Umbraco.TypedContentAtRoot().FirstOrDefault();
}

foreach (var newsCat in root.Descendants().Where(n => n.IsDocumentType("NewsCategory") && n.Descendants().Any(d => d.IsDocumentType("NewsArticle"))))
{

}

Or maybe if you don't like the really long LINQ expression, you could do something like this:

@{
    var currentPage = Model.Content;
    var root = Umbraco.TypedContentAtRoot().FirstOrDefault();
}

foreach (var newsCat in root.Descendants().Where(n => n.IsDocumentType("NewsCategory")))
{
    if(!newsCat.Descendants().Any(d => d.IsDocumentType("NewsArticle"))
    {
        continue;
    }
}

May i ask why u use Descendants ? Your title indicates to me that u have a strukture like this

News Node 
 - News Category 
 -- News 
 -- News 
 - News Category 

then u should not use Descendants use children instead, u will get a better preformance

@foreach (var newsCategory in Model.Content.Children.Where(child => child.IsDocumentType("NewsCategory")))
{
    if (newsCategory.Children.Any())
    {
        <ul>
            @foreach(var news in newsCategory.Children)
            {
                <li>@news.Name</li>
            }
        </ul>
    }
    else
    {
        <span>no children</span>
    }

}

if u have some other odd strukture with date folders u have to use Descendants

Aye its more like this

Category
 - Stuff
 - Nonsense
 - MayBe News 
 -- Article
 -- Article
 -- Article
 - More stuff

.

So I want to only call the category names if it happens to have news in it.

Ah simple solution thanks to all, I thought I could do it in one for each but this works just as well without much fuss

@foreach(var newsCat in CurrentPage.Site().Descendants("newsCategory"))
    {

        if(newsCat.Descendants("newsArticle").Any()){

    <li>@newsCat.Name</li>
        }

    }

Thanks again

Doogie

is working on a reply...