I agree about keeping focus on Kanban. If we were to narrow it even further, a suggested title modification could be: "Kanban in software development". If we have Kanban in general, we should at least be very clear about the difference between product development/ continually making something new, and manufacturing/ routine, maybe through wise use of tags.
However, it's not David Anderson's system, even if we all listen to him... See, e.g., the Personal Kanban site. Also, I think http://crisp.se/kanban has good descriptions of Kanban in software development (for inspiration when finding a good description).
Suggested (start of) description:
Proposed Q&A site for questions about Kanban, especially in software development...