Re: [binarycloud-dev] BC and the <title> issue...

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

you can do that with default template->module associations.
you coudl have a module that deals with all of your <head> contents, or just
leave that markup in the master template.

_a

----- Original Message -----
From: "jason" <ja...@gr...>
To: <bin...@li...>
Sent: Saturday, July 07, 2001 7:36 AM
Subject: Re: [binarycloud-dev] BC and the <title> issue...

>
> I haven't look at the system in detail to get a full analysis of this
> problem, but by just reading this scenerio I can see where we may need
> to have the entire <HEAD> stanza as a template in itself.  There will be
> cases where we have multiple MASTER templates using this same HEAD
> template.  (one site that has different table/layout designs).  In
> theory this doesn't seem like a big deal to implement for such a
> worthwhile feature to have.
>
> jason
>
>
> Peter Bowyer wrote:
> > At 07:33 AM 7/7/01 -0400, you wrote:
> > >With the present platform, the source of the <title> is, of
> > >course, the template used out of the $bc_page['templates']
> > >selection.  The result of this machinery is that the
> > >reusability of the template is diminished, and you _must_
> > >have a unique template for each page if you wish the title to be
> > >different, even though such a template may be simple and
> > >is able to be generalized and used over and over for a
> > >large percentage of, or all, pages.
> >
> > What about the meta description and keywords? I like to change these
> > slightly for each page on the web site - it helps with search engine
> > ranking.  A method of specifying default keywords, and then custom ones
to
> > append/replace the default with would be a good idea.
>
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>