I'm not sure if you still have it in the core ML version. We all got a taste of it before implementation of DNN 5.5. Some of the portal settings in admin->portal settings could be localized by all portals that had multiple languages installed. A dropdown allowed us to switch culture and edit basic site settings for that other culture. You had to save the settings before you switched culture, otherwise your changes to the current culture would be lost, without warning.

To save those settings, you had to scroll down the page and click Update Settings. You were able to scroll up while your browser was communicating with the server, but you would be taken down again when the communication was completed. After that, you had to scrol back to the top to change language.This was a disaster in terms of user friendliness, and I hope users of core ML have seen improvements in newer releases.

Too much is still presented in a bulk admin page: it's all there, the things you want to change and things you shouldn't touch. I am thinking of ways to make this more functional. The function that is utmost in my mind is that of content translator. A special version of the control panel and special translation action items for content translators. I would see the future of the UI in popup windows presenting just that information you need to change and a button structure as much as possible based on "preview - accept - discard".

I can configure many modules now. I can configure the calendar module, rewriting the html template in one of its settings and customizing css in a special folder. To customize an announcements module, you will want to put the necessary css code in your skin.css. Customizing a links module still follows a different system. The point I want to make is that there is a lack of unity in the concept. The function of a designer is made unnecessary difficult. I would like, as much as possible to avoid this lack of unity. I would like to see my application as much as possible fit into the (future) DNN user friendly UI. So, I don't know if my concept of popups and preview-accept-discard will fit into

There are two roles I want to pay attention to: translators and designers. bringing some functions for the designer to the rendered page might for some be quite an improvement. Change something in the skin.css or container.css, preview, accept.

I'm contemplating a future for DSL. Last night, I did some more thorough testing on the solution, halfway the cleanup. To my surprise, one of the two issues was no longer an issue. It's a pitty I haven't found the exact cause, but good enough, one more issue to go. I haven't tested that one, because it takes different easy identfiable skins to test. I'm going to clean up all those other warnings anyway. I'm down to 66 now. Now you understand why I'm thinking of the future for the project. I just wished I knew what DNN is going to do: are there any shake-ups to be expected in the UI department? Is there a strategy?