Detecting language please wait for.......
Note step #2 is very important, this is also something which comes up when people forget to publish the HTML design initially and find out DXA does not work without a version.json. The /system/assets folder is versions through the value inside the version.json file to prevent unwanted browser caching of our design assets when we update the HTML design. So keep in mind that when you deploy your HTML design manually, you will have to update the version string in the version.json file for it to become available direct without client caching issues. I hope this article gives you more insight and I wish you all a merry x-mas!
Raj Kumar 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.
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.
Alvin Reyes 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
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?