diff --git a/documentation/index.html b/documentation/index.html
index ae05244..b403142 100644
--- a/documentation/index.html
+++ b/documentation/index.html
@@ -65,9 +65,11 @@
Kobalt
A universal build system for the exigent developer.
+
diff --git a/home/index.html b/home/index.html
index 6829856..309d25e 100644
--- a/home/index.html
+++ b/home/index.html
@@ -123,9 +123,34 @@ I have been a fervent believer that there is nothing that dynamically typed lang
Just a personal thing. After toying with the language for almost four years now, I wanted to take my efforts to the next level and push the language to the limit. So far, the language has held all its promises and then some.
+The path to Kobalt 1.0
+
+
+
Next step
-Is your curiosity piqued? Then proceed to Kobalt's main documentation!
+
+Even though Kobalt is currently in Alpha, I'm already using it to build most of my projects. Here are links to a few build files you can inspect to get a feel for what Kobalt enables:
+
+
+
+ - JCommander.
+ - TestNG (this build file shows an example of adding a custom task in the build itself).
+ - ... and of course, Kobalt itself (this build file demonstrates multi projects and project dependencies).
+
+
+
+Here are some of the features I'm either working on or planning to (or hoping that a contributor will take on):
+
+
+
+ - More plug-ins: Android, apt, coverage, etc...
+ - Improve existing plug-ins (Java, Kotlin, etc...).
+ - An IDEA plug-in to improve auto completion in the IDE. Since Kobalt build files are Kotlin files, the IDE already does a good job at offering helpful auto completion suggestions, but a thin plug-in on top of the Kotlin mode would allow to reorder these suggestions and put the Directives (Kobalt's functions that you can use in a build file) at the top of the list, making writing build files even easier than it already is.
+ - Support for build flavors and build types. I'd like to adapt what's currently available in the Gradle Android plug-in and make it available across all build types (e.g. debug/release, etc...), which might mean supporting build flavors and types in Kobalt's core itself.
+
+
+Is your curiosity piqued? Are you interested in writing some cool Kotlin code and contribute to Kobalt? Or maybe just download and run Kobalt on your own projects just to get a feel for it? Then proceed to Kobalt's main documentation!