Initial commit

.editorconfig

@@ -0,0 +1,21 @@
+# EditorConfig helps developers define and maintain consistent
+# coding styles between different editors and IDEs
+# editorconfig.org
+
+root = true
+
+
+[*]
+
+# Change these settings to your own preference
+indent_style = space
+indent_size = 2
+
+# We recommend you to keep these unchanged
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

.gitignore

@@ -1,37 +1,5 @@
-# Logs
-logs
-*.log
-npm-debug.log*
-
-# Runtime data
-pids
-*.pid
-*.seed
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
-coverage
-
-# nyc test coverage
-.nyc_output
-
-# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (http://nodejs.org/api/addons.html)
-build/Release
-
-# Dependency directories
+bower_components
+dist
 node_modules
-jspm_packages
-
-# Optional npm cache directory
-.npm
-
-# Optional REPL history
-.node_repl_history
+build
+.idea/

.travis.yml

@@ -0,0 +1,36 @@
+language: node_js
+sudo: required
+dist: trusty
+node_js:
+  - '6'
+cache:
+  directories:
+    - node_modules
+branches:
+  except:
+    - /^v\d/
+install:
+  - npm install
+  - npm install -g bower
+  - bower install
+before_script:
+  - npm run lint
+script:
+  - npm test
+before_deploy:
+  - npm run build
+deploy:
+  - provider: firebase
+    edge: true
+    skip_cleanup: true
+    project: devfest-grx-develop
+    token: $FIREBASE_TOKEN
+    on:
+      branch: develop
+  - provider: firebase
+    edge: true
+    skip_cleanup: true
+    project: devfest-grx
+    token: $FIREBASE_TOKEN
+    on:
+      branch: master

CONTRIBUTING.md

