diff --git a/README.md b/README.md
index b21bfb22d..c83285f63 100644
--- a/README.md
+++ b/README.md
@@ -11,3 +11,31 @@ until they are able to migrate away from it, since most of the implementations o
 
 - It is compulsory to run openmrs-module-legacyui against legacyui branch of openmrs-core
 that I have created to eventually remove legacyui.
+X
+# openmrs-module-legacyui
+[![Build Status](https://travis-ci.org/openmrs/openmrs-module-legacyui.svg?branch=master)](https://travis-ci.org/openmrs/openmrs-module-legacyui) [![Coverage Status](https://coveralls.io/repos/github/openmrs/openmrs-module-legacyui/badge.svg?branch=master)](https://coveralls.io/github/openmrs/openmrs-module-legacyui?branch=master)
+
+- The legacy user interface for OpenMRS Platform 2.x is chiefly comprised of administrative functions and the patient dashboard. 
+- A new and more contemporary UI has been introduced via a UI framework and the legacy UI is kept around for 
+administrative functions that are not yet implemented in the new UI.
+- To retire the Legacy UI as planned, it is required to move the implementations and modules that still rely on it in order to 
+maintain backwards compatibility.
+- The main idea behind this project is to move legacy UI functions into an OpenMRS module that these implementations can install
+until they are able to migrate away from it, since most of the implementations of OpenMRS around the world are running OpenMRS 1.9.
+
+- It is compulsory to run openmrs-module-legacyui against legacyui branch of openmrs-core
+that I have created to eventually remove legacyui.
+X
+# openmrs-module-legacyui
+[![Build Status](https://travis-ci.org/openmrs/openmrs-module-legacyui.svg?branch=master)](https://travis-ci.org/openmrs/openmrs-module-legacyui) [![Coverage Status](https://coveralls.io/repos/github/openmrs/openmrs-module-legacyui/badge.svg?branch=master)](https://coveralls.io/github/openmrs/openmrs-module-legacyui?branch=master)
+
+- The legacy user interface for OpenMRS Platform 2.x is chiefly comprised of administrative functions and the patient dashboard. 
+- A new and more contemporary UI has been introduced via a UI framework and the legacy UI is kept around for 
+administrative functions that are not yet implemented in the new UI.
+- To retire the Legacy UI as planned, it is required to move the implementations and modules that still rely on it in order to 
+maintain backwards compatibility.
+- The main idea behind this project is to move legacy UI functions into an OpenMRS module that these implementations can install
+until they are able to migrate away from it, since most of the implementations of OpenMRS around the world are running OpenMRS 1.9.
+
+- It is compulsory to run openmrs-module-legacyui against legacyui branch of openmrs-core
+that I have created to eventually remove legacyui.