Open Theme Project

Welcome To The Open Theme Project

,

The Open Theme Project was designed to make blog theme creation fast, fun and flexible. To enable this designs created using the Open Theme Project consist of two main parts - the core design and the skin design.

The Core Design is the main structure of the theme, that dictates where certain elements go and how they react. As this is kept apart from the skins and imported into the blogs that use it, it can be updated at any time allowing every blog design based on it to be updated along with it, which gives the potential of fast maintenance across potentially thousands of blogs. Another benefit of storing this seperately is that users only have to worry about tinkering with the skin part of their design.

The Skin Design is the essence of a theme. By seperating the skin from the core design, users only have to think about what images they want to use and how they'll work together as well as a few other little details. The skin has been distilled down to a few essential lines of code that just need a few details filled in to let people create something beautiful. Skins have been further refined into modules that can replace existing lines of code for different results. These are displayed further down along with a small tutorial on each module that should allow even novices to decide which one suits their needs best.


While I'm hoping that the module tutorials that I'll put up here will enable anyone to use the Open Theme Project at some level, I'll provide the basic skin code here so those with some knowledge of CSS will be able to use it straight away. The code should be saved to be used with no underlying theme.

/*This theme was created as part of the Open Theme Project*/
/*Create your own at http://my.opera.com/openthemeproject */
@import url(http://files.myopera.com/Furie/themes/basicstructure.css);

/*Text Colours*/
body,h1,h2,p,a,div.content, a:link, a:visited, a:active, a:hover,#userlinx b,.drop {color:# !important;}

/*Banner*/
#top {height:px !important;background:url() top center no-repeat;background-attachment:fixed;}

/*Background*/
body,#wrap0 {background:url() top center no-repeat;background-attachment:fixed;}
#menu,#wrap4 {background-image:none;background:url() top center no-repeat;background-attachment:fixed;}

/*Menu Titles*/
#menu_blog a {content: "Blog";}
#menu_archive a {content: "Archive";}
#menu_albums a {content: "Albums";}
#menu_forums a {content: "Forums";}
#menu_favorites a{content:"Favourites";} 
#menu_unite a{content:"Unite";}
#menu_links a{content:"Links";} 
#menu_friends a, #menu_members a{content:"Friends";}
#menu_about a {content: "About";}

/*Sidebar Headings*/
#side h2, #side caption,#blogsearch label.h2 {background:# url() no-repeat;}
#side h2, #side caption,#blogsearch label.h2,#side a#calendarmonth {color:# !important;}

I have a lot of faith in the Open Theme Project (so much so that several of my own group designs have been created using it), and will be constantly updating it so that it's the best it can possibly be.

UPDATE - Now Compatible With The Beta Version Of My Opera

Comments

Dark FurieFurie Tuesday, August 3, 2010 1:14:44 PM

I'll be inviting some people with more knowledge than me to work on the core theme and make it more flexible and accessible over time. However the current bug affecting importing CSS files means it's not currently worth it as the themes wont be updated until the bug is fixed. Themes can still be made using the basic template though.

I'll also be creating new core templates (and hoping members will donate their own templates to the project) to allow more freedom in layout.

metude Thursday, August 5, 2010 2:33:57 PM

Originally posted by Furie:

However the current bug affecting importing CSS files means it's not currently worth it as the themes wont be updated until the bug is fixed.


I have same problem, but sometime it's working properly...

Originally posted by Furie:

I'll also be creating new core templates (and hoping members will donate their own templates to the project) to allow more freedom in layout.


up

Dark FurieFurie Thursday, August 5, 2010 2:42:05 PM

Unfortunately it doesn't work properly here, meaning the base template is still in it's half finished state. The structure is there but there's a few problems, particularly with half applied borders on posts (a scrapped feature) and the site badge not appearing in the sidebar.

Suntana Thursday, August 19, 2010 9:43:45 PM

Ohhh, so there's a bug in the importing CSS function.
I wasn't aware of that. That explains the problem my friend was having then.

Furie, my friend was telling me just 2 or 3 days ago that she had been trying to experiment with importing one of your themes and DrLaunch's Neo theme and she couldn't. It didn't want to work. I tried elaborating as Step by Step as I could think of how else to explain it to her. It still didn't work for her. So, I told her, "I don't know. It should be working. I'll have to experiment with that CSS Importing function at SuntanaLab when I finish my current theme and get back to you."

So, now I see why she couldn't get it to work.
Thanks for the Heads Up. up

Suntana Thursday, August 19, 2010 9:57:30 PM

Anyway ... Ohhhhh! So this is your project, Eh, Furie?
I had no idea. When I saw the link in my Inbox, I was bigeyes left right nervous scared
Yep, I was leery. I was going, "Is this a trick? What nefarious agenda is going on here?" http://files.myopera.com/Tamil/Smilies/LOL.gif -
So, I just let it be for a while until today when I was purging PMs.
I decided to assume my Martial Arts stance norris ...
Throw the dice and see what I'd encounter when I clicked on the link. http://files.myopera.com/Tamil/Smilies/BigGrin2.gif -

Dark FurieFurie Friday, August 20, 2010 10:15:01 AM

Ain't she pain free compared to other templates? The secret's in the frosting, but I'll never tell. wink

Suntana Friday, August 20, 2010 3:47:23 PM

I don't know. Depends to what you are referring.
You mean the CSS in the Box above?
If so, then why yes, of course ... even a snake would be able to pull off Skinning. http://files.myopera.com/Tamil/Smilies/LOL.gif -

Anyway, I need some clarification, well, not for me but for my friend.
Okay, so when people import your and DrLaunch's themes, what do you two allow people to change? I know the people who import your themes will of course be able to insert their own Blog Title and Subtitle. But, beyond that, what all else are they allowed to change before a Red Alert is triggered and you go and give that person a Code Red and make'em disappear? scared

It's that now having learned CSS herself, my friend likes to eventually go hog wild scared with changing my original versions of themes that I hand over to her ... usually to a point beyond recognition or close to it. http://files.myopera.com/Tamil/Smilies/Scared.gif - So, I told her that while right now that CSS Importing function isn't working, I COULD get her your Sunset Storm CSS and DrLaunch's Neo CSS ... but, that she'd have to behave and follow y'all's rules. http://files.myopera.com/Tamil/Smilies/Yes.gif - I told her that when using your and DrLaunch's themes, she cannot remotely assume that she has carte blanche to change anything and everything.

So yeah, I need to know what y'all typically allow to be changed on a theme before you take a person out for a ride into the forest for a Copyright destroying attitude adjustment. yikes http://files.myopera.com/Tamil/Smilies/ROFL.gif -

Dark FurieFurie Friday, August 20, 2010 10:04:05 PM

For my themes I allow anything to be changed as the user desires if they have the skill, so long as they realise that I do update them and my updates may break their changes at some point. However, if the person is changing one of my themes and importing the code, I would ask that the original theme group be linked to somewhere in the blog, preferably on the sidebar, so people can see my own unedited work. If a theme isn't being imported but the code is being cannibalised, then the same applies but I'd also ask that a post be made about the new theme, linking to the theme group and also to my page as the original designer. It's the same courtesy I gave others.

You'd have to ask the Doc what he prefers if people edit his themes.

Suntana Friday, August 20, 2010 10:27:01 PM

Okay, I'll give her the lowdown on the rules.
While I could be wrong, I THINK on your Sunset Storm theme she probably wouldn't be going all crazy with changes. She seems to like it as is. At most, most assuredly she WOULD eventually want to change the Background image because she likes to change Headers and Backgrounds frequently anyway. Since she liked the transparent nature of it, that's why I'm guessing she probably won't be making any drastic / wholesale changes.

Anyway, yeah, let me PM her the Behavior Code http://files.myopera.com/Tamil/Smilies/BigGrin.gif - she'll have to follow to use your themes.

Dark FurieFurie Monday, October 11, 2010 7:44:56 PM

I've bypassed the importing problem by setting up a file with the code instead of a group until the issue is fixed. As such this place should look how I designed it to look and the project is off to a good start.

Suntana Friday, October 29, 2010 5:47:48 AM

Out of curiosity, I tried out the Sidebar Headings Code. As it turned out, for my typical Designs, it won't work as is out of the box, out of the gate. I guess the default Code is for standard, regulation size Sidebar Headings. With me using 240 x 40 Sidebar Headings, the canvas is to short for my Sidebar Headings.

I had to add padding. Plus, I had to use the Line Height property. Nnnnggg, I don't particularly like the Line Height property. It tends to be unstable between Browsers. Like I got the text vertically centered in the NEW MyOpera. Yet the current MyOpera won't exactly maintain the vertical alignment on the Blog Search and Calendar Sidebar Headings.

If the current MyOpera can't even interpret the Line Height property consistently, I see other Browsers having problems displaying the text properly aligned vertically.

Dark FurieFurie Friday, October 29, 2010 10:07:53 AM

If you have a heading that is large enough to make the heading stretch to a second line then it'll show more of whatever image you have set. up

Suntana Friday, October 29, 2010 2:54:12 PM

Hmmm? That's odd.
Using the default Code, my Sidebar Headings were chopped off.

Anyway, let me make sure I understand how this Open Theme Project works since Linda asked me how it worked.

Sooo, whoever wants to use the DIY flexible theme has to first add that @import url line in the CSS Box, right?
Then that additional Code from your Post has to be tacked on ... of course with all the appropriate URLs, Color Codes and Height parameter all filled in, right?

Suntana Friday, October 29, 2010 2:57:40 PM

Then again, now that I think about it, I can't remember with 100% certainty whether I conducted my Sidebar Headings experiment in the current MyOpera or the NEW MyOpera. I keep losing track of where I am regarding the current or NEW MyOpera.

I may have to try it again sometime later today to see what happens.

Adonis @ my.opera /friendspartyworldAdonisali Saturday, October 30, 2010 3:45:31 AM

So as i may see it, open doesnot mean easy.
wink i can learn a lot here, though i should need a place and opportunity to apply this. faint

Dark FurieFurie Saturday, October 30, 2010 10:43:38 AM

Open is a damn sight easier than creating a theme from scratch, but it has to be a little complex to allow for individuality. If you're after a way to learn the basics and just make a very basic theme, then I have a few tutorials on my own page. Just check the sidebar. up.


Sooo, whoever wants to use the DIY flexible theme has to first add that @import url line in the CSS Box, right?

Yep, the import code gets rid of all the inconsistencies in the regular code, takes all reference to images, background colours and text colours out and makes it a lot easier to actually create the theme you want. Once that's in place, the rest of the basic template should take care the majority of needs, but obviously you may want a different image on the menu than the wrap or a new image on the sidebar, so it can be edited to your needs and integrated with your existing code.

Suntana Saturday, October 30, 2010 2:29:52 PM

Got it. up

lucideer Sunday, October 31, 2010 3:03:58 AM

Not meaning to criticise your aesthetic taste, but as a theming project, the theme of this blog should be a showcase, and the current one is unreadable. Black text on a dark background=bad.

Other than that, I like the idea behind the project. Will see if I can't contribute at some stage in the future.

Dark FurieFurie Sunday, October 31, 2010 12:23:28 PM

It's as clear as can be for me. You really can't read it? Anyone else having these problems?

How about this?

Suntana Sunday, October 31, 2010 2:13:04 PM

Maybe it's displaying completely different on Mobile, Furie.
As for on MY end ...
It isn't unreadable, but it IS difficult.
The Black text on Grey Background is NOT ideal on MY screen.
Especially on the dark areas of the Background.

NOTE: And this is considering that my Monitor has and has always had a flaw since I got it used ...
My Monitor actually has a faint light grey sheen that actually makes anything and everything appear brighter than what it actually is. So, I can imagine that probably what is displaying is probably darker than what I'm actually seeing on my flawed Monitor. That's probably why Lucideer sees it closer to "unreadable."

What IS definitely a problem is the Cursor Color.
Most of the time I can't see it. So I lose track of where I am. Actually, just barely today it has somewhat appeared. In past days it was flat out 100% invisible.

Are you by any chance using that new CSS3 with some sort of fading out effect? Cuz I kid you not ... on the few times that I do see the Cursor, it eventually disappears.

I'm gonna conduct a test in the next comment to see what that Blue text looks like.

Suntana Sunday, October 31, 2010 2:18:59 PM

Testing ... Testing -- One Two Three This is a test of the Blue Font on the Open Theme Project theme. abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ The quick brown fox jumped over the lazy dog's back. THE QUICK BROWN FOX JUMPED OVER THE LAZY DOG'S BACK. sing Oh give me a home, where the buffalo roam And the deer and the antelopes play. Hmmm? Do deer and antelopes play? I might have the lyrics wrong. lol

Suntana Sunday, October 31, 2010 2:23:09 PM

Well, I think I have a different shade of Blue than you do, Furie. I used the plain ole "blue" shade from HTML Code. It appears a tad brighter than what you are using. Either way, it doesn't look good. scared

For sure it's gonna be tough to find a Font Color that contrasts well on this Grey Background what with it being semi-transparent and the Background with varying colors coming through.

Suntana Sunday, October 31, 2010 2:28:32 PM

Check and see what DrLaunch and Andrew are seeing on their end, Furie. Monitors do seem to vary a lot in how they display content.

I have this Header that I made for a Newsletter way back in around 2001 when my other computer, my Gateway was new. So, I would THINK that the colors, brightness & contrast should have been perfect at that time. Yet when I view that Header on THIS Monitor, it looks like Crap ... all washed out.

lucideer Sunday, October 31, 2010 4:10:05 PM

The header text and menu are ok, but only because the text is very large. I can read the text in the post, but it's quite hard on the eyes. The text in the #myo bar however is completely unreadable.

Dark FurieFurie Sunday, October 31, 2010 5:13:26 PM

Ah, you're using the old version. On the beta and the upcoming new version of the site you'll find the topbar much more readable. I did still have edits that made the existing topbar more chunky, but they gave problems between versions so I removed it in preparation for the new version.

Lucideer, I agree that the grey isn't ideal. It is just a placeholder though and will be replaced at some point. This whole place is in beta at the moment as I test new elements (problem with banners for some reason but I'm working on it) and Opera releases new things, but the main elements are ready enough that they'll work for most people. Just changed the text to white so let me know if that's a little more readable guys.

