Slashdot Mirror

← Back to Stories (view on slashdot.org)

Small but Mighty:The Bricolage Story

Posted by timothy on from the now-there's-an-ecosystem dept.

SilentBob4 writes "Bricolage is an example of the power of an open source project to survive its proprietary origins. As you will read below, Bricolage was originally started in-house by Salon magazine, and then open sourced by About.com. I imagined how very frustrated David Wheeler, a Salon employee, would have been had he been forced to watch the code he helped develop just die on the shelf. Never underestimate the strength of the human passion to create, and to see one's creations bloom in the light of day." The full story is at Mad Penguin."

5 of 95 comments (clear)

  1. Re:Whats Bricolage? by stratjakt · · Score: 3, Interesting

    My only point was that that blurb doesn't tell me what it is.

    It's full featured, ACID compliant, templated, backwards compatible, vertically integrated, etc..

    What is it? Some sort of gameboy game?

    --
    I don't need no instructions to know how to rock!!!!
  2. Bricolage Defined. by RandoX · · Score: 1, Interesting


    ...to use something that is easy at hand for a tool it was not designed for. A brick used for a hammer, for exaple, is bricolage...

    Doesn't sound all that efficient, really...

  3. Re:For those who wonder... by kebes · · Score: 2, Interesting

    As a french-speaker, I'll add that "bricolage" is often used to mean "doing crafts" (like making decorations and stuff) even though the dictionary definition is closer to "doing odd-jobs".

  4. CMS? by Quixote · · Score: 2, Interesting
    OK, I RTFP (read the first page), and figured out that Bricolage is a CMS.

    Now, as a non-web developer, I have to ask: what does a CMS like Bricolage do? Can someone give some examples, other than a finished site? I want to know more about the backend stuff of a CMS. Call it idle curiosity.

    1. Re:CMS? by publius_ovidius · · Score: 3, Interesting

      One key difference between Bricolage and Zope is that we (Bricolage) are entirely back-end. Once we serve the content, there's no overhead of some framework slowing things down. The people can choose to use any technology they want to drive the front end (many folks use PHP). Heck, if they are having performance problem on the front end, they can switch to a different technology and still use Bricolage to manage things on the back end. Many content management systems do not allow this. This is a huge benefit of Bricolage.