diff --git a/categories.xml b/categories.xml
index b4f7f51..e17ec9e 100644
--- a/categories.xml
+++ b/categories.xml
@@ -1,4 +1,5 @@
 <categories>
-	<category name="Uncategorized" slug="uncategorized"/>
+	<category name="Uncategorized" slug="uncategorized"></category>
+        <category name="Configuration and Utilities" slug="config"></category>
 	<category name="All" slug="all"></category>
 </categories>
diff --git a/entries/Globalize.load.xml b/entries/Globalize.load.xml
new file mode 100644
index 0000000..68a4933
--- /dev/null
+++ b/entries/Globalize.load.xml
@@ -0,0 +1,100 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl" href="../entries2html.xsl" ?>
+<entry type="method" name="Globalize.load">
+    <title>Globalize.load()</title>
+    <signature>
+        <argument name="cldrJSONData" type="Object">
+            <desc>A JSON object with CLDR data.</desc>
+        </argument>
+    </signature>
+    <desc>This method allows you to load CLDR JSON locale data.</desc>
+    <longdesc>
+        <p>
+            This method can be called as many time as needed. All passed JSON objects are deeply merged internally.
+        </p>
+    </longdesc>
+    <example>
+        <desc>Load CLDR data.</desc>
+        <code><![CDATA[
+Globalize.load({
+  "main": {
+    "en": {
+      "identity": {
+        "version": {
+          "_cldrVersion": "25",
+          "_number": "$Revision: 91 $"
+        },
+        "generation": {
+          "_date": "$Date: 2014-03-13 22:27:12 -0500 (Thu, 13 Mar 2014) $"
+        },
+        "language": "en"
+      },
+      "dates": {
+        "calendars": {
+          "gregorian": {
+            "months": {
+              "format": {
+                "abbreviated": {
+                  "1": "Jan",
+                  "2": "Feb",
+                  "3": "Mar",
+                  "4": "Apr",
+                  "5": "May",
+                  "6": "Jun",
+                  "7": "Jul",
+                  "8": "Aug",
+                  "9": "Sep",
+                  "10": "Oct",
+                  "11": "Nov",
+                  "12": "Dec"
+                }
+              }
+            },
+            "dayPeriods": {
+              "format": {
+                "wide": {
+                  "am": "AM",
+                  "am-alt-variant": "am",
+                  "noon": "noon",
+                  "pm": "PM",
+                  "pm-alt-variant": "pm"
+                }
+              }
+            },
+            "dateFormats": {
+              "medium": "MMM d, y"
+            },
+            "timeFormats": {
+              "medium": "h:mm:ss a",
+            },
+            "dateTimeFormats": {
+              "medium": "{1}, {0}"
+            }
+          }
+        }
+      },
+      "numbers": {
+        "defaultNumberingSystem": "latn",
+        "symbols-numberSystem-latn": {
+          "group": ","
+        },
+        "decimalFormats-numberSystem-latn": {
+          "standard": "#,##0.###"
+        }
+      }
+    }
+  },
+  "supplemental": {
+    "version": {
+      "_cldrVersion": "25",
+      "_number": "$Revision: 91 $"
+    },
+    "likelySubtags": {
+      "en": "en-Latn-US",
+    }
+  }
+});
+]]></code>
+    </example>
+    <category slug="config"/>
+</entry>
diff --git a/entries/Globalize.locale.xml b/entries/Globalize.locale.xml
new file mode 100644
index 0000000..c281ab6
--- /dev/null
+++ b/entries/Globalize.locale.xml
@@ -0,0 +1,44 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl" href="../entries2html.xsl" ?>
+<entry type="method" name="Globalize.locale">
+    <title>Globalize.locale()</title>
+    <signature>
+        <argument name="locale" type="String">
+            <desc>The locale string, eg: <strong>en</strong>, <strong>pt-BR</strong>, or <strong>zh-Hant-TW</strong>. </desc>
+        </argument>
+    </signature>
+    <desc>Set default locale, or get it if locale argument is omitted.</desc>
+    <longdesc>
+        <p>
+          An application that supports globalization and/or localization will need to have a way to determine the user's preference. Attempting to automatically determine the appropriate locale is useful, but it is good practice to always offer the user a choice, by whatever means.
+        </p>
+        <p>
+          Whatever your mechanism, it is likely that you will have to correlate the user's preferences with the list of locale data supported in the app. This method allows you to select the best match given the locale data that you have included and to set the Globalize locale to the one which the user prefers.
+        </p>
+        <p>
+          LanguageMatching TBD (CLDR's spec <a href="http://www.unicode.org/reports/tr35/#LanguageMatching">http://www.unicode.org/reports/tr35/#LanguageMatching</a>).
+        </p>
+    </longdesc>
+    <example>
+        <desc>Prior to using this function, you must load cldr/supplemental/likelySubtags.json. Read CLDR content if you need more information.</desc>
+        <code><![CDATA[
+// Set "pt" as our default locale.
+Globalize.locale( "pt" );
+
+// Get default locale.
+Globalize.locale();
+// > {
+//   attributes: {
+//      "languageId": "pt",
+//      "maxLanguageId": "pt_Latn_BR",
+//      "language": "pt",
+//      "script": "Latn",
+//      "territory": "BR",
+//      "region": "BR"
+//   },
+//   some more stuff...
+// }
+]]></code>
+    </example>
+    <category slug="config"/>
+</entry>
diff --git a/pages/index.html b/pages/index.html
new file mode 100644
index 0000000..c4c5366
--- /dev/null
+++ b/pages/index.html
@@ -0,0 +1,9 @@
+<script>{
+    "title": "Globalize API Documentation"
+}</script>
+
+<p>Globalize is a JavaScript library for internationalization and localization that leverages the official Unicode CLDR JSON data.</p>
+
+<p>To get started, use the search at the top of the page, view the
+    <a href="/category/all/">full listing of entries</a>, or browse by
+    category from the sidebar.</p>
\ No newline at end of file