diff --git a/css/site/site.css b/css/site/site.css index b6d5092d..9519056a 100644 --- a/css/site/site.css +++ b/css/site/site.css @@ -160,7 +160,7 @@ section.grey:after { color:#333333; } -.library .row .well { +.library .tutorials .well { height: 60px; } diff --git a/library.html b/library.html index 850afcf3..4e980bc6 100644 --- a/library.html +++ b/library.html @@ -4,10 +4,9 @@ title: Library - Home ---
Models help you structure your work with data by providing some standard objects such as Dataset and Record – a Dataset being a collection of Records. More »
+Backends connect your Models to data sources (and stores) – for example Google Docs spreadsheets, local CSV files, the DataHub, ElasticSearch etc. More »
+Views are user interface components for displaying, editing or interacting with the data. For example, maps, graphs, data grids or a query editor. More »
+Recline has a simple structure layered on top of the basic Model/View - distinction inherent in Backbone.
- -There are two main model objects:
-Additional, related models:
-More detail of how these work can be found in the Model source docs.
- - -Backends connect Dataset and Records to data from a - specific 'Backend' data source. They provide methods for loading and saving - Datasets and individuals Records as well as for bulk loading via a query API - and doing bulk transforms on the backend.
- -A template Base class can be found in the - Backend base module of the source docs. It records both the relevant - methods a Backend must have and (optionally) provides a base 'class' for - inheritance. You can also find detailed examples of backend implementations in - the source documentation below.
- -Complementing the model are various Views (you can - also easily write your own). Each view holds a pointer to a Dataset:
-There are additional views which do not display a whole dataset but which - are useful:
-