andrewworsfold

Wow. Based on an initial review this looks amazing. Congratulations! This could come in handy for future projects.

That'd be awesome. Here's a (very) brief writeup of the element that this initial version of the extension provides if you're interested: https://medium.com/@tailorwp/drag-and-drop-your-way-to-an-on...

The initial version of the WooCommerce extension is now up in the GitHub repository. Shhhh!! It's still a secret and won't be in the WordPress plugin repository for a day or two ;)

Yep. I've tested Genesis 2.3.0 using a few child themes are everything works fine!

That empty repo will be the WooCommerce extension, yes. It's simple at the moment, allowing products to be displayed using an element similar to the one that displays posts (i.e., all the usual options and ability to present them in a list, grid or carousel layout). I'll try and get that up on both GitHub and the WordPress plugin repository in the next day or two.

Also - if you have any ideas with respect to that WooCommerce plugin, drop me a line. Much like the plugin itself, the direction can be guided by those who are using it..

Please do. If you have any thoughts or suggestions, please let me know.

I'd love to know what the biggest issues you faced were. Easy of use (for both users and developers) is a key goal with this plugin. The decision to have portfolio and ecommerce (i.e., WooCommerce support) as separate free extensions is for this reason; not everyone needs or wants those things cluttering up the main plugin.

I might consider releasing a paid extension or two, depending on demand. Perhaps a theme that really makes the most of Tailor's feature set (though to be honest I'd probably just end up releasing that for free too :P). It's important to note though that Tailor itself is and always will be free and features will never be removed. In fact it will only get better with time.

That's right. Given it's a WordPress plugin GPLv3 was the natural choice. I'm open to hearing arguments for and against though..

Yes, that's definitely going to be supported.

This is a WordPress plugin and is therefore dependent on WordPress as the earlier poster mentioned. You're certainly welcome to port the code to some other platform, but there would be a lot of work involved in that. I'm afraid I'm not aware of similar products that don't use WordPress.

That's definitely an advantage. I'd recommend using it to see how it stacks up (you've got nothing to lose). Tailor aims to be easier to use, particularly for users who are already familiar with WordPress. I'm not personally a fan of builders that make you first select a "column structure"; with Tailor you just drag elements relative to one another and dragging to the left or right creates (or adds) a column. Of course you can then resize then using a simple drag action.

Awesome! If it does look like something you'd like to use then I'd love to get any feedback and suggestions you have. You can email (hi@tailor.com), jump on GitHub or leave a note in our forum which can be found at http://support.gettailor.com.

I agree. Given this particular forum I thought the free and open source aspect of it would be more interesting, but you're right: it's definitely not the drawcard of Tailor. That said, the benefits of it being free are obvious and being open source people can get involved and help shape it (like WordPress!).

Tailor works with any theme. Plugins like WooCommerce that do something specific (like ecommerce) can easily be supported. In fact, I have created a simple WooCommerce extension for Tailor (also free) for people who want to manage products.

Thanks to both of you! I'll update the landing page based on your recommendations.

Content is maintained separate from the plugin, but Tailor does provide it's own set of minimal styles for elements. The main problem it solves it getting "locked in" to a plugin (i.e., being left with nothing but shortcodes when the plugin is disabled), but the element styles would no longer be applied when the plugin is disabled.

That's an interesting thought though and something I'll explore. If it can be achieved without hacking WordPress or introducing other issues then I will introduce it. One of the great things about Tailor at the moment is that it doesn't mess with WordPress and I haven't had to release a single maintenance release to support new versions of WordPress.

Thanks! I look forward to hearing your feedback!

Hi all - given the timezone (I live in AU) my responses will probably slow down. Please go ahead and post any other questions or comments you have as it's been great to hear them and I will respond ASAP.

I guess so. They both set out to achieve the same sort of goal, but obviously have slightly different approaches.

Thanks!

Element data (or models) are stored as meta data and the content generated by Tailor is saved as HTML within the post (with a few exceptions for dynamic elements that use shortcodes). The benefit to this ofcourse is that when you disable the plugin you're not left with shortcodes in the place of content. This is one way in which the plugin differs from something like Visual Composer.

Conceptually it's very similar to other plugins: drag and drop elements on the page, configure them to your liking. Differences I'm proud of are the way in which rows and columns work (drag elements to the left or right of an existing element), the primacy of content (see my other comment), the way templates are managed (saving, importing, exporting and adding to the page) and the revision history panel.

There's a lot more under the hood and a lot of time and effort has gone into it, so if you're interested I hope you'll check it out - it's free after all :D

Thanks. Much appreciated!

It should support any theme engine, if my understanding of what a theme engine is is correct. Did you have an example of one?

Great! I'm definitely keen to receive any suggestions or feedback you have (hi@gettailor.com or the community forum at support.gettailor.com) and the project's up on GitHub too if you want to get involved (https://github.com/andrew-worsfold/tailor).

It's used to build page layouts using an existing theme (any theme). Certain effects would depend on the theme used. For example, a full-width slider or hero section would require a page without a sidebar.

Thanks for pointing that out! Should've spent more time on the landing page ;) I like the idea of hosting a bunch of sample pages built using the plugin too. I'll get on that.

The plugin generates CSS based on the options end users select when configuring their elements. These rules are combined and added to the page in a separate stylesheet. When "Tailoring" a page, dynamic stylesheets are managed using JavaScript. It's also possible for developers to utilise media queries (thought that's probably a little off topic). I've got a little info about that on the Help Center: http://support.gettailor.com.

I know page builder plugins are a dime a dozen nowadays (both free and premium). The idea with this plugin is to simplify the process of creating layouts for users who want to use their favourite theme. It focusses more on usability rather than cramming as many "elements" in as possible. I'm also a big believer in WordPress' philosophy of "decisions not options" and the separation of concerns between plugins and themes; this plugin aims to try and strike the right balance between those things.

The result is (hopefully) something that does what it does and does it well out-of-the-box and can be easily extended by plugin and theme authors. I see this a key differentiator with Tailor.

To answer your question though: there are some obvious similarities between this and Elementor. A key difference is the role that content plays in Tailor (being the core element and something you can move around within the page in its own right). Elements typically contain and style content, with some (like carousels and tabs) utilising JavaScript to change the behaviour. You can pull content from a carousel, for example, into a hero section and have those style changes immediately take effect.

I hope that answers the question somewhat :)

Thanks! Glad you like it.