What I am wondering is, what about all the OOB feature staplers (FeatureSiteTemplateAssociation)? It seems that they are activated in a web template just fine. For example AssetLibrary that is a site (SiteCollection) scoped feature. This feature is only activated through feature stapling on a farm scoped feature.
Checking this feature on my CWT site reveals that it is activated during provisioning:
PS>get-spfeature -Identity assetlibrary | Format-List DisplayName, Status DisplayName : AssetLibrary Status : Online
An article on MSDN specifies that:
Unless indicated otherwise, excerpts used in the following examples are taken from the Onet.xml file for the STS site definition
This does not seem to be true for modules, doctemplates etc, and also goes directly against what Vesa specifies in the FAQ part of his article. I am speculating though, if what is ment on MSDN is, that feature stapling still is triggered based on the base template.
Can anyone share their thoughts on this? Despite being hyped as the new black, CWT unfortulately is lacking good documentation on MSDN. :-/