One other thing that I wanted to clarify a bit: The *Recommended* Guidelines serve a couple of purposes: they may be Guidelines that we want to make *Required* in the future, but need to provide time and education for implementation before making them required; but they might also simply be things that we consider as best-practice implementations, and highlight as "Recommended" in order to help facilitate/drive adoption of the practice.

If it's something that we're hoping to make "Required" at some point in the future, we'll usually mention that, as well as some kind of timeline. If it's something that we'd *like* to make "Required", but don't know if doing so would be feasible, we might just make it "Recommended", and then gauge adoption and implementation issues.

But at this point in the maturity of the Guidelines, I'm more interested in helping to drive Theme development best practices. Other than Guidelines changes driven by changes to core or new features in core, the Guidelines don't generally change that much at this point. We've established a pretty solid baseline for Theme quality. We've got a great opportunity to engage the Theme developer community, and to be a leader and hub for collaboration, education, and development of best-practice consensus. That's why things like using custom nav menus for social profile links might show up as "Recommended" in the Guidelines.