about processes and engines


Floyd Marinescu ‘unlaunched’ his new Uber-Community site : InfoQ.

Alexandru Popescu (aka “The Mindstorm“) is one of his fellow ‘unlaunchers’.

Alexandru being a Magnolia contributor/committer, no surprise, the site’s running on Magnolia CMS.
Scroll down their about page to learn more about Alexandru.

I’m looking forward seeing this site grow and publish quality content… Hey, there’s even a welcome goodie : a book named “Java Transaction Design Strategies” (available as a free PDF download), 188 pages on java transactions.

Congratulations to the InfoQ team !

Written by John Mettraux

May 18, 2006 at 3:40 pm

Posted in cms, dev, magnolia, oss

4 Responses

Subscribe to comments with RSS.

  1. Hi John and thanks!

    Hope you will become a regular user of Soon, I will start to publish about the architecture behind InfoQ, because I think it is quite interesting what we have there, being a new mixture of things :-).



    :Architect of
    .w( the_mindstorm )p.

    Alex Popescu

    May 20, 2006 at 4:53 pm

  2. Hi Alex,

    I’m looking forward reading those future posts.

    Congrats again !



    May 20, 2006 at 8:52 pm

  3. Does it really run on Magnolia? Wow, that’s one fine reference site :)

    Also looking forward to see some posts on how it was done.

  4. Alex,

    I attended your excellent presentation of the InfoQ architecture at Javazone in september, and got the idea that Magnolia could be used for publishing parts of the site contents in a custom-made web application implemented in some Java based web framework.

    I figure this could be achieved by doing something like this:

    1. Create Magnolia page and paragraph templates.

    2. Edit (using the templates from step 1) and store the content in the Jackrabbit repository by using the Magnolia Authoring system.
    (Also need do publish it? To an “invisible”/not used Magnolia Public Instance?)

    3. In the web application, read the published content from the Jackrabbit repository using the JSR-170 API and render it into templates similar to the Magnolia templates from step 1 (use the templates directly as-is, or custom made “parallels”? Might be dependant on the web framework used?)
    (BTW, could Magnolia paragrah templates be used independant of Magnolia page templates?)

    Is the above a recommended (and even intended) way to use Magnolia and JSR 170?
    How well documented is the Magnolia repository content hierarchy?

    Best regards,

    Morten Haugen

    October 26, 2006 at 6:29 am

Comments are closed.

%d bloggers like this: