In reply to Anh Tran.

If you go too ambitious with your first project, it can sometimes take too long to get off the ground. Often, it is better to start with smaller projects to solve some of the bigger issues that you'll run into later.

For example, some of the things we needed to figure out were:

- Project naming.
- Namespacing.
- Build process for assets.
- Whether to force Composer usage.

Those are "big" questions. By working on a smaller project to start with, we could explore some variations and decide on answers to those questions without it getting too much in the way of releasing a 1.0. Then, those questions are already answered for future projects.

Sure, the end result of the two packages may not be all that exciting. However, they've allowed us to get something, anything, off the ground and set us up for success in the long term. I'll take small wins any day.

As for Composer, we're strongly pushing theme authors to use it for dependency management and autoloading. However, some folks need a little help getting there. This is strictly a transitional tool. Not everyone grasps Composer right off the bat. We want to gently nudge them into that world, not shove them in head first.