History of PackageMSS
Version 9 | Current version | |
---|---|---|
this is no actual feature yet, but a feature proposal PrefaceThemes are the reason for webmasters to try out a CMS. Only if its looks can easily be personalized it is considered a professional solution. Modern CMS sport features like "Themes", "Styles", or "Skins". Most of them, though, just have one actual theme, and some variations of colors and borders. The (now) classic source for what themes actually mean, is probably CSS Zen Garden. Every theme is different, still you could vary each one of them with another logo and some different colors to gain a nice sub-theme.Our PlanA wizard called my site stylist (not just CSS, but MSS) encourages an admin or user to adapt a given theme and apply basic style-changes. The result will not be a new theme, but a sub-theme. MSS aims at the user who doesn't know enough CSS and HTML to produce a full fledged theme by himself. The main target group is the admin of a Tikipro site. After the MSS wizard is done, the resulting style will give his site a "different from the rest" look.Flow chart about the whole thingA designer designed a theme called grind. An unknown admin likes it and decides to use it for his Tikipro site. Four files are involved:
grind.css source[+]grind_comments_en.css source[+]We had somehow educated that designer that his theme would never be part of Tikipro, and thus he would remain un-honored for the rest of his life, if he didn't deliver a thought-through CSS and very interesting comments in a 2nd file. As soon as the unknown admin fires up his My Site Stylist (MSS), a script must open up grind.css and grind_comments_en.css (language depending on user settings) and collect the selectors, the styles, and the comments, so that the following huge form can happen to the user:this form is currently under heavy development user's form source code / form[+]Now, ))grind_admin.css(( will be created. In header.tpl it will have to be included as the very last style sheet, so that its style overwrites grind.css (the !important trick will also serve that purpose). grind_admin.css source[+]That's it. Let's talk about
Suggestions for Tags, Attributes and Classes that can be set:
please add yout thoughts as you see fit Problems
| this is no actual feature yet, but a feature proposal PrefaceThemes are needed in a CMS for consistent appearance and flexibility is needed so it can be adjusted for a site. Only if its looks can easily be personalized it is considered a professional solution. Modern CMS sport features like "Themes", "Styles", or "Skins". Most of them, though, just have one actual theme, and some variations of colors and borders. The (now) classic source for what themes actually mean, is probably CSS Zen Garden. Every theme is different, still you could vary each one of them with another logo and some different colors to gain a nice sub-theme.Our PlanA wizard called my site stylist (not just CSS, but MSS) encourages an admin or user to adapt a given theme and apply basic style-changes. The result will not be a new theme, but a sub-theme. MSS aims at the user who doesn't know enough CSS and HTML to produce a full fledged theme by himself. The main target group is the admin of a bitweaver site. After the MSS wizard is done, the resulting style will give his site a "different from the rest" look.Flow chart about the whole thingA designer designed a theme called grind. An unknown admin likes it and decides to use it for his bitweaver site. Four files are involved:
grind.css source[+]grind_comments_en.css source[+]We had somehow educated that designer that his theme would never be part of bitweaver, and thus he would remain un-honored for the rest of his life, if he didn't deliver a thought-through CSS and very interesting comments in a 2nd file. As soon as the unknown admin fires up his My Site Stylist (MSS), a script must open up grind.css and grind_comments_en.css (language depending on user settings) and collect the selectors, the styles, and the comments, so that the following huge form can happen to the user:this form is currently under heavy development user's form source code / form[+]Now, ))grind_admin.css(( will be created. In header.tpl it will have to be included as the very last style sheet, so that its style overwrites grind.css (the !important trick will also serve that purpose). grind_admin.css source[+]That's it. Let's talk about
Suggestions for Tags, Attributes and Classes that can be set:
please add yout thoughts as you see fit Problems
|