We have great news for all WordPress developers and WordPress themes lovers. At the beginning of September we launched Unyson - the Drag & Drop WordPress Framework that let developers create complex WordPress themes with ease.
At the beginning we built the framework for ThemeFuse themes only, but it became such a great product, that we decided to share with all developers for FREE. So the open-source Unyson framework includes ten excellent built-in extensions:
Drag & Drop Builder
Shortcodes
Portfolio
Mega Menu
Sidebars
Styling
Slider
Breadcrumbs
SEO
Backup
Unyson framework is free and will always be, so you may create WordPress themes using Unyson and being allowed to sell them on Envato or other marketplaces. The icing on the cake being the visual drag & drop page builder that will let you create countless pages at a drop of a dime.
Here are some links that will help you view and test the Unyson WordPress framework:
Live Demo – a demo of the first theme built on Unyson
Test Labs – test the framework on our servers for 14 days
Unyson Page – find out more about the features & built in extensions
is there documentation about how to create our own module for drag and drop interface?
Yesterday I’ve already tried it in my localhost, it’s really promising…
But, I really hope that the design of theme options layout will be just like other options frameworks (let’s say, SMOF), you know, the menu on the left (with child menu), the content of options is on the right. That’d be super duper awesome…
But, I really hope that the design of theme options layout will be just like other options frameworks (let’s say, SMOF), you know, the menu on the left (with child menu), the content of options is on the right. That’d be super duper awesome…
I admire the people who make open source. But regarding this framework I must say that most of the so called extensions should not be a part of the framework itself. They must be separated in plugins. From the list you provided I think that only the “Backup”, “Styling” and maybe “Slider” should be included, everything else must be a separated plugin.
Right now it is allowed on Themeforest, but I don’t think it’s a good choice to do it so. Think of Phase 2 where all this will be required to be moved in plugins.
Probably some will not approve my oppinion but I prefer to move all this in plugins.
Wish you good luck and thank you for being open source.
I saw this in the thread for the option frameworks, great great work!
I saw somewhere that it has One Click Demo install integration, or am I mistaken?
Hey, our old framework included One Click Install option. At the moment, we work around this option and we’ll include it in the new framework, later.
All our recent themes from ThemeFuse are created on our old framework. Starting the next release, all our themes will be developed on Unyson framework.
Can i make this framework compatible with bootstrap 3 framework ?
Thanks!
Unyson does not affect the frontend area of the theme, that’s why you can incorporate your theme with any CSS framework. For example, the default theme from our Demo was created with Unyson: http://demo.themefuse.com/unyson/. So, you can see that we didn’t incorporate something special, it’s the WordPress default theme.
But, I really hope that the design of theme options layout will be just like other options frameworks (let’s say, SMOF), you know, the menu on the left (with child menu), the content of options is on the right. That’d be super duper awesome…
When developing Unyson, we tried to keep WordPress UI design.
Can i make this framework compatible with bootstrap 3 framework ?
Thanks!
Unyson does not affect the frontend area of the theme, that’s why you can incorporate your theme with any CSS framework. For example, the default theme from our Demo was created with Unyson: http://demo.themefuse.com/unyson/. So, you can see that we didn’t incorporate something special, it’s the WordPress default theme.
I admire the people who make open source. But regarding this framework I must say that most of the so called extensions should not be a part of the framework itself. They must be separated in plugins. From the list you provided I think that only the “Backup”, “Styling” and maybe “Slider” should be included, everything else must be a separated plugin.
Right now it is allowed on Themeforest, but I don’t think it’s a good choice to do it so. Think of Phase 2 where all this will be required to be moved in plugins.
Probably some will not approve my oppinion but I prefer to move all this in plugins.
Wish you good luck and thank you for being open source.
Andrei.
Hi, we took that into consideration, but considered this to be the best way to built our framework. In future, we will develop it as a plugin. Keep your eyes on us to see the improvements in the next updates
I admire the people who make open source. But regarding this framework I must say that most of the so called extensions should not be a part of the framework itself. They must be separated in plugins. From the list you provided I think that only the “Backup”, “Styling” and maybe “Slider” should be included, everything else must be a separated plugin.
Right now it is allowed on Themeforest, but I don’t think it’s a good choice to do it so. Think of Phase 2 where all this will be required to be moved in plugins.
Probably some will not approve my oppinion but I prefer to move all this in plugins.
Wish you good luck and thank you for being open source.
Andrei.
Hi, we took that into consideration, but considered this to be the best way to built our framework. In future, we will develop it as a plugin. Keep your eyes on us to see the improvements in the next updates
Thank you so much for the effort. This will help us a hell lot!
I was thinking that there should be a standard streamlined way for all the theme authors on ThemeForest to create the backend of the their themes, that way it will be way easier to work with any theme bought from here, and it would benefit ThemeForest, the authors and the users/developers that have to work on the theme later.