Native confluence news? Huh?
Moving the old news... is the painful process of converting html to
wiki... and AFAIK there is no way to backdate the content, so will
have to put a note in the news stating which date it was really
from. Unless you want to hack the DB... which I don't recommend.
Its been a while since I looked into it though... might be some
backdate support in the newer versions of Confluence.
--jason
On Feb 19, 2007, at 4:31 PM, Hernan Cunico wrote:
Oh, I wasn't talking about the autoexport. Native Confluence News,
up to 4 mins to show up with the {blog-posts} macro.
any idea for moving the "old news"?
Cheers!
Hernan
Jason Dillon wrote:
News is one of those dynamic bits which won't get updated unless
the page which uses the macro is re-rendered. I just made a minor
change to index and it picked up the new news.
What we need to do is have a period full export of the site to
keep these more dynamic bits updated. I'm not sure if we can
tickle a specific page to re-render, except for changing its
content. And really, it would suck to have to do that, cause the
rev history would be a mess.
But, if we can figure a way to make AutoExport export one page,
then I can hack hokeypokey up to list all pages that have changed
since the last check er something.
But for now, probably doing a full export on the hour (hopefully
thats not too expensive) before the sync to live happens is
probably good enough. Can probably hack something in hokeypokey
to trigger to full export only if pages have changed...
David Blevins mentioned something about some new XMLRPC bits in
the AutoExport plugin... but I don't know more details about that.
But, in short... we have to have something tickle these pages
periodically to update. I think if we time the tickle properly it
will minimize the lag between confluence update to live site update.
--jason
On Feb 19, 2007, at 4:05 PM, Hernan Cunico wrote:
Hey Jason,
I'm trying to catch up with the News/blog-posts on GMOxSITE as
part of the web site update. I created a few tests (added News)
but these posts take forever to show up. Any suggestions?
Anyway, do you have any idea how could we port the *News* we have
on the live site?
Cheers!
Hernan
Jason Dillon wrote:
On Feb 15, 2007, at 9:17 AM, Hernan Cunico wrote:
Folks,
after lots of separated discussions on different threads it is
clear the spirit for moving the authoring of our web site over
Confluence. Let's bring to this thread all the ideas and
discussion.
Proposal:
The idea is to use Confluence as the authoring tool for
Geronimo's web site. To achieve this we will use the autoexport
plugin already installed and in use on the cwiki.apache.org.
With the autoexport plugin we can customize the generated HTML
look and feel by using templates. The current POC can be viewed
at http://cwiki.apache.org/GMOxSITE (thx Jason D.)
Some suggestions (mine ;-) )
- Avoid JIRA references/direct imports, if JIRA is down or
running slow it will affect the main web site.
Eh... maybe... though JIRA should not be down or slow. These
are also static pages, which only pull images off of the JIRA
webapp, but we could remove the icon from the rendering. I
personally think its useful to show some JIRA activity on some
page on the website. Shows that we are still moving even if the
website content isn't.
- Remove edit/print/export links from the generated site. Only
Geronimo committers will have edit access
Fine w/me.
- Update the template L&F. Why not? It is a good opportunity to
do it !!!
Ya, probably some changes to be made... I like the Cayenne site
a lot... clean, simple... nice popup menus.
- Need to define how to integrate the other subprojects web
sites (consider confluence spaces too).
Aye, we need a basic theme that works for the main site,
documentation sites and sub-project sites.
- pls chime in!!!
I volunteer to start updating the content (matching with what
we already have on the live site), unless somebody else wants
to go it!
I will also look at some alternative templates.
I really would like to see this happen... so I can lend a hand.
--jason
