Jeremy Caney
My feedback
-
2 votes0 comments · SharePoint Administration » Integration with Other products · Flag idea as inappropriate… · Admin →
Jeremy Caney shared this idea ·
-
2 votes0 comments · SharePoint Administration » Integration with Other products · Flag idea as inappropriate… · Admin →
Jeremy Caney shared this idea ·
-
13 votes
An error occurred while saving the comment Jeremy Caney supported this idea ·
-
18 votes
An error occurred while saving the comment Jeremy Caney commented
FYI: There is another request for this that currently has more votes. It may be worth consolidating votes around that request to give it more visibility.
This would be really useful, especially for large deployments.
One of the best practices we preach to our clients is to establish centralized master templates, list templates, content types, and, where appropriate, web parts up-front so it's easier to manage (and cross-reference) content later.
We also use site templates for this. But the inability to inherit changes to those templates after site has been provisioned greatly limits their usefulness. Ideally, sites would have the option to continue inheriting changes from the site definition, web template, or project solution they were created with so that themes, features, web parts, and other configuration settings could be easily rolled out to a large number of subsites later on.
Jeremy