slingshot.site.configuration.xml vs. share-config-custom.xml

[mwallach]

In 4.2/5.0, I'm wanting to set/change default theme to one I created. i can do this my creating a slingshot.site.configuration.xml and specifying:

   <source-id>site</source-id>
   <properties>
      <theme>myTheme</theme>
      <root-page>site-index</root-page>
   </properties>


I can also do this in share-config-custom:

<config evaluator="string-compare" condition="WebFramework">
   <web-framework>
       <defaults>
           <theme>myTheme</theme>
       </defaults>
   </web-framework>
   </config>

Is one method preferred over other? Is the slingshot config more specific to controlling theme in site vs. overall? How would you determine which is preferred and/or how to know this? Is there somewhere in source one would to make this determination (slingshot vs. share-config file)?

Mike

[mitpatoliya]

share-config-custom.xml is the preferred way. The reason is this is one place where you could put all your most of the custom configurations so easy to maintain and manage.
Also if you notice in the config related to share-config you are only modifying theme part you do not have to specify any other details so less error prone compare to first one.