Demo > Can't Add Link To Image

[duracell80]

Can't link an image in Demo, clicking the "+" in the plus button menu, replaces the image with a link. Found in Windows 10 Chrome.

[wincent]

Thanks for this (and the other issues you've just filed), @duracell80.

[duracell80]

I get that the team is under resourced and can only hope that the severity of the quality issues are highlighted further on up. Where attention can be brought to the appropriate people so that something can be done to get out of the trenches.

This is the interface to users content. It is being said that a content management system can't give resources to its content editor.

Working around Alloy Editor in DXP by providing functionality outside of AE is ok in areas like content pages, but other areas will be left behind, perhaps to be deprecated which would be a real shame.

It would be a shame to loose blogs, to have to create blog pages manually in content pages just to make the content attractive.

I really feel for you guys, something needs to happen to give this editor the resources it needs because I think this project is a canary in a coal mine.

[jbalsas]

Hey @duracell80, as @wincent has said here and in other interactions, we truly appreciate your continued passion, engagement and will to produce the best experience for your users. I think @wincent has explained

A bit of an off-topic for this issue, but one thing you've raised here (and in the forums in the past) which I think is the key point is that content generation needs to be seen and worked out holistically rather than as an aggregate of technical features. While AlloyEditor has many many shortcomings, there are many instances where a poor integration or specific team decisions have made that experience suffer at the expense of the editor itself.

I've been bringing this up with Product Management internally, and we're all in agreement that this needs to be re-evaluated and a better focus needs to be put in each content-generating application independently to produce the best possible experience in each case. To that end, we plan to:

• Reduce maintenance surface to focus efforts on configuration and content generation. This might mean implementing AlloyEditor UX on top of CKEditor's Balloon Toolbar so we can focus on adding features on top rather than having to reimplement them here.
• Simplify editor configuration API and interface (so no Java coding is required)
• Review each instance of content generation with the corresponding team to understand what's the best possible experience in each case

[duracell80]

The focus is very much needed. I think because we have a content management system that is giving people a bad experience it leads to a bad perception of your overall product.

I just don't understand why the main input of content in a content management system is under resourced.

It's not like we fix it and it's fixed. I have to keep highlighting the same issues over and over again. Mostly it's the image capabilities or lack of, but there are other issues.