diff --git a/Gemfile b/Gemfile
index 85339b4..7410638 100644
--- a/Gemfile
+++ b/Gemfile
@@ -13,6 +13,9 @@ gem "jekyll", "~> 3.7.0"
 # This is the default theme for new Jekyll sites. You may change this to anything you like.
 gem "minima", "~> 2.0"
 
+# Highlighter
+gem "rouge"
+
 # If you want to use GitHub Pages, remove the "gem "jekyll"" above and
 # uncomment the line below. To upgrade, run `bundle update github-pages`.
 # gem "github-pages", group: :jekyll_plugins
diff --git a/Gemfile.lock b/Gemfile.lock
index 4b08d7a..721c885 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -64,6 +64,7 @@ DEPENDENCIES
   jekyll (~> 3.7.0)
   jekyll-feed (~> 0.6)
   minima (~> 2.0)
+  rouge
   tzinfo-data
 
 BUNDLED WITH
diff --git a/_config.yml b/_config.yml
index 4f544ee..e105596 100644
--- a/_config.yml
+++ b/_config.yml
@@ -30,6 +30,7 @@ github_username:  fullhacker
 # Build settings
 markdown: kramdown
 theme: minima
+highighter: rouge
 plugins:
   - jekyll-feed
 
diff --git a/_drafts/draft-one.md b/_drafts/draft-one.md
index 36580a0..fca5dad 100644
--- a/_drafts/draft-one.md
+++ b/_drafts/draft-one.md
@@ -3,3 +3,11 @@ layout: post
 ---
 
 # Sample Draft
+How to Create a Github Pages blog *FREE HOSTING*
+
+- a bit technical, you might see some code.
+
+1. Github account
+2. Set up SSH Keys (optional, but beneficial)
+2. Github repo
+3. Advanced: Jekyll
diff --git a/_includes/head.html b/_includes/head.html
index f75d467..b8e571b 100644
--- a/_includes/head.html
+++ b/_includes/head.html
@@ -12,5 +12,5 @@
   src="https://code.jquery.com/jquery-3.2.1.min.js"
   integrity="sha256-hwg4gsxgFZhOsEEamdOYGBf13FyQuiTwlAQgxVSNgt4="
   crossorigin="anonymous"></script>
-  <script src="{{ "/assets/type.js" | relative_url }}"></script>
+  <script src="{{ "/assets/type-js.js" | relative_url }}"></script>
 </head>
diff --git a/_posts/2018-01-01-test-post.md b/_posts/2018-01-01-test-post.md
deleted file mode 100644
index 01fbdad..0000000
--- a/_posts/2018-01-01-test-post.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
----
-
-# Test Post
diff --git a/_posts/2018-01-09-hello-world.md b/_posts/2018-01-09-hello-world.md
index e475432..845e0c9 100644
--- a/_posts/2018-01-09-hello-world.md
+++ b/_posts/2018-01-09-hello-world.md
@@ -6,6 +6,8 @@ permalink: '/hello-world'
 
 Yes, yet another blog. Hopefully this one sticks.
 
