Hello!
I'm relatively new to Drupal, and because I've historically had a very different approach to CMS implementation, I think I may be missing the point of the architectural qualities of Drupal.
I'm a .NET developer who's used Umbraco and EPiServer a lot, but had limited experience in Drupal.
What Umbraco offers is a way for users to organise their content in the admin panel, such that items will happily sit in a tree structure under other items.
In the case that you have a news section, you would have the following structure in Umbraco:
News landing page
- News story 1
- News story 2
- News story 3
This hierarchical approach is also easily transferrable to organising other types of content, such as slideshows for specific page. You could have a homepage which would consist of a slideshow with four slides in it, and that slideshow could be specific to that homepage. This would look like this:
Homepage
- Slideshow
+ Slide 1
+ Slide 2
+ Slide 3
+ Slide 4
In Drupal, I've noticed that all pages sit together in a sort of "page soup" and someone else coined, and an implementation of a taxonomy is relied upon to ensure that content is organised on the front-end.