Update

CNAME

@@ -0,0 +1 @@
+madhattercreek.com

README.md

@@ -1,15 +1,2 @@
 # Portfolio Iro Theme
 ## Based on Type Theme
-
-![Default Type Theme blog](https://bloc-global-assets.s3.amazonaws.com/portfolio/portfolio-iro.png)
-
-A free and open-source [Jekyll](http://jekyllrb.com) theme. Great for blogs and easy to customize.
-
-## Get Started
-
-[Demo](https://rohanchandra.github.io/type-theme/)
-
-[Using Type](https://rohanchandra.github.io/project/type/)
-
-## License
-The MIT License (MIT)

_config.yml

@@ -1,46 +1,52 @@
 # SITE CONFIGURATION
 baseurl: "" # the subpath of your site, e.g. /blog/
-url: "0.0.0.0" # the base hostname & protocol for your site
+#url: "0.0.0.0" # the base hostname & protocol for your site
+
+url: "https://robbee72.github.io"
+
 
 # THEME-SPECIFIC CONFIGURATION
 theme_settings:
   # Meta
-  title: Joey Kirk
-  avatar: avatar.png
+  title: Keith Robinson
+  avatar: krobinson.png
   gravatar: # Email MD5 hash
   description: "A website with blog posts and pages" # used by search engines
 
-  # Header and footer text
-  header_text: >
-     <h1>Designer, Developer, Writer, and Dad.</h1>
+  # Header and footer tex
+  header_text:
+
+     <h1>Mad Hatter Creek Studio.</h1>
+
+
   header_text_feature_image:
   footer_text: >
    Powered by <a href="http://jekyllrb.com">Jekyll</a> with <a href="https://rohanchandra.github.io/project/type/">Type Theme</a>
 
   # Icons
   rss: false
-  email_address: # Full email address, e.g. "sam@example.com"
+  email_address: krobnson@gmail.com
   behance:
   bitbucket:
-  dribbble: "joeykirk"
-  facebook: "joeykirk"
+  dribbble: 
+  facebook: profile.php?id=100009547817420
   flickr:
-  github: "madebymunsters/type-theme"
+  github: robbee72/robbee.github.io
   google_plus:
-  instagram: "joeykirk"
+  instagram: 
   linkedin:  # Full URL
   pinterest:
   reddit:
-  soundcloud:
+  soundcloud: keith-robinson-101595413
   stack_exchange:  # Full URL
   steam:
   tumblr:
-  twitter: "joeykirk"
+  twitter: 
   wordpress:
   youtube:
 
   # Scripts
-  google_analytics: # Tracking ID, e.g. "UA-000000-01"
+  google_analytics: "UA-23660105"
   disqus_shortname:
   katex: true # Enable if using math markup
 
@@ -57,7 +63,7 @@ theme_settings:
   google_fonts: "Source+Sans+Pro:400,700,700italic,400italic"
 
 # PAGINATION
-paginate: 5
+paginate: 6
 paginate_path: "blog/page:num"
 
 # COLLECTIONS
@@ -71,4 +77,4 @@ sass:
   sass_dir: _sass
   style: :compressed
 
-gems: [jekyll-paginate]
+gems: [jekyll-paginate]

_portfolio/PTO.md

@@ -0,0 +1,79 @@
+---
+layout: post
+
+title: PTO 
+
+feature-img: "img/events_controller.png"
+thumbnail-path: "img/calendar_controller.png"
+short-description: Paid Time Off  Calendar!
+
+---
+ The PTO project was designed to track and schedule an employees paid time off.  This was not a preset bloc project . It allows employees to look at a calendar and request Paid Time Off from the calendar, that employees manager can then approve or disapprove a request. From the managers calendar they can see all scheduled PTO on a given calendar. Thus, schedule around those requests.
+
+ ___
+
+*Here is the index page that includes a register menu; listing current user, their role, and options such Editing and Upgrading the users role. It also provides a menu bar that currently has two primary links: Calendar and Change Events.*
+{:.center}
+![]({{ site.baseurl }}/img/Frontpage.png)
+
+---
+
+
+The calendar
+{:.center}
+![]({{ site.baseurl }}/img/employee_calendar
+.png)
+
+New Event for PTO.
+
+*From the drop-down an employee or  manager can add an event which will be displayed on the calendar for a that given date.*
+{:.center}
+![]({{ site.baseurl }}/img/New_Event_PTO
+.png)
+
+---
+
+Manager's calendar.
+
+*From this calendar a manager can see all requests from employees. Here John Smith has the role of admin.*
+{:.center}
+![]({{ site.baseurl }}/img/mgr_calendar
+.png)
+
+___
+
+Events page
+{:.center}
+![]({{ site.baseurl }}/img/Allevents.png)
+
+___
+Company “W” currently employs 12,000 employees, within 32 departments, with multi-managers, running three shifts 24-7-365. Today, their use a paper Paid Time Off. The forms consist of a request form and attached calendar. There are three copies made; employee’s, supervisor manager’s, and department head’s. Per interoffice mail (snail mail) another copy is send to Human Relations, there an employee manually enters information into ERP software. Checking the status of PTO hours (or days) available for that employee. Two more copies are made; one heading to accounting/payroll and the other back to the department head.  Usually, takes seven to ten days to filter thru the system and between twenty to thirty sheets of paper, and the labor involves seven or eight people touching each “Request for PTO” form.  The currently system is a mess. 
+
+___
+Benefit chart
+{:.center}
+![]({{ site.baseurl }}/img/TaskUARB.png)
+
+___
+
+
+Code for the calendar structure.
+{% highlight javascript %}
+class Calendar
+  def initialize(date=Date.today)
+    @date = date
+
+  end
+
+  def to_a
+    CalendarWeeks.new(@date).to_a.map do |week|
+      week.map do |date|
+        [date, CalendarStyles.new(date).to_s]
+      end
+    end
+  end
+end
+{% endhighlight %}
+ Have an employee login to their personal company account. From there provide a web page base interface. Thru a calendar form that displays current status of PTO available. Here, once a manager approves the request all parties have access to the data. The employee, Human relations, accounting/payrolls. Each event has an ID. And that data can be migrated into a given database. 
+
+With Ruby on rails, I created an application that along with a bit of CSS launched a register page, a calendar, a short option menu. Giving all parties access of their data. This project could be developed farther depending on the organization and data needed. This project was developed over a three week period. 

_portfolio/alexa_project.md

@@ -0,0 +1,47 @@
+---
+layout: post
+title: Alexa Project
+feature-img: "img/amazon-echo.png"
+thumbnail-path: "img/amazon-echo.png"
+short-description: Amazon Echo Alexa project
+
+---
+Amazon's Echo Alexa project is a speech recognition app for the stand-alone device. 
+By creating a Lambda function code can be uploaded to the AWS console.
+
+{:.center}
+![]({{ site.baseurl  }}/img/lambda_function.png)
+
+---
+The developer console sets several testing and configurations. The Compliance timeframe is quick and informative. 
+
+{:.center}
+![]({{ site.baseurl }}/img/developerAmazon.png)
+
+---
+From one of my skills for Alexa. Code to randomly pick a fact the database of facts.
+
+{% highlight javascript %}
+/**
+ * Gets a random new fact from the list and returns to the user.
+ */
+function handleNewFactRequest(response) {
+    // Get a random space fact from the space facts list
+    var factIndex = Math.floor(Math.random() * FACTS.length);
+    var randomFact = FACTS[factIndex];
+
+    // Create speech output
+    var speechOutput = "Here's your fact: " + randomFact;
+    var cardTitle = "Your Fact";
+    response.tellWithCard(speechOutput, cardTitle, speechOutput);
+}
+
+// Create the handler that responds to the Alexa Request.
+exports.handler = function (event, context) {
+    // Create an instance of the SpaceGeek skill.
+    var fact = new Fact();
+    fact.execute(event, context);
+};
+{% endhighlight %}
+
+---

_portfolio/blocChat.md

@@ -0,0 +1,58 @@
+---
+layout: post
+title: BlocChat
+feature-img: "img/sample_feature_img.png"
+thumbnail-path: "img/ChatGruntBrackets.png"
+short-description: Chat page with Firebase.
+
+---
+The BlocChat project was fun. Implementing the Firebase tools and intrastructure (google).
+
+---
+
+
+{:.center}
+![]({{ site.baseurl }}/img/Coffee_house.png)
+
+---
+Realtime Database on Firebase (Google) console.
+
+{:.center}
+![]({{ site.baseurl }}/img/firebasedb.png)
+
+---
+Using Grunt from terminal on my local server.
+
+{:.center}
+![]({{ site.baseurl }}/img/ChatGruntBrackets.png)
+
+---
+Added scripts: jquery, UI Bootstrap library, Angularjs, and local scripts. 
+The code also, ran a cookies service.
+
+{% highlight javascript %}
+  <body>    
+        <ui-view></ui-view>
+
+        <script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
+        <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.4.7/angular.min.js"></script>
+        <script src="https://cdn.firebase.com/js/client/2.2.4/firebase.js"></script>
+        <script src="//maxcdn.bootstrapcdn.com/bootstrap/3.3.1/js/bootstrap.min.js"></script>
+
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/angular-ui-bootstrap/1.3.3/ui-bootstrap-tpls.min.js"></script>
+        <script src="https://cdn.firebase.com/libs/angularfire/1.2.0/angularfire.min.js"></script>
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/angular-ui-router/0.2.13/angular-ui-router.min.js"></script>
+        <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.5.2/angular-cookies.js"></script>
+        <script src="/scripts/app.js"></script> 
+        <script src="/scripts/controllers/HomeCtrl.js"></script> 
+        <script src="/scripts/controllers/ModalCtrl.js"></script>
+        <script src="/scripts/services/Room.js"></script>
+        <script src="/scripts/services/Modal.js"></script>
+
+ </body>
+{% endhighlight %}
+
+___
+
+
+Interesting real world note:  AngularFire's Authentication API documentation and the Google Angular Firebase was not consistent, updated, and or complete at the time of this exercise. Recently, Google purchased Firebase. 

_portfolio/blocipedia.md

@@ -0,0 +1,45 @@
+---
+layout: post
+
+title: Blog
+feature-img: "img/edit_wiki.png"
+thumbnail-path: "img/blocipedia_index.png"
+short-description: Blocipedia!
+
+---
+ The Blocipedia project was designed to understand how blog pages work. 
+
+ ___
+
+Here is the index page that includes a register menu; listing current user, their role, and options such Editing and Upgrading the users role. It also provides a menu bar that currently has two primary links: 
+{:.center}
+![]({{ site.baseurl }}/img/blog_entry.png)
+
+---
+
+Account upgrade link to Stripe.
+
+{:.center}
+![]({{ site.baseurl }}/img/link_to_stripe
+.png)
+
+___
+
+Edit registration page. This page was setup with Devise gem for authentication.   
+
+{:.center}
+![]({{ site.baseurl }}/img/edit_reg
+.png)
+
+---
+
+Upgrading account with Stripe. A plug and play recurring billing solution for members.
+
+{:.center}
+![]({{ site.baseurl }}/img/stripe_pay.png)
+
+___
+
+This was a good exercise for using CRUD. Also, incorporated the Pundit gem for authorization of roles.
+Used the Faker gem to generate random fake data for both users and wikis. Redcarpet gem to parse Markdown syntax. Replicated the code in HAML. A shorter, simpler form.   
+

_portfolio/blocjams.md

@@ -1,9 +1,31 @@
 ---
 layout: post
 title: BlocJams
-feature-img: "img/sample_feature_img.png"
-thumbnail-path: "https://d13yacurqjgara.cloudfront.net/users/3217/screenshots/2030966/blocjams_1x.png"
+feature-img: "img/cheeseHead.png"
+thumbnail-path: "img/cheeseHead.png"
 short-description: BlocJams for iOS is awesome!
 
 ---
-This is an example of a post which includes a feature image specified in the front matter of the post. The feature image spans the full-width of the page, and is shown with the title on permalink pages.
+Yes, there are many audio players already out there! But the BlocJams-Angular was a great project for   migrating css, assets, and angular.js development.  The project utilized Grunt (Node.js package). 
+
+The Audio player with Angular. Here I uses Bootstrap front-end framework for this Application.
+
+{:.center}
+![]({{ site.baseurl }}/img/BlocJamsAngular_grunt.png)
+
+---
+Mobile application to scale the pages.
+
+{:.center}
+![]({{ site.baseurl }}/img/BlocJamsAngular2.png)
+
+---
+
+Some of code that converts time function into minutes and seconds.
+
+{:.center}
+![]({{ site.baseurl }}/img/timecode.png)
+
+---
+The naming description logic in this project was a lesson for me. To short, and the the meaning of variables were unrecognizable. To long and meaning became overstated. 
+