themes galore
Scott Merrill
are starting to get some attention.
The Style Contest was an effort to develop themes that would work for
both Movable Type, TypePad, and LiveJournal.
http://thestylecontest.com/
Similar to the CSS Zen Garden, these themes all work through CSS only:
no code changes.
It would be _extremely_ cool if someone could create basic one-, two-,
and three-column template files for Habari, such that a user could drop
one of the Style Contest CSS files into the theme directory and have it
"just work".
This link provides information and sample files, from which one might
derive the proper way to construct the Habari template:
http://thestylecontest.com/help
--
GPG 9CFA4B35 | ski...@skippy.net | http://skippy.net/
Vix
>
> It would be _extremely_ cool if someone could create basic one-, two-,
> and three-column template files for Habari, such that a user could drop
> one of the Style Contest CSS files into the theme directory and have it
> "just work".
I do a lot of work with Livejournal themes so I can work on this.
----
Vix
http://garinungkadol.com
vkaryl
themes.... but who knows? New year, new blogging software....
Root
templates so it would certainly fit my
methodology. There has been a comment over there tho that the allowed
mark up does not include a footer. Just a thought. What I like about
the thing is that if some one is able to impose a disciplined
framework as they do - we get far more consistency in the end product.
This is a weakness in other platforms. Now by all means themers should
do their own thing - but for shipping in defaults and mu hosted
environments, then a common nomenclature and classes framework is
ideal. Good stuff. I hadn't seen it before.
Root
On Feb 5, 2:29 am, Scott Merrill <ski...@skippy.net> wrote:
> I've mentioned this before, but it's worth repeating now that templates
> are starting to get some attention.
>
I can't help but mention in passing that on the link given to
thestylecontest - that there is a 2 px footer jog :)
This is a very poular feature in a lot of WP designs.
Matthew
> thestylecontest - that there is a 2 px footer jog :)
> This is a very poular feature in a lot of WP designs.
Can you elaborate?
Im don't know what a "2 px footer jog" is or why it might be popular.
Root
px. As it does in some WP themes. OT none of the themes seem to
validate. 14 / 15 errors.
Matthew
--
Matthew Maber, UK
www.sflwa.com
vkaryl
wouldn't make any difference here, would it? Seems that most bloggers
expect a footer these days, well even most people with "plain" html
sites do (last time I tried to convince a client he didn't need a
footer he acted as if I didn't know my own business....)
vkaryl
bane of a lot of wp themes, beginning with the default and going on
from there. I've actually not run into it in my own designs; not sure
what it is I do different....
Firas Durri
>
> Looks fine to me in both FF and Safari
>
> On 2/5/07, Root <atth...@gmail.com> wrote:
> >
> > Well on the page you arrive at the footer is offset to the left by 2
> > px. As it does in some WP themes. OT none of the themes seem to
> > validate. 14 / 15 errors.
> >
He's talking about the pre-IE7 3 pixel jog bug in Internet Explorer.
Root, please stop being so opaque.
--
Firas Durri | http://firasd.org
Root
On Feb 5, 10:08 pm, "Firas Durri" <fir...@gmail.com> wrote:
> On 2/5/07, Matthew <sfoo...@gmail.com> wrote:
>
>
>
> > Looks fine to me in both FF and Safari
>
Vix
> It would be _extremely_ cool if someone could create basic one-, two-,
> and three-column template files for Habari, such that a user could drop
> one of the Style Contest CSS files into the theme directory and have it
> "just work".
I ported the Style Contest themes for all four options. It's drop-in
ready without having to change any paths to images given Habari's
current permalinks but that will (may) change once there is a
provision for date archive permalinks.
As others have mentioned the lack of a footer, I added two ids:
#footerbody
#footerbody-inner
I also added an entry-tags class for the post tags.
I'm thinking that it would be easier if the theme options page
included a column for the name of the style sheet? That way I could
store a bunch of styles in a folder and just call the one I'd like to
use.
----
Vix
http://garinungkadol.com
vkaryl
> style-1col.zip
> 49KDownload
>
> style-2col-left.zip
> 100KDownload
>
> style-2col-right.zip
> 100KDownload
>
> style-3col.zip
> 50KDownload
Vix
Haha. I'm a girl :)
----
Vix
http://garinungkadol.com
vkaryl
Scott Merrill
> I ported the Style Contest themes for all four options. It's drop-in
> ready without having to change any paths to images given Habari's
> current permalinks but that will (may) change once there is a
> provision for date archive permalinks.
>
> As others have mentioned the lack of a footer, I added two ids:
> #footerbody
> #footerbody-inner
>
> I also added an entry-tags class for the post tags.
_Fantastic!_ This is wonderful. Thank you.
> I'm thinking that it would be easier if the theme options page
> included a column for the name of the style sheet? That way I could
> store a bunch of styles in a folder and just call the one I'd like to
> use.
This is an interesting suggestion. It certainly makes sense for the
Style Contest themes, which all use the same base template files (for
each of one-, two- and three-column layouts). I wonder how many other
templates would benefit from a selectable stylesheet, though?
Any suggestions on how you'd like to see something like this being
implemented? Should it be a per-theme option to declare the stylesheet
to use for that theme, or should it like selecting a whole new theme?
Vix
No problem. I get that a lot.
----
Vix
vkaryl
Vix
> This is an interesting suggestion. It certainly makes sense for the
> Style Contest themes, which all use the same base template files (for
> each of one-, two- and three-column layouts). I wonder how many other
> templates would benefit from a selectable stylesheet, though?
A selectable stylesheet for themes offers a great deal of flexibility.
As a theme user I don't have to constantly upload a bunch of files
whenever I want to change the look of my blog.
As a theme developer having a base to work off makes it easier to
provide different styles - the more familiar you are with how a layout
is set up the easier development is. Plus, all I have to do is package
the images and the stylesheet.
Using Livejournal as an example - they have over 30 themes to choose
from which makes it easy to customize the look a journal depending on
your css comfort level (since some styles are more complex than
others). This kind of functionality is what I hope Habari will offer.
> Any suggestions on how you'd like to see something like this being
> implemented? Should it be a per-theme option to declare the stylesheet
> to use for that theme, or should it like selecting a whole new theme?
I'm not keen on each stylesheet being considered a new theme - a
person with a lot of stylesheets would have a long list and that would
be too confusing.
Like I mentioned earlier, for each theme folder listed, I'd like to
select the from a drop-down list, the name of the style sheet I'd like
to use. By default it would be style.css so even if I only had one
stylesheet it offers a launchpad to work off.
----
Vix
Owen Winkler
>
> On 2/7/07, Scott Merrill <ski...@skippy.net> wrote:
> > This is an interesting suggestion. It certainly makes sense for the
> > Style Contest themes, which all use the same base template files (for
> > each of one-, two- and three-column layouts). I wonder how many other
> > templates would benefit from a selectable stylesheet, though?
>
> A selectable stylesheet for themes offers a great deal of flexibility.
> As a theme user I don't have to constantly upload a bunch of files
> whenever I want to change the look of my blog.
Perhaps this is a feature we can integrate into the base Theme class.
Two things:
1) Reading a stored option for the theme that has the stylesheet(s) to
include, and putting them into the theme variables to be output.
2) Providing an interface in the admin for a theme to select the
stylesheets that are packaged with the theme.
That seems like a really good idea.
Vix, thanks for the work on the theme!
Owen
vkaryl
On Feb 6, 7:21 pm, "Owen Winkler" <epit...@gmail.com> wrote:
Scott Merrill
> I ported the Style Contest themes for all four options. It's drop-in
> ready without having to change any paths to images given Habari's
> current permalinks but that will (may) change once there is a
> provision for date archive permalinks.
I'd _love_ to distribute these template files in the Habari download.
Anyone interested in making a Habari-specific CSS for each of the four
layouts? Heck, we can have more than one: anyone who's interested
should feel free to submit to this list any original stylesheet(s) they
develop for these templates.
Vix: if the popcorn stylesheet you included _is_ original, please accept
my apologies: I haven't scoured the offerings from StyleContest yet. If
it's original, may we include it? If it's not original, are you
interested in submitting original stylesheets?
That way, we can ship with 1, 2, and 3 column layouts using a default
stylesheet, and support all the StyleContest stylesheets that users
might choose to install.
Vix
> Vix: if the popcorn stylesheet you included _is_ original, please accept
> my apologies: I haven't scoured the offerings from StyleContest yet. If
> it's original, may we include it? If it's not original, are you
> interested in submitting original stylesheets?
Unfortunately it's not my original design. It's the winner of the
Style Contest. I chose it because it covers all theme options. I'll
ask the designer if she'd mind us including it.
As for additional stylesheets I'll work some up and submit it to the group.
----
Vix
Root
a coded solution. Thanks to Vix.
Multiple style sheets working of each of several templates is just the
way I wanted us to go. I do have quite a lot of issues to do with the
details of the implementation but this is not the time to get into it.
Vix has got the thing rolling. Early adopters can all look spiffy. :)
Vix
she said we can include it in the release.
Vix
Root
> Any suggestions on how you'd like to see something like this being
> implemented? Should it be a per-theme option to declare the stylesheet
> to use for that theme, or should it like selecting a whole new theme?
>
> --
> GPG 9CFA4B35 | ski...@skippy.net |http://skippy.net/
I would like to see both in the admin panel. The option to select a
whole theme (a set of template files), and then to select a style
sheet for that theme. With preview options etc. :) This is the logical
development of the separation of style and content. The generic use of
the word *themes* can be confusing on *legacy blogging platforms*. We
might need some new terminology.
vkaryl
forward to playing with the setups!
Vix
>
> I would like to see both in the admin panel. The option to select a
> whole theme (a set of template files), and then to select a style
> sheet for that theme. With preview options etc. :) This is the logical
> development of the separation of style and content.
So what you're saying is to present a list of themes and then when you
select a theme, a list of styles and previews would be shown. That
would work for me.
What I had in mind the idea was brought up was that what you would see
in the Theme options would be all the styles. Which I find
overwhelming but your explanation makes sense and is more user
friendly (kinda like a style browser for each theme).
> The generic use of
> the word *themes* can be confusing on *legacy blogging platforms*. We
> might need some new terminology.
Agreed. I prefer to use "templates" to describe the markup and
"styles" for the stylesheets.
Vix
Michael Bishop
On Feb 7, 11:12 pm, Vix <garinungka...@gmail.com> wrote:
> Agreed. I prefer to use "templates" to describe the markup and
> "styles" for the stylesheets.
But there needs to be some distinction of the "package". Without
that, there's nothing to delinieate a set of "templates" and "styles".
Otherwise, IMO, end users would confuse the fact that some "styles"
only work with a certain group of "templates".
I also think it's unlikely that all themes are going to be offered
with multiple style sheets.
I would even go as far as to say that most will not.
Michael
Vix
>
> Ditto Root - both in the admin panel would be good. Vix, I'm looking
> forward to playing with the setups!
As am I!
----
Vix
Vix
> On Feb 7, 11:12 pm, Vix <garinungka...@gmail.com> wrote:
>
> > Agreed. I prefer to use "templates" to describe the markup and
> > "styles" for the stylesheets.
>
> But there needs to be some distinction of the "package". Without
> that, there's nothing to delinieate a set of "templates" and "styles".
I'm not certain where the confusion is. When I say theme/template I'm
talking about a different markup and structure.
The template would be called "The Style Contest" or "Habari Template"
or something more interesting while the stylesheets themselves would
have their own names. Or do I just have my wires crossed?
> I also think it's unlikely that all themes are going to be offered
> with multiple style sheets.
>
> I would even go as far as to say that most will not.
I'm not certain how many other theme designers re-use markup so
perhaps I'm in the minority that does re-use the same code while
changing stylesheets.
Right now in my wordpress installation I have four theme folders, all
of which have the same set of theme files. The only difference - the
stylesheet.
It makes sense to me that it would be easier to maintain (ala the
Sandbox theme - http://www.plaintxt.org/themes/sandbox/) if all the
styles were in one folder.
Vix
Root
Well I guess what your perspective is. :) Single template / multiple
styles by different authors has historically been my modus operandi.
Not a model thats widely followed by other people it is true. But a
model that has proved for us at least very durable and surprisingly
popular. The Gemini installed user base is several thousand strong. It
has also been ported every which way on an industrial scale. Sandbox
takes that type of thing forward as well.
The mystery is why more people do not do it. ? I have a few ideas
about that but its not important.
The ultimate tool though might be an admin panel theme generator. I
understand that some legacy platforms have plugins like that. The
methodology is there. In my year off the net I hacked about at it as a
php learning tool. Could be cool. Hell of a job to put it together
though.
vkaryl
clients' sites up and going. Most of my themes have pretty much
identical files, with just different includes where needed if a REALLY
unusual setup for me (couple of 4-col ones for instance).
On Feb 7, 10:40 pm, Vix <garinungka...@gmail.com> wrote:
> Sandbox theme -http://www.plaintxt.org/themes/sandbox/) if all the
Root
that. As well as yourself Joni Muller, Jenn Ledbetter, even NTU and a
bunch of others. In short - the professionals. They are all pretty
discerning about what goes in the template to start with. I guess I
now think in modular terms but when I see things like WP com I am
struck by how much the themes have in common. There is a lot of
potential there for reuseable code as there is here. Hence I am just
testing my new Habari Genesis template pack.
Matthias Bauer
> I contacted the creator of the popcorn stylesheet, Liz Lubowitz and
> she said we can include it in the release.
I am pretty sure that for us to ship with the stylesheet, it has to be
released under the Apache License (or similarly free, BSD should be ok).
If the creator was willing to do that, could she please send a statement
saying so to the ML ("I hereby release <title> under the Apache License,
version 2.0")?
Thanks,
-Matt
Vix
>
>
> I am pretty sure that for us to ship with the stylesheet, it has to be
> released under the Apache License (or similarly free, BSD should be ok).
> If the creator was willing to do that, could she please send a statement
> saying so to the ML ("I hereby release <title> under the Apache License,
> version 2.0")?
I'll ask her to do that.
----
Vix
not.th...@gmail.com
themselves are under, and can't find anything on the style contest
site about it. To be on the safe side, shouldn't we get them cleared
for use as well? (If Byrne Reese's comments on Sandbox are anything to
go by [http://www.majordojo.com/blogging/
wordpress_mulls_standardizing_their_html.php], I wouldn't anticipate
too many problems.)
Having worked with them for a while now, I have a couple of
reservations about the 6A templates (one of which has already been
dealt with by the addition of a footer ;) ) but they're stable, have a
good pre-existing library of styles and might help Habari get away
from the 'Wordpress fork' label by showing that we're willing to take
the best elements from ALL the competition.
C
On Feb 14, 1:02 am, Vix <garinungka...@gmail.com> wrote: