What method would that be?<br><br><div class="gmail_quote">On Fri, Oct 28, 2011 at 11:16 AM, Doug Stewart <span dir="ltr"><<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Since they're low-volume requests, oughtn't a method like Sara's be a<br>
decent stopgap measure?<br>
<div><div></div><div class="h5"><br>
<br>
On Fri, Oct 28, 2011 at 12:12 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> Doug,<br>
> We certainly want "niche" Themes in the repository; however, right now it's<br>
> an infrastructure problem. It's on the long-term list of things to figure<br>
> out how to handle; the problem is the automated uploader. It has no way of<br>
> differentiating between a normal Theme (with all required functionality) and<br>
> a "niche" Theme (with either reduced or extra, non-conventional<br>
> functionality).<br>
> With the understanding that the Theme Review Team has no direct control over<br>
> any of the infrastructure (the Theme uploader script, the<br>
> appearance/functionality of WPORG/Extend, SVN, Trac), we certainly welcome<br>
> any suggestions and ideas for how we might accommodate "niche" Themes.<br>
> Chip<br>
><br>
> On Fri, Oct 28, 2011 at 11:00 AM, Doug Stewart <<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>> wrote:<br>
>><br>
>> Cais:<br>
>> I think it unreasonable to look for full repo compliance when<br>
>> considering these sorts of single-purpose theme. I think the community<br>
>> suffers by not having access to these sorts of efforts and so some<br>
>> consideration ought to be extended.<br>
>><br>
>> On Fri, Oct 28, 2011 at 11:36 AM, Edward Caissie<br>
>> <<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:<br>
>> > Sara -<br>
>> ><br>
>> > Thank you for your interest in having your theme hosted at the WordPress<br>
>> > Extend repository.<br>
>> > Although, for the most part, previously "live" themes may not be a good<br>
>> > benchmarks a quick review of the "Launch" themes you are referencing<br>
>> > would<br>
>> > indicate both need to have modifications made before a newer version<br>
>> > would<br>
>> > be approved.<br>
>> ><br>
>> > As to the issues that you are seeing with the upload script stopping you<br>
>> > from submitting your theme, there is no real manual process for working<br>
>> > around it. I would suggest implementing, perhaps with additional options<br>
>> > to<br>
>> > display, all of the functionality your theme's submission report is<br>
>> > stating<br>
>> > as "REQUIRED". Once your theme is in Trac we can look further into your<br>
>> > use-case scenarios.<br>
>> ><br>
>> > Please keep in mind, the Themes found in the repository are meant to be<br>
>> > potentially used by the community in general, not necessarily by a small<br>
>> > niche group. That being said I would still very much like to see a<br>
>> > "Launch"<br>
>> > theme that meets all of the current guidelines in the repository.<br>
>> ><br>
>> ><br>
>> > Cais.<br>
>> ><br>
>> ><br>
>> > On Fri, Oct 28, 2011 at 11:11 AM, Sara Chai Butler<br>
>> > <<a href="mailto:sara@launcheffectapp.com">sara@launcheffectapp.com</a>> wrote:<br>
>> >><br>
>> >> Hi everyone,<br>
>> >> I hope this email finds you well! I was directed here by the moderater<br>
>> >> for the Themes and Templates forum, esmi.<br>
>> >> I was wondering how to go about submitting a one-page theme to the<br>
>> >> WordPress theme repository. The theme is called Launch Effect and it is<br>
>> >> basically a placeholder page with email sign-up, unique URL generator,<br>
>> >> and<br>
>> >> built-in statistics and incentive tracking. It has almost 4,000<br>
>> >> downloads<br>
>> >> and a dedicated technical support. The demand for this type of theme,<br>
>> >> and<br>
>> >> the feedback for ours specifically, has been really good and you can<br>
>> >> see<br>
>> >> examples of it in use on our homepage: <a href="http://www.launcheffectapp.com" target="_blank">http://www.launcheffectapp.com</a>.<br>
>> >> It includes a robust theme options panel where every aspect of the<br>
>> >> design<br>
>> >> can be customized and a stats panel where users are able to track<br>
>> >> signups<br>
>> >> and conversions (people who shared the site) and export their data.<br>
>> >> TL;DR<br>
>> >> Our one-page theme (<a href="http://www.launcheffectapp.com" target="_blank">http://www.launcheffectapp.com</a>) fails the theme<br>
>> >> upload<br>
>> >> because it's not a blog and has no need for comments or tags, etc... I<br>
>> >> was<br>
>> >> wondering if its possible for a theme with a very specific<br>
>> >> functionality<br>
>> >> like this to be submitted. I can't figure out how the other two launch<br>
>> >> type<br>
>> >> themes were able to upload (these two:<br>
>> >> <a href="http://wordpress.org/extend/themes/search.php?q=launch" target="_blank">http://wordpress.org/extend/themes/search.php?q=launch</a> ) because<br>
>> >> neither of<br>
>> >> theme have any kind of blog infrastructure in place.<br>
>> >> We'd love to be included in the official theme repository of WordPress<br>
>> >> and<br>
>> >> we thank you in advance for your guidance on this.<br>
>> >> Sara<br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> Sara Chai Butler<br>
>> >> Web Developer<br>
>> >><br>
>> >> Barrel<br>
>> >> 197 Grand Street, Suite 6S<br>
>> >> New York, NY 10013<br>
>> >> <a href="tel:%28212%29%20239-2072%20x7013" value="+12122392072">(212) 239-2072 x7013</a><br>
>> >> <a href="http://www.barrelny.com" target="_blank">www.barrelny.com</a><br>
>> >><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>
>> ><br>
>> ><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>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> -Doug<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>
><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>
><br>
<br>
<br>
<br>
--<br>
-Doug<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>
</div></div></blockquote></div><br>