How to find other embedded DWT fields?

Question

In the Building Template DWT block, we can use several "free" variables, such as @@Component.Title@@ or @@Component.ID@@ , as well as the built-in DWT Functions .

I did not understand that we could also get a description of the component schema using @@Component.Description@@ or @@Description@@ .

Ready Default Dreamweaver Component Design has a good set of examples, as well as an example of iterating over Tridion Cook books , and SDL Live Content .

How else can you find other permitted built-in functions and DWT variables, programmatic or others?

In other words, I would not have thought that @@Description@@ was even available in DWT without first seeing an example (and not the one I have for it yet).

Edit (June 8, 2013): I found additional information about the contents of SDL Live ( login required ). Of course, we can use the available Package Variables as described in the documentation .

Answer 1

Having studied a little, I found that if we go to the tridion.contenmanager.config file, we find a node that refers to the type of the Dreamweaver mediator:

 <mediator matchMIMEType="text/x-tcm-dreamweaver" type="Tridion.ContentManager.Templating.Dreamweaver.DreamweaverMediator" /> 

This namespace is inside Tridion.ContentManager.Templating.dll

Decompilation is the best way to find out what's inside and learn something. Since this is .Net code, this will not be a problem, there are many good free tools available. I have been using JustDecompile recently

I didn't go too deep into the code, but I see that there is a TridionObjectSource class with the number of constants for reserved words, for example:

• ReservedNameTitle
• ReservedNameDescription

Finding where these constants are used in your code can help you better understand what they are doing and the way the Dreamweaver broker works.

Sounds like an interesting training exercise.

Answer 2

I believe that you were looking for documentation for an answer and left empty. I suggest you go to the relevant part of the LiveContent documentation and add a comment. This will allow you to directly contact the documentation team, and I'm sure it will be very interesting for them to hear about a function that was not properly covered. With some luck, they will update it, and you will do us all a favor.

I also have a liking for the “help yourself” approach, but if you discover a feature of your own software analysis and it will be removed in a later release, you will not have any legs left to stand on complain about it. So help Tridion get the documentation and then use it with confidence.