Hi Yaco

'ChildrenOfType' returns an IEnumerable of IPublishedContent - where each IPublishedContent item represents your news item in a 'generic way'.

With IPublishedContent you can access the properties using the .Value helper

So in your example above you'd be able to write out your title and Short Description by using their alias in the backoffice on the doc type.

so

@{
    var inTheNews = Umbraco.Content(Guid.Parse("257d436e-d180-46af-b37e-585136836c8d"))
    .ChildrenOfType("newsItemPage")
    .Where(x => x.IsVisible())
    .OrderByDescending(x => x.CreateDate);
}
<ul>
    @foreach (var item in inTheNews)
    {
        <li>
            <a href="@item.Url()">@item.Name()</a> - @item.Value<string>("title") - @item.Value<string>("shortDescription")
        </li>
    }
</ul>

But if you want to use the 'Modelsbuilder' approach to listing out the children then you would have instead

@{
    var inTheNews = Umbraco.Content(Guid.Parse("257d436e-d180-46af-b37e-585136836c8d"))
    .Children<NewsItemPage>()
    .Where(x => x.IsVisible())
    .OrderByDescending(x => x.CreateDate);
}
<ul>
    @foreach (var item in inTheNews)
    {
        <li>
            <a href="@item.Url()">@item.Name()</a> - @item.Title - @item.ShortDescription
        </li>
    }
</ul>

Here Umbraco knows the children are explicitly NewsItemPage types and so you can use the strongly typed property access instead of .Value

You can then use the properties for filtering too eg

@{
    var inTheNews = Umbraco.Content(Guid.Parse("257d436e-d180-46af-b37e-585136836c8d"))
    .Children<NewsItemPage>()
    .Where(x => x.IsVisible() && x.PublishDateOrWhatever > new DateTime("somedate"))
    .OrderByDescending(x => x.CreateDate);
}

This cheatsheet is geared for using Modelsbuilder and might give you some hints for working with Children etc

https://drive.google.com/file/d/171sMUOjjKv-bvlFEDNk7WN0I_UD9g670/view

regards

Marc