retlehs/roots — Issue #167: Child theme issue
Author: skipstorm
Created: 2011-11-06 01:27:02+00:00
State: open

I'm not a roots expert so I might be talking nonsense but please give me an honest opinion and if I'm right i'll post here a patch to solve or propose a solution for at least some of these issues.

- I think the editing of roots files should be discouraged and a basic child theme should be served with roots.
Some parts of roots like the css in css/style.css should go in the child theme.

- Some hooks can be easily changed via remove_filter / add_filter as for excerpt_more some not.
I guess pluggable functions are lighter than adding hooks and some should be added in critical points of roots code.

Some other theme framework get really slow due to too many hooks, this must be avoided.

- As already pointed out roots must be activated before the child, i didn't check but my guess is this issue has something to do with theme options.
I had a related problem.
What if i don't want my customer to be able to mess with theme options? Or what if my child theme has his own admin panel?

One should be able to deactivate roots options panel and set his own defaults from a child theme.
After all wich css framework to use is more of a developer choice rather than something you can change on the fly.

thanks for your help