Merge pull request #34 from strongloop/ov_diagram

added apiexplorer placeholder and big picture
This commit is contained in:
Al Tsang 2013-09-17 09:29:35 -07:00
commit ea70e0d08f
7 changed files with 30 additions and 6 deletions

View File

@ -6,6 +6,7 @@
"docs/gettingstarted.md", "docs/gettingstarted.md",
"docs/resources.md", "docs/resources.md",
"docs/concepts.md", "docs/concepts.md",
"docs/apiexplorer.md",
"docs/cli.md", "docs/cli.md",
"docs/api.md", "docs/api.md",
"docs/ios.md", "docs/ios.md",
@ -13,7 +14,5 @@
"docs/java.md", "docs/java.md",
"docs/rest.md" "docs/rest.md"
], ],
"assets": { "assets": "/docs/assets"
"/": "/docs"
}
} }

5
docs/apiexplorer.md Normal file
View File

@ -0,0 +1,5 @@
##API Explorer
***Raymond-- Please insert here***
---

View File

Before

Width:  |  Height:  |  Size: 64 KiB

After

Width:  |  Height:  |  Size: 64 KiB

BIN
docs/assets/loopback_ov.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 167 KiB

View File

@ -29,7 +29,7 @@ $ slc run my-app
``` ```
#### model #### model
Create a model in an existing LoopBack application. If you provide the Create a model in an existing LoopBack application. If you provide the
`-i` or `--interactive` flags, you will be prompted through a model `-i` or `--interactive` flags, you will be prompted through a model
configuration. The `--data-source` flag allows you to specify the name of a configuration. The `--data-source` flag allows you to specify the name of a
custom data. Otheriwse it will use the data source named "db". custom data. Otheriwse it will use the data source named "db".
@ -38,3 +38,5 @@ custom data. Otheriwse it will use the data source named "db".
$ cd my-app $ cd my-app
$ slc lb model product $ slc lb model product
``` ```
---

View File

@ -27,7 +27,7 @@ mobile SDKs for [iOS, Android, and HTML5](#mobile-clients). Using the API,
clients can query databases, store data, upload files, send emails, create push clients can query databases, store data, upload files, send emails, create push
notifications, register users, and any other behavior provided by data sources. notifications, register users, and any other behavior provided by data sources.
![concepts](loopback-concepts.png "LoopBack Concepts") ![concepts](assets/loopback-concepts.png "LoopBack Concepts")
### Mobile Clients ### Mobile Clients
@ -216,4 +216,23 @@ your client on the front end.
For more information, please read the [Remoting Guide](/strong-remoting). For more information, please read the [Remoting Guide](/strong-remoting).
### The Big Picture
LoopBack's overall representation is illustrated below through its
runtime sub-components:
- Mobile Clients
- API Gateway - ***Coming Soon***
- API Server
- Enterprise Connectors
As well as its management sub-components:
- Editor - ***Coming Soon***
- Admin Console - ***Coming Soon***
- LoopBack Shell
- Repository/Registry
![loopback_overview](assets/loopback_ov.png "LoopBack Overview")
--- ---

View File

@ -56,5 +56,4 @@ API Explorer</a>
- To see the provided CPU profiling and path trace features, check out the - To see the provided CPU profiling and path trace features, check out the
[StrongOps Quick Start Guide](http://docs.strongloop.com/strongops#quick-start). [StrongOps Quick Start Guide](http://docs.strongloop.com/strongops#quick-start).
--- ---