+Test inline code: `hey`
+
 ``` javascript
 // here's some code
 console.log("here's some code");
diff --git a/_posts/Miscellaneous/0.intro.md b/_posts/Miscellaneous/0.intro.md
deleted file mode 100644
index e69de29..0000000
diff --git a/_posts/Miscellaneous/mailchimp-and-lotus-notes-issue.md b/_posts/Miscellaneous/mailchimp-and-lotus-notes-issue.md
deleted file mode 100644
index 1649b5c..0000000
--- a/_posts/Miscellaneous/mailchimp-and-lotus-notes-issue.md
+++ /dev/null
@@ -1,52 +0,0 @@
-# Mailchimp + Lotus Notes Solution for HTML Email Campaigns
-
-I remember the first time I saw a web page code generated by a WYSIWYG (What You See Is What You Get)... I had an unpleasant feeling and thought, "How could people stomach this?"
-
-Maybe because with little to no technical know-how and with minimal time and effort, they do get what they want to see? But what if after using such a tool, with much frustration, you don't get the results you want?
-
-I had a client using one WYSIWYG tool for designing HTML Email campaigns and guess what... they are not getting the results they want to see. The HTML email designs are chaotic when received in their readers' computers.
-
-
-## The Problem
-
-The client's readers use Lotus Notes for reading their emails. The problem is, Lotus Notes may not always display HTML emails as expected. Instead, it displays HTML emails in a proprietary rich-text format. This means that Lotus Notes, as an email reader, uses its own standards in rendering HTML emails that is quite different compared to all other popular email readers (i.e., Gmail, Outlook, etc.).
-
-There are HTML elements that Lotus Notes simply does not understand. To make things more complicated, different versions of Lotus Notes have different rendering standards. This means that creating an HTML email template that works for one Lotus Notes version does not guarantee it will work on others.
-
-This is why HTML Email designers hate Lotus Notes the most--pretty much like Internet Explorer for Web Developers.
-
-
-## Findings on Lotus Notes HTML email rendering
-
-Lotus Notes has several issues with widely accepted HTML standards because of its own proprietary rich-text formatting. Here are some of these issues that can be found if you search the web:
-- COLSPANS. These are attributes of table cells to tell the email client or the browser how many columns they span over. Lotus Notes cannot seem to understand this and we might need to just use multiple tables as a workaround.
-- CENTER ALIGNMENT. Using `<TABLE ALIGN="CENTER">` worked great in Lotus Notes 6.5.3. But not at all in Lotus Notes 6.5.4. Also, `<CENTER>` tags around the tables didn’t work in 6.5.4 either. We can make things simpler as a workaround so they'd look okay as left-aligned in 6.5.4.
-
-
-## Other Possible Workarounds and Good Practice
-Here are some helpful tips in designing HTML emails for Lotus Notes:
-- Use Mail Chimp's `*|ARCHIVE|*` merge tag to automatically generate a link to the online version of your MailChimp campaign. Subscribers can click this link to view your campaign directly in their web browsers.
-- Allow your subscribers to choose which version of your campaign they want to receive when they sign up to your list: HTML, Text, or Mobile. If they have difficulty viewing HTML email, they can select the Text option instead.
-- Keep your designs simple so that if they fail, your email is still readable.
-
-## Suggestion on Campaign Creation Workflow
-The WYSIWYG tool I mentioned earlier, is one that is provided by Mailchimp. This tool is great. I recommend it... if your readers' does not use Lotus Notes.
-
-Mailchimp’s Drag and Drop tool for creating Email Campaigns generates HTML code that tries to make the campaign look good in many popular email programs. Unfortunately, Lotus Notes does not play well with most of these programs’ HTML rendering standards.
-
-To make sure the Campaign will look good in Lotus Notes, we have to clean up the code that Mailchimp generates.
-
-Follow these steps to clean up the HTML email design:
-- Save Campaign as Template. To do this, Go to Campaigns page, Edit your Campaign, then click “Save as Template”. This is necessary because Mailchimp only allows Exporting to HTML from Templates.
-- Export Template to HTML. Once the Campaign is saved as a Template you can now export it into HTML code that we can clean up. Go to Templates page, click the dropdown button beside the Edit button on the Template, then select “Export as HTML”
-- Clean Up the HTML Code. Once you select the “Export as HTML” option, a file will be downloaded to your computer. Open this file in a Text Editor then do the following:
-- Add Lotus Notes specific elements.
-- In the HTML code you downloaded, you will most probably find a line with this code: `<!--[if gte mso 9]>` … replace all occurrence with `<!--[if (gte mso 9)|(IE)]>`
-- Lotus notes Microsoft’s Internet Explorer (IE) to render HTML emails.
-- Remove style rules intended for smartphones.
-- In the HTML code, if you find @media{ … } rules inside the `<style> ... </style>` tags, you may remove it.
-- These @media{ ... } rules are intended for smartphones and may not play well with Lotus Notes.
-- Make CSS style rules inline. As much as possible, apply style rules found inside the `<style> ... </style>` tags as inline styles to the elements. As of writing this blog, Mailchimp has an automatic inline feature to do this. Just check the checkbox in the design settings and Mailchimp will automatically do this for you.
-- Upload the Clean HTML Code into Mailchimp. Once you have done the cleaning up steps, you can go back to Mailchimp then create a Campaign using the new HTML Email. Create a Campain then choose HTML Email, then paste the code from the Text Editor you used.
-- Test the how the HTML Email looks. Mailchimp provides a paid feature called Inbox Preview to see how the HTML Email renders in several popular Email programs. If you are on a free account, you can use Preview Mode instead. Another option is opening an account in Litmus (http://litmus.com) which gives you screenshots of the HTML Email rendered in various Email Programs (including versions of Lotus Notes).
-
diff --git a/_posts/Opensource/0.intro.md b/_posts/Opensource/0.intro.md
deleted file mode 100644
index 020bfa5..0000000
--- a/_posts/Opensource/0.intro.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Open Source - Where to start?
-
-I have been using open source since college, studying Computer Science, and I have released a number of projects over at [Github](http://github.com/ayoayco). But up until now, I have not contributed in any other open source project (except maybe that one time in college where we were required to do so...)
-
-In this note I will document my journey into contributing to the open source community.
-
-
-## Wet your apetite
-
-Here is a list of communities/places/actions I have found over the web where I get my interest in open source all fired up.
-
-1. [Reddit's r/opensource](https://www.reddit.com/r/opensource/) - To see what's the latest in the community.
-2. [Github Trending](https://play.google.com/store/apps/details?id=com.rubik.github) - To browse through interesting repositories in Github.
-3. [Stackoverflow](https://stackoverflow.com) - To see what other developers are confused about... and sometimes to answer questions.
-4. Open an account at [Github](https://github.com).
-5. Read the [The Conscience of a Hacker](http://www.phrack.org/issues/7/3.html)
-6. Read on [How To Become A Hacker](http://catb.org/%7Eesr/faqs/hacker-howto.html)
-7. Install and play with a linux distribution (Ubuntu is a good starting point for me) [Ubuntu Homepage](https://ubuntu.com)
-8. Publish [Notes](https://github.com/ayoayco/notes) at Github
-
--- To be Continued --
-
diff --git a/_posts/Opensource/1.github.md b/_posts/Opensource/1.github.md
deleted file mode 100644
index 5ff2b53..0000000
--- a/_posts/Opensource/1.github.md
+++ /dev/null
@@ -1,20 +0,0 @@
-# Github
-
-[Github](https://github.com) is a website for opensource communities. It is sort of the place in the Web where developers get together to work on projects. Hence, I find it the best place to learn how to contribute to/start an opensource project or even just to see and learn how other developers code and communicate with each other to resolve issues. To cut the long story short, Github's a good place to learn.
-
-## Things I have learned over at github
-
-Here, I list some significant things I have learned over the time I have lurked around Github.
-
-1. Projects, the good ones, attract developers with the same interests. Communities get born around good projects. Once the project becomes big enough, Governing bodies with leaders rise up to ensure the direction of the project is properly set.
-1. There are documents that are crucial to the health of a good project. The leaders of the community/contributors need to work on these:
-   1. README.md - this document contains necessary information regarding the project for everyone interested in it.
-   2. CONTRIBUTING.md - this document contains the steps anyone who wants to contribute need to take and the principles they need to understand.
-   3. CODE\_OF\_CONDUCT.md - this document contains the pledge of everyone in the community, usually promising to be welcoming and nurturing, protecting everyone from harassment or abuse, and promoting constructive attitude.
-   4. LICENSE - this document takes care of legal matters (I still need to read more regarding this)
-1. Essentially, anyone should be able to contribute. Opensource!
-1. But before you do get to contribute to the source code, usually, projects require the code you are *merging* in to the master branch to be reviewed by other contributors. This ensures that no one messes up the code without another contributor allowing it. :)
-1. If not contributing code, you may contribute by reporting an issue.
-1. The UNIX project pioneered the idea that opensource projects must stay flexible to developers that want to change it. This means that I can take a projects code, and then hack away as my heart desires. In this sense, anyone is free to change the original project's code in anyway they want. However, any code that will be requested to merge to the original project's master branch should conform to the project's set standards such as Coding Style and Project Roadmap.
-1. Github *Issues* is the tracker for every task or discussions related to the project. Commits could directly reference an issue by having the issue number in the commit message. For example, the commit message "Fixes #1 - check for undefined parameters" will reference issue #1.
-1. A commit that refer to an issue with the word "Fixes", "Fixed", "Fix", "Closes", "Closed", or "Close" will close the issue when merged to the master branch.
diff --git a/_posts/Programming/2010-01-05-good-practice.md b/_posts/Programming/2010-01-05-good-practice.md
deleted file mode 100644
index 06819dd..0000000
--- a/_posts/Programming/2010-01-05-good-practice.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "Good Programming Practices"
-permalink: "/:title"
----
-I want to talk about programming and some practices that, I think, can make a programmer more efficient when observed. First, let's talk about what programming is.
-
-### Programming as Problem Solving
-- Programming is basically writing down code to instruct computers how to solve problems.
-- This means that there may be as many ways to code a program as there are ways to solve a problem.
-- A particular solution may be correct, but it could also be a bad/inefficient solution.
-- Never settle for correct but inefficient solutions.
-- A good programmer does not only solve problems... he does it well/efficiently.
-- To do this, one must observe good programming practices.
-
-### Good Programming Practices
-Here are some points I try to observe while programming:
-1. Think of the most appropriate data structures for the problem at hand. Don't do everything in arrays. Remember that there are other ways to represent your models than the common, out-of-the-box data types (i.e., linked lists, trees, heaps, queues, etc.)
-2. Think of the most efficient algorithm.
-3. It does not hurt to lint your code. Code linting is arguably the easiest and fastest thing you can do to make sure your code is clean. Learn how to configure code linting so that it becomes natural to your programming practice. Linting detects problematic patterns in your code that might result into bugs and even some lines that are not following a certain style guide.
-4. Follow a style guide.
-5. Writing code is very much like writing literature in the sense that you get better at it as you read and read and read good code from experienced programmers. Read code by experienced programmers. If you don't have access to these experienced programmers in your immediate circle, you can always go to [Github](https://github.com).
-6. Make it easier for others to debug / check your code. Make it as human readable as possible, without sacrificing code efficiency and simplicity.
-7. Code [DRY](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself). Meaning, Don't Repeat Yourself. Make new methods / functions for lines of code you frequently repeat, make your code design moduler for reusability. DRY coding is the opposite of WET conding which means "Write Everything Twice" or "We Enjoy Typing" or "Waste Everyone's Time" ... you get the idea.
-8. Peer Programming or just having your code reviewed by other programmers is also a good practice.
-
-### Further Readings for Good Programming Practices
-
-1. [A Pragmatic Quick Reference](https://blog.programminghorror.com/a-pragmatic-quick-reference/) - a good summary of the book [The Pragmatic Programmer: From Journeyman to Master](https://www.amazon.com/exec/obidos/ASIN/020161622X/codihorr-20)
diff --git a/_posts/Programming/basics.md b/_posts/Programming/basics.md
deleted file mode 100644
index 721be88..0000000
--- a/_posts/Programming/basics.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: "Programming Basics"
-permalink: "/programming-basics"
----
-## Table of Contents
-1. [Choosing Your First Programming Language ](#1-choosing-your-first-programming-language)
-2. [Hello World](#2-hello-world)
-3. [Inputs, Outputs](#3-inputs-outputs)
-4. [Loops](#4-loops)
-5. *...to be continued*
-
-
-## 1. Choosing Your First Programming Language
-When learning programming for the fist time, I believe it is important to decide what programming language you will study first. There is quite a lot of programming languages out there, but not all are friendly for beginners. So far, there are two programming languages that rise above the rest when it comes to friendliness to first-time programmers: C and Python.
-
-The main difference between the two as options for learning programming could be likened to your options when learning to drive cars--would you like to try out an automatic or a manual?
-
-Learning in Python is much like learning how to drive a car with an automatic transmission. You don't have to mind much of the what's happening under the hood, and what's happening is often abstracted to you. For an example, you don't have to worry about memory allocation. Whereas in C, you have more control: you're driving a manual.
-
-I learned programming for the first time in C. This, I believe, made it easier for me to learn other languages and understand how the computer works. For this reason, I find Python a little lacking when it comes to control. But I also understand Python is easier to learn and use for beginners who just wants to start coding and doesn't really plan to dive deep into computers. This is why, I think, many tutorials and classes for beginners use and recommend Python.
-
-If you have a particular problem you want to solve, you will have to consider other factors in choosing your programming language. Remember, I'm not talking about which language is more powerful (though I would still pick C). Rather, I'm just bringing up the difference of the two languages when it comes to friendliness for first-time programmers.
-
-In this note, I will be using C for my examples for the basic programming concepts I will discuss.
-
-## 2. Hello World
-```c
-#include <stdio.h>
-
-int main(void){
-    pritf("Hello world!");
-}
-```
-
-## 3. Inputs, Outputs
-## 4. Loops
-
diff --git a/_posts/Programming/linting.md b/_posts/Programming/linting.md
deleted file mode 100644
index 2a0d0b5..0000000
--- a/_posts/Programming/linting.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Code Linting
-
-Code linting is basically using a program (i.e., "linter") to check your code for problematic patterns that may cause bugs or does not conform to your preferred style guide.
-
-
diff --git a/_posts/WebDev/Angular/0.intro.md b/_posts/WebDev/Angular/0.intro.md
deleted file mode 100644
index 72576d6..0000000
--- a/_posts/WebDev/Angular/0.intro.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Angular Notes
-
-[Angular](https://angular.io) is a framework for building frontend client apps for the web and mobile. It is "Opinionated" in the sense that it *forces* you to build your app in a way that is arguably strict.
-
-Angular's version 2 and above radically changed the implementation of the first version, AngularJS. It steers away from the popular dev paradigm MVC and calls its framework MV\* (where * stands for *whatever*, i.e., Model-View-Whatever). This means that you can handle the Models in virtually whatever way you want.
diff --git a/_posts/WebDev/Angular/components.md b/_posts/WebDev/Angular/components.md
deleted file mode 100644
index 4b9599c..0000000
--- a/_posts/WebDev/Angular/components.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Angular Components
-
-Angular Components are sort of the puzzle pieces that will make the whole. As you design your angular app, you will find the different parts that you will need to work on, and these parts will directly translate into Angular Components.
-
-Here's a template for an empty component called SideBarComponent:
-
-```typescript
-import { Component } from '@angular/core';
-
-@Component({
-    selector: 'app-sidebar',
-    templateURL: './app.sidebar.component.html',
-    styleURLs: ['./app.sidebar.component.css']
-})
-
-export class AppSidebarComponent {
-
-    constructor(){}
-
-}
-```
-
-Let's break this code down and discuss it line-by-line.
-
-```typescript
-import { Component } from '@angular/core';
-```
-The first line imports other "parts" from other libraries/module. This "part" is technically a JavaScript class which could be component, service, or pipe, or maybe another JavaScript module from an external Node app. This makes it easy to reuse code by other developers or something you did for a previous project.
-
-*to be continued* 
-
diff --git a/_posts/WebDev/JavaScript/tips-and-tricks.md b/_posts/WebDev/JavaScript/tips-and-tricks.md
deleted file mode 100644
index 829f7be..0000000
--- a/_posts/WebDev/JavaScript/tips-and-tricks.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# JavaScript Random Tips and Tricks
-
-Here's a list of some JavaScript techniques I've learned so far.
-
-## Table of Contents
-- [Notation](#notation)
-- [Tips and Tricks](#tips-and-tricks)
-    1. [Exclamation Conversion to Boolean](#exclamation-conversion-to-boolean)
-    2. [Computing for Various Widths](#computing-for-various-widths)
-    3. [Quotes Conversion to String](#quotes-conversion-to-string)
-
-## Notation
-
-`// ->` is used to show the result of an expression. For example:
-
-```js
-1 + 1 // -> 2
-```
-
-`// >` means the result of `console.log` or another output. For example:
-
-```js
-console.log('hello, world!') // > hello, world!
-```
-
-`//` is just a comment used for explanations. Example:
-
-```js
-// Assigning a function to foo constant
-const foo = function () {}
-```
-
-## Tips and Tricks
-### Exclammation Conversion to Boolean
-Exclamation points can be used to convert any data type into boolean.
-
-```js
-'random string' // -> 'random string'
-!'random string' // -> false
-!!'random strign' // -> true
-```
-
-### Computing for Various Widths
-Widths can be a pain when you don't know what you're doing. Fortunately, jQuery offers methods we can use for this. The following computes for the border, padding, and margin of an image element:
-
-```js
-var borderWidth = $('img').outerWidth() - $('img').innerWidth();
-var paddingWidth = $('img').innerWidth() - $('img').width();
-var marginWidth = $('img').outerWidth(true) - $('img').outerWidth();
-
-var formattedBord = borderWidth + 'px';
-var formattedPadd = paddingWidth + 'px';
-var formattedMarg = marginWidth + 'px';
-```
-
-### Quotes Conversion to String
-A pair of single quotes (`''`) and double quotes (`""`) can be used to convert any data type into string by adding them:
-
-```js
-var integer = 123;
-var bool = true;
-var und = undefined;
-
-'' + integer // -> '123'
-"" + bool // -> 'true'
-"" + und // -> 'undefined'
-```
-
diff --git a/_posts/WebDev/web-service.md b/_posts/WebDev/web-service.md
deleted file mode 100644
index d4e892b..0000000
--- a/_posts/WebDev/web-service.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Web Services
-
-Web services make the front-end / back-end architecture possible, where most (if not all) business logic are separated from rendering the view. Here comes two popular types of Web APIs: REST and SOAP. REST, if I understand it correctly, can serve with any prototype such as HTTP or SMTP; while SOAP *is* a prototype particularly for XML-based exchange.
-
-## REST APIs
-
-REST APIs have become popular with the rise of JavaScript because it can data in JSON format, which is built in / native in JS, among other reasons. Many of today's most popular web applications provide Back-end API endpoints to provide integration capabilities for programmers.
-
-## Micro-Services
-
-Micro-services, in concept, are web services that are built independently to have virtually no effect on other features in the Web Application. Technologies should be independent from other services such that it is able to run fully whether the other services are running or not.
diff --git a/assets/main.scss b/assets/main.scss
index a25eb79..495107b 100644
--- a/assets/main.scss
+++ b/assets/main.scss
@@ -3,6 +3,8 @@
 ---
 
 @import "minima";
