“Sticking with the idea of bare minimums, releasing it as a theme requires name, description, and little stuff that comes with a functional theme.”

I think I get what you mean now. So your saying name, description, author, author uri should be left blank in styles.css?

As far as not releasing it as a theme, I’ll try that and see how that works out. It seems logical given the fact that I’m developing this for people who know what their doing (read: advance users) so a link to the SVN repository should suffice for now.

Thanks again for some value feedback. I need to rethink the theme development process as much as possible and abstract a few things in order for everyone to benefit from it.

Sticking with the idea of bare minimums, releasing it as a theme requires name, description, and little stuff that comes with a functional theme.

Every time you upgrade, your framework users will have to remove the little details to end up with a fill in the blank version of your framework.

To take as much as hassle out of the process as possible, don’t release it as a theme. Leave stuff like the names, description, version number out of it. Allow people like me to simply fill in the blanks.

I know it sounds like a stupid idea, but I’ve never seen a fill in the blank or pluggable feature type of framework before. You’re in position (early stages) to do that so I’m suggesting it now before it’s too late.

Thx for considering my feedback instead of taking it as pure bs =)

And I know what you mean by figuring out the target audience, that thought comes up in to mind every time I think about a new addition or feature I’m glad you address that. In a perfect world WPF would cater to both developer and non-techies (bloggers) but that’s not going to happen through one framework (i think). More on that later though because I might have a solution to get them both in. But for now as WPF is in it’s infancy, beginners can easily get it and (hopefully) follow along as the Framework matures. (hopefully I answered your question. in short until I figure the above problem out, WPF will be focus on advanced users)

However, your going to have to elaborate on what you mean by not releasing it as a theme. I’m not sure I get where your coming from.

As far as getting beefy, that’s been one of my top priorities since day one. Trust me when I tell you, boastness will be dealt with if that ever becomes an issue. I’m very strict on what goes in the core (in fact, I removed IE6 png fix a few days ago).

You’ll get a better understanding of where I’m coming from once the first release comes out.

A framework with too many features becomes its own theme with a lot of nice-to-haves (but useless) instead of serving as a blank slate for its niche, which is why the future should be focused on niche frameworks not the best framework.

If you’re focusing on bare minimums then don’t upgrade unless new useful/better techniques, which majority of the blogs should adopt, emerges.

And if you’re focusing on the bare minimums and efficiency, remove the credits in the header and style file. Also, don’t release it as a theme.

Good starting point so far. I’m looking forward to what you can do without ending up with a beefy theme. I hope you’ll make new features optional.