Tripoli Beta in Development
36 comments so far | Add yours
Tripoli, a project about resetting and rebuilding HTML standards, quickly became very popular and buzzed when it was released in early August 2007. Since then it’s been a work in progress with some great help from others. After making some hard-core tests in the real world, it’s almost about time to release the Beta version.
The following new features will be held in the beta version of Tripoli, among others:
- A disabled section, gently disabling deprecated HTML markup
- Improved CSS code in general, meaning better IE support, less quirks and less specific.
- Smaller file size and compact code - now only 5.5k
- All screen CSS is now in one
tripoli.cssfile for easier implementation - Useful notes in the IE CSS file about png images, transparency and such
Tripoli is different from other frameworks, because it doesn’t tell you how to code your web sites. Just plug it in, add a simple content class where you want your HTML content and you’re all set. The specificity is kept low so you can easily extend it with your own classes and layouts.
You can follow the beta development via the log file. You can also have a look into the development files tripoli.css, tripoli_ie.css and tripoli_print.css. There’s also a sample page and the W3C document selectors with Tripoli injected into it. Do not hesitate to contact me or make a comment in the blog if you have suggestions or comments about Tripoli.
As a side note, there is also a layout plug in progress, for one-line, cross-browser layout templates based on body classes. But that is not a part of the Tripoli core, just an interesting extension. The easiest way to stay informed until the official beta is released is to subscribe to our RSS feed. Stay tuned.
36 Responses so far. Add yours.
-
At 8:16 pm on October 24th, 2007 , Off wrote:
Best simple framework ever. Thank you for putting file reset.css insde tripoli.css. That’s better. Is ‘*’ the best choice over there? I heard that it takes so much for browser to render all ‘*’ elements. I think there will be better to mention all those elements and separate them.
* {
font-size:1em;
margin:0pt;
outline-color:invert;
outline-style:none;
outline-width:medium;
padding:0pt;
text-decoration:none;
}
-
At 8:22 pm on October 24th, 2007 , Dominik Porada wrote:
Really smart project. I do like it.

