SDL Tridion Introduction Diagram Proposal. What do you think?

RE: SDL Tridion Introduction Diagram Proposal. What do you think?

Alvin Reyes — Sat, 22 Feb 2020 11:35:21 GMT

As a follow-up to this post, see the latest iteration(s) of the diagram is the SDL Documentation Center.

RE: SDL Tridion Introduction Diagram Proposal. What do you think?

Alvin Reyes — Mon, 16 Oct 2017 14:48:47 GMT

Let's continue the discussion here: community.sdl.com/.../14517

RE: SDL Tridion Introduction Diagram Proposal. What do you think?

Julie Landman — Fri, 13 Oct 2017 14:09:01 GMT

Now for a second comment on #4 regarding where/how Blueprinting should be represented. I am not certain how it ended up in D&D, but agree this may not be the best place. I do think it needs to be included though, even if it is a logical structure. As I am considering it again now, I think that it should be an organizational item. In fact, this is where the options/ribbon for it is located in the Explorer toolbar. Furthermore, the label should be "BluePrint Hierarchy" to match what is is in the user interface. Thoughts?

RE: SDL Tridion Introduction Diagram Proposal. What do you think?

Julie Landman — Fri, 13 Oct 2017 13:32:50 GMT

Hi Ron. Julie here. Thanks for your feedback! I have a few thoughts to add to Alvin's.

We are all totally in agreement on #1 (obvious) and on #2.

On #3, I'm not quite certain we are thinking about this from the same perspective. Indeed, schemas are selected by Editors when working with pages and components, but I think the reasons they were put in the Development and Design category is that they do not themselves represent content. Basically, I saw the Editorial Items category as including the things that the Editor role has primary responsibility for as an author/creator/editor. Would Editors be the creators of the schemas? I thought that schemas are pre-existing from an Editors point of view, and that someone else, someone more technical, would have created them as part of the D&D role/phase of implementation, but perhaps I am wrong about that.

RE: SDL Tridion Introduction Diagram Proposal. What do you think?

Alvin Reyes — Thu, 05 Oct 2017 14:55:33 GMT

Good catch and nice suggestions. I'm wondering why we had BluePrinting in the original diagram. Perhaps it was to let new users learn about this very important concept even if it didn't have an actual "item" in the system? We might want to keep it somewhere in the diagram.

Schemas definitely relate to Editorial Items, especially since editors select them and they define fields for Components and Pages. But editors also select templates so I'm thinking Schemas are still a development "thing."

RE: SDL Tridion Introduction Diagram Proposal. What do you think?

Ron Grisnich — Tue, 03 Oct 2017 13:09:30 GMT

My initial feedback:

1. Rename "DreamWeaver Templating" to "Dreamweaver Templating"

2. Move "Publications" into "Organization & Classification"

3. Move "Schemas" to "Editorial Items"

4. Remove "BluePrinting" from "Design & Development"