anchor.diff:  	|  Pretty straight forward. I send in the "active" property to indicate which menu is currently the active menu. We'll later extend this to enable it to change dynamically on the client. 
   	| However, we're first building for  server only, "static" pages. That means that when the component renders, which is only once on the server, it only needs to know which menu item is active for that response.
   p
  -	| On a personal note, the Menu component eloquently  captures what I love about React and the way to build components in it. It is all about composability and reuse. It's very powerful pattern.
  +	| On a personal note, the Menu component eloquently  captures what I love about React and the way to build components in it. It is all about composability and reuse. It's a very powerful pattern.
   p
   	| That's the menu created. Quite simple!
   h5 The ContentPanel
  
positive.code: 					var content = Jade.renderFile(path, {compileDebug:true});	
  					return content;
  				}
  	p No particular magic here to note. In the "getParsedPage()",  we find the file base on convention (named the same as the menu item), and as Jade to render it for us.
  	
  	h4 4. Using the rendered output
  	| React has rendered our components to strings, and now we must use those strings. In "/views/layout.jade", we use the header and menu HTML strings as follows:
  
negative.code: 	span.title Express
  	span.description
  		| An open source web application framework for Node.js. In other words, it
  		| provides the infrastructure for handling HTTP requests and responses.
  	a.reference(href="http://expressjs.com/") Express.js home
  	a.reference(href="https://www.npmjs.com/package/express") Express.js NPM package
  p.definition
  