DXA HTML design decisions

RE: DXA HTML design decisions

Bart Koopman (former member) — Thu, 24 Dec 2015 14:16:02 GMT

[mention:1851258c721147eb972dac778d859159:e9ed411860ed4f2ba0265705b8793d05] that is not really related to the HTML design, but indeed flagged as an issue. Initially we ignored any kind of caching in the DXA web application, because we considered caching strategies something each implementation will want different, so no common ground for us to build upon. However, there is a default cache in DD4T, which automatically gets exposed and also because DXA does not set any cache headers in its HTTP response, the behaviour of the browser for client side caching can be unexpected and unwanted. We are currently revising this for DXA 1.3, and plan to do more in upcoming releases around performance and caching.

RE: DXA HTML design decisions

Raj Kumar — Thu, 24 Dec 2015 14:11:44 GMT

I don't like DXA checking each and every request of binary whether its stale or new. its slowdown the loading of assets. it should be separate thread doing all this stuff, rather than intercepting all the calls.

RE: DXA HTML design decisions

Bart Koopman (former member) — Thu, 24 Dec 2015 13:53:43 GMT

[mention:2fe22d8719924b4c949af914996511e8:e9ed411860ed4f2ba0265705b8793d05] maybe not the HTML itself (apart from fixes perhaps), but yeah it would be nice if the community could come up with some decent "skins" making the design a bit more attractive in demo scenarios. This is also something we will need in the future when we deliver DXA in the cloud in a multi tennant scenario, but I won't go into too much detail there yet ;o).
How to collaborate on that, well these skins could be packed as a module and uploaded to the eXtensions area of the Tridion Developer community https://community.sdl.com/developers/tridion_developer/m/mediagallery

RE: DXA HTML design decisions

Alvin Reyes — Thu, 24 Dec 2015 12:22:00 GMT

Nice, Bart. Do you see the HTML side of DXA evolving in the community (or even in other communities)? I know of a few DXA HTML variants for training and demos, but how could we collaborate here?

One idea we had for Spark 45, a DXA precursor was a context for the HTML design. Think that or a hackathon might fit your open source DXA model?