Alexandro Colorado pisze:
well an RSS is really simple I did a python script that will rip the content, put it on a mysql database and generate the RSS using a php class.

All you need to do from then is just post your [RSS] icon on the page. It doesnt need to be integrated.

Alexandro, when starting this thread, I mentioned I already have a RSS writer implemented in AWK (no mysql needed for such a trivial purpose!) but I don't want to implement anything that will be discarded in a couple of months.

Now, the smart way of updating the website is such that it divorces data & presentation, and this is why a blog system would work fine for our purposes. I mean editing HTML manually isn't the most efficient way of keeping the pages up-to-date.

Regards,
Marcin

On Tue, 01 Apr 2008 12:22:02 -0600, Marcin Miłkowski <[EMAIL PROTECTED]> wrote:

John McCreesh pisze:
:murb: [maarten brouwers] wrote:
Euh,

The 'blogging' system I referred to is actually the news/RSS thing. It is nothing special. So there is nothing really to look for, just something to
consider (or is there actually a more advanced blog system that I don't
know of)?
 I'm not aware of one.
Probably the simplest solution is to create a 'real' OOo blog somewhere (wordpress.com, blogspot.com ...) and then either 'window' it - like http://marketing.openoffice.org/blog 'windows' http://ooomarketing.blogspot.com - or use the planet mechanism to copy it to the OOo site (like http://marketing.openoffice.org/planet, http://native-lang.openoffice.org/planet, and http://pl.openoffice.org/planeta)

+1 for blogspot.com - it can put its files on a ftp site, and this can be committed to CVS via cron script. This sounds simple enough for me.

regards
Marcin

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to