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
