<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>#1 - it's fine, inside the theme is
okay</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>#2 - if it's a theme-design thing, no
problem</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>#3 - i found text widgets to be more of a proper
use for these, but hey, if it's in the design i'm not going to
argue</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>all of which again, recommendations are not 'do it
or else it won't get accepted' they're only something that we need to put
in there to have you think about possibly switching to that method in the
future</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>--- As for child theme deployment</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>The guidelines are not set and the WPTRT discussion
is continueing right now, we'll open it up on the make.wordpress.org/themes
site soon as we get a proper grasp of what it entails, however i posted a
preliminary list on this mailing list last night, it's only just some thoughts
to mull over and give your opinion on since at this moment nothing is set in
stone, child themes at this time are still not approved to be placed on the
repository</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=rahul286@gmail.com href="mailto:rahul286@gmail.com">Rahul Bansal</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, January 21, 2011 1:56
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] Questions
regarding theme review process</DIV>
<DIV><BR></DIV>Hi Philip,
<DIV><BR></DIV>
<DIV>Thanks for details. </DIV>
<DIV><BR></DIV>
<DIV>I even believe myself not everything that can be done via
plugin should be done inside theme.</DIV>
<DIV>When wordpress-seo by yoast came, we removed our SEO options and now
display "list of recommended plugins" in theme options pages.</DIV>
<DIV>We support many plugins like subscribe-to-comments, YARPP's related post,
etc.</DIV>
<DIV><BR></DIV>
<DIV>Main concern is - some tiny plugins. I will explain this bit with more
examples.</DIV>
<DIV><BR></DIV>
<DIV><B>#1 - Align RSS plugins (<A
href="http://wordpress.org/extend/plugins/align-rss-images/">http://wordpress.org/extend/plugins/align-rss-images/</A>)</B></DIV>
<DIV>Wordpress adds classes like .alignleft and .alignright for which we add
some codes in style.css </DIV>
<DIV>Now when these wordpress-generated classes goes into RSS feed content,
image alignment do not work as style.css cannot be loaded by
feed-readers.</DIV>
<DIV>Just 2-3 lines in theme can replace 'class=alignright' with
"style=float:left" in feed-output.</DIV>
<DIV><BR></DIV>
<DIV><B><SPAN style="FONT-WEIGHT: normal" class=Apple-style-span>There are few
more plugins which "fixes" something. Personally, I believe these fixes should
be added inside wordpress-core!</SPAN></B></DIV>
<DIV><B><SPAN style="FONT-WEIGHT: normal"
class=Apple-style-span><BR></SPAN></B></DIV>
<DIV><B>#2 - Sharing icons</B></DIV>
<DIV>Since facebook/twitter shares icons gets displayed on front-end, having
theme control their dimension and other aspects can improve
theme aesthetically.</DIV>
<DIV>Most plugin which latch on fliters ruin themes output. Then a user is
forced to add function call himself in theme codes to get desired placement of
these buttons.</DIV>
<DIV><BR></DIV>
<DIV><B>#3 - Advertising </B></DIV>
<DIV>An average blog sells ad via 3rd party. He only want a place to put some
HTML/JS codes given to him.</DIV>
<DIV>If theme provides textareas for common ad-slots, that will save him from
using bloated plugins which counts impressions and do plenty of other
things. </DIV>
<DIV>Such stats are already provided by ad-networks so why to waste CPU power
& database space of server. </DIV>
<DIV> </DIV>
<DIV>I observed that, plugins which adds HTML/CSS/JS on front-end generally
miss preciseness. In that case, user starts altering code and a single
biggest mistake they make is adding function provided by plugin
without surrounding it via if(function_exists('example'))
block.</DIV>
<DIV><BR></DIV>
<DIV>Using WordPress API is of highest priority here. In fact,
rather than relying in codex documentation, we trace wordpress core cods to
find functions which we can reuse always!</DIV>
<DIV><BR></DIV>
<DIV>
<DIV>On sidenote, as a theme-developer, while adding such functionality, I
will keep it disabled by default and will provide an option for user to enable
it if they like to.</DIV>
<DIV><BR></DIV>
<DIV>Only thing I expect from WPTRT is freedom for theme-developers to decide
on functionality they want to add inside theme. </DIV></DIV>
<DIV><BR></DIV>
<DIV>==</DIV>
<DIV><BR></DIV>
<DIV>Please someone clear my doubts regarding parent-child theme
deployment.</DIV>
<DIV><BR clear=all>--<BR>Rahul Bansal | Founder & CEO | rtCamp Solutions
Pvt. Ltd.<BR>Mobile: +91-9860501882 | Web: <A href="http://rtcamp.com/"
target=_blank>http://rtcamp.com/</A><BR><BR><BR><BR>
<DIV class=gmail_quote>On Fri, Jan 21, 2011 at 2:55 PM, Philip M. Hofer
(Frumph) <SPAN dir=ltr><<A
href="mailto:philip@frumph.net">philip@frumph.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV bgcolor="#ffffff">
<DIV><FONT size=2 face=Arial>While timthumb has been banned, that doesnt
mean other internal functionality will ever be banned as
such. You might come across recommendations that
said functionality should be a plugin, but it is only that a
recommendation.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>To answer your list.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>1. Fine - recommend plugin</FONT></DIV>
<DIV><FONT size=2 face=Arial>2. Fine - recommend plugin </FONT></DIV>
<DIV><FONT size=2 face=Arial>3. Fine</FONT></DIV>
<DIV><FONT size=2 face=Arial>4. Definately Ok.</FONT></DIV>
<DIV><FONT size=2 face=Arial>5. Absolutely Ok.</FONT></DIV>
<DIV><FONT size=2 face=Arial>6. Fine - recommend plugin</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>While the push for developers to strive to
utilize as much api and plugins that do the load of the work that you are
describing, there's nothing that you wrote there that would be
not-accepted; however, that being said it is in the developers
interest to utilize as much of the plugin to theme control as possible and
more importantly the WordPress API itself.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Frameworks at this time are finalizing the
guidelines for it. Chip is probably the best person to respond about
that. - as for integration as you speak of, that one client doesn't justify
the large number of possible users to the theme that might want a different
functionality from a plugin instead. It is in my opinion better
to cater to the wider audience then the single one, giving the audience
which uses the themes/derivatives/child themes a wider variety of
possibilities goes quite a long way.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>On a side note, I used to believe integrating
everything was the right choice as well.. .until something occured with an
update of WordPress which made one single function not behave as it should
which ruined the theme for everyone who upgraded.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>^ My 2cents, nothing more.</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV>
<DIV></DIV>
<DIV class=h5>
<DIV style="FONT: 10pt arial; BACKGROUND: #e4e4e4"><FONT
style="BACKGROUND-COLOR: #ffffff" size=3
face="Times New Roman"></FONT> </DIV>
<DIV><BR></DIV>
<DIV>My concern is, for our next theme, which is actually our internal
base-theme (sort of framework) and contains features like:</DIV>
<DIV>
<OL>
<LI>Social bookmarking/Sharing controls (twitter/facebook/etc buttons)
<LI>Advertising options (like Google AdSense/BuySellAds/Kontera etc)
<LI>Typography options (font-faces/font-sizes/etc)
<LI>Layout Options (2-column/3-column/etc)
<LI>Content Options (Thumbnail size/summaries/read-more settings)
<LI>Other options like feedburner integration, favicon/logo
upload</LI></OL></DIV>
<DIV>There were SEO options also which we plan to retire in favor of
wordpress-seo plugin by yoast.</DIV>
<DIV><BR></DIV>
<DIV>To give you better ideas, just think of themes at themeforest which
provides theme-options.</DIV>
<DIV>We have many clients on themeforest for which above said internal
framework has been maintained and continuously updated from a
year.</DIV>
<DIV><BR></DIV>
<DIV>Now question is - if we decide to release our framework in
open-source, which features we need to remove (if any) to maintain
compliances here?</DIV>
<DIV><BR></DIV>
<DIV>Also, can we upload themes we have developed for themeforest
here? </DIV>
<DIV>Will there be any extra regulations regarding features & options
themes at themeforest provides? </DIV>
<DIV>Just a note - themeforest publishers are very aggressive. On one
instant a client sent us list of 30+ plugins which he wanted to integrate
in a wordpress-theme! </DIV>
<DIV> </DIV>
<DIV>We have many themes in our repo, originally developed for
themeforest but never launched for various reasons (most common is client
defaulting payment). </DIV>
<DIV>We are owners of all graphics/code which we want to release on
wordpress theme repo, of course under GPL :-)</DIV>
<DIV><BR></DIV>
<DIV>==</DIV>
<DIV><BR></DIV>
<DIV>My second question is regarding parent-child theme.</DIV>
<DIV><BR></DIV>
<DIV>Here is what we want to achieve.</DIV>
<DIV>
<OL>
<LI>Our base theme (framework) is common across all our themes [Parent]
<LI>Each theme has its own set of local changes [Child]</LI></OL>
<DIV>We want to leverage power of parent-child theme to push
updates. If there is any change in base-framework - all child theme
users should get a notification about new update of parent theme.</DIV>
<DIV><BR></DIV>
<DIV>Not sure if possible here, specially as SVN access is not available
on theme-repo (like we have access to SVN on plugin-repo).</DIV></DIV>
<DIV><BR></DIV>
<DIV>Regarding release - should we release parent
and child theme separately? Is there any extra guideline on
parent-child theme release.</DIV>
<DIV><BR></DIV>
<DIV>Also while answering please consider 3-level relationship =>
parent-child-grandchild as well!</DIV>
<DIV><BR></DIV>
<DIV>==</DIV>
<DIV><BR></DIV>
<DIV>The only purpose of asking all questions in advance here is to save
our development efforts and also precious time of theme review
team.</DIV>
<DIV><BR></DIV>
<DIV>I hope to get some good
suggestions/guidance/inputs here. </DIV>
<DIV><BR></DIV>
<DIV>Thanks All,</DIV>
<DIV>-Rahul</DIV>
<DIV><BR></DIV><BR clear=all>--<BR>Rahul Bansal | Founder & CEO |
rtCamp Solutions Pvt. Ltd.<BR>Mobile: +91-9860501882 | Web: <A
href="http://rtcamp.com/"
target=_blank>http://rtcamp.com/</A><BR><BR></DIV></DIV>
<P></P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR>
<P></P></BLOCKQUOTE></DIV><BR>_______________________________________________<BR>theme-reviewers
mailing list<BR><A
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>