YOOtheme Pro is here! The best WordPress and Joomla theme. Learn more

The Invisible Framework

YOOtheme Pro gets native

YOOtheme Pro The Invisible Framework

In our last post we gave you an overview of what to expect from the Warp 7 successor. With our upcoming series of blog posts we want to go more into depth and explain the new main features in detail. Today, we're going to look into the new, more native concept behind our framework.

What does Native mean?

One of our main goals during development was to simplify things. To make everything easier to use, we have made the framework structure more "native". This means that the framework moves into the background, with a more typical theme structure in the foreground. A theme should feel like any other theme in Joomla and WordPress, with nothing between you and the CMS.

Why is this better than before?

It's now easier for developers to customize theme files. Thanks to the adapted structure, those who are already acquainted with Joomla or WordPress will feel right at home. There is no need to "learn" the framework for someone coming from Joomla or WordPress.

Native file structure

The modularized file structure is now closer to what developers are used to from Joomla and WordPress. This means that the Joomla version of a theme is structured a bit differently than the WordPress version, as you can see in the following example.

In the existing Warp 7, you find the entire site's layout in the theme.php file, which has been different from what the CMS usually expects.


In the new framework the layout is divided into several template files. This makes the core structure organized more clearly and mimicks the original structures from Joomla and WordPress.

In WordPress the file structure now looks like this:


For Joomla, you will now find a file structure like this:


Native system calls

The new native approach also applies to system API calls. So far, Warp has used its own method to render modules. To someone new to the framework this can already be a barrier. Even though it is easy to understand when you think about it, it is definitely unfamiliar.

<?php if ($this['widgets']->count('toolbar-l')) : ?>
    <?php echo $this['widgets']->render('toolbar'); ?>
<?php endif; ?>

Our new framework uses the same calls as Joomla and WordPress.

Here is the example for Joomla:

<?php if ($this->countModules('toolbar-left')) : ?>
    <jdoc:include type="modules" name="toolbar" style="cell" />
<?php endif ?>

A powerful new framework with a native approach

The native approach that we have chosen promises a rapid learning process to users who have experience in working with Joomla or WordPress. The powerful features that you are used to – and many more that we will be talking about – are always at your disposal, while being beautifully integrated in the CMS.

In our next post we will be entering into the topic of child themes and how they solved the dilemma that was keeping us from implementing 1-click updates.

Related Posts

Here is a short list of all related posts about YOOtheme Pro:
Page Builder
Website Builder
1-Click Updates
Native Structure

By Sascha | | Posted in Pro

