Kevin, remember that $$vars are populated from data variables first
and code.snippets second. Which means if you put in your skin:

        <meta name="description" content="$$description" />

You could then create an action which create a data field description
on any page you want. Where not set, the code.snippets value would be
put in. But where a value was set that would get supplied first. There
is no hierarchical way to do--which would be the ideal solution--but
that would require a custom plugin. This is because I don't want to
have to open all the pages up the hierarchy for that information.

My solution would be to use something like ==[(meta description)]== in
the skin and then write a plugin that scans up the hierarchy for the
closest corresponding data variable, ending with code.snippets if
nothing else is found. If you need help pulling it together, I'd be
happy to do it. But the code would be fairly simple.

Cheers,
Dan

P.S. If you do write the code, please publish it. It's a task I've
thought about doing for quite a while.

On Thu, Nov 5, 2009 at 2:47 PM, Kevin <[email protected]> wrote:
> The use of Meta tags is not very useful.
>
> Right now, the system uses the same meta tags for basically every page.
>
> In real usage, this is not correct since each page should have the ability
> to define the meta tag description and perhaps keywords that describe the
> actual page that is being loaded rather than using a system wide generic.
>
> This provide much better search engine results for those engines that rely
> on the meta description to describe the page they are loading.
>
> I'm guessing that you could create a data variable in the page that is then
> used by the system to set the meta description and if needed keywords.  Not
> sure if you could do it using a function
>
> [(meta description "the description of the page")]
>
> [(meta keyswords "key, keyword, other words")]
>
> which you put at the top of each page you want to change from the default.
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "BoltWire" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/boltwire?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>

--

You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=.


Reply via email to