jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Fixed typos in some of the pages (#1270)

Browse source 
* Update architecture.markdown

* Update component_discovery.markdown

* Update development_validation.markdown

* Update frontend.markdown

* Update maintenance.markdown

* Update multiple_instances.markdown

* Update python_api.markdown

* Update releasing.markdown

* Update rest_api.markdown

* Update server_sent_events.markdown

* Update website.markdown
This commit is contained in:
KAMAL AWASTHI 2016-10-20 14:59:37 +05:30 • committed by Fabian Affolter
parent 2484dc43e3
commit 404815fae0
11 changed files with 30 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

4
source/developers/frontend.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
---
Home Assistant uses [Polymer](https://www.polymer-project.org/) for the UI and [NuclearJS](http://optimizely.github.io/nuclear-js/) for maintaing the app state.
Home Assistant uses [Polymer](https://www.polymer-project.org/) for the UI and [NuclearJS](http://optimizely.github.io/nuclear-js/) for maintaining the app state.
* Polymer allows building encapsulated custom HTML elements.
[Home-Assistant-Polymer source code on GitHub.](https://github.com/home-assistant/home-assistant-polymer)
@ -29,7 +29,7 @@ http:
development: 1
```
As everything is compiled into the file `frontend.html` you do not want to work with the compiled version but with the seperate files during development.
As everything is compiled into the file `frontend.html` you do not want to work with the compiled version but with the separate files during development.
Next step is to get the frontend code. When you clone the Home Assistant repository, the frontend repository is not cloned by default. You can setup the frontend development environment by running: