I had a Magento theme downloaded and i want to use it to my wordpress site. I searched wordpress version of the theme but no luck. Is there a way i can convert magento theme to wordpress theme?
There is no automatic way to do that, you will need to migrate your theme manually, with that I mean, you will need to code the theme in WordPress.
There's no way of magically rewriting a Magento theme into a Wordpress theme.
Like Enrique said, you will need to recode the entire thing.. well, almost, at least. This really depends on whether or not you simply want them to look the same or to actually be structured identically. The former is easier.
You can most likely salvage the majority of the skin folder, especially css and js. Then it's a matter of matching up Magento element names to corresponding Wordpress element names. An example might be .button and .btn.
As far as the structure, you may want to simply view source on the theme as it renders on the actual site, grab the source and do some heavy analysis. Figure out which portions render in the header, content and footer and try to piece them into the corresponding Wordpress files. It's a daunting task but believe it or not, I've done similar things before.
Note that Wordpress is nowhere near as complex in terms of application structure as Magento, so you'd really be dumbing down the Magento theme to accomplish this.
To convert your theme unfortunately you will have to manually rebuild it line by line for Wordpress. You said that you could not find the wordpress version of the theme but if possible the theme vendors might have HTML or PSD versions of the theme which would be a much closer starting point than Magento to Wordpress conversion.
Related
I have been trying to develop my first WordPress theme. When I added a theme "primer" and started customizing it, it appears as an image.
The primer theme appearing as shown not as it is shown in demo
Can you give a little more detail. Normally themes are generally blank and often never look like the picture. Its up to you to use the themes composer, purchase a composer if your theme does not have one, or hand codde the site only using the theme for an overall look. For instance my theme I use a mix. I installed it and got a blank theme. I then used the composer to add elements and build out the page. Some themes even offer templates which is likely what you saw when you bought the theme. Your theme should have some sort of templates for free or premium templates for purchase you can add on top of your theme to get a prebuilt layout. I would highly enocourage watching a few youtube videos over themes and customizations and using envato.com to our advantage. Wordpress is a beast most people dont realize. Its not a change words and done. There are multiple other sites for that. I just finished my first one and its a bear. It take patience creativity and a basic understanding of Wordpress to operate, and some coding experience would greatly benefit to.
I need to build a new WordPress site form scratch. So I guess I need a blank theme to do that. I need to know where I can find such a theme like that, and I need a tutorial that can help me to create my first WordPress theme from scratch.
I'm new in that world. So please I need your help.
If you're starting with no WP knowledge, I believe you're better off modifying a blank theme than you are creating one from scratch.
Here is a great tutorial I used when I started doing custom themes. The HTML is getting outdated semantically, but it will teach you all working parts of a WP theme.
As a starter theme I use HTML5 Boilerplate which is full of quality HTML5 and additional features like file caching, cross-browser readiness, mobile device readiness, and file caching, to name a few. Also it's got a minimal default styling.
You may also find the wordpress site helpful. Cheers.
starting with twentyten or twentyeleven isn't a bad option either.
Whatever theme you choice make it a child theme.
It may seem like something complex at first but it will make things easier along the way.
Theme Hybrid has a great blank theme: http://themehybrid.com/themes/skeleton
I have a starter theme on github that was originally based off html5 boilerplate that you can check out.. https://github.com/FernE97/html5-blank-slate
first approach to CMS and wordpress I'm wondering if there's any predefined html structure and classes/IDs "must-be" reference that I can refer for making my own theme willing to change in the future for another wordpress theme
thanks
Luca
There are a few other 'template' themes that could get you started - if Starkers isn't quite your thing, you might find WP Framework a good alternative. Or - just start stripping down the Twenty Eleven theme to give you a base (which is just what the Starkers theme does, using the Twenty Ten theme as a base).
There's also quite a handy first-time guide on the WordPress Codex around theme development if you'd prefer to start from scratch.
Wordpress doesn't require you to have any specific classes or IDs in your theme in terms of the HTML and CSS, the only things WP needs are things like the wp_head function inside your element on every page. Having said that themes such as Starkers were created to enable developers to have a starting point instead of starting from scratch.
Now the above applies only to whatever code you write, there are however some functions in WP that will return standard code, for instance if you don't specifically create the comment thread code, WP will generate it for you, and that is really the only code that many themes will share.
I would say that if you are intending on making a number of blogging themes for instance, having a set of standard code might be a good idea, for the article pages for example, so that you don't have to re-write code over and over. Aside from that the only code I ever reuse when making themes is the CSS to style comments if I don't hand-code the comments section, this is a good idea as it will save you a lot of time.
Wordpress provide some functions which add CSS classes depending of page type, templete, conditional tags . . .etc.
These functions are body_class() and post_class().
For more info check:
http://codex.wordpress.org/Function_Reference/post_class
http://codex.wordpress.org/Function_Reference/body_class
I got the design (PSD) from client. Which should i choose to make custom Wordpress themes.
I should use any Wordpress theme
Framework?
or Any WordpressBlank theme?
or I should find similar free theme
to my design then edit to it
I can't say for sure without knowing your PSD. It depends.
If the layout from your PSD is too specific, I would go for a blank theme.
If it's a well known 3 column pattern for example that you don't need to create any customization whatsover, I would use a Wordpress Theme Framework.
I would never try to find a free theme and edit it, mainly because:
you need to read it's licenses and usually attribute properly with a link in your project (bad option when you're doing something for a client);
usually it's more work to adapt a theme instead of creating from scratch. I would adapt a theme only if 80% of it would be already equal to my PSD requirements.
I agree with the other comment. I've used all 3 methods: framework, pre-made, and blank themes, and I've found that using a blank theme is the easiest when starting from a PSD file. I've used Chris Coyier's blank theme (http://digwp.com/2010/02/blank-wordpress-theme/), which is a bare bones theme with the basic functionality of a WordPress theme, but no CSS styling, making it easier to add your own markup. I wrote a blog post about this, comparing the differences among blank themes, frameworks, and pre-made themes (http://www.sinawiwebdesign.com/blog/topics/wordpress/use-wordpress-framework-or-blank-theme/).
When I build themes starting from a PSD file, I first write the HTML, CSS, and Javascript code to get a working prototype, and then I convert it to WordPress using a blank theme. I copy and paste most of my code directly into the blank theme with little modification, then add some code for custom menus, widget areas, support for post thumbnails, etc.
What think to be consider when you prefer coding a solution in form of child theme rather then in form of a plugin ?
Themes and plugins solve different problems: plugins are for business logic, themes for presentation. They are not interchangeable. I prefer the right tool for the right job. :)
i prefer in child theme (or in function.php), rather then in form of plugin. It's more easy to reuse. You can just move it from one theme to another.
Any generic functions should be in a plugin. That way, they are available to all themes, and if you make changes in one place, you don't have to copy and paste to several files.
The benefit of a child theme is that you can make changes to an existing theme, such as twentyten, without directly modifying the source code, which is fragile -- it can cause errors and has to be repeated every time the theme is updated.
Depends on the situation. If it's something that could readily be used by any (or many) different sites regardless of the theme, I do a plugin.
If it's something specific to This Particular Site Only, I would probably put it in the child theme's functions.php. Even if specific to the one particular site only, I might make it a plugin if it's something I might want to turn on and off later.
Other than the fact that you can turn plugins on and off, there is little if any difference between code in a plugin and code in functions.php.
If it's something most easily coded straight into the theme (e.g. a particular permutation of the_loop) then of course just do it in the theme template and put supporting code in functions.php