Since WordPress is licensed as GPLv2, you can license any addition (i.e. theme) with a license that’s compatible with version 2 of the GPL. Now here’s the unfortunate part … version 1 of the aGPL is not compatible with any version of the GPL. Version 3, however, is compatible with GPLv3 … but not GPLv2. … Read more
I would say: you should not use the style.css for the actual production CSS. The reason is simple: minification. You cannot minify the content of the file completely, because WordPress has to read it. In my themes, I use style.css just for the headers, and I add a comment, explaining where to find the real … Read more
Does this licensing scheme (for file groups) violates the WordPress license? No, only the PHP code needs to be GPL’d. A popular example is Thesis: http://mashable.com/2010/07/22/thesis-relents/ http://markjaquith.wordpress.com/2010/07/17/why-wordpress-themes-are-derivative-of-wordpress/ Do I have to publish the PHP code of the theme so it is available to everyone? You don’t have to publish it if your intention is to … Read more
From what I understand Starkers 3.0 fits the bill. Do you want something this naked, or less?
The difference between theme and non-theme code is organizational rather than technical. Any code that is active contributes to resulting environment, does not matter where it is loaded from. There is number of places where code gets loaded from, which are not part of WordPress core: wp-config.php configuration file active theme (and its parent in … Read more
As you’ve already discovered, links to the customizer always start with /wp-admin/customize.php. Append ?autofocus[section] =section_name to checkout your section within the customizer. Both parameters (section and section_name) are registered within your customize_register hook: $wp_customize->add_section If you can’t find the hook, check the HTML markup of the customizer for further information. Both parameters are included within … Read more
This depends on how the theme was developed from the beginning. Theoretically, if everything was coded to standards you can rename the folder and nothing bad will happen. When renaming the folder you are at risk of breaking code that asks specifically for files from the theme directory by name. WordPress offers a number of … Read more
It all depends on the scale of your customizations and how you will organize your stuff. But there is 2 main ways of doing it. functions.php and template files The way I like to do it, is register all my script/styles in functions.php so I know what I will work with but I will enqueue … Read more
Looking through some resources, I found this track ticket which discusses the same topic. It seems the following will stop it, add it to your wp-config.php: define(‘CORE_UPGRADE_SKIP_NEW_BUNDLED’, true);
SOLUTION: after_switch_theme does exactly what I intended here. It fires after the theme is switched TO your theme. One of the solutions mentioned below uses switch_theme. This does not have the desired results, since it only happens upon switching away from your theme. Here is an article that I found as reference: http://core.trac.wordpress.org/ticket/7795#comment:29 Here is … Read more