Renaming "Children"-tab

[apeisa]

If there is only one template allowed for children, then it would be nice to show that template name instead of more generic "children" as a tab label.

Of course this would require nice (& multilingual) titles for templates. And actually would probably need plural version of that title also. So when I am viewing my "news" template, it would show "News items" instead of "Children".

[Pete]

That's a good idea I think.

My first thought was that it might make things less intuitive, but then that all depends on whether someone chooses a silly name for the child template.

I would suggest that it maybe be configurable somehow rather than automatically done else it might take some users by surprise.

[apeisa]

Yep. Optional setting would be great.

[apeisa]

Actually, I am not sure if this is a good idea anymore

Probably something where repeatable elements would fill the gap most of the times. I am currently building simple event management, and I need to support multiple instances for same event. Decided to add other instances (place and time) as children pages. It all feels nice, but not sure how easy it is for end user.

[Pete]

In which case it would make sense to be able to set that on a per-template basis I think. Label fields for single and plural versions would make sense in case the template name isn't properly formatted to be a tab title (sometimes mine aren't at least).

[ryan]

I'm a little conflicted on this because this is something that was in PW1 for awhile, and I later removed it. I thought it would be nicer for the client to have labels for Children (called Subpages in PW1) that could be context specific, like News Items, Press Releases, Articles, Villas, etc. I used it that way for awhile, and surprisingly it made things seem a lot more complex (to the client and to me). PW seems simple because how you edit one thing is how you edit everything, and there really isn't much terminology to wrap your mind around. But once you pull in all these new terms to refer to the same thing (pages) it just becomes a lot harder to think about or even talk about. So I ended up going back to using the same common term regardless of context. At least in my case, the benefits of site-wide consistency ended up outweighing the benefits of custom names. But that was only my experience, and others may have a completely different experience. I'm not opposed to supporting the ability to customize the labels like that, and I actually do think it's a good idea... it just didn't play out well in my case. But I think we'll want to move towards making such behaviors pluggable to give people the flexibility they want in customizing these things.