Think back of three key words you extracted out of the first notions you got when learning Tridion. It will not be a wild guess to say one of those key words would likely be 'Blueprinting'.
The Blueprinting hierarchy within Tridion is the skeleton of your implemenation, like the chassis of a car. Building a robust chassis will help the car when facing bumps in the road ;)
But the question now is... how to proceed when, for any reason which is not so relevant anymore, the initial Blueprinting hierarchy is not strong or extensible enough and you wish to transfer it into a new one that follows known best practices?
I do not have one answer for all the cases, but a lot of them are going to be helped by SDL Content Porter.
I am aware that many people have developed some "allergies" against Content Porter, but we should not underestimate its power for certain things; a good example is its Blueprinting awareness.
In this article, I will give you a couple of tricks and simple steps to follow when restructuring your Blueprinting hierarchy. That is to say, we are porting from and to the same environment, but from and to different Publications within that environment.
The Blueprinting hierarchy within Tridion is the skeleton of your implemenation, like the chassis of a car. Building a robust chassis will help the car when facing bumps in the road ;)
But the question now is... how to proceed when, for any reason which is not so relevant anymore, the initial Blueprinting hierarchy is not strong or extensible enough and you wish to transfer it into a new one that follows known best practices?
I do not have one answer for all the cases, but a lot of them are going to be helped by SDL Content Porter.
I am aware that many people have developed some "allergies" against Content Porter, but we should not underestimate its power for certain things; a good example is its Blueprinting awareness.
In this article, I will give you a couple of tricks and simple steps to follow when restructuring your Blueprinting hierarchy. That is to say, we are porting from and to the same environment, but from and to different Publications within that environment.
