The trac wiki pages have a <div id="wikipage"> for the page content. We could easily extract the contents of this div and use it as content part of a TT page.
Plan B: Request the page as text ( http://padre.perlide.org/trac/wiki/WikiStart?format=txt ) and use one of the Wiki2HTML modules from CPAN to create the TT content part out of it. We might need to modify our Padre homepage CSS to support the <h2> and other tags used by the trac or CPAN wiki formatter but that's a one-time-action. Sebastian On 24.07.2012 10:21, Gabor Szabo wrote: > I think that would make it harder or even impossible to have the > same look-and-feel on all the padre web pages - these pages will just look > like > trac pages - and it won't help us move away from Trac. > > Gabor > > On Tue, Jul 24, 2012 at 10:33 AM, Sebastian Willing <s...@cpan.org> wrote: >> Hi, >> >> no need to make it "black or white". Why not keep the page in the Wiki >> and "download" it to a website page (on save? regulary?). >> >> A script could issue a HTTP request to trac, fetch the page, strip off >> the trac layout and output it using the website layout. We'ld get all >> trac links for free and could even add a "edit this page" link which >> forwards to the wiki edit page (or registration). >> >> The script may run as a cronjob or proxy script (fetch page, store the >> result and don't try another fetch for 1, 12 or 24 hours). >> >> Sebastian >> >> On 24.07.2012 08:39, Gabor Szabo wrote: >>> Hi, >>> >>> I wonder what do you think about moving some of the wiki pages from the >>> Trac wiki to the real Padre site? >>> >>> That way we can allow search engines to index those pages without hitting >>> out trac. In the longer run it will make it easier for us to move away from >>> Trac >>> to whatever bug tracking we might want to use. >>> >>> The "cost" is that only people with commit bit will be able to update the >>> wiki, >>> but I don't think there were many people who wanted to update the wiki. >>> Also we could always give out commit bit to the web site separately >>> from commit bits to the code. >>> >>> Then there is the cost of writing a script that would take the template >>> and apply the information from the trac database: >>> - Listing related tickets >>> - linking r123 to the revision 123 of SVN >>> - linking #123 to ticket number 123 of trac and striking out the >>> number if the ticket is closed >>> >>> >>> I thought we could start with the Feature pages under >>> http://padre.perlide.org/trac/wiki/Features >>> as they are probably the most interesting pages >>> for the general public. >>> >>> >>> What do you think? >>> Gabor > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
