- I think it's doing the Zen 'platform' a disservice. It's a bland theme and not a particularly exciting example of Zen's sub themeability.
- It surely must be an extra burden for the Zen maintainer.
- No real harm done if provided as a seperate download I think? Maaaaybe you can even find another maintainer for it.
- It's just an extra theme in my Drupal's theme list I would rather not have to remove everytime I update Zen.

Thoughts?

Comments

I support this proposal.

+1. We are safe to remove this.

I used it the other day, I needed a bland theme that was easy to modify. Maybe the dis-service could be counter acted by adding more "exciting" sub themes? Maybe Zen classic and other sub themes could be moved into their own spot? I dont really know how theme projects work, as I'm used to modules. Mostly I just wanted to say, I used it the other day.

@YesCT: Yes, the proposal is to remove it from the Zen download and make it a separate project, not to kill it, you'd still be able to download and use it.

I'd just like to see the Zen theme focus on being just the framework+starterkit.

Not many zen sub themes get contributed back at all and even if they do, it would not be useful to add them to the actual Zen download. It would mean a lot more work for the maintainer and the use case for any 'designed' sub theme would always be smaller than for the primary use case of the actual framework.

Sounds reasonable. Could the zen sub themes be put in the zen catagory, or easy to locate some how when browsing or searching for themes? Maybe ask for a community guideline when contributing a zen sub theme that the project description use the phrase "zen subtheme" and link to the main zen project/theme. I guess that might happen naturally. Maybe there could be a link from the zen project page to an issue in the queue, and people could add to that issue a link to new zen subthemes? Or would that be better in the docs somewhere?

Maybe this might encourage more subthemes being contributed back? But, that would require themers to learn to use the revision control system and maintains their own project...

Version:6.x-2.x-dev» 6.x-1.x-dev
Status:Active» Patch (to be ported)

I think keeping sub-themes out of the main Zen download is good idea. So, Zen Classic should be moved to its own project.

BTW, I named it “Zen Classic” when I moved that styling to a sub-theme of Zen; the style (which was ported to Drupal) was originally called Deliciously Blue.

However, if this is going to be put into a separate project, two things need to be resolved:

  1. We need a maintainer for it. I’m not volunteering. :-p
  2. The maintainer needs to resolve the lingering licensing issues. See #143795: (More than) 43 Non-GPL Themes hosted on Drupal.org and my comment at #30.

Removed in 6.x-2.x-dev.

Status:Patch (to be ported)» Fixed

Removed from 6.x-1.x-dev.

Version:6.x-1.x-dev» 5.x-1.x-dev
Status:Fixed» Patch (to be ported)

Per the licensing issues, I'm removing it from 5.x-1.x-dev as well.

Status:Patch (to be ported)» Fixed

Done.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Component:Subtheme: Zen Classic» layout.css

Component:layout.css» Miscellaneous

subscribe