# Welcome to <img alt="Lively 4" style="position:relative; top: 25px" src="media/lively4_logo_smooth_100.png" />

* Sofware Architecture Group, Hasso Plattner Institute,  2015, 2016 [MIT LICENSE](LICENSE)
* Stefan Lehmann, Jens Lincke, Tim Felgentreff, et al
* Seminars
  * Software Design  [SWD 2015](https://lively-kernel.org/lively4/Lively4.wiki/SWD15.md) 
   [SWD 2016](https://lively-kernel.org/lively4/Lively4.wiki/SWD16.md)
  * Web-based Development [WebDev 2016](https://lively-kernel.org/lively4/Lively4.wiki/WebDev16.md) 
* [readme](README.md)

## Live Source Code

* [modules](src/client/) 
  * [lively.js](src/client/lively.js)
  * [contextmenu.js](src/client/contextmenu.js)
  * [keys.js](src/client/keys.js)
  * [html.js](src/client/html.js)
  * ...
* [UI components (templates)](templates/) [UI classes](templates/classes/) 
  * [lively-container template](templates/lively-container.html) |  [Container class](templates/classes/Container.js)
  * ...
* [service worker](src/swx/)


## External Code

We hope to come up with a solution, that will be as comfortable as npm for node.js development, 
but at the same time will serve our need better to jump into development and immediatly make local customizations. 

* [node modules](node_modules/): automatically updated, but not availablen on github.io
* [external](src/external/): static copies, manually management needed
* [vendor](vendor/) #Refactor