To be able for each language versions of an item to have their own renderings in our Sitecore instance version 7.2, the __Renderings field shared option was set to false. This is not Sitecore Best Practice, but this is how it was solved. When migrating the content to Sitecore 8.2 I wrote a Power Shell script to migrate the rendering settings to the new __Final Rendering field.
The editors at the company where I work have been working on a new content tree in Sitecore. First we cloned the Home-node to a NewHome node. This way they could rearrange the structure without changing the pulished one. Still they got updates that were applied to the Home node. When we went live with the new structure we wanted all the old search indexed pages to be redirected to the new page in the new structure. This is how we did it!
We received a lot of items from our translation agancy Lionbridge. I would like to make it as simple as possible for our editors to find and approve the items in the Sitecore Editor. This is how it was solved.
Our organisation is working on a new content structure and took a decision to do this by creating a new content tree by cloning the present one. When it was time to go live with the new content we found that when deleting the clone ID we lost a lot of information on the clone item. The only way to save the information on the fields were to break the inheritance and then delete the dependency to the master item. Doing that manually would have taken a huge amout of time on thousands of items in 16 languages. This was a great opportunity to figure out how to use the Sitecore PowerShell Extension!
I needed to update a NuGet package in Visual Studio using the Package Manager Console but the network policy settings were overriding my local client permissions. This is how to solve the issue.