[theme-reviewers] Header Redirect: Any Good Reason For This?

Edward Caissie edward.caissie at gmail.com
Tue Sep 28 19:32:14 UTC 2010

I'd be fine with all the artistic flair an author can put into the file, its
the content of the public facing links etc. that would be my biggest
concern. I'd look at it more like an easter egg/artist's (read: author's)
signature item.


On Tue, Sep 28, 2010 at 3:27 PM, Ken (WraithKenny)
<ken.adcstudio at gmail.com>wrote:

> ... perhaps a public facing version of the style.css header block as a
>> starting point for the discussion?
> ( This is what I should've said instead of "using data from the repo meta"
> :-)
> I figure that since the location would be in wp-content/ that my
> no-follow/index concern is already handled, so maybe the author and theme
> uris in the style.css header block shouldn't affect google rankings and
> such...
> Perhaps minimal stylings akin to the login screen for presenting the header
> block?
> Addition info that might be appropriate there is if a gpl-compatible
> library (JS or PHP) was used, it could be mentioned and perhaps thank-yous
> to contributors/works inspired from (that may be overboard tho)
>> Best way to do this would be to simply stick an index.html into a
>> theme. Anybody looking at the theme directly would get that.
>> -Otto
> Agreed (unless someone wants to create an automated feature). But in any
> case, we'd have to figure what's allowed here (redirects aren't?) and a
> standard example/best practice, right?
> A better question may be "what isn't allowed here?"
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20100928/e54aaade/attachment.htm>

More information about the theme-reviewers mailing list