+@import url(type-js.css);
+@import url(vim.css);
 
 body {
     background: #333;
@@ -163,28 +165,4 @@ body {
     margin: 0;
 }
 
-/**/
-.text-js{
-    opacity: 0;
-  }
-  .cursor{
-    display: block;
-    position: absolute;
-    height: 100%;
-    top: 0;
-    right: -5px;
-    width: 3px;
-    /* Change colour of Cursor Here */
-    background-color: white;
-    z-index: 1;
-    animation: flash 0.5s none infinite alternate;
-  }
-  @keyframes flash{
-    0%{
-      opacity: 1;
-    }
-    100%{
-      opacity: 0;
-    }
-  }
   
diff --git a/assets/type-js.css b/assets/type-js.css
new file mode 100644
index 0000000..2d6a885
--- /dev/null
+++ b/assets/type-js.css
@@ -0,0 +1,25 @@
+/**/
+.text-js{
+    opacity: 0;
+  }
+  .cursor{
+    display: block;
+    position: absolute;
+    height: 100%;
+    top: 0;
+    right: -5px;
+    width: 3px;
+    /* Change colour of Cursor Here */
+    background-color: white;
+    z-index: 1;
+    animation: flash 0.5s none infinite alternate;
+  }
+  @keyframes flash{
+    0%{
+      opacity: 1;
+    }
+    100%{
+      opacity: 0;
+    }
+  }
+
diff --git a/assets/type.js b/assets/type-js.js
similarity index 100%
rename from assets/type.js
rename to assets/type-js.js
diff --git a/assets/vim.css b/assets/vim.css
new file mode 100644
index 0000000..3b5d33e
--- /dev/null
+++ b/assets/vim.css
@@ -0,0 +1,78 @@
+.highlight .hll { background-color: #222222 }
+.highlight  { background: #000000; color: #cccccc }
+.highlight .c { color: #000080 } /* Comment */
+.highlight .err { color: #cccccc; border: 1px solid #FF0000 } /* Error */
+.highlight .esc { color: #cccccc } /* Escape */
+.highlight .g { color: #cccccc } /* Generic */
+.highlight .k { color: #cdcd00 } /* Keyword */
+.highlight .l { color: #cccccc } /* Literal */
+.highlight .n { color: #cccccc } /* Name */
+.highlight .o { color: #3399cc } /* Operator */
+.highlight .x { color: #cccccc } /* Other */
+.highlight .p { color: #cccccc } /* Punctuation */
+.highlight .ch { color: #000080 } /* Comment.Hashbang */
+.highlight .cm { color: #000080 } /* Comment.Multiline */
+.highlight .cp { color: #000080 } /* Comment.Preproc */
+.highlight .cpf { color: #000080 } /* Comment.PreprocFile */
+.highlight .c1 { color: #000080 } /* Comment.Single */
+.highlight .cs { color: #cd0000; font-weight: bold } /* Comment.Special */
+.highlight .gd { color: #cd0000 } /* Generic.Deleted */
+.highlight .ge { color: #cccccc; font-style: italic } /* Generic.Emph */
+.highlight .gr { color: #FF0000 } /* Generic.Error */
+.highlight .gh { color: #000080; font-weight: bold } /* Generic.Heading */
+.highlight .gi { color: #00cd00 } /* Generic.Inserted */
+.highlight .go { color: #888888 } /* Generic.Output */
+.highlight .gp { color: #000080; font-weight: bold } /* Generic.Prompt */
+.highlight .gs { color: #cccccc; font-weight: bold } /* Generic.Strong */
+.highlight .gu { color: #800080; font-weight: bold } /* Generic.Subheading */
+.highlight .gt { color: #0044DD } /* Generic.Traceback */
+.highlight .kc { color: #cdcd00 } /* Keyword.Constant */
+.highlight .kd { color: #00cd00 } /* Keyword.Declaration */
+.highlight .kn { color: #cd00cd } /* Keyword.Namespace */
+.highlight .kp { color: #cdcd00 } /* Keyword.Pseudo */
+.highlight .kr { color: #cdcd00 } /* Keyword.Reserved */
+.highlight .kt { color: #00cd00 } /* Keyword.Type */
+.highlight .ld { color: #cccccc } /* Literal.Date */
+.highlight .m { color: #cd00cd } /* Literal.Number */
+.highlight .s { color: #cd0000 } /* Literal.String */
+.highlight .na { color: #cccccc } /* Name.Attribute */
+.highlight .nb { color: #cd00cd } /* Name.Builtin */
+.highlight .nc { color: #00cdcd } /* Name.Class */
+.highlight .no { color: #cccccc } /* Name.Constant */
+.highlight .nd { color: #cccccc } /* Name.Decorator */
+.highlight .ni { color: #cccccc } /* Name.Entity */
+.highlight .ne { color: #666699; font-weight: bold } /* Name.Exception */
+.highlight .nf { color: #cccccc } /* Name.Function */
+.highlight .nl { color: #cccccc } /* Name.Label */
+.highlight .nn { color: #cccccc } /* Name.Namespace */
+.highlight .nx { color: #cccccc } /* Name.Other */
+.highlight .py { color: #cccccc } /* Name.Property */
+.highlight .nt { color: #cccccc } /* Name.Tag */
+.highlight .nv { color: #00cdcd } /* Name.Variable */
+.highlight .ow { color: #cdcd00 } /* Operator.Word */
+.highlight .w { color: #cccccc } /* Text.Whitespace */
+.highlight .mb { color: #cd00cd } /* Literal.Number.Bin */
+.highlight .mf { color: #cd00cd } /* Literal.Number.Float */
+.highlight .mh { color: #cd00cd } /* Literal.Number.Hex */
+.highlight .mi { color: #cd00cd } /* Literal.Number.Integer */
+.highlight .mo { color: #cd00cd } /* Literal.Number.Oct */
+.highlight .sa { color: #cd0000 } /* Literal.String.Affix */
+.highlight .sb { color: #cd0000 } /* Literal.String.Backtick */
+.highlight .sc { color: #cd0000 } /* Literal.String.Char */
+.highlight .dl { color: #cd0000 } /* Literal.String.Delimiter */
+.highlight .sd { color: #cd0000 } /* Literal.String.Doc */
+.highlight .s2 { color: #cd0000 } /* Literal.String.Double */
+.highlight .se { color: #cd0000 } /* Literal.String.Escape */
+.highlight .sh { color: #cd0000 } /* Literal.String.Heredoc */
+.highlight .si { color: #cd0000 } /* Literal.String.Interpol */
+.highlight .sx { color: #cd0000 } /* Literal.String.Other */
+.highlight .sr { color: #cd0000 } /* Literal.String.Regex */
+.highlight .s1 { color: #cd0000 } /* Literal.String.Single */
+.highlight .ss { color: #cd0000 } /* Literal.String.Symbol */
+.highlight .bp { color: #cd00cd } /* Name.Builtin.Pseudo */
+.highlight .fm { color: #cccccc } /* Name.Function.Magic */
+.highlight .vc { color: #00cdcd } /* Name.Variable.Class */
+.highlight .vg { color: #00cdcd } /* Name.Variable.Global */
+.highlight .vi { color: #00cdcd } /* Name.Variable.Instance */
+.highlight .vm { color: #00cdcd } /* Name.Variable.Magic */
+.highlight .il { color: #cd00cd } /* Literal.Number.Integer.Long */