@Tim: Sorry about the confusion. I should've realized you were talking about something which still needs to be developed. I got a little excited

Again, I would say both of these options would adequately address the issue. Whats more, I think they are both worth developing, as opposed to one versus the other. There are certain circumstances where one option would be more appropriate to use than the other. Going back to what I was saying, I believe having the ability for them to be nestable would be a great feature, and would expand its usefulness. As Silverstripe's user base begins to grow, and more content is created on Silverstripe run sites, I'm sure this will be an important issue. I wish I could give more feedback, these are the only ideas that I have. I'll be sure to post anymore that I might have.

In the meantime, as far as my situation is concerned, you suggest that I implement that solution from the trouble ticket above, and perhaps move my older articles in a Archived news section?

Because the options you've suggested are important to me, and I would like to see them implemented soon, I'd love to contribute to the development somehow, but unfortunately I feel as though I'd have a lot of catch up to do, not having looked at Silverstripe's Code much.

Just replying again to subscribe... (forgot it earlier).

I think this is a pretty important something, and I personally can't wait till this is released.

Maybe I can add this to the GHOP list? Or is this too complicated for that?

I know simon_w seems to have time enough for coding? :-P

@dio5: i think this is outside of the scope for a GHOP-task - we need to discuss/architect this feature properly, which in turn means a lot of preparation/mentoring-effort and a way longer timespan than the average GHOP-task.