Design integration requirements
advertisement
Design integration requirements Introduction Those requirements apply to Full Design Integration paid feature. Your design pack must fulfill all of those, in order to be accepted and integrated. Otherwise it will be rejected and sent back to you. Of course, if you want to integrate the design for your own then you don’t have to obey any rules. Basics The design packs must contain at least 4 HTML pages (listed below). It should be packed in .ZIP or .RAR format. File structure must be as follows: Images/Global/all images Styles/css stylesheeets Scripts/JS or jQuery files Global.master.html (main wrapper) Content.master.html Page.master.html Default.html The concept There is one main wrapper (Global.master.html), two sub-wrappers (Content.master.html and Page.master.html) and one content page (Default.html). Global.master.html This is the main wrapper and the only one full HTML page (contains <html>, <head>, <body> etc. tags). It must have: Logo Top-Menu (2 versions for logged and not-logged users. We recommend [Home, Advertise, Login, Register, Forum] and [Home, Account, Ads, Forum, Logout] but it is all up to you how the menu will look like and what it will include) Footer (must be the place for Language selection and footer links) Of course it is all up to the designer, where those elements would be. You can have “footer” on the top of the page and even divide it into multiple parts (Flags on the top, links on the bottom etc.) Default.html This is the main page user will see when entering the website. As you see on the image this is not full HTML page, just a part of it which fits to the Global.master.html. Content.master.html This is helpful “bridge” page if you have problems with putting Page.master.html into Global.master.html. If you don’t have any, you can leave it blank. Page.master.html This is the most important one. Submenu It must have submenu (wherever you want) which provide navigation to the service sub-websites. Because submenu is not always displayed it must be easy to remove it. E.g you put menu in <div id=menu1><ul>…</ul></div>. If we remove whole <div id=menu1><ul>…</ul></div> section, page must look fine without the menu. See Titan Demo http://demo.usetitan.com/usr/default (with menu) and http://demo.usetitan.com/proofs (without menu) for the example. Sidebar Sidebar has two states: for logged in users and not-logged in users. You can put whatever info you want here (On Titan Demo for not-logged in we display news and Constant Banner, for logged-in we display avatar, membership, balances, achievements and also Constant Banner). If you leave it blank we will display defaults. Other pages If you want to any other pages to look different than in Titan demo, please provide corresponding .HTML source files. If you don’t provide any additional files, we will only update the various color schemes to fit your new design but the core concept design (tables, buttons, forms) will look the same as in the Titan demo. Notifications If you want your design to support notifications, just add one sample formatted number in Top-Menu/Submenu. Tips for designers Create page1_default.html and page2_content.html as you always do. Change the folder paths for the required ones. Now extract “content” part from page1_default.html into Default.html. You have 2/4 pages done (page1_default.html without content is now Global.master.html). Now fit page2_content.html “content” into Global.master.html file. Extract the content which fit into Content.master.html and Page.master.html. Additional questions If you have any questions (e.g. you are a designer, and have some doubts) feel free to write to contact@usetitan.com