Hmmm, I hadn't noticed the cursor problem. I wonder how I managed that? I'll have a look at it later and see what part of the code I forgot to dot an I or cross a T on.

L2D2 Sunday, October 31, 2010 6:57:05 PM

Hi Furie. The white text is more readable on the gray. Gray is a difficult color to work with anyway.

Just wanted to let you know that I just started playing with your open theme CSS. So far, using the code above, the banner is chopped off at the top if an image like Chuck and I use in our headers is used. I tried different height parameters, but always with the end product being an image that is truncated for the top one fourth or one third.

I also had to change the parameter from no-repeat to repeat in order to get seamless tiles to work so I could have a header image at all. Had to do the same for the foreground wrap.

That's about as far as I got with it, except how do I make the sidebar headings? So far I have been able to get nothing to work except plain black strips that I suppose are default.

Like I said, just started playing with the design.

Oh, another thing---in the code I have, the Blog Title is not any larger than the Menu fonts. Where can I change the size of the blog title font? And the padding?

I think it will be a good thing in final version. Going to check out the link to beta code you put up there as it may be different from what I have now. Thanks for the white text here! My eyes are bad.

Suntana Sunday, October 31, 2010 9:13:10 PM

The White Text is better, especially at the Top Bar.

As for the Cursor, maybe you missed it because for all I know, maybe it does show up in Mobile.

