I am not a designer that's why I need to buy others template and then convert them to WordPress to sell in marketplace. I saw some awesome html templates I really love them and I didn't find these templates for WordPress. That's why I am willing to buy these html templates and convert them to WordPress theme.
Is it acceptable by themeforest and other marketplace?
Yes you can convert static HTML themes to Wordpress, but you would need some knowledge of Wordpress development to do so. It would entail replacing the content with the dynamic functions that Wordpress provides.
Buying themes from places like Themeforest is perfectly acceptable, and a great deal of small businesses and blogs do this. Just make sure the theme will do what you need it to. Also, worth checking their return policy - many premium themes and plugins have a 30-day money-back guarantee which will allow you to make sure the theme is right for you or you can get your money back, no questions asked.
At the moment our wordpress theme is only available in the 'standard' version but in the near future we plan to offer an 'studio' version. What do you guys think would be the best way to manage 2 versions / editions of a theme without having 2 individual reposetories?
My idea at the moment would be to have a branch called 'studio' which gets all the features / bugfixes from the 'master' and on top of course includes the exclusive features from the 'studio' version.
Maybe there are some best practices iam not aware of but i had no luck searching for it.
Thanks in advance!
I would recommend harnessing WordPress' Child Themes functionality. So your Studio theme would essentially be a child of the Standard theme.
When creating the CSS comment/headers in your style.css, just be sure to reference the parent theme, like so:
/*
Theme Name: My Studio Theme
Theme URI: http://www.example.com/themes/mystudiotheme
Description: Managing Multiple Versions of a Theme
Author: 2190870
Author URI: http://www.stackoverflow.com/users/2190870/user2190870
Template: mystandardtheme
*/
Resources:
How to Create a Child Theme
Theme Stylesheet
I am deciding between using a child theme vrs a copy of a parent theme.
I know the rule is to use child always. My prob is that I'm changing basically every file and css page in it significantly. (it's a beginner theme so it's not all that much) it seems easier just to copy the whole theme and hack it up.
It's an older theme (2yrs old) so I don't see it being updated to much. Is there a way to 'detach' it from updates so if one occurs it won't screw it up?
I'm not to worried about hackers etc on my simple site.
If you want to disable theme update notifications you can do it by changing the Theme Name field in the main style.css, or if you don't wanna change the name the other option is changing its version number to something really high.
/*
Theme Name: Your Theme Name
Author: Your Name
Author URI: Your URL
Description: Your theme description
Version: 1.0
*/
I am using Wordpress along with the story theme for this website. I have installed the Stella plugin for multiple language support. It works fine when translating the content in the pages, but when it comes to things like "Custom Page title" (see image), which is part of the story theme, it will not translate as I switch between English and German. Is there anyway to fix this or is the stella plug in just not compatible with my theme?
There is a plugin called "Poly-lang" which is compatible with most themes, including story.
I tried looking for a quick and dirty getting started with wordpress theme development tutorial. Now I know how to go and discover things myself, I'm looking for "top ten FAQ for programmers" when starting wordpress development. (For example, Turn on debugging and where the debugging option is located), how best to setup your dev environment.
All I can find is elaborate or too low level or too high level guides to it. Coming from a background of creating custom wordpress-like applications makes me frustrated.
So perhaps someone can list of the few things I need. I don't need to know how wordpress works, what a database or widget or page is.
Question I was specifically searching for:
1. How do I make wordpress watch the theme folder for changes from my IDE ( I can't really believe anybody would develop through the wordpress admin theme editor...No Undo history!). Changing the files doesn't seem to take affect until I re-install the theme. Debug mode needs to be true?
Any links condensed version of this: http://codex.wordpress.org/Theme_Development or similar?
WordPress use a hierarchy of files to determine what ends up being shown to the user. For starters all you need to create a WordPress theme is a style.css and index.php.
This is what you will have to put in your style.css in order to make it a valid WordPress theme:
/*
Theme Name: Your theme name
Theme URI: http://www.example.com/
Description: Describe your theme.
Author: Your name or company
Author URI: http://www.example.com/
Version: 1.0
Tags: black, blue, white, two-columns, fixed-width, custom-header, custom-background, threaded-comments, sticky-post, translation-ready, microformats, rtl-language-support, editor-style, custom-menu (optional)
License:
License URI:
General comments (optional).
*/
All you really need to include is a unique name for your theme and WordPress will recognize it and list it among your other themes. Even though that works, I would recommend including as much info as possible.
With just two files, index.php will then run for every single page view, no matter the type of content the user asks for. You can extend this by adding files like page.php to display all your pages, single.php to display single posts differently and so on.
I highly recommend getting familiar with the WordPress Codex. This is a good place to start:
http://codex.wordpress.org/Template_Hierarchy
The image below explains the hierarchy and what file ends up being served. I use it sometimes for reference, there is no need to memorize it entirely.
you need to become familiar with basic wordpress functions like the_permalink, the_title, the_content, etc. these are easy to remember and you can always refer to wordpress.org documentation if you don't want any out of box functionality and you pay more attention to design
if you intend to submit theme to wordpress.org than turn on debugging wile developing and read this before start http://codex.wordpress.org/Theme_Review
Theme development for beginners can be made easier by basing it on an existing theme such as the twentytwelve theme. I have written a blog post on it here http://johnadavies.me/2013/09/19/wordpress-child-theme-development/
John
turning on debugging it's the root-directory config-file.php look for faction call in
// Enable WP_DEBUG mode
define('WP_DEBUG', true);