When creating content with entities (e.g. Product Name), these entities have to be written in the content as normal text. Considering Pre-Embargo and Post-Embargo scenarios, the Product Name may initially be a Code Name, which needs then to be manually found and updated in all the content. Also, as localisation is involved, this is a very time consuming activity and prone to mistakes.

We are using taxonomy for creating the properties of these entities, which in this example would contain the Code Name and Product Name. The idea would be to be able to add into the content the entity keywords rather than written normal text, which when publishing to Staging and Live, based on embargo dates, would determine which value(s) would be added in the published content.

For example, where the [ ] is used to show the added keyword in the content:

1. Entity in normal content: The new SDL Tridion Sites 9.6 will introduce new cutting edge features that will change the CMS world.
2. Entity as a keyword: The new [SDL Tridion Sites 9.6] will introduce new cutting edge features that will change the CMS world.

This would also require that content sent for translation would recognise keywords in the content and treat them as non-translatable elements (as they will go through their own localisation workflow).