{"id":1849,"date":"2013-05-09T09:47:28","date_gmt":"2013-05-09T14:47:28","guid":{"rendered":"https:\/\/2013.austin.wordcamp.org\/?page_id=1849"},"modified":"2013-05-14T22:51:03","modified_gmt":"2013-05-15T03:51:03","slug":"devday","status":"publish","type":"page","link":"https:\/\/austin.wordcamp.org\/2013\/devday\/","title":{"rendered":"Dev Day"},"content":{"rendered":"<h2>Advanced Sessions for Code Developers<\/h2>\n<table class=\"schedule\" width=\"625\" border=\"0\">\n<thead>\n<tr>\n<th>Time<\/th>\n<th class=\"content-track\">DevDay Tracks<br \/>\nContent<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"registration\">\n<th><\/th>\n<td class=\"widecell\" colspan=\"2\"><\/td>\n<\/tr>\n<tr>\n<th>9:00 &#8211; 9:15A<small>m<\/small><\/th>\n<td class=\"widecell\" colspan=\"2\">Welcome &#8211; Opening Remarks, Fire Exits and Bathrooms and Beer (Dev Day\u00a0 will be a soda, lemonade, ice tea event, (It was with :-)))) so, Devs, the expectation of beer is reserved for the Fire House later :-).<\/td>\n<\/tr>\n<tr>\n<th>9:30 &#8211;<\/th>\n<td class=\"content-track\">\n<div><b>Mark Kelnar<\/b><\/div>\n<div>Deploying code with Git: Everything you always wanted to know, but were afraid to ask<\/div>\n<div><\/div>\n<div>This will be a technical talk that covers using Git for version control, why it\u2019s useful for WordPress developers, as well as Git\u2019s advantages over SVN. You\u2019ll see specific use-cases from consultants and best-practice developers in the Community who use Git for their projects. We\u2019ll walk through concepts like creating a repo, committing files, versioning, and using Git to work in teams and avoid \u201cCowboy Coding.\u201d You\u2019ll also get a walkthrough of deploying to a WordPress site with Git, and conclude with Q&amp;A.<\/div>\n<\/td>\n<\/tr>\n<tr class=\"alt\">\n<th><\/th>\n<td class=\"widecell\" colspan=\"4\">\n<div><b>Jason Weaver <\/b><\/div>\n<div><strong>Responsive Menus and Off Canvas Elements<\/strong><\/div>\n<div><\/div>\n<div>The biggest challenge for front-end developers today might be the staggering amount of diversity from one browser to the next. We try to build sites that last. We try to make them look good on all the things. Considering this, we\u2019ll need to stay focused and build great looking sites that work well on any device. Common front-end layout patterns can certainly help.<\/div>\n<div><\/div>\n<div>In this session, we\u2019ll dive into code for a jQuery plugin for responsive menus and take a look at off canvas patterns for device-agnostic layouts. The talk will emphasize large and small touch screen considerations.<\/div>\n<\/td>\n<\/tr>\n<tr class=\"alt\">\n<th><\/th>\n<td class=\"content-track\"><strong>Lunch<\/strong><\/td>\n<\/tr>\n<tr class=\"alt\">\n<th><\/th>\n<td class=\"widecell\" colspan=\"2\">\n<div><b>Eddie Machado<\/b><\/div>\n<div><strong>What could possibly go wrong?<\/strong><\/div>\n<div><\/div>\n<div>How do you go about redesigning a high traffic and well established site without annoying all the users? Let&#8217;s take a look and figure it out together. Oh, and It needs to be finished next week and it should be responsive.<\/div>\n<div><\/div>\n<div>(Liason&#8217;s note: I know this session looks sparse, but he&#8217;s talking about rebuilding\u00a0<a href=\"http:\/\/thechive.com\" target=\"_blank\">thechive.com<\/a>, which I would LOVE to hear about)<\/div>\n<\/td>\n<\/tr>\n<tr class=\"alt\">\n<th><\/th>\n<td class=\"content-track\">\n<div><b>Paul Ruescher<\/b><\/div>\n<div><strong>JavaScript in WordPress<\/strong><\/div>\n<div><\/div>\n<div>The web is becoming more and more of a JavaScript playground, and WordPress is no exception. \u00a0From the recent overhaul of the media manager to some of the post revision functionality in 3.6, WordPress is undergoing a direction shift. \u00a0This session will go over the very basics of JavaScript MVC and how they can be applied to WordPress.<\/div>\n<\/td>\n<\/tr>\n<tr class=\"alt\">\n<th><\/th>\n<td class=\"content-track\">\n<div><b>Chris Olbekson<\/b><\/div>\n<div><strong>Managing themes and server environments with extensible configuration arrays<\/strong><\/div>\n<div><\/div>\n<div>The standard pattern for configuring a server environment and its sites\u2019 themes is to define several constants, set a bunch of global variables, call a few functions, and sprinkle in a few filters into the wp-config.php and functions.php. This methodology to configure WordPress makes it burdensome to allow child themes to override settings in parent themes and for there to be environment-specific configurations across servers, from development to production.<\/div>\n<div><\/div>\n<div>My talk will delve into how we have tackled this problem for large multisite installs by using multidimensional configuration arrays that can be merged and extended before being converted into the constants, global variables, and filters that WordPress relies on. Beyond the increased consistency and convenience of a central configuration registry, we\u2019ll see how using such extensible arrays allows for mixin configurations and \u201cstep-parent\u201d themes. We\u2019ll also see how storing all configuration in data arrays (as opposed to code) allows our code to be aware of its larger environment.<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>Advanced Sessions for Code Developers Time DevDay Tracks Content 9:00 &#8211; 9:15Am Welcome &#8211; Opening Remarks, Fire Exits and Bathrooms and Beer (Dev Day\u00a0 will be a soda, lemonade, ice tea event, (It was with :-)))) so, Devs, the expectation of beer is reserved for the Fire House later :-). 9:30 &#8211; Mark Kelnar Deploying [&hellip;]<\/p>\n","protected":false},"author":11322336,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-1849","page","type-page","status-publish","hentry"],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/P3740D-tP","_links":{"self":[{"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/pages\/1849","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/users\/11322336"}],"replies":[{"embeddable":true,"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/comments?post=1849"}],"version-history":[{"count":19,"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/pages\/1849\/revisions"}],"predecessor-version":[{"id":2130,"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/pages\/1849\/revisions\/2130"}],"wp:attachment":[{"href":"https:\/\/austin.wordcamp.org\/2013\/wp-json\/wp\/v2\/media?parent=1849"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}