I opened this topic at Justin's invitation to promote the constructive, open discussion of specifically those aspects of the Hybrid framework implementation that are transcendent of specific themes, or child themes - and are not tied to specific, individualized issues and solutions that are already well-represented in the other forums and topic areas.
The Hybrid Framework originated from a specific, and clear set of design objectives:
It was intended to be:
1. A lightweight framework (imagine the frame of a house).
2. A development tool to create child themes and plugins.
3. An extension of WordPress on the frontend.
With a User base of:
1. People with little or no PHP, HTML, and CSS skills.
2. People with some skills in between 1 and 3.
3. Developers that need something to build from.
As such, it sits "between" WordPress' vast capabilities and broad user-base, with an already large number of extensions implemented via Plugins and the rigors of open-source development - So the question is: What is the Hybrid Framework "difference"?
The discussion for this topic should probably center on:
1. What else should the Hybrid Framework be to meet the needs of the user base? (what?)
2. How might those extensions be best represented and implemented? (where?, how?)
3. What does the framework do now, that might benefit from "another look"?
It is expected that some of this disussion will be of a highly technical nature - because it "straddles" the full-range of implementation domains of themes, web technologies, software development, generally, and WordPress itself - With the implicit goal of making the Hybrid Framework the preferred basis for implementing an ever-expanding range of end-user capabilities.