# Summary

Allows creating customized layouts.

Currently issuing alpha releases.

# Project URL

https://www.drupal.org/project/panels

# Where is the code?

http://cgit.drupalcode.org/panels/log/?h=8.x-3.x

# Estimated completion date

Target beta: Jan 9, 2016.

# Dependencies

# Who's doing the port?

  • David Snopek (dsnopek), freelance

# What help do they need?

See roadmap doc below.

# D8 roadmap

#2169319: [meta] Drupal 8 port of Panels
Panels eco-system roadmap

# Kanban board

Panels: http://contribkanban.com/board/panels/8.x-3.x
Panels in D8: http://contribkanban.com/sprint/d8panels

# Background and reference information

Holding meetings on IRC every Tuesday at 12 noon CDT (UCT-0500) in the #drupal-scotch channel.

Comments

webchick created an issue. See original summary.

webchick’s picture

Priority: Major » Critical

Escalating, since this blocks other contributed modules from being ported.

mglaman’s picture

Issue summary: View changes

Adding kanban boards

saltednut’s picture

There are a number of submodules within Panels. Are these all owned in this issue?

For example, panels_ipe is a Panels sub-module our team have started working on at #2600634: Implement Panels In-place editor display builder in panels_ipe module

webchick’s picture

That's a great question. Is the plan to split panels_ipe into its own separate project, like Page Manager was in D8? That would certainly make the answer much more straight-forward.

japerry’s picture

Assigned: Unassigned » japerry

I think if its staying within panels (which I hope it does, I think that makes sense?) then we should add the link here perhaps.

I'm hoping to roll in our META issue to this one, no need really for us to be tracking in two places.

webchick’s picture

I've seen your meta issue and it has tons of technical details, links to meeting minutes, etc. Please keep that over in your queue. ;)

dsnopek’s picture

One of the goals for D8 is that the Panels IPE and the normal Panels admin interface will share more code and work in a more similar fashion (rather than having too totally different code branches and interfaces for editing a Panels display). So, I also think keeping them together in one module makes the most sense. In the end, hopefully, the IPE will just be an alternate way to activate the same admin interfaces from Panels -- but, obviously, we have a lot of work to get to that point. :-)

saltednut’s picture

+1 for Panels IPE staying as part of panels and +2 sharing with the back-end for a more fluid interface.

Benia’s picture

Are you guys planning to make the Panels 8.x layouts Mobile-first-responsive? Ben,

dsnopek’s picture

@Benosika: That's a great idea! But we haven't really started looking at the layouts included in Panels yet. I've made an issue so we don't forget to address this: #2619018: Layouts included in Panels should be responsive and support RTL

That said, the Radix Layouts module provides a whole bunch of responsive layouts that work with Panels! So, even if the layouts we bundle in Panels aren't responsive (yet), you can still build responsive layouts using Panels.

webchick’s picture

Benia’s picture

When I started working with Panels in my RTL sites it was a nightmare for me to do 2 things:

1. To RTLize each native-layout.

2. To Responsify each layout (before I knew the Mobile-first paradigm). It took me much time, but I've learned much from that.

In any case, I think A Mobile-first responsification AT LEAST, is very very important, and could save tons of time for many Dev's, Site-builders, and could give spare time for people like me to RTLize the layouts...

webchick’s picture

Issue summary: View changes

Adding Panels eco-system roadmap to the list of resources, and updating the estimated completion date based on this doc to note that betas of various projects are tentatively scheduled for early Q1 2016.

webchick’s picture

Issue summary: View changes
InterceptPoint’s picture

I've installed Panels and all of the supporting modules on 2 Drupal 8 systems. One is local Windows and the second is a Pantheon Dev system. Both installations are working fine but Panels is simply non-functional on both the Windows and the Pantheon installations.

The Good News for both systems:

The Panels and the supporting modules all show as installed and enabled.
I see a Configure Panels Permissions Using the Admin Toolbar Tools.

But on the Structure Page there is no Panels Entry and so I'm unable to access the Panels system.

Is this a known issue?
Or am I just missing some important step?

ip

dsnopek’s picture

@InterceptPoint: You need to install a module that uses Panels, like Page Manager. Then you'll have a "Pages" link under "Structure" that you can use to create pages which use Panels.

InterceptPoint’s picture

OK. I installed Page Manager at the same I installed Panels so I have a Pages link in Structure. I'll give it a try in the morning.

If you could point me to the best documentation for using Panels with Page Manager I would appreciate it. And note this is a Drupal 8 Installation.

Thanks for the help. It is greatly appreciated. I did a huge Drupal Project back in 2010 but not much since. I just decided it was time to jump back in when Drupal 8 was released. But obviously I'm a little rusty.

ip

InterceptPoint’s picture

I've managed to dig into Page Manager far enough that I can see that this is the path to utilizing Panels. Lots for me to learn. I'm still looking for some up to date documentation and/or YouTube videos. It's pretty clear to me that the change in the Panels ecosystem as we moved from 7 to 8 is pretty significant.

Thanks again.

ip

dsnopek’s picture

Currently, there's no documentation for Panels and Page Manager, as they're still -alpha code and changing constantly. Any documentation we made (especially something that showed the user interface) would be out of date very quickly! That said, all the same concepts apply from D7, even if the modules are incomplete and the user interface is different. When we get the -beta stage, that'll be a good time to try and put together some more documentation.

InterceptPoint’s picture

I'm assuming that when you get to the beta-stage we will see a Panels Link under Structure that opens up a Drupal 7 type Panels Page.

If so, do you have a target date for the beta release?
If not, what is the plan?

And I certainly understand your comments about documentation. Thanks for the input.

ip

InterceptPoint’s picture

At least partially answering my own question it looks like THIS is the plan for Panels.

ip

michelle’s picture

@InterceptPoint See comment #15. :) And it looks like the advice I gave you in your other post about needing a module to use Panels was right. Good to know. My D8 Panels knowledge is minimal but I figured it would be similar to D7 in needing Page Manager or something.

dsnopek’s picture

I'm assuming that when you get to the beta-stage we will see a Panels Link under Structure that opens up a Drupal 7 type Panels Page.

Actually, we don't have any plans at this time to implement that. Please feel free to open an issue in the queue for it:

https://www.drupal.org/node/add/project-issue/panels

But since the planned -beta data is coming up quickly, that probably won't get included unless someone from the community contributes a patch. Hint, hint. ;-)

webchick’s picture

Hey, folks, can we please keep support requests/requests for missing documentation and the like to issues in the Panels queue instead? This issue should be reserved more for high-level status updates, specific places for people to help, etc. Thank you. :)

webchick’s picture

mustanggb’s picture

We've passed through two milestone dates (Feb 16th + May 1st) since the last comment in this issue, anyone feel like giving another one of those high-level status updates?

I'd love to start migrating and building new sites in D8; Panels et al is the largest stumbling block to this goal.

Benia’s picture

For anyone who missed this discussion - Making Panels Responsive and RTLized.

damienmckenna’s picture

Status: Needs review » Fixed

8.x-4.0 is now available.

Status: Fixed » Closed (fixed)

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