Hi, Reviving this old thread.
On 30 Oct 2007, at 19:34, Sean Cribbs wrote: > I have a really "dumb" (as in simple) extension that adds description > and keywords Radius tags and fields on the Page model. If you like, I > could open-source it. I've had a go at this myself, and wanted to compare notes with you. Here is the description of what my tag does: > <r:meta /> > > Creates a meta tag, whose content attribute is populated from a > page part. By default, the tag @<r:meta />@ expands to @<meta > name="description" content="Taken from page part called > description"/>@. You can override the @name@ attribute, e.g. > @name="keywords"@, and can specify any page part to be used. The > content from the specified page part is stripped of all HTML tags > before insertion, which is necessary to produce validating code. > > Usage is similar to the @<r:content />@ tag, with @inherit@ causing > the parent page part to be used if this page does not have one. By > default, this is set to true. > > Only suitable for use in @<head>@ section of a document. > > *Usage:* > <pre><code><r:meta [part="part_name"] [inherit="true|false"] > [name="description"] /></code></pre> I also wondered about making it strip the length of the content attribute to 200 characters (configurable), as this is the upper limit recommended by search engines. Here is a link to the article that got me thinking about this in the first place: http:// www.seobook.com/video-optimizing-meta-description-tags-google It makes for a pretty lame extension by itself, so I wondered whether it might be considered for the standard tags? Once I've written some tests... Any thoughts? Drew _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
