There are three large changes made to the Aurora Base Theme itself. The two most prominent ones are the removal of the two sidebar regions from the standard
page.tpl.php
because, let’s be honest, sidebars are a lie, and the removal of the standard system information frompage.tpl.php
(site name, logo, tabs, messages, etc…). Instead we encourage you to create your layouts through CSS and a grid system for when you need it and to use Blockify (or a similar module) to get those blocks you’d like back.
(Source: http://snugug.com/musings/aurora-30-magic-birds-and-boars)
I can accomodate that "sidebars are a lie" and calling regions this name is not too semantic. However from time to time we need more regions and not just in the main part of the site (which can be handled by Panels). What are your suggestion to these situations? Write our own version of page.tpl.php
? Or?
Switching to Blockify from hardcoded standard system information is a more flexibe solution, it's ok. But blocks are stored in the db so I can't manage them with Git. To take them back to code I need Features and Features Extra, or Blockexport or own install profile or coding block calls in page.tpl.php
… :p You do not suggest either in Auorora docs. So what is the best practice (or Your practice) to resolve this problem?
I'm sure you use Site name, Page title, tabs and Git too, and (sometimes) more regions. ;) How do you do it?
Comments
Comment #1
Snugug CreditAttribution: Snugug commentedFeatures, custom (not flexible) Panels, standard Drupal template suggestions.
Comment #1.0
Snugug CreditAttribution: Snugug commentedUpdated issue summary.
Comment #2
iamcarrico CreditAttribution: iamcarrico commentedClosing as thamas gets it. :-)
Comment #3
thamasSnugug was not too verbose… But it's OK, to close this. :)
Comment #4
iamcarrico CreditAttribution: iamcarrico commented... which is odd... because Snugug is usually VERY verbose.
But in full: Keep things in panels, which supports features / git export. Don't use flexible panels layouts--- they are bad. And put things into templates where needed.
Comment #5
thamasThank you!