{"action":"created","issue":{"url":"https://api.github.com/repos/drupalprojects/kalatheme/issues/187","labels_url":"https://api.github.com/repos/drupalprojects/kalatheme/issues/187/labels{/name}","comments_url":"https://api.github.com/repos/drupalprojects/kalatheme/issues/187/comments","events_url":"https://api.github.com/repos/drupalprojects/kalatheme/issues/187/events","html_url":"https://github.com/drupalprojects/kalatheme/issues/187","id":97571146,"number":187,"title":"Add panelized region between two hard coded regions using one-region approach?","user":{"login":"heatherfarrier","id":8184593,"avatar_url":"https://avatars.githubusercontent.com/u/8184593?v=3","gravatar_id":"","url":"https://api.github.com/users/heatherfarrier","html_url":"https://github.com/heatherfarrier","followers_url":"https://api.github.com/users/heatherfarrier/followers","following_url":"https://api.github.com/users/heatherfarrier/following{/other_user}","gists_url":"https://api.github.com/users/heatherfarrier/gists{/gist_id}","starred_url":"https://api.github.com/users/heatherfarrier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/heatherfarrier/subscriptions","organizations_url":"https://api.github.com/users/heatherfarrier/orgs","repos_url":"https://api.github.com/users/heatherfarrier/repos","events_url":"https://api.github.com/users/heatherfarrier/events{/privacy}","received_events_url":"https://api.github.com/users/heatherfarrier/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-27T22:35:56Z","updated_at":"2015-07-28T14:08:11Z","closed_at":null,"body":"We are using Kalatheme with Panopoly and radix layouts. The home page (and some subpages) design calls for a persistent top nav bar, a banner region, main navigation region and the content region. See attached layout for visual explanation. \r\n \r\n![layout](https://cloud.githubusercontent.com/assets/8184593/8919434/2bb5470c-3474-11e5-8da4-286b17595295.jpg)\r\n\r\nWe want the top nav and main nav regions to remain in code while the banner and content regions are controlled by the page manager. Is there a way to accomplish this using Kalatheme's one-region approach? If so, how can we move the banner region above the main nav region while still allowing site builders to manage the banner content using page manager?"},"comment":{"url":"https://api.github.com/repos/drupalprojects/kalatheme/issues/comments/125621817","html_url":"https://github.com/drupalprojects/kalatheme/issues/187#issuecomment-125621817","issue_url":"https://api.github.com/repos/drupalprojects/kalatheme/issues/187","id":125621817,"user":{"login":"labboy0276","id":5560907,"avatar_url":"https://avatars.githubusercontent.com/u/5560907?v=3","gravatar_id":"","url":"https://api.github.com/users/labboy0276","html_url":"https://github.com/labboy0276","followers_url":"https://api.github.com/users/labboy0276/followers","following_url":"https://api.github.com/users/labboy0276/following{/other_user}","gists_url":"https://api.github.com/users/labboy0276/gists{/gist_id}","starred_url":"https://api.github.com/users/labboy0276/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/labboy0276/subscriptions","organizations_url":"https://api.github.com/users/labboy0276/orgs","repos_url":"https://api.github.com/users/labboy0276/repos","events_url":"https://api.github.com/users/labboy0276/events{/privacy}","received_events_url":"https://api.github.com/users/labboy0276/received_events","type":"User","site_admin":false},"created_at":"2015-07-28T14:08:11Z","updated_at":"2015-07-28T14:08:11Z","body":"I have done something quasi similar to this with another client.  However, you can only have the Persistent top nav in code (in page.tpl).  then you need to use a custom panel pane to create the other nav.  The problem is, it is too difficult to split out the content at the page.tpl then have the layout template wrap around that.  \r\n\r\nThere are more alternatives too, like using hook_theme to render the 2nd menu.  Then having that hook pass info into the layout template level.  I could think of a few scenarios where you could use hook_theme and hook_theme_registry_alter to make some magic that could happen with this...."}}