Re: [sfWiki-devel] web formatting

[Todd L. M. <tm...@ha...>]

> Both.  On the main page we may want a short summary, and on 
> separate pages, a full global and by web listing.

	Of course.  With the include/variable idea, this becomes simpler.

	Here's what's up with templates and the speed stuff.  sfWiki,
right now, only pre-renders the raw text that the user supplied in the
edit box for that page.  That means that any PHP code executed in the
framework/templates is executed on every page view -- which is why I had
concerns about it.  The question is one of balance; how much content is
truly dynamic and how much can we pre-render -- and how much can we
pre-render but code more elegantly as dynamic element?  Off-hand, I can't
think of anything we're doing that can't be cached, but I don't
particularly want to force others into that design without thinking it
through first.  It would possible, in the interim, to do /more/
pre-rendering* but not completely obliterate the possibility for dynamic
stuff. 

	(* e.g.: still use CommonHeader & Footer, but empty, with all the
stuff done in template.ihtml.)

	I think when we change the template, we can just lock the database
and NULL out the rendertext column, though I'll have to look into what the
most efficient way to do this is.  Doing things this way would save a
'status' flag.


> [JOS] PageName : WebName

	One one hand, this isn't in any normal order w.r.t. to
speficity; on the other, it's probably the best way to order things,
especially as the WebName isn't particularly important -- since all webs
are equal to the search engine/topic linker.

> That would be cool to get a wiki logo.  You are supposed to post a 
> sourceforge logo on at least your "home page" for your website.  
> Although sourceforge ranks websites by how many page views 
> they get from their logo so it may be nice to put the sourceforge 
> logo on every page.

	Right.  Does it have to be a particular logo or will the default
one that comes with the page work?  (Do you know?)

-_Quinn