History: Maintainability of advanced configurations of features

Most features have a checkbox, and a large number of preferences to permit configuration.

Some needs are more vague:
* ((Project Management Requirements Introduction))
* ((Social Networking)) and ((Enterprise Social Networking))
* ((Customer Relationship Management))
* ((CartoGraf))
* {wish id=1746}
* {wish id=221}
* ((profiles:Barter_Market))

Thus, they end up as advanced configurations and perhaps profiles.

But 
* There is a maintainability challenge
* It's difficult for new users to get started
* There may be profiles for various versions of Tiki, but there are no (as of now) upgrade profiles. Ex: a diff of the two profiles, like our SQL patches)

Could we imagine something like ((doc:Workspace UI)) where there is a GUI mode which is fine for the simple use cases, but easily evolvable to advanced mode?


Related: 
* ((Configuration Management and Systems Orchestration))
* ((Divergent Preferences in Staging Development Production))
* ((System features))


-=alias=-
* (alias(Maintainability of Advanced uses of features for some use cases))
* (alias(Maintainability of Advanced configurations of features for some use cases))