-
At 9:35 am on October 28th, 2007 , Dan wrote:
What about including tripoli_print.css in the tripoli.css file, and wrap the print-specific code in @media print { … print specific code … } ?
This allows you to include all the rules in two files.
Also, on the Yahoo developer network blog there was an article about using stylesheets in a way that maximizes the download and render speed of a web page. In the comments one of the Yahoo engineers stated that when using @import to pull in CSS inside your style tags, IE will delay downloading the stylesheets and not progressively render the page with the styles. Search for “FOUC” to find more information about this.
Given this I’m wondering if perhaps the example HTML should be updated to use link tags rather than style tags using the @import rule.
-
At 11:39 am on October 28th, 2007 , David Hellsing (author) wrote:
@Dan: the beta actually uses the link tag instead of @import. The IE effect of @import you mention is real, I’ve seen it myself in my own tests.
The print-specific code was actually something I have been testin out but I never found a solid cross-browser way to do that, so I resorted to the link tag as I know it works everywhere. I might have a look at it again. Thank you for your comments.
-
At 6:33 pm on November 27th, 2007 , geoff wrote:
With Regards FOUC this only happens when there is no javascript calls in the head afaik, so if you not using js sim ply add a null js call ala this prevents the “flashing of unstyled content”
Also, by going over to link you now potentially making the really old browsers which some users are still using, fluff up more so, than when they did before, at least with @import these browser ignore any user styles.
G
-
At 5:54 am on November 30th, 2007 , wooden trays wrote:
Thanks for your articles; your voice cheers my day and excites my desire to explore the world of foods, techniques and cooking.
-
At 2:59 am on December 10th, 2007 , Kelly Miyashiro wrote:
Using the “*” selector to reset all those properties is not a good idea. While in most cases it is fine, it also tends to reset some elements from the browser defaults that are tedious to fix and cause problems when left unfixed. I’d suggest using Eric Meyer’s CSS reset at http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/
-
At 9:05 am on December 25th, 2007 , Dan wrote:
It would be nice if Tripoli’s default font would result in text that lines up on a baseline grid.
-
At 12:11 am on December 29th, 2007 , Johann wrote:
I like it and will be using it as the base for my next layout. I have some points you might want to consider though.
* I wouldn’t style anchor colors at all. I guess everyone has its own colors.
* I removed the DISABLE section since I write valid XHTML and don’t use these elements anyway.
* What’s the point of resetting h1, h2, …, strong and then boldfacing them again?
* A version for XHTML Basic with only the allowed elements would be nice (and smaller).-
At 3:30 pm on January 21st, 2008 , Simon wrote:
Nice work there, I’m particularly fond of this style, and have been using it for years.
Frameworks beat copy and pasting files
Nice Work!
-
At 1:20 pm on January 22nd, 2008 , xeito wrote:
Amazing work!
I’m developing a CSS template for my Company and I’m seriously considering to include your solutions.
I have seen other solutions like “Blueprint” but I agree with you that it restricts so much the design process.
Congratulations.
-
At 6:01 pm on January 22nd, 2008 , Jörn Zaefferer wrote:
On the beta sample page, the select looks a bit weird with Firefox 2. There’s too much padding on the right between the down-arrow and the border.
Otherwise it all looks great.
-
At 6:54 am on January 24th, 2008 , steiny wrote:
Nice! Can’t wait to see the final beta release.
-
At 5:23 pm on February 5th, 2008 , Kris Gosser wrote:
David,
This is a great framework. I’ve massaged it into my site, and it’s done wonders. Thank you very much.
I have some input regarding your use of the @import over in the header, though. I recently purchased the book High Performance Web Sites (http://stevesouders.com/hpws/) and have been learning a lot about front-end optimization. In chapter 5, he says that using in the header rather @import(style.css) will speed up a site.
I’m hesitant to use it because you have decided to use @import, and I trust your testing scenario better than his optimization scenario. For more info: http://stevesouders.com/hpws/css-top-import.php
What’s your take on it?
-
At 5:24 pm on February 5th, 2008 , Kris Gosser wrote:
Note: In the previous comment I said “left cheviot” link “/right cheviot” a lot, and the formatting seems to have taken it out. If you are reading a sentence and it seems like a word is missing, that’s what it is ;).
-
At 11:50 pm on February 21st, 2008 , Andreas Rübner Johnsen wrote:
Thanks for a great framework!
In Tripoli you are using
html {font-size:62.5%}to scale 1em to 10px. This works well for small dimensions set in ems. But IE6 ignores the decimal number so larger dimensions will have a noticeable rounding error. E.g 70em is not 700px in IE6.I think it would be better to use
html { font-size: 125%; } body { font-size: 50%; }-
At 1:30 am on February 23rd, 2008 , Jason M. Putorti wrote:
Hey David,
I figured I’d let you know that Tripoli is powering the http://mint.com corporate site, and a stripped down version is inside the app itself as well. Great work.
Jason M. Putorti
Lead Designer, mint.com-
At 5:37 pm on February 26th, 2008 , Fransızca tercüme wrote:
Your comment contains very useful information about all thank you fransızca tercüman
-
At 9:42 am on March 20th, 2008 , William wrote:
In IE6 the radio button can’t be selected. I don’t know if this is a known issue or not.
-
At 5:24 pm on April 10th, 2008 , Maniquí wrote:
I will be using Tripoli some time soon. Although I haven’t even tested it yet, I have been taking a look at its demos and, obviously, reading the CSS and the philosophy behind Tripoli and I like it. I think you have created something good here.
Of course, I need to test it yet to see if it is easy to work with Tripoli in the real world.One suggestion: it could be useful that rules from generic.css which are then overridden in ie.css, could have a comment so CSS developers know that an specific rule is overridden somewhere (ie.css) else.
Someone a little asleep could spent some minutes (or even hours) to find out why some CSS style isn’t being applied on IE.
I suggest something like:/* extra rules for IE in ie.css */-
At 5:53 pm on April 25th, 2008 , Maniquí wrote:
For those having some little issues here and there :
I’ve found that the generic.css that is currently in the downloadable zip files differs from the one on your samples (the good one).
For example, the one on the zip files have some issues with blockquotes and proper quoting elements inside blockquote. Also, some other minor issues (like wrong margins) inside blockquotes too.
The one on the samples (on Tripoli site, not on the full zip) fix those issues and other ones already reported (like the problem on IE7 regarding line-breaks on textareas).
-
At 6:32 am on May 1st, 2008 , Messy wrote:
Last post from the author date of late October, is the project still maintained?
I’d love to see it reach a stable release one day as it’s a pretty impressive piece of work already.
All the best,
/M-
At 7:37 pm on May 3rd, 2008 , Mark Lawrence wrote:
Since things have gone a little quiet here I’ve modified the beta version with some adjustments which others may find useful.
The changes are mostly cosmetic. I ran tripoli.css and tripoli_print.css through the csstidy program with a template setting of “low”. This made the source much more readable and removed a few duplicate items. I did some other cleanups by hand (:last-child is not CSS2 for example) to get the file to validate.
Then I re-ran csstidy with a template setting of “highest” (and a quick Perl fix for quotes) to reduce the size down to the 4126 bytes. This is automatic with the Makefile in the zip or tgz files.
http://rekudos.net/t2/t2src.css (8130 bytes)
http://rekudos.net/t2/t2.css (4216 bytes)
http://rekudos.net/t2/MakefileAll packaged up together:
http://rekudos.net/t2/t2.zip
http://rekudos.net/t2/t2.tgzCheers,
Mark.-
At 6:56 am on May 6th, 2008 , David (author) wrote:
@All: Thanks alot for your comments and suggestions. Tripoli is definetely not an abandoned project; it’s still in constant development. I’m just not so good at documenting it…
The tripoli project will move to DevKick pretty soon and an official beta will be released then. I will also open up a forum for tripoli discussions.
- david
-
At 6:59 pm on May 7th, 2008 , Dennis Kempin wrote:
Hi David,
I really like your Project! But I have a few suggestions:
1. Why do you try to normalize 1em to 10px? I don’t see the point in trying this. The default font size can be selected in every Browser and that is the default font size a website should use in my opinion.
2. Why do you reset all Elements and then style them again?Keep up the good work!
Regards
Dennis-
At 7:26 am on May 14th, 2008 , :-: S€zæR -> wrote:
css web template page (example) — http://www.css-lessons.ucoz.com/css-template-page.htm
-
At 6:20 am on November 18th, 2008 , 婚禮攝影 wrote:
oh it sounds so great,can wait to c it~
-
At 7:39 pm on March 19th, 2009 , eric wrote:
@Dennis Kempin:
I can’t speak for the developer, but as a developer who works with designers and creative directors, I can tell you that they are not willing to accept ‘use the client’s default font size’ as an answer. People in situations like mine require the ability to specify a stable type presentation across user agents. So David’s work on this is greatly appreciated in some quarters.
As for resetting styling, I believe it’s a question of zeroing out unexpected inheritances.
8 Trackbacks & Pings:
-
Trackback at 5:57 pm on October 25th, 2007 by News: Tripoli Beta In Development | Matt Snider JavaScript Resource: […] Tripoli Beta In Development […]
-
Trackback at 6:49 am on November 14th, 2007 by Derek Bender - the blog » Blog Archive » Using Tripoli - A CSS Framework: […] To use and find out more about Tripoli and the upcoming Tripoli Beta release, check out the Tripoli website. Filed in Innovation, […]
-
Trackback at 5:19 am on November 20th, 2007 by Customized Design Solutions: Customized Design Solutions…
I couldn’t understand some parts of this article, but it sounds interesting…
-
Trackback at 10:58 pm on April 23rd, 2008 by Singapore Increase Web Traffic: Singapore Increase Web Traffic…
How to get people to your website? Well, there are lots of ways, some take time others take money….
-
Trackback at 8:22 pm on May 8th, 2008 by Tripoli Beta : DevKick Blog: […] Read more and try it out in the Tripoli project page. If you are new to Tripoli, you might want to check out two earlier blog posts as the project was initiated: Introducing Tripoli and Tripoli Beta in Development […]
-
Trackback at 4:20 pm on January 1st, 2009 by Tripoli Beta | Castup: […] Read more and try it out in the Tripoli project page. If you are new to Tripoli, you might want to check out two earlier blog posts as the project was initiated: Introducing Tripoli and Tripoli Beta in Development […]
-
Trackback at 10:09 am on June 20th, 2009 by Swiatłem Malowane - Fotografia ślubna - wyjątkowe Zdjęcia Ślubne. .: Śląsk, Sosnowiec, Katowice, Dąbrowa Górnicza, Będzin, Czeladź :.: Swiatłem Malowane - Fotografia ślubna - wyjątkowe Zdjęcia Ślubne. .: Śląsk, Sosnowiec, Katowice, Dąbrowa Górnicza, Będzin, Czeladź :….
I like Yours post. If You have time, come and visit our’s site….
-
Trackback at 12:26 am on June 24th, 2009 by Using Tripoli - A CSS Framework: […] Since released in August 2007, Tripoli has underwent some changes and is about to be released in Beta version. To use and find out more about Tripoli and the upcoming Tripoli Beta release, check out the Tripoli website. […]