Displaying 1 To 5 Of 5 Comments WordPress News Sites And The Bermuda Triangle WP Realm seems to have the right idea, has a great team behind it http://wprealm.com/the-team/ » Posted By Simon On January 19, 2013 @ 7:34 AM Pet Peeve – Akismet Configuration Link Location move it to the settings menu without a doubt » Posted By Simon On March 23, 2011 @ 6:08 AM Thesis Goes Split Licensed – Hell Freezes Over Thought I’d pitch in… I remember having a discussion on someone’s blog a couple of years ago on the same topic (although centered around plugins more than themes). Matt left a comment in which he indicated his interpretation (everything that interacts with / uses WordPress code should be GPL) and it was as a result of that that I changed the way my own product was structured to ensure it would be compatible with GPL. I therefore have a “plugin” layer (licensed under GPL) acting as a bridge between my product and WordPress. I could therefore license the code for my product (which functions as a standalone app as well) as I wished, without infringing upon GPL. The situation from that point on has always seemed relatively straight-forward to me (I won’t say anything definitive, because this whole area is a minefield), for both plugins and themes – license anything that interacts with WordPress code directly as GPL; anything that doesn’t, can be whatever you want. For themes, that means images / css / custom javascript (as happened with thesis), and for plugins it means code with standalone functionality that does not interact directly with WordPress code. It does mean having to structure things in a certain way (for plugins, at least), but for any project where it’s worth a separate license, it’s probably best practice to do so anyway (eg. so you can bridge it with other software too). PS. I do understand the viewpoint of those who say “it all should be GPL regardless”, but you also need to consider that not all projects are WordPress specific. Whilst such projects should be GPL-compatible (eg. via split licensing), they should not be GPL simply because WordPress is. » Posted By Simon On July 23, 2010 @ 7:29 PM Listener Poll: How Should I Review A Theme? Just voted for the fresh install. A classic blog theme should handle all kind of content on an established site (number of categories and pages, length of teaser texts, width of images and videos in the content etc.). But a theme like the portfolio theme deGusto that puts an emphasis on design, layout and images should always be tested on a fresh install in my opinion. The XML with the content exclusively for the theme is a great idea! » Posted By Simon On June 20, 2009 @ 9:57 AM Review – Degusto By ThemeShift Thanks for your review, Jeff! And thanks for the nice comments. You are definately right. The deGusto theme is more suitable for blogs/portfolio sites that start from scratch or with less content than your test site. You should definately give deGusto a try on a fresh install :-) Like many other themes (apart from blog themes) that focus on design and layout deGusto needs a little adaptation of the content (length of the teaser text, width of images). Gracias mil y saludos de Canarias! » Posted By Simon On June 19, 2009 @ 3:57 AMComments Posted By Simon
«« Back To Stats Page