The technology has been there since 20 years ago.  Not until 2015 when KF explored different technologies to build a Knowledge Repository, he found this solution.  Most importantly, no coding is necessary to build an enterprise solution.  That's how the story started.

When we start, very often we do not have a concrete idea of how things go.  We need the flexibility in our hands and we make changes along the way.  BYOS enables us to do this, and we can do one step at a time, and go back to make changes.  It's actually simple but that's how miracles happened.

When content is shared, when repository is serious, if it is a long-term practice, content structure becomes the first and most important thing to consider, because you want it to be systematic.  For things to be systematic, it needs to be structured.  Structuring the knowledge content is difficult, because it is a lot of tacit knowledge.  That's why BYOS fits well.

This is a typical example of designing a knowledge base.  This video describes the reasons behind, the design philosophy and the final outcome.  It is an iteration process, which we call BayGO, meaning Build-as-you-GO, one step at a time.  A lot of changes in between before coming to this near final version.  After all, ACTION is most important, and everybody can do it.

Purpose of Knowledge Repository is to organize our knowledge, and content structure is the key.  This video provides a complete and in-depth explanation with illustrations.  Building a proper knowledge structure is an evolving process and that's the reason why it requires continually customization and enhancement.  Taxonomy is everywhere in life, and is what enabled the A.I. feature too.