I've been sifting through the Panopoly code. There are many awesome improvements, but there are also:
many features we don't need/want--only some of which have off switches.
exportables weaved in that don't little sense outside of demoing Panopoly or using it as-is. Example: the "Panopoly Categories" taxonomy vocabulary that's stitched into Panopoly Core.
Tons of code in .module files that belongs in includes (admin forms, long hook_menu implementations, etc.).
My best idea so far is to fork Panopoly into some kind of Panopoly Lite. (Or maybe call it Backpanel? :grin:)
I've been sifting through the Panopoly code. There are many awesome improvements, but there are also:
My best idea so far is to fork Panopoly into some kind of Panopoly Lite. (Or maybe call it Backpanel? :grin:)