I have been using Omega 4, Panels and Panels Everywhere successfully. Now I have a site where I have three different page layouts so I have created three different variants of the Panels Everywhere site template. However, some of the panes (in the header region for example) are common to all three variants so I thought I could maybe use mini-panels to abstract these panes and make maintenance of the variants easier.

Is this a technique other Omega users have implemented? I see two challenges with this approach:

  1. Abstracting the mini-panel page elements from the page template file and
  2. Availability of (ctools) contexts to the mini panel and site template variants

Any feedback on the above would be appreciated.

Comments

fubhy’s picture

Status: Active » Fixed

Yes, I do that all the time. Not so often on the Page layout level but very regularly in Panelizer view modes, etc. Forwarding context is not a problem either because you can simply set required contexts for your Mini panel which you then have to provide upon attaching them somewhere. You can also always access the global contexts from within a mini panel. So there is really no problem regarding 2).

As mentioned, my primary use-case is different bundles/view modes that have similiarities in how I want to render them. But it certainly also works on the page layout level (and I do that too every now and then).

Does that answer your question?

eft’s picture

That is very helpful thank you. I will try this and see how I get on. Thank you for all your work on Omega 4. It is a pleasure to work with.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.