Posted by emmajane on January 30, 2013 at 3:01am
6 followers
Jump to:
| Project: | Omega |
| Version: | 7.x-4.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
fubhy and I talked about this on IRC...I hate "advanced" labelling. People are afraid of things that are labelled with a degree of difficulty. From a teaching perspective it also means that I have to teach people how to use "default" and then I have to reteach people how to use "advanced". I've been trying to think of alternate pairs of words that might work. I don't think I have the solution yet, but I wanted to open an issue about it.
Currently:
default || advanced
Suggestions:
condensed || expanded
Comments
#1
I guess the trick here is to try to capture specifically what it is that is different about the two starterkits. From what I can tell, the essential difference is the degree to which the Sass partials are broken down and made more modular. Is that correct?
If that is the case then your suggestion of 'condensed || expanded' does fit but I'd be worried that some people may confuse 'condensed' with 'minified' and presume a performance perk and/or lack of whitespace in the code.
#2
I'm not sure one has to be the opposite of the other, one can just be the default. How about:
Default || Expanded
Default || Condensed
Default || Modular
#3
I am absolute +1 on changing the names of the starterkits to something that makes more sense. I won't decide though and let the native speakers do that instead :).
So whatever you think works... go for it!
However, one thing that I would like to point out is that the advanced starterkit does not only have a more verbose Sass structure but will also contain more in-depth documentation in the future (not there yet).
#4
The goal is to also have some example files in there that you can opt-out from while generating the starterkit (via --no-readme, will probably rename that to --no-help at some point so that it makes more sense). So the goal is to also make the starterkits a viable resource documentation-wise so that you can easily refer to example preprocess / process functions or template files and frequently used hook implementations without leaving the IDE.
#5
Haven't really looked at it, but how about:
Standard || Extended
#6
+1
#7
@robin.prieschl I really liked your suggestion but decided that default should stay default. The main reason for this is that if you don't specify a starterkit in drush omega-subtheme, it uses the default theme. I don't think standard really made sense in that context.
So, renamed advanced -> extended and commited.
#8
Automatically closed -- issue fixed for 2 weeks with no activity.