You might be using some custom workflow !! but OOB it should work...

Hi Amrit,   I doubt if there are multiple of edtions of AEM 6.0. However, you can find all the documentations w.r.t AEM 6.0 here http://docs.adobe.com/docs/en/aem/6-0.html

you can refer here [1][1] http://dev.day.com/docs/en/cq/current/deploying/upgrading.html

add a node with a sling:resourceType 'cq/personalization/components/target' programatically similar to other nodes. This creates a target componentUnder this, you can create a node by name 'default' with the sling:resourceType mapping to your component would get the default content to it.

You can see the rollout configs used to create the geometrixx mobile site and follow the same. 

You can do in multiple ways1st approach : Create a page property for a template at site page. So that property can be set at every site level2nd approach : If you want to use it in OSGi, then create a OSGi configuration at each site and set this property it depends on where and how you need to use t...

I agree with @josh.. 'Deny' first is the approach we need to follow.

in this case, it depends on the order in which the rules are applied.You can understand this by looking at rep:policy node at each of your project node and the order of permissions applied under each of these policy node

that you cant change there in the configMgr. However, you can have your PID names under your config folder in /apps (eg: PID-test1, PID-test2). So you can refer that which will be user friendly to identify.

you can customize the deactivate action and assign that service when you click on 'deactivate' button