add connect

Author: barnjamin

DESIGN.md

@@ -10,7 +10,7 @@ To address this goal, the SDK is structured into layers
 ```
 core/ -- Low level packages 
     base/ -- Constants and utilities
-    definitions/ -- Definitions of interfaces required for Platforms, Protocol interfaces and Payload layout structures
+    definitions/ -- Definitions of interfaces for Platforms/Protocols and Payload Layouts
     icons/ -- Logos for chains
 
 connect/ -- Makes use of the interfaces in `definitions` to expose protocols in a platform independent way. 
@@ -26,7 +26,7 @@ platforms/ -- Contains `Platform` and `Protocol` implementations
     solana/ -- Contains Solana `Platform` and `Protocol` implementations
     etc...
 
-sdk/ -- Metapackage that depeneds on the rest of the packages, meant to be a simpler way to install/use. Exports packages in a way that allows for tree shaking unused packages and splitting chunks. 
+sdk/ -- Metapackage that depeneds on the rest of the packages, meant to be a simpler way to install/use.
 
 examples/ -- Examples, also used for README string replace
 ```
@@ -48,6 +48,14 @@ A Protocol (fka `Module`) is a specific application, it provides a set of method
 
 To allow platform agnostic access to Protocols, each Platform that provides the protocol should have its own implementation. 
 
+# Connect package
+
+The `connect` package provides access to all the `Platform` and `Protocol` implementations through their interfaces. 
+
+The `Wormhole` class represents a context to register specific Platforms and set some initial configuration overrides. It provides utility methods to do things like create a `ChainContext` or parse an address.
+
+The `routes` directory contains the logic to make use of the Protocol implementations by composing a route through the use of one or more Protocol interfaces.
+
 # SDK package
 
 The `@wormhole-foundation/sdk` package was created to reduce the confusion reported by devs around what they needed to install and use.