L2D2 Sunday, October 31, 2010 9:54:05 PM

My cursor disappears in the comment box at Carol's and, I believe, at Dirk's. All having a black background.

L2D2 Sunday, October 31, 2010 9:54:06 PM

My cursor disappears in the comment box at Carol's and, I believe, at Dirk's. All having a black background.

Suntana Sunday, October 31, 2010 10:23:55 PM

And the plot thickens. Muhahahahah!
It's obviously NOT a NEW MyOpera issue since I'm here right now in regular MyOpera.

L2D2 Sunday, October 31, 2010 11:15:22 PM

The transparency definitely seems to affect the cursor because it becomes transparent also on a black background.

L2D2 Sunday, October 31, 2010 11:19:14 PM

Fury, I don't think that URL imported because I have not blog title like you have here, the banner I have looks very different and I have no top bar at all with O on it or otherwise.

How do I get the structural base CSS if the URL won't import?

lucideer Monday, November 1, 2010 12:18:27 AM

Massive improvement! Fair play.

Originally posted by Mik Furie:

Ah, you're using the old version.... gave problems between versions.


Ah yes, I had some issues between versions as well - I've similarly just disabled some things (though I disabled them in the new version, I'm coding for the old version 'til they change the domain permanently). Quick tip though, prefixing things with .section-user in the CSS targets only the newer version (as they've handily added that className to the html element).