@@ -0,0 +1,67 @@
+## Guide for Contributors
+
+Hoverboard are built in the open, and the GDG[x] team eagerly encourage any and all forms of community contribution. When contributing, please follow these guidelines:
+
+### Filing Issues
+
+**If you are filing an issue to request a feature**, please provide a clear description of the feature. It can be helpful to describe answers to the following questions:
+
+ 1. **Who will use the feature?** _“As someone filling out a form…”_
+ 2. **When will they use the feature?** _“When I enter an invalid value…”_
+ 3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
+
+**If you are filing an issue to report a bug**, please provide:
+
+ 1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
+
+ ```markdown
+
+ The `paper-foo` element causes the page to turn pink when clicked.
+
+ ## Expected outcome
+
+ The page stays the same color.
+
+ ## Actual outcome
+
+ The page turns pink.
+
+ ## Steps to reproduce
+
+ 1. Put a `paper-foo` element in the page.
+ 2. Open the page in a web browser.
+ 3. Click the `paper-foo` element.
+
+ ```
+
+ 3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
+
+### Submitting Pull Requests
+
+**Before creating a pull request**, please ensure that an issue exists for the corresponding change in the pull request that you intend to make. **If an issue does not exist, please create one per the guidelines above**. The goal is to discuss the design and necessity of the proposed change with Polymer authors and community before diving into a pull request.
+
+When submitting pull requests, please provide:
+
+ 1. **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues in the pull request description using the following syntax:
+
+ ```markdown
+ (For a single issue)
+ Fixes #20
+
+ (For multiple issues)
+ Fixes #32, fixes #40
+ ```
+
+ 2. **A succinct description of the design** used to fix any related issues. For example:
+
+ ```markdown
+ This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
+ ```
+
+ 3. **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
+
+If a proposed change contains multiple commits, please [squash commits](https://www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request) to as few as is necessary to succinctly express the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that!
+
+
+
+_Copied from [Polymer Elements contributing guide](https://github.com/PolymerElements/ContributionGuide/blob/master/CONTRIBUTING.md)_

Dockerfile

@@ -0,0 +1,15 @@
+FROM node
+
+RUN npm i -g polymer-cli bower
+
+RUN useradd -m node 
+
+ADD . /app
+
+USER node
+WORKDIR /app 
+
+RUN bower install
+
+EXPOSE 8080
+CMD polymer serve

LICENSE.md

@@ -0,0 +1,23 @@
+# License
+
+The MIT License (MIT)
+
+Copyright (c) 2016 Oleh Zasadnyy, GDG Lviv
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1 +1,171 @@
-# devfest
+![preview-web](https://cloud.githubusercontent.com/assets/2954281/17777476/5dbbbe1c-6569-11e6-9cc4-77185ae9bf92.png)
+
+# Project Hoverboard 
+
+[![Join the chat at https://gitter.im/gdg-x/hoverboard](https://badges.gitter.im/gdg-x/hoverboard.svg)](https://gitter.im/gdg-x/hoverboard?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+
+> Project Hoverboard is the next generation conference website template after 
+[Project Zeppelin](https://github.com/gdg-x/zeppelin) and more optimized 
+version - [Project Zeppelin-Grunt](https://github.com/gdg-x/zeppelin-grunt).
+
+> Template is brought by [Oleh Zasadnyy](https://plus.google.com/+OlehZasadnyy) 
+from [GDG Lviv](http://lviv.gdg.org.ua/).
+
+> *Do you :heart: it?* Show your support - please, :star: the project.
+
+:zap: [Live demo](https://hoverboard-dev.firebaseapp.com/)
+
+### Features
+:white_check_mark: Polymer  
+:white_check_mark: [PRPL pattern](https://www.polymer-project.org/1.0/toolbox/server)  
+:white_check_mark: Offline access  
+:white_check_mark: i18n  
+:white_check_mark: Material design  
+:white_check_mark: Animations  
+:white_check_mark: Integrated speakers and sessions management  
+:white_check_mark: SEO friendly  
+:white_check_mark: Optimized and fast  
+:white_check_mark: Editable theme colors  
+:white_check_mark: Quick deploy  
+
+### Setup
+:book: [Full documentation](/docs/).
+
+##### Docker based development env
+
+If you don't want to bother with the dependencies, you can develop in the docker container.
+
+Build:
+
+    docker build -t hoverboard .
+
+and run:
+
+    docker run -it -v "$PWD":/app -p 8080:8080 hoverboard
+
+:book: Read more in [docker docs](/docs/tutorials/docker.md).
+
+###### Prerequisites
+
+Install [polymer-cli](https://github.com/Polymer/polymer-cli):
+
+    npm i -g polymer-cli
+
+and [Bower](https://bower.io/):
+
+    npm i -g bower
+
+:point_right: **[Fork](https://github.com/gdg-x/hoverboard/fork) this repository** and clone it locally.
+
+##### Install dependencies
+
+    bower install
+
+##### Start the development server
+
+This command serves the app at `http://localhost:8080` and provides basic URL
+routing for the app:
+
+    polymer serve
+
+:book: Read more in [setup docs](/docs/tutorials/set-up.md).
+
+
+### Build
+
+This command performs HTML, CSS, and JS minification on the application
+dependencies, and generates a service-worker.js file with code to pre-cache the
+dependencies based on the entrypoint and fragments specified in `polymer.json`.
+The minified files are output to the `build/unbundled` folder, and are suitable
+for serving from a HTTP/2+Push compatible server.
+
+In addition the command also creates a fallback `build/bundled` folder,
+generated using fragment bundling, suitable for serving from non
+H2/push-compatible servers or to clients that do not support H2/Push.
+
+    polymer build
+
+Or you can build in Docker container:
+
+    docker run -v "$PWD":/app hoverboard polymer build
+
+:book: Read more in [deploy docs](/docs/tutorials/deploy.md).   
+
+### Updating
+Here is a git workflow for updating your fork (or downloaded copy) to the latest version:
+```
+git remote add upstream https://github.com/gdg-x/hoverboard.git
+git fetch upstream
+git merge upstream/master # OR git merge upstream/develop
+# resolve the merge conflicts in your editor
+git add . -u
+git commit -m 'Updated to the latest version'
+```
+
+### Who uses the template?
+
+Going to use the template? Go on! The only thing we ask - let us know with a 
+pull request, so we can include you in this list.
+
+| [GDG DevFest Ukraine](http://devfest.gdg.org.ua) |
+| :------------ |
+| [GDG DevFest Sao Paulo](http://sp.devfest.com.br)  |
+| [GDG DevFest Hamburg 2015](http://devfest.de)  |
+| [GDG DevFest Mezam 2015](https://devfest-mezam.gdgbambili.xyz) |
+| [GDG DevFest Silicon Valley 2015](http://devfest2015.gdgsv.com/) |
+| [GDG DevFest Belgium 2015](http://devfest.be/) |
+| [GDG DevFest South East Nigeria 2015](http://www.devfestse.com) |
+| [GDG DevFest Istanbul 2015](https://www.devfesttr.com) |
+| [GDG Cáceres CodeWeek 2015](http://codeweek.gdgcaceres.es) |
+| [GDG Bingham University Website](http://bhu.gdg.ng) |
+| [Google I/O Extended 2016 Kuala Lumpur](https://ioxkl2016.firebaseapp.com) |
+| [GDG DevFest Hamburg 2016](https://hamburg.devfest.de) |
+| [GDG DevFest Mezam 2016](https://devfest-mezam.gdgbambili.xyz) |
+| [GDG DevFest Vietnam 2016](https://devfest.vn) |
+| [GDG DevFest Seattle 2016](https://devfest.gdgseattle.org) |
+| [GDG DevFest Belgium 2016](https://devfest.be) |
+| [GDG DevFest Lisbon 2016](https://devfestlisbon.firebaseapp.com) |
+| [GDG DevFest Sudbury 2016](https://devfest.gdgsudbury.ca) |
+| [GDG DevFest Hong Kong 2016](https://devfest.gdghk.org) |
+
+### Roadmap :rocket:
+:x: Admin panel  
+:x: Firebase Integration   
+:x: My schedule  
+:x: Push notification  
+:x: ES2015  
+:x: Accessibility  
+:x: Unit/Integration Tests  
+:point_right: __Propose your feature with [creating an issue](https://github.com/gdg-x/hoverboard/issues/new)__
+
+### Contributing
+
+Project Hoverboard is still under development, and it is open for contributions. 
+Feel free to send PR. If you have any questions, feel free to contact 
+[Oleh Zasadnyy](https://plus.google.com/+OlehZasadnyy).
+
+##### General workflow
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Make your changes
+4. Run the tests, adding new ones for your code if necessary
+5. Commit your changes (`git commit -am 'Added some feature'`)
+6. Push to the branch (`git push origin my-new-feature`)
+7. Create new Pull Request
+
+:book: Read complete [contributing guide](CONTRIBUTING.md).
+
+
+### Contributors :sparkles:
+See [list of contributors](https://github.com/gdg-x/hoverboard/graphs/contributors).
+
+__Maintainer:__ [Oleh Zasadnyy](https://github.com/ozasadnyy) and [Sophie Huts](https://github.com/sophieH29).
+
+
+######The GDG App, GDG[x] are not endorsed and/or supported by Google, the corporation.
+
+
+### License
+
+Project is published under the [MIT license](https://github.com/gdg-x/hoverboard/blob/master/LICENSE.md).  
+Feel free to clone and modify repo as you want, but don't forget to add reference to authors :)