Comments (34)

  • joomill


    | Profile |
    I'm not a fan of the pagebuilder idea, but this sounds great!

    Will there be also a "free to use" master theme?
    It's the theme i use in 99% of the time (as a subscribed member :) )
    • sascha


      | Profile |
      Hi, I understand your feeling about page builders. Especially because many page builders are bloated and don't work great. Our will be completely different. It is an integrated solution into our themes and will be super lightweight, generate perfect markup and work as expected. Think of Widgetkit with a little more drag n drop. It's also optional and you can still code the way you are used to.

      The first theme will be Nano like :-) which is also a great starter theme.
      • niall.sheehan


        | Profile |
        Sorry but they NEVER create 'perfect markup' and the statement show arrogance to say this product will be different. That said if it makes it easier for non-coding "editors" or "publishers" to use at the front end that would be helpful. This is the largest barrier to get buy in moving a CMS to something other than Word Press.
        • sascha


          | Profile |
          Our page builder markup is templated through PHP. It is safe to say, it will be bloat-free, look nearly hand coded. It's definitely different to the normal WYSIWYG experience you have with standard HTML editors.
  • coreyallen


    | Profile |
    Excited to finally be able to use child themes with Yootheme
  • akcreation


    | Profile |
    Well done yooguys, I think this will be a huge improvement and it shows a lot of effort to integrate seamlessly with each CMS. Great work
  • david.pook


    | Profile |
    When is this going to be released? Do you have a definite date?
  • sazqatch


    | Profile |
    One of the drawbacks to using Yootheme templates has been the lack of WYSWIG editing within widgetkit or Wordpress widgets. My clients get confused. Will this be resolved in the new platform?

  • patrick.fuchshofer.92


    | Profile |
    what means it for warp? i mean will WARP disappear as open source system and replaced with yootheme pro which is commercial or will warp still supported? i dont get that till now...ty :)
  • rick.kasparek


    | Profile |
    I can't wait to get my hands on it to see what it can do! And... BONUS, you're releasing it on my birthday! (kinda like a birthday present everyone can enjoy!)
  • pmarty


    | Profile |
    All that sound great :)

    What about pricing?
    Will you change the current plans and their respective prices?
  • rosston.meyer.95


    | Profile |
    Have you guys changed the way we apply widgets to certain pages in this update? That's always been a bit tricky, with such as small section to choose the selctions from.
  • tannreiser


    | Profile |
    Confused! Are you replacing Joomla and WP with a new CMS?
    • akcreation


      | Profile |
      no @tannreiser, they are releasing a new version of their framework (think of it as Warp 8) which will work on Joomla and Wordpress (I believe it will also work with PageKit which IS their own CMS)
    • tannreiser


      | Profile |
      Yes, thats what I like to think, but when I read the blogposts I get confused. I can't find anywhere that this is Joomla or WP based, only that if you are familiar to Joomla or WP bla bla .. and that the filestructure will be different compare to Joomla and WP. And something native what I don't understand what is.
      So the next blogpost should tell us whether this is build on Joomla&WP CMS or not.
      The concern is what happens when I am going to use Yootheme Pro with my many Joomla extensions
      • akcreation


        | Profile |
        The file structure is not different to Joomla or WP. What they are saying is that the file structure will work BETTER with Joomla and WP than it did before. Warp used to have it's own way of working (which required you to learn it on top of learning the usual Joomla or WP way of doing things). The new framework will work in the way other Joomla or WP extensions / templates work, that's what they mean by 'Native'. SO you won't have to 'learn' warp as well as learn Joomla and WP.
        As I mentioned above it WILL work WITH Joomla, Wordpress and also PageKit.
        From what I have read and what I can see it will work fine with your other Joomla extensions. It is NOT a CMS, it is a template framework which will also have a pagebuilder functionality built in. I think that is where you are getting confused.
        From what I have read you have absolutely nothing to be worried about and should be excited as you will have a lot more flexibility than before, plus the pagebuilder (although I don't personally wish to use this) will give non-coders the ability to build fully functional pages without any coding knowledge.
        I hope that helps clear things up a bit :)
  • rick.stoffiere


    | Profile |
    I cannot wait!!!
  • .86


    | Profile |
    Video Tuto should be a good idea beacause the Yoo support is not ok!
    At the begining of Yootheme you had real nice video tuto, it miss!
    A lot of customer (UX !, see JED for exemple) found that the documentaion and support is not great at all. So please take time for great and full documentation and video tuto step by step for this new framework version !
    • sascha


      | Profile |
      Hi, yes, YOOtheme Pro themes will be very easy to work with. Later, once YOOtheme Pro is released we will start working on video tutorials.
  • hubert.cole


    | Profile |
    This sounds like Christmas in October to me and I can't wait to get my hands on it. Will the page builder use elements the same way ZOO does. Will it support 3rd party elements (ie Zoolanders) and extensions like Zoocart?
  • huw.roberts


    | Profile |
    Hi 2 Q's
    1. Will existing sites running W7 templates be able to be upgraded easily to the new framework? If yes how?
    2.Will UIKIT still work for layout
    • sascha


      | Profile |
      Sorry, Warp 7 themes can't be updated to YOOtheme Pro.

      YOOtheme Pro themes will be based on UIKit 3.
  • triangle


    | Profile |
    As someone who completely began and started with Joomla and YooTheme Warp templates, it is all I know. Will I now have to relearn, the "normal" Joomla/template way? Will it be an easy transition? I hope documentation/video tutorials are being prepared (and maybe some additions to your support team).
  • stephan.herby


    | Profile |
    Hi, I have already let my comment about how Yootheme Pro seems amazing. I know it is not really the place here for this one, but is there any raodmap for Zoo to get that kind of improvment ? And of course the possibility to upgrade/import from older version ?
    • akcreation


      | Profile |
      +1 - unfortunately we never seem to hear anything when it comes to zoo :(
  • markprintergto


    | Profile |
    Have not written a joomla article for years always use zoo which is brilliant again lack of documentation and video tutorials not the code held back this brilliant component . hence the reason for you running back to the native cms style of approach. Having used joomla and zoo respectively Zoo is by far been superior for content creation than the native approach.

Leave a comment

Please login to leave a comment.