Blog - All Comments

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 2)

Jonathan Williams — Tue, 05 Jun 2018 09:01:04 GMT

I really like the new designs and especially the extra attention that Experience Manager is getting. Keep up the good work!

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Alvin Reyes — Sun, 18 Feb 2018 11:10:31 GMT

I've definitely heard requests to remove the type column, especially since it's implied by context and the item icons already.

Perhaps it wouldn't be in a future version of Tridion Sites or it could be replaced by something more specific (or maybe actionable), like the specific schema rather than just the fact that something is a Component.

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Philipp Engel — Mon, 15 Jan 2018 15:48:16 GMT

Hi [mention:ecb152f8469d483cb9d301eda33b67ca:e9ed411860ed4f2ba0265705b8793d05] thanks for your feedback! Really appreciate the effort and are excited to hear that you think it’s a good direction.

Let me respond to your questions:

Type Column: You are correct to ask if we should have a “type” column in the CME lists (As this is not the most useful one). I actually envision the new UI to work as most modern web applications: You get some default columns for a list, which should represent a reasonable and useful selection (and “type” might not be in there). But a right click would reveal a whole range of other data column that you can add as well. Drag and drop should be the way to rearrange. This could be saved per user and list type (e.g. all lists for “folder” will show that).

Navigation: Should be personalized according to roles and permissions. So a user should only see the navigation options she needs (and that might exclude “Targeting” already), but if your organization does not use “Targeting” at all then it would be hidden of course.

First time login: This follows the general UX strategy for most of the UI which is: Provide a good and reasonable default (e.g. a generic “welcome to Tridion” video) but make sure it’s easy to customize to the needs of the particular customer.

Repeated Login: This is an example how a landing page could change from “very simple – what’s her to see” to “here are the information and actions you need for your job”. So the question would be: What would useful and relevant for your users when they enter Tridion?

Agile/Kanban boards in Tridion: I understand your concern regarding duplication of tasks and boards, especially as all organizations have existing tooling (e.g. Jira) that does this very well. We are discussing this at the moment. I think a better strategy would be to expose tasks in Tridion via an API towards such tools (e.g. Jira) and allow some basic visualization and interaction (e.g. moving a task from one column to the next) in case a customer does not use any other tool.

Again thanks a lot for your feedback! Let me know if you have more.

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Andrew Ross — Thu, 28 Dec 2017 21:24:37 GMT

Part 1 Feedback.

Overall, I think the design will be appealing to the SDL user base - both technical and content users.

I think the CME UI will initially be a learning curve for those who are in there on a daily basis, but general concepts like Publications and list views within should help with any initial confusion – as far as browsing directory levels and ultimately finding your content items.

Consideration - Seems like the perfect time to ask within the CME, do we really need to have “Type” column carried forward within the list view; considering it is also accompanied with an icon that distinctly separates the different types? I know in our implementation, I had to swap that column for a Schema Name Column, which is much more necessary when looking at items in a list view.

Liked:

- Overall UI redesign

- Concept of “Roles and Personas”

- Love the “Activity Updates” stream

- Workflow and especially Translation cards will be popular, qq is there a DXA for Tridion workflow or is that coming from Translation Manager workflow?

Questions:

- “Navigation” what if we are not using SDL personalization or any navigational item, can we hide it? For example, if we are not using SDL Personalization, is the “Targeting” tab in the navigation still visible?

- “First-time Login” page will it ship with a SDL Product video and/or will we have an opportunity to upload our own branded implementation video there instead?

- "Dashboard" What about an api that we could hook into here? For example, hook into the web traffic from a vendor like Adobe or Google for analytics could work well as apart of the dashboard cards (or maybe as prewired widgets to choose from?),

- Looking at it from a more decoupled presentation model where those insights are loosely tied to the content and templates inside of Tridion

Considerations:

- Overall the evolution of the “Repeated Login” experience is a pretty cool new concept, and although I could see use-cases where this would work with well with decentralized teams (and centralized teams with the Translation metrics alone), I also think the users could complain that this is duplicated effort of what is in our daily scrum tools.

- Looking more into Dashboard - What would work well (for us) would be if it was an api and we could pump from our scrum tool into this space or some sort of ux combination or if a better spot would be in the “Projects” sub navigation of “Activity”.

- If you’re in an organization that has daily scrum’s that ultimately bubble up to scrum of scrums meetings, it could be duplicate work to use other options as far as Agile methodology tools considering most of those tools are dictated down at an organizational level.

- Considering the majority of all of the activity will be coming from a Production environment, and our Project Managers are not users within Production (or any instance) where content and owners of that content are extremely sensitive. However, other organizations might have users that wear many hats.

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 2)

