|
AJHall, I have some points to relay as feedback from working with your member templates:
Get rid of fractured tables in html, by 'fractured' I mean tables that are generated from various template pieces where table can start in one file continue in other files with some more tables, etc. Once we did complete members design with our own sliced html of course, without tables - man, it was a pain to bring it over into your templates, although I love smarty ;)
I haven't looked in a while at ElevatedX templates, if you still use tables I would suggest make your members templates table-less except only where it's required for tabular data. We could help with it btw, we have very good html coders on our staff.
Personally, I usually don't require any live support when working with new systems given it has good documentation along with it where
general template file structure covered and or visualized;
which templates are part of others;
list of all available variables/arrays/objects and mention whichever only available to certain templates;
guide how new pages can be created and linked within;
instructions how a new theme could be created/added/copied, since editing default is never a good idea, and maybe add a feature to quickly switch between them from admin and add ability for devs to test out theme before applying it in live production.
templates need to be as flexible and simple as possible, then designers can do with them as they please - bring over their code or adjust current code/style easily.
|