I created several sites using Framework and will stick to it for further development. It takes less time to create a new theme with Framework then using other framework themes, like Zen.
So thanks for this very usefull theme.

I have a comment and a request. Not about the quality but about the usability of the theme.

1. The official documentation of Drupal recommends to make a clone of a formal published theme when changing something for your own site. Up till my current project, I forgot to do this using Framework. So upgrades now are more difficult for me (my problem).
I used the Zen framework several times. The bright side of this theme is: there is a "starterkit" for everybody to start changing the theme. Everybody starting to change the theme immediately knows he should use the starterkit and how.
For my current project: I used the Zen starterkit to make a sub-theme of Framework.
My request: can you supply a "starterkit" with your theme, including the great, structured, but empty css file?

2. Since v6.x-3.0 I get a annoying warning in the available updates: "not supported". I will upgrade to 3.0, but don't have the time at this very moment. Is it possible to give a less strict warning by moving v2.6 to other releases and marking it as "no future updates"?
Since 3.0 is a rewrite, the use of an own sub-theme wouldn't have helped with the timing of the upgrade, but, yes indeed, with the impact.

Comments

andregriffin’s picture

andregriffin commented

Thanks for the comments. I will look into including an empty sub-theme into the next release.

andregriffin’s picture

andregriffin commented

Thinking about it, I usually find myself adding to or altering just about every CSS selector I've included in the default CSS file, and I would personally find it quite annoying having to go back to the "base-theme" CSS file to see what I need to override. I'd like to get some more users's perspective on this.

Really, I don't see being able to "Upgrade" Framework of much importance to Framework users, as the theme is intended to be altered beyond recognition, and once it's working to a user's needs as a custom theme, there isn't much a change in the "Official Framework" can do for it. Most changes involve small tweaks that make it more universally friendly to ways in which it might be altered, or just organizational adjustments, or just small things that keep the "wtfs per minute" down to a minimum. These things don't do much for an altered theme that is already working to a user's needs. If I'm wrong in this assumption, please let me know.

petarb’s picture

petarb commented

Hi Andre

I use Framework almost exclusively now. I owe you a donation!

Let's get back on subject. I agree 100% with your last statement. Sub theming is great for what it is (personally I find it annoying and a bit bloated), but Framework is what I use for some pretty deep theming. My final custom themes look NOTHING like Framework, and I ruthlessly remove and change lots of code in Framework - not just CSS. If you want to go the subtheming route, there are plenty of other themes like Zen which will float your boat but Framework is a different beast entirely. Keep it simple, keep it the way probably most of your users use it for - a blank canvas which they change for their own purposes.

About to see now 7.0 goes. Thanks again.

andregriffin’s picture

andregriffin commented

PetarB,

This is what I thought. This is exactly how I use Framework, and dealing with subtheming would be detrimental to my workflow. I understand users who feel the compulsive need to make sure they're using the "latest and greatest" version, but thats not really necessary with Framework. Yes, occasionally there may be some bugs, but if it's a problem, an Issue is created explaining a simple fix, and is not usually something that requires an "version update" of the theme.

If it really came down to it, I could include a subtheme and users could just choose whether or not to use it, but I think that may give most new users the wrong impression about how to approach using Framework.

Anyway, thanks for the feedback. Always glad to hear from the users, and yes donations are always appreciated ;)

andregriffin’s picture

andregriffin commented
Status: Active » Closed (works as designed)