Link to the syncbase example apps from the overview doc.
Change-Id: Ib790ae535ec5f84412bf1c2e2b7428d006e28db5
diff --git a/content/concepts/syncbase-overview.md b/content/concepts/syncbase-overview.md
index fb1480d..06c1a82 100644
--- a/content/concepts/syncbase-overview.md
+++ b/content/concepts/syncbase-overview.md
@@ -215,13 +215,14 @@
## Example Apps
-We examined 15+ apps in detail to understand what granularity of access control
-and syncing was appropriate. For some apps like a news reader or a brokerage,
-everything is single user, so syncing all of the data in the local database is
-appropriate. For apps like turn-based games or Nest, there are islands of data
-(e.g. one instance of a game is totally separate from another, one house is
-totally separate from another), so grouping the data into syncgroups is easy.
-The remaining apps were more complicated.
+We [examined 15+ apps in detail](/designdocs/syncbase-examples.html)
+to understand what granularity of access control and syncing was appropriate.
+For some apps like a news reader or a brokerage, everything is single user, so
+syncing all of the data in the local database is appropriate. For apps like
+turn-based games or Nest, there are islands of data (e.g. one instance of a
+game is totally separate from another, one house is totally separate from
+another), so grouping the data into syncgroups is easy. The remaining apps
+were more complicated.
For productivity apps like Todos or Docs, it might make sense to have folders
and subfolders. The user might want to share a root folder, a subfolder, or