Alvin Reyes — Fri, 01 Dec 2017 15:27:23 GMT

When we last researched visualizations, I asked the community what they were doing or being asked about in this question:

tridion.meta.stackexchange.com/.../example-tridion-reports

I'd definitely recommend our community of customers and implementers to add feedback to this post and/or to that Tridion Stack Exchange Meta question to help discuss real-life use cases.

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Philipp Engel — Thu, 09 Nov 2017 13:13:43 GMT

[mention:4600ff517e424975a207ffeba2ae0d34:e9ed411860ed4f2ba0265705b8793d05] Thanks for your feedback, glad you like our direction.

Creating folders and managing publications will be part of the next weeks post, which focuses on tasks and needs of the implementation and power user audience. Stay tuned!

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Philipp Engel — Thu, 09 Nov 2017 13:10:04 GMT

[mention:2fe22d8719924b4c949af914996511e8:e9ed411860ed4f2ba0265705b8793d05] Yes this is beyond Tridion Sites 9.

And yes we are more than aware of the special needs for power users and implementers, I will address design concepts for them in the second part of this post next week.

But to your question - I agree that the content of an onboarding experience (and the entire implementation setup for that matter) should remain flexible and adjustable for implementers so they can make it specific and relevant to each implementation and the needs and characteristics of the individual customer. This is much easier of course if the "default" setup is provided in a way that works great as it is, but that is also simple to adjusted so you can focus on the elements that really make a difference. We will certainly review your proposals and ideas from www.createandbreak.net/.../training-your-sdl-tridion-cms.html

Thanks for your feedback!

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Philipp Engel — Thu, 09 Nov 2017 12:54:40 GMT

[mention:56998976837d4672bdef0764b5d379dc:e9ed411860ed4f2ba0265705b8793d05] We have not explored connectors in-depth yet, but yes we discussed the need to connect Projects and related tasks to industry standard tools such as Jira, Trello, Asana, etc. We will make sure that connectivity is possible via API and see which connectors we will provide out of the box and which could be provided by the community.

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Mathijs Panhuijsen — Thu, 09 Nov 2017 09:46:12 GMT

What I like best about the new approach is the task-oriented perspective. From a documentation viewpoint, this is a major breakthrough, allowing us to make our help topics context-sensitive, which we can't really do now. And from a usability viewpoint, it works wonders to make the interface less intimidating and overwhelming.

I do wonder, though: where do you do "auxiliary" tasks like creating a Folder, navigating through a publication, and other stuff like that?

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Alvin Reyes — Thu, 09 Nov 2017 02:25:51 GMT

[mention:91366a4678d94473b65b802f5999224b:e9ed411860ed4f2ba0265705b8793d05]: impressive!

To be clear, we might start working with the new UI/UX approach for Tridion Sites 9 but this is definitely for beyond 9, right?

Initial feedback:

I suspect moving from a slide out navigation to top navigation would help keep context and frequent tasks nearby. For example, one complaint we've had on Translation Jobs in the slide out meant it was farther away from the actual working area and content you're translating.

I'm wary of simplifying too much for all users. I'm glad you called out more personas beyond the occasional user. :-)

Though I'm also aware of the initial learning curve with any software. I'd expect the onboarding experience to be something you could revisit as a user if you wanted to. Ideally you'd also be able to see implementation-specific information.

I'm a bit meta in that I feel the UX should be easy for users but also easy for power users and implementers to guide other users. See some of these kinds of features that I love about Tridion: www.createandbreak.net/.../training-your-sdl-tridion-cms.html

I think our biggest opportunity and challenge is in choosing what to focus on first and validating those Graphene implementations with customers and especially end users. The transparency (this far upstream) is definitely welcome and refreshing!

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Alvin Reyes — Thu, 09 Nov 2017 01:48:53 GMT

[mention:56998976837d4672bdef0764b5d379dc:e9ed411860ed4f2ba0265705b8793d05] I've heard one JIRA Integration request which I asked [mention:27ca963e2fe24717923c82a5a5681cf2:e9ed411860ed4f2ba0265705b8793d05] to look into an example (see his Alchemy extension).

Maybe this is an interesting candidate for our Connectors. See: community.sdl.com/.../integration-to-create-jira-items-or-requests-from-the-context-of-a-website.

I know we use JIRA, but how does it fare compared to other work tracking systems?

RE: A Peek Into the Future UX and UI Beyond Tridion Sites 9 (Part 1)

Karim Mazzoni — Tue, 07 Nov 2017 17:14:32 GMT

Have you explored connectors to productivity tools, such as Jira, for the Projects aspect?