2. Book-Tree

Book-Tree

In amazon, when you comes to a page, which is about a book "Polar Bear, Polar Bear What Do You Hear?" .

With rolling down this page, you can see how Amazon has designed many functions for a visitor to jump from this book to other books.

If I take this book page as a record, then each sub-section in this page is like a field for this record. For example, in the Amazon interface, it might look like this:

In a Excel table, it might be this way: 

If the whole record about this book is a tree, each way/field is like a branch of this tree.

Moreover, since a field might cross/thread a few records/trees, this field looks like a tree too.

So, Amazon has built a net woven with tree-threads. Some tree-threads are book-tree-threads; others are field-tree-threads.

For users, this net provides routes to different books, in some meaningful ways.

Amazon achieve the goal of guiding users to as many as books in one time.

Two month ago, I did the analysis for the purpose of giving www.ted.com some suggestions: How can TED build more meaningful routes from one talk to other talks?

In TED, a talk is most visited when it was highlighted in the first month of being posted, when it was on the homepage. But, after that, the visiting rate is much lower. TED can learn a lot from Amazon.

The analogy transfer is from 'A book' to 'A talk'

NOW, I am capable of applying this pattern/structure into more contexts. For example, I can apply it into 'A theory'. I want to connect a theory to other theories.

My goal is more advanced than building net-routes between theories; I want to synthesize theories, with using dynamic and visualizable tree-thread-net. >> For details, see Theory-Tree.