New readme.md (for flatdoc library)

docs/EN/core.md

@@ -1,251 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.1 Core
-Lungo has several methods that are used inside its engine. Here you have them if you need to include some of their functionality in your application.
-
-
-### 3.1.1 log()
-Console system to display messages when you are in debug mode.
-
-**PARAMETERS**
-
-```
-number: 	Severity based in (1)Log, (2)Warn, (>2)Error
-string: 	Message to show in the console
-```
-
-**EXAMPLE**
-
-```
-Lungo.Core.log(1, "Launched event");
-Lungo.Core.log(2, "Warning!!");
-Lungo.Core.log(3, "Error!!!!");
-```
-
-
-### 3.1.2 execute()
-Executes callbacks based on the parameters received. 
-
-**PARAMETERS**
-
-```
-function:	callback to execute
-```
-
-**EXAMPLE**
-
-```
-var myFunc = function(){
-    //Do something
-};
-var myFunc2 = function(){
-    //Do something
-};
-Lungo.Core.execute(myFunc, myFunc2);
-```
-
-
-### 3.1.3 bind()
-Creates a new function that, when called, itself calls this function in the context of the provided this value, with a given sequence of arguments preceding any provided when the new function was called. 
-
-**PARAMETERS**
-
-```
-object:		object that 'this' can refer in the new function.
-function:	A function object.
-```
-This method **return** the function which will do the action on the object.
-
-**EXAMPLE**
-
-```
-var example = "This is ";
-var addText = function(textToAdd){
-    text = this;
-    for(var i = 0, len = textToAdd.length; i < len; i++){
-        text += " " + textToAdd[i];
-    }
-    return text;
-};
-var text = ["an", "example"];
-var finalText = Lungo.Core.bind(example, addText)(text);
-//Result: "This is an example"
-```
-
-
-### 3.1.4 mix()
-Copy from any number of objects and mix them all into a new object. The implementation is simple; just loop through arguments and copy every property of every object passed to the function. 
-
-**PARAMETERS**
-
-```
-object:	 	arguments to mix them all into a new object.
-object: 	arguments to mix them all into a new object.
-```
-This method **return** an object with the mix done.
-
-**EXAMPLE**
-
-```
-var CONFIG_BASE = {
-    name: 'lungo_db',
-    version: '1.0'
-};
-
-var CONFIG = {
-    version: '1.1';
-}
-
-var finalConfig = lng.Core.mix(CONFIG_BASE, CONFIG);
-
-/*
-Result:
-{
-    name: 'lungo_db',
-    version: '1.1'
-}
-*/
-```
-
-
-### 3.1.5 isOwnProperty()
-Every object descended from Object inherits the hasOwnProperty method. This method can be used to determine whether an object has the specified property as a direct property of that object. 
-
-**PARAMETERS**
-
-```
-object: 	object to test for a property's existence inside itself.
-string:		property the name of the property to test.
-```
-This method **return** boolean indicating if property exists.
-
-**EXAMPLE**
-
-```
-var car = {wheels:4,doors:true};
-Lungo.Core.isOwnProperty(car,"wheels");	//Result: true
-Lungo.Core.isOwnProperty(car,"wings");		//Result: false
-```
-
-
-### 3.1.6 toType()
-Determine the internal JavaScript [[Class]] of an object. 
-
-**PARAMETERS**
-
-```
-object:		object to get the real type of itself.
-```
-This method **return** a string with the internal JavaScript [[Class]]
-
-**EXAMPLE**
-
-```
-var name = "Lungo";
-Lungo.Core.toType(name);	//Result: "string"
-```
-
-
-### 3.1.7 toArray()
-Convert an array-like object into a true JavaScript array. 
-
-**PARAMETERS**
-
-```
-object:		Any object to turn into a native Array.
-```
-This method **return** the object in a plain array.
-
-**EXAMPLE**
-
-```
-var execute = function() {
-	var args = lng.Core.toArray(arguments);
-}
-```
-
-
-### 3.1.8 isMobile()
-Determine if the current environment is a mobile environment. This method **return** An object with the mix done.
-
-**EXAMPLE**
-
-```
-Lungo.Core.isMobile();
-```
-
-
-### 3.1.9 environment()
-**Returns** information of execute environment.
-
-**EXAMPLE**
-
-```
-Lungo.Core.environment();
-```
-
-
-### 3.1.10 orderByProperty()
-Copy from any number of objects and mix them all into a new object. The implementation is simple; just loop through arguments and copy every property of every object passed to the function. 
-
-**PARAMETERS**
-
-```
-list:		List of objects.
-string:		Name of the property.
-string: 	Type of order: asc or desc.
-```
-This method **return** an ordered list of objects by a property.
-
-**EXAMPLE**
-
-```
-var list = [
-    {name: 'Lungo', twitter: 'lungojs'},
-    {name: 'Quojs', twitter: 'quojs'},
-];
-
-var ordered_list = lng.Core.orderByProperty(list, 'name', 'asc');
-```
-
-
-### 3.1.11 parseUrl()
-
-**PARAMETERS**
-
-```
-string:		Url string.
-```
-This method **return**  a correct URL using hashtag character.
-
-**EXAMPLE**
-
-```
-var url = Lungo.Core.parseUrl("http://tapquo.com/#folks");
-//Result: "#folks"
-```
-
-
-### 3.1.12 findByProperty()
-Copy from any number of objects and mix them all into a new object. The implementation is simple; just loop through arguments and copy every property of every object passed to the function. 
-
-**PARAMETERS**
-
-```
-list:		The list with objects.
-string:		Name of the property.
-```
-This method **return** An instance of the object found, null if not found.
-
-**EXAMPLE**
-
-```
-var list = [
-    {name: 'Lungo', twitter: 'lungojs'},
-    {name: 'Quojs', twitter: 'quojs'},
-];
-
-var user = lng.Core.findByProperty(list, 'name', 'Lungo');
-```
-```

docs/EN/data/cache.md

@@ -1,77 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.2.1 Cache
-Lungo implements its own cache type. This cache will store the value until the wepapp is closed
-
-
-### 3.2.1.1 set()
-Sets in the LungoJS cache system a new key/value pair. 
-
-**PARAMETERS**
-
-```
-string:		Key for the new value.
-string:		[OPTIONAL] Subkey in LungoJS Cache System.
-object:		Value asigned to the key.
-```
-
-**EXAMPLE**
-
-```
-var framework = {name: "Lungo", twitter: "lungojs"};
-Lungo.Data.Cache.set("lungoFramework", framework);
-```
-
-
-### 3.2.1.2 get()
-Returns the cached value of a given key. 
-
-**PARAMETERS**
-
-```
-strin:		Key in LungoJS Cache System.
-string:		[OPTIONAL] Subkey in LungoJS Cache System.
-```
-This method **return** an object containing the value.
-
-**EXAMPLE**
-
-```
-var cachedFramework = Lungo.Data.Cache.get("lungoFramework");
-//Result: {name: "Lungo", twitter: "lungojs"}
-```
-
-
-### 3.2.1.3 remove()
-Removes the instance of a given key in LungoJs Cache System. 
-
-**PARAMETERS**
-
-```
-string:		Key in LungoJS Cache System.
-string:		[OPTIONAL] Subkey in LungoJS Cache System.
-```
-
-**EXAMPLE**
-
-```
-Lungo.Data.Cache.remove("lungoFramework");
-```
-
-
-### 3.2.1.4 exists()
-Checks if the given key is stored in the cache.
-
-**PARAMETERS**
-
-```
-string Key in LungoJS Cache System.
-```
-This method **return** a boolean value which is true if the key is found
-
-**EXAMPLE**
-
-```
-Lungo.Data.Cache.exists("lungoFramework");
-```

docs/EN/data/sql.md

@@ -1,167 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.2.2 SQL
-HTML5 provides the users with a database API. Lungo.Data.Sql is a wrapper for WebSQL to work with this APIs in the easiest way.
-
-
-### 3.2.2.1 .init()
-Initializes the SQLite storage. 
-
-**PARAMETERS**
-
-```
-object:		Object with the database configuration.
-```
-
-**EXAMPLE**
-
-```
-var CONFIG = {
-    name: 'lungo_db',         //Name of the database
-    version: '1.0',           //Version of the database
-    size: 65536,              //Size of the database
-    schema: [                 //Database schema
-        {
-            name: 'demo',     //Table name
-            drop: true,       //Drop existing content on init
-            fields: {         //Table fields
-              id: 'INTEGER PRIMARY KEY',
-              name: 'TEXT',
-              description: 'TEXT',
-              type: 'STRING',
-              done: 'INTEGER DEFAULT 0',
-              created_at: 'DATETIME'
-            }
-        },
-        {
-            name: 'twitter',
-            fields:{
-                id: 'INTEGER PRIMARY KEY',
-                name: 'TEXT',
-                account: 'TEXT'
-            }
-        }
-    ]
-};
-Lungo.Data.Sql.init(CONFIG);
-```
-
-
-### 3.2.2.2 insert()
-Inserts a data set in the given table. 
-
-**PARAMETERS**
-
-```
-string:		Name of the table that will store the entry.
-object:		Object or array of objects to store.
-```
-
-**EXAMPLE**
-
-```
-var accounts = [
-    {
-        id : 0,
-        name : 'lungo',
-        account: 'lungojs'
-    },{
-        id : 1,
-        name : 'quojs',
-        account: 'quojs'
-    }
-];
-
-Lungo.Data.Sql.insert('twitter', accounts);
-```
-
-
-### 3.2.2.3 select()
-Makes a selection query using a data set on the given table 
-
-**PARAMETERS**
-
-```
-string:		Name of the table to search into.
-object:		[OPTIONAL] Search condition.
-function:	Callback function.
-```
-This method **return** the function which will do the action on the object.
-
-**EXAMPLE**
-
-```
-var showInfo = function(data){
-    for(var i = 0, len = data.length; i < len; i++){
-        var text = "The account " + data[i].account;
-        text += " name is " + data[i].name;
-        console.log(text);
-
-};
-
-Lungo.Data.Sql.select('twitter', {account: 'Lungojs'}, showInfo);
-```
-
-
-### 3.2.2.4 update()
-Updates an entry in a given table based on a data object and an optional selection object. 
-
-**PARAMETERS**
-
-```
-string:		Name of the table to update entry.
-object:		Object data used to update the entry.
-object:		[OPTIONAL] Object selection condition.
-```
-This method **return** an object with the mix done.
-
-**EXAMPLE**
-
-```
-var account = {name: 'Quo'};
-
-Lungo.Data.Sql.update('twitter', account, {account: 'quojs'});
-```
-
-
-### 3.2.2.5 drop()
-Deletes an entry in a given table based on a selection object. 
-
-**PARAMETERS**
-
-```
-string:		Name of the table to delete entry.
-object:		Object search condition.
-```
-This method **return** boolean indicating if property exists.
-
-**EXAMPLE**
-
-```
-Lungo.Data.Sql.drop('twitter', {account: 'quojs'});
-```
-
-
-### 3.2.2.6 execute()
-Executes a SQL statement in the WebSQL storage. 
-
-**PARAMETERS**
-
-```
-string		SQL statement.
-function:	[OPTIONAL] The callback that gets a SqlResultSet
-```
-This method **return** a string with the internal JavaScript [[Class]]
-
-**EXAMPLE**
-
-```
-Lungo.Data.Sql.execute('SELECT * FROM twitter', function(result){
-    //result is a SqlResultSet
-});
-
-//Another example:
-var sql = 'UPDATE twitter SET name = "quojs" WHERE account = "quojs"';
-Lungo.Data.Sql.execute(sql);
-```

docs/EN/dom.md

@@ -1,57 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.3 DOM
-Lungo uses the famous library [QuoJS](http://quojs.tapquo.com) to handle the DOM of your application. QuoJS is a micro, modular, Object-Oriented and concise JavaScript Library that simplifies HTML document traversing, event handling, and Ajax interactions for rapid mobile web development. It allows you to write powerful, flexible and cross-browser code with its elegant, well documented, and micro coherent API.
-
-
-### 3.3.1 DOM manipulation
-Using QuoJs, you can chain functions to execute several commands in one row. For more info about [Quo's](http://quojs.tapquo.com) API please go here.
-
-**EXAMPLE**
-
-```
-<section id="main"">
-    <header data-title="Dom Manipulation"></header>
-    
-    <article id="main-article" class="active">
-        <ul>
-            <li class="dark">
-                Tap here to change the color
-            </li>
-        </ul>
-    </article>
-</section>
-
-// Subscribe to a tap event with a callback
-Lungo.dom('#main-article li').tap(function(event) {
-    Lungo.dom(this).toggleClass('light').toggleClass('dark');
-});
-
-```
-
-
-### 3.3.2 Triggers
-When sections or articles are switched an event is launched. The target section/article will launch an `load` event and the current section/article will launch the `unload` one. We can bind to this events using QuoJs.
-
-**EXAMPLE**
-
-```
-<section id="section1">
-    <article id="article1">
-        <button data-view-section="section2" data-label="2nd Section"></button>
-    </article>
-</section>
-<section id="section2">
-    <article id="article2">{{CONTENT}}</article>
-</section>
-
-// JavaScript Code
-Lungo.dom('#section1').on('unload', function(event) {
-    alert("Unloaded section 1");
-});
-
-Lungo.dom('#section2').on('load', function(event){
-    alert("Loaded section 2");
-});
-```

docs/EN/element/carousel.md

@@ -1,72 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.4.5 Lungo.Element.Carousel
-Lungo has a carousel element where content can be published can be published and the user can navigate through it using the caroussel controls.
-
-**PARAMETERS**
-
-```
-string:		Element query selector.
-function:	Function to execute when switching slide.
-```
-
-**EXAMPLE**
-
-```
-<section id="carousel" data-transition="slide">
-    <header>
-        <div class="centered title">Photo: <span>1</span></div>
-    </header>
-    <article id="art" class="active block" data-control="carousel">
-        <div>
-            <div align="center">
-                <img src="http://lorempixel.com/320/418/food/">
-            </div>
-            <div align="center">
-                <img src="http://lorempixel.com/320/418/sports/">
-            </div>
-        </div>
-    </article>
-</section>
-
-// JavaScript Code
-var el = Lungo.Dom('[data-control=carousel]').first();
-
-var example = Lungo.Element.Carousel(el, function(index, element) {
-    Lungo.dom("section#carousel .title span").html(index + 1);
-});
-```
-
-### 3.4.5.1 .prev()
-Show the previous slide.
-
-**EXAMPLE**
-
-```
-var example = Lungo.Element.Carousel(Lungo.Dom('[data-control=carousel]').first());
-Lungo.dom('[data-direction=left]').tap(example.prev);
-```
-
-
-### 3.4.5.2 .next()
-Show the next slide.
-
-**EXAMPLE**
-
-```
-var example = Lungo.Element.Carousel(Lungo.Dom('[data-control=carousel]').first());
-Lungo.dom('[data-direction=left]').tap(example.next);
-```
-
-
-### 3.4.5.3 .position()
-Returns the actual index.
-
-**EXAMPLE**
-
-```
-var example = Lungo.Element.Carousel(Lungo.Dom('[data-control=carousel]').first());
-example.next();
-alert(example.position());
-```

docs/EN/element/count.md

@@ -1,41 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.4.1 Lungo.Element.Count
-As it has been shown in the prototyping chapter, you can add a counter to elements using the data-count attribute. You can also add this counter using javascript.
-
-
-### 3.4.1.1 JavaScript method
-Set a counter to the element:
-
-**PARAMETERS**
-
-```
-string:		Element query selector.
-number:		Value of the counter.
-```
-
-**EXAMPLE**
-
-```
-Lungo.Element.count("#messages", 5);
-```
-
-
-### 3.4.1.2 HTML
-You can define via HTML a default value for a count element.
-
-**EXAMPLE**
-
-```
-<section>
-	…
-	<footer>
-		<nav>
-			<a href="#" data-icon="user" data-count="12"></a>
-			<a href="#" data-icon="globe"></a>
-			<a href="#" data-icon="cog"></a>
-		</nav>
-	</footer>
-</section>
-```

docs/EN/element/loading.md

@@ -1,26 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.4.3 Lungo.Element.Loading
-As it has been shown in the prototyping chapter, you can create a loading animation using the data-loading attribute. You can also add this animation using javascript
-
-**PARAMETERS**
-
-```
-string:		Element query selector.
-string:		[OPTIONAL] Stylesheet.
-```
-This method **returns** an instance of the object founded.
-
-**EXAMPLE**
-
-```
-<section id="main" data-transition="">
-    <header data-title="loading"></header>
-    <article id="main-article"></article>
-</section>
-
-// JavaScript Code
-Lungo.Element.loading("#main-article", 1);
-```
-

docs/EN/element/progress.md

@@ -1,32 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.4.2 Lungo.Element.Count
-As it has been shown in the prototyping chapter, you can create a progress bar using the data-progress attribute. You can also add this bar using javascript.
-
-**PARAMETERS**
-
-```
-string:		Element query selector.
-number:		The percentage value.
-boolean:	Boolean to show the percentage label.
-```
-
-**EXAMPLE**
-
-```
-<section id="main" data-transition="">
-    <article id="main-article" class="active list indented scroll">
-        <form>
-            <div class="progress">
-                <span class="bar">
-                    <span class="value"></span>
-                </span>
-            </div>
-        </form>
-    </article>
-</section>
-
-Lungo.Element.progress("#progress-normal", 65, true);
-```
-

docs/EN/element/pull_and_refresh.md

@@ -1,41 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.4.4 Lungo.Element.Pull
-As it has been shown in the prototyping chapter, you can create a pull and refresh element addind data-pull and some javascript code. Here you will see how to write the javascript code.
-
-**PARAMETERS**
-
-```
-string:		Element query selector.
-object:		Object with the configuration.
-```
-
-**EXAMPLE**
-
-```
-<section id="main" data-pull="normal">
-    <header data-title="Pull & Refresh"></header>
-    <article id="main-article">
-        <ul>
-             <li class="dark" data-icon="help">
-                    <strong>
-                    Test this featury only drag down.
-                </strong>
-                <small>This element has an associated event</small>
-            </li>
-        </ul>
-    </article>
-</section>
-
-var pull_example = new Lungo.Element.Pull('#main-article', {
-    onPull: "Pull down to refresh",      //Text on pulling
-    onRelease: "Release to get new data",//Text on releasing
-    onRefresh: "Refreshing...",          //Text on refreshing
-    callback: function() {               //Action on refresh
-        alert("Pull & Refresh completed!");
-        pull_example.hide();
-    }
-});
-```
-

docs/EN/notification.md

@@ -1,154 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.5 Notification
-To display notifications, many times people tend to use the javascript alert() function. The notification it shows looks different depending on the browser. Lungo has a notification system that shows pretty and responsive notifications styled in the same way in all the browsers, making your app look the same no matter the browser you use.
-
-
-### 3.5.1 show()
-Shows a customized notification. 
-
-**PARAMETERS**
-
-```
-string:		The icon, null for no icon.
-string:		Notification's title.
-number:		The time to show the notification, 0 for unlimited.
-function:		A function to execute when hiding the notification.
-```
-If you call to the show function without parameters it will show a loading screen
-
-**EXAMPLE**
-
-```
-var afterNotification = function(){
-    //Do something
-};
-
-Lungo.Notification.show(
-    "check",                //Icon
-    "Success",              //Title
-    3,						//Seconds
-    afterNotification       //Callback function
-);
-
-//Show loading screen
-Lungo.Notification.show();
-```
-
-
-### 3.5.2 hide()
-Hides the current notification.
-
-**EXAMPLE**
-
-```
-Lungo.Notification.hide();
-```
-
-
-### 3.5.3 success()
-Shows success notification. 
-
-**PARAMETERS**
-
-```
-string:		Notification's title.
-string:		Notification's description.
-string:		The icon, null for no icon.
-number:		The time to show the notification, 0 for unlimited.
-function:	A function to execute when hiding the notification.
-```
-
-**EXAMPLE**
-
-```
-var afterNotification = function(){
-    //Do something
-};
-
-Lungo.Notification.success(
-    "Success",                  //Title
-    "Successful operation",     //Description
-    "check",                    //Icon
-    7,                          //Time on screen
-    afterNotification           //Callback function
-);
-```
-
-
-### 3.5.4 error()
-Shows an error notification. 
-
-**PARAMETERS**
-
-```
-string:		Notification's title.
-string:		Notification's description.
-string:		The icon, null for no icon.
-number:		The time to show the notification, 0 for unlimited.
-function:	A function to execute when hiding the notification.
-```
-
-**EXAMPLE**
-
-```
-var afterNotification = function(){
-    //Do something
-};
-
-Lungo.Notification.error(
-    "Error",                      //Title
-    "Unsuccessful operation",     //Description
-    "cancel",                     //Icon
-    7,                            //Time on screen
-    afterNotification             //Callback function
-);
-```
-
-
-### 3.5.5 confirm()
-Shows a confirmation notification. 
-
-**PARAMETERS**
-
-```
-object:		An object with the notification's config.
-```
-
-**EXAMPLE**
-
-```
-Lungo.Notification.confirm({
-    icon: 'user',
-    title: 'Title of confirm.',
-    description: 'Description of confirm.',
-    accept: {
-        icon: 'checkmark',
-        label: 'Accept',
-        callback: function(){ alert("Yes!"); }
-    },
-    cancel: {
-        icon: 'close',
-        label: 'Cancel',
-        callback: function(){ alert("No!"); }
-    }
-});
-```
-
-
-### 3.5.6 html()
-Creates a notification using your own html code. 
-
-**PARAMETERS**
-
-```
-string:		The html code for the notification.
-boolean:	The closing button text.
-```
-
-**EXAMPLE**
-
-```
-Lungo.Notification.html('<h1>Hello World</h1>', "Close");
-```

docs/EN/prototype/elements.md

@@ -1,90 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 2.2 Elements
-In the ["Getting started" chapter](https://github.com/tapquo/Lungo.js/blob/master/docs/EN/prototype/get_started.md) we have talked about the basic structure of the application. To do that we used sections and articles. But Lungo uses the semantic language markup introduced with HTML5, so you can add this elements using the new semantic tags.
-
-### 2.2.1 Section & Article
-A `<section>` is a view of our application where content will be displayed and where there may be subelements as `<header>`, `<footer>` and `<article>`.
-
-```
-<section id="main">
-    <article id="main-article" class="active">
-        {{CONTENT}}
-    </article>
-</section>
-```
-
-The content a particular `<section>` is structured by `<article>`. Within a section may be as many `<article>` as you like. The article of the section that will be shown first must have th `class="active"` attribute set.
-
-```
-<section id="main_section">
-    <header data-title="example"></header>
-
-    <article id="main-article" class="active">
-        {{CONTENT}}
-    </article>
-</section>
-```
-
-
-### 2.2.2 Headers
-Each `<section>` can contain a `<header>` where the tittle of the section will be shown. Optionally you can add navigation buttons, to go to another section, go back to a previous one, go to another article or just open the aside menu.
-
-```
-<section id="main_section">
-    <header data-title="example"></header>
-
-    <article id="main-article" class="active">
-        {{CONTENT}}
-    </article>
-</section>
-```
-
-
-### 2.2.3 Footers
-Each `<section>` can contain a `<footer>`. There you can add buttons to navigate through articles, sections and even asides.
-
-```
-<section id="main_section">
-    <article id="main" class="active">
-        {{CONTENT}}
-    </article>
-    <footer>
-        <nav>
-            <a href="#" data-icon="menu" class="active"></a>
-            <a href="#" data-icon="share"></a>
-            <a href="#" data-icon="user"></a>
-            <a href="#" data-icon="users"></a>
-        </nav>
-    </footer>
-</section>
-```
-
-
-### 2.2.4 Aside
-The `<aside>` element gives us a lateral area which will appear depending on the device (tablet) or hidden (mobile). Its structure is very similar to the section one's. We can create a link that references a `<aside>` with a particular id using the navigation system of Lungo. We will use the attribute data-router (which will be discussed in subsequent chapters). We can also define the positioning of it, using style classes. The default position is left.
-
-```
-<aside id="features">
-    <header data-title="Options"></header>
-    <article class="active">
-        {{CONTENT}}
-    </article>
-</aside>
-```
-
-In your section you need link your aside (#features) with `data-aside` attribute, and you can display/hide with attribute `data-view-aside`:
-
-```
-<section id="main_section" data-aside="features">
-    <header data-title="Aside">
-        <nav>
-            <button data-view-aside="features" data-icon="menu"></button>
-        </nav>
-    </header>
-    <article id="main-article" class="active indented">
-        {{CONTENT}}
-    </article>
-</section>
-```

docs/EN/prototype/get_started.md

@@ -1,45 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 2. How to prototype
-Here you have the minimum structure of your Lungo application's body. It must contain at least: 
-
-```
-<section id="main">
-	<article id="main-article">
-		Your content
-	</article>
-</section>
-```
-
-`<section>` it's the main container of your UI Components in your App and `<article>` it must be placed inside your section and must have…. Each section and article must contain an unique ID. The JavaScript function that initializes Lungo it's:
-
-```
-Lungo.init({
-    name: 'example'
-});
-```
-
-#### Load Sync resources on init
-To make easier to create and modify your app you can create the sections in separate html files and load the synchonously, making your main file smaller and having your code organized better.
-
-```
-//Load resource on app init
-Lungo.init({
-    name: 'example',
-    resources: ['section_to_load.html']
-});
-```
-
-#### Load async resources by link
-There is other way to load resources asynchronously, just add to the `<a>` tag element the attribute data-async with the link to the section.
-
-```
-<section id="loader" data-transition="">
-    <article id="art1" class="active">
-        <a href="#main" data-router="section" data-async="section_to_load.html">
-            Go to section
-        </a>
-    </article>
-</section>
-```

docs/EN/prototype/navigation.md

@@ -1,124 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 2.3 Navigation
-The navigation in Lungo is entirely semantic, and you will use the element `<a>` or `<button>` and his data attribute "view-*" to tell the system which `<section>`, `<article>` or `<aside>` you want to go to.
-
-### 2.3.1 Data-View-* attribute
-The `data-view-*` attribute is set in the `<a>` or `<button>` element to set the type of element we are going to navigate to (`<section>`, `<article>` or `<aside>`) and in the href attribute the hashbang plus the id of the element has to be set. For this purpopuse Lungo uses the bread crumbs.
-
-```
-<section id="main">
-    <article id="article_1" class="active">
-        <button class="button" data-view-article="article_1" data-icon="forward">To article_2</button>
-    </article>
-    
-    <article id="article_2">
-        <button class="button" data-view-article="article_2" data-icon="home" data-label="To article_1"></button>
-    </article>
-</section>
-```
-
-
-### 2.3.2 Data-back attribute
-As it has been said before, Lungo's navigation is based on the bread crumbs pattern, so navigation backwards between sections is done using the data-back functionality. You can set a button in your header using the data-back attribute or use in `<a>` or `button` tags data-router="section" with href="#back"
-
-```
-<section id="main">
-    <article id="main_1" class="active">{{CONTENT}}</article>
-    <article id="main_2">{{CONTENT}}</article>
-</section>
-
-<section id="second">
-    <header data-back="home"></header>
-    <article id="second_1" class="active">
-        Same as header:
-        <button data-view-section="back" data-icon="left" data-label="Return to previous section"></button>
-    </article>
-</section>
-```
-
-
-### 2.3.3 Nav
-To create simple structures of navigation buttons within a footer or header the nav element has to be used. In the header, the nav element's position will depend on the class applied to it. `left` to the left and `right` to the right.
-
-```
-<section id="main">
-    <header data-title="<nav> example">
-        <nav class="on-left">
-            <button data-view-article="article_1" data-label="Home"></button>
-        </nav>
-        <nav class="on-right">
-            <button data-view-section="second" data-label="Section"></button>
-        </nav>
-    </header>
-
-    <article id="article_1" class="active">{{CONTENT}}</article>
-    <article id="article_2">{{OTHER_CONTENT}}</article>
-    
-    <footer>
-        <nav>
-            <a href="#" data-view-article="article_1" data-icon="home"></a>
-            <a href="#" data-view-article="article_2" data-icon="user"></a>
-            <a href="#" data-view-section="second" data-icon="right"></a>
-        </nav>
-    </footer>
-</section>
-
-<section id="second">
-    <header data-back="home" data-title="example"></header>
-    <article id="second_1">{{CONTENT}}</article>
-</section>
-```
-
-
-### 2.3.4 Groupbar
-Lungo gives you the capability to have a special menu at the top of your UI. To do this you have to extend the header element using class="extended" and create inside of it a nav element with class="groupbar"
-
-```
-<section id="main">
-    <header data-title="groupbar" class="extended"></header>
-    
-    <nav class="groupbar">
-        <a href="#" data-view-article="article_1" class="active">Art-1</a>
-        <a href="#" data-view-article="article_2">Art-2</a>
-    </nav>
-    
-    <article id="article_1" class="active">{{CONTENT}}</article>
-    <article id="article_2">{{OTHER_CONTENT}}</article>
-</section>
-```
-
-
-### 2.3.5 Title Bindings
-To update the title of a section through the navigation, just use the attribute `data-title` in your navigation element.
-
-```
-<section id="main">
-    <header data-title="Default title"></header>
-    <article id="first" class="active">
-        <button data-view-article="second" data-title="Second Article"></button>
-    </article>
-    <article id="second">
-        <button data-view-article="first" data-title="First Article"></button>
-    </article>
-</section>
-```
-
-
-### 2.3.6 Visualization bindings
-You can show nav elements when a particular article is visible.
-
-```
-<section id="main">
-    <header data-title="Title of section">
-        <nav class="on-right">
-            <button data-article="second" data-view-article="first" data-icon="left"></button>
-            <button data-article="first" data-view-article="second" data-icon="right"></button>
-        </nav>
-    </header>
-    
-    <article id="first" class="active">{{CONTENT}}</article>
-    <article id="second">{{OTHER_CONTENT}}</article>
-</section>
-```

docs/EN/router.md

@@ -1,64 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.6 Notification
-Lungo.Router provides the user with the neccesary functions to manage the navigation through javascript. The following functions allow developers to work with the navigation through sections, articles and also asides.
-
-
-### 3.6.1 section()
-This function allows the navigation from a section to another one. It is done to navigate forward to a section, if you want to go back to a previous one you have to use the back function which will be explained later. 
-
-**PARAMETERS**
-
-```
-string:		The section's id.
-```
-
-**EXAMPLE**
-
-```
-Lungo.Router.section("features");
-```
-
-
-### 3.6.2 hide()
-This function allows the navigation from an article to another one.
-
-**PARAMETERS**
-
-```
-string:		The article's id.
-```
-
-**EXAMPLE**
-
-```
-Lungo.Router.article("list","list-indented");
-```
-
-
-### 3.6.3 aside()
-Toggles the aside in a particular section. 
-
-**PARAMETERS**
-
-```
-string:		The section's id.
-string:		The aside's id.
-```
-
-**EXAMPLE**
-
-```
-Lungo.Router.aside('main', left_menu);
-```
-
-
-### 3.6.4 back()
-Lungo uses the bread crumb pattern, so to return to a previous section you have to use the Lungo.Router.back function.
-
-**EXAMPLE**
-
-```
-Lungo.Router.back();
-```

docs/EN/service.md

@@ -1,139 +0,0 @@
-Lungo - *Cross-Device Framework*
-================================
-
-## 3.7 Service
-Lungo can also make ajax requests to web services.
-
-
-### 3.7.1 Settings
-Object containing the ajax configuration.
-
-**EXAMPLE**
-
-```
-Lungo.Service.Settings.async = true;
-Lungo.Service.Settings.error = function(type, xhr){
-    //Do something
-};
-Lungo.Service.Settings.headers["Content-Type"] = "application/json";
-Lungo.Service.Settings.crossDomain = false;
-Lungo.Service.Settings.timeout = 10;
-```
-
-
-### 3.7.2 get()
-Load data from the server using a HTTP GET request. 
-
-**PARAMETERS**
-
-```
-string:		The URL to which the request is sent.
-object:		A map or string to to the server.
-function:	[OPTIONAL] Callback function. (Asynchronous)
-string:		[OPTIONAL] Mime-Type: json, xml, html, or text.
-```
-
-**EXAMPLE**
-
-```
-var url = "http://localhost:8080/myService";
-var data = {id: 25, length: 50};
-var parseResponse = function(result){
-    //Do something
-};
-
-Lungo.Service.get(url, data, parseResponse, "json");
-
-//Another example
-var result = Lungo.Service.get(url, "id=25&len=50", null, "json");
-```
-
-
-### 3.7.3 post()
-Load data from the server using a HTTP POST request. 
-
-**PARAMETERS**
-
-```
-string:		The URL to which the request is sent.
-object:		A map or string to send to the server.
-function:	[OPTIONAL] Callback function. (Asynchronous)
-string:		[OPTIONAL] Mime-Type: json, xml, html, or text.
-```
-
-**EXAMPLE**
-
-```
-var url = "http://localhost:8080/myService";
-var data = {id: 25, length: 50};
-var parseResponse = function(result){
-    //Do something
-};
-
-Lungo.Service.post(url, data, parseResponse, "json");
-
-//Another example
-var result = Lungo.Service.post(url, "id=25&len=50", null, "json");
-```
-
-
-### 3.7.4 json()
-Load data from the server using a HTTP GET request and mime-type JSON. 
-
-**PARAMETERS**
-
-```
-string:		The URL to which the request is sent.
-object:		A map or string to send to the server.
-function:	[OPTIONAL] Callback function. (Asynchronous)
-```
-
-**EXAMPLE**
-
-```
-var url = "http://localhost:8080/myService";
-var data = {id: 25, length: 50};
-var parseResponse = function(result){
-    //Do something
-};
-
-Lungo.Service.json(url, data, parseResponse);
-
-//Another example
-var result = Lungo.Service.json(url, "id=25&len=50");
-```
-
-
-### 3.7.5 cache()
-Auto-caching system with date pattern for HTTP GET requests. 
-
-**PARAMETERS**
-
-```
-string:		The URL to which the request is sent.
-object:		A map or string to send to the server.
-string:		Date pattern (example: 15 minutes, 1 hour, 3 days).
-function:	[OPTIONAL] Callback function. (Asynchronous)
-string:		[OPTIONAL] Mime-Type: json, xml, html, or text.
-```
-
-**EXAMPLE**
-
-```
-var url = "http://localhost:8080/myService";
-var data = {id: 25, length: 50};
-var parseResponse = function(result){
-    //Do something
-};
-
-Lungo.Service.cache(url, data, "2 hours", parseResponse, "json");
-
-//Another example
-var result = Lungo.Service.cache(
-    url,
-    "id=25&len=50",
-    "2 hours",
-    null,
-    "json"
-);
-```