Why not go the roots route? Build a parent theme/theme framework that does everything you want - while maintaining WordPress as its base. This allows you to t

Why not go the roots route? Build a parent theme/theme framework that does everything you want - while maintaining WordPress as its base. This allows you to take advantage of the changes in WordPress overtime - and allows users to switch to a full website if their blog takes off and they turn it into a company/personal website instead of blog. Best of both worlds. I think forking wordpress isn't as good of an idea as building a product which changes wordpress but still leaves everything in tact if someone wants to switch without requiring complex importing/exporting.