[Suggestion] New GT template system
Important note: The suggested new template system would be completely backward compatible with the GT template used in v2.x GT products! Nobody would need to use the new skeleton based template system if doesn't want.
I decided to start a new thread about my suggested new GT template system.
The template discussion started in this thread:
Gossamer Links 3.0 mockup
I suggested:
Avoiding redundant HTML codes, and skeleton based inheriting would be important part of the new template system.
Imagine, that you want to change the whole lookout, the design of your site, and you need to change the main table structure just in one file, and not in all 30-50-100 template files you use. Do you see how much time (and time is money) could you save with this new template system? Not to mention the advantage, that you can change your site design within days (and not within weeks), which can give you the possibility to upgrade your site design as often you need, to keep yourself competitive with your competitors.
I extended the template system idea a bit to be a 4 level hierarhical template system:
Site-Theme-Page-Element + Styles template system
The 5. Style is not really a hierarchical element, as any hierarchical level may contain styles. The style could be also skeleton based, inherited if needed. That's why it's mentioned separately. I'm not style expert so comments are welcome about style implementation.
Site: site is new concept. contains the whole site skeleton, theme skeleton, pages, elements, styles.
Theme: (currently known as template set) contains theme skeleton, pages, elements, styles
Page: (currently known as template) contains pages, elements, styles
Element: (currently known as includes, but would group more than includes) contains elements, styles
Styles: contains styles only. Style is not really a hierarchical element, as any hierarchical level may contain styles. But style could be also skeleton based, inherited if needed. I'm not style expert so comments are welcome about style implementation.
Details are described following posts.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
I decided to start a new thread about my suggested new GT template system.
The template discussion started in this thread:
Gossamer Links 3.0 mockup
I suggested:
Quote:
It would be really important to improve the template system, to support skeleton-like, "sites-themes-elements" style, which can inherit content from parent content. All this, to ignore redundant HTML codes.Avoiding redundant HTML codes, and skeleton based inheriting would be important part of the new template system.
Imagine, that you want to change the whole lookout, the design of your site, and you need to change the main table structure just in one file, and not in all 30-50-100 template files you use. Do you see how much time (and time is money) could you save with this new template system? Not to mention the advantage, that you can change your site design within days (and not within weeks), which can give you the possibility to upgrade your site design as often you need, to keep yourself competitive with your competitors.
I extended the template system idea a bit to be a 4 level hierarhical template system:
Site-Theme-Page-Element + Styles template system
The 5. Style is not really a hierarchical element, as any hierarchical level may contain styles. The style could be also skeleton based, inherited if needed. That's why it's mentioned separately. I'm not style expert so comments are welcome about style implementation.
Site: site is new concept. contains the whole site skeleton, theme skeleton, pages, elements, styles.
Theme: (currently known as template set) contains theme skeleton, pages, elements, styles
Page: (currently known as template) contains pages, elements, styles
Element: (currently known as includes, but would group more than includes) contains elements, styles
Styles: contains styles only. Style is not really a hierarchical element, as any hierarchical level may contain styles. But style could be also skeleton based, inherited if needed. I'm not style expert so comments are welcome about style implementation.
Details are described following posts.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
[Suggestion] New GT template system