SuntanaLab Monday, November 1, 2010 12:39:58 AM

Hmmm? Well, that's odd.
The Tamil Smilies Toolbar is being chopped off on the bottom in the NEW MyOpera.

Peppermint, can you confirm that?
First make sure you click on that "BETA" link that Furie put in one of his comments. Then let me know if you also see the Tamil Smilies Toolbar being chopped off at the bottom.

SuntanaLab Monday, November 1, 2010 12:43:50 AM

Peppermint, all these experiments you've been conducting with Furie's theme ... HAVE you been conducting them while in the BETA (NEW MyOpera) version of his theme? Maybe that would solve some of your problems?

I know that the 2 or so times that I tested the CSS, I did so in the regular version of the Open Theme Project. So, I don't know how much if any of the problems / irregularities that I encountered could be attributed to being in the regular MyOpera at the time.

L2D2 Monday, November 1, 2010 6:23:52 AM

I think it's totally been in regular my opera, Chuck. I'll test drive it in beta, but I really believe the URL didn't import Furie's base code. Something is definitely missing in present OC.

L2D2 Monday, November 1, 2010 6:26:26 AM

Chuck, I'm at Furie's place in beta right now and my Tamil bar is fine. How is yours chopped off??

Dark FurieFurie Monday, November 1, 2010 10:56:44 AM

