Update pages

index.html

@@ -18,6 +18,10 @@ badges:
       url:  https://build.spring.io/browse/SDG
       icon: ci
 
+    - name: CI (Travis)
+      url:  https://travis-ci.org/spring-projects/spring-statemachine
+      icon: ci
+
     - name: StackOverflow
       url:  http://stackoverflow.com/questions/tagged/spring-statemachine
       icon: stackoverflow
@@ -45,13 +49,15 @@ Spring Statemachine aims to provide following features:
 * Recipes for usual use cases
 * Distributed state machine based on a Zookeeper
 * State machine event listeners.
+* UML Eclipse Papyrus modeling.
+* Store machine config in a persistent storage.
 * Spring IOC integration to associate beans with a state machine.
 
 State machines are powerful because behaviour is always guaranteed to be consistent and relatively easily debugged due to ways how operational rules are written in stone when machine is started. Idea is that your application is and may exist in a finite number of states and then something happens which takes your application from one state to the next. What will drive a state machine are triggers which are either based on an events or timers.
 
 It is much easier to design high level logic outside of your application and then interact with a state machine with a various different ways. You will simple send interact with a state machine by sending event, listening what a state machine does or simply request a current state.
 
-Do you want to ask a question? Go to [StackOverflow](http://stackoverflow.com) and use a tag [spring-statemachine](http://stackoverflow.com/questions/tagged/spring-statemachine).
+Do you want to ask a question? Go to [StackOverflow](http://stackoverflow.com) and use a tag [spring-statemachine](http://stackoverflow.com/questions/tagged/spring-statemachine) or [Gitter](https://gitter.im/spring-projects/spring-statemachine).
 
 <span id="quick-start"></span>
 ## Quick Start