Make explicit plane of UX separation

[pdamoc]

The main concern of this proposal, as far as I understand it, seams to be Skeleton/Surface separation.

Maybe this could be made explicit in the README.

The layouts are more or less platform independent but the surface relates to both platform visual identity and branding concerns.

One added advantage of making this separation explicit is the possibility of providing a wire-framing theme that will produce UIs devoid of thematic decisions (colours, fonts). Images in this theme could be replaced by a simple grey box diagonal.

[nikgraf]

hehe, to me all of theses changes were equally important, but after some consideration I feel this indeed might have the most impact. I will revisit the document in the next couple days. If you have suggestions how to do it I'm all ears :smile:

Another question: I looked into Elm a bit more yesterday, but haven't touch styling there. Would these suggestion also apply fine to Elm UI libraries? Does one even exist?

[pdamoc]

If you have suggestions how to do it I'm all ears

Start with the WHY of it. Why should this separation exist? Why should anyone care? What value can it bring? I think that facilitating a discussion with the client about functionality that is unencumbered by "Surface" arguments like colours and fonts is an amazing benefit. It could make things go faster.

I would also make this more visual. :)

I looked into Elm a bit more yesterday, but haven't touch styling there. Would these suggestion also apply fine to Elm UI libraries? Does one even exist?

I think this suggestions are universal and they would apply to any project that creates a User eXperience.

To my knowledge, there is no Elm UI.

Graphics.* was an attempt at moving towards such an UI but it has been abandoned in favour of elm-html.

There are a few projects that try to create UI libraries and I believe that they would benefit tremendously by the leadership that React provides.