Hi Freddy,
I got quite frustrated when Wappler would not select my Bindings that’s probably most of my reason for going back to DW to speed up some work-flow as some of the pages have a lot of Bindings on them (and having to go in to code view to select them really slowed me down considerably).
The header menu is all external includes as is the main content area due to several different Groups viewing the pages, each served its own content based on permissions and several other factors. Likewise the footer is an invcludes file, not that complex but again there are some other versions that are deployed based upon user criteria and settings (and for update purposes, new features etc, same for the header and other includes files). All scripts are again in a separate includes file to allow for easy updates and additions across all pages calling the scripts.
A mixture of sessions created upon successful log-in and cookies via various methods. It was pointed out to me that the use of cookies is questionable… NO not at all. They are a great way to get a job done and can offer great security when deployed correctly. They can save huge amounts of execution time and the need for overly complicated actions calling multiple joins to fulfill a simple task for example. Just make sure to destoy them once you are done with them. Sessions as I mentioned also play a good part in repeating data that would otherwise be called via queries here and there. I say make as much use as you can of the great features available within the State Management extension and Wapplers functionality with regards to this area. It is there for a reason and not to be shied away from (my two cents of course)…