Closed (fixed)
Project:
Drupal Commons
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
2 Aug 2012 at 20:57 UTC
Updated:
1 Nov 2012 at 12:41 UTC
I propose that as much as possible, landing pages in Commons (eg site homepage, group homepages) be exported into their own features separately of the underlying views and other dependencies. The reason for that is to simplify customization on a per-site basis. If I want to customize a page, I can disable the Commons_Homepage feature and create a new Panels page that has the blocks and content I want, featurize it, and run my site in a default (non-overridden) state.
Comments
Comment #1
ezra-g commentedComment #2
izkreny commentedI like your proposal. Although, we should probably need to get our hands dirty to found out how hard/easy will be to customize Commons without breaking update path.
Possibly related and interest issue: #1713524: Mini Panels + the Sidebar Problem
WRT #1664956: Make Open Outreach Panopoly-based:
Comment #3
crimsondryad commentedI'm for Mini Panels. Scaling doesn't sound like a big deal, but doesn't everyone hope their community grows like wildfire? Then it's a BIG problem.
I do plan on customizing our Commons install quite a bit, so having landing pages in a separate feature would be really really nice. We're going to wall off our garden. It would be super special if there was a way for those snifty landing pages to easily handle that.
Comment #4
ezra-g commentedWe're following this approach - marking as fixed.