Skip to main content
Tridion Meta

Return to Question

replaced http://tridion.stackexchange.com/ with https://tridion.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

In looking at the Tag Synonyms (http://tridion.stackexchange.com/tags/synonymshttps://tridion.stackexchange.com/tags/synonyms) suggested by Bart, one of the suggestions that really stood out to me as maybe not being a good idea is the one for making a synonym for .

To me it looks like two of the questions (Developing Page/Component Template Designs through Visual StudioDeveloping Page/Component Template Designs through Visual Studio and How can Content Porter be automated to move commonly changed items between environments?How can Content Porter be automated to move commonly changed items between environments?) are actually about deploying (or moving) items to/between Tridion instances and not really about content-delivery in any way.

It looks like another two questions (Aspx page rendering SmartTarget <tcdl> tagsAspx page rendering SmartTarget <tcdl> tags and Publishing issue for a single pagePublishing issue for a single page) are really about publishing and the deployer and not specifically about content-delivery.

It looks like really the only question that might be considered to be about content-delivery is Implementing Multiple deployers/Broker databases vs. replicationImplementing Multiple deployers/Broker databases vs. replication even though it really spans publishing, the deployer and content-delivery.

So, the questions I have are:

  • Does this Synonym really make sense?

  • Is a better approach in this case to ensure there is a tag wiki for explaining when to use that tag along with additional instructions in the tag wiki’s for and ?

  • Although most of us probably consider the deployer services/storage as part of ‘publishing’ would it reduce some confusion if we had a tag in addition to the tag?

In looking at the Tag Synonyms (http://tridion.stackexchange.com/tags/synonyms) suggested by Bart, one of the suggestions that really stood out to me as maybe not being a good idea is the one for making a synonym for .

To me it looks like two of the questions (Developing Page/Component Template Designs through Visual Studio and How can Content Porter be automated to move commonly changed items between environments?) are actually about deploying (or moving) items to/between Tridion instances and not really about content-delivery in any way.

It looks like another two questions (Aspx page rendering SmartTarget <tcdl> tags and Publishing issue for a single page) are really about publishing and the deployer and not specifically about content-delivery.

It looks like really the only question that might be considered to be about content-delivery is Implementing Multiple deployers/Broker databases vs. replication even though it really spans publishing, the deployer and content-delivery.

So, the questions I have are:

  • Does this Synonym really make sense?

  • Is a better approach in this case to ensure there is a tag wiki for explaining when to use that tag along with additional instructions in the tag wiki’s for and ?

  • Although most of us probably consider the deployer services/storage as part of ‘publishing’ would it reduce some confusion if we had a tag in addition to the tag?

In looking at the Tag Synonyms (https://tridion.stackexchange.com/tags/synonyms) suggested by Bart, one of the suggestions that really stood out to me as maybe not being a good idea is the one for making a synonym for .

To me it looks like two of the questions (Developing Page/Component Template Designs through Visual Studio and How can Content Porter be automated to move commonly changed items between environments?) are actually about deploying (or moving) items to/between Tridion instances and not really about content-delivery in any way.

It looks like another two questions (Aspx page rendering SmartTarget <tcdl> tags and Publishing issue for a single page) are really about publishing and the deployer and not specifically about content-delivery.

It looks like really the only question that might be considered to be about content-delivery is Implementing Multiple deployers/Broker databases vs. replication even though it really spans publishing, the deployer and content-delivery.

So, the questions I have are:

  • Does this Synonym really make sense?

  • Is a better approach in this case to ensure there is a tag wiki for explaining when to use that tag along with additional instructions in the tag wiki’s for and ?

  • Although most of us probably consider the deployer services/storage as part of ‘publishing’ would it reduce some confusion if we had a tag in addition to the tag?

retagged to reflect this is about tag-synonyms
Link
Glenn Stevens Mod
Glenn Stevens Mod
  • 1.9k
  • 9
  • 18
Source Link
Glenn Stevens
Glenn Stevens
  • 1.9k
  • 9
  • 18

Should deployment be a synonym for content-delivery?

In looking at the Tag Synonyms (http://tridion.stackexchange.com/tags/synonyms) suggested by Bart, one of the suggestions that really stood out to me as maybe not being a good idea is the one for making a synonym for .

To me it looks like two of the questions (Developing Page/Component Template Designs through Visual Studio and How can Content Porter be automated to move commonly changed items between environments?) are actually about deploying (or moving) items to/between Tridion instances and not really about content-delivery in any way.

It looks like another two questions (Aspx page rendering SmartTarget <tcdl> tags and Publishing issue for a single page) are really about publishing and the deployer and not specifically about content-delivery.

It looks like really the only question that might be considered to be about content-delivery is Implementing Multiple deployers/Broker databases vs. replication even though it really spans publishing, the deployer and content-delivery.

So, the questions I have are:

  • Does this Synonym really make sense?

  • Is a better approach in this case to ensure there is a tag wiki for explaining when to use that tag along with additional instructions in the tag wiki’s for and ?

  • Although most of us probably consider the deployer services/storage as part of ‘publishing’ would it reduce some confusion if we had a tag in addition to the tag?