From fe913b0072ba6242c3e675f218f2bbc7c9fec504 Mon Sep 17 00:00:00 2001
From: Jocelyn Fiat <github@djoce.net>
Date: Thu, 27 Feb 2014 06:48:24 -0800
Subject: [PATCH] added anchor link for wiki and jekyl engine

---
 Documentation.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation.md b/Documentation.md
index 14145ffe..89c4264c 100644
--- a/Documentation.md
+++ b/Documentation.md
@@ -15,6 +15,7 @@ The framework also provides a router component to help dispatching the incoming
 A service can be a web api, a web interface, … what ever run on top of HTTP.
 
 <a name="wiki-service"></a>
+<a name="service"></a>
 # Service
 > see interface: **WSF_SERVICE** 
 
@@ -29,6 +30,7 @@ For convenience, the framework provides richer service interface that handles th
 > [Learn more about service](Documentation__Service)
 
 <a name="wiki-request"></a><a name="wiki-response"></a><a name="wiki-request-and-response"></a>
+<a name="request"></a><a name="response"></a><a name="request-and-response"></a>
 # Request and Response
 > see interface: **WSF_REQUEST** and **WSF_RESPONSE** 
 
@@ -51,6 +53,7 @@ The **WSF_RESPONSE** represents the communication toward the client, a service n
 > [Learn more about request](Documentation__Request) and [about response](Documentation__Response)
 
 <a name="wiki-connector"></a>
+<a name="connector"></a>
 # Connectors: 
 > see **WGI_CONNECTOR**
 
@@ -66,6 +69,7 @@ It is fairly easy to add new connector, it just has to follow the EWSGI interfac
 > [Learn more about connector](Documentation__Connector)
 
 <a name="wiki-router"></a>
+<a name="router"></a>
 # Router or Request Dispatcher:
 > Routes HTTP requests to the proper execution code
 
@@ -166,9 +170,11 @@ examples
 
 
 <a name="wiki-EWSGI"></a>
+<a name="EWSGI"></a>
 # EWSGI Specification
 
 <a name="wiki-libraries"></a>
+<a name="libraries"></a>
 # Libraries 
 
 External libraries are included, such as Cypress OAuth (Security), HTML parsing library, Template Engine Smarty.