Right, the cursor is still there in the comment box. It's just grey on a grey background. Once I get around to changing this image it'll show up again. A new problem is that the mouse pointer is slightly transparent too. Not a big problem but still a problem.

L2D2 Tuesday, November 2, 2010 3:14:13 AM

I guess the mouse pointer is what I've been referring to, as well as the cursor. Can't see pointer in these blogs I've described.

Suntana Tuesday, November 2, 2010 4:19:53 AM

Actually, I don't recall the Mouse Pointer having been a problem.

L2D2 Tuesday, November 2, 2010 6:22:59 AM

Mine disappears in a few of these black designs. Could be the operating system.

Dark FurieFurie Thursday, November 18, 2010 4:03:29 AM

So, now that the update is complete, how does she look?

SuntanaLab Sunday, November 21, 2010 4:29:37 AM

I'll have to wait until I finish fixing my Designs before I conduct another Beta Test with this template.

But, there IS something I'm noticing.
The Sidebar Headings' Height and the Vertical Text Positioning withing the Sidebar Headings is inconsistent.

Dark FurieFurie Sunday, November 21, 2010 3:06:43 PM

Hmmm, it's centred on Opera, apart from the search bar which is a little bitch. irked

SuntanaLab Sunday, November 21, 2010 4:23:33 PM

Let me see if I can clarify what I'm seeing on my end.
I haven't taken out a Ruler and a Magnifying Glass so as to assess the Millimeter / Pixel differences. But, just by the strictly visual method, the Calendar Month Sidebar Heading is taller than the other Sidebar Headings. And it's possible that the Search Bar Sidebar Heading is a micro smidgen shorter than the others, or at least it appears to be. It might be an optical illusion.

The Search Bar text is way at the bottom of its Sidebar Heading vs. where other Sidebar Headings' text is vertically.

Then the 3 instances of text:
Open Theme Project
Members (3) With the very tall parenthesis
Tags

IMO, these 3 are complicating things for you to center them vertically in the short height of their respective Sidebar Headings. Those letters that drop below the letter line and those big parenthesis are throwing some wrenches in the equation.

I think if you make ALL the Sidebar Headings the same height as that taller Calendar Month Sidebar Heading, that would make it easier for all those different instances of text to appear more uniformly vertically centered. That taller height will give you more working room.

Dark FurieFurie Sunday, November 21, 2010 9:29:14 PM

Well spott5ed. I didn't notice any of those. I'll put them on the fix list for the next iteration. Due to the way the current import system works I'm fixing several problems before I upload the file again. It's a shame as the idea behind this group was to have several modules that could be imported to build the theme users wanted to have.

Write a comment

New comments have been disabled for this post.