1. page builder- add the ability to put columns inside a column, or the ability to change element’s width to set 2 elements side by side.
right now there is no option to do that. it sometimes needed, example: in a 2/3 column, i want to put an image that will slide from the right and i want this image to be on the left side of a text block.

2. page builder- add the ability to put a color box inside a column. ( example- i want 2/3 column white, and 1/3 column green)

thanks!

Why not an optional authorbox under posts, like in the “Habitat” theme (with a enfold-type modern style) ?

Also, in the last updates, there was some microdata implementations, but the theme is still not exactly matching the google authoship rules.

Thanks for this great theme ;)

Hey!

Revert the code change Ismael suggested in his last post and insert this code at the very bottom of enfold/js/avia.js:

(function($){
	$(document).on( "click", '.portfolio-preview-title.entry-title', function(e) {
	  $(this).parents('.portfolio_preview_container').find('.avia_close').trigger( "click" );
	  e.preventDefault();
	});
})( jQuery );

Best regards,
Peter

I’m not even sure if this is a good idea because of potential downsides, but I may have a suggestion to improve the mega menu editing interface. It’s probably one of the least important things possible to worry about, but hey, might as well post it.

I actually think what you have now is really great and very functional, but it’s a little odd from a UX standpoint. You can tell it’s engineered to get around WordPress’ limitations (which is not your fault of course). Check a box to make a mega menu, and suddenly pages or custom links turn into columns. Drag them in a level deeper, and they’re pages and custom links again. Check another box, and now the description is a thing you can use to put custom content in. Not bad, just kind of weird.

Some months ago, a little-known plugin was released called Big Voodoo Mega Menu & Related Links Menu. While it falls flat in its front-end implementation, the back-end is pretty good. Here’s a look at it. Columns and what Enfold calls text blocks are their own separate elements, with their own properties, and I think it works well.

Downsides vs. the current Enfold way are:

• It’s not as easy to link to a page from a column heading (since you can’t just make a page also a column with this method)
• Pages and text blocks can be on the same level as columns, which would be layout chaos
• There’s nothing stopping you from making a column or text block a top level item, which would also be layout chaos.

But maybe there’s a clever way to solve those issues, like still doing the “page becomes a column” thing if a user is absolutely insisting, and a JavaScript check to keep columns inside the second level and text blocks inside the third level (although what do you do about adding them to the menu initially?). And, on the other hand, maybe it’s not a big deal, and users will use the tools as intended.

Anyway, I think it’s more intuitive, but a lot easier to break, so I’m not sure if it’s a useful suggestion. I’ll let you decide.