diff --git a/exampleSite/content/blog/2016-chicago.md b/exampleSite/content/blog/2016-chicago.md
new file mode 100644
index 000000000..7dc96c492
--- /dev/null
+++ b/exampleSite/content/blog/2016-chicago.md
@@ -0,0 +1,85 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2016-12-12T16:31:00-06:00"
+title = "Chicago 2016 in review"
+
++++
+
+*This post, written by Matt Stratton, first appeared on the [Chef Blog](https://blog.chef.io/2016/09/09/chef-devopsdays-chicago-wrap/) on Sept 19, 2016*
+
+[DevOpsDays Chicago](https://devopsdays.org/events/2016-chicago) took place on August 30th & 31st at Summit West in beautiful downtown Chicago. A sold-out, diverse crowd gathered for keynotes, presentations, lightning talks, and open spaces to learn, discuss, and promote all things DevOps.
+
+## Day One
+### The Presentations
+
+Leading off the presentations was a keynote by [Adam Jacob](https://twitter.com/adamhjk), who discussed [The Future of Automation](https://www.devopsdays.org/events/2016-chicago/program/adam-jacob). Topics such as the idea of “ubuntu” (not the Linux distro!), context, and the importance of ease over simplicity were markedly well-received by the audience. “When you suffer, I suffer. When you thrive, I thrive.”
+
+Other presentations included first-time presenter Joel Vasallo (Gogo), who walked us through [“The Five Phases of DevOps”](https://www.devopsdays.org/events/2016-chicago/program/joel-vasallo). Joel’s enthusiasm was contagious, and his animated GIF game was truly on-point.
+
+We can’t talk about DevOps in 2016 without a talk about Serverless, and [Jeremy Edberg](https://www.devopsdays.org/events/2016-chicago/program/jeremy-edberg) described moving to AWS Lambda, replete with real-world examples and challenges. Serverless is a hot topic, and I learned quite a bit from his presentation.
+
+Wrapping up the morning was Angela Dugan’s talk [“Fear and (Self)-Loathing In IT”](https://www.devopsdays.org/events/2016-chicago/program/angela-dugan).
+
+
+
+The key takeaway is that everyone feels like an imposter sometimes – and we are better than we think we are.
+
+### Ignite Sessions
+
+Immediately following lunch were the lightning talk Ignite sessions. For those not familiar, Ignite talks are 5 minutes long consisting of 20 slides that advance every 15 seconds.The Ignite format can be one of the most challenging ways to present a talk (I speak from experience in this!), and all of the Ignites were thought-provoking. They included:
+
+- [Alison Stanton – Ways DevOps Could Be More Accessible](https://www.devopsdays.org/events/2016-chicago/program/alison-stanton)
+- [Allie Richards – What’s that creature living in my cloud?](https://www.devopsdays.org/events/2016-chicago/program/allie-richards)
+- [Jamesha Fisher – Out of the Basement: Demystifying Security and Operations](https://www.devopsdays.org/events/2016-chicago/program/jamesha-fisher)
+- [Rebecca Miller-Webster – Building resilience in our organizations, our teams, and ourselves](https://www.devopsdays.org/events/2016-chicago/program/rebecca-miller-webster)
+- [Jeff Smith – Dungeons and Dragons….and DevOps](https://www.devopsdays.org/events/2016-chicago/program/jeff-smith)
+
+### Open Spaces
+
+In my mind, the Open Spaces are one of the most powerful and thought-provoking experiences of a DevOpsDays event. As an event organizer, I firmly believe that the main goal of the talks is to drive the discussions in the open spaces. Attendees suggested topics for discussion, and then moved into smaller rooms. The vast majority of attendees had never experienced an Open Space before, and when I spoke with them privately, many told me it was their favorite part of the conference.
+
+### Yakkity Yak (Don’t Talk Back)
+
+In DevOps, we often talk about the concept of [“yak shaving.”](http://www.hanselman.com/blog/YakShavingDefinedIllGetThatDoneAsSoonAsIShaveThisYak.aspx) At DevOpsDays Chicago, we “leveled up” our commitment for our love of yaks by actually having a yak mascot wandering through the event for participants to take “yak selfies.” Some of the best ones can be seen on the [@devopsyak Twitter account](https://www.twitter.com/devopsyak).
+
+
+
+### Evening Event
+
+On Tuesday evening, attendees retired to [10pin](http://www.10pinchicago.com/), for a night of board games, delightful beverages and snacks, and bowling! Prizes were awarded for the first people to bowl a turkey (three strikes in a row), and we were pleased to give away not one, but two Amazon Alexa devices for those excellent bowlers.
+
+## Day Two
+
+### Presentations
+
+We kicked off Wednesday with an opening keynote from [Jill Jubinski](https://twitter.com/jilljubs), entitled [“Devopsing Recruitment.”](https://www.devopsdays.org/events/2016-chicago/program/jill-jubinski) Jill helped us understand how to be empathetic to recruiters, to understand that they are actually hard-working people who want to help teams get the best people possible, and that there really isn’t that big of a divide between recruiters and engineers. Plus, there were a lot of rainbows in the presentation, which makes for good DevOps.
+
+Àbéjídé Àyodélé followed up with [“Lessons learnt from ‘Shipping’ Containers,”](https://www.devopsdays.org/events/2016-chicago/program/abejide-ayodele) and he very well might have been the most engaging speaker of the entire event! Àbéjídé dug into some of the challenges his organization had with the lifecycle of their container creation and management, and the audience hung on his every word.
+
+[Nell Shamrell-Harrington](https://twitter.com/nellshamrell) walked us through “Untangling Infrastructure Code Through Refactoring”, which was a deep-dive into a practical approach for improving our code for efficiency, readability, and optimization. Nobody can accuse this event of being light on technical content after Àbéjídé and Nell’s talks, that is for sure!
+
+Wrapping up the morning was DevOpsDays Chicago alumn Brian Henerey, sharing with us his experiences in [“Leading an Enterprise to the Public Cloud.”](https://www.devopsdays.org/events/2016-chicago/program/brian-henerey) Many folks in the audience identified with some of the “enterprise challenges” that Brian experienced, and while he (as he expected), ran out of time, his content was densely packed and very enlightening.
+
+### Ignites
+
+Day two ignites included:
+
+- [Ken Mugrage – The answer to the “where do we start” question](https://www.devopsdays.org/events/2016-chicago/program/ken-mugrage)
+- [Heidi Waterhouse – Fear of the Bus](https://www.devopsdays.org/events/2016-chicago/program/heidi-waterhouse)
+- [Morgan Rhodes – Presenting Nervously](https://www.devopsdays.org/events/2016-chicago/program/morgan-rhodes)
+- [Michael Stahnke – What I’ve learned interviewing more than 150 people face to face](https://www.devopsdays.org/events/2016-chicago/program/michael-stahnke)
+- [Joshua Zimmerman – DevOps Deep Thoughts by Not Jack Handey](https://www.devopsdays.org/events/2016-chicago/program/joshua-zimmerman)
+
+While as an organizer, I should love all of my presenters equally, Josh’s Ignite might have been my favorite of the entire conference. It was super hilarious, and one of the most clever approaches I’ve seen at a DevOpsDays.
+
+
+
+## Wrap-up
+
+This was the third iteration of DevOpsDays Chicago, and I have been an organizer of all three of them. As an organizer, I can say that this was the most smoothly run event we have ever done. Our content was top-notch, and we had over 380 attendees with a waiting list of over 150 people. In the future, we will be considering what we can do to expand the attendance to allow even more folks to join us in this great experience.
+
+If you attended the event and want to give us feedback, please feel free to tweet to [@devopsdayschi](https://twitter.com/devopsdaysChi)! We would love to hear what you thought.
+
+If you are in the Chicago area, please also join the [Chicago DevOps Meetup group](http://www.meetup.com/devops/) to collaborate with your local peers, and hear even more great talks.
diff --git a/exampleSite/content/blog/2016-chicago/deepthoughts.png b/exampleSite/content/blog/2016-chicago/deepthoughts.png
new file mode 100644
index 000000000..5199dd5a5
Binary files /dev/null and b/exampleSite/content/blog/2016-chicago/deepthoughts.png differ
diff --git a/exampleSite/content/blog/2016-chicago/imposter.png b/exampleSite/content/blog/2016-chicago/imposter.png
new file mode 100644
index 000000000..4df47137a
Binary files /dev/null and b/exampleSite/content/blog/2016-chicago/imposter.png differ
diff --git a/exampleSite/content/blog/2016-chicago/yak.png b/exampleSite/content/blog/2016-chicago/yak.png
new file mode 100644
index 000000000..14c05675d
Binary files /dev/null and b/exampleSite/content/blog/2016-chicago/yak.png differ
diff --git a/exampleSite/content/blog/2016-minneapolis.md b/exampleSite/content/blog/2016-minneapolis.md
index 57e02ce80..d54032541 100644
--- a/exampleSite/content/blog/2016-minneapolis.md
+++ b/exampleSite/content/blog/2016-minneapolis.md
@@ -5,7 +5,7 @@ Tags = ["2016"]
Author = "Bridget Kromhout"
+++
-
+
diff --git a/exampleSite/content/events/2015-amsterdam/conduct.md b/exampleSite/content/events/2015-amsterdam/conduct.md
new file mode 100644
index 000000000..b7c5a76d5
--- /dev/null
+++ b/exampleSite/content/events/2015-amsterdam/conduct.md
@@ -0,0 +1,27 @@
++++
+date = "2016-05-02T13:06:03-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## Code of Conduct
+
+Exhibitors, speakers, sponsors, staff and all other attendees at events organized by DevOps Amsterdam (DevOpsDays Amsterdam, meetups, user groups) are subject to these Community Guidelines and Code of Conduct. We are dedicated to providing a harassment-free experience for everyone, and we do not tolerate harassment of participants in any form.
+
+We ask you to be considerate of others and behave professionally and respectfully to all other participants. Remember that sexual language and imagery is not appropriate for any event venue, including talks. Participants violating these rules may be sanctioned or expelled from the event without a refund at the discretion of the organizers.
+
+Harassment includes offensive verbal comments related to gender, gender identity or expression, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+If a participant engages in harassing behavior, the event organizers may take any action they deem appropriate, including warning the offender or expulsion from the event with no refund. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of the event staff immediately.
+
+Event staff will be happy to help participants address concerns. All reports will be treated as confidential. We strongly encourage you to address your issues privately with any of our staff members who are organizing the event. We encourage you to avoid disclosing information about the incident until the staff has had sufficient time in which to address the situation. Please also keep in mind that public shaming can be counter-productive to building a strong community. We do not condone nor participate in such actions.
+
+We expect all participants to follow these rules at all event venues and related social events.
+
+### Credits
+
+Credit to Docker, Inc. and Julien Barber for writing this Code of Conduct and allowing us to use it.
+
+Additional credit to Puppet Labs, 01.org and meego.com, since they formed the starting point for many of these guidelines. The Event Code of Conduct is based on the example policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers. The PyCon Code of Conduct also served as inspiration.
+
diff --git a/exampleSite/content/events/2015-amsterdam/contact.md b/exampleSite/content/events/2015-amsterdam/contact.md
new file mode 100644
index 000000000..ae6567fbd
--- /dev/null
+++ b/exampleSite/content/events/2015-amsterdam/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-02T13:06:03-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2015-amsterdam/location.md b/exampleSite/content/events/2015-amsterdam/location.md
new file mode 100644
index 000000000..e415f1833
--- /dev/null
+++ b/exampleSite/content/events/2015-amsterdam/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-05-02T13:06:03-05:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2015-amsterdam/program.md b/exampleSite/content/events/2015-amsterdam/program.md
new file mode 100644
index 000000000..e5777f958
--- /dev/null
+++ b/exampleSite/content/events/2015-amsterdam/program.md
@@ -0,0 +1,29 @@
++++
+date = "2016-05-02T13:06:03-05:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2015-amsterdam/propose.md b/exampleSite/content/events/2015-amsterdam/propose.md
new file mode 100644
index 000000000..a88206241
--- /dev/null
+++ b/exampleSite/content/events/2015-amsterdam/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-02T13:06:03-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2015-amsterdam/sponsor.md b/exampleSite/content/events/2015-amsterdam/sponsor.md
new file mode 100644
index 000000000..6b8bd8042
--- /dev/null
+++ b/exampleSite/content/events/2015-amsterdam/sponsor.md
@@ -0,0 +1,15 @@
++++
+date = "2016-05-02T13:06:03-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+We greatly value sponsors for this open event. If you are interested in sponsoring [drop us an email](mailto:organizers-amsterdam-2015@devopsdays.org).
+
+
Please click here to download the Sponsor offering for Amsterdam 2015!
+
+
+
+devopsdays is a self-organizing conference for DevOps practitioners that depends on your sponsorships to happen. However, because of the nature of the event, we do not have vendor booths or book product pitches.
+
diff --git a/exampleSite/content/events/2015-amsterdam/welcome.md b/exampleSite/content/events/2015-amsterdam/welcome.md
new file mode 100644
index 000000000..6f61c82dd
--- /dev/null
+++ b/exampleSite/content/events/2015-amsterdam/welcome.md
@@ -0,0 +1,52 @@
++++
+date = "2016-05-02T13:06:03-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2015-amsterdam"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+ {{< event_logo >}}
+
+
+This year, we are hosting the third edition of devopsdays Amsterdam. We are looking forward to welcoming 300+ attendees, speakers and trainers for three days of interesting sessions in June 2015.
+
+
+
+
+-----
+
+Do you have any thoughts, concerns or ideas you want to share with us? Talk to the organizers!!
diff --git a/exampleSite/content/events/2015-austin/conduct.md b/exampleSite/content/events/2015-austin/conduct.md
new file mode 100644
index 000000000..756ce43e9
--- /dev/null
+++ b/exampleSite/content/events/2015-austin/conduct.md
@@ -0,0 +1,46 @@
++++
+date = "2016-05-02T13:04:01-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+* Email address for organizers: organizers-austin-2015@devopsdays.org
+* Local law enforcement: City of Austin Police - call 911
+* Sexual assault hotline: SafePlace - (512) 267-7233
+* Medical Emergency: Call 911
+* Local taxi company: Yellow Cab Austin - (512) 452-9999, Austin Cab (512) 478-2222
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays Austin is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff t-shirts. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
+
+
diff --git a/exampleSite/content/events/2015-austin/contact.md b/exampleSite/content/events/2015-austin/contact.md
new file mode 100644
index 000000000..e5e47da31
--- /dev/null
+++ b/exampleSite/content/events/2015-austin/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-02T13:04:01-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2015-austin/location.md b/exampleSite/content/events/2015-austin/location.md
new file mode 100644
index 000000000..9dac45191
--- /dev/null
+++ b/exampleSite/content/events/2015-austin/location.md
@@ -0,0 +1,22 @@
++++
+date = "2016-05-02T13:04:01-05:00"
+title = "location"
+type = "event"
+
++++
+
+### Conference location:
+The Marchesa
+http://www.themarchesa.com/
+
+
+FOR GPS or GOOGLE MAPS --> USE ADDRESS 6226 Middle Fiskville Rd. This address will bring you directly to our building, thanks!
+Austin, TX 78752
+(512) 454-2000
+
+
+ View Larger Map
+
+### Food and Drinks Nearby
+Nearby Food
+
diff --git a/exampleSite/content/events/2015-austin/program.md b/exampleSite/content/events/2015-austin/program.md
new file mode 100644
index 000000000..ec8e3a329
--- /dev/null
+++ b/exampleSite/content/events/2015-austin/program.md
@@ -0,0 +1,10 @@
++++
+date = "2016-05-02T13:04:01-05:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
diff --git a/exampleSite/content/events/2015-austin/propose.md b/exampleSite/content/events/2015-austin/propose.md
new file mode 100644
index 000000000..2355abe16
--- /dev/null
+++ b/exampleSite/content/events/2015-austin/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-02T13:04:01-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2015-austin/sponsor.md b/exampleSite/content/events/2015-austin/sponsor.md
new file mode 100644
index 000000000..23a6fd35c
--- /dev/null
+++ b/exampleSite/content/events/2015-austin/sponsor.md
@@ -0,0 +1,64 @@
++++
+date = "2016-05-02T13:04:01-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+We greatly value sponsors for this open event. If you are interested in sponsoring [drop us an email](mailto:organizers-austin-2015@devopsdays.org).
+
+-----
+
+
+
+
Buy Silver
+
+
+
+
Buy Gold
+
+
+
+
Buy Lanyard
+
+
+
+
Buy Happy Hour
+
+
+
+
+
+
+-----
+
+Download the Sponsor Guide
+
+DevOpsDays is a self-organizing conference for DevOps practitioners that depends on your sponsorships to happen. However, because of the nature of the event, we do not have vendor booths or book product pitches.
+
+Attendees, including sponsors, will have the opportunity to host a 5 minute product demo as part of an open space session during the program.
+
+Gold sponsors do get a table they can hang out at and put materials on for interested people to come visit during breaks, and of course all attendees are welcome to propose any subject they want during the openspaces, but this is not 'that kind of conference' and heavy marketing will probably work against you when trying to make a good impression on the attendees. The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
diff --git a/exampleSite/content/events/2015-austin/welcome.md b/exampleSite/content/events/2015-austin/welcome.md
new file mode 100644
index 000000000..65a44ace8
--- /dev/null
+++ b/exampleSite/content/events/2015-austin/welcome.md
@@ -0,0 +1,24 @@
++++
+date = "2016-05-02T13:04:01-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2015-austin"]
+
++++
+
+
+
+
+If you want to be the first to know [subscribe to the devopsdays mailinglist](http://groups.google.com/group/devopsdays)
diff --git a/exampleSite/content/events/2015-bangalore/conduct.md b/exampleSite/content/events/2015-bangalore/conduct.md
new file mode 100644
index 000000000..647891523
--- /dev/null
+++ b/exampleSite/content/events/2015-bangalore/conduct.md
@@ -0,0 +1,41 @@
++++
+date = "2016-05-02T13:21:47-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+* Email address for organisers: organizers-bangalore-2015@devopsdays.org (*fr* & *en*)
+
+
+## ANTI-HARASSMENT POLICY
+
+Devopsdays Bangalore is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organisers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualised images, activities, or other material. Booth staff (including volunteers) should not use sexualised clothing/uniforms/costumes, or otherwise create a sexualised environment.
+
+If a participant engages in harassing behavior, the conference organisers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at Devopsdays, learning from and sharing with other Devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to Devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the Devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the Devopsdays event organisers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organisers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the Devopsdays organisers and attendees will co-create the best possible experience for everyone involved, as I will. I believe Devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organisers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2015-bangalore/contact.md b/exampleSite/content/events/2015-bangalore/contact.md
new file mode 100644
index 000000000..eba31cde7
--- /dev/null
+++ b/exampleSite/content/events/2015-bangalore/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-02T13:21:47-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: [team@devopsdaysindia.org](mailto:team@devopsdaysindia.org)
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2015-bangalore/location.md b/exampleSite/content/events/2015-bangalore/location.md
new file mode 100644
index 000000000..63f2c833b
--- /dev/null
+++ b/exampleSite/content/events/2015-bangalore/location.md
@@ -0,0 +1,31 @@
++++
+date = "2016-05-02T13:21:47-05:00"
+title = "location"
+type = "event"
+
++++
+## Conference location
+
+Venue: Hotel Royal Orchid
+Address: [Old Airport Road, Bangalore](https://goo.gl/maps/ifbou)
+
+## Travel
+
+### Air
+Bangalore is major south indian hub. All major world carriers and alliances operate (often multiple) daily flights.
+
+* [Bangalore International Airport (BLR)](https://goo.gl/maps/2nxMA)
+
+To get to city there are air conditioned buses or radio taxis outside airport.
+
+### Rail
+
+Bangalore has good connectivity for railways as well, please visit [IRCTC](http://irctc.co.in)
+
+
+### Public Transportation
+Bangalore has good public transport - there are buses and metro rails to major part of city connectivity.
+
+## Accommodation
+There are 4 hotels nearby venue - which are 4 - 5 stars, but Indiranagar and Domlur also provide good accomodation. Royal orchid has India Hotel in neighbouring diamond district for comfortable stay.
+
diff --git a/exampleSite/content/events/2015-bangalore/program.md b/exampleSite/content/events/2015-bangalore/program.md
new file mode 100644
index 000000000..a97e895e9
--- /dev/null
+++ b/exampleSite/content/events/2015-bangalore/program.md
@@ -0,0 +1,15 @@
++++
+date = "2016-05-02T13:21:47-05:00"
+title = "program"
+type = "event"
+
++++
+
+## Language
+
+All of the presentations will be held in *English*. Open spaces are participant-lead, and as such, occur in whatever language the particular group is comfortable with. For more information about open spaces, click here!
+
+This year DevOpsDays will have special containers theme dedicated for second day.
+
+For more information please visit [DevOpsDaysIndia](http://devopsdaysindia.org)
+
diff --git a/exampleSite/content/events/2015-bangalore/propose.md b/exampleSite/content/events/2015-bangalore/propose.md
new file mode 100644
index 000000000..60b6cf17f
--- /dev/null
+++ b/exampleSite/content/events/2015-bangalore/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-02T13:21:47-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2015-bangalore/sponsor.md b/exampleSite/content/events/2015-bangalore/sponsor.md
new file mode 100644
index 000000000..f6d3ed744
--- /dev/null
+++ b/exampleSite/content/events/2015-bangalore/sponsor.md
@@ -0,0 +1,8 @@
++++
+date = "2016-05-02T13:21:47-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+We greatly value sponsors for this open event. If you are interested in sponsoring [drop us an email](mailto:team@devopsdaysindia.org).
diff --git a/exampleSite/content/events/2015-bangalore/welcome.md b/exampleSite/content/events/2015-bangalore/welcome.md
new file mode 100644
index 000000000..4069c9825
--- /dev/null
+++ b/exampleSite/content/events/2015-bangalore/welcome.md
@@ -0,0 +1,33 @@
++++
+date = "2016-05-02T13:21:47-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2015-bangalore"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+ {{< event_logo >}}
+
+
+The 4th Devopsdays in India will take place on 12-13th September 2015 at the [Royal Orchid](location).
+
+## Sponsorship
+Sponsorship Opportunities are still available please visit [DevOpsDays India](http://devopsdaysindia.org)
+
+## Tickets
+
+Please purchase tickets [here](https://www.townscript.com/devopsdays-2015)
+
+## Language
+
+All of the presentations will be held in *English*.
+
+For more information, you can reach us at team@devopsdaysindia.org
+
+## More information
+
+Please visit [DevOpsDays India](http://devopsdaysindia.org) for more and upto date information
+
diff --git a/exampleSite/content/events/2015-berlin/conduct.md b/exampleSite/content/events/2015-berlin/conduct.md
new file mode 100644
index 000000000..177944dac
--- /dev/null
+++ b/exampleSite/content/events/2015-berlin/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-02T13:22:22-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2015-berlin/contact.md b/exampleSite/content/events/2015-berlin/contact.md
new file mode 100644
index 000000000..1784ef5be
--- /dev/null
+++ b/exampleSite/content/events/2015-berlin/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-02T13:22:22-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2015-berlin/location.md b/exampleSite/content/events/2015-berlin/location.md
new file mode 100644
index 000000000..0dee1bfd8
--- /dev/null
+++ b/exampleSite/content/events/2015-berlin/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-05-02T13:22:22-05:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2015-berlin/program.md b/exampleSite/content/events/2015-berlin/program.md
new file mode 100644
index 000000000..53f43efdf
--- /dev/null
+++ b/exampleSite/content/events/2015-berlin/program.md
@@ -0,0 +1,170 @@
++++
+date = "2016-05-02T13:22:22-05:00"
+title = "program"
+type = "event"
+
++++
+
+
diff --git a/exampleSite/content/events/2015-berlin/sponsor.md b/exampleSite/content/events/2015-berlin/sponsor.md
new file mode 100644
index 000000000..599304a44
--- /dev/null
+++ b/exampleSite/content/events/2015-berlin/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-05-02T13:22:22-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2015-berlin/welcome.md b/exampleSite/content/events/2015-berlin/welcome.md
new file mode 100644
index 000000000..b01adea33
--- /dev/null
+++ b/exampleSite/content/events/2015-berlin/welcome.md
@@ -0,0 +1,49 @@
++++
+date = "2016-05-02T13:22:22-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2015-berlin"]
+
++++
+
If you spend most of your time in places like Portland or Brooklyn, our metro will feel familiar,
+with its bike share stations, beautiful riverfront, and numerous craft brewery tap-rooms with food
+trucks in their parking lots. (Hey, a good excuse to come the weekend before!)
The value of micro services, containers, and continuous deployment is powerful only when brought together in a logical, scalable and platform agnostic manner.
+
Moreover, when used in the wrong way, it is fairly easy to shoot your self (and your entire application) in the foot. For eg: Micro services can be used to either create unnecessary pockets of redundancy, or used to isolate functionality and directly be an ally of efficient continuous deployment. I have seen more incorrect usages of containers and micro services than I’d like to admit, and a few key components are frequently left out of the cloud-native architecture while starting down this path.
+
Using the micro service paradigm is not a panacea for all problems, because one is creating a large-scale distributed cluster, in essence. Another aspect that is frequently neglected is large-scale containerized search in a cloud-native environment, a governance model around micro services and cloud orchestration. For instance, API frameworks like swagger.io enhance the usability of micro services by documenting the API functionality in real-time alongside the API contract. A micro service is only as useful as the interface contract that it has with other services in the application eco system.
+
Based on my experience over multiple cloud deployments, I will share a collection of anti-patterns and best practices to build production-ready cloud-native applications.
+
“If you can’t explain it to a six year old, you don’t understand it yourself.” - Albert Einstein
+
As someone who has to explain complex technology for a living, I live by this quote every day.
+
I'm a software engineer by training, and a cloud architect by trade. I work closely with Fortune 100 customers at Pivotal, guiding them towards a cloud native architecture, helping them build the next generation of Internet-of-Things (IoT) applications, and doing all this in a scalable way using technologies like Cloud Foundry, In-memory data technologies, and application architecture paradigms like micro services, setting up continuous deployment pipelines, and making the product reach the customer quickly.
In a world where our systems are becoming more distributed then ever due to growing trends to decouple systems into small services, we are becoming dependent on network communication between these services to be reliable. But as we all know the number one fallacy of distributed computing is that the network is reliable.
+
Armed with this knowledge, we know that things will fail. So we must do our best to expect that failure will occur anywhere and everywhere. Thus, let's explore different techniques we can use to build antifragile systems, that degrade gracefully when the network fails and the services we depend on are no longer available.
+
Dan Riti is a software engineer at AppNeta, where his focus is on tracing distributed web applications. Additionally, Dan enjoys Python, Javascript, and music with a lot of bass.
Over the past few years, massive open online courses (MOOCs) powered by Open edX have become wildly popular, bringing free or low-cost education to millions of students around the world. Such success, however, presents a slew of challenging problems in terms of providing a scalable, robust, and secure platform.
+
At Appsembler, we offer customers a fully managed and supported Open edX stack, all the way from the frontend web application to the backend services like ElasticSearch, MySQL, and MongoDB. With so many moving parts, we have come to realize the value of a multi-container, microservices-oriented architecture using Docker.
+
In contrast to a single-container deployment of the Open edX stack, a multi-container approach allows us to scale different services independently; improves robustness since we can simply spin up new copies of containers if they go down; and results in improved security through greater segmentation and isolation. In addition to discussing these benefits, we'll also cover how we're managing deployments using Kubernetes for orchestration and service discovery along with Google Cloud infrastructure.
+
Nate Aune is a developer and entrepreneur with over 15 years of professional experience building highly scalable web applications. Nate is also the founder and CEO of Appsembler. Morgan Robertson is a DevOps Engineer at Appsembler with experience in Docker, Ansible, Python, and automation tools.
DevOps does not exist in a vacuum; social structure and culture are inherently intertwined. The hierarchies within organizations, industry connections, and globalization influence culture. Culture influences social structures, impacting how effective some structures are in an environment with a specific culture. Tools can play a large part in instilling behaviors, automation of systems, sharing knowledge, and changing organizational hierarchies.
+
Often technology choices are framed as 'best practices' or the right way to solve a problem. How do we resolve the cognitive dissonance that arrises from this fixed mindset, having chosen the best practice and the need to handle change as problems evolve? As technology accelerates our work, how do we determine what tools and technology to adopt to help effect the right change? This talk will help you frame the choices available to you, identify the fragility in your environment disguised by tools now, and to be more effective and deliberate with technology in your organization.
What can Women’s Tackle Football teach us about building successful software delivery organizations? As it turns out, quite a bit. This presentation will explore how women’s football teams instill the same cultural principles needed to create agile, competitive organizations. We’ll even teach you some techniques based on the methods of winning football teams. Specifically, we will cover how to affect two key features of successful football teams that we can leverage to implement effective DevOps: Specialization and Mission Focus.
+
Breaking Down the Walls: Silos vs Specialization
+
Specialization is one of the key features of building an efficient and profitable product. But often specialization gets confused with – and devolves into – breaking the organization into silos. Being able to maximize the benefits of specialized roles and talents while promoting shared ownership requires a cultural shift. We’ll explore how many women’s football players and coaches have overcome this challenge and how those lessons can be applied to software delivery.
+
Why Are We Here: Mission Focus
+
Ask any football player why they came to the field on any given game day and they will all tell you the same thing: to win the game. In software delivery, the answer to that question can be as varied as the people answering it. While it’s important to have individual and short-term goals, the team must be focused on the same overall mission in order to accomplish it: no one builds agile software or agile infrastructure by accident. The balance between these goals and the ability to define the primary mission of the team is one of the most important cultural lessons we can learn from successful football teams.
+
Katie Rose is a uniquely experienced developer, football player, and comedian. After 15 years in IT Operations and Service Delivery she is now a web developer for GridIronOps, Booz Allen Hamilton’s open-source, DevOps-driven software delivery platform. She uses her eclectic background to foster the cultural changes that produce competitive organizations and effective teams. Building on her experience in Performance Management and ITIL-based IaaS delivery, she is developing methods and principles that can help organizations bridge the gap between people and tools/process.
Given the DevOps buzz these days and many organizations struggling to get DevOps ingrained in the process, I would like to share how we have introduced DevOps, the challenges we faced and ideas on how those challenges can be overcome. How is it relavant to QA and DBA teams. How can QA be part of DevOps seamlessly. Focus will be more on how QA teams should take automation testing of an unstable product as an opportunity rather than a blocker. Given DevOps team structures, teams are now more product silo'd. Contract testing in Microservices is key to have a successful DevOps team in an organization.
+
Vijaya Kokkili is a QA Manager at CommerceHub, where her team is responsible for the quality of CommerceHub's external and internal applications. Building the automation from ground up at CommerceHub, she has stumbled upon every issue that you can think of, in the software testing and automation world. 'Automation is a learning experience' is the philosophy she believes in. Teams at CommerceHub have gone through several challenges of DevOps and they came a long way overcoming those challenges. Vijaya would like to take this opportunity to share the kind of challenges an organization will go through when DevOps teams are structured and also want to share few ideas that can be put in place from a process perspective that can help other organizations. This talk will be not be focused on general DevOps challenges, but, more on operations teams (DBA, IT, Technical support...) challenges in a DevOps structured team.
If we think of git as a way to track changes to text files, we apply this to code every day. Network device configurations, either Cumulus Linux or Cisco IOS, are simply 1 or more text files. If I need to make a change to the network it's the same as making a change to code. Branch off for your change to add a new VLAN or access control list, make the changes and propose a pull request to provide an opportunity to have senior engineers review those changes or tie it to virtual environments and tools like Jenkins to do further validation of your change. It's not really rocket science, but more of showing two different silos how the other side lives.
+
Pete Lumbis is a data center network architect for Cumulus Networks where he helps customers design data centers of all sizes while applying DevOps principals to networking. Before working at Cumulus, Pete was the routing protocols escalation engineer for the global Cisco support organization. Pete is CCIE #28677 and CCDE 2012::3.
Software and Application development are not slowing down... can your application security efforts keep pace? With agile development, continuous deployment, DevOps, and Cloud the pace of change in the software industry has only increased. Application security professionals face the prospect of rapidly delivering services while simultaneously ensuring that these applications are built both reliably and securely. With deployments deploying sometimes several times a day, weeklong security assessment just do not work anymore.
+
In this talk, I will discuss ways in which the DevOps philosophy can be utilized in application security. What are the key ways to keep your application security program robust enough to maintain relevance in today’s ever-changing environment? This talk will highlight methods for securing infrastructure, apps, APIs and source code.
+
Edward Ray is a Security Solutions Architect at Rackspace, possessing a deep background in Information Security. Ed has provided provided security management and technical leadership as well as performed hundreds of vulnerability assessments, penetration tests, host security reviews, web application assessments and security infrastructure reviews for corporate and governmental agencies in the U.S. and abroad. He has also written articles and technical papers on security and presented to audiences worldwide on computer and network security. In addition, Ed has also provided technical and management consulting on information security incident investigations and forensic analysis.
Real innovation in Healthcare comes from people with lived experience and knowledge of the latest research. Current state of practice in healthcare is a decade or more behind. We need to make it easier for small companies to bring current research and modern technology into healthcare related services - costly regulations like HIPAA scare off most small teams. This is an experience report from 3 years working on a SaaS application that people to use with their psychiatrist (CommonGround). I will cover what works, what doesn't, ways to save money on compliance, and what we can all do to lower the cost of running applications securely. This talk should be interesting for anyone that cares about safeguarding customer data.
+
I'm Elliot Murphy, I want to speak to raise awareness of how security and regulatory issues affect innovation in critical sectors such as healthcare. I currently work at Kindly Ops, but this talk is based on my experiences over the last 3 years as the CTO of a bootstrapped healthcare startup: www.patdeegan.com/commonground
In this workshop, we will explore the value of Kibana 4 for log analysis and will give a real live, hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. We will examine three use cases: IT operations, business intelligence, and security and compliance. This is a hands-on session which will require participants to bring their own laptops, and we will provide the rest.
+
Asaf Yigal is co-founder and VP of Product at log analytics software company Logz.io. In the past, he was co-founder of social-trading platform Currensee, which was later acquired by OANDA. Yigal was also an early employee of server performance-monitoring company Akorri and storage resource-management startup Onaro, both of which were acquired by NetApp (NTAP). Yigal graduated from the Techion -- the Israeli version of MIT -- and he later created an AI algorithm on naval warfare for the Israeli military.
+
Asaf has an extensive presentation experience at both international conferences and local Meetups. Asaf created and gave training programs while he was at Onaro and Akorri and has frequently participated in financial panels in London hosted by the company Finance Magnates. Currently, Asaf presents at at the Tel Aviv ELK meetup and the Boston Elasticsearch meetup.
+
+Email the organizers - {{< email_organizers >}}
+
+
+
+
On Tuesday, September 15th and Wednesday, September 16th, DevOpsDays is returning to Boston!
+
+
The event's schedule will consist of a mixture of traditional sessions, ignite talks,
+and the unique "open space" format that DevOpsDays is known for. We've reserved the first floor of the Microsoft NERD Center
+ and expect to fill it to capacity.
+
+
NOTE: Microsoft has been extremely generous in providing us access to their private space to
+host this event. To repay their generosity, we ask that you pay attention to their guidelines.
+Most importantly, you must present identification to sign into the building! If you don't bring
+identification on the day of the event, you will not be permitted to attend.
+
+
+
+
+
diff --git a/exampleSite/content/events/2015-minneapolis/conduct.md b/exampleSite/content/events/2015-minneapolis/conduct.md
new file mode 100644
index 000000000..29c1e765d
--- /dev/null
+++ b/exampleSite/content/events/2015-minneapolis/conduct.md
@@ -0,0 +1,43 @@
++++
+date = "2016-05-02T13:06:12-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+* Local law enforcement: City of Minneapolis Police - call 911
+* Sexual assault hotlines: Sexual Violence Center (612) 871-5111; Rape and Sexual Abuse Center (612) 825-4357
+* Medical Emergency: Call 911
+* Local taxi companies: Viking Airport Taxi (952) 927-0000; Reli-a-Car Transportation (612) 333-6363
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2015-minneapolis/contact.md b/exampleSite/content/events/2015-minneapolis/contact.md
new file mode 100644
index 000000000..b7d59cda2
--- /dev/null
+++ b/exampleSite/content/events/2015-minneapolis/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-02T13:06:12-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2015-minneapolis/location.md b/exampleSite/content/events/2015-minneapolis/location.md
new file mode 100644
index 000000000..7c0c6c167
--- /dev/null
+++ b/exampleSite/content/events/2015-minneapolis/location.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-02T13:06:12-05:00"
+title = "location"
+type = "event"
+
++++
+
+
+The conference will take place Wednesday July 8 and Thursday July 9, 2015 at the downtown Minneapolis Hilton. We have a room rate of $169/night for those who'd like to stay at the Hilton.
+
+
+The recommended way to travel between the airport and downtown Minneapolis is via the light rail train to Nicollet Mall station. You can walk (under a mile), transfer to a free bus on the bus/bike/pedestrian Nicollet Mall in downtown, or take a short cab ride from the LRT. Uber & Lyft are also available, as is car2go.
+
+
+If you spend most of your time in places like Portland or Brooklyn, our metro will feel familiar, with its bike share stations, beautiful riverfront, and numerous craft brewery tap-rooms with food trucks in their parking lots.
+
+
diff --git a/exampleSite/content/events/2015-minneapolis/program.md b/exampleSite/content/events/2015-minneapolis/program.md
new file mode 100644
index 000000000..aeffc1006
--- /dev/null
+++ b/exampleSite/content/events/2015-minneapolis/program.md
@@ -0,0 +1,151 @@
++++
+date = "2016-05-02T13:06:12-05:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+Call for proposals is now closed.
+Selected proposals will be announced by the 1st of May.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
diff --git a/exampleSite/content/events/2015-minneapolis/registration.md b/exampleSite/content/events/2015-minneapolis/registration.md
new file mode 100644
index 000000000..f60acfef6
--- /dev/null
+++ b/exampleSite/content/events/2015-minneapolis/registration.md
@@ -0,0 +1,11 @@
++++
+date = "2016-05-02T13:06:12-05:00"
+title = "registration"
+type = "event"
+
+
++++
+
+Go to devopsdays Minneapolis registration for 2016.
+
+
diff --git a/exampleSite/content/events/2015-minneapolis/sponsor.md b/exampleSite/content/events/2015-minneapolis/sponsor.md
new file mode 100644
index 000000000..c9de9c0b9
--- /dev/null
+++ b/exampleSite/content/events/2015-minneapolis/sponsor.md
@@ -0,0 +1,50 @@
++++
+date = "2016-05-02T13:06:12-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+
+Go to devopsdays Minneapolis sponsorship for 2016.
+
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please check out our prospectus and drop us an email: {{< email_organizers >}}.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold Medal sponsors get a full table and Silver Lake sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Stone Arch SOLD OUT
+
Silver Lake SOLD OUT
+
Gold Medal SOLD OUT
+
+
+
2 included tickets
+
logo on devopsdays minneapolis event website
+
logo on shared slide, rotating during breaks
+
logo on all email communication
+
logo on its own slide, rotating during breaks
+
1 minute pitch to full audience (including streaming audience)
+
2 additional tickets (4 in total)
+
4 additional tickets (6 in total)
+
shared table for swag
+
booth/table space
+
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, ?subject=Sponsor devopsdays <%= @eventid %>">send us an email.
+
+
+
+DevOpsDays Minneapolis 2015 was Wednesday & Thursday July 8-9, 2015. It was held at the {{< event_link page="location" text="downtown Minneapolis Hilton" >}}.
+
+You can view the DevOpsDays Minneapolis 2015 {{< event_link page="program" text="program of 30-min talks & Ignites" >}}.
+
+
+{{< event_link page="contact" text="Email the organizers" >}}.
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2015-ohio/conduct.md b/exampleSite/content/events/2015-ohio/conduct.md
new file mode 100644
index 000000000..0c6b9411c
--- /dev/null
+++ b/exampleSite/content/events/2015-ohio/conduct.md
@@ -0,0 +1,37 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "conduct"
+type = "event"
+draft = false
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2015-ohio/contact.md b/exampleSite/content/events/2015-ohio/contact.md
new file mode 100644
index 000000000..c2bedd855
--- /dev/null
+++ b/exampleSite/content/events/2015-ohio/contact.md
@@ -0,0 +1,18 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "contact"
+type = "event"
+draft = false
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2015-ohio/location.md b/exampleSite/content/events/2015-ohio/location.md
new file mode 100644
index 000000000..c9bc398c9
--- /dev/null
+++ b/exampleSite/content/events/2015-ohio/location.md
@@ -0,0 +1,19 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "location"
+type = "event"
+draft = false
+
++++
+
+
+ The Bluestone located at 583 E. Broad St. Columbus, Ohio 43215.
+
+
+ Hotel and parking information can be found at the Bluestone website here.
+
+Mallika Iyer - Cloud Anti-Patterns: Micro services, Containers and Large Scale Search gone wrong
+
+
+
11:10-11:20
+
+Sponsors
+
+
+
11:20-11:50
+
+Fred Hatfull - Humans by the Hundred
+
+
+
11:50-13:00
+
Lunch (catered)
+
+
13:00-13:30
+
Ignites
+1) Adam Luck - Automating Threat Detection and Intelligence
+
+2) Monica McJunkin - Driving DevOps with Data
+
+3) Mike Sandman, Dan McSorley and Adam Kentosh - Zero effort developer on-boarding
+
+4) Rob Kinyon - Questions to ask Operations
+
+
+
13:30-14:00
+
Open Space (Open Space) Open Space Opening
+
+
14:00-14:45
+
Open Space (Open Space) Open Space #1
+
+
15:00-15:45
+
Open Space (Open Space) Open Space #2
+
+
16:00-16:45
+
Open Space (Open Space) Open Space #3
+
+
16:45-17:00
+
Close Day & Logistics
+
+
17:00-late
+
Evening Event
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
08:00-09:00
+
Registration, Breakfast, and Sponsor Booths Open
+
09:00-9:15
+
Opening Welcome
+
09:15-09:45
+
+Courtney Kissler - Nordstrom - Vice President of E-Commerce and Store Technologies - "Transforming to a Culture of Continuous Improvement"
+
+
09:45-09:55
+
+Sponsors
+
+
09:55-10:25
+
+Dustin Collins - Human Error and Secure Systems
+
+
10:25-10:40
+
+Break
+
+
+
10:40-11:10
+
+Kelly Looney - The DevOps Journey in Real Money Gaming
+
+
+
11:10-11:20
+
+Sponsors
+
+
+
11:20-11:50
+
+JP ODonnell - DBAs and DEVs, we really can be friends
+
+
+
11:50-13:00
+
Lunch (catered)
+
+
13:00-13:30
+
Ignites
+1) Matt Williams - The Three R's of DevOps
+
+2) Justin Kuss - Dos and Don'ts for Raising Cattle In Your Data Centers
+
+3) Mike Sandman, Dan McSorley and Adam Kentosh - 12-factor assessment in 5 minutes (working title)
+
+4) Gene Pavell - Change Management Does Not Have To Be Horrible
+
+
+
13:30-14:00
+
Open Space (Open Space) Open Space Opening
+
+
14:00-14:45
+
Open Space (Open Space) Open Space #1
+
+
15:00-15:45
+
Open Space (Open Space) Open Space #2
+
+
16:00-16:45
+
Open Space (Open Space) Open Space #3
+
+
17:00
+
Close Day & Farewell
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2015-ohio/propose.md b/exampleSite/content/events/2015-ohio/propose.md
new file mode 100644
index 000000000..0bff5bc60
--- /dev/null
+++ b/exampleSite/content/events/2015-ohio/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-02T13:23:02-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2015-ohio/sponsor.md b/exampleSite/content/events/2015-ohio/sponsor.md
new file mode 100644
index 000000000..eeda8587e
--- /dev/null
+++ b/exampleSite/content/events/2015-ohio/sponsor.md
@@ -0,0 +1,16 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "sponsor"
+type = "event"
+draft = false
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+Details on the different sponsorship levels can be found in the Sponsorship Prospectus found
+here.
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
diff --git a/exampleSite/content/events/2015-ohio/welcome.md b/exampleSite/content/events/2015-ohio/welcome.md
new file mode 100644
index 000000000..8edd8d24a
--- /dev/null
+++ b/exampleSite/content/events/2015-ohio/welcome.md
@@ -0,0 +1,115 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2015-ohio"]
+draft = false
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
DevOpsDays Ohio 2015
+ {{< event_logo >}}
+
+
+
+
+ Thank you to the participants, speakers, vendors, and organizers for making the 2015 Ohio DevOpsDays
+ event a
+ great success!
+
+ Special thanks to our partners COHAA for helping organize this event, in addition to providing highlights for the event to share!
+
+
+
+
+ We are in the midst of gathering the slides from the presenters, listed below. If we do not have your
+ slides yet, please
+ email them to the
+ organizers
+
+
+
+ From fledgling startups to established industry, the Midwest is home to a large, vibrant technology
+ community. Ohio in particular has been a flurry of activity in the past several years, drawing attention
+ from around the globe.
+
+ DevOpsDays Ohio will bring 300+ development, infrastructure, operations, InfoSec, management and
+ leadership professionals together to discuss the culture and tools to make better organizations and
+ products.
+
+ The event's schedule will consist of a mixture of single-track presentations, Ignite Talks, and the
+ "open space" format that DevOpsDays is known for.
+
+ We're thrilled to announce two of our keynote speakers:
+
+
Carmen DeArdo - Nationwide Insurance - Build Technology Leader - - "The Nationwide DevOps
+ Journey"
+
+
Courtney Kissler - Nordstrom - Vice President of E-Commerce and Store Technologies -
+ "Transforming to a Culture of Continuous Improvement"
+
+
+
+ Please contact us if you'd like to sponsor the event! It's a
+ great way to promote your organization.
+
+ If you are interested in joining the planning committee or have general questions, feel free to
+ email the organizers.
+
+
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/conduct.md b/exampleSite/content/events/2016-amsterdam/conduct.md
new file mode 100644
index 000000000..05fd5da52
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/conduct.md
@@ -0,0 +1,40 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+heading = "devopsdays Amsterdam - Code of Conduct"
+title = "Code of Conduct"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-amsterdam/contact.md b/exampleSite/content/events/2016-amsterdam/contact.md
new file mode 100644
index 000000000..265124741
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+heading = "devopsdays Amsterdam - Contact"
+title = "Contact"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-amsterdam/location.md b/exampleSite/content/events/2016-amsterdam/location.md
new file mode 100644
index 000000000..8f1034247
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/location.md
@@ -0,0 +1,47 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+heading = "devopsdays Amsterdam - Event Location"
+title = "Event Location"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+
+### Conference Location
+
+The conference is located at [Pakhuis de Zwijger](http://www.dezwijger.nl/ "Website of Pakhuis de Zwijger")
+
+Piet Heinkade 179
+1019 HC Amsterdam
+The Netherlands
+
+
+
+## Getting there and accommodation
+
+### Transportation
+
+Amsterdam has a fantastic public transportation system.
+- Buses [48](http://maps.gvb.nl/en/lijnen/48), [246](http://maps.gvb.nl/en/lijnen/246) and [759](http://maps.gvb.nl/en/lijnen/759) stop right in front of the conference.
+- Tram [26](http://maps.gvb.nl/en/lijnen/26), departing from Amsterdam Centraal Station (main train station in the city).
+
+More information can be obtained by using the [GVB](http://en.gvb.nl/) or [9292](http://9292.nl/en) websites. Both have excellent apps in the iOS ([GVB](https://itunes.apple.com/nl/app/gvb/id370393784) & [9292](https://itunes.apple.com/nl/app/9292/id556557690)) and Google Play ([GVB](https://play.google.com/store/apps/details?id=nl.moopmobility.gvb&hl=en)) & [9292](https://play.google.com/store/apps/details?id=nl.negentwee&hl=en)) store. Other apps (like Google Maps) have great integration as well.
+
+##### A note to out of towners in in regards to obtaining a reloadable card for public transportation.
+
+You can purchase an "OV chipkaart" at Amsterdam Centraal and most large metro stations (including Schiphol). Note that the unattended machines do not handle non-EU issued (e.g. Chip+Signature) cards well. Some U.S. Credit Unions now offer Chip+Pin technology on their *debit* card (note: not *credit* card). If your card doesn't work or want to use Euros (other than coins), there is a customer service center located on the "IJ side" of Amsterdam Centraal where you can purchase a chipkaart in person at the [Service Office](https://www.nsinternational.nl/en/tickets-services/opening-hours-ticket-and-service-shops "Link to NS International Service Office"). If you're arriving via Schiphol - a similar service is offered in the main train hall
+
+#### Alternative methods of transportation
+- [Uber](https://www.uber.com/)
+- [Rent A Bike](http://www.iamsterdam.com/en/visiting/plan-your-trip/getting-around/rental/bike-hire)
+- And if you want must -- [Taxis](http://www.iamsterdam.com/en/visiting/plan-your-trip/getting-around/taxis)
+
+
+### Accommodations
+Amsterdam has amazing hotels and incredible amount of Airbnbs spread out all over the city that allows you to experience life as an Amsterdammer (Beware of the dark red bike paths!). Besides Airbnbs, here is a list of hotels that are near to the [Pakhuis de Zwijger](http://www.dezwijger.nl/ "Website of Pakhuis de Zwijger").
+
+* [Mövenpick Hotel Amsterdam City Centre](http://www.movenpick.com/en/europe/netherlands/amsterdam/hotel-amsterdam/overview/)
+* [DoubleTree by Hilton Hotel Amsterdam Centraal Station](http://doubletree3.hilton.com/en/hotels/netherlands/doubletree-by-hilton-amsterdam-centraal-station-AMSCSDI/index.html)
+* [Hotel NH Barbizon Place](http://www.nh-hotels.nl/hotel/nh-collection-amsterdam-barbizon-palace)
+* [Inntel Hotels Amsterdam Centre](http://www.inntelhotelsamsterdamcentre.nl/)
diff --git a/exampleSite/content/events/2016-amsterdam/program.md b/exampleSite/content/events/2016-amsterdam/program.md
new file mode 100644
index 000000000..418e79b59
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/program.md
@@ -0,0 +1,559 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+heading = "devopsdays Amsterdam - Program"
+title = "Program"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+
+
+
+
+
+
+
+ The Workshops have their own section this year! Please click here for the 29 June schedule!
+
+
+
+
+
+
+
+
+
+ With talks in the morning and Attendee Driven Open Space breakout discussions in the afternoon, we have two full days of content!
+
+
+
+
+
+
+
+
+
+
The Program
+
+
+
+
+
+
+
+
+
+
30 June - Thursday
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
We often hear talks of "scale" and "reliability", mostly based on personal experience and lessons learned. What can Mathematics tell us about reliability and scale? Can math help us make our systems and companies more reliable?
+ It turns out that failure models, probability, statistics and other domains can help our analysis and provide insights.
+
+
This talk will present a simple failure models, explain the math behind common practices, introduce emergent system properties and showcase mathematical examples of why things behave differently at scale and how things that work well in small systems can be horrible at scale.
Title: Working in and with Open Source Communities
+
+
Description:
+
+
Starting an open source project is very easy, especially in the days of GitHub. Push your code and see if somebody is interested in. If you are able to gain attention and interest for you project you feel motivated and work all night long. But on the other hand, people will start complaining about open bugs, missing features and your evil or non existing website. Believe it or not, but this will pursue you until your last user dies.
+
+
One of the most important things for a successful open source project is to treat you community well. This talk will share some experiences made during the last 6 years with Icinga. Starting with basic concepts, it deals with tools and methods helping to increase and cultivate your community. It also covers internal organisation requirements for successful community work and upcoming challenges if you strike some new paths with your project.
Title: How the hell do I run my microservices in production, and will it scale?
+
+
Description:
+
+
Let's assume you’ve already had every *Docker 101 tutorial* for breakfast. You’re now ready to take that brilliantly crafted application into production. But wait... first you need to test your container-based microservices architecture. What does the whole DevOps workflow look like? What about performance and security? And last but not least; how the hell do I run my microservices in production, and will it scale?
+
+
Let Daniël guide you through the wonderful world of container-based development and running microservice architectures at scale. By attending the talk*, you’ll gain insight into how to bootstrap and dive straight into learning what DevOps workflow should look like when using containers.
With testing late in the software development process, you risk discovering problems at a very late stage. You want to be able to test earlier so that: issues can be fixed earlier, submitted code is checked with every push/merge/build for example. We will tell you our story about what mistakes we made and how we learned to reach towards a continuous testing process.
+ Some key mistakes and learnings we made are related to:
+ - Way of creating tests and test data
+ - Process of executing, maintaining tests and agreements surrounding it
+ - Applicability, evaluation of the tool stack we use(d)
+
+
+
We also learned continuously regarding our test implementation and acted upon these learnings. Therefore, we hope to share our story that others can relate/learn from the pain we suffered before we could enjoy our continuous testing process.
+Although Test driven development is a familiar thing, Test driven infrastructure is not so much. If you are moving to infrastructure-as-code, then it is important to implement the same Test-driven principle to infrastructure, for an automated IaaS delivery pipeline. In the world of containers, we have tools like serverspec and continerspec (which is based on cucumber) to ensure that the containers and images are configured as we want them to be. In this talk we look at how and what can be tested in this way, and the advantages and limitations of the testing methods. Test-driven infrastructure is not that difficult to implement after all.
Some of the very things that make JavaScript awesome can also expose it to security risks. This talk will go through some sample security flaws unique to Node’s async nature and surrounding ecosystem (or especially relevant to it). We'll show how these could occur in your own code or in npm dependencies.
+
+
The talk will revolve around a sample vulnerable application, which we will exploit as an attacker would. For each issue, we'll explain why it happened, show its impact, and – most importantly – see how to avoid or fix it.
Title: One engineer, four environments, no termination policy.
+
+
Description:
+
+
Terminating all environments just days before going live and getting back from scratch. We were days away from going live with our AWS Mesos stack until one unlucky engineer ran a faulty playbook.
+
+
This talk will focus on how we build and operate the new Wehkamp stack. We’ll start at the AWS level where we have several hundred instances, ELB’s and supporting services. On top of those instances we run services like Mesos, Consul, Kafka, ElasticSearch and Cassandra. Our real workload lives on Mesos, the microservices architecture we call Blaze. Next we’ll go over what happened in the days before we flipped the switch to go live, and the steps involved creating everything from scratch. How we utilize ansible and we’ll briefly touch Jenkins as our CI/CD tool. The final words will describe our plans in this area for the near future, and the improvements on what we’ve seen so far.
Title: Workshopping Bias: Designing Solutions to Improve Decision Making and Unleash Your Team's Potential
+
+
This workshop will provide an overview of how our brains process information and how those systems break down. We'll talk about a few specific types of unconscious bias and how they limit the potential of our teams and organizations. Then, participants will have a chance to test themselves and work together to identify subtle improvements to the way they evaluate candidates, direct reports, and their colleagues to interrupt biases where they appear.
+
In 1975, Fred Brooks published The Mythical Man-Month, a book of observations and recommendations for software project management and team collaboration. One of the most enduring statements from the book, often called "Brooks’ Law," states that “adding manpower to a late software project makes it later.
+
+
But Brooks (and nearly all projects in 1975) used Waterfall methodologies. I'll dive deeper into what Brooks' Law means for agile projects and how DevOps practices might nullify it altogether.
Title: You Don't Belong Here: Dealing with Imposter Syndrome
+
+
Description:
+
+
An estimated 70% of people will experience Impostor Syndrome at some point in their lives, despite having objective evidence of success in their field, sometimes in copious amounts. People in all fields of work experience pervasive psychological distress, believing that they are intellectual frauds and fearing being recognized as impostors. The objective of this presentation is to provide relief to those suffering from Impostor Syndrome by analyzing possible sources of this distress, exploring tactics to overcome these feelings, and recognizing that we have a community of peers sharing the same experience. Through scientific research and personal exploration, we'll dig deep into the root causes of this feeling and identify paths to successfully working through moments of Impostorism.
Title: What we’re learning about burnout and how a DevOps culture can help
+
+
Description:
+
+
One of the most overlooked advantages of converting to a DevOps culture can be the reduction of stress. This could be due to “sharing the load” as a whole team, the feeling of joint ownership in solving a business problem, or many other things.
+
+
If you’re asked to support somebody else’s application without any insight to how it was built and what problems it’s trying to solve you’re likely to experience more than a little stress. The same is true if you’ve toiled away creating the perfect application only to see it deployed in a way that makes it unable to perform.
+
+
The combination of stress and burnout is perhaps the biggest health threat in our industry. In fact, recent research has found that burnout--and the related concept of ""vital exhaustion""--increases your risk of cardiovascular disease as much as body mass index, smoking and lipid levels. Unfortunately there are also well-known stories of burnout-related suicides in our industry, making this literally a life and death issue.
+
+
If that isn’t reason enough to address the issue, we also know from the State of DevOps survey that the #1 indicator of company success is job satisfaction.
+
+
In this talk Ken will go over some of the leading research in the area of burnout. We’ll talk about some of the more common causes of burnout as identified by clinical research and talk about how you can learn from organizations with solid DevOps cultural practices to help alleviate them.
As the complexity of software grows - machine learning, big data, container infrastructure - the burden is less on how to get the software, or install the software, but the knowledge it takes to run, maintain, and scale software.
+
+
Open Sourcing operations not only allows us to keep up, but punch up above our weight classes.
Super inspired by last year's DevOpsDays talk, Radically Open Security embraced the concept of ChatOps for security audits and penetration testing - and the results have been nothing short of phenomenal! This talk will introduce the basics of Pentesting ChatOps, and will discuss the processes and open-source tools (RocketChat, Hubot, Gitlab, various pentesting tools) needed to enable Pentesting ChatOps within your own organization.
Title: The importance of ‘why’ for software operations.
+
+
Description:
+
+
When working with multiple software development teams it is important to keep the teams motivated and aligned with each other while still allowing teams’ autonomy. Most architects and product managers try to focus on what needs to be done and how. However it’s more important to pay attention to why the change is needed or why the exact architecture is required. When teams know exactly why the change is needed they can find how to start and continue working without having to constantly align with architects and product management. ‘Why?’ is a hard question in software development. It’s even harder for software delivery. We know why should we automate our pipelines or why programmable infrastructure is better than snowflake server. But each one of use needs to be able to answer why we are doing this from the company mission or from the product ideas perspectives. Then we could link our daily work to something that has higher value.
When we build a software or a Web service, we utilize many static analysis tools such as Lint, CheckStyle or FindBugs. These static code analysis tools help us to write simple code and they improve productivity. Many inspection tools are compatible with CI tools or services . CI services are useful in that they ensure that users follow the coding standard.
+
+
This presentations shows continuous checking of technical documents or software manuals with the combination of common CI services and RedPen. RedPen is an open source document validation tool and check if the input document to adhere to a writing standard. RedPen provides many features useful for writing large document such as support of markup languages (AsciiDoc, Markdown and LaTeX) and the customizability.
Title: Preparing for the Day After Tomorrow - Test-Driven Infrastructure
+
+
Description:
+
+
With infrastructure and application automation, we have gained the tools to change systems rapidly. However, with increased project size, complexity, and requirements, its is very challenging to meet the time and quality expectations. In order to build a high velocity organization, uncertainty and complexity need to be reduced to gain speed while working in a trusted environment. This talk will introduce a DevOps workflow that helps to establish trust in your software development and release process. Moreover, we will look into the management of divergent environments, from legacy systems to modern clouds by using InSpec and Test-Kitchen.
Do you need to secure your leading technology product and business? Are you struggling with aligning your security program to agile and devops? Organizations can be compliant and secure while remaining innovative. This presentation explores innovative processes and practices for evolving traditional security controls. With these techniques, you can securely enable the speed of change needed to disrupt in today's market place while meeting compliance and audit requirements. Warner will explore alternative methods using real world examples for addressing security controls such as separation of duties, change control, and release management using automation and modern practices.
Title: An ElasticSearch Cluster Named George Armstrong Custer
+
+
Description:
+
+
This is the epic tale of an elasticsearch cluster named "Custer", named after the US Calvary Commander.
+
+
+It didn't start out with a name, it started out as our logstash cluster, but after experiencing how easy it was to search and find logs using logstash, our developers took it upon themselves to see what else it could be used for. This was our Battle of Little Big Horn.
+
+
+ In this ignite talk, attendees will laugh and learn as I explain:
+ • the origin of our cluster
+ • how it got it's name
+ • Where things went wrong
+ • Steps we took (good and bad) to deal with daily crashes (a.k.a. Little Big Horn)
+ • Lessons learned on using and scaling elasticsearch
+
+
+
+ Attendees will leave this short, 5 minute talk with the ability to identify the signs and symptoms of an over-utilized cluster. Specific thresholds that proved invaluable to us, such as JVM heap usage, memory utilization, shard movement, and index latency will be shared. They will also learn the tips and tactics on how to recover once a problem cluster is identified.
+
+
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/proposals.md b/exampleSite/content/events/2016-amsterdam/proposals.md
new file mode 100644
index 000000000..d4276c7d6
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/proposals.md
@@ -0,0 +1,16 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+heading = "devopsdays Amsterdam - Proposals"
+title = "Proposals"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-amsterdam/propose.md b/exampleSite/content/events/2016-amsterdam/propose.md
new file mode 100644
index 000000000..843e21655
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/propose.md
@@ -0,0 +1,13 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+heading = "devopsdays Amsterdam - Call for Papers"
+title = "Propose"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+ {{< cfp_dates >}}
+
+
+The call for proposals is closed. Thank you for the many submits we have received! We hope to finish the selection soon and inform you.
diff --git a/exampleSite/content/events/2016-amsterdam/registration.md b/exampleSite/content/events/2016-amsterdam/registration.md
new file mode 100644
index 000000000..9a678df8b
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/registration.md
@@ -0,0 +1,29 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+heading = "devopsdays Amsterdam - Registration"
+title = "Registration"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/andrew-farley.md b/exampleSite/content/events/2016-amsterdam/workshops/andrew-farley.md
new file mode 100644
index 000000000..55c4af7d8
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/andrew-farley.md
@@ -0,0 +1,63 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Introduction to designing scalable services on Amazon’s Web Services"
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/andrew-farley/"]
+
++++
+
+
+
Title: Introduction to designing scalable services on Amazon’s Web Services
+
+
+Amazon offers a wide number of tools to architect scalable services in various ways. I will walk you through creating your first simple autoscaling application via EC2/Autoscaling/RDS. By the end of this workshop, you will have setup your (first?) own autoscaled application on AWS which can scale up, handle load, and tolerate failures and you'll have an understanding of the technologies and tools and methodologies to succeed in using Amazon for autoscaling services.
+
+
+
+I’ll kick the workshop off with one main topic doing this with one common and simple approach. And then based on shared interest and time we’ll cover the optional topics below and/or explore more techniques together. The topics available include…
+
+
+
+Main Topic
+• Creating/modifying an existing application for (auto)scale on AWS (Workshop with EC2, RDS, Cloudwatch Logs, AutoScaling)
+
+
+
+Optional Topics (time permitting and interest-based)
+• Deployment Strategies, Schema Change Strategies with our just-created environment
+• Explanation, demonstration and Q&A discussion of Continuous Delivery/Deployment Strategies and tools and their uses/usage pertaining to AWS
+• Scalable Services on AWS in a healthy DevOps culture (SNS, SQS, AWS Lambda, Slack)
+• Architecting Services without Servers (Workshop with AWS Lambda, NodeJS, Serverless, API Gateway, CloudFront)
+• Insert your other topic here, questions and curiosity is welcome during the workshop!
+
+
+
+To participate in this workshop and to maximize what you can get out of this workshop, you will need…
+• A functional unix-based or unix-friendly computer or VM (or enough skills with windows cygwin to get by)
+• A functional Amazon AWS Account (https://aws.amazon.com)
+• Amazon’s CLI toolkit installed (https://aws.amazon.com/cli/)
+• Amazon’s CLI toolkit configured on your machine (http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-set-up.html)
+• Simple command-line usage abilities (cd, ls, curl, ssh)
+• A general understanding of some of the various technologies and concepts above and/or interest to learn
+• If you want to "dabble" a little bit with Lambda / API Gateway, a basic understanding of programming concepts will be necessary (esp. Python / NodeJS)
+• If we get into trying "serverless" together, you'll need NodeJS v4.x or newer installed
+
+
+
NOTE: This is a beginner-to-intermediate level class. If you're already an experienced sysadmin managing numerous servers for clients, this might not be a class for you unless you have no experience with AWS.
+
+
+In this workshop I will provide…
+• Slides at the start of the chat
+• Demo/Sample API endpoints and code to be used by some of the workshop
+• Various sample codebases and/or tools in various git repositories to be used in the workshop
+• A friendly helpful guide to explore various tools and technologies with you and answer any questions you might have
+
+
+
About the speaker
+
Farley is a Senior DevOps Engineer and consultant for OlinData. He has experience with high-scalability systems both in bare metal and in the cloud for the last 12 years and on AWS for over 6 years now. He's founded a handful of startups and been doing consulting for a wide range of companies in Silicon Valley and around the world. He is passionate about high-scalability and redundant, systems, automation, agile and continuous deployment, documentation, diagramming and open-source software. He has no associations with Amazon other than being a passionate user of their platform and holding an AWS Associate Certification.
+
+
Farley's interests don’t end at managing servers, he's authored and launched over 30 mobile applications, numerous games, he’s launched or been an early employee at a dozen startups, and has years of experience designing and consuming APIs using various languages. And for fun he plays with microelectronics and designs & flies racing quad-copters in his free time.
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/arnold-van-wijnbergen.md b/exampleSite/content/events/2016-amsterdam/workshops/arnold-van-wijnbergen.md
new file mode 100644
index 000000000..83e24cade
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/arnold-van-wijnbergen.md
@@ -0,0 +1,31 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "First steps to create your IT Operations data lake with ELK Stack and Graphite"
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/arnold-van-wijnbergen/"]
+
++++
+
+
+
Title: First steps to create your IT Operations data lake with ELK Stack and Graphite
+
+
+ELK (Elasticsearch-Logstash-Kibana) and Graphite/Grafana are the most popular tools for analyzing your logs and metrics. Almost every company has one of these tools running, with various use cases like big data, analytics or just monitoring.
+
+
+
+In this hands-on workshop the student learns the fundamental skills needed to understand the concepts en start creating their Monitoring configuration.
+Main topics that are covered are setting up your logstash configuration for log parsing, enabling metric gathering with Graphite (i.e. Collectd) and finally create some awesome dashboards.
+
+
+The hands-on workshop is fully scenario based, including helpful lab exercises, sample code and a prepared Vagrant Box running on Linux.
+To run the Vagrant Box in Virtual Box a minimum of 2 GB memory or better is preferred."
+
+
+
About the speaker
+
Arnold van Wijnbergen is an independent advisor, coach and consultant from Devoteam. He specializes in Monitoring and Automation topics to improve quality and efficiency of operational control of IT4IT business. To achieve this he combines Lean principles with DevOps culture, because he strongly believes in the power of culture and self-steering teams. His broad experience in Monitoring and Automation tooling implementations ranges from MKB till enterprise scale, formed mainly in the banking, insurance, governance, retail, telco and service provider branches.
+
At ING he is management consultant within the ING Automate monitoring stream, which is responsible for advising, training and coaching DevOps teams with improving their monitoring capabilities.
+Ansible has taken a prominent place in the configmanagement world. By now many people involved in DevOps have taken a look at it, or done a first project with it. Now it is time to step back and look at quality and craftmanship. Bas Meijer, Ansible ambassador, will talk about Ansible best practices, and will show tips, tricks and examples based on several projects.
+
+
+
About the speaker
+
Bas is a systems engineer and software developer and wasted decades on latenight hacking. He is currently helping out 2 enterprises with continuous delivery and devops.
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/christoph-andreas-torlinsky.md b/exampleSite/content/events/2016-amsterdam/workshops/christoph-andreas-torlinsky.md
new file mode 100644
index 000000000..381e72bb4
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/christoph-andreas-torlinsky.md
@@ -0,0 +1,40 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "A Place for SDN in DevOps"
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/christoph-andreas-torlinsky/"]
+
++++
+
+
+
Title: A Place for SDN in DevOps
+
+
+This workshop will let you bring your own laptop (provided wifi works) and we will download an SDN SDK from the Github at Nuage Networks (https://github.com/nuagenetworks/) and with the SAN box SDN setup on the cloud we will code some primitives using python against the Network, then dump it all into JSON format for further consumption or version control.
+
+
+
+Requirements for the workshop are virtualenv python setup, ability to pypi install the required components for the SDK, and access to the Internet with basic Python working Knowledge.
+
+
+
+The Workshop will detail the Hardware Decoupled architectural drivers for Software Defined Networking along with Restful API components used and consumption of SDN for Continious Delivery."
+
+
+
+By the end of the workshop you will have the understand to see how a Network is translated into Infrastructure as Code for use cases such as Containers or Private Cloud Deployments at Scale and faster Application Delivery
+
Leveraging Nuage SDN APIs, Red Hat OpenStack and Thoughtworks Go for Speedy Application Delivery.
+
+
About the speaker
+
Hello, i work for a Startup called Nuage Networks in EMEA and we are actively trying to change how Software interacts with the Network. Check us out, I've been working for a number of companies prior to Nuage in the Networking and Linux and Operating Space.
Title: Creating high-performance teams with DevOps behavior
+
+
+High-performance teams are NOT the teams with the newest tools or the coolest pipelines. High-performance teams are teams showing ""the right behavior"" every single day.
+
+
+
+But what is this "right behavior" in the DevOps context? And how can you help your team mates in achieving this?
+
+
+
+ And how do you effectively change (read: positively manipulate) the behavior of all the stakeholders in your domain, like your fellow team members, your customers, your manager, or that awful guy from compliancy & risk?
+
+
+
+ This highly interactive workshop will give you real practical instruments, tips & tricks (all based on scientific & practical evidence and experience) how to help truly create a high-performance environment in your organization.
+
+
+
About the speakers
+
Dave van Herpen is management coach (Enterprise Agility & DevOps) at Sogeti Netherlands. In his role as practitioner, coach, trainer and change agent, Dave has been supporting his customers to organize for end-to-end agility for the past 15 years.
+
+
Robert den Broeder is owner of Trigono BV and is a certified trainer / coach in Service Management and Organizational Behavior Management (OBM). Robert supports organizations with implementing and improving service management processes, with special attention for behavioral change.
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/jim-leitch.md b/exampleSite/content/events/2016-amsterdam/workshops/jim-leitch.md
new file mode 100644
index 000000000..f31cccd91
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/jim-leitch.md
@@ -0,0 +1,33 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Like A Rhino in Your Kid Brother's White Tuxedo - Legacy and Awesome is not an Oxymoron"
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/jim-leitch/"]
+
++++
+
+
+
Title: Like A Rhino in Your Kid Brother's White Tuxedo - Legacy and Awesome is not an Oxymoron
+
+
+At night you dream of Microservices, Immutable Infrastructures and Immortal Awesomeness. By day you are looking after Oracle 9 systems on AIX with 32 bit Oracle Forms, due to be retired sometime in the decade after next.
+
+
+This workshop will show you how you can use the fun new techniques that everyone is talking about to boot your legacy enterprise environment to be supplying SelfService for developers and running Continuous Deployment.
+
+
+We'll supply you with your own cloud environment and all the scripts necessary to get a Self Service and CD environment running. To let you see CD in action and to kick the tyres yourself, we'll have an example set of enterprise applications with source code on Windows/ASP.NET, PHP/MySQL and Java/OracleDB. Tools used, in no particular order, are: Terraform, Vagrant, Vault, Jenkins, Chef, Selenium, SonarQube, Nexus, VisualStudio.
+
+
+
+ We'll be eating our own dogfood by booting the complete underlying infrastructure from zero using Terraform and Chef.
+ All you need to bring is a pen, some paper, your laptop and a burning desire to squeeze your enterprise rhino into that small white tuxedo.
+
+
+
About the speaker
+
+
Jim is a family man, guitarist and dog lover. Having lived in the Netherlands for the last 22 years he knows where the best stroopwafels are.
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/karleen-wijsman.md b/exampleSite/content/events/2016-amsterdam/workshops/karleen-wijsman.md
new file mode 100644
index 000000000..992171891
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/karleen-wijsman.md
@@ -0,0 +1,31 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Appreciative Inquiry, the most enjoyable way of change."
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/karleen-wijsman/"]
+
++++
+
+
+
Title: Appreciative Inquiry, the most enjoyable way of change. Small steps for your people, giant leaps for your organization.
+
+
You bought the right tools, you built state of the art pipelines, you hired the right people and you trained their skills. Why do you keep thinking that your teams could perform better? Because that is true in most cases.
+
+
+Why not improve performance and glee at the same time (sometimes more than 50 %)?
+
+
+
+From our research we derived that every DevOps organization occasionally needs a spark to get its teams one or many steps further. This takes even more effort for experienced teams than for starters. The method we use for this is Appreciative Inquiry. It discovers the best practices that work within an organization, the reason they work and how these combined practices can be used to move forward, to move faster and create a strategic change. With Appreciative Inquiry the aim is to build – or even rebuild – organizations around what works, rather than trying to fix what doesn’t. This method creates a flow of positive energy in which change is inevitable.
+
+
+
In this workshop we introduce you to this technique and you will find out that it is the most enjoyable way of change.
+
+
About the speakers
+
Jan de Vries is a senior business IT consultant and a trusted advisor in the fields of requirements engineering, business information management, application management and DevOps. He is a BiSL, ASL, ITIL, ISM and FSM trainer and convenor of the Enterprise DevOps working group that unites members of the ASL BiSL Foundation and the Agile Consortium. He founded Blue Ocean Recon to do research that focuses on Blue Oceans and Lean Startups.
+
+
Karleen Wijsman is an all-round IT Specialist and has many years of experience in providing training and workshops in the field of personal development and organisational change. Her NLP Practitioner and NLP Master background give her a solid foundation to motivate, engage and energize people and organizations
Title: Working with Docker & Microsoft Azure Container Service
+
+
+Docker is taking the world by storm and Microsoft Azure Container Service is where Azure and Docker meet! During this workshop Mark van Holsteijn will give you a brief introduction into Docker and Microsoft Container Service. After which you will have ample opportunity to get hands-on with Docker, Marathon, Azure and ASP.NET core.
+
+
+
We will show you how Azure Container Services provides an excellent platform for creating cross-cloud applications.
+
+
About the speaker
+
+
Mark van Holsteijn is Principal Consultant at Xebia specialized in cloud software architectures with open-source technologies.
+In this workshop you will learn how to get started writing Chef recipes. We will also teach you how to begin the process of doing Test Driven Development with Chef to confirm your recipes work before sharing them with others.
+
+
+
About the speaker
+
Michael Ducy currently works as a Manager for Solutions Architects at Chef focusing on helping companies understand Chef, DevOps, and IT transformation. Previously, Michael focused on designing and implementing automation solutions for customer’s Cloud, IT Automation, and Continuous Delivery needs. Michael has also worked in a variety of roles in his career including Cloud Architecture, Systems Engineering , Performance Engineering, and IT Instructor. Michael holds a Masters in Computer Science from the University of Chicago and an MBA from The Ohio State University.
+With this Icinga 2 workshop you will get an overview of our new monitoring framework. You will gain in-depth inside in the Open Source Monitoring software Icinga, its add-ons as well as the monitoring of modern IT infrastructure. Real life examples and the brand new Icinga Web 2 are also a big part of that workshop.
+
+
+
About the speaker
+
Michael has been an Icinga core developer for more than 7 years. He is currently leading the Icinga 2 development together with Gunnar. In addition to the exciting core architecture work he likes to play with Vagrant. Docker and Dashing. You’ll also find him active over at monitoring-portal.org, most recently as administrator too. In his spare time Michael loves to build LEGO models and enjoys Nuremberg with his Austrian dialect.
+Docker is very popular these days, how many of us are really familiar with the basic building blocks of Linux containers and their implications? What's missing in the good ol’ chroot jails? What are the available Copy-on-Write options and what are their pros and cons? Which syscalls allow us to manipulate Linux namespaces and what are their limitations? How do resource limits actually work? What different behaviors do containers and VMs have?
+
+
+
+In this hands-on workshop, we will build a small Docker like tool from O/S level primitives in order to learn how Docker and containers actually work. Starting from a regular process, we will gradually isolate and constrain it until we have a (nearly) full container solution, pausing after each step to learn how our new constraints behave.
+
+
+
+Pre-Requisites:
+Be sure to read up on the prep material that will give you the necessary background to be successful for this workshop!
+
+
+
+
+
About the speakers
+
Avishai Ish-Shalom is a veteran Ops and a survivor of many production skirmishes. Avishai helps companies deal with web era operations and scale as an independent consultant. In his spare time Avishai is spreading weird ideas and conspiracy theories such as DevOps.
+
Nati Cohen is a Production Engineer at SimilarWeb, fighting manual labor with code and vengeance. Previous experience includes: operations consulting, software development, *nix administration and security research in the Intelligence corps as well as in multiple startup companies.
One of the hottest and most widely used tools for log monitoring and analytics at the moment is the Elastic Stack:
+
+
+ * Elasticsearch doing the hard work of analyzing and searching large amounts of data.
+ * Logstash and Beats for collecting them.
+ * Kibana for powerful visualizations.
+
+
+
+This workshop gives you an overview of the four technologies, how they are working together, and how they can solve your problems. And of course attendees are setting up the full stack on their laptop to try it out for themselves!
+
+
+
About the speaker
+
Philipp is a Developer Advocate at Elastic, spreading the love and knowledge of full-text search, analytics, and real-time data. He is a frequent speaker at conferences and meetups about all things search & analytics, databases, cloud computing, and devops. Philipp lives in Vienna where he enjoys experimenting with software, organizing meetups, and sports.
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/remi-bergsma.md b/exampleSite/content/events/2016-amsterdam/workshops/remi-bergsma.md
new file mode 100644
index 000000000..263f576c3
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/remi-bergsma.md
@@ -0,0 +1,35 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Build your own Cloud in record time with Cosmic"
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/remi-bergsma/"]
+
++++
+
+
+
Title: Build your own Cloud in record time with Cosmic
+
+
In this workshop you will learn how to build your own Cloud and play with it!
+
+
+Cosmic Cloud is an IaaS platform geared towards Mission Critical workloads. We made it so easy that anyone can set it up and use it. Cosmic was forked off of on Apache CloudStack. The main reason was that we wanted to move much faster. In 2016 so far we did about 50 releases and deployed those to production. Our record is 5 times a day.
+
+
+
+We'll walk trough building your Cloud, but also on how to use it. What management tool to use. How to automate deployments with tools like CloudMonkey and Terraform. How to test changes and make sure nothing breaks.
+
+
+
+By the end of the workshop you are able to set it up yourself, you understand the concepts and have played with Cosmic quite a bit. And of course, you have asked any question you had :-)
+
+
+
Please bring your laptop! See ya there!
+
+
About the speaker
+
Remi Bergsma is an engineer with a pasion for automation. He works for Schuberg Philis, a Mission Critical outsourcing company in NL. Since about 2,5 years Remi works in the Mission Critical Cloud Team at Schuberg Philis. In this role he and his colleagues make sure their Mission Critical Cloud simply works. That is truly DevOps: from ordering, racking and automatically configuring hardware all the way to developing new features and fixing bugs in the Java and Python code.
+
+
Remi is an Apache CloudStack committer/PMC member and was Release Manager for CloudStack 4.6, 4.7 and 4.8. Nowadays Remi is one of the committers in the Cosmic Cloud project. He did several talks and workshops on conferences and enjoys teaching others new stuff.
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/simon-fisher.md b/exampleSite/content/events/2016-amsterdam/workshops/simon-fisher.md
new file mode 100644
index 000000000..641f1df44
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/simon-fisher.md
@@ -0,0 +1,33 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Out with the old, in with the new – Modernizing Application Deployment with Habitat"
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/simon-fisher/"]
+
++++
+
+
+
Title: Out with the old, in with the new – Modernizing Application Deployment with Habitat
+
+
+I created DAFNE Online, a website for people with Type 1 Diabetes back in 2008. I’d heard about this awesome new web application framework called Ruby on Rails so decided to learn that and implement the site using it, mainly because I like learning new stuff. Back then I was purely on the Dev side of DevOps and wasn’t too bothered about how the application was going to run in production, so with the aid of Google search and a few pieces of string I cobbled together a solution to get the app up and running on the web. Fast forward to 2016 and it was still running on the same basic stack – which was very outdated and required a manual effort to fix with every deployment.
+
+
+
+Enter a new way of deployment offered by Chef called Habitat, which allowed me to keep the environment up to date and automatically deploy the application without any fix or manual effort needed. In this workshop I'll give you a hands on snapshot of the journey from the old to the new, and show how this technology can configure and deploy Rails applications with ease.
+
+
+
+Pre-Requisites:
+- Signed up for Habitat
+- A Github Account
+- A Docker Registry account
+- A laptop installed with an OS that can reliably execute Rust and Go
+
+
+
About the speaker
+
Simon is a Solutions Architect at Chef, he has spent the past few years helping customers solve their Continuous Delivery problems with a variety of products and methods. In his spare time he also develops and maintains DAFNE Online, a site for people with Type 1 Diabetes in the UK. He also enjoys watching rugby, attempting to learn the piano, and learning how to be a new dad.
+
+
diff --git a/exampleSite/content/events/2016-amsterdam/workshops/stefan-stolzle.md b/exampleSite/content/events/2016-amsterdam/workshops/stefan-stolzle.md
new file mode 100644
index 000000000..101fb3467
--- /dev/null
+++ b/exampleSite/content/events/2016-amsterdam/workshops/stefan-stolzle.md
@@ -0,0 +1,37 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Implementing a CI and CD Pipeline with GitHub"
+type = "talk"
+aliases = ["/events/2016-amsterdam/program/stefan-stolzle/"]
+
++++
+
+
+
Title: Implementing a CI and CD Pipeline with GitHub
+
+
+GitHub makes it easy to collaborate on code, but its true power comes when it is used as the centrepiece of a modern deployment pipeline.
+
+
+
+This workshop will start with an overview of Git and GitHub, then deep dive into the concepts behind Continuous Integration (CI) and Continuous Delivery (CD), two cornerstones of good software development. After that, we'll cover how to start incorporating these practices into your workflow, by using GitHub to integrate with best-of-breed 3rd party tools.
+
+
+
+This workshop is designed for those with intermediate Git and GitHub knowledge, but limited hands-on experience implementing CI/CD practices.
+
+
+
+Pre-Requisites
+If you haven't done so already, please sign up for GitHub, Heroku and Travis CI accounts before the workshop (it's free). Everyone will use their individual Heroku and Travis CI accounts to deploy their own version of a sample app.
+
+
+
If you rather only sit in and watch, you don't need to setup any accounts.
+
+
About the speaker
+
Stefan has been a software developer, teacher and consultant for over 10 years, he believes "code is beautiful" and achieving it through collaboration. On the Professional Services team at GitHub his focus lies in helping companies to implement and migrate Git and GitHub, and to learn about the GitHub Flow to write beautiful software.
+
Be able to continuously deploy and test independently features that the dev team is building is a challenge.
+
+
For each pull request opened we should be able to see if it builds correctly, if all unit tests pass and if there is any issue with the integration test. Automated tests try to avoid regression but there are some things that are very hard to test in an automated fashion. At this point deploying and checking manually the feature on some live environment becomes crucial.
+
+
Things get even more interesting when several features development happen in parallel and all the PRs will be eventually merged into master.
+
+
Most of the work flow described for feature branches will apply for master but the deployment will be extended. Master will be provisioned on several environments with different characteristics which leads to manage various configurations.
+
+
In this workshop we will show how we implemented a continuous deployment pipeline for one of our customer on top of Jenkins with the help of Ansible.
+
+
In this workshop audience will learn:
+* building pipeline in Jenkins as a set of downstream/upstream jobs
+* reliably deploying each features independently with Ansible
+* tracking deployed features
+* how dev teams can support continuous deployment
+* not to be afraid of rebuilding your infrastructure"
+
+
+
About the speaker
+
I'm an independent Italian software engineer working in the software industry for more than a decade. My expertise lies in backend and system integration, never the less I've a strong background (and passion) in automation and devops.
+
I'm a co-founder of the StarterSquad community where I take part in several teams. We earn our living working for several startups around the world.
+
I'm a collaborative problem solver with strong analytical skills and committed to a continuous improvement process."
+
+
diff --git a/exampleSite/content/events/2016-atlanta/conduct.md b/exampleSite/content/events/2016-atlanta/conduct.md
new file mode 100644
index 000000000..1ca9cae10
--- /dev/null
+++ b/exampleSite/content/events/2016-atlanta/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+##ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+##CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-atlanta/contact.md b/exampleSite/content/events/2016-atlanta/contact.md
new file mode 100644
index 000000000..e641865cb
--- /dev/null
+++ b/exampleSite/content/events/2016-atlanta/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-atlanta/location.md b/exampleSite/content/events/2016-atlanta/location.md
new file mode 100644
index 000000000..ede04c9ad
--- /dev/null
+++ b/exampleSite/content/events/2016-atlanta/location.md
@@ -0,0 +1,32 @@
++++
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+
+Atlanta 2016 will be held at the Historic Academy of Medicine at Georgia Tech:
+
+875 West Peachtree St., NW
+Atlanta, GA 30309
+
+## Driving
+
+Parking will be provided free of charge.
+
+
+
+[View on Google Maps](https://goo.gl/maps/QjHRM8LhG8L2)
+
+## Airport
+
+There is a taxi stand outside of the baggage claim at the airport. Most taxi companies have a flat, standard rate from the airport to Midtown of $32. You may pay a little less or a little more, but please be aware about the taxi that you choose: ensure that it’s a legitimate taxi company and agree upon how the price will be determined (flat rate or meter) before putting your luggage inside. If you need help, do not hesitate to ask an airport employee; we’re known to be polite here in Georgia! Unfortunately, [ride-share companies like Uber](http://www.marketplace.org/2015/11/24/business/taxi-and-uber-fight-curb-atlanta-airport) are not allows to pick-up customers at the airport.
+
+## Public Transportation
+
+[MARTA](http://www.itsmarta.com/) serves the Historic Academy of Medicine. Follow the signs from baggage claim at the airport to get to the MARTA station. From Hartsfield International Airport take MARTA to the Midtown Station. The Historic Academy of Medicine is less than a quarter-mile walk from the MARTA station, or ride the [Georgia Tech Trolly](http://pts.gatech.edu/Documents/trolley%20rambler%2014%2015%20map.pdf).
+
+## Lodging
+
+The [Renaissance Atlanta Midtown Hotel](http://www.marriott.com/hotels/travel/atlbd-renaissance-atlanta-midtown-hotel/) is conveniently located across from the Historic Academy of Medicine. We have not reserved any special rates with the hotel.
diff --git a/exampleSite/content/events/2016-atlanta/program.md b/exampleSite/content/events/2016-atlanta/program.md
new file mode 100644
index 000000000..a87995e61
--- /dev/null
+++ b/exampleSite/content/events/2016-atlanta/program.md
@@ -0,0 +1,222 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+ Ignites
+
+
+
+ Affecting Change in Your Organization – Being an Agent of Change
+
+ byJosh Goldman
+
+
+
+ Critical Incident? WTF (What’s the format)? - Minimum Viable Runbooks
+
+ byWill La
+
+
+
+ Driven Off a Cliff: the Effects of Tool-Driven Architecture
+
+ byJosh Lohrman
+
+
+
+ Are YOU the Change Agent your Organization is Looking For…?
+
+ byDrew Nienaber
+
+
+
+ Everything I need to know about devops I learned from Metal
+
+ byJohn Vincent
+
+
diff --git a/exampleSite/content/events/2016-atlanta/propose.md b/exampleSite/content/events/2016-atlanta/propose.md
new file mode 100644
index 000000000..0c2b2c279
--- /dev/null
+++ b/exampleSite/content/events/2016-atlanta/propose.md
@@ -0,0 +1,38 @@
++++
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-atlanta/sponsor.md b/exampleSite/content/events/2016-atlanta/sponsor.md
new file mode 100644
index 000000000..7bb4ef0d8
--- /dev/null
+++ b/exampleSite/content/events/2016-atlanta/sponsor.md
@@ -0,0 +1,90 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference
+for practitioners that depends on sponsorships.
+We do not sell product presentations
+or distributee attendee contact lists.
+Sponsors have the opportunity for
+short elevator pitches during the program,
+recognition on the website,
+and social media before, during, and after the event.
+
+Sponsors are encouraged to represent themselves by actively participating
+and engaging with the attendees as peers.
+Any attendee has the opportunity
+to demo products/projects as part of an open space session.
+All attendees are welcome to propose any subject they want during the open spaces,
+but this is a community-focused conference,
+so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Bronze 1000 USD
+
Silver 3000 USD
+
Gold 5000 USD
+
+
+
included tickets
+
1
+
3
+
5
+
+
+
logo on DevOpsDays Atlanta 2016 event website
+
+
+
+
+
+
logo on all email communication
+
+
+
+
+
+
logo on banner at venue during event
+
+
+
+
+
+
mention by MC at kickoff and close
+
+
+
+
+
+
1 minute pitch to full audience (including streaming audience)
diff --git a/exampleSite/content/events/2016-bangalore/contact.md b/exampleSite/content/events/2016-bangalore/contact.md
new file mode 100644
index 000000000..0091636ae
--- /dev/null
+++ b/exampleSite/content/events/2016-bangalore/contact.md
@@ -0,0 +1,16 @@
++++
+date = "2016-05-03T06:32:33-05:00"
+title = "contact"
+type = "event"
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-bangalore/propose.md b/exampleSite/content/events/2016-bangalore/propose.md
new file mode 100644
index 000000000..ef2edd206
--- /dev/null
+++ b/exampleSite/content/events/2016-bangalore/propose.md
@@ -0,0 +1,50 @@
++++
+date = "2016-06-17T18:13:19-05:00"
+title = "propose"
+type = "event"
+aliases = ["/events/2016-bangalore"]
+
++++
+
+### [Talk at DevOpsDays - India - 2016](https://www.papercall.io/devopsdays-india-2016)
+
+> {{< cfp_dates >}}
+
+DevOpsDays India this year is scheduled for {{< event_start >}} - {{< event_end >}}. We have CFP open till 4th September’ 2016 with Speakers having enough time to propose a talk.
+
+**[Submit Your Talk Here](https://www.papercall.io/devopsdays-india-2016)**
+
+We are looking for submissions under all 3 traditional categories
+
+
Lightening Talk (5-10min)
+
Talk (30-45 min)
+
Workshop (>60min)
+
+
+The topics can vary from further emphasis on DevOps philosophy to nerd internals of an awesome utility from the toolbox.
+
+It can be having fun with containers or fierce scale cluster handling petabytes of data.
+
+Or just some new monitoring/logging/analytics/automation framework you’re building or got introduced to.
+
+If you have ideas for multiple talk proposals, do submit them separately.
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Contact
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+{{< event_twitter devopsdaysin >}}
+
diff --git a/exampleSite/content/events/2016-bangalore/registration.md b/exampleSite/content/events/2016-bangalore/registration.md
new file mode 100644
index 000000000..7aa6754c1
--- /dev/null
+++ b/exampleSite/content/events/2016-bangalore/registration.md
@@ -0,0 +1,19 @@
++++
+
+date = "2016-06-22T20:21:47-05:00"
+title = "registration"
+type = "event"
+aliases = ["/events/2016-bangalore"]
+
++++
+
+### [Register to attend DevOpsDays India 2016](https://www.townscript.com/e/dod16)
+
+Tickets are now available for the event.
+
+**[Register Here](https://www.townscript.com/e/dod16)**
+
+You can confirm your attendence at the DevOpsDays community conference now.
+To meet, listen to and discuss with the leading members of DevOps community.
+
+---
diff --git a/exampleSite/content/events/2016-bangalore/welcome.md b/exampleSite/content/events/2016-bangalore/welcome.md
new file mode 100644
index 000000000..7810f2ea7
--- /dev/null
+++ b/exampleSite/content/events/2016-bangalore/welcome.md
@@ -0,0 +1,31 @@
++++
+date = "2016-05-03T06:32:33-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-bangalore"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+DevOps Days is returning to Bangalore!
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Contact
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+{{< event_twitter devopsdaysin >}}
+
diff --git a/exampleSite/content/events/2016-berlin/conduct.md b/exampleSite/content/events/2016-berlin/conduct.md
new file mode 100644
index 000000000..7addf8163
--- /dev/null
+++ b/exampleSite/content/events/2016-berlin/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-07-07T18:12:13+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-berlin/contact.md b/exampleSite/content/events/2016-berlin/contact.md
new file mode 100644
index 000000000..5ee3745df
--- /dev/null
+++ b/exampleSite/content/events/2016-berlin/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-07-07T18:12:13+02:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-berlin/location.md b/exampleSite/content/events/2016-berlin/location.md
new file mode 100644
index 000000000..3510575e9
--- /dev/null
+++ b/exampleSite/content/events/2016-berlin/location.md
@@ -0,0 +1,28 @@
++++
+date = "2016-07-07T18:12:13+02:00"
+title = "location"
+type = "event"
+
++++
+
+## Kalkscheune Berlin
+
+
+
+
+
+
+
+Located along Friedrichstrasse, within walking distance of the Brandenburg Gate, and of Museum Island and close to the central railway station, the Kalkscheune Centre provides setup and seating for our DevOpsDays Berlin. Varied rooms in a landmarked building and a green inner courtyard provide a very special framework for our event.
+
+Find out more about the Kalkscheune on their website.
+
+
+
+Venue: Kalkscheune Berlin
+Address: Johannisstrasse 2, 10117 Berlin, Germany
+
Title:
+“Forget about redshirts, here come the tribbles” (serverless microservices will rule the world)
+
+
+
Description:
+
+
+TL;DR this talk is about Microservices and serverless architectures (FaaS) compared to PaaS.
+
+Yes, of course this title requires an explanation.
+
+In her keynote at DevOpsDays Berlin 2014 Dawn Foster
+(https://twitter.com/geekygirldawn) was introducing an appealing Star Trek
+metaphor to explain the idea that we better treat servers as something
+replaceable: “Treat your servers as redshirts”. (You probably remember that
+redshirts are in the Star Trek world are the poor security guys that always die
+when they are joining an excursion to a planet, whereas the yellow and blue
+shirts, namely Kirk and his deck crew, always survive.)
+
+Now after a few years we are ready for a new metaphor: “Forget about redshirts,
+here come the tribbles”. Rather than crafting our code and a deployment
+pipeline to deploy in our favorite cloud PaaS on servers (redshirts), we write
+many microservices using lambda functions and AWS is executing -- and magically
+spinning up nameless tribbles. (As you of course know tribbles are the plushy,
+nameless animals starring in Star Trek 2×13.)
+
+We are going to cover how FaaS architectures (function as a service), that is
+serverless microservice architectures (e.g. AWS Lambda), can help us to
+implement apps and services quickly in a quite simple way, how to deploy them.
+Even the feature flag can be replaced by using quite simple patterns. Of
+course we will cover also the business and financial aspects FaaS compared to
+PaaS.
+Presented as a message to a former colleague still in a more traditional IT Ops role who would like to “devops” but is not sure how, this hopefully entertaining talk covers the cultural and technological journey from being in an old-school Systems Department at a telecoms company to the world of “Devops” filled with buzzwords, 100x more recruiter emails, and co-workers born when I was in high school. From the perspective of an engineer just turned 40, topics will cover life in German startups, what Devops means and how I’ve seen it implemented, what tools and skills you would need to make the switch, and why you would want to.
+
Title:
+Implementing versioned service discovery in 100 Lines Of Code
+
+
+
Description:
+
+
+
+Service discovery has been made too complex by "complexing" it with orchestration. There are too many beasts-of-a-tool out there that do too much, and yet don't service versioning in service discovery.
+This talk will walk you through 100 lines of Node.js code with no dependencies other than redis, and implement a service discovery service with the following features:
+
+Semantic versioning of services
+Services depend on specific versions of other services, so v1.2.3 & v1.3.0 can be both live, and you kill off old services that have no users.
+
+
+Live health checks with inversion of responsibility
+Don't ping a service under high load with status & health checks, instead let it ping back when it can. If it can't ping back because it's near-capacity, then don't route any more traffic to it!
+
+
+Mocking services during testing & development
+Should not have to bring up the entire microservices stack do develop one of them.
+
+
+Randomized scheduling
+So you don't starve any one service, instead pick one at random from the ones available & healthy.
+
+
+No highly-available service discovery service
+Solving the chicken & egg requirement of a highly available service discovery service, in order to enable other highly available services. Only the service discovery database (redis) needs to distributed (redis cluster).
+
+A surprising number of tools out there simply fail to provide these features, and yet come with too many other things they want to do. This talk does the above in easy-to-understand 100 LOC that you can use & modify with confidence!
+
+We often hear talks of "scale" and "reliability", mostly based on personal experience and lessons learned. What can Mathematics tell us about reliability and scale? Can math help us scale our systems and companies? It turns out that failure models, probability, statistics and other domains can help our analysis and provide insights.
+
+This talk presents various mathematical models that support our understanding of reliability and failure. There are many nuances and pitfalls associated with reliability and mathematical modelling helps to reveal and avoid them.
+
+This talk will present basic models of failure and reliability and discuss their implications:
+
+Graphs. All operators and most of the developers use them to
+identify problems and forecast trends. There are so many solutions out
+there to collect and visualize data. Currently one of the most famous is
+Grafana. Used with multiple backends, it is capable to correlate data
+from very different sources.
+
+In my ignite talk I will show how one can
+see dynamic thresholds in a graph, while deployments, puppet runs or SSH
+logins are displayed in the same graph. This can be achived by combining
+multiple tools: Icinga2, Graphite, Elastic Stack and Grafana. I will
+show an example on how a single graph can tell a whole story. Beginning
+from a user doing a deployment, a server starting to fail, up to another
+user logging in and fixing the issue.
+
+Have you ever googled for a error message, and the only result was that message in the original project? Or the proposed solution is not applicable to your situation? Or there is no result, because the error is from a internal project? It's time to break out the tools.
+
+Every error has a cause somewhere. Luckily, most probably in a piece of code someone has written at one time in the past. Due to the rise of free and open software (FOSS), ever more of the code involved in those issues is accessible to us. To use that as a resource, I need to be able to find, browse, read, analyze, understand, and evaluate that code. Which is basically what I did the last few years working with various open source tools. In this session I want to share some of my experiences, and approaches to understand what's happening, when something goes wrong:
+
+
+
Reading and browsing code for understanding
+
Building a mental model of the running system
+
Comparing expected and observed behaviours
+
Observing deeper into the system: strace, tcpdump, etc
+Cultural Fit and Diversity are two over-used concepts that betray themselves by their apparent opposition: Hiring for cultural fit reduces diversity, and vice versa. First I will point out some of the things that went wrong in this area over the last years: e.g. the rise and fall of Political Correctness, or statistic-based diversity initiatives. Finally I ask you to stop slacking off and do the right things:
+
+* Instead of fitting people in, hire for cultural fitness! You need folks that can listen, understand, and act, not people that blend in.
+
+* Instead of paying lipservice to (at best) partial solutions, actively make folks of all backgrounds feel welcome in your team, company, or community.
+
+If we don't make the world a better place, who else would do it for us?
+
+
+During the Habitat Workshop we will start with a deep dive into the components that make up Habitat and learn all about what it takes to create a Habitat Artifact that is runtime agnostic. You will then be exposed to a few demos showing off some of Habitat’s awesome features.
+
+Have you heard about Roles in Chef Server? Have you heard that “best practice” says not to use them because they’re not versionable? Have you been warned not to store attributes in Roles? Well what if we could have it all? What if we could use Roles that were versionable and were safe to store attributes in? Well you’re in luck — we can! Join me as we dive into the Role-Cookbook Pattern and learn that we can, indeed, have our cake and eat it too!
+
+My friend Romain Pelisse and I would like to submit a proposal for the upcoming Berlin Devops Days named (for now) "Chef vs Ansible". This would be a hands on lab, where we would walkthrough the attendees into setting up a server (including some services and a webapp) using either Chef and Ansible.
+
+During the hands on, we will cover the main features of each technologies, and point out both their common grounds, limitations and qualities. The aims is also to help "troubleshoot" their issue on the selected technologies, and therefore getting out of the session an interactive tutorial.
+
Title:
+Turtles all the way down: native containers, native code
+
+
+
Description:
+
+
+We need to talk about our reliance on virtualization.
+
+ Most of us seem to be running Java virtual machines on top of virtual machines, so I’d like to look at both VMs and the JVM. At a time when performance is at a high premium in terms of power consumption and cost of compute cycles, are the trade-offs still worth it?
+
+Now is a good time to take stock of how far container and technology and tooling have caught up with full virtualization, and to gauge the promise of a new family of languages that compile to native code. It’s hardly a coincidence that one of them, Go, dominates Linux container management and orchestration.
+
+Nevertheless, the last time this question came up, the decision taken was to place all containers on a VM layer; the JVM was never in doubt. Is it too early to dream of native code running in native containers on physical hardware?
+
Title:
+Information Overload and the Real Costs of Interruptions
+
+
+
Description:
+
+
Lift your head from the screen for a second. Reflect for a moment on where your attention is. Is it where it’s supposed to be? Where you want it to be? Probably not. Where is it instead?
+
+Ask yourself why. Why did I start checking twitter, facebook, slack, hipchat anyway? Why did I just pick up my phone? I’m sure I felt a vibration...hmmm maybe not.
+
+If we begin with the assumption that our time is our most precious asset then we have a problem. Our attention and our time are being fought over all day every day, and no one is immune to this type of “digital disruption”. Productivity is plummeting, anxiety and stress are prevalent. Email Apnea is a thing.
+
+In this talk we’ll look at our relationship to technology in the workplace and what this impact has on culture, job satisfaction, productivity and mental health.
+
+We’ll also discuss what we can do as individuals and teams to get better and to help each other.
+A presentation about a next gen config management tool, and the
+specific problems this project solves.
+
+Three of the main design features of the tool include:
+
+
Parallel execution
+
Event driven mechanism
+
Distributed architecture
+
+
+This talk will demo a prototype I've built that implements these ideas
+and which is written in golang. I will also show the automatic edge,
+automatic grouping and automatic elastic etcd clustering management
+features.
+
+An introductory blog post on the subject is available. https://ttboj.wordpress.com/2016/01/18/next-generation-configuration-mgmt/ Attendees are encouraged to read it before the talk if they are interested!
+
Title:
+How GitHub uses GitHub to develop and deploy GitHub
+
+
+
Description:
+
+
+Learn how GitHub's globally distributed teams use GitHub tooling to develop GitHub, collaborate with
+engineering, sales, marketing, services and legal and deploy more than 500 times a week. Experience
+ChatOps, a great way to reduce friction between development and operations and super efficient
+way to bring new engineers up to speed.
+See life examples on how to use Hubot to retrieve log files, graph various metrics and deploy pull
+requests directly from Slack to Heroku. Get some ideas how to build such a ChatOps environment
+yourself.
+
+Description:
+
+
Zen of GitHub as guiding philosophy for any new feature work, nature of features, internal and external communication
+
remote nature of GitHub organization and its implications on standups, pair programming and working style (default to asynchronous)
+
walk through the GitHub Flow based on examples from different teams (engineering, web site, legal, services)
+
introduction of GitHub's deployment API and life demo how to ue it from Slack and Hubot to deploy pull requests to Heroku preview environment
+
introduction into ChatOps
+
life command execution
+
philosophy
+
reduce communication friction between dev and ops
+
have all needed context in one chat room
+
learn from day one on, even from historic conversations
+
+
ChatOps examples from the DevOps team
+
+
ChatOps in the context of continuous deployment at GitHub
+
introduction to various deployment environments (lab, canary, production)
+
introduction to the queueing mechanism for the prod env
+
introduction to the confidence dashboard (deployment metrics)
+The micro service paradigm goes well with the notion of agile, autonomous full stack development teams. But what about the underlying infrastructure like CI/CD systems, monitoring, log analytics, message busses and so on? These are often build as monolithic services maintained by centralised teams. All the scalability woes and maintenance issues that we would liked to have left behind great again.
+Instead these services can be built as appliances that are used in self-service by the product development teams. At ImmobilienScout teams get dedicated accounts in the cloud that they fully own and that come with all the supporting services.
+It adds some challenges to the game: How to package, distribute and update this distributed infrastructure? Who’s monitoring and taking responsibility when one these components breaks? High reliability and proper documentation are needed.
+In the end providing all the teams with self service infrastructure enables a truly distributed service landscape that scales up and down along the needs of the business.
+
+7 years ago we had the idea to organise a conference in Gent to bridge the gap between developers and the people runing their code. It was the start of a new global movement. This talk will guide you trough that journey and discuss some of the things we learned along the way.
+
Title:
+Communities of practice in large scale DevOps transformations
+
+
+
Description:
+
+
+Swisscom started its DevOps Journey late 2014 - over enthusiastic and infected by the books, blogs and success stories of various DevOps leaders. But how do you transfer a company with round about 4’000 IT specialists, hierarchical structures and legacy-monoliths? How do you centrally organize a change if the target structure is decentralized and self-organizing? How can you spread good practices and amplify them beyond team boundaries?
+
+I’d like to talk about our DevOps journey – from first bottom-up pilot teams, early success stories, how we involved top management and how we plan to scale the change in the future. A key element in our story are communities of practices. We started such communities on different levels with different focus. Shipit days on team level, communities on department level to discuss technically specific cross-team aspects and guilds on enterprise level to foster good practices, share knowledge and bunch energy to resolve common seen impediments. To benefit from outside views, we also founded a Meetup Community to exchange with other DevOps Enthusiasts from the area. It is amazing to see what developed out of these communities and how much energy is involved in these topics.
+
+You can’t get DevOps by buying a tool - because it’s about culture. Sounds easy and compelling. In this talk I would like to propose a way how to get such a DevOps culture in a big legacy company. I would like to share the experience we made so far and the next steps we intend to take. And I would like to share my conviction that communities of practice play a central role in a large scale DevOps transformation. I thought that this might be interesting for other participants as the talk is about a large-scale transformation of a big Telco company with lots of legacy and “netnear” IT infrastructure.
+
+Be prepared for 20 awesome ways to make your project fail. You will laugh, cry, and learn how to do better to save your project and your DevOps initiative.
+
+I like git. And I love GitHub. As a developer and tech-savvy person I spend quite a lot of my time working with version control & ticketing systems. And as a human, I’m lazy. So I’m always looking for ways to make my everyday routine easier with the use of technology.
+
+Luckily the folks from GitHub are the same and are trying hard to make our everyday life easier too.
+This talk will bring you some tips & tricks for everyday git(hub) usage including these how-to’s:
+
+Hey, I’m an application developer and I’m done managing my server infrastructure. Stop slowing me down.
+
+Application developers are sick and tired of being slowed down by having to learn new tasks and care about mundane details. I don’t care about server infrastructure. In fact, I hate DevOps! I don’t need to worry about the differences between cloud and a data center; the applications I create are brilliant, running them is not my job. Let’s talk about walls and boundaries. You do your job, I’ll do mine, and we can both get back to moving fast.
+
+This talk is inspired, in part, by http://thenewstack.io/serverless-computing-growing-quickly/ As someone practicing DevOps for a number of years it’s really easy to let quotes like this make you cry: “DevOps significantly adds to the development time as application builders are weighed down by the need to manage their server infrastructure at the same time.”
+
Title:
+Talking to People: The forgotten DevOps tool
+
+
+
Description:
+
+
+Main statement: We can improve devops processes and software delivery by focusing on better communications, not more complex software tools.
+
+As we focus on how to how to best use JIRA, Hipchat, Slack, project management products, incident and defect tracking solutions, and a myriad of other software tools as a part of our development and delivery environment, we often lose sight of the most fundamental and powerful tool available – talking to people, to our team members, management, users, and other stakeholders.
+
+Rather than burying ourselves in tools and devices, software and search engines, we can do more for our overall application quality and delivery processes by simply talking to the people around us. While a focus on software may produce more data, knowing the thoughts, expectations, and ideas of the stakeholders will result in more innovative ideas as well as a filter for determining optimal solutions.
+
+Using the research of MIT researcher Sherry Turkle and others, this presentation uses the power of conversation to illustrate how we can improve our testing practices and results, for the good of all stakeholders. It illustrates how our conversations can be more powerful and directed than any software tool in determining and delivering on application quality and performance. Last, it examines the role of ChatOps tools in supplementing conversation with actionable ideas and automated responses
+to be a true real time response environment.
+
+Main takeaways:
+
How a search for the perfect software tools may be preventing us from using our fundamental communication skills in a devops context.
+
How talking to people in our project work is becoming a lost art.
+
Why starting an active program of interpersonal interaction can improve your application quality and delivery right away.
Title:
+Building a Culture of Builders - The adventures of building an engineering team at Facebook London
+
+
+
Description:
+
+
+Production Engineering (PE) is the team that greases the gears of hundreds of systems at Facebook. We use different engagement models to work with several teams and make sure that all the pieces stay together, as well as put together the pieces that eventually fall apart. This talk will cover the process of stablishing the PE presence in a thriving and quickly growing engineering office in London, detail the different engagement models that we use and the bumps and bruises we got along the
+way.
+
+ Topics that will be covered include:
+
+My friend François Le Droff and I would like to submit a proposal for the upcoming Berlin Devops Days named (for now) "Chef vs Ansible". This would be a hands on lab, where we would walkthrough the attendees into setting up a server (including some services and a webapp) using either Chef and Ansible.
+
+During the hands on, we will cover the main features of each technologies, and point out both their common grounds, limitations and qualities. The aims is also to help "troubleshoot" their issue on the selected technologies, and therefore getting out of the session an interactive tutorial.
+
+Everyone has heard the phrase “Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live”. But fear is never the best way to motivate people to build supportability into their projects. In this talk we’ll discuss tips for writing and publishing software code which is easier for other people to support, whether they are open source contributors or current colleagues.
+
+We’ll cover:
+
+
The importance of clean code
+
The usefulness of examples you can copy and paste
+
What makes for great documentation
+
Quick and polite responses to issues and pull requests
+
Making your project easy to use out of the box
+
Why empathy for others is critical for projects which can be supported by a wide group of people
+
+The audience should come away with:
+
+
A good list of common pitfalls to avoid when writing supportable code
+
Examples of common traits of successful projects.
+
Knowledge of how to better promote co-operation, especially for open source projects
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-berlin/proposals.md b/exampleSite/content/events/2016-berlin/proposals.md
new file mode 100644
index 000000000..c2494686a
--- /dev/null
+++ b/exampleSite/content/events/2016-berlin/proposals.md
@@ -0,0 +1,9 @@
++++
+date = "2016-07-08T18:12:13+02:00"
+title = "proposals"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+This page lists the talk proposals and workshops we have received.
diff --git a/exampleSite/content/events/2016-berlin/propose.md b/exampleSite/content/events/2016-berlin/propose.md
new file mode 100644
index 000000000..d990aa67f
--- /dev/null
+++ b/exampleSite/content/events/2016-berlin/propose.md
@@ -0,0 +1,65 @@
++++
+date = "2016-07-07T18:12:13+02:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+As DevOps is an accepted working culture by now, we're curious about how that might affect other parts of the workplace, too. But we're also open for any DevOps related topics you want to talk about, be they cultural or technical.
+
+This is what we're especially looking for:
+
+
Culture
+
+
+
Diversity: Productive teams benefit from a diverse line-up.
+
+
What are your success stories?
+
How do you cope with the challenges this poses?
+
Who is responsible for making this a success?
+
+
How do you hire for cultural fit?
+
What's the stance on management in this culture?
+
Have you seen this culture spread to other parts of the company?
+
+
What's their story?
+
How does that work?
+
+
+
+
Technical things, we're still engineers!
+
+
Assumption: Automating infrastructure is the easy part, automating data is hard. Discuss.
+
Which impact does DevOps have on traditional security auditing or change control?
+
How do you describe your network infrastructure as code?
+
You Build It You Run It: Which kind of team do you need for that?
+
+
+
There are four ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
Hands-On session : if your talk is of a technical nature, maybe it makes more sense to show others what and how you do it. These are 45 minute sessions parallel to the Open Space sessions. Give people a chance for questions. Please: No product demos.
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-berlin/speakers.md b/exampleSite/content/events/2016-berlin/speakers.md
new file mode 100644
index 000000000..f7a807652
--- /dev/null
+++ b/exampleSite/content/events/2016-berlin/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-10-03T15:43:20+02:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-berlin/sponsor.md b/exampleSite/content/events/2016-berlin/sponsor.md
new file mode 100644
index 000000000..6240d3ab2
--- /dev/null
+++ b/exampleSite/content/events/2016-berlin/sponsor.md
@@ -0,0 +1,55 @@
++++
+date = "2016-07-07T18:12:13+02:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+
+Platinum sponsors get a full table and Gold sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+### Sponsoring packages
+
+
+
Packages
+
Silver 1000 EUR
+
Gold 3000 EUR
+
Platinum 5000 EUR
+
+
+
2 included tickets
+
logo on event website
+
logo on shared slide, rotating during breaks
+
logo on all email communication
+
logo on its own slide, rotating during breaks
+
1 minute pitch to full audience
+
2 additional tickets (4 in total)
+
4 additional tickets (6 in total)
+
shared table for swag
+
booth/table space
+
thank you tweet
+
+
+### Evening event package
+
+In addition to the standard sponsoring packages we are offering an exclusiv evening event sponsoring for 7500 EUR. The evening event sponsor package includes all Platinum benefits and an exlusive evening event branding.
+
+
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, drop us an email: {{< email_organizers >}}.
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+{{< event_twitter blndevops >}}
diff --git a/exampleSite/content/events/2016-boise/conduct.md b/exampleSite/content/events/2016-boise/conduct.md
new file mode 100644
index 000000000..e47289e35
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-03T13:24:36-06:00"
+title = "Code of Conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-boise/contact.md b/exampleSite/content/events/2016-boise/contact.md
new file mode 100644
index 000000000..342d92c41
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-03T13:24:36-06:00"
+title = "Contact Us"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-boise/location.md b/exampleSite/content/events/2016-boise/location.md
new file mode 100644
index 000000000..7e46c2aae
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/location.md
@@ -0,0 +1,23 @@
++++
+date = "2016-05-03T13:24:36-06:00"
+title = "Location"
+type = "event"
+
++++
+
+Boise Centre
+850 W. Front Street
+Boise, ID 83702
+
+
+
+[View on Google Maps](https://goo.gl/maps/EJKghfejxw32)
+
+## Lodging Options
+
+The following hotels have extended a discounted rate to DevOpsDays Boise attendees:
+
+* [The Grove Hotel](https://bookings.ihotelier.com/bookings.jsp?hotelId=76224&identifier=TAOS)
+ The Grove Hotel is in the same plaza as the Boise Centre.
+* [Hotel 43](https://gc.synxis.com/rez.aspx?Hotel=14937&Chain=5150&arrive=10/07/2016&depart=10/09/2016&adult=1&child=0&PROMO=DODG)
+ Hotel 43 is across the street from the Boise Centre at 9th & Grove Street.
diff --git a/exampleSite/content/events/2016-boise/program.md b/exampleSite/content/events/2016-boise/program.md
new file mode 100644
index 000000000..d28bf1075
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program.md
@@ -0,0 +1,93 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
The Schedule
+
+
+
+
+
+ •
+
+
+
+
+ Search for "DevOpsDays Boise 2016" in the MyEvents2Go app.
+
+
+
+
+
+
+
+
Day 1
+
+
+ {{< program_entry time="08:00-09:00" title="Registration, Breakfast, and Sponsor Booths Open" >}}
+ {{< program_entry time="09:00-09:15" title="Opening Welcome" >}}
+ {{< program_entry time="09:15-09:45" title="No Ops" presenter="-kelsey-hightower" >}}
+ {{< program_entry time="09:45-10:15" title="People Make It Happen" presenter="dave-harrison" >}}
+ {{< program_entry time="10:15-10:30" title="Break" >}}
+ {{< program_entry time="10:30-11:00" title="How Netflix Thinks about DevOps" presenter="dave-hahn" >}}
+
+ {{< program_entry time="11:00-11:30" title="Bottoms Up! Exploring History of Operations Mgmt from Henry Ford to John Willis" presenter="ben-rockwood" >}}
+ {{< program_entry time="11:30-12:00" title="DevOps will Fail... How the Phoenix Project Simulation can help you Succeed" presenter="jean-bennett" >}}
+ {{< program_entry time="12:00-12:55" title="Lunch & Book Signing with Kelsey Hightower and Jason Hand" >}}
+ {{< program_entry time="12:55-13:30" title="Ignite Talks" >}}
+
+ {{< program_entry time="13:30-14:00" title="Configuration Management is an Anti-Pattern" presenter="jonah-horowitz" >}}
+ {{< program_entry time="14:00-15:30" title="Open Space" >}}
+ {{< program_entry time="15:30-16:00" title="DevOps @Scale with Baruch Sadogursky" presenter="leonid-igolnik" >}}
+ {{< program_entry time="16:00-16:15" title="Break" >}}
+ {{< program_entry time="16:15-16:45" title="The Unrealized Role of Monitoring & Alerting" presenter="jason-hand" >}}
+ {{< program_entry time="16:45-17:15" title="From Theory to Practice –Developing DevOps Capability to Delivery Enterprise Level Products" presenter="darryl-bowler" >}}
+ {{< program_entry time="17:15-17:30" title="Day One Wrap-Up" >}}
+ {{< program_entry time="19:00-21:00" title="Evening Social @ Basque Center" >}}
+
+
+
+
+
Day 2
+
+
+ {{< program_entry time="08:00-09:00" title="Registration, Breakfast, and Sponsor Booths Open" >}}
+ {{< program_entry time="09:00-09:15" title="Opening Welcome" >}}
+ {{< program_entry time="09:15-09:45" title="Day 2 Keynote" presenter="-vm-brasseur" >}}
+ {{< program_entry time="09:45-10:15" title="NASA Jet Propulsion Lab and DevOps" presenter="dan-isla" >}}
+ {{< program_entry time="10:15-10:30" title="Break" >}}
+ {{< program_entry time="10:30-11:00" title="Patterns and Antipatterns in Docker Image Lifecycle" presenter="baruch-sadogursky" >}}
+ {{< program_entry time="11:00-11:30" title="IC to VP: An Experience Report on Becoming a Manage" presenter="seth-falcon" >}}
+ {{< program_entry time="11:30-12:00" title="DevOps and Groupthink: An Oxymoron?" presenter="gerie-owen" >}}
+ {{< program_entry time="12:00-13:00" title="Lunch" >}}
+ {{< program_entry time="13:00-13:30" title="New Docker Features for Orchestration and Clusters" presenter="jeff-anderson" >}}
+ {{< program_entry time="13:30-14:00" title="What Goes in Must Come Out: Hidden Defects in your Software Application" presenter="matthew-barker" >}}
+ {{< program_entry time="14:00-15:00" title="Open Space" >}}
+ {{< program_entry time="15:00-15:30" title="Talking to People: The Forgotten DevOps Tool" presenter="peter-varhol" >}}
+ {{< program_entry time="15:30-15:45" title="Break" >}}
+ {{< program_entry time="15:45-16:15" title="Managing Multiple SaltStack Environments for Fun & Profit" presenter="gareth-greenaway" >}}
+ {{< program_entry time="16:15-16:45" title="Cross Platform Tool Development in GO" presenter="caskey-dickson" >}}
+ {{< program_entry time="16:45-17:15" title="The Database Server is about to Have a Terrible Accident" presenter="corey-quinn" >}}
+ {{< program_entry time="17:15-17:30" title="Wrap-Up" >}}
+
diff --git a/exampleSite/content/events/2016-boise/program/-kelsey-hightower.md b/exampleSite/content/events/2016-boise/program/-kelsey-hightower.md
new file mode 100644
index 000000000..f5274fb51
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/-kelsey-hightower.md
@@ -0,0 +1,10 @@
+---
+City: "Boise"
+Year: "2016"
+linktitle: "-kelsey-hightower"
+title: "Kelsey Hightower"
+type: "talk"
+
+---
+
+## Day 1 Keynote
diff --git a/exampleSite/content/events/2016-boise/program/-vm-brasseur.md b/exampleSite/content/events/2016-boise/program/-vm-brasseur.md
new file mode 100644
index 000000000..e64208c32
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/-vm-brasseur.md
@@ -0,0 +1,9 @@
+---
+City: "Boise"
+Year: "2016"
+linktitle: "-vm-brasseur"
+title: "VM Brasseur"
+type: "talk"
+---
+
+## Day 2 Keynote
diff --git a/exampleSite/content/events/2016-boise/program/alan-kraft.md b/exampleSite/content/events/2016-boise/program/alan-kraft.md
new file mode 100644
index 000000000..46435cd57
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/alan-kraft.md
@@ -0,0 +1,14 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Alan Kraft"
+type: "talk"
+---
+
+## DevOps at 800C : Learning from Wildland Firefighters
+
+DevOps practitioners can learn valuable lessons from the wildland firefighting community. My interest in proposing this talk was sparked both by DevOps thought leaders and a family connection to wildland firefighting & Boise.
+
+I’ll provide some background on wildland firefighters and the application of some of their techniques to DevOps. I’ll discuss adaptation, socio-technical systems and complex adaptive systems. I’ll talk about wildland firefighting accident investigation and its relevance to blameless postmortems in a DevOps context. I’ll cover what we can learn about leadership training and the learning organization from the wildland firefighting community. I’ll discuss the concept of margin and how it could benefit DevOps practitioners; and conclude with research into the transformation of culture in the wildland firefighting community and its relevance to DevOps transformations.
+
+This Ignite talk will provide a good starting point for open spaces discussions on blameless postmortems (learning reviews), learning organizations & systems thinking, complex adaptive systems, and cultural transformation. Links to sources for those interested in learning more about wildland firefighting and DevOps will be provided in the slide deck.
diff --git a/exampleSite/content/events/2016-boise/program/baruch-sadogursky.md b/exampleSite/content/events/2016-boise/program/baruch-sadogursky.md
new file mode 100644
index 000000000..113ac4044
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/baruch-sadogursky.md
@@ -0,0 +1,16 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Baruch Sadogursky"
+type: "talk"
+---
+
+## Patterns and Antipatterns in Docker Image Lifecycle
+While Docker has enabled an unprecedented velocity of software production, it is all too easy to spin out of control.
+A promotion-based model is required to control and track the flow of Docker images as much as it is required for a traditional software development lifecycle.
+New tools often introduce new paradigms. We will examine the patterns and the antipatterns for Docker image management, and what impact the new tools have on the battle-proven paradigms of the software development lifecycle.
+
+## DevOps @Scale
+Co-Presented with [Leonid Igolnik](/events/2016-boise/program/leonid-igolnik/)
+
+Remember the times when one server was enough? And a guy named “sysadmin” was babysitting it along with his other duties of installing MS Office for everybody? For better or for worse, those times are long gone. Today, companies manage tens of thousands of servers and perform thousands of production changes per day. In this talk we will look at the resources, techniques and tools needed for managing DevOps at Scale and we will discuss the challenges that companies encounter when they hit it.
diff --git a/exampleSite/content/events/2016-boise/program/ben-rockwood.md b/exampleSite/content/events/2016-boise/program/ben-rockwood.md
new file mode 100644
index 000000000..67d224fbf
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/ben-rockwood.md
@@ -0,0 +1,12 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Ben Rockwood"
+type: "talk"
+---
+
+## Bottoms Up! Exploring History of Operations Mgmt from Henry Ford to John Willis
+
+A thoughtful examination of the history of management which asserts that DevOps was an inevitable evolution of business as we entered the 21st century, and namely the Internet revolution that it brought. An understanding of this history allows us to consider at a deeper level the future that lies ahead for us and how we should position ourselves today
+
+## Next Gen Secrets Management with Hashicorp Vault
diff --git a/exampleSite/content/events/2016-boise/program/caskey-dickson.md b/exampleSite/content/events/2016-boise/program/caskey-dickson.md
new file mode 100644
index 000000000..837ede928
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/caskey-dickson.md
@@ -0,0 +1,12 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Caskey Dickson"
+type: "talk"
+---
+
+## Cross Platform Tool Development in GO
+Go is an excellent language for doing cross-platform development which is ideal for ops tools. As an SRE deploying into a multi platform (Linux, Windows, OSX, \*BSD, Solaris, etc.) environment I've found that the features built into Go enable me to write once and run anywhere. This talk will cover the language features that enable you to deploy the same code to multiple platforms, a few gotchas, and a few examples.
+
+## SRE Lessons from a 17th century Samurai
+In the 17th century one of the greatest samurai in history climbed a mountain and put down on paper his philosophy on strategy and combat. His insights into defeating one, ten, or even ten thousand resonate with the devops philosophy of ops at scale and consistent delivery of quality. I'll present some selections from his teachings that show everything old is new again and even from a cave 300 years ago there is wisdom we can use.
diff --git a/exampleSite/content/events/2016-boise/program/corey-quinn.md b/exampleSite/content/events/2016-boise/program/corey-quinn.md
new file mode 100644
index 000000000..3de5e0aa9
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/corey-quinn.md
@@ -0,0 +1,14 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Corey Quinn"
+type: "talk"
+---
+
+## This Conference Will Pay For Itself: Salary Negotiation for DevOps
+
+“I’m sure if I work hard, my contribution will one day be recognized and I’ll get a raise.” – Everyone At Some Point In Our Careers. The world is unfair; this talk won’t do much to fix that– but it will give insight from a hiring manager on how to maneuver within the world we currently inhabit.
+
+Discussing compensation is a taboo for many of us. We consider it “rude,” “not other people’s business,” or just not a comfortable conversation to have. Unfortunately, information asymmetry around how others are compensated enables many of us to be drastically underpaid compared to what we could be earning.
+
+In this talk, a hiring manager gives profoundly honest advice on how to ensure you’re being paid fairly for the market in which you work, how active career management is critical to your future, and why so many of us find the entire subject so uncomfortable. Topics covered include how to figure out what “market rate” for your area is, why it’s probably considerably more than you think it is, and selected techniques to help you earn more sooner rather than later without having to change your personality to do it.
diff --git a/exampleSite/content/events/2016-boise/program/dan-isla.md b/exampleSite/content/events/2016-boise/program/dan-isla.md
new file mode 100644
index 000000000..405d088b9
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/dan-isla.md
@@ -0,0 +1,13 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Dan Isla"
+type: "talk"
+---
+
+## NASA Jet Propulsion Lab and DevOps
+
+At the Jet Propulsion Laboratory, real-time analytics for data collected from the Mars Rover Curiosity is critical when millions of telemetry data points are received daily. Building portable containerized data systems and tools that can be continuously deployed enables our Systems Engineers and Data Scientists to quickly develop, analyze and share their visualizations and algorithms. With the AWS GovCloud region, export-controlled data can be securely stored and processed using the familiar AWS services and APIs that scale on-demand. Containers, DevOps, and high levels of automation are the most important concepts when building infrastructure at scale that can be robust and operated by just a few admins.
+
+DevOps is more than just automation and fancy tools and is really about culture change within the organization. At JPL and other Government agencies, legacy is everywhere from the apps to the ops; with the Analytics Cloud Services, we have successfully demonstrated ways to modernize legacy systems using containers to make them more secure and operable on modern infrastructure.
+In this talk, Dan will share how his team revolutionized Interplanetary Mission Operations and created a new paradigm for software development and collaboration at JPL.
diff --git a/exampleSite/content/events/2016-boise/program/darryl-bowler.md b/exampleSite/content/events/2016-boise/program/darryl-bowler.md
new file mode 100644
index 000000000..5a1df05ef
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/darryl-bowler.md
@@ -0,0 +1,18 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Darryl Bowler"
+type: "talk"
+---
+
+## From Theory to Practice – Developing DevOps Capability to Delivery Enterprise Level Products
+
+Putting theory into practice is one of the most difficult aspects when engaging a fast pace project. How do you implement new CI & CD processes and replace incumbent processes without impacting the flow and productivity of development & QA team. Enterprise delivery demands scale, consistency and repeatability, all of which DevOps promise to delivery. In the talk you will learn the 5 key areas you need to focus on
+
+The talk will be presented by Darryl Bowler who has firsthand experience of delivering enterprise grade products using DevOps capabilities, Continuous integration & delivery. In the talk the audience will learn the common pitfalls and the important keys areas that enable scale and flexibility without compromise of consistency and reuse. Topics will include
+
+* Why branching / merging strategy impacts delivery and release
+* Pitfalls and how to manage environments at scale
+* Configuration management across multi-tiered applications
+* Beyond pipeline views - Tailored & custom dashboards
+* Embedding quality in the process
diff --git a/exampleSite/content/events/2016-boise/program/dave-hahn.md b/exampleSite/content/events/2016-boise/program/dave-hahn.md
new file mode 100644
index 000000000..1b7c167f9
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/dave-hahn.md
@@ -0,0 +1,9 @@
+---
+City: "Boise"
+Year: "2016"
+title: "Dave Hahn"
+type: "talk"
+---
+
+## How Netflix Thinks about DevOps
+Netflix is considered a large DevOps environment. However, 'DevOps' isn't something that Netflix talks much about. If it's so key to the success of the organization, why don't we hear more about it? Netflix considers DevOps to be a result of our rigorous adherence to our culture -- not a cream you generously apply to problems. Culture is key, chaos is your friend, and trust is an absolute requirement.
diff --git a/exampleSite/content/events/2016-boise/program/dave-harrison.md b/exampleSite/content/events/2016-boise/program/dave-harrison.md
new file mode 100644
index 000000000..7bc7d9ca9
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/dave-harrison.md
@@ -0,0 +1,9 @@
+---
+City: Boise
+Year: 2016
+title: "Dave Harrison"
+type: talk
+---
+
+## Taking to the Mountains: Guerilla Methods to win your DevOps Battle
+Most of us know that – just as with Agile – people remain the biggest obstacle to instilling change management culture; you simply cannot buy DevOps as a package. For many organizations (the horses, not the unicorns!) the move to DevOps comes with unexpected bottlenecks. At times it seems like securing management buy-in – especially when there’s issues or delays – becomes the biggest obstacle. We’ll discuss a phased approach to building out support, beginning with sneaky guerilla methods and ending with a more direct, KPI- and business-objective-driven campaign to get the executive firepower you need to create your own “cultural revolution”.
diff --git a/exampleSite/content/events/2016-boise/program/gareth-greenaway.md b/exampleSite/content/events/2016-boise/program/gareth-greenaway.md
new file mode 100644
index 000000000..545a03538
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/gareth-greenaway.md
@@ -0,0 +1,14 @@
+---
+City: Boise
+Year: 2016
+title: "Gareth Greenaway"
+type: talk
+---
+
+## Managing Multiple SaltStack Environments for Fun & Profit
+
+One of the power features of SaltStack is the ability to segment Salt states into separate environments, minions can then be setup to only receive their states from specific environments. The most common use case for using multiple environments in Salt is to provide multiple versions of states, for example development and production environments. This can be extended to support other use cases, such as providing different environments for different projects or different clients. In this talk we'll explore a real world solution that will allow us to sanely support & manage multiple Salt environments. We'll look at various approaches that didn't work and why, and then at the final approach which uses various features of Salt to solve the problem.
+
+## Leaving an Open Source Project
+
+In the professional world when you decide to leave your job there is a whole process. Traditionally you'll begin to transition tasks you worked on to another employee, your various accounts are terminated, you'll go through an exit interview and then receive your final paycheck before being escorted from the building. But what happens when you decide to leave an open source project? Are you no longer a member of that community simply because you're no longer actively contributing? Can you easily come back to the project? This talk will hopefully answer these and other questions.
diff --git a/exampleSite/content/events/2016-boise/program/gerie-owen.md b/exampleSite/content/events/2016-boise/program/gerie-owen.md
new file mode 100644
index 000000000..51a2bb551
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/gerie-owen.md
@@ -0,0 +1,10 @@
+---
+City: Boise
+Year: 2016
+title: Gerie Owen
+type: talk
+---
+## DevOps and Groupthink: An Oxymoron?
+DevOps teams bring together specialists from disciplines with different views on what is most important which forms the basis for preventing groupthink. However, all closely-knit teams are susceptible to groupthink, a cultural attitude that implicitly rewards members whose striving for unanimity override their motivation to realistically appraise alternative courses of action. DevOps team members from different functional specialties may often defer to the expert in a particular realm to solve individual problems. Teams also recognize that they have to solve issues quickly and decisively, and may defer to the team member with the most authoritative voice.
+
+This presentation examines the development of groupthink within devops teams. It draws upon the research of Irving Janus, Daniel Kaheman and Carol Dweck to look at how biases and mindsets contribute to groupthink, and why groupthink invariably leads to poor decision-making. I’ll how groupthink can be managed using these theories. Then using Gloria Eoyang’s CDE theory, I’ll show what managers can do to positively influence groupthink behaviors. From this presentation you will learn how sustained groupthink can prevent the DevOps team from achieving its operational goals of agility and quick corrective action and you will learn to use a combination of defined process and prescriptive actions, as individuals and as a team both internally and externally.
diff --git a/exampleSite/content/events/2016-boise/program/jason-hand.md b/exampleSite/content/events/2016-boise/program/jason-hand.md
new file mode 100644
index 000000000..ed0b24309
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/jason-hand.md
@@ -0,0 +1,32 @@
+---
+City: Boise
+Year: 2016
+title: Jason Hand
+type: talk
+---
+
+## The Unrealized Role of Monitoring & Alerting
+
+In today's world, a company must be a "Learning Organization" in order to be successful and innovative. Learning from both failure and success, in order to implement small incremental improvements is critical. But until you implement and apply new information, you haven't truly "learned” anything and you certainly haven’t improved.
+
+According to the 2015 Monitoring Survey, most companies leverage metrics from monitoring and logging purely for performance analytics and trending. If high availability and reliability are important, they also leverage metrics to alert on fault and anomaly detection. Despite these “best practices”, the metrics are primarily only used as context to keep things “running” or return them back to "normal" if there’s a problem. Rarely is that data used as a method to identify areas of improvement once services have been restored.
+
+When an outage occurs to your system, you will absolutely repair and restore services as best you know how, but are you paying attention to the data from the recovery efforts? What were operators seeing during diagnosis and remediation? What were their actions? What was going on with everyone, including conversations? A step-by-step replay of exactly what took place during that outage.
+
+This “old-view” perspective on the purpose of monitoring, logging, and alerting leaves the full value of metrics unrealized. It fails to address what’s important to the overall business objective and it lacks any hope of seeking out innovation or disruption of the status quo.
+
+This talk will illustrate how to identify if your company is making the best use of metrics and ways to not only learn from failure, but to become a "Learning Company”.
+
+## The Benefit of a Systems Lens
+
+Understanding feedback through a systems lens has advantages. This pure feedback loop is more accurate, it moves us away from needless judgement, and it enhances accountability just to name a few. By taking a step back and examining the feedback and data we receive in three different ways, we can understand it much clearer.
+
+Those ways are:
+
+1. Are differences between the giver and receiver creating friction for the feedback?
+2. Is the feedback partly related to the differing roles between giver and receiver as it relates to the common “system”?
+3. Are processes, policies, physical environment, or other factors within the system reinforcing problems with the feedback?
+
+Allowing ourselves to view feedback from a “Systems Thinking” model, we can begin to look for patterns, understand the feedback loop with more accuracy, and identify contributing factors to both failure and success.
+
+This quick (IGNITE-style) talk will discuss feedback from a “Systems Thinking” perspective.
diff --git a/exampleSite/content/events/2016-boise/program/jean-bennett.md b/exampleSite/content/events/2016-boise/program/jean-bennett.md
new file mode 100644
index 000000000..cbf812ac0
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/jean-bennett.md
@@ -0,0 +1,9 @@
+---
+City: Boise
+Year: 2016
+title: Jean Bennett
+type: talk
+---
+
+## DevOps will Fail… How the Phoenix Project Simulation can help you Succeed
+Industry trends reveal that organizations are not realizing the enormous business benefits in adopting DevOps by failing to address ‘cultural and behavioral’ issues and inadequately addressing organizational change. Learn how The Phoenix Project business simulation can increase the velocity of your adoption, create buy-in, improve communication and collaboration skills between Dev and Ops, and capture concrete, shared, improvement actions aimed at creating success.
diff --git a/exampleSite/content/events/2016-boise/program/jeff-anderson.md b/exampleSite/content/events/2016-boise/program/jeff-anderson.md
new file mode 100644
index 000000000..415c7bb99
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/jeff-anderson.md
@@ -0,0 +1,9 @@
+---
+City: Boise
+Year: 2016
+title: Jeff Anderson
+type: talk
+---
+
+## New Docker Features for Orchestration and Clusters
+Docker has long been known for the familiar 'docker run' command, which spawns a single container based on a Docker image. But with the recently-added clustering features and services abstraction, Docker can now do much more. Users can create a cluster of Docker daemons and declare a desired state for their distributed application that will be maintained in the face of failures.
diff --git a/exampleSite/content/events/2016-boise/program/jonah-horowitz.md b/exampleSite/content/events/2016-boise/program/jonah-horowitz.md
new file mode 100644
index 000000000..cc7802634
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/jonah-horowitz.md
@@ -0,0 +1,10 @@
+---
+City: Boise
+Year: 2016
+title: Jonah Horowitz
+type: talk
+---
+
+## Configuration Management is an Anti-Pattern
+Configuration Management tools were a revolution when they first appeared. Gone were the days of every Sys Admin carrying around their own collection of Bash scripts to get things done. It's no surprise that they became so popular so quickly. That said, the age of Configuration Management is quickly coming to an end. Serverless and immutable infrastructure are the future.
+In this talk you'll hear from one of Netflix's CORE SREs about how we run on a mostly immutable infrastructure, all the ways that Configuration Management has failed over the years and why you should stop using it.
diff --git a/exampleSite/content/events/2016-boise/program/leonid-igolnik.md b/exampleSite/content/events/2016-boise/program/leonid-igolnik.md
new file mode 100644
index 000000000..5a02955d8
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/leonid-igolnik.md
@@ -0,0 +1,13 @@
+---
+City: Boise
+Year: 2016
+title: Leonid Igolnik
+type: talk
+---
+
+## DevOps @Scale
+Co-Presented with [Baruch Sadogursky](events/2016-boise/program/baruch-sadogursky/)
+
+Remember the times when one server was enough? And a guy named “sysadmin” was babysitting it along with his other duties of installing MS Office for everybody?
+For better or for worse, those times are long gone. Today, companies manage tens of thousands of servers and perform thousands of production changes per day.
+In this talk we will look at the resources, techniques and tools needed for managing DevOps at Scale and we will discuss the challenges that companies encounter when they hit it.
diff --git a/exampleSite/content/events/2016-boise/program/mary-younce.md b/exampleSite/content/events/2016-boise/program/mary-younce.md
new file mode 100644
index 000000000..a272e8aec
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/mary-younce.md
@@ -0,0 +1,6 @@
+---
+City: Boise
+Year: 2016
+title: Mary Younce
+type: talk
+---
diff --git a/exampleSite/content/events/2016-boise/program/matthew-barker.md b/exampleSite/content/events/2016-boise/program/matthew-barker.md
new file mode 100644
index 000000000..a8b5873e2
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/matthew-barker.md
@@ -0,0 +1,19 @@
+---
+City: Boise
+Year: 2016
+title: Matthew Barker
+type: talk
+---
+
+## What Goes in Must Come Out: Hidden Defects in your Software Application
+"Build quality in" is a core mantra of DevOps practices, yet development practices are blindly building defects into their applications en masse.
+
+You see, every software development organization on the planet has a software supply chain that is consuming a massive volume of open source and third-party components. In 2015, 11 million developers consumed over 30 billion components. The use of these components is accelerating innovation while at the same time introducing elective risks and costly rework.
+
+In June, Sonatype released its 2016 State of the Software Supply Chain Report. It is a deep analysis of development practices across 3,000 development organizations consuming and 25,000 applications. While the average organization in the study consumed 229,000 open source and third party software components, the study revealed:
+
+* 6.8% of components consumed included known security flaws, impacting the integrity of operations
+* Costs to remediate 10% of vulnerabilities across a large application portfolio can exceed $7,000,000
+* Older components have a 3x higher defect density
+
+But this discussion is not intended as a platform to shed light on bad practices; it is bringing greater awareness of building quality in. Attendees will gain new visibility as to what’s happening in their own software supply chains, receive industry benchmarks driving enhanced quality and security, and discover three core principles that can be applied to improving their DevOps practices.
diff --git a/exampleSite/content/events/2016-boise/program/peter-varhol.md b/exampleSite/content/events/2016-boise/program/peter-varhol.md
new file mode 100644
index 000000000..c55211b4b
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/peter-varhol.md
@@ -0,0 +1,19 @@
+---
+City: Boise
+Year: 2016
+title: Peter Varhol
+type: talk
+---
+
+## Talking to People: The Forgotten DevOps Tool: Peter Varhol, Dynatrace
+As we focus on how to how to best use JIRA, Hipchat, Slack, project management products, incident and defect tracking solutions, and a myriad of other software tools as a part of our development and delivery environment, we often lose sight of the most fundamental and powerful tool available – talking to people, to our team members, management, users, and other stakeholders.
+
+Rather than burying ourselves in tools and devices, software and search engines, we can do more for our overall application quality and delivery processes by simply talking to the people around us. While a focus on software may produce more data, knowing the thoughts, expectations, and ideas of the stakeholders will result in more innovative ideas as well as a filter for determining optimal solutions.
+
+Using the research of MIT researcher Sherry Turkle and others, this presentation uses the power of conversation to illustrate how we can improve our testing practices and results, for the good of all stakeholders. It illustrates how our conversations can be more powerful and directed than any software tool in determining and delivering on application quality and performance. Last, it examines the role of ChatOps tools in supplementing conversation with actionable ideas and automated responses to be a true real time response environment.
+
+Main takeaways:
+
+1. How a search for the perfect software tools may be preventing us from using our fundamental communication skills in a devops context.
+2. How talking to people in our project work is becoming a lost art.
+3. Why starting an active program of interpersonal interaction can improve your application quality and delivery right away.
diff --git a/exampleSite/content/events/2016-boise/program/seth-falcon.md b/exampleSite/content/events/2016-boise/program/seth-falcon.md
new file mode 100644
index 000000000..1dac20728
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/program/seth-falcon.md
@@ -0,0 +1,11 @@
+---
+City: Boise
+Year: 2016
+title: Seth Falcon
+type: talk
+---
+
+## IC to VP: An Experience Report on Becoming a Manager
+How do you stay at your job for six years and maintain the feeling of I-have-no-idea-what-I’m-doing (and I’m going to do it anyway)? This is my story of joining a company as an individual contributor (IC), working across the code base, leading a scaling project, growing a team to launch a new product, and ending up as VP of Engineering. My aim is to share things I’ve learned on this journey and highlight specific things that can help ICs and managers be more effective.
+
+Who should come to this talk? Engineers interested in engineering management will get to hear a first-hand account of becoming a manager. Engineering managers who are interested in becoming Directors will get to hear about my transition from managing ICs to managing managers. The management lessons are not engineering specific — though that is my context — and I expect are relevant elsewhere. More experienced leaders and executives should come and tell me all the parts I’ve got wrong.
diff --git a/exampleSite/content/events/2016-boise/propose.md b/exampleSite/content/events/2016-boise/propose.md
new file mode 100644
index 000000000..cfd67db0b
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/propose.md
@@ -0,0 +1,35 @@
++++
+date = "2016-05-03T13:24:36-06:00"
+title = "Propose A Session"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk : these are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, ignite, etc.)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
diff --git a/exampleSite/content/events/2016-boise/speakers.md b/exampleSite/content/events/2016-boise/speakers.md
new file mode 100644
index 000000000..e5a8a253b
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/speakers.md
@@ -0,0 +1,7 @@
++++
+date = "2016-05-03T13:24:36-06:00"
+title = "Speakers"
+type = "speakers"
+
+
++++
diff --git a/exampleSite/content/events/2016-boise/sponsor.md b/exampleSite/content/events/2016-boise/sponsor.md
new file mode 100644
index 000000000..3092f54a1
--- /dev/null
+++ b/exampleSite/content/events/2016-boise/sponsor.md
@@ -0,0 +1,102 @@
++++
+date = "2016-05-03T13:24:36-06:00"
+title = "Sponsor Us"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+
+All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
+
+
packages
+
Bronze
+
Silver
+
Gold
+
Diamond
+
+
+
Price (USD)
+
$1,000
+
$2,000
+
$3,000
+
$10,000
+
+
+
included tickets
+
2
+
3
+
5
+
8
+
+
+
logo on event website
+
+
+
+
+
+
+
logo on emails
+
+
+
+
+
+
+
table space
+
shared swag table
+
1/2 table
+
Full table
+
Full table
+
+
+
1 minute pitch
+
+
+
+
+
+
+
meal sponsorship
+
+
+
+
+
+
+
pay online
+
+
+
+
+
+
+
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, {{< email_organizers >}}.
+
+
+
+ {{< event_link page="registration" text="Register to attend the event!" >}}
+
+
+
+
+
+ Program
+
+
+ View the {{< event_link page="program" text="program." >}}
+
+
+
+
+
+ Speakers
+
+
+ Check out the {{< event_link page="speakers" text="speakers!" >}}
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+{{< event_twitter devopsdaysboise >}}
diff --git a/exampleSite/content/events/2016-boston/conduct.md b/exampleSite/content/events/2016-boston/conduct.md
new file mode 100644
index 000000000..a8cb8ab94
--- /dev/null
+++ b/exampleSite/content/events/2016-boston/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-07T08:37:22-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-boston/contact.md b/exampleSite/content/events/2016-boston/contact.md
new file mode 100644
index 000000000..18138f87a
--- /dev/null
+++ b/exampleSite/content/events/2016-boston/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-07T08:37:22-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-boston/location.md b/exampleSite/content/events/2016-boston/location.md
new file mode 100644
index 000000000..59c6ce09d
--- /dev/null
+++ b/exampleSite/content/events/2016-boston/location.md
@@ -0,0 +1,19 @@
++++
+date = "2016-05-07T08:37:22-05:00"
+title = "location"
+type = "event"
+
++++
+
+
Boston Park Plaza
+
+Thursday, August 25th - Friday, August 26th, 2016.
+Boston Park Plaza
+50 Park Plaza at Arlington Street | Boston, MA 02116-3912
+
+
+
If you spend most of your time in places like Portland or Brooklyn, our metro will feel familiar,
+with its bike share stations, beautiful riverfront, and numerous craft brewery tap-rooms with food
+trucks in their parking lots. (Hey, a good excuse to stay the weekend after!)
Title:
+ Implementing Metrics-Driven DevOps: Why and How!
+
+
+
Description:
+
+
+ How can we detect a bad deployment before it hits production? By automatically looking at the right architectural metrics in your CI/CD and stop a build before its too late. Lets hook up your test automation with app metrics and use them as quality gates to stop bad builds early!
+
+ Mentoring and teaching are key to professional development. More organizations are adopting a "75% technical / 25% manager" role to enable career coaching and growth. Good, engaged, technical management can completely change the happiness of an entire organization.
+
+ Diversity and inclusion have become hot topics in technology, but you may not know how to you can make a difference. However, this talk will help you understand that, no matter your background, you have privilege and can lend it to marginalized groups in tech.
+
+ "Serverless" apps are built not as contained services but rather as lean handlers that respond to events. Not just the server but the entire application platform is offloaded to "the cloud", meaning a more manageable application architecture that can scale dynamically as your application grows.
+
Title:
+ This Conference Will Pay For Itself: Salary Negotiation for DevOps
+
+
+
Description:
+
+
+ "I'm sure if I work hard, my contribution will one day be recognized and I'll get a raise." -- Everyone At Some Point In Our Careers.
+The world is unfair; this talk won't do much to fix that-- but it will give insight from a hiring manager on how to maneuver within the world we currently inhabit.
+
+ Are you sitting in front of a cluster right now? Surely you are typing at a laptop running a cluster just like the ones you have in production. And the process of moving your efforts from the laptop up to production, is it silky smooth? Maybe not. Let's talk about why.
+
+
+
+ When Docker burst on the scene in 2013, one promise that excited both developers and operations people alike was the idea that a dev would create a container on her laptop that could then be shipped right up to production. Three years later, most people have realized that it may not be that simple.
+
+In a world where we are building microservices and distributed systems, how can you ensure that the laptop you are typing at now is a step towards production-ready software and not a distraction from it? Let's get deep down and dirty into the art of constructing useful clusters on our primary development/operations control machines and the challenges we face in the process.
+
Title:
+ Continuous Improvement and Development Drives Successful Recruiting: DevOps Style
+
+
+
Description:
+
+
+ In my talk, I will share my experiences on how to successfully grow and develop
+ technical teams. My practices are designed to align employer's/employee's
+ values and goals. I will provide specific and actionable steps that can be
+ adjusted to fit your organizations' specific needs.
+ Grow together!
+
Title:
+ Redefining collaboration norms as your company grows
+
+
+
Description:
+
+ DevOps is all about collaboration, but what does that mean at a growing
+ company? Abstractions tend to wall us off from each other, but they also
+ provide the opportunity to experiment (e.g., don't need to wait for ops to
+ spin you a server up to try something out). As companies grow,
+ communication overhead increases. As your organization grows, different
+ techniques are needed to prevent everyone from getting bogged down.
+
+ Learning any new tool can be intimidating, particularly if your company
+ doesn’t encourage experimentation. This tutorial is designed to get you
+ comfortable writing Ansible playbooks for routine operations tasks in just
+ two hours, even if you’ve never heard of it before.
+
+ The first 30 minutes of the workshop will position you to evaluate Ansible by
+ relating it to the broader ecosystem of devops tools. You’ll learn the key
+ concepts that define Ansible workflows (inventories, playbooks, roles, and
+ variables) and how they compare to concepts from other systems. By the
+ break, you’ll understand Ansible’s strengths and weaknesses relative to other
+ options, giving you the information you need to decide whether it’s right for
+ your team, or to sell it effectively to your manager.
+
+ The second portion of the workshop will consist of live Ansible exercises.
+ You’ll work your way up from a “Hello, World” playbook on localhost to
+ deploying and managing a multi-server microservice application (via Vagrant).
+ Along the way, you’ll learn about the most important Ansible modules, the fine
+ points of Ansible repository structure, and the wider world of Ansible Galaxy.
+ And since Ansible’s greatest weakness is its flexibility, we’ll also show you
+ what not to do in order to avoid costly refactoring in the future! By the close
+ of the workshop, you will be comfortable using Ansible to automate routine
+ operations tasks, and you’ll know where to start with Ansible for
+ infrastructure-as-code.
+
+ NOTE: A laptop with internet access, git, VirtualBox, and Vagrant are
+ required for the second portion of the tutorial. Please install these tools in
+ advance. Additionally, it’s recommended to come to this tutorial familiar with
+ at least two of git, ssh, and Vagrant. On the other hand, you don’t have to
+ have used configuration management previously to benefit from this
+ workshop.
+
Title:
+ If You Build it, They Will Come: But Will They Stay?
+
+
+
Description:
+
+
+ How do you create the best devop you can be? When building a devop, we usually
+ think about our technical skills but often forget aspects of our personal brand
+ including relationship building, reputation, communication... all on top of the
+ awesomeness you already can do. Let's talk about building the 'well rounded
+ devop'. After we've built the devop of our dreams, how do you keep such awesome
+ devops working in your company? Based on Jill's experience working with many
+ engineers as well as perspectives from small (DigitalOcean), medium
+ (Rackspace), and large (IBM) companies we'll discuss what it takes to become a
+ sparkly devop unicorn.
+
+ I've found when working with many developers and operations folks that there is a real lack of understanding with regards to how TLS/SSL works. This talk was originally given internally at Braintree to help folks understand this important part of the stack.
+
Title:
+ Telling your Story: Speaking for Non-Speakers
+
+
+
Description:
+
+
+ Many conference attendees come year after year without giving presentations. The sense that there's a high bar for perfection is pervasive, and people are afraid of being "wrong." Everyone has a story to tell about a problem they've solved or issues they've tackled.
+
+
+
+ The intent of this talk is to define the place for business units at DevOps table to improve overall organization communication and tech team efficiency, including monitoring strategy, post-mortems, chatops and other DevOps-centric processes.
+
+ Everyone is affected by being on call in different ways. A rotation that seems "equal" may not be "equitable," namely, it may place significantly more burden on some employees than others. I'll discuss how to make everyone comfortable, happy, and not burnt out
+
Title:
+ Building an enterprise git repository (the hard bits!)
+
+
+
Description:
+
+
+ Source code: Just put it in git, right? Scale? Github!
+
+1000's of repos? No problem! Bitbucket Server!
+
+Now: Add PCI & SOX.. Audit. SSO. SSH key management. DR. Geo diversity.
+
+This starts where the vendor stop- workflows to keep work moving, security & audit to ensure code integrity.
+
+
+ We all know and love DevOps. But how do we bring DevOps to the ultimate waterfall enterprise (the US Government)? It's not easy and we're not out of the woods yet. I'd like to share with you the story of my journey and where we are heading so that others may follow in our footsteps.
+
+ Ready to leverage your Docker skills? Come to this session to see how your current Docker skill set can be easily mapped to Kubernetes concepts and commands. And get ready to deploy your containers in production! This hands-on lab will cover from basics to advanced Kubernetes features.
+
+ How do you start young people out with STEM skills, and DevOps in particular? Make it useful, make it fun!
+
+I taught my nine year old nephew to take his Minecraft game to a whole new level by showing him how to administer a remote Minecraft server, a Docker container running on Digital Ocean.
+
+ Code review has always been used by developers, recently operations has started as well. How is it different when operators are reviewing code that has an operations impact? How can it be optimized? Our team has been reviewing ops code for years, and I'm here to share the lessons we learned.
+
+ "Serverless". It is already being called the buzzword of 2016. Steve is going to bring "serverless" back to reality by showing how Bustle has built a fully serverless application platform. Real production examples handling millions of API calls a day. You will leave knowing if the hype is justified.
+
+ It's hard to write documentation that anyone can get excited about. This is true for projects aimed at beginners, but it goes double for projects and writing aimed at intermediate/expert programmers. Find out how to write documentation that *everyone* would want to read and can understand.
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, drop us an email: {{< email_organizers >}}.
+
+
+
+
+
+DevOpsDays Boston is a self-organizing conference for practitioners that
+depends on sponsorships. We do not have vendor booths or sell product
+presentations. Sponsors have the opportunity to have short elevator pitches
+during the program and will get recognition on the website and social media
+before, during and after the event. Sponsors are encouraged to represent
+themselves by actively participating and engaging with the attendees as peers.
+Any attendee also has the opportunity to demo products/projects as part of an
+open space session, but this is not 'that kind of conference' and heavy
+marketing will probably work against you when trying to make a good impression
+on the attendees.
+
+
+
+The best thing to do is send engineers to interact with the experts at
+DevOpsDays on their own terms.
+
+
+
+
+
Packages
+
Platinum 10000 USD
+
Gold 8000 USD
+
Silver 5000 USD
+
+
+
Included passes
+
10
+
8
+
5
+
+
+
Table space
+
✅
+
✅
+
+
+
+
Logo on DevOpsDays Boston event website and email
+
✅
+
✅
+
✅
+
+
+
Logo on digital banners
+
Large
+
Medium
+
Small
+
+
+
Sponsored breakout room
+
✅
+
+
+
+
+
Mentions through social media
+
✅
+
✅
+
✅
+
+
+
+
+
+There are also opportunities for exclusive special sponsorships. We'll have
+sponsors for an evening social with special privileges for the sponsors of this
+event. If you are interested in special sponsorships or have a creative idea
+about how you can support the event, drop us an email: {{< email_organizers >}}.
+
+
+
+## POLÍTICA ANTI-ASSÉDIO
+
+DevOpsDays é dedicado a fornecer uma experiência de conferência livre de assédio para todos, independentemente do sexo, orientação sexual, deficiência, aparência física, tamanho do corpo, raça ou religião. Nós não toleramos o assédio dos participantes da conferência, sob qualquer forma. Linguagem sexual ou imagens não é adequado para qualquer local da conferência, principalmente palestras. Os participantes da conferência que violem estas regras podem ser sancionados ou expulsos da conferência sem um reembolso a critério dos organizadores da conferência.
+
+O assédio inclui comentários ofensivos verbais relacionadas com o género, orientação sexual, deficiência, aparência física, tamanho corporal, raça, religião, liguagem ou imagens sexuais nos espaços públicos, intimidação deliberada, perseguição seguida de fotografia ou gravação assediosa, sustentada interrupção das conversações ou outros eventos, inadequado contato físico e olhar sexual indesejada. Os participantes solicitados a interromper qualquer comportamento de assédio devem cumprir imediatamente.
+
+Expositores em seus espações reservados, patrocinadores ou fornecedores, parceiros ou atividades similares também estão sujeitas à política anti-assédio. Em particular, os expositores não devem usar imagens, atividades ou outro material de conteúdo sexualizados. Integrantes das diversas equipes (incluindo voluntários) não devem usar roupas/uniformes/vestimenta sexualizadas, ou de outra forma criar um ambiente sexualizado.
+
+Se um participante se envolve em comportamento de assédio, os organizadores da conferência podem tomar todas as medidas que considerem adequadas, nomeadamente alertando e/ou expulsando o autor da conferência com nenhum reembolso.
+
+Se você está sendo assediado, ao perceber que alguém está sendo assediado, ou tem quaisquer outras preocupações correlatas, entre em contato com um membro da equipe da conferência imediatamente.
+
+Os organizadores da Conferência podem ser identificados por crachás e camisas específicos. Os organizadores da conferência ficarão felizes em ajudar os participantes a contatar a equipe de segurança do local ou agentes da lei local ou ajudar aqueles que experimentam o assédio para se sentirem seguros durante a conferência. Nós valorizamos a sua participação.
+
+Esperamos que os participantes permaneçam aderentes ao código de conduta em todos os locais de conferência e eventos sociais relacionados com a conferência.
+
+## CÓDIGO DE CONDUTA
+
+I. Eu sou um participante na devopsdays, aprendendo e compartilhando com outros devopsdays participantes em um esforço para melhorar a mim mesmo e minha indústria. Eu colaborativamente crio experiências com outros participantes. Estou preparado para dar a minha energia, presença e sensibilidade para criar a melhor experiência possível para mim e para os outros.
+
+II. Estou vindo para devopsdays para interagir com as pessoas. Eu entendo que as imagens e linguagem que é sugestivo ou depreciativa vai ofender e fazer as pessoas desconfortáveis. Eu também entendo que as pessoas podem ter limites e sensibilidades diferentes da minha. Vou aceitar sem questionar quando informado de que algo é ofensivo ou inaceitável no contexto do evento devopsdays.
+
+III. Eu nunca vou assediar, perseguir intencionalmente ou ofender outro participante, independentemente do sexo, orientação sexual, deficiência, aparência, tamanho do corpo, raça ou religião e eu não vou tolerar outro participante sendo assediado ou ofendido. Caso eu tome conhecimento de que alguém esteja desconfortável ou inseguro, vou notificar aos organizadores do evento devopsdays sobre aqueles que potentialmente estejam promovendo ofenças.
+
+IV. Se estou ofendido ou incomodado, vou informar as pessoas em que confio ou ao meu redor que me fazem sentir segura e aos organizadores do evento. Se eu me sinto seguro, a meu critério, vou informar àqueles ofensores de suas específicas atitudes com a esperança de que a outra parte está bem-intencionada, mas é ignorante; porém sob nenhuma obrigação de fazê-lo.
+
+V. Eu entendo que as pessoas são diferentes e eu tentarei ser complacente com outras ações em nível de sua verdadeira intenção, mas a minha prioridade é minha segurança e a segurança dos outros. Vou agir sem hesitação ou reserva até que não haja segurança de todas as partes.
+
+VI. Eu confio que os organizadores do devopsdays e os participantes colaborativamente criarão a melhor experiência possível para todos os envolvidos, como eu quero e também farei. Acredito devopsdays é de empoderamento de pessoas e não vou esquecer que eu tenho o poder para criar um ambiente seguro e acolhedor. Se eu ou qualquer outro participante viole este Código de Conduta do evento, espero que os organizadores da conferência tomem atitudes adequadas que protejam os participantes, incluindo expulsando aqueles que violem e entre em contato com as autoridades apropriadas para medidas cabíveis.
diff --git a/exampleSite/content/events/2016-brasilia/conduct.md b/exampleSite/content/events/2016-brasilia/conduct.md
new file mode 100644
index 000000000..68277b11c
--- /dev/null
+++ b/exampleSite/content/events/2016-brasilia/conduct.md
@@ -0,0 +1,42 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-brasilia/contact.md b/exampleSite/content/events/2016-brasilia/contact.md
new file mode 100644
index 000000000..bf9f682fc
--- /dev/null
+++ b/exampleSite/content/events/2016-brasilia/contact.md
@@ -0,0 +1,21 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+
+
+Team for funding and publishing: Aline Hubner, Dirceu Silva, Eustáquio Guimarães, Diego Aguilera, Rogério Fernandes Pereira
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-brasilia/location.md b/exampleSite/content/events/2016-brasilia/location.md
new file mode 100644
index 000000000..5834cad4b
--- /dev/null
+++ b/exampleSite/content/events/2016-brasilia/location.md
@@ -0,0 +1,32 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+# Local
+
+### Parque Cidade Corporate's Convention Center
+
+**Address**:
+
+- *Centro de Convenções*
+ Edifício Parque Cidade Corporate
+ Setor Comercial Sul (SCS), quadra 9, bloco A,
+ Asa Sul, Brasília/DF
+
+The *Convention Center* is located in Asa Sul, *Plano Piloto*, Brasília/DF and nearby it has:
+
+- Hotels (in Hotel Sector South / SHS)
+- Restaurants and malls (in the Commercial Sector South / SCS)
+- Points of interest (such as the City Park, TV Tower, Craft Fair/*Feira da Torre*, Esplanade of Ministries, The Three Powers Square etc)
+- Hospitals (such as Hospital Medical Sector South / SMHS)
+- in the event building: there are also restaurants and paid parking (*we're trying to get discounts for the participants of the event*)
+
+
+Below a reference map:
+
+{{< event_map >}}
diff --git a/exampleSite/content/events/2016-brasilia/program.md b/exampleSite/content/events/2016-brasilia/program.md
new file mode 100644
index 000000000..ba3764399
--- /dev/null
+++ b/exampleSite/content/events/2016-brasilia/program.md
@@ -0,0 +1,486 @@
++++
+City = "Brasília"
+Year ="2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+ "Comparar sistema de containers (engine) Docker e Rkt. São dois grandes projetos, com abordagens diferentes que realmente vale comparar qual é mais adequado para você".
+
+
+ Fernando Ike
+
+
+ OpenShift Intro
+
+
+
+ Uma discussão sobre OpenShift e suas principais funcionalidades.
+
+
+ Gustavo Luszczynski
+
+
+ GitLab CI + Rancher
+
+
+
+ Pipeline de integração contínua do GitLab (GitLab-CI) integrado à plataforma de gerenciamento de containers Rancher.
+
+
Title:
+Produção nove vezes ao dia - Como um time da Rackspace torna isso possível?
+
+
+
Description:
+
+
+Vamos apresentar quais técnicas e ferramentas são usadas no nosso time para garantir que as entregas em produção de um projeto com 5 anos de vida tenham valor e qualidade e sejam feitas 9 vezes ao dia, 5 dias por semana, 12 meses ao ano. Espere ouvir sobre pipeline, testes, automação, revisão de código, branch based development, multiple single page applications, Pikachu, ChatOps, Hackdays e feature toggles.
+
Title:
+Docker na Globo.com: Usando o tsuru para escalar milhares de containers em centenas de maquinas
+
+
+
Description:
+
+
+O objetivo dessa palestra é mostrar como a Globo.com usa docker como a principal forma de deploy de aplicações para produção usando o PaaS tsuru desenvolvido internamente como um projeto completamente open-source. Vamos ver na prática como o tsuru faz o scheduling de containers Docker e de VMs, como é feito o tratamento automático de falhas e deploys sem nenhum downtime. Além disso, vamos ver um números e informações sobre como a Globo.com usa o tsuru para proporcionar um ambiente de deploy seguro onde quase 1000 containers Docker são recriados diariamente. O tsuru é um PaaS open-source e mais informações sobre ele podem ser encontradas em https://tsuru.io/ e https://github.com/tsuru/tsuru.
+
+Modern software development process is spread across many tools. Every tool covers a part of the whole process. This talk highlight GitLab’s open set of tools for the software development lifecycle, from idea to production, through chat, issues, planning, merge request, CI, and CD.
+
Title:
+The Deploy Master: From Basic to Zero Downtime, Blue/Green, A/B, and Canary
+
+
+
Description:
+
+
+The “deploy moment” is an occasion that still gives many developers the shivers. But it shouldn’t be this way (at least not every time). Luckily enough, we have tools and processes today that enable us to turn the deploy moment into a usual activity.
+
+
Check out this session to learn how we can evolve our Java deployment process from the very basic to zero downtime and then apply some very interesting strategies such as blue/green, A/B, and Canary deployments.
+Falaremos um pouco sobre a produto Swarm da Docker que foi remodelado e agora seu uso de cluster é muito mais simples. Configurar um ambiente de produção nunca foi tão fácil. Falaremos de como iniciar serviços e como subir esse ambiente em poucos comandos.
+
Title:
+Implementando DevOps em nossos clientes no Vale do Silício: 5 práticas comprovadas para acelerar a mudança de cultura
+
+
+
Description:
+
+
+Mudança de cultura é um dos maiores desafios para a adoção de DevOps. A Daitan tem contribuído e também aprendido com a adoção de DevOps em nossos clientes no Vale do Silício já há alguns anos, em dezenas de projetos. Nesta conversa, compartilharemos 5 práticas que em nossa experiência prática mostraram-se úteis para aproximar os times de Dev e Ops, desde a construção criteriosa de objetivos para os times, até ferramentas que aumentam a interação e diminuem o atrito entre esses grupos.
+
+A palestra consistirá na apresentação de arquiteturas de referência para a implantação de um sistema de gestão centralizada de logs com o ELK abordando vantagens e desvantagens de cada arquitetura, e apresentar o case da Dataprev mostrando a arquitetura adotada, volumes e tipos de logs tratados.
+
+Essa palestra vai iniciar o ouvinte na cultura DevOps, o objetivo é fazer com que os iniciantes entendam como surgiu o termo, quem foram os idealizadores da ideia, quais as motivações para criação de tal movimento, como ele se organiza e também mostrar como funciona a comunidade em volta da iniciativa.
+
Title:
+Começando com tudo: Rancher Convoy-NFS, Proxy, Private Registry e Catalog
+
+
+
Description:
+
+
+Mostrar a importância destes 4 itens itens básicos, que são pilares para o início da adocação da cultura dos containers e do desenvolvimento do processo de DevOps nas organizações.
+
Title:
+O início da infraestrutura como código no Tribunal de Contas da União
+
+
+
Description:
+
+
+Nesta apresentação iremos compartilhar nossa experiência com “Infra as Code”, Cultura DevOps e em especial o processo de automação de nossa infraestrutura utilizando Puppet no Tribunal de Contas da União.
+
+Durante os mais de 10 anos de existência do Puppet, a sua linguagem de modelagem vem evoluindo e acrescentando cada vez mais funcionalidades e recursos.
+
Veremos como e porque o Puppet foi deixando de lado inspirações vindas da orientação a objetos, partir para composição ao invés de herança e recebendo influência de linguagens funcionais também.
+
Além disso, veremos como e porque a implementação do Puppet que inicialmente era apenas em Ruby MRI, hoje utiliza uma combinação de JRuby, Clojure e Java e está passando por uma reimplementação em C++.
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal:
+
+* fill in the form below (questions only in Portuguese for now)
+
+
+
+
diff --git a/exampleSite/content/events/2016-brasilia/registration.md b/exampleSite/content/events/2016-brasilia/registration.md
new file mode 100644
index 000000000..9e12f87a3
--- /dev/null
+++ b/exampleSite/content/events/2016-brasilia/registration.md
@@ -0,0 +1,14 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "registration"
+type = "event"
+draft = true
+
+
++++
+
+
It is finished the sponsorship program for this event!
+
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+
DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists.
+
Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers.
+
Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
Packages
+
Sponsor group
+
+
+
Supporter
+
Bronze
+
Silver
+
Gold
+
+
+
Included tickets
+
2
+
4
+
6
+
8
+
+
+
Releases on website and communities
+
-
+
-
+
Yes
+
Yes
+
+
+
Distribution of flyers
+
-
+
-
+
Yes
+
Yes
+
+
+
logo on event website
+
Yes
+
Yes
+
Yes
+
Yes
+
+
+
logo on badges
+
Yes
+
Yes
+
Yes
+
Yes
+
+
+
logo on event posters
+
Yes
+
Yes
+
Yes
+
Yes
+
+
+
table and banner next to coffee break table
+
-
+
-
+
Yes
+
Yes
+
+
+
1 minute pitch to full audience between talks (if it's the case including streaming audience)
+
-
+
Yes
+
Yes
+
Yes
+
+
+
1 minute pitch to full audience in the Opening Welcome
+
+
+**For the first time, DevOpsDays is coming to {{< event_location >}}!**
+
+
+ {{< event_logo >}}
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-capetown/conduct.md b/exampleSite/content/events/2016-capetown/conduct.md
new file mode 100644
index 000000000..6e48add21
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-07T09:47:20-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-capetown/contact.md b/exampleSite/content/events/2016-capetown/contact.md
new file mode 100644
index 000000000..bfa6e7c2e
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-07T09:47:20-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-capetown/location.md b/exampleSite/content/events/2016-capetown/location.md
new file mode 100644
index 000000000..3b17ed706
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/location.md
@@ -0,0 +1,15 @@
++++
+City = "Cape Town"
+Year = "2016"
+date = "2016-05-07T09:47:20-05:00"
+title = "location"
+type = "event"
+
++++
+
+The conference will take place {{< event_start >}} and {{< event_end >}} at the DoubleTree Hilton in Woodstock, Cape Town!
+
+
+
+
+There are plenty of hotel options in the immediate area, as well as a short bus ride or Uber ride away.
diff --git a/exampleSite/content/events/2016-capetown/program.md b/exampleSite/content/events/2016-capetown/program.md
new file mode 100644
index 000000000..1b07ae428
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/program.md
@@ -0,0 +1,346 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
In July 2015, Nomanini got an order to produce thousands of a hardware point of sale terminal that only existed in a sales pitch. Some might have called it vaporware - we called it a challenge.
+
+Using practices honed during our first four years of building and deploying hardware, firmware and software we were able to launch our second product, from nothing, in less than six months.
+
+This talk will cover our small teams' big lessons learned while designing hardware and manufacturing at scale, and running a highly available transaction backend.
Title: Where are we going and how did we get here?
+
+
+Abstract: The term Devops was coined in 2008 as a
+tongue-in-cheek moniker for the process of getting developers and operations
+people to speak to each other. From those humble origins, it has today
+blossomed into a worldwide phenomenon, encompassing everything from software
+development methodologies, enterprise software packages, training,
+certifications, and more. It seems like everywhere you look, Devops is there -
+but what is it, and what does it mean?
+
+
+In this talk we'll get back to basics and examine the living history of Devops,
+including the context from which the movement came to exist, how it has evolved
+until today, and where we're potentially headed in the next few years. Along
+the way we'll meet some colourful characters, cut through the marketing jargon,
+and get to the essence of Devops itself.
+
Change is hard! Everyone always talks about new shiny tools and “Devops” but what happens when you have a product that does billions of pageviews with teams that span multiple continents and timezones with more than a few hundred engineers (2000+ total employees).
+
+In this talk David will highlight some of the challenges OLX experienced with a recent move from high spec physical servers to running container based orchestration on AWS using versioned infrastructure. He also touches on how we dealt with keeping our teamwork great as well as the platform architecture.
+
Join me as I tell you the story of Jane, a rockstar developer with a great idea that could breathe new life into her company! That is, if she doesn’t table-flip trying to figure out HOW and WHERE to deploy her great idea. Cloud? PasS? Docker? Follow Jane as she descends into the fiery depths of infrastructure-complexity hell. If only a Habitat plan.sh could come together to save the day...
Do you know what your infrastructure is doing? Does it sometimes end up phoning you awake in the dead of the night? This talk aims to give a whirlwind tour of some common monitoring approaches, some common mistakes, along with imparting some general hard-earned wisdom.
So your organisation is successful at what they do? Great! That means that it is time to grow. More customers, more services, more engineers. The DevOps movement has brought focus to the value of alignment between development and operations. In this talk Noa Resare, Production Engineer at Facebook, will talk about what DevOps at scale can teach organisations of all sizes.
Vault is a free and open source tool that disrupted the security software industry since its announcement in 2015. Due to its innovative architecture, Vault is highly scalable, incredibly flexible, operationally secure, and designed to fit almost any organization. In addition to behaving like an encrypted key-value store (like encrypted Redis ), Vault's dynamic secret backends are capable of generating database login credentials on demand, Amazon IAM users, and even act as a full certificate authority! Vault handles the leasing, key revocation, key rolling auditing, and more. Vault is truly a pleasure to work with as both an operator maintaining the Vault and a developer interacting with it. This live-demo will provide a 360-view of Vault, following the story of an evolving startup and their secret management solution.
Code review has been shown to help developers produce better code. It can also help SREs run more reliable systems. Our ops team is fanatic about using code review and representing our infrastructure as code so that code review can be leveraged. In this presentation I will show how we use code review to manage our infrastructure, modify and create systems, administer services, etc. I'll discuss why we use code review for our operations work, and where we get value from it. I'll show the path we took to get here, what actions couldn't be piped through code review, and what we're going to next.
The new swarm features in docker make cluster setup and deployment feel to easy. Though in this case the cake is not a lie. In this talk Tim will show how simple it is to start a cluster with networking and how to deploy a fault tolerant db and application to it.
+
+
diff --git a/exampleSite/content/events/2016-capetown/propose.md b/exampleSite/content/events/2016-capetown/propose.md
new file mode 100644
index 000000000..bec190530
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/propose.md
@@ -0,0 +1,39 @@
++++
+date = "2016-05-07T09:47:20-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+
+### As this is the first Cape Town event, we cannot guarantee the ability to contribute to flight & accomodation for speakers yet. This might change, please indicate if your company can cover your costs, contribute a portion or none at all.
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice.
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+- _no third-party submissions_: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
+- _original content_: the talk should have been created by yourself and not copied from another person's one.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-capetown/registration.md b/exampleSite/content/events/2016-capetown/registration.md
new file mode 100644
index 000000000..6b7d39d5b
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/registration.md
@@ -0,0 +1,16 @@
++++
+City = "Cape Town"
+Year = "2016"
+date = "2016-05-07T09:47:20-05:00"
+title = "registration"
+type = "event"
+
++++
+### Details
+{{< event_start >}} - {{< event_end >}}
+
+
+### For bulk or corporate attendance of 5 tickets or more
+Please {{< event_link page="contact" text="get in touch with the organizers" >}} for a discount.
+
+
diff --git a/exampleSite/content/events/2016-capetown/speakers.md b/exampleSite/content/events/2016-capetown/speakers.md
new file mode 100644
index 000000000..8e8e2e0d1
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-capetown/sponsor.md b/exampleSite/content/events/2016-capetown/sponsor.md
new file mode 100644
index 000000000..0f577782a
--- /dev/null
+++ b/exampleSite/content/events/2016-capetown/sponsor.md
@@ -0,0 +1,175 @@
++++
+City = "Cape Town"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+Thank you for being here, and for considering sponsorship of Cape Town's first DevOpsDays! Sponsors are what makes community events like this possible. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}. Gold, Silver, and Bronze packages are detailed below.
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+All sponsors get a full table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+Please do not hesitate to reach out to us at {{< email_organizers >}} if you have any questions we can answer for you.
+
+
+
+## Sponsorship Levels
+### Platinum Sponsorship (Sold Out)
+
+
+
Details
+
+
+
+
+
Custom package
+
+
+
+
+
+
+### Gold Sponsorship (R75,000)
+
+
+
Details
+
Sponsor Now
+
+
+
+
+
4 tickets to the event
+
Logo on DevOpsDays Cape Town event website
+
Logo on event t-shirt
+
Branded items for goodie bag
+
Logo on all DevOpsDays email communication
+
Logo and short, soundless video playing on screens outside conference hall
+ {{< event_link page="propose" text="Propose a talk!" >}}
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ Check out the {{< event_link page="sponsor" text="sponsors!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+{{< event_twitter devopsdayscpt >}}
diff --git a/exampleSite/content/events/2016-chicago/conduct.md b/exampleSite/content/events/2016-chicago/conduct.md
new file mode 100644
index 000000000..39482f9a4
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/conduct.md
@@ -0,0 +1,49 @@
++++
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+* Email address for organizers: {{< email_organizers >}}
+* Phone number for organizers: Matt Stratton (312) 361-7611
+* Local law enforcement: City of Chicago Police - call 911
+* Sexual assault hotline: Rape Crisis Hotline (888) 293-2080
+* Medical Emergency: Call 911
+* Local taxi companies:
+ * Chicago Carriage Cab (312) 326-2221
+ * Flash Cab (773) 561-4444
+ * Yellow Cab (312) 829-4222
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
+
diff --git a/exampleSite/content/events/2016-chicago/contact.md b/exampleSite/content/events/2016-chicago/contact.md
new file mode 100644
index 000000000..7d9294a68
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/contact.md
@@ -0,0 +1,16 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
++++
+
+If you'd like to contact us by email: {{< email_organizers subject="DevOpsDays Chicago">}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-chicago/location.md b/exampleSite/content/events/2016-chicago/location.md
new file mode 100644
index 000000000..b35765e99
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/location.md
@@ -0,0 +1,24 @@
++++
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+### Conference Location
+Summit West
+500 W Madison St
+Chicago, IL 60661
+
+
+View on Google Maps
+
+
+
+
+
+### Getting there
+
+Summit West is located in the Ogilvie Transportation Center and is easy to reach by any mode of transit you want.
+
+
diff --git a/exampleSite/content/events/2016-chicago/program.md b/exampleSite/content/events/2016-chicago/program.md
index b3d5a5338..a49d548c3 100644
--- a/exampleSite/content/events/2016-chicago/program.md
+++ b/exampleSite/content/events/2016-chicago/program.md
@@ -1,9 +1,414 @@
+++
-City = "Chicago"
-Year = "2016"
-date = "2016-07-15T22:06:24-06:00"
-title = "Chicago 2016 Program"
-type = "program"
+date = "2016-07-15T21:31:25-06:00"
+title = "program"
+type = "event"
+
+++
-We’ll talk about the fundamentals of automation, what we’ve learned over multiple generations of tooling and research, and discuss the path forward.
+
+ In Spring of 2016 Braintree decided to rebuild its CI system. At braintree we chose docker to power the CI system. In this talk I will discuss things we learnt with the Docker ecosystem (Docker, Docker-Compose and Docker-Registry).
+
+
+ {{< youtube ZG2_acl-Ks4 >}}
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-chicago/program/adam-jacob.md b/exampleSite/content/events/2016-chicago/program/adam-jacob.md
index 84a4e9c8d..e032dd4e5 100644
--- a/exampleSite/content/events/2016-chicago/program/adam-jacob.md
+++ b/exampleSite/content/events/2016-chicago/program/adam-jacob.md
@@ -2,14 +2,28 @@
City = "Chicago"
Year = "2016"
date = "2016-07-15T22:06:24-06:00"
-title = "The Evolution of Automation"
+title = "Adam Jacob"
type = "talk"
aliases = ["/events/2016-chicago/program/adamjacob/"]
-youtube = "emGKB8TABvI"
-vimeo = ""
-speakerdeck = "https://speakerdeck.com/mattstratton/shifting-left-securely"
-slideshare = "http://www.slideshare.net/mattstratton/the-five-love-languages-of-devops-54549536"
-slides = ""
+
+++
+
+
+
Title:
+The Evolution of Automation
+
+
+
Description:
+
+
We’ll talk about the fundamentals of automation, what we’ve learned over multiple generations of tooling and research, and discuss the path forward.
+
+ I probably am doing DevOps without even knowing it. When I discovered the DevOps Dictionary definition of "goat" I fell in love. My perspective on DevOps as a self-taught woman in technology and what the DevOps community could be more inclusive and accessible to me and other people I know.
+
+ DevOps has a well-established relationship with animals, particularly cattle and pets. Many attempts to "cattlle-ize" existing systems stall halfway, leading to somewhat different outcomes and leaving operations teams wondering what happened. This talk will focus on some common hurdles encountered when to moving towards the servers as cattle model and discuss some ways to identify and address them.
+
Title: Fear and (Self) Loathing in IT – A Healthy Discussion on Imposter Syndrome
+
+
Description:
+
+ Many of us feel nervous or fearful about fully engaging with our teams, lest we be "found out" as an imposter who doesn't belong there. Imposter Syndrome is not silly, trivial, or something you’ll “just grow out of”. Many people have been experiencing Imposter Syndrome since childhood. But when does this anxiety become unhealthy? Is Imposter syndrome something we really even NEED to cure? As a fellow imposter, I’d like to share some of my own adventures in embracing my fears, learning to trust myself, and getting comfortable with asking for help.
+
Title:
+Leading an Enterprise to the Public Cloud
+
+
+
Description:
+
+
+I want to talk about the experience I've been a part of, bringing a large Enterprise company to using AWS for mission critical applications. This required collaboration across Development, Operations, Networking, Legal, Security, Audit, Risk, and Executive Management. Cross-team representatives worked together over several months, developed a written business case, and won executive backing to use AWS for mission critical services, including NPI data. I'll be sharing lessons learned along the way.
+
+Do you wake up in a cold sweat when you think about what would happen if one of your devops people were to suddenly vanish, or win the lottery? Could you carry on? Can anyone on your team take vacations to cell-phone dead spots?
+
+
+Devops is such a dynamic and flexible part of an organization that it is the absolute hardest thing to get documented, and the place where it really makes a difference to burnout if you have managed the miracle.
+
Title:
+Out of the Basement: Demystifying Security and Operations
+
+
+
Description:
+
+
+Have you ever wondered is there's really some truth behind those stories of Bad Operators from Hell and Stifling Security Engineers? Jamesha Fisher, both seasoned in security and operations, hopes to detangle false notions, and uplift the generalized perspective of security and operations, bringing pride, as well as their importance to the DevOps movement.
+
Title:
+How is the role of DevOps changing in a Serverless environment?
+
+
+
Description:
+
+
+Serverless is the next step after containers. DevOps will not go away, but it will certainly change. Getting ahead of the curve is important for a DevOps practitioner so that they can make sure the transition goes smoothly when their organization changes.
+
+
+I’ll cover where my company ran into trouble when going serverless and how we solved all the new problems that come with managing a bunch of small functions instead of larger programs. I’ll also cover specifics of how our company manages an almost completely serverless environment, including the open source tools that we use and publish.
+
+ All aspects of DevOps are difficult; acknowledging, implementing, hell even defining. But do you know whats even harder then DevOps? People. Finding, recruiting and retaining.
+
+
+ We’ve seen great strides in the DevOps community in terms of changing the way engineering teams think about process and procedures, but why stop there? Why not use DevOps principles in another aspect of technology that seems to be broken; recruitment.
+
+ So you want to start a DevOps revolution. Great...where do you start? Going from manual deployments to a fully automated delivery pipeline has brought many changes; both technical and cultural. In this talk, we will cover "the five phases of DevOps" we found on our journey at Gogo. Finally, we will wrap up the talk with how you too can start your own DevOps revolution! We will talk about our successes and challenges implementing various tools and driving large cultural changes.
+
Title: The answer to the “where do we start” question
+
+
Description:
+
+ Where do we start? This is by far the question I’m asked the most when talking to people about implementing continuous delivery. Unlike other types of long journeys, the answer is rarely “at the beginning”.
+
+
+ One of the best ways to determine the best place to start is to figure out where you’re wasting the most resources, and one of the best ways to do that is to create a value stream map.
+
+
+ We’ll go over what a value stream map is, how you can create one, and how it can help you answer some important questions about your business. Questions like “where do we start?”.
+
Title: What I’ve learned interviewing more than 150 people face to face
+
+
Description:
+
+ I’ve been part of growing Puppet from 35 to 450+ people over the last five years. I’ve spent many hundreds of hours on the hiring process - but really want to dig into the interview. I’ll highlight the 10,000 hour rule from Anders Ericsson (made famous by M Gladwell) on experience and measurement of success by tying that in with deliberate practice/continuous improvement when it comes to interviewing. I’ll share some science, some practices (such as my 6 question interview) and some humor to hopefully shift your thoughts interviewing and hiring - all in 5 minutes.
+
+ Submitting proposals and speaking at conferences can be very stressful, especially as an introvert. This talk will cover tips I have found to help make presenting more pleasant and why it's important to give talks despite being nervous about giving talks.
+
Title: Untangling Infrastructure Code Through Refactoring
+
+
Description:
+
+ The point of infrastructure as code is to make managing infrastructure as simple as updating a config file and running a command such as “chef-client” or “terraform apply.” However, as code changes and becomes unruly or tangled, it is time to apply a new development practice - refactoring. Refactoring infrastructure code presents unique challenges - particularly when live, in production infrastructure is involved. This talk will show you how to know when it is time to refactor your infrastructure code and to do it with the least risk possible.
+
Title:
+Building resilience in our organizations, our teams, and ourselves
+
+
+
Description:
+
+
+We talk about redundancy and security when it comes to our infrastructure and applications, but we rarely think about creating those same things in our teams and ourselves.
+
+
+From the start-up financial roller coaster to a teammate's marriage (or divorce) to our own personal issues, success, scaling, and our future depend on complex and often chaotic factors.
+
+
+In order to succeed, we need to create resilience, not just in our technology, but also in our organizations, our teams, and ourselves.
+
+
+{{< youtube KQFxyfYEMSM >}}
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-chicago/proposals.md b/exampleSite/content/events/2016-chicago/proposals.md
new file mode 100644
index 000000000..0000a6d02
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/proposals.md
@@ -0,0 +1,12 @@
++++
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-chicago/propose.md b/exampleSite/content/events/2016-chicago/propose.md
new file mode 100644
index 000000000..fae60dcd4
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/propose.md
@@ -0,0 +1,60 @@
++++
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+
+
+
+
+## Types of Talks
+
+### Session Talks
+30 minute slots that will have the full attention of all attendees, as everybody will be in the main presentation room together.
+
+### Ignite Talks
+Presented during their own specific session in the afternoon on both Tuesday and Wednesday. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in main presentation room.
+
+There will also be Open Spaces allowing for additional conversations to take place. Those topics will be suggested and selected just prior to Open Spaces on the day of the event.
+
+## Criteria
+
+### Original Content
+Content not yet presented at other conferences, or a new angle to an existing problem. DevOpsDays is one of the best events to learn about the DevOps movement. Look for ways to present or explain subjects that are related to DevOps. Interesting ways to explain DevOps to those that are not familiar with the term or how it can help their team and/or organization is highly encouraged
+
+### New Presenters
+People who are new to the space and have insightful things to say and share. There are a number of great presenters on a variety of DevOps subjects. However, we want to encourage new voices and thoughts to the space.
+
+### No Vendor Pitches
+The quickest way to be denied to present is to pitch your company’s product or service. As much as we value vendors and sponsors, we just don't think this is the right forum. This is a participatory event in which everyone in attendance is encouraged to interact and discuss a wide range of DevOps topics. It is not a forum to pitch your services. You can demo at your table or during Open Space. Additionally, Gold sponsors will be given a 60-second slot to have the full attention of the audience in order to share a little bit about your company and it’s offerings. Please keep this in mind when submitting proposals. If we feel that you may be using it as an opportunity to “sell” your company, you’ll likely be declined.
+
+### Compelling & Fun
+No one likes to attend conferences where the presentations are dry and hard to sit through. We are looking for topics (and presenters) who can deliver a compelling message and perhaps even make it fun. We don’t expect comedic-like delivery, but find ways to keep it entertaining to a certain degree if possible.
+
+## Tips
+
+### Be as specific as possible
+CFP submissions that aren’t clear in what they intend to deliver and how it is useful to the audience won’t be selected. It is possible that organizers may reach out to you for clarification of an abstract, but try to be as descriptive as possible. A description of about 20 lines is about right. Detail is good but not as important as explaining why your proposal would be interesting to our participants. Explain to us why your proposal has value to the group and DevOps space in general.
+
+### Propose your own talk
+We understand that many who are interested in presenting are very busy. Trust us. We know. However, it’s best to submit your own CFP rather than having someone from a marketing team (or 3rd party) submit. We want to be able to reach out to the presenter for clarification on abstracts if necessary. We may possibly even suggest a slight modification to the talk to make it fit the overall agenda and voice of DevOpsDays. Working through anyone other than the person actually presenting the talk is very frustrating and may result in turning down a possibly great talk.
+
+### Nominations welcome
+If you know someone who has content or experience relevant to the DevOps conversation, please point us in their direction! It’s a great big world out there. It’s likely that you know of folks who have given killer presentations that really made a difference in your understanding of DevOps. Let us know who they are, or better yet, encourage them to submit a CFP.
+
+### Multiple proposals welcome
+There is no limit on the number of CFP’s you can submit. In fact, the more the better. We encourage you to submit more than one. It’s possible that a talk you propose may also be proposed in a similar way from another person. In that case, we’ll have to pick just one to avoid too much overlap or duplication of topics. The more CFP’s you submit, the better your chances of being selected is. Just be sure to follow the criteria mentioned above.
+
+## Submitting
+Go to http://cfp.devopsdayschi.org/, sign up/in, and submit your proposal. Please let us know via email or twitter if you encounter technical issues during submission.
+
+### Mentoring
+We encourage new and seasoned speakers. If you're interested in working with a mentor to develop an idea into a session or ignite, please reach out via email at {{< email_proposals >}}. We will do our best to provide options for mentorship pairing. At the very least, we'll do our best to provide mentorship ourselves. :)
+
+### Travel Assistance
+Please let us know if you need assistance with travel costs including hotel, flight, and parking. This will not affect our decision-making one way or the other, but it is good to know as we finalize our budget.
+
diff --git a/exampleSite/content/events/2016-chicago/registration.md b/exampleSite/content/events/2016-chicago/registration.md
new file mode 100644
index 000000000..c11b81d78
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/registration.md
@@ -0,0 +1,11 @@
++++
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+
Please email us if you wish to attend but consider the cost to be prohibitive.
+
+
diff --git a/exampleSite/content/events/2016-chicago/speakers.md b/exampleSite/content/events/2016-chicago/speakers.md
new file mode 100644
index 000000000..1c1323327
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/speakers.md
@@ -0,0 +1,7 @@
++++
+date = "2016-07-15T21:31:25-06:00"
+title = "speakers"
+type = "speakers"
+
++++
+
diff --git a/exampleSite/content/events/2016-chicago/sponsor.md b/exampleSite/content/events/2016-chicago/sponsor.md
new file mode 100644
index 000000000..aa0353a96
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/sponsor.md
@@ -0,0 +1,102 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this community event. If you are interested in sponsoring, please check out our prospectus and details, or [send us an email](mailto:sponsorships@devopsdayschi.org?subject=Interested in Sponsoring DevOpsDays Chicago 2016).
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that
+depends on sponsorships. We do not have vendor booths or sell product
+presentations. Sponsors have the opportunity to have short elevator
+pitches during the program and will get recognition on the website
+and social media before, during and after the event. Sponsors are
+encouraged to represent themselves by actively participating and
+engaging with the attendees as peers. Any attendee also has the
+opportunity to demo products/projects as part of an open space
+session, but this is not 'that kind of conference' and heavy
+marketing will probably work against you when trying to make a good
+impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Bronze SOLD OUT
+
Silver SOLD OUT
+
Gold SOLD OUT
+
+
+
included tickets
+
1
+
2
+
4
+
+
+
logo on DevOpsDays Chicago event website
+
+
+
+
+
+
logo on all email communication
+
+
+
+
+
+
logo on banner at venue during event
+
+
+
+
+
+
+
mention by MC at kickoff and close
+
+
+
+
+
+
1 minute pitch to full audience (including streaming audience)
+
+
+
+
+
+
ability to reserve "demo space"
+
+
+
+
+
+
dedicated booth/table space
+
+
+
+
+
+
shared booth/table for swag
+
+
+
+
+
+
+
+ Sponsors are responsible for providing high-res logos for use on the website and in promotional materials. The preferred file formats are EPS or AI.
+
+
+
+ There are also opportunities for exclusive special sponsorships. We have sponsorships available for the evening event, video recording, live transcription, and wifi. If you are interested in special sponsorships or have a creative idea about how you can support the event, [send us an email](mailto:sponsorships@devopsdayschi.org?subject=DevOpsDays Chicago 2016 Sponsorship).
+
+
+
+
diff --git a/exampleSite/content/events/2016-chicago/volunteer.md b/exampleSite/content/events/2016-chicago/volunteer.md
new file mode 100644
index 000000000..f28c8b6f9
--- /dev/null
+++ b/exampleSite/content/events/2016-chicago/volunteer.md
@@ -0,0 +1,11 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "volunteer"
+type = "event"
+
++++
+
+If you would like to volunteer at DevOpsDays Chicago 2016, please fill out this form!
+
+
+
diff --git a/exampleSite/content/events/2016-chicago/welcome.md b/exampleSite/content/events/2016-chicago/welcome.md
index 06d781717..5cf01a7a7 100644
--- a/exampleSite/content/events/2016-chicago/welcome.md
+++ b/exampleSite/content/events/2016-chicago/welcome.md
@@ -1,9 +1,72 @@
+++
-Description = ""
-title = ""
-speaker = ""
-images = [""]
-aliases = ["/events/2016-chicago/"]
+date = "2016-03-04T17:36:05-06:00"
+title = "welcome"
type = "event"
+aliases = ["/events/2016-chicago"]
+
+++
-Pivot paradigm sticky note agile grok unicorn waterfall is so 2000 and late responsive affordances thought leader. Grok big data ship it unicorn long shadow long shadow hacker. Entrepreneur waterfall is so 2000 and late integrate user centered design innovate integrate parallax prototype pivot user story fund latte iterate driven. Human-centered design SpaceTeam pitch deck workflow responsive venture capital earned media ideate user centered design thinker-maker-doer viral. Engaging co-working paradigm prototype latte prototype parallax sticky note ship it.
+
+
{{< event_start >}} - {{< event_end >}}
+
+Welcome! The group that brought you DevOpsDays Chicago 2015 is back together and planning the 2016 event. We're encouraged by the feedback from last year's event and are determined to bring an improved experience and continue the DevOps conversation this August in Chicago.
+
+
+ {{< event_logo >}}
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}} in downtown Chicago
+
+
+
+
+
+ Participants
+
+
+ {{< event_link page="registration" text="Register to attend the event!" >}}
+
+
+
+
+
+ Speakers
+
+
+ View the {{< event_link page="program" text="program" >}} and {{< event_link page="speakers" text="speakers." >}}
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+{{< event_twitter devopsdayschi >}}
diff --git a/exampleSite/content/events/2016-cuba/conduct.md b/exampleSite/content/events/2016-cuba/conduct.md
new file mode 100644
index 000000000..c882514ed
--- /dev/null
+++ b/exampleSite/content/events/2016-cuba/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-09-17T16:53:08+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-cuba/contact.md b/exampleSite/content/events/2016-cuba/contact.md
new file mode 100644
index 000000000..1feaf2a36
--- /dev/null
+++ b/exampleSite/content/events/2016-cuba/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-09-17T16:53:08+02:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-cuba/location.md b/exampleSite/content/events/2016-cuba/location.md
new file mode 100644
index 000000000..1635dd123
--- /dev/null
+++ b/exampleSite/content/events/2016-cuba/location.md
@@ -0,0 +1,12 @@
++++
+date = "2016-09-17T16:53:08+02:00"
+title = "location"
+type = "event"
+
++++
+
+DevOps Days Cuba is going to held at the University of Informatic Sciences (Spanish: Universidad de las Ciencias Informáticas). UCI, also known as the University of Information Sciences and University of Informatics Sciences, is a university research center based in Boyeros, Havana, Cuba. Born as a project of the Cuban Revolution called the "Future Project" which has two objectives: to computerize the country and develop the software industry to contribute to economic development the same. It is the first Cuban university to be established under the purposes of the Battle of Ideas. (wikipedia)
+
+UCI website
+
+
diff --git a/exampleSite/content/events/2016-cuba/program.md b/exampleSite/content/events/2016-cuba/program.md
new file mode 100644
index 000000000..2f9127512
--- /dev/null
+++ b/exampleSite/content/events/2016-cuba/program.md
@@ -0,0 +1,122 @@
++++
+date = "2016-09-17T16:53:08+02:00"
+title = "program"
+type = "event"
+
++++
+
+
+
diff --git a/exampleSite/content/events/2016-cuba/propose.md b/exampleSite/content/events/2016-cuba/propose.md
new file mode 100644
index 000000000..cc9b8fe75
--- /dev/null
+++ b/exampleSite/content/events/2016-cuba/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-09-17T16:53:08+02:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-cuba/sponsor.md b/exampleSite/content/events/2016-cuba/sponsor.md
new file mode 100644
index 000000000..14ad4abb8
--- /dev/null
+++ b/exampleSite/content/events/2016-cuba/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-09-17T20:06:23+02:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-cuba/welcome.md b/exampleSite/content/events/2016-cuba/welcome.md
new file mode 100644
index 000000000..b4d893f89
--- /dev/null
+++ b/exampleSite/content/events/2016-cuba/welcome.md
@@ -0,0 +1,50 @@
++++
+date = "2016-09-17T16:53:08+02:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-cuba"]
+
++++
+
+DevOps Days is coming to Cuba!
+
+**It will be hosted at {{< event_location>}} on {{< event_start >}} till {{< event_end >}}**
+
+Please go to the local website to get more information: devopsdayscuba.eventos.uci.cu (Yes, please accept the certificate...)
+
+
+ {{< event_logo >}}
+
+
+
+
+
Dates
+
{{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
Speakers
+
Already confirmed speakers, Patrick Debois, Bridgit Kromhout, Bernard Grymonpon, Mike Rosado. More will be announced later.
+
+
+
Contact
+
{{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+ {{< event_twitter devopsdayscuba >}}
+
+
+
diff --git a/exampleSite/content/events/2016-dallas/conduct.md b/exampleSite/content/events/2016-dallas/conduct.md
new file mode 100644
index 000000000..33e3ff83b
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-dallas/contact.md b/exampleSite/content/events/2016-dallas/contact.md
new file mode 100644
index 000000000..b840d5bc6
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/contact.md
@@ -0,0 +1,26 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/location.md b/exampleSite/content/events/2016-dallas/location.md
new file mode 100644
index 000000000..231f094ae
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/location.md
@@ -0,0 +1,37 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+The location will be Grapevine Convention Center, 1209 S. Main Street, Grapevine, TX 76051.
+
+
+[More information about the venue here](http://www.grapevinetexasusa.com/grapevine-convention-center/)
+[Google Maps](https://goo.gl/maps/FUnWbVN4P3J2)
+
+
+
+The event will be during a very fun week in Grapevine, GrapeFest®. If you arrive late to the conference parking will be challenging, keep that in mind as you plan.
+
+[More information about GrapeFest®](http://www.grapevinetexasusa.com/festivals-events/grapefest/)
+
+
+
+If you are traveling to attend this event, the Grapevine Convention Center is really very close to the DFW Airport. Here is a list of hotels and their distance from the hotel to the Grapevine Convention Center for your convenience:
+
+[More information about Hotels](http://www.hotels-for-everyone.com/hotels-in-city/near,Grapevine-Convention-Center.html?utm_source=bing&utm_medium=cpc&utm_campaign=TX+Grapevine+-+Grapevine+Convention+Center&utm_term=Hotels+Close+to+Grapevine+Convention+Center&utm_content=TX+Grapevine+-+Grapevine+Convention+Center+-+Hotel&range=4&i=10&adults_1=1&spec=1&checkIn=09/14/2016&checkOut=09/17/2016)
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-dallas/program.md b/exampleSite/content/events/2016-dallas/program.md
new file mode 100644
index 000000000..e4b22dd58
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program.md
@@ -0,0 +1,340 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ [DevOps for Normals (Michael Coté)](/events/2016-dallas/program/michael-cote/)
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-dallas/program/allison-pollard.md b/exampleSite/content/events/2016-dallas/program/allison-pollard.md
new file mode 100644
index 000000000..78fa1cd15
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/allison-pollard.md
@@ -0,0 +1,13 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Allison Pollard"
+type = "talk"
++++
+
+**Title:** Encouraging Future Leaders
+
+**Description:**
+
+Leadership development is about helping others to grow. As leaders, how are we creating opportunities for other leaders to emerge and allowing them to grow? In our journeys, we’ve gone from feeling “no one is stepping up” to recognizing that today’s leaders show up in a different way if you expand your view to see them. It’s rare to find someone like yourself to handle certain responsibilities, and being open to new ideas and new practices can pave the way for more leaders to emerge. Regardless of title or role, teams and groups can evolve from “leadership from a few” to becoming “leaderful.”
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/program/franklin-mosley.md b/exampleSite/content/events/2016-dallas/program/franklin-mosley.md
new file mode 100644
index 000000000..307fefcee
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/franklin-mosley.md
@@ -0,0 +1,15 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Franklin Mosley"
+type = "talk"
++++
+
+**Title:** RoboCop: Bringing law and order to CICD
+
+**Description:**
+
+In the movie, RoboCop is given three primary directives: "Serve the public trust, Protect the innocent, and Uphold the law". We built our own RoboCop in order to bring law and order to our CI/CD pipeline. DevOps practices are all about enabling fast and frequent delivery of new software. In order to keep pace in a DevOps culture, application security must be reliably integrated into the CI/CD pipeline.
+
+In this talk, we will show how our small AppSec team combined automated tools along with human oversight in order to achieve our directives at scale, while winning the hearts and minds of our development teams.
diff --git a/exampleSite/content/events/2016-dallas/program/jeffrey-snover.md b/exampleSite/content/events/2016-dallas/program/jeffrey-snover.md
new file mode 100644
index 000000000..f62eaa6d8
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/jeffrey-snover.md
@@ -0,0 +1,13 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Jeffrey Snover"
+type = "talk"
++++
+
+**Title:** The Devopsification of Windows Server 2016
+
+**Description:**
+
+Everyone knows that Devops is not about technology – it is about culture and process. But some technologies make some certain processes and cultures difficult and other technologies makes them easy. This session explores why and how Windows Server 2016 was developed with DevOps in mind and what this means to customers adopting a devops workflow.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/program/kevin-witherstine.md b/exampleSite/content/events/2016-dallas/program/kevin-witherstine.md
new file mode 100644
index 000000000..b2ad972f7
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/kevin-witherstine.md
@@ -0,0 +1,19 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Kevin Witherstine"
+type = "talk"
++++
+
+**Title:** NetDevOps - A Network Engineer's journey into a software world
+
+**Description:**
+
+I’m a network engineer with an electrical engineering background, all I hear is how software is eating the world. What’s to become of me? Those were my thoughts several years ago. A little introduction to Python programming and early Openstack almost made me run and hide, a stint with VMware gave me a little hope. All the while linux was a part of the equation.
+
+Now, linux has almost become second nature and github and Ansible are my favorite tools. This didn’t all happen overnight, but it did happen and now that I see how powerful those tools are, I want to show other network engineers that it’s not impossible to bridge the gap between the CLI and NetDevOps.
+I’m terrible at writing code. I just can’t wrap my head around it. But learning enough to read what someone else wrote and understand what they are trying to accomplish is probably enough to get you going.
+
+In this talk I plan to walk you through the journey I took. Start with the basic tools, show you why they matter, and put them into practice.
+
diff --git a/exampleSite/content/events/2016-dallas/program/marissa-lerer.md b/exampleSite/content/events/2016-dallas/program/marissa-lerer.md
new file mode 100644
index 000000000..3bf66fec1
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/marissa-lerer.md
@@ -0,0 +1,13 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Marissa Levy Lerer"
+type = "talk"
++++
+
+**Title:** Where My Ladies At: The Radical Topic of Women in Tech
+
+**Description:**
+
+There’s no disputing that the future has arrived for pocket computers, autonomous cars and croissants that are also, somehow, donuts. Innovation is moving at light-speed but women are being left behind when it comes to tech. We still having the same, tired conversation about (say it with me) “women in tech.” We are inundated with jargon about leaning in, opting out, work-life balance, which can be discouraging for women, especially for those beginning their careers. This presenter is a CTO, mom, and proud chick coder understands what it’s like to survive the “woman in tech” scene. Join her for an empowering journey of where we’ve been, where we’re heading and some unsolicited advice about making the most of your career.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/program/michael-cote.md b/exampleSite/content/events/2016-dallas/program/michael-cote.md
new file mode 100644
index 000000000..d3f2379d7
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/michael-cote.md
@@ -0,0 +1,17 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Michael Cote"
+type = "talk"
++++
+
+**Title:** DevOps for Normals - what’s happening as donkeys adopt DevOps
+
+**Description:**
+
+In a post-unicorn era of DevOps, as “donkeys” start to adopt and use DevOps, what’s working and not working? This talk with present my current observations and advice on the topic, as well as a quick assessment of “the state of DevOps.”
+
+In the past two years, DevOps has clearly gone mainstream which is creating all sorts of interesting experiments to observe as “normal” companies, outside of technology, adopt DevOps practices. These companies are often beguiled by the core berries to DevOps adoption - a corporate culture and processes that are built around slow, project-mindset driven application delivery - but are also encountering problems unique to “normals” like dealing with legacy code, audit and compliance, and managers who don’t quite seem to get how computers work.
+
+I’ve been studying these stories over recent years and will present what I’ve observed organized into best and worst practices. My goal is always to give helpful advice that can actually be put into practice once the audience goes back to work.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/program/michael-hedgpeth.md b/exampleSite/content/events/2016-dallas/program/michael-hedgpeth.md
new file mode 100644
index 000000000..2b962895b
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/michael-hedgpeth.md
@@ -0,0 +1,15 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Michael Hedgpeth"
+type = "talk"
++++
+
+**Title:** Orchestrating Independence: Our journey from an orchestration script to zero-downtime, scalable orchestration of changes
+
+**Description:**
+
+You’ve automated the provisioning of your infrastructure with a configuration management solution. But now you have to manage how that interacts with other changes in the system. Is it time to write a bash script or use an orchestration feature of your solution that, let’s face it, looks a lot like a bash script?
+
+At NCR, we went in a different direction and came up with a model to orchestrate changes to infrastructure in a way that eliminates downtime and reduces dependency between nodes, opening the possibility for red/green deployments and more. We’ll talk about considerations when approaching orchestration, how we designed our model with Hashicorp Consul and Chef, and the benefits we’ve seen from doing so.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/program/nathen-harvey.md b/exampleSite/content/events/2016-dallas/program/nathen-harvey.md
new file mode 100644
index 000000000..f892f6382
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/nathen-harvey.md
@@ -0,0 +1,14 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Nathen Harvey"
+type = "talk"
++++
+
+**Title:** Delightful DevOps Days
+
+**Description:**
+
+This year marks the seventh anniversary of the first DevOps Days event. The format of the events has been fairly consistent from one DevOps Days to the next. This may be your first DevOps Days or your fifth. In fact, this may be your first technical event ever. So, how did we get here and how can you make the most of the next two days? Let's look back on the history of DevOps through the eyes of someone who's been a community participant from the early days of the movement. As we do so, we'll look at some tips you can takeaway to help make sure your DevOps Days DFW experience is delightful. Be prepared to learn, be prepared to make new friends, and, most importantly, be prepared to be surprised.
+
diff --git a/exampleSite/content/events/2016-dallas/program/shazad-brohi.md b/exampleSite/content/events/2016-dallas/program/shazad-brohi.md
new file mode 100644
index 000000000..f391fc060
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/shazad-brohi.md
@@ -0,0 +1,15 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Shazad Brohi"
+type = "talk"
++++
+
+**Title:** Orchestrating Independence: Our journey from an orchestration script to zero-downtime, scalable orchestration of changes
+
+**Description:**
+
+You’ve automated the provisioning of your infrastructure with a configuration management solution. But now you have to manage how that interacts with other changes in the system. Is it time to write a bash script or use an orchestration feature of your solution that, let’s face it, looks a lot like a bash script?
+
+At NCR, we went in a different direction and came up with a model to orchestrate changes to infrastructure in a way that eliminates downtime and reduces dependency between nodes, opening the possibility for red/green deployments and more. We’ll talk about considerations when approaching orchestration, how we designed our model with Hashicorp Consul and Chef, and the benefits we’ve seen from doing so.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/program/zach-cannon.md b/exampleSite/content/events/2016-dallas/program/zach-cannon.md
new file mode 100644
index 000000000..f641d9a9e
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/program/zach-cannon.md
@@ -0,0 +1,13 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-09-15T09:00:00-08:00"
+title = "Zach Cannon"
+type = "talk"
++++
+
+**Title:** Encouraging Future Leaders
+
+**Description:**
+
+Leadership development is about helping others to grow. As leaders, how are we creating opportunities for other leaders to emerge and allowing them to grow? In our journeys, we’ve gone from feeling “no one is stepping up” to recognizing that today’s leaders show up in a different way if you expand your view to see them. It’s rare to find someone like yourself to handle certain responsibilities, and being open to new ideas and new practices can pave the way for more leaders to emerge. Regardless of title or role, teams and groups can evolve from “leadership from a few” to becoming “leaderful.”
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/proposals.md b/exampleSite/content/events/2016-dallas/proposals.md
new file mode 100644
index 000000000..6cd8ea7a8
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/proposals.md
@@ -0,0 +1,55 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+
+
+
Conference Talks
+Please submit you papers via paper call. All papers need to be submitted there to be considered, if you have problems please let us know.
+[https://www.papercall.io/devopsdays-dfw-2016](https://www.papercall.io/devopsdays-dfw-2016)
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+
+For DevOpsDays Dallas 2016, we are actively soliciting programming that addresses these topics:
+
+* Software development practices for the DevOps world
+* Velocity, sustainability, and technical debt
+* Quantifying productivity, failure, and risk metrics
+* Professional development, teaching, training, and mentorships
+* Emotional labor and empathy
+* Teaching junior engineers how to be senior engineers
+* Mental health, stress, and burnout
+* Learning lessons from other fields (manufacturing, military, etc.)
+
+We will also accept submissions on perennially popular topics as discussed at other DevOpsDays:
+
+* Continuous Deployment
+* Automation
+* Containerization
+* Performance Monitoring
+* Configuration Management
+* DevOps in the Enterprise
+* Microservices
+* Managed Services
+* Development methodology
+* Scaling out DevOps
+* Hiring for DevOps
+
+However, please consider that novelty is heavily encouraged as per our guidelines above. These topics are popular, but every year we will be receiving more submissions about them than we can accept.
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-dallas/registration.md b/exampleSite/content/events/2016-dallas/registration.md
new file mode 100644
index 000000000..44ba074a0
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/registration.md
@@ -0,0 +1,29 @@
++++
+City = "Dallas"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+Early Bird Registration opens May 9th, so don't miss out on this great opportunity to get a ticket at an excellent discounted price.
+
+Early Bird Tickets are limited. https://devopsdays-dfw-2016.eventbrite.com/
+
+
+
+Why Sponsor Us?
+
+The DevOpsDays event mandate is to bring the highest quality speakers, experts and the curious together.
+By sponsoring DevOpsDays, you will be exposing your company’s brand and services to Dallas’s top talent
+in this rapidly growing space. (And feel great about it, too!)
+We greatly value sponsors for this open event. If you are interested in sponsoring please reach out to us at: {{< email_organizers >}}.
+
+Please click HERE to download the full sponsor prospectus for DevOpsDays Dallas 2016!
+
+
+
+
+Platnium Sponsor:
+
+
+
+
+Gold Sponsor:
+
+
+
+
+Silver Sponsor:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+DevOpsDays is a self-organizing conference for DevOps enthusiasts and evangelists that depends on your sponsorship and participation to happen. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session. The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
diff --git a/exampleSite/content/events/2016-dallas/welcome.md b/exampleSite/content/events/2016-dallas/welcome.md
new file mode 100644
index 000000000..873a87c26
--- /dev/null
+++ b/exampleSite/content/events/2016-dallas/welcome.md
@@ -0,0 +1,95 @@
++++
+City = "Dallas"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-dallas"]
+
+
++++
+
+
+ {{< event_logo >}}
+
+
+
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+ Propose
+
+
+ {{< event_link page="proposals" text="Propose a talk!" >}}
+
+
+
+
+
+ Register
+
+
+ {{< event_link page="registration" text="Register to attend the event!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-denver/conduct.md b/exampleSite/content/events/2016-denver/conduct.md
new file mode 100644
index 000000000..9569fe4fd
--- /dev/null
+++ b/exampleSite/content/events/2016-denver/conduct.md
@@ -0,0 +1,48 @@
++++
+City = "Denver"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+* Local law enforcement: Denver Police - Non-Emergency Help [720-913-2000](tel:720-913-2000), Emergency call 911
+* Sexual assault hotlines: The Blue Bench: English [303-322-7273](tel:303-322-7273), Spanish [303-329-0031](tel:303-329-0031), [1-888-394-8044](tel:1-888-394-8044)
+* Medical Emergency: Call 911
+* Local taxi companies: [Yellow Cab](http://www.denveryellowcab.com) - [303-777-7777](tel:303-777-7777),
+[Metro Taxi](http://www.metrotaxidenver.com/) [303-333-3333](tel:303-333-3333)
+
+##ANTI-HARASSMENT POLICY
+
+DevOpsDays Denver is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+##CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
+
diff --git a/exampleSite/content/events/2016-denver/contact.md b/exampleSite/content/events/2016-denver/contact.md
new file mode 100644
index 000000000..61a2c6069
--- /dev/null
+++ b/exampleSite/content/events/2016-denver/contact.md
@@ -0,0 +1,22 @@
++++
+City = "Denver"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+Follow @devopsdaysrox
+
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+** Our local team**
+
+{{< list_organizers >}}
+
+** The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-denver/program.md b/exampleSite/content/events/2016-denver/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2016-denver/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2016-denver/propose.md b/exampleSite/content/events/2016-denver/propose.md
new file mode 100644
index 000000000..adcb05549
--- /dev/null
+++ b/exampleSite/content/events/2016-denver/propose.md
@@ -0,0 +1,40 @@
++++
+City = "Denver"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
diff --git a/exampleSite/content/events/2016-denver/sponsor.md b/exampleSite/content/events/2016-denver/sponsor.md
new file mode 100644
index 000000000..89afbd716
--- /dev/null
+++ b/exampleSite/content/events/2016-denver/sponsor.md
@@ -0,0 +1,77 @@
++++
+City = "Denver"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+
+## Sponsorship Packages
+
+
+### Gold Sponsorship ($3,500) (Sold out!)
+
+* 6 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* 1 minute pitch to full audience (including streaming audience)
+* Demo a product (20 min) during Open Space Session
+* Booth/Table space
+* Logo Co-branded on lanyard
+
+### Silver Sponsorship ($2,500)
+
+* 4 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* Booth/Table space
+* Display of your roll-up/pop-up banner in the venue near high traffic areas
+
+### Copper Sponsorship ($2,000)
+
+* 2 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* Shared table for gifeaways
+* Special Visibility promotion
+
+### Bronze Sponsorship ($1,500)
+* 2 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* Shared table for gifeaways
+
+### Social Hour Sponsorship – Availability 1 ($4,000)
+
+* 2 tickets to the event
+* 6 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* 1 minute pitch to full audience (including streaming audience)
+* Demo a product (20 min) during Open Space Session
+* Booth/Table space
+* Logo Co-branded on lanyard
+* Full access to decorate bar and host activities during Happy Hour
+
+### Special Visibility Packages
+With each of these sponsor options, we will make sure the attendees know you sponsored the
+event by providing the opportunity to associate your brand with a high-visibility activity during
+the event. There will be up-front announcements of these events, social media, website
+promotion and, of course, your logo or pop-up banner will be incorporated in some fashion
+(depends on option).
+Each of these are unique opportunities and are available on a first-come / first served basis.
+When we run out, we have run out!
+
+* Caffeine: We plan to have a coffee cart to keep the audience caffeinated through the
+event.
+* Wireless Networking: Your company name will be the SSID for the network at the
+conference.
+* Ice Cream Social/Smoothie: During our afternoon break on day 1, we will have an ice
+cream social featuring Little Man Ice Cream.
+* Dessert/Cupcake Break: During our afternoon break on day 2, we will have a little
+dessert social.
+
+
+For more information and FAQ's see the [Sponsorship Packages.pdf](http://www.devopsdaysrox.org/sponsor/2016-DevOpsDaysRox-Sponsorship.pdf)
diff --git a/exampleSite/content/events/2016-denver/welcome.md b/exampleSite/content/events/2016-denver/welcome.md
new file mode 100644
index 000000000..65e8064d9
--- /dev/null
+++ b/exampleSite/content/events/2016-denver/welcome.md
@@ -0,0 +1,67 @@
++++
+City = "Denver"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-denver"]
+
+
++++
+
+
+
+ {{< event_logo >}}
+
+
+
+
+
+
+ DevOpsDays is back for its 2nd anual event in the Rocky Mountains {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ The event will be held in Denver, spanning two days of great talks and breakout sessions.
+
+
+
+ Call for Proposals Has ended, stay tuned for voting!
+
+
+
+ Check out our site, it will serve as the main place we
+ will update information as well as act as our program for the
+ event.
+ http://www.devopsdaysrox.org/
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Date
+
{{< event_start >}} - {{< event_end >}}
+
+
+
Location
+
+ Fortrust
+ 4300 Brighton Boulevard Denver, CO 80216
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-detroit/conduct.md b/exampleSite/content/events/2016-detroit/conduct.md
new file mode 100644
index 000000000..a2c48e4fe
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Detroit"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-detroit/contact.md b/exampleSite/content/events/2016-detroit/contact.md
new file mode 100644
index 000000000..8dfdb12cf
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Detroit"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-detroit/location.md b/exampleSite/content/events/2016-detroit/location.md
new file mode 100644
index 000000000..6188b1dec
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/location.md
@@ -0,0 +1,26 @@
++++
+City = "Detroit"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
Conference Location
+DevOpsDays Detroit 2016 is being held at the College for Creative Studies, A. Alfred Taubman Center for Design Education. The building address is: 460 W. Baltimore Ave, Detroit, MI 48202. Maps and Directions
+Attendee Parking is available at the Woodward Lot, located on Baltimore between Cass and Woodward.
+
+
About the Taubman Center
+
+The A. Alfred Taubman Center for Design Education is an educational complex devoted to creativity. It houses a learning community, focused on art and design, extending from middle school through graduate school and beyond into the professional realm. It houses several departments for the College of Creative Studies, a library, dormitory, gymnasium, book store, cafe, and conference space. The building, formerly known as the Argonaut building, was designed by Albert Kahn for General Motors.
+
+
Hotel
+
+We have reserved a block of rooms at the Hotel St. Regis.
+
King or Double rooms are $119, and valet parking is $20/day. Use this
+link to reservations and enter group code `GDOP`
diff --git a/exampleSite/content/events/2016-detroit/program.md b/exampleSite/content/events/2016-detroit/program.md
new file mode 100644
index 000000000..f43898784
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program.md
@@ -0,0 +1,457 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
diff --git a/exampleSite/content/events/2016-detroit/program/adventures-in-public-speaking.md b/exampleSite/content/events/2016-detroit/program/adventures-in-public-speaking.md
new file mode 100644
index 000000000..cfee4f93b
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/adventures-in-public-speaking.md
@@ -0,0 +1,20 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Adventures in Public Speaking"
+type = "ignite"
+
++++
+
+**Speaker**: Leon Fayer, OmniTI
+
+Lately, I've been having a lot of conversations with conference goers. Most
+attend numerous conferences, have great hallway discussions and yet, are too
+hesitant to submit a proposal with their story. The reasons vary, but the
+hesitation (or even fear) to present a topic publicly is pretty common in our
+industry. Being a fairly new speaker myself, I can relate to a lot of these
+concerns. Hence the reason for this talk.
+
+This talk covers a few of the more common objections to public speaking,
+recommendations on how to address them as well as tips for new (and maybe
+veteran) speakers. Everyone has a story. That story should be heard.
diff --git a/exampleSite/content/events/2016-detroit/program/beginners-guide-to-data-analytics.md b/exampleSite/content/events/2016-detroit/program/beginners-guide-to-data-analytics.md
new file mode 100644
index 000000000..b451f7077
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/beginners-guide-to-data-analytics.md
@@ -0,0 +1,54 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Beginners Guide to Data Analytics"
+type = "talk"
+
++++
+
+**Speaker**: David Barnett, RightBrain Networks
+
+Getting started in data analyses is daunting. The field is full of tools with
+clever, but ultimately non-descriptive names (Hadoop, Spark, Hive, Pig, etc).
+Operating a distributed Hadoop or Spark cluster takes significant time and
+treasure.
+
+Amazon Web Services (AWS) provides a complete toolchain for doing big-data
+analysis. This talk, intended for beginner to intermediate experience levels,
+will focus on the task of analyzing web logs to solve the real world business
+case “Who is visiting my site, and what are they up to”? Attendees will learn
+about the tools available for data ingress (Kinesis Firehose), data integration
+(Lambda), data analysis (EMR hosted Spark, Hive, Pig, etc), and data
+warehousing (Redshift).
+
+These are complex tools, each with their own intricacies. However, by the end
+of the session attendees should feel comfortable enough to dive in and begin
+doing analyses on their own data.
+
+#### Who am I? ####
+
+David Barnett
+
+Senior Software Engineer, RightBrain Networks
+Twitter: @dhbarnett
+
+David Barnett is a Senior Software Engineer at RightBrain Networks. An Ann
+Arbor-based software development and cloud consulting firm, RightBrain Networks
+uses today’s cutting-edge technologies to help companies reinvent themselves in
+the cloud.
+
+For nearly 20 years David has helped organizations deliver quality software
+that exceeds business expectations. He has experience working on and/or leading
+a variety of teams including software quality, product delivery, research, and
+cloud development and operations with a focus on Linux/Unix systems. He has
+worked for companies ranging in size from 20 employees to Fortune 10.
+
+At RightBrain Networks David develops custom solutions for companies looking to
+architect or re-architect their software in the cloud. He focuses on
+data-driven applications, microservices, networking, security and scientific
+computing.
+
+Outside of work, David is active in his local community. In addition to serving
+on neighborhood and community boards, David coaches science olympiad and
+participates in community theater. He is also a member of AWS Michigan.
+
diff --git a/exampleSite/content/events/2016-detroit/program/code-your-infrastructure.md b/exampleSite/content/events/2016-detroit/program/code-your-infrastructure.md
new file mode 100644
index 000000000..ad4b74722
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/code-your-infrastructure.md
@@ -0,0 +1,22 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Code your Infrastructure"
+type = "ignite"
+
++++
+
+**Speaker**: Kevin Remde, Microsoft
+
+“Infrastructure as Code” as a tenet of DevOps is exciting to IT and Dev
+organizations alike. Imagine quickly and consistently building, tearing down,
+and re-building whole test/dev/production environments in the public and/or
+private cloud. Create and apply a text file that quickly configures storage,
+network, subnets, virtual machine NICs, firewall configurations, and virtual
+machines; all in one operation! In this session we’ll walk through the basics
+of building and utilizing these JSON templates, both in plain text and when
+driven through other tools such as Git, Git Hub, Notepad++, Visual Studio Code,
+and Visual Studio. This will be a demo-heavy session, leaving you with
+examples and do-it-yourself homework to help you continue learning this very
+useful new cloud-first engine.
+
diff --git a/exampleSite/content/events/2016-detroit/program/collaborating-with-hubot.md b/exampleSite/content/events/2016-detroit/program/collaborating-with-hubot.md
new file mode 100644
index 000000000..1e80d6a81
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/collaborating-with-hubot.md
@@ -0,0 +1,19 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Collaborating with Hubot for a More Efficient DevOps Workflow"
+type = "ignite"
+
++++
+
+**Speaker**: Mike Nguyen, GitHub
+
+This talk will introduce attendees to Hubot, an open source robot who sits in
+your company's chat client to help your developers by doing most of the heavy
+lifting. We'll look at how he can bring GitHub and many core DevOps tools and
+philosophies to developers' fingertips and why everyone on the team gains from
+this benefit. We'll also see how easy it can be to configure Hubot to plug into
+other tools and what results we can expect to see from using Hubot. By the end
+of this session, we will have outlined why using Hubot is better for
+individuals and teams, while increasing the speed to develop any of your
+features.
diff --git a/exampleSite/content/events/2016-detroit/program/containers-will-not-fix.md b/exampleSite/content/events/2016-detroit/program/containers-will-not-fix.md
new file mode 100644
index 000000000..9523cf3b1
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/containers-will-not-fix.md
@@ -0,0 +1,41 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Containers Will Not Fix Your Broken Culture (and Other Hard Truths)"
+type = "talk"
+
++++
+
+**Speaker**: Bridget Kromhout, Pivotal
+
+Containers will not fix your broken culture. Microservices won’t prevent your
+two-pizza teams from needing to have conversations with one another over that
+pizza. No amount of industrial-strength job scheduling makes your organization
+immune to Conway’s Law.
+
+Does this mean that devops has failed? Not in the slig htest. It means that
+while the unscrupulous might try to sell us devops, we can’t buy it. We have to
+ live it; change is a choice we make every day, through our actions of
+ listening empathetically and acting compassionately. Iterative improvement
+ starts somewhere for us all; let’s talk about it.
+
+Tools are essential, but how we implement the tools and grow the culture and
+practices in our organizations needs even more attention. Whether you’re just
+starting to implement technical and organizational change, or facing the
+prospect that you already have legacy microservices, it’s worth considering the
+why and the how of our behaviors, not just the what.
+
+Making thoughtful decisions about tools and architecture can help. Containers
+prove to be a useful boundary object, and deconstructing systems to human-scale
+allows us to comprehend their complexity. We succeed when we share
+responsibility and have agency, when we move past learned helplessness to
+active listening. But there is no flowchart, no checklist, no shopping list of
+ticky boxes that will make everything better. “Anyone who says differently is
+selling something”, as The Princess Bride teaches us. Instead, let’s talk about
+practical, actionable steps that will help. How do we evaluate our progress?
+How do we know when to course-correct? How do we react when it seems like
+there’s always something new we should have done last month?
+
+Part rant, part devops therapy, this talk will explain in the nerdiest of terms
+why CAP theorem applies to human interactions too, how oral tradition is like
+never writing state to disk, and what we can do to avoid sadness as a service.
diff --git a/exampleSite/content/events/2016-detroit/program/customer-success-missing-link.md b/exampleSite/content/events/2016-detroit/program/customer-success-missing-link.md
new file mode 100644
index 000000000..19aba94a2
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/customer-success-missing-link.md
@@ -0,0 +1,32 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Customer Success: The Missing Link in the Feedback Loop to Engineering"
+type = "ignite"
+
++++
+
+**Speaker**: Dylan Schowengerdt, VictorOps
+
+Being responsible for the success of 10,000+ customers is a big challenge. This
+is especially true when success cannot be generalized to fit every customer.
+Using principles adopted from DevOps and Agile, we developed and implemented a
+new strategy to focus on our customers’ success. As a result, we discovered
+better insight into customer behavior, shortened feedback loops from customers
+to our product developers, and increased transparency between internal business
+units. This was all in an effort to better meet the needs of our customers and
+has been a huge success.
+
+In this talk, I’ll define Customer Success, show
+philosophical similarities to DevOps, and outline challenges we faced
+implementing Success into our organization.
+
+Audience members will learn:
+
+* How to strategically sell the idea and value of Customer Success internally.
+ What it is, what it is not and how it affects each department in your
+ organization
+* How to generate dynamic visuals with tailored data for business experts
+* How to promote internal collaboration through information transparency
+* How to turn a vision into reality by working as the hub of the wheel between
+ engineering, product, marketing, sales and support
diff --git a/exampleSite/content/events/2016-detroit/program/debugging-tls-ssl.md b/exampleSite/content/events/2016-detroit/program/debugging-tls-ssl.md
new file mode 100644
index 000000000..17f663d65
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/debugging-tls-ssl.md
@@ -0,0 +1,25 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Debugging TLS/SSL"
+type = "talk"
+
++++
+
+**Speaker**: John Downey, Braintree/PayPal
+
+I’ve found when working with many developers and operations folks that there is
+a real lack of understanding with regards to how TLS/SSL works. This talk was
+originally given internally at Braintree to help folks understand this
+important part of the stack.
+
+The first thing to know is that SSL is technically now replaced with TLS. Even
+though TLS is one of the bedrocks of internet security, it is still a
+complicated and frustrating topic to approach. Together we’ll go through
+acronym soup (X509, PEM, DER, ASN1) and come out the other side with a better
+understanding of how the protocol works. This talk is aimed at helping you
+diagnose those cryptic secure connection errors.
+
+I’ve been working in the security realm for many years now as a developer. This
+has given me an unhealthy amount of insight into how TLS/SSL works and
+especially how that plays into the OpenSSL library/tools.
diff --git a/exampleSite/content/events/2016-detroit/program/dev-owns-quality.md b/exampleSite/content/events/2016-detroit/program/dev-owns-quality.md
new file mode 100644
index 000000000..904ae89bb
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/dev-owns-quality.md
@@ -0,0 +1,31 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Dev Owns Quality When Dev Feels The Pain"
+type = "talk"
+
++++
+
+**Speaker**: Jeremy Rickard, VMWare
+
+I worked on a team at VMware that delivered one of our first SaaS services. To
+reach that goal, we transitioned from delivering shrink wrapped stuff every
+six/nine months to pushing to production on a daily basis. We started with a
+separate test team that picked up when development was over and an operations
+team that handled most escalations, and ended up carrying a pager(duty app). We
+also got woken up at varying hours of the night to handle problems…sometimes
+our problems and sometimes not. We went from a modest level of unit testing
+with fairly manual processes to fully automated unit testing, integration
+testing and deployment all driven from Jenkins. We also implemented extensive
+instrumentation and logging to facilitate triage of issues and implemented a
+number of additional monitoring solutions for our deployed services using a
+variety of Open Source/Commercial Tools, as well as some pretty fun custom
+built Slack driven automation to reduce the time it took to deploy new changes,
+as well as to discover and remediate problems (vrac-bot: @channel I’ve noticed
+that heap allocation on instance XYZ is at 80% or brac-bot: @channel,
+ping-o-meter reports instance XYZ down, I’ve created a new channel for this
+incident). We also did this while being a fairly distributed team across 4
+different geographical locations. In my talk, I’ll talk about our journey and
+the changes the experience drove within our team, how we built/tested our
+stuff, how we learned to embrace automation and overall how I think it made me
+a better developer and why I think all developers need to have that experience.
diff --git a/exampleSite/content/events/2016-detroit/program/dimly-lit-side-of-devops.md b/exampleSite/content/events/2016-detroit/program/dimly-lit-side-of-devops.md
new file mode 100644
index 000000000..a2a923250
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/dimly-lit-side-of-devops.md
@@ -0,0 +1,20 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Dimly Lit Side of DevOps. App Support Nightmares"
+type = "ignite"
+
++++
+
+**Speaker**: Joshua Goldman, Secureworks
+
+I’d like to propose an Ignite that hits close to home for me. I’ve been in App
+Support for a number of years and I’ve dealt with a few common nightmares
+associated with the roll. The ignite goes over the top 5 nightmares an app
+support engineer deals with and I give a bit of insight on how to better come
+to grips on handling them.
+
+- What is this mysterious new app, and why is it broken at 3am?
+- Brace yourselves a new release is coming!
+- You did what to my server?
+- And more
diff --git a/exampleSite/content/events/2016-detroit/program/drawing-success-from-dfd.md b/exampleSite/content/events/2016-detroit/program/drawing-success-from-dfd.md
new file mode 100644
index 000000000..e0101a749
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/drawing-success-from-dfd.md
@@ -0,0 +1,53 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "How You Can Help in Your Corner with Data Science: Drawing from Successes at the Detroit Fire Department"
+type = "talk"
+
++++
+
+**Speaker**: Cassie DeWitt, Detroit Fire Department
+
+
+Data science at the Detroit Fire Department utilizes an integration of
+technology and data to problem solve and provide actionable insight in response
+to several key issues. In the first half of my presentation, I cover *how* I have
+utilized a combination of technology and data to lay the groundwork for a
+successful data science program. During this part of my presentation, I
+reference the partnerships, tools, and practices I have used to create a
+foundation for data science at the Detroit Fire Department. In the second half
+of my talk, I demonstrate *how* the Detroit Fire Department is utilizing this
+foundation of data science, where analytics at DFD are headed, and a trajectory
+I have charted for this direction. During the second half of my presentation, I
+reflect upon the field of data science and, thereafter, posit that the field
+needs to better ask questions that point to the betterment of the
+organizations/departments that data scientists serve. In addition, I propose
+that the field needs to better utilize technology, not as a product—but as
+something that helps the organizations and institutions that data scientist
+serve better realize their mission and vision. Expounding upon this
+bi-proposal, I explain how the Detroit Fire Department is utilizing these needs
+into its evolving data science program.
+
+
+#### Speaker bio ####
+Cassie DeWitt is a Detroit-based data scientist and social scientist who
+integrates quantitative and spatial data analysis with technology and applied
+research methodology. She utilizes this combination to identify and help solve
+problems the Detroit Fire Department encounters in moving towards its strategic
+vision. As the Lead Data Scientist at the Detroit Fire Department, she has
+demonstrated a track record of producing actionable insight on building fire +
+EMS incidents, response time analysis, and resource allocation. She
+additionally manages the DFD Data Team, which comprises the Detroit Fire
+Department and the Department of Innovation and Technology. Under her
+leadership, the DFD Data Team oversees the Open Data Portal; reports
+performance-based metrics to Commissioner Jones and Mayor Duggan; and oversees
+data quality.
+
+Previous to the role of Lead Data Scientist, Ms. DeWitt was a
+Data Analyst under the former Executive Fire Commissioner Edsel Jenkins. From
+2011 to 2012, she worked on several revitalization projects in the City of
+Detroit.
+
+Ms. DeWitt received her MA from Taubman College at the University of
+Michigan. She holds a Bachelor of Arts (double honors) in English from Wayne
+State University.
diff --git a/exampleSite/content/events/2016-detroit/program/hierarchy-of-devops.md b/exampleSite/content/events/2016-detroit/program/hierarchy-of-devops.md
new file mode 100644
index 000000000..79d35f79f
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/hierarchy-of-devops.md
@@ -0,0 +1,52 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Hierarchy of DevOps Needs"
+type = "talk"
+
++++
+
+**Speaker**: Zach Steindler, Duo Security
+
+Maslow's hierarchy of needs is a well-known concept in psychology. It's a
+multi-level pyramid with basic needs on the bottom (like physical safety) that
+need to be met before someone can think about higher level needs (like
+self-actualization, although to be honest I'm not exactly sure what that phrase
+means).
+
+I think it's useful to think about a hierarchy of needs for a Dev Ops
+organizations as well, although there are some major differences. First, for
+any given need, you don't need to have it completely solved before you go on to
+the next level. In fact, it's often better to make sure every level has a
+minimal system in place before going back and thinking about what an improved
+version looks like. In this talk we'll go over several levels, from basic to
+advanced, and discuss both a bare minimum solution as well as how to iterate to
+something better. Specifically, we'll discuss:
+
+- Logging: Why it's the foundation for every other category of need. The bare
+ minimum here is quite minimal, but spending some time adding capabilities
+ like semantic logging and full-text search can have a huge impact.
+
+- Monitoring: If you have any sort of SLA / SLO you need to be proactively
+ notified of issues. We'll go over the difference between tickets and alerts,
+ and how to tame whatever system you currently have in place to get the volume
+ to a reasonable level.
+
+- Incident response: A little bit of planning can greatly reduce stress and
+ mean time to recovery when things go sideways. We'll talk about how to
+ implement incident commanders, response playbooks, and how to communicate
+ with the rest of the org during an incident.
+
+- The release process: Arguably the highest value and highest risk activity.
+ This includes simple and more complex ways of qualifying a release, the 3
+ questions I always ask before a deploy, and techniques for releasing without
+ causing downtime.
+
+- Capacity planning: Crucial for moving your organization from reactive to
+ proactive. This isn't just tracking CPU and memory usage, although that's a
+ start, but systematically identifying resource constraints and strategies for
+ figuring out their breaking point.
+
+The examples will be drawn from what I've seen work (and sometimes not work)
+since joining the the Dev Ops team at Duo Security this year and from my 6
+years as a technical co-founder at Olark before that.
diff --git a/exampleSite/content/events/2016-detroit/program/metrics-are-infra-metrics-are-code.md b/exampleSite/content/events/2016-detroit/program/metrics-are-infra-metrics-are-code.md
new file mode 100644
index 000000000..bfed29ad1
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/metrics-are-infra-metrics-are-code.md
@@ -0,0 +1,44 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Metrics are Infra, Metrics are Code: Yelp’s time series data at scale"
+type = "talk"
+
++++
+
+**Speaker**: Zach Musgrave, Yelp
+
+It’s 2016, and “measure absolutely everything” is the new normal. Servers are
+cheap, and data is abundant. Time series data drives engineering and business
+decisions, and systems enabling such high-scale collection must scale along
+with the rest of the organization.
+
+Over the years, Yelp accumulated many ways of generating metrics, monitoring,
+doing analytics, and alerting. In the past year, a dedicated metrics team
+formed to integrate and maintain all the tools as a platform for the wider
+engineering organization - providing monitoring as a service. To achieve this,
+principles from the Infrastructure as Code movement become essential: ephemeral
+servers managed within version control, distributed configuration management
+via CI/CD pipelines, and aggressive containerization of federated resources via
+PaaS techniques.
+
+Join us to hear about auto-scaling stateful aggregation systems that don’t want
+to auto-scale. Listen in for tools that work across vendors, libraries
+supporting in-house innovation, and a strong push toward self-service metrics
+for all our internal users. Check out Yelp’s approaches to redundant alerting,
+ cheap yet resilient storage, and expressive client libraries that actually
+ don’t suck.
+
+“Who monitors the monitors?” We do.
+
+#### Speaker bio ####
+
+Zach Musgrave is the Tech Lead for Yelp’s Metrics team, which provides the
+instrumentation, monitoring, and alerting platforms for Yelp’s Engineering and
+Operations teams. From graduate school onwards, Zach has worked in performance
+optimization: from individual systems and code paths to cluster wide service
+performance for thousands of machines. At Yelp, he’s also worked on large scale
+deployment infrastructure, Hadoop operations, and key management. Back in the
+day, Zach was an English major.
+
+
diff --git a/exampleSite/content/events/2016-detroit/program/migrating-legacy-infrastructure-to-kubernetes.md b/exampleSite/content/events/2016-detroit/program/migrating-legacy-infrastructure-to-kubernetes.md
new file mode 100644
index 000000000..8706350bb
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/migrating-legacy-infrastructure-to-kubernetes.md
@@ -0,0 +1,23 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Migrating legacy infrastructure to Kubernetes: Olark’s lessons from the trenches"
+type = "talk"
+
++++
+
+**Speaker**: Brandon Dimcheff, Olark
+
+When you start building new infrastructure from scratch, it’s relatively easy
+to take into account the constraints that Docker and Kubernetes impose.
+Unfortunately most of us aren’t starting brand new projects, but are
+maintaining and migrating legacy infrastructure that may not be well suited to
+run on Kubernetes. Over the past several months, Olark has migrated a number
+of services that were never designed with Kubernetes or Docker in mind from
+over 200 puppet-managed Ubuntu VMs to Google Container Engine. Brandon will
+share some of Olark’s successes and failures, so that hopefully you can have a
+good starting point and avoid making the same mistakes that they did. He’ll
+also answer some questions like: How can I set up DNS and VPN so that I can
+route between my legacy infrastructure and Kubernetes services? I have a
+stateful application, can (or should) I still use Kubernetes? What are some
+things I can do to reduce the risk involved in a large-scale migration?
diff --git a/exampleSite/content/events/2016-detroit/program/moving-from-regular-sysadmin.md b/exampleSite/content/events/2016-detroit/program/moving-from-regular-sysadmin.md
new file mode 100644
index 000000000..5b5e108c9
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/moving-from-regular-sysadmin.md
@@ -0,0 +1,21 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Moving from a regular sysadmin role to a DevOps role"
+type = "ignite"
+
++++
+
+**Speaker**: Oguz Pastirmaci, Microsoft
+
+I was the regular enterprise sysadmin: network administrator & datacenter
+systems engineer in an ISP, IT operation support administrator in a retail
+company and IT systems engineer in a software development company. I spent time
+on choosing cool names for my servers. I knew the exact location of a server in
+the datacenter. I felt sad when their lights stopped blinking. I felt more sad
+it that happened on a weekend night.
+
+And then I joined a team adopting the DevOps mindset. Let me be honest: change
+was scary! But it was also a great learning experience. This talk will share
+what was challenging and what worked for me in my transition from being a
+regular sysadmin to living and breathing DevOps.
diff --git a/exampleSite/content/events/2016-detroit/program/putting-on-the-suit.md b/exampleSite/content/events/2016-detroit/program/putting-on-the-suit.md
new file mode 100644
index 000000000..8e1481d70
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/putting-on-the-suit.md
@@ -0,0 +1,29 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Putting on the Suit"
+type = "ignite"
+
++++
+
+**Speaker**: Ry4an Brase, Duo Security
+
+
+ Engineer. Dev. Coder. The person who can find the minimal regex to match any
+ three strings. These are key parts of my self-identity. I’d been a
+ coder-who-also-manages for more than a decade, but when offered a promotion to
+ a position featuring spreadsheets instead of terminal windows, I was more
+ afraid than excited. I made a list of concerns, and had a frank discussion
+ with my CEO. I was worried about having a gap in actual work if I left pure
+ management. I was worried about earning the respect of new team members if
+ they only knew me as a suit and the author of legacy code they’re working to
+ refactor. And I was worried about not enjoying my work anymore.
+
+Now with sixteen months’ distance I know which of those concerns were valid
+and what I should have worried about that I didn’t even consider. I’ll also
+talk about how I structured the compensation adjustment, what was great
+about the new role, and why I’m back to being an individual contributor
+(and adapting to not having anyone to boss around).
+
+I’ll totally, sort-of, not-really manage to avoid a Neil Patrick Harris
+"Suit Up" joke.
diff --git a/exampleSite/content/events/2016-detroit/program/trough-of-disillusionment.md b/exampleSite/content/events/2016-detroit/program/trough-of-disillusionment.md
new file mode 100644
index 000000000..80bbf0a4e
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/trough-of-disillusionment.md
@@ -0,0 +1,42 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Enter the Trough of Disillusionment"
+type = "talk"
+
++++
+
+**Speaker**: Jim Drewes, Daugherty Business Solutions
+
+Developers love to solve problems, but we hate doing things more than once.
+DevOps has been exciting for developers because we can grassroots solve
+problems that help us avoid the repetitive work of releasing software. Gartner
+describes this shiny-new-toy phase we’re in as the “Peak of Inflated
+Expectations” according to their Hype Cycle curve. Unfortunately, what comes
+next is the “Trough of Disillusionment,” and developers will soon find
+themselves encountering this low point. Fortunately, this too shall pass and
+DevOps will rise up to take its proper place in the fabric of generally
+accepted software product development practices.
+
+In this talk Jim will explain what is going to happen in the next couple of
+years when the DevOps hype reaches the trough of disillusionment, and
+developers are forced to deal with an unpleasant new normal. Enterprise
+adoption will suck all the joy out of DevOps for a little while, and we’ll
+witness some claims that “DevOps is dead.” Jim will cover some of the industry
+and editorial trends that are the leading indicators that we’re about to hit
+the trough, as well as what sorts of impacts we’ll see once we get there.
+Additionally, Jim will present strategies for minimizing the negatives of the
+trough, and working through the politics and project failures to bring our
+industry and organizations to a lasting adoption of DevOps practices.
+
+
+#### Speaker Bio ####
+
+Jim Drewes is a leader in the St. Louis Software Architecture and Engineering
+practice for Daugherty Business Solutions, a leading IT consulting firm with
+nationwide offices. He leverages 15 years of experience in development and
+operations to bring leading DevOps practices to Fortune 500 organizations.
+When he’s not helping clients solve their big problems, Jim enjoys running,
+tinkering with Arduinos and Amazon Echos, or just playing with his four little
+boys.
+
diff --git a/exampleSite/content/events/2016-detroit/program/what-the-military-taught-me.md b/exampleSite/content/events/2016-detroit/program/what-the-military-taught-me.md
new file mode 100644
index 000000000..dc44d51af
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/what-the-military-taught-me.md
@@ -0,0 +1,63 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "What the Military Taught Me About DevOps"
+type = "talk"
+
++++
+
+**Speaker**: Chris Short
+
+**Intro**
+
+11 years in the US Air Force working in joint units/roles (meaning I worked
+with the Army, Navy, Marines, NSA, NRO, NGIA, CIA, etc.)
+
+Heavy IT focus but also worked with satellite communications, phone switches,
+foreign country transmission infrastructure, etc.
+
+Left USAF in 2010 and went into a Support Ops role. Bounced around to a few
+different places and have been working DevOps specifically for about two years
+now.
+
+**DevOps Points**
+
+Kanban - Work could not pile up around anyone. Tickets could be used to track
+activity; used less to prioritize when to do work. Sure certain missions,
+personnel required immediate attention but first in, first out applied more
+often than not and every team member was an equal (a project manager's dream).
+
+Documentation - A lot of the standards and instructions were high-level
+guidelines; actual implementation guides needed to be developed based off
+needs. Hardware/software requirements, configuration templates, etc. were all
+built and needed to be shared through various teams/networks. Odd one-off
+problems and solutions rarely were documented so I created a "What's The Fix?"
+wiki to identify weird problems and their solutions that were likely to be
+encountered again based off mission cycles
+
+Configuration Management - Version control systems were not readily used during
+my time in the military but boy it would have been really nice to have a
+subversion/mercurial/git repo. Config standards were maintained through tight
+access controls but were frequently modified based off discussed improvements.
+
+Fail Fast Because Ultimate Failure Is Not an Option - Do the unimaginable in a
+remote location under austere circumstances. Ideas had to be tested immediately
+and often needed to be abandoned quickly based off mission needs and war time
+circumstances.
+
+Diversity Was Everywhere - Black, Brown, Yellow, White, Green (sea/air/motion
+sick) did not matter to us. We were there to get the job done, period. Your
+gender did not matter, your socioeconomic status did not matter, and your
+ethnicity did not matter. If you didn't know something, you were taught. If you
+were color blind it didn't matter I could teach you to terminate Cat5e/Cat6
+with the best of them. If you were willing to learn, I was willing to teach.
+
+Conflict Resolution - The best idea rose to the top of teams. Rank seldom
+mattered so long as your idea was better. Input was constantly sought after
+from all parties.
+
+**Conclusion**
+
+I cannot stress how invaluable my time was in the Air Force. It made me who I
+am but it also taught me a lot of what DevOps is today. Don't overlook veterans
+in your attempts to diversify.
diff --git a/exampleSite/content/events/2016-detroit/program/women-in-technology.md b/exampleSite/content/events/2016-detroit/program/women-in-technology.md
new file mode 100644
index 000000000..eb04ef77a
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/program/women-in-technology.md
@@ -0,0 +1,37 @@
++++
+City = "Detroit"
+Year = "2016"
+title = "Women in Technology"
+type = "ignite"
+
++++
+
+**Speaker**: Tanya Atanasova, RightBrain Networks
+
+It’s 2016, and the tech field finally realizes why women in technology are so
+important. However, with many examples of powerful women in technology - i.e.
+Slack, Google Maps - why do women still shy away from engineering careers?
+Tanya Atanasova, RightBrain Networks’ Software Developer, reviews the
+professional and educational factors behind this question.
+
+There are many examples of very powerful women in technology. In fact, we can't
+go without women in technology. Interesting fact: The VP of Product of Slack is
+a woman. Her name is April Underwood. The VP of Google Maps is also a woman.
+Her name is Jen Fitzpatrick.
+
+Women account for approximately 70% of shoppers in the world. If you are
+developing a product or a service, most likely a woman will be purchasing it.
+Thus, it's important that the product is evaluated by a woman.
+
+In this presentation, I will focus on what ways women can make important
+contributions to technology, and point out factors as to what discourages women
+from joining the field - which includes taking a look at girls’ education and
+why there’s a stronger push towards art majors rather than science.
+
+#### Speaker bio ####
+
+Tanya Atanasova is a software engineer at RightBrain Networks and a Graduate
+from Boston University in major Computer Science. Tanya worked as a Software
+Engineer for a publishing company in Rhode Island before joining RightBrain
+Networks Engineering Team. Currently Tanya holds AWS Certified Associate
+Developer Certification.
diff --git a/exampleSite/content/events/2016-detroit/proposals.md b/exampleSite/content/events/2016-detroit/proposals.md
new file mode 100644
index 000000000..109a4061d
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/proposals.md
@@ -0,0 +1,15 @@
++++
+City = "Detroit"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-detroit/propose.md b/exampleSite/content/events/2016-detroit/propose.md
new file mode 100644
index 000000000..dacf3b92e
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/propose.md
@@ -0,0 +1,48 @@
++++
+City = "Detroit"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
+Some example topics:
+ Including but not limited to:
+
+
Introducing cloud computing to skeptics
+
The virtues of diversity hiring
+
How to manage on-call effectively
+
How to get your team to care about security
+
DevOps means educating, sharing, and building trust
+
How to resolve technical disagreements in your organization
diff --git a/exampleSite/content/events/2016-detroit/sponsor.md b/exampleSite/content/events/2016-detroit/sponsor.md
new file mode 100644
index 000000000..e829121ee
--- /dev/null
+++ b/exampleSite/content/events/2016-detroit/sponsor.md
@@ -0,0 +1,48 @@
++++
+City = "Detroit"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Platinum sponsorships come with all of the benefits of a Gold sponsorship, with the addition 2 dedicated sponsor banners in high traffic/high visibility locations. Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Bronze 1000 USD
+
Silver 3000 USD
+
Gold 5000 USD
+
Platinum 10000 USD
+
+
+
High Visibility Dedicated Sponsor Banner (x2)
+
2 included tickets
+
logo on event website
+
logo on shared slide, rotating during breaks
+
logo on all email communication
+
logo on its own slide, rotating during breaks
+
1 minute pitch to full audience (including streaming audience)
+
2 additional tickets (4 in total)
+
4 additional tickets (6 in total)
+
shared table for swag
+
booth/table space
+
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, send us an email at {{< email_organizers >}}
+
+ View the {{< event_link page="program" text="program." >}}
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter devopsdaysdet >}}
diff --git a/exampleSite/content/events/2016-ghent/conduct.md b/exampleSite/content/events/2016-ghent/conduct.md
new file mode 100644
index 000000000..5119bac4d
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-07T09:25:01-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-ghent/contact.md b/exampleSite/content/events/2016-ghent/contact.md
new file mode 100644
index 000000000..5ef84935f
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-07T09:25:01-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-ghent/location.md b/exampleSite/content/events/2016-ghent/location.md
new file mode 100644
index 000000000..0d051e421
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/location.md
@@ -0,0 +1,15 @@
++++
+date = "2016-05-07T09:25:01-05:00"
+title = "location"
+type = "event"
+
++++
+
+Devopsdays Ghent will be held at Zebrastraat
+Address: Zebrastraat 32, 9000 Gent, Belgium
+Phone: +32 471 31 00 01
+How to get there
+
+Looking for accomodation?
+
+{{< event_map >}}
diff --git a/exampleSite/content/events/2016-ghent/program.md b/exampleSite/content/events/2016-ghent/program.md
new file mode 100644
index 000000000..7053a67de
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/program.md
@@ -0,0 +1,324 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
Title:
+Serverless as a Collaborative Economy enabler
+
+
+
Description:
+
+
+In recent years, the uprise of the cloud has brought us a lot of new and disruptive technology. Everybody is talking about SaaS, PaaS, IaaS and other aaS’es. In 2014 Amazon launched AWS Lambda as the pinnacle of the cloud computing. It allows developers to focus on code, without spending time on managing servers. The goal of this talk is not only introducing the serverless architecture style, but also tackle popular myths regarding “No More Servers” and “No More Ops”. Throughout the talk, we will focus on a “collaborative economy” approach to explain these concepts.
+
+This talk reports about the introduction of an OpenStack based private cloud at the iMinds-DistriNet research group. (1) The process taking away “pets” and giving them “cattle”. (2) Technical and management challenges for managing a virtual environment with very diverse requirements.
+
+
+
Description:
+
+This talk reports about the introduction of an OpenStack based private cloud at the iMinds-DistriNet research group. This group consists of about 80 researchers and works on security, distributed systems and software engineering. This internal project started in 2012 and is still ongoing. The talk will zoom on two aspects: (1) The process: in four year we went from almost 100% shadow IT for experiments, to a single platform for most experiments. This means taking away “pets” and giving them “cattle”. (2) Technical and management challenges: during this process we encountered many challenges related to managing the virtual environment for a diverse set of research experiments: data intensive, distributed, cpu-intensive and security sensitive.
+
+
+
+As Devops is a cultural movement, how do you certify culture? There is no exam that can certify how effectively you communicate with other people, how well teams in your company work together, how your organization learns, or anything else like that. However, I believe that certification is key to inspire other people to engage in the Devops movement.
+
+My Ignite Talk will be about the Why, How and What of Devops certification.
+
+The Why part elaborates on the purpose and benefits. The How part gives some practical examples of how to submerge into knowledge about Devops. The What part is about the questions you have to ask yourself before applying for (any) certification.
+
+To my opinion Devops certification has value because it is an instrument to measure if you know enough about Devops to be taken seriously when you initiate practices in your organizations or when you try to help other people become more Devops.
+
+Therefore, certify to inspire!
+
Title:
+Deploy HA MySQL environment using Puppet and MySQL Group Replication
+
+
+
Description:
+This talk is covering the automation of MySQL HA environment setup using Puppet. All members of the InnoDB Cluster will be replication from each other (no asyncrhonous master/slave replication anymore) using the new MySQL Group Replication. This replication is much easier to deploy than usual MySQL replication as every members are equals. We will use a dedicated puppet module and hiera to setup our environment and important decision and variables will be highlighted and explained. The session finishes with a full cluster deployment on Vagrant in 2 minutes.
+
Title:
+"We'll do it Live!" - Why you should test your software in production
+
+
+
Abstract:
+The most valuable type of software testing happens with production workloads, within a production setting. Thus, developers should limit the amount of time that they spend on pre-production testing, and optimize for shipping software to production as soon as possible.
+
+
+
+
Description:
+
+
+All pre-production software is happy; every software project in production can be unhappy in its own way. With software there are many factors that can lead to unhappiness, and unfortunately we human developers can only imagine a subset of these. Production traffic and production infrastructure are the best tools that we have for revealing flaws in our software, and so developers should optimize for shipping software to production as quickly as possible.
+
+When you’re building or improving a service that customers rely on (like PagerDuty), shipping software to production can be an intimidating task. One of the things that makes this task less intimidating is extensive testing in pre-production, sometimes with representative load. However, this is can be expensive in terms of time, and it can often be a source of false comfort.
+
+This talk will argue that the most valuable type of software testing happens with production workloads, and that with the right safeguards, this should happen within a production setting. This will be illustrated with examples from real-life software projects. This talk will examine what you’ll need to have in place for effective production testing - an organization that takes DevOps seriously, is able to move quickly, and an architecture that is capable of limiting the “blast radius” of production software failures.
+
+For decades, sales reps were told they had to act like a dealer in a car showroom. “Sir, this brilliant vehicle has a 320 bhp V8 engine and is made of lightweight aluminium, has Power Assisted Steering and a double wishbone suspension for a smooth and comfortable ride.” And amazingly, this approach worked. But times have changed.
+
+
+
Description:
+
+Because of the (mobile) internet, consumers have more information then ever before, available at any moment. And social media has given consumers an even stronger platform. They can now ask friends and family to share their opinions on brands, products and services. People expect brands and companies to be honest now. Because they will find out if they’re not.
+
+Bringing operations and development together is already an implementation of this new approach. The first thing we ask when a potential customer sends us an e-mail, asking for an offer is “What does the website/application actually do? Can you give us an estimate on the amount of visits? Does your website/application make use of Varnish, Solr … ? How much RAM do you think you’ll need?”
+
+By providing us with as much information as possible, we have a better insight in what the customer needs. Looking at an application from an operational point of view, we advise our clients to make changes in certain aspects of development. Together with our clients, we can make the application faster, easier and better.
+
Title:
+Running against the oneway: push the hassle from production to developers. Easily.
+
+
+
Description:
+
+
+
+
+In pre-production, there’s lots of tools that help optimizing your code: debuggers, CI/CD, load tests, etc. There’s even tools that automatically deploy them into production. Plus, engineers usually have a whole sprint as a time frame. Once you’re in production, things are a bit different and all that convenience is just not there for operators. They need to be able to pinpoint trouble spots within minutes. They have to identify the handful of bad requests out of thousands that allows for reproduction of the problem. And then, they are finally required to hand all that information over to the developers as convenient and as soon as possible. And nothing of that is automated.
+
+Performance monitoring, call-tracing and visualization are the concepts any developer should know about to be able to provide as much insight as possible into running systems. This session introduces open-source tools that allow devs and ops to work together much closer. To name just a few: * statsd / collectd * Zipkin * Spring-Cloud Sleuth * and some more
+
+For the sake of completeness and to also cover the Enterprise user-space, the main commercial vendors in that space will also be mentioned real quick.
+
+After that session, you’ll see new ideas popping up inside your head and already have all the knowledge you need to directly jump into planning and implementation.
+
+Ever wondered how “Clash of Clans” could make $5M/day with a “free” game? Or why Netflix has insane customer support? That’s because they “design for valorization”, not just functionality. This talk will introduce data driven product management as one of the key functions in modern tech companies.
+
+
+
+
+
Description:
+
+
+It’s hard to be a successful software company today: sure, lean startup told us to build MVP’s,* Open Source* and the Cloud provides us with building blocks galore to build and run large, complex applications, the DevOps community gave us plenty of tools and insights to make sure these large apps run smoothly. All this makes it easier to build and launch a good software product. No wonder that today’s users are spoiled with gorgeous apps that are available 24x7, for (almost) free. That’s why a modern software company needs to “design for valorisation”, i.e. actively design, implement, test and measure how they make money.
+
+Take games like Clash of Clans: these “free to play” games contain many mechanics that keep players play. By buying virtual money via in-app purchases, players speed up their progress. Behind the scenes though, this whole experience is measured, analysed and fine-tuned to ensure that players don’t get too annoyed with the slow, unpaid progress, yet are incentivised enough to buy the credits.
+
+For Netflix, operating in a very competitive market, with a technical infrastructure that is far from trivial, every $7.99 counts. That’s why they listen so much to customers, and why their customer support is stellar. [Remember this Star Trek story?] (http://imgur.com/e0LcT6J)
+
+Setting up a working designing for valorisation strategy requires strong analytics, a lot of data science, experiments and probably above all, a strong view on how users experience your product or service. This is traditionally the role of software product manager.
+
+In this talk, we’ll discuss how IMHO a modern (SaaS) software product manager should look at her job, how she can leverage DevOps practices on the product level and I’ll end with some tips and advice on how to start.
+
+How the financial organisation of companies make people work inefficient, and create frustration? Is it another way?
+
+
+
Description:
+
+
+This talk is about how financially minded management of companies lead to split the IT management into several business units, each with its own goals and management. This split creates misalignment and conflicts between teams that were supposed to work together.
+
+This talk is a toolbox designed to help you bring proper implementation of devops and to make people work together on a common goal: efficient automatisation and use of the human brain power geared towards making IT an asset instead of a cost center.
+
+
+Ever been to a conference, get inspired, try to bring what you learned back to the office, only to be stymied by co-workers who aren’t interested in rocking the status quo? It turns out that people tend to resist change in patterns, and like any pattern they can be overcome by using other people’s experiences with those skeptics. This session will teach you how to identify the skeptics, how to counter them, and give you a strategic framework to convince your whole office.
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-ghent/propose.md b/exampleSite/content/events/2016-ghent/propose.md
new file mode 100644
index 000000000..a82cd4def
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-07T09:25:01-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-ghent/speakers.md b/exampleSite/content/events/2016-ghent/speakers.md
new file mode 100644
index 000000000..7c0e5ce33
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-10-01T13:18:07+02:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-ghent/sponsor.md b/exampleSite/content/events/2016-ghent/sponsor.md
new file mode 100644
index 000000000..ffeb25bcf
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/sponsor.md
@@ -0,0 +1,43 @@
++++
+date = "2016-05-07T09:25:01-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}} .
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
+
packages
+
Silver 1500€
+
Gold 3000€
+
+
+
included tickets
2
4
+
logo on event website
+
logo on all email communication
+
shared table for swag
+
booth/table space
+
1 minute pitch to full audience (including streaming audience)
+
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, please drop us an email at {{< email_organizers >}}.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-ghent/welcome.md b/exampleSite/content/events/2016-ghent/welcome.md
new file mode 100644
index 000000000..ec7dcd472
--- /dev/null
+++ b/exampleSite/content/events/2016-ghent/welcome.md
@@ -0,0 +1,110 @@
++++
+date = "2016-05-07T09:25:01-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-ghent"]
+
++++
+
+## devopsdays is coming back to Ghent
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+
+
The DevOpsDays Belgium team didn't want to wait another 5 years to bring the conference back to Belgium.
+
+
+
Enjoy two full days of presentations followed by open space discussions, with topics spanning the range of Automation, Metrics, Culture, and Sharing. At the end of each day, expect evening social events, both organized and ad hoc.
+
+
Included in the price are 2 days of conference attendance, breakfast, hot lunch, drinks and dinner/happy hour the
+ first day.
+
+
NOTE: we send invoices for all orders. If you want your TVA id on the invoice, please register
+ as a business and fill in the TVA Registration ID field. We can not change this
+ afterwards!
+
+
+
+
+{{< event_twitter devopsdays >}}
diff --git a/exampleSite/content/events/2016-istanbul/conduct.md b/exampleSite/content/events/2016-istanbul/conduct.md
new file mode 100644
index 000000000..1ca9cae10
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+##ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+##CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-istanbul/contact.md b/exampleSite/content/events/2016-istanbul/contact.md
new file mode 100644
index 000000000..e641865cb
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-istanbul/location.md b/exampleSite/content/events/2016-istanbul/location.md
new file mode 100644
index 000000000..7a5ebc236
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/location.md
@@ -0,0 +1,12 @@
++++
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
++++
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/a-developers-journey-into-building-automated-tests-for-it-from-the-ground-up/index.md b/exampleSite/content/events/2016-istanbul/proposals/a-developers-journey-into-building-automated-tests-for-it-from-the-ground-up/index.md
new file mode 100644
index 000000000..2a3fb52b5
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/a-developers-journey-into-building-automated-tests-for-it-from-the-ground-up/index.md
@@ -0,0 +1,24 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "A developer's journey into building automated tests for IT from the ground up"
++++
+
+**Abstract:**
+
+Having learned the benefits of applying TDD to application code, my team decided to apply the same technique to infrastructure code. There isn't quite as much literature available, and we faced many challenges, but we ended up with a rewarding result: a continuous integration server that runs tests at several levels, including acceptance tests. The technology stack involves Chef, Test Kitchen, Vagrant, KVM, Serverspec and Jenkins. Although each one of these parties has at least a good level of maturity, integrating all the blocks has been the interesting part.
+We discuss how to put together virtualization solutions, configuration management and BDD specs to converge into a fully automated continuous integration system that can and, in our opinion, should become part of the workflow for DevOp teams."
+
+
+I plan to include a practical demonstration of the concepts discussed by using most of the tools involved.
+
+The idea for the presentation came from observing the positive reaction from the DevOps community after the publication of the following blog post that I wrote myself:
+http://www.agilosoftware.com/blog/configuring-test-kitchen-jenkins/
+
+Basically the interest revolves around the fact that although there are good tools to treat infrastructure code with the same dignity and professionalism as application code, there is not as much maturity in the ways to converge all the parts into an integrated solution, and ours is a possible approach to this problem.
+
+**Speaker:**
+Stefano Rago
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/a-security-state-of-mind-continuous-security-for-containers-in-devops/index.md b/exampleSite/content/events/2016-istanbul/proposals/a-security-state-of-mind-continuous-security-for-containers-in-devops/index.md
new file mode 100644
index 000000000..907a885f2
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/a-security-state-of-mind-continuous-security-for-containers-in-devops/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "A Security State of Mind: Continuous Security for Containers in DevOps"
++++
+
+**Abstract:**
+
+With the rise of DevOps, containers are at the brink of becoming a pervasive technology in Enterprise IT in order to accelerate application delivery for the business. When it comes to adopting containers in the enterprise, Security is the highest adoption barrier. Is your organization ready to address the security risks with containers in a DevOps environment?
+
+**Speaker:**
+Chris Van Tuin
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/an-audit-compliant-paas-on-top-of-aws/index.md b/exampleSite/content/events/2016-istanbul/proposals/an-audit-compliant-paas-on-top-of-aws/index.md
new file mode 100644
index 000000000..a13567301
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/an-audit-compliant-paas-on-top-of-aws/index.md
@@ -0,0 +1,25 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title ="An Audit-Compliant PaaS on Top of AWS"
++++
+
+**Abstract:**
+
+Zalando is a public company with more than 85 development teams. Unlike some other public companies, deployments are not a bottleneck here. This talk will show how one public company applies microservice architecture in an audit compliant way with the help of open source tools. No magic, no propriety software involved here. Tools we use work on top of AWS.
+
+Even if you do not use any of the open-source tools developed by our technology team, one can still benefit from ideas on how deployments and infrastructures can be managed in an audit compliant way.
+
+I will show briefly:
+
+* How we leverage immutability instead of standard Docker Registry (Pier One)
+* How we dropped mail chains for deployment approvals which no one ever reads (Kio)
+* What parts of infrastructure we decentralised and centralised (Taupage, ZMON)
+* How we allow developers access to even production environments (Even&Odd)
+* How we change credentials among applications (mint&berry)
+
+**Speaker:**
+Şenol Çağdaş
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/automating-the-quality-cycle-for-devops-acceleration/index.md b/exampleSite/content/events/2016-istanbul/proposals/automating-the-quality-cycle-for-devops-acceleration/index.md
new file mode 100644
index 000000000..d6142da4c
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/automating-the-quality-cycle-for-devops-acceleration/index.md
@@ -0,0 +1,17 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Automating the quality cycle for DevOps acceleration"
++++
+
+**Abstract:**
+
+* Apply mathematical techniques to understand what assets are required for testing
+* Leverage automation to create the assets
+* Apply automation to execute
+
+**Speaker:**
+Huw Price
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/boost-your-devops-adaptation-with-openshift-paas/index.md b/exampleSite/content/events/2016-istanbul/proposals/boost-your-devops-adaptation-with-openshift-paas/index.md
new file mode 100644
index 000000000..aa39446fc
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/boost-your-devops-adaptation-with-openshift-paas/index.md
@@ -0,0 +1,14 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Boost your DevOps adaptation with OpenShift PaaS"
++++
+**Abstract:**
+
+Although the DevOps itself is more about cultural change in IT rather than technology stack, right tooling is also crucial for successful DevOps adaptation and PaaS platforms are one of the most important enabler tools of DevOps. Red Hat's open source technology OpenShift is one the leading technology in PaaS landscape that uses Docker containers as deployment units and Kubernetes as orchestration technology. OpenShift itself sits on top of those technologies and adds seamless & painless developer user experience for both developers and operations. It offers application management at scale, source code management, CI/CD processes, team collaboration and organization, self-service capabilities. In my presentation I'll briefly introduce Docker container technology and ways of orchestrating containers with Kubernetes at enterprise scale, benefits of OpenShift to boost up development lifecycle and also give an example demonstration of developing micro service applications with automated CI/CD pipeline.
+
+**Speaker:**
+Serhat Dirik
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/building-a-serverless-data-pipeline-with-aws/index.md b/exampleSite/content/events/2016-istanbul/proposals/building-a-serverless-data-pipeline-with-aws/index.md
new file mode 100644
index 000000000..fdf6aaa7e
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/building-a-serverless-data-pipeline-with-aws/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Building a serverless data pipeline with AWS"
++++
+
+**Abstract:**
+
+Collecting web data for both real-time and batch analytics is a common problem. Of course, there are many ways to solve it, but they often require a lot of complex IT plumbing which creates even more issues around scalability, reliability, performance and monitoring. Wouldn’t you rather spend time working on your business projects, creating value for your company and your customers ? The purpose of this presentation is to show you how you can quickly build such a pipeline, using a serverless architecture based on highly available, highly scalable AWS managed services… and very little code. After a brief introduction to AWS Lambda, we’ll build the pipeline step by step, using API Gateway, Lambda, DynamoDB, DynamoDB streams, Kinesis Firehose, CloudWatch Events and S3. And of course, we’ll run some tests !
+
+**Speaker:**
+Julien Simon
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/containers-devops-apache-mesos-and-cloud-reshaping-how-we-develop-and-delivery-software/index.md b/exampleSite/content/events/2016-istanbul/proposals/containers-devops-apache-mesos-and-cloud-reshaping-how-we-develop-and-delivery-software/index.md
new file mode 100644
index 000000000..7d6698bab
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/containers-devops-apache-mesos-and-cloud-reshaping-how-we-develop-and-delivery-software/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Containers, DevOps, Apache Mesos and Cloud - Reshaping how we Develop and Delivery Software"
++++
+
+**Abstract:**
+
+Container technology are being evaluated by software developers and administrators with a great deal of interest. Developers want to focus on what they do best: Creating and coding new applications. That shouldn't have to change just because they need to deploy an application to a different environment. Administrators want the environment to stay reliable and stable, keeping changes at a minimum. By following a strategy that embraces good Architecture, use of Containers, DevOps philosophy, Apache Mesos and a Cloud based environment, developers and operators can create, consume and collaborate on the infrastructure configuration over the time, deploy Java EE applications and test your application infrastructure consistently regardless of the stage of the development life cycle.
+
+**Speaker:**
+Marcelo Sousa Ancelmo
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/continuous-delivery-at-github-with-hubot/index.md b/exampleSite/content/events/2016-istanbul/proposals/continuous-delivery-at-github-with-hubot/index.md
new file mode 100644
index 000000000..da8a75760
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/continuous-delivery-at-github-with-hubot/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Continuous delivery at GitHub with Hubot"
++++
+
+**Abstract:**
+
+On a daily base, GitHub’s developers push about 40 different changes to the production platform. I would like to walk you through the workflow and tools we use to achieve this, and introduce you to the hardest working employee of the company, Hubot.
+
+**Speaker:**
+Alain Hélaïli
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/database-lifecycle-management-getting-it-right/index.md b/exampleSite/content/events/2016-istanbul/proposals/database-lifecycle-management-getting-it-right/index.md
new file mode 100644
index 000000000..fc63ba435
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/database-lifecycle-management-getting-it-right/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Database Lifecycle Management: Getting it Right"
++++
+
+**Abstract:**
+
+Frequent releases to our applications are an important part of keeping them healthy. With modern tools, it’s easy to frequently and automatically generate the application release artifacts. However, this process requires a little more thought when it comes to relational database schema changes. If you’ve ever tried to regularly deploy changes to a SQL Database, you know exactly what I mean. Thankfully, there is some guidance to help us along the way. Let me introduce you to Database Lifecycle Management (DLM) – a set of patterns and practices for getting your database changes from your development machine to production while leaving the pain behind. During this talk, I’ll run through the core concepts of DLM, with samples and demos to show you how it’s possible to make your database schema deployments just another part of your continuous delivery setup. By the end of this talk, you will have a clear understanding of the challenges of database continuous delivery, the advantages of embracing DLM, and how to adapt your existing processes to start painlessly delivering your databases right away.
+
+**Speaker:**
+Alain Hélaïli
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/devops-tactical-adoption-theory/index.md b/exampleSite/content/events/2016-istanbul/proposals/devops-tactical-adoption-theory/index.md
new file mode 100644
index 000000000..ea2575636
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/devops-tactical-adoption-theory/index.md
@@ -0,0 +1,23 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "DevOps: Tactical Adoption Theory"
++++
+
+**Abstract:**
+
+DevOps is a state of art describing each software development step as a repeatable, automatable and deterministic process excluding error-prone human factor first time in the history of software development. The model defines the entire value chance from concept to concrete product. It is an evolutionary end for the models of software development and agile movement. But, there is a problem with the concept; though described easily, implemented a little hard.
+
+DevOps Tactical Adoption Theory tries to make the transition process as smooth as possible. It hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step. The innovative idea here, it is not required to add the tools/processes to stack from sequential beginning to end, but seeking benefit.
+
+The reason behind the theory is to encourage practitioners to apply each step one-by-one and then having the benefits in projects. Consequently, each step is tested in terms of utility and proved method validity for the further steps. In contrast to previous adoption models, for example the one publish by Inedo[1], our model indicates concrete activities rather than general statements.
+
+Theory built on the claim that many DevOps transition projects considered problematic, impractical or even unsuccessful causing concept to become a goal more than a technique. Basically, theory consists of different areas of interest describing various actions on a schema.
+
+In the session, it is planned to demonstrate “Tactical DevOps Adoption Theory” with focus on Testing Practices sectioned "Continuous Testing in DevOps".
+
+**Speaker:**
+Berk Dülger
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/getting-into-the-zero-downtime-deployment-world/index.html b/exampleSite/content/events/2016-istanbul/proposals/getting-into-the-zero-downtime-deployment-world/index.html
new file mode 100644
index 000000000..2c2893c7a
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/getting-into-the-zero-downtime-deployment-world/index.html
@@ -0,0 +1,16 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Getting Into the Zero Downtime Deployment World"
++++
+
+**Abstract:**
+
+Continuous delivery is a huge step forward in our ability to rapidly deliver features and value to the users of distributed applications, but it comes with a cost and a responsibility. Most modern web applications need to be highly available, and this also means that it should be up during the deployments. Dealing with zero-downtime deployments is a challenge, and there is no easy solution. Moreover, the solutions available vary based on the number of integrated clients, which parts of the World it addresses, how many active users it has... Isn’t there a simple way to figure out how to get there? Join me to get into the details of the key steps on your path to zero downtime deployments. Learn about the patterns, practices and techniques that make it easier, such as semantic versioning and blue/green deployments. We’ll also walk through an end-to-end demo of how a high traffic web application can survive the challenge of deployments. What seemed insurmountable at the start of the session will be practical and applicable by the time we’re finished, and you should be able to see how to start moving your production application close to the zero-downtime gold standard.
+
+
+**Speaker:**
+Alain Hélaïli
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/how-an-organization-can-successfully-adopt-devops-principals/index.md b/exampleSite/content/events/2016-istanbul/proposals/how-an-organization-can-successfully-adopt-devops-principals/index.md
new file mode 100644
index 000000000..1bd1f2b2d
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/how-an-organization-can-successfully-adopt-devops-principals/index.md
@@ -0,0 +1,17 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Continuous Delivery & DevOps CoE, how an organization can successfully adopt DevOps principals"
++++
+
+**Abstract:**
+
+* Where to start with DevOps and/or Continuous Delivery, some practical examples
+* How to get buy in from the business
+* How to build a CoE, some practical lessons
+
+**Speaker:**
+Simon Poulton
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/how-devops-culture-transformed-software-testing/index.md b/exampleSite/content/events/2016-istanbul/proposals/how-devops-culture-transformed-software-testing/index.md
new file mode 100644
index 000000000..58c193384
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/how-devops-culture-transformed-software-testing/index.md
@@ -0,0 +1,24 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "How DevOps Culture transformed Software Testing"
++++
+
+**Abstract:**
+
+In the DevOps World, testing and the QA role is extremely important. Continuous testing and test automation is simply a must. In this presentaion I’d like to talk about how we implemented automated test levels in various projects in Turkey. My talk will focus on Continuous Delivery Pipeline and cover these areas;
+
+* How to establish a testing culture in the team
+* Owning quality as a team
+* How to build automated checks before the production code (ATDD)
+* What levels of automation we put in (unit, CDC, journey, acceptance, regression, sit, XFR)
+* Checking the cross functional along with the functional automatically (performance, security)
+* How to scale your automation (dynamic provisioning, parallelisation)
+
+This talk would be interesting for the audience because this approach is not practiced very commonly in Turkey. People would like to hear about a complete set of testing levels. It would help draw attention to the technical side of testing and help establish a true DevOps culture in software teams.
+
+**Speaker:**
+Alper Mermer
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/how-to-move-forward-to-a-devops-culture/index.md b/exampleSite/content/events/2016-istanbul/proposals/how-to-move-forward-to-a-devops-culture/index.md
new file mode 100644
index 000000000..2fc9d6d39
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/how-to-move-forward-to-a-devops-culture/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "How to move forward to a DevOps culture?"
++++
+
+**Abstract:**
+
+The approaches, techniques and technologies which are promoting to have a DevOps mindset environment will be discussed - Automated Provisioning - Self-service IT - Containers - ChatOps - Autonomic Infrastructure - Automated Deployment - Deployment Techniques
+
+**Speaker:**
+Derya Sezen
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/index.md b/exampleSite/content/events/2016-istanbul/proposals/index.md
new file mode 100644
index 000000000..95f55a484
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/index.md
@@ -0,0 +1,45 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
This page lists the proposals we have received. Help the presenters with your feedback!
diff --git a/exampleSite/content/events/2016-istanbul/proposals/infinite-scalable-systems/index.md b/exampleSite/content/events/2016-istanbul/proposals/infinite-scalable-systems/index.md
new file mode 100644
index 000000000..798b4627c
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/infinite-scalable-systems/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Infinite Scalable Systems with Docker, Docker Swarm, and Docker Machine"
++++
+
+**Abstract:**
+
+I want to talk about Infinite Scalable Systems with Docker, Docker Swarm, and Docker Machine. In this session I will mention about Docker and history of containerization technology. I will also mention about Docker Machine to create machines along the cloud providers and then use Docker Swarm to setup native clustering beside those machines. At the end of session, I will show a quick demo.
+
+**Speaker:**
+Hüseyin BABAL
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/introduction-to-vagrant/index.md b/exampleSite/content/events/2016-istanbul/proposals/introduction-to-vagrant/index.md
new file mode 100644
index 000000000..7cfaf472e
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/introduction-to-vagrant/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Introduction to Vagrant"
++++
+
+**Abstract:**
+
+Sunumda Vagrant teknolojisinin ne olduğunu, neden kullanmamız gerektiğini anlatmaya çalışacağım. Vagrant ile geliştirme ortamlarının nasıl kolayca yönetilebileceğine değineceğim. Son olarak Vagrant ile ilgili bazı terminolojilere değinip, küçük bir örnek yapacağım Vagrant ile ilgili.
+
+**Speaker:**
+Mesut Özen
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/project-management-in-devops/index.md b/exampleSite/content/events/2016-istanbul/proposals/project-management-in-devops/index.md
new file mode 100644
index 000000000..712ac88fe
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/project-management-in-devops/index.md
@@ -0,0 +1,15 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Project Management in DevOps"
++++
+
+**Abstract:**
+
+DevOps is an extension of agile thinking. It is not a fad. It is a culture! As long as the agile based methodologies are hot topics, DevOps culture will be our concern, too. So, if DevOps is not a one size fits all, then we should start to change our management skills according to new game rules. In this session, the way of project management in DevOps will be presented.
+
+**Speaker:**
+Seçil Kavas
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/rkt-whats-coming-next/index.md b/exampleSite/content/events/2016-istanbul/proposals/rkt-whats-coming-next/index.md
new file mode 100644
index 000000000..af51ef778
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/rkt-whats-coming-next/index.md
@@ -0,0 +1,19 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "rkt, what's coming next"
++++
+
+**Abstract:**
+
+rkt is the next-generation container manager for Linux clusters. Designed for security, simplicity, and composability within modern cluster architectures, rkt discovers, verifies, fetches, and executes application containers with pluggable isolation.
+
+After 1.0 rkt has continued changing a lot, and judging by the amount of changes in the last months, it doesn't show signs of stopping! Come and learn what’s new in the rkt world, what challenges did we face recently and what are the plans for the future.
+
+The talk will include a brief introduction to rkt so don't hesitate to come even if you know nothing about it or about Linux containers in general.
+
+**Speaker:**
+Iago López Galeiras
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/the-future-of-infrastructures/index.md b/exampleSite/content/events/2016-istanbul/proposals/the-future-of-infrastructures/index.md
new file mode 100644
index 000000000..64c5532ab
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/the-future-of-infrastructures/index.md
@@ -0,0 +1,17 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "It automation & devops, what is the future of infrastructures?"
++++
+
+**Abstract:**
+
+The way IT change economy, work and the world is growing and impactful, and we just start to think about our process as IT workers. What is our role? Why developer efficiency is really important? How about deliverability velocity?
+
+This talk is focus on process, tools and organisation around the software delivery and focus about the infrastructure role. The goal is to give insight about architecture choices, arguments to promote projects and investments to the management, transitional vision and traditional IT integration.
+
+**Speaker:**
+Quentin Adam
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/the-m-in-clams-what-will-we-measure/index.md b/exampleSite/content/events/2016-istanbul/proposals/the-m-in-clams-what-will-we-measure/index.md
new file mode 100644
index 000000000..af55638a2
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/the-m-in-clams-what-will-we-measure/index.md
@@ -0,0 +1,21 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "DevOps - the M in CALMS, what will we measure"
++++
+
+**Abstract:**
+
+* In the CAMLS approach to DevOps the M is Measurement
+* What shall we measure?
+ - App usage
+ - App performance
+ - Code Stats
+ - Success factors
+* Some examples from the field
+
+**Speaker:**
+Simon Poulton
+
diff --git a/exampleSite/content/events/2016-istanbul/proposals/utilizing-devops-dynamics-for-security-orchestration-and-situational-awareness/index.md b/exampleSite/content/events/2016-istanbul/proposals/utilizing-devops-dynamics-for-security-orchestration-and-situational-awareness/index.md
new file mode 100644
index 000000000..2ef31d1eb
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/proposals/utilizing-devops-dynamics-for-security-orchestration-and-situational-awareness/index.md
@@ -0,0 +1,19 @@
++++
+City = "Istanbul"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+type = "event"
+title = "Utilizing DevOps dynamics for Security Orchestration and Situational Awareness"
++++
+
+**Abstract:**
+
+Using DevOps orchestration & BigData tools, we'll be demonstrating :
+ * Monitor: How to collect NetFlow data from both network devices and hosts
+ * Analyze: How to analyze NetFlow and various other log metrics utilizing ElasticSearch
+ * Detect : How to detect anomalies and aberrant traffic/activity
+ * Respond : Utilizing DevOps orchestration tools to faster reponse to incident and issues.
+
+**Speaker:**
+Kayra Otaner
+
diff --git a/exampleSite/content/events/2016-istanbul/propose.md b/exampleSite/content/events/2016-istanbul/propose.md
new file mode 100644
index 000000000..a177c3c9d
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/propose.md
@@ -0,0 +1,46 @@
++++
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+
+
+Call for proposals closed for 30 minutes talks,
+
+We still accept proposals for ignite talks as there are open slots.
+
+
+ {{< cfp_dates >}}
+
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider [commenting on proposals submitted by others](/events/2016-istanbul/proposals/)
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to {{< email_organizers >}} with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
diff --git a/exampleSite/content/events/2016-istanbul/sponsor.md b/exampleSite/content/events/2016-istanbul/sponsor.md
new file mode 100644
index 000000000..c631e6b1f
--- /dev/null
+++ b/exampleSite/content/events/2016-istanbul/sponsor.md
@@ -0,0 +1,56 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Bronze $1,000 USD
+
Silver $2,000 USD
+
Gold (max 5) $5,000 USD
+
Platinum (max 2) $10,000 USD
+
Host (max 1) Sold Out $10,000 USD
+
+
+
2 included tickets
+
Logo on DevOpsDays website
+
Logo on shared slide, rotating during breaks
+
3 minute pitch to full audience
+
2 additional tickets (4 in total)
+
4 additional tickets (6 in total)
+
Logo at the expo area
+
Shared Sponsor table in expo area and roll-ups
+
Private Sponsor table in expo area and roll-ups
+
Private meeting room for customer meetings and demos
+
Participation at the Opening Bell Ceremony
+
3 minute pitch at the Opening Bell Ceremony
+
5 minute opening welcome at the Opening Bell Ceremony
+
Logo on event t-shirt
+
Logo on event bag (logo size based on sponsorship)
+
Acknowledgement of the company as sponsor in the pre and post-bulletins of the event
+
+
+
+
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, {{< email_organizers >}} send us an email.
+
+
+
The team that brought you the monthly DevOps Turkey meetup is now
+organizing the 1st DevOpsDays in Istanbul. With a finely curated list of
+speakers and inspirational talks, June 3 - 4, 2016 will be the DevOps
+event no one should miss.
+
+
+
+
+
+
+
+
+
+
+
Dates
+
{{< event_start >}} - {{< event_end >}}
+
+
Location
+
{{< event_location >}}
+
+
Propose
+
{{< event_link page="propose" text="Propose a talk!" >}}.
+
+
Register
+
{{< event_link page="registration" text="Register to attend the event!" >}}
+
+
+
Program
+
View the {{< event_link page="program" text="program" >}}.
+
+
+
Sponsors
+
{{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
Contact
+
{{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
diff --git a/exampleSite/content/events/2016-kansascity/conduct.md b/exampleSite/content/events/2016-kansascity/conduct.md
new file mode 100644
index 000000000..be6824c57
--- /dev/null
+++ b/exampleSite/content/events/2016-kansascity/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-07T09:30:25-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-kansascity/contact.md b/exampleSite/content/events/2016-kansascity/contact.md
new file mode 100644
index 000000000..79b4b2dcd
--- /dev/null
+++ b/exampleSite/content/events/2016-kansascity/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-07T09:30:25-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-kansascity/location.md b/exampleSite/content/events/2016-kansascity/location.md
new file mode 100644
index 000000000..f148813be
--- /dev/null
+++ b/exampleSite/content/events/2016-kansascity/location.md
@@ -0,0 +1,14 @@
++++
+date = "2016-05-07T09:30:25-05:00"
+title = "location"
+type = "event"
+
++++
+
+Musical Theater Heritage in Crown Center
+2450 Grand Blvd #301, Kansas City, MO 64108
+The event will take place on the third floor directly up the escalators inside the door on Grand Boulevard.
+
+Take a Virtual Tour of this awesome venue!
+
+
diff --git a/exampleSite/content/events/2016-kansascity/program.md b/exampleSite/content/events/2016-kansascity/program.md
new file mode 100644
index 000000000..860946622
--- /dev/null
+++ b/exampleSite/content/events/2016-kansascity/program.md
@@ -0,0 +1,379 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+From the Phoenix Project there are three ways. This short talk is about the all important third way, which focuses on continual improvement and taking risks.
+
Title:
+Your Meetings Are Unbearable: Cheat Codes From Occupy
+
+
+
Description:
+
+
+Most work meetings are full of interruptions, repetitions and microaggressions, and tend to drag on forever.
+
+At Occupy, we used a simple, efficient horizontal decision-making process based on hand signals. In this talk, I'll show how to use these hand signals to cut meeting times in half.
+
+
Title:
+Innovating is not about technology, but psychology.
+
+
+
Description:
+
+
+Why do we do it? Why do we try so hard? Why are we paying to be here, to listen to people talk? Maybe because we’re life long learners - we want to learn new things? Commune with our own kind? But why? Come examine our motives as developers, the pitfalls we fall into, and the cost of being great.
+
+You may recognize the word "Ansible" from Ender's Game, however in the context of Systems Administration, it signifies an even greater tool than Orson Scott Card could ever imagine. This talk covers the basics of Ansible, a powerful IT automation tool, and how you can harness it in your IT team.
+
Title:
+Docker Container Lifecycles – Problem or Opportunity?
+
+
+
Description:
+
+
+Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is promotion-based model appropriate to control and track the flow of Docker images from development to production?
+
+If your company is bringing in millions in revenue, but still editing configs by hand, there’s a crisis of identity. We’ll share our experiences of growing small companies' platforms for resiliency and scale.
+
+Software changed and became distributed. Distributed applications are hard. We need logical models to understand how the software interconnects. Great operations knowledge is scarce. Sharing the operations is hard. We need tools that allow us to share the ops knowledge as easily as we share open source software.
+
Title:
+Secure Your Containers! What Network Administrators Should Know When Moving Into Production
+
+
+
Description:
+
+
+This session offers techniques for securing Docker containers and hosts using open source network virtualization technologies to implement microsegmentation. Come learn real tips and tricks that you can apply to keep your production environment secure.
+
Title:
+How Can You Scale It If You Don't Trust It?
+
+
+
Description:
+
+
+When you scale up an infrastructure it is crucial that you can trust you have the right resources in play, the right code deployed and that information can only flow in a secure manner. When you scale the organization, trust is required amongst all of the people responsible for coding, testing, deploying and managing the applications that power the business.
+
+With all of the chatter around scaling, you would think someone would have told you the key ingredient necessary for creating and fostering the required trust. Unfortunately it is very easy to get to the end of the diving board, right on the edge of jumping into something like a hybrid cloud deployment, before you realize you need to figure this out on your own.
+
+This talk can help. We'll discuss some concrete ways you can engineer trust into the system (complete with examples) you are building or operating so that it works well for cloud-native and legacy applications. By the end, you’ll have a good idea of the decision/enforcement points you'll need to consider to be able to create a system (and an organization) that can scale.
Title:
+Escaping the Black Hole of Release Management
+
+
+
Description:
+
+
+Why manually handle release management? It consumes entire teams, leaving no time for improvement or innovation. Escaping the gravitational pull of mundane tasks requires cultural change. This talk walks through incremental improvements possible while increasing the value you deliver to your team.
+
+Human Factors applies knowledge of human performance to the design of technology. DevOps changes the way we create and deliver software and infrastructure through the development of a myriad of new tools. Are the tools making the best use of how people work? What will it take to make more progress?
+
+A quick introduction / live demo of Habitat (www.habitat.sh) and how it fits into the current DevOps landscape. I will discuss some of the concepts Habitat brings such as "packaging the automation with the application" and how those concepts differ from other approaches.
+
+The intent of this talk is to define the place for business units at DevOps table to improve overall organization communication and tech team efficiency, including monitoring strategy, post-mortems, chatops and other DevOps-centric processes.
+
Title:
+Building a DevOps Enterprise Community Across 10 Businesses
+
+
+
Description:
+
+
+Kick-starting a DevOps transformation is daunting. Including all levels of the org is critical to success! I share the tactics of building a DevOps community across 10 business units inside HBM. The challenges, failures and ultimate successes that go into transforming culture, process and tools.
+
+If your company is bringing in millions in revenue, but still editing configs by hand, there’s a crisis of identity. We’ll share our experiences of growing Pinsight Media's platforms for resiliency and scale.
+
+With the advent of log aggregation tools, we can go beyond text logs and output rich payloads that give the context and detail needed to troubleshoot an application in prod. In this lightning talk, I go over some key aspects of modern JSON logging and the power of tools like Graylog or Splunk.
+
+Doing continuous delivery? Got nothing left to learn? Yeah right!
+
+The journey to continuous delivery (CD) is long, winding and always evolving. Come hear my stories, learn what worked and what didn't work for us and get some helpful tips!
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-kansascity/propose.md b/exampleSite/content/events/2016-kansascity/propose.md
new file mode 100644
index 000000000..64565ab74
--- /dev/null
+++ b/exampleSite/content/events/2016-kansascity/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-07T09:30:25-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}.
+
+Download the full sponsor prospectus for devopsdays Kansas City 2016!
+
+
+
+
+devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-kansascity/welcome.md b/exampleSite/content/events/2016-kansascity/welcome.md
new file mode 100644
index 000000000..083b1017d
--- /dev/null
+++ b/exampleSite/content/events/2016-kansascity/welcome.md
@@ -0,0 +1,98 @@
++++
+date = "2016-05-07T09:30:25-05:00"
+title = "Welcome"
+type = "event"
+aliases = ["/events/2016-kansascity"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+DevOpsDays is coming to {{< event_location >}} in Kansas City!
+
+Where large enterprise software companies and a growing startup community are fueled by the fastest internet in the world. With more than 500 members in the local DevOps Meetup group, this conference will draw an elite group. Come and enjoy excellent presentations from local and international experts as well as the famous hallway track.
+
+
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+
+
+ Register
+
+
+ {{< event_link page="registration" text="Register to attend the conference!" >}}
+
+
+
+
+
+ Program
+
+
+ View the {{< event_link page="program" text="program." >}}
+
+
+
+
+
+ Speakers
+
+
+ Check out the {{< event_link page="speakers" text="speakers!" >}}
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter devopsdayskc >}}
diff --git a/exampleSite/content/events/2016-kiel/conduct.md b/exampleSite/content/events/2016-kiel/conduct.md
new file mode 100644
index 000000000..0ec9e1658
--- /dev/null
+++ b/exampleSite/content/events/2016-kiel/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Kiel"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+**ANTI-HARASSMENT POLICY**
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+**CODE OF CONDUCT**
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-kiel/contact.md b/exampleSite/content/events/2016-kiel/contact.md
new file mode 100644
index 000000000..7ab5dcded
--- /dev/null
+++ b/exampleSite/content/events/2016-kiel/contact.md
@@ -0,0 +1,47 @@
++++
+City = "Kiel"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+- Doris Weßels
+
+Dr. Doris Weßels is professor of business information systems at the University of Applied Sciences in Kiel. She studied mathematics and computer sciences, business and economics. Her main research and teaching areas are within network-oriented and inter-organizational project and knowledge management, entrepreneurship management and future work. Furthermore, she is founder and leader of the IPMA-GPM regional group in Schleswig-Holstein and board member of the cluster management "Digital Economy Schleswig-Holstein".
+
+- Jerome Güls
+
+Jerome is a communicative 30-year-old Account Manager, living and working in Hamburg. Not only to understand the needs and challenges of his customers and to meet their demands, he is interested in IT topics. He enjoys talking to CTOs, project managers and other seniors to always find the best solution to integrate young people in IT projects and departments.
+
+- Maik Wojcieszak
+
+Maik Wojcieszak is co-founder of wobe-systems GmbH. As an author of various articles he shares his experience in network protocol design, system automation and parallel processing. Under the umbrella of the cluster "Digital Economy Schleswig-Holstein" he is founder and leader of the open business workgroup.
+
+- Oliver Dissars
+
+Oliver Dissars is co-founder of wobe-systems GmbH. His experience as a consultant helps international customers to improve their business. Targeting the relation of system automation and business development in industrial production, he is a valuable counterpart while developing new ideas.
+
+- Sabine Bernecker-Bendixen
+
+Sabine Bernecker-Bendixen works as a consultant and trainer for companies in the tech industry on topics of team communication, soft skills, culture and leadership. She is an experienced speaker at international conferences and author of many articles and blog posts on these issues.
+
+- Wilhelm Hasselbring
+
+Prof. Dr. Wilhelm (Willi) Hasselbring is professor of Software Engineering at Kiel University. In the competence cluster Software Systems Engineering (KoSSE), he coordinates technology transfer projects with (local) industry. In the excellence cluster Future Ocean, a large-scale collaborative project of Kiel University and GEOMAR, he is principal investigator and coordinator of the research area Ocean Observations.
+
+- Wolfgang Bär
+
+Wolfgang Bär is co-founder of wobe-systems GmbH. He is the main link between worldwide customers and product development. By coordinating feature request and juggling requirements he designs automation solutions together with customers to make their visions a reality.
+
+
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-kiel/location.md b/exampleSite/content/events/2016-kiel/location.md
new file mode 100644
index 000000000..c0c558fdc
--- /dev/null
+++ b/exampleSite/content/events/2016-kiel/location.md
@@ -0,0 +1,60 @@
++++
+City = "Kiel"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+
+Conference Location |
+Hotel Booking
+
+
+
+
+
+For attendees of DevOpsDays, Kiel-Marketing has arranged discount rates with some hotels. To book the hotels download the PDF, fill out the document and send it to the address of Kiel-Marketing at the top of the document via email or fax.
+
+DOWNLOAD BOOKING DOCUMENT
+
+For more information about the hotels, follow the links below.
+
+[Ringhotel Birke](https://www.hotel-birke.de/en/)
+
+[Best Western Hotel Kiel](https://www.bestwestern.de/hotels/Kiel/BEST-WESTERN-Hotel-Kiel)
+
+[Maritim Hotel Bellevue](https://www.maritim.de/de/hotels/deutschland/hotel-bellevue-kiel/uebersicht)
+
+[Hotel Consul](https://www.hotel-consul-kiel.de/en/hotel)
+
+[Hotel Wiking](http://hotel-wiking.com/en/)
+
+### Speaker Hotels
+
+
From 0 to DevOps - Coping with Continuous Delivery to the Cloud by Oliver Siebenmarck
+
+
"Hey, we're doing this really cool new platform and it will be run in the cloud. The team is international and everything will be DevOps. Interested?"
+"Sure!"
+
+
And so, a tale of woe begins. Not because DevOps is hard, but because it has to be learned to be done right. By the young talents as well as the old guard. Mistakes were made, misunderstandings were common, shouting matches only avoided by the low quality of some telephone lines.
+So, how come that in the end it all worked out? That people like each other, that everyone kept their sanity and that the portal went live in time and with good quality.
+
+
This talk will give a detailed report on the lessons learned by a diverse project team that tried to do everything right while keeping deadlines. Insights include managing a geographically diverse team, when to use automation and how to make sure that tech and people play nice.
+
Speaker
+
Oliver happily works as a consultant for IBM, with a focus on all topics cloud and innovation in IT. He has a keen interest in application lifecycle management and the question of how people can best work together on a project. Oliver lives and codes in Kiel, Germany.
+
+
+
+
+
ITIL and DevOps can be friends by Jan-Joost Bouwman
+
+
ING is a worldwide financial institution, based in the Netherlands. The IT department of the Netherlands manages a mix of off the shelf applications and in house built software. Traditionally development was governed by CMMi and IT Servicemanagement by ITIL processes. Three years ago the developers started working in Agile/Scrum teams, dropping CMMi. The next step was to involve Operations as well and transform to an DevOps organisation, striving for Continuous Delivery.
+
+In a lot of Agile organisations ITIL is considered the evil soul sucking epiphany of bureaucracy. But is it really? If we look at the tasks you perform in the ITIL processes Incident management, Problem management and Change management, you will find that a lot of those you still need to perform in an Agile/Scrum way of work. And that there actually is a lot of value in making some rules on how we want to interact in these processes between teams. But we may call the task differently than we were used to in ITIL. And we may choose to use different tools to handle parts of the process. We call this adaptation of ITIL Agile ITSM.
+
+This talk focuses on the adaptations we have made to our ITSM processes to accommodate the requirements of an Agile/Scrum way of work. Proving that there is still value in a lot of the things we used to do in ITIL And that there is no real conflict between Agile and ITIL.
+
+Speaker
+
+Jan-Joost stumbled into IT almost 20 years ago, starting on a temp job for 5 days that lasted 7 years. During those years he has been mostly on the functional/process side of things, having worked as tester, designer, information analyst, project manager, application manager, change manager and currently as process owner the ITIL change management process at ING.
+
+He is also the self appointed DevOps evangelist and community leader there, trying to help his co-workers to make the transition to DevOps and Continuous Delivery and have fun with it at the same time!
+
+In his spare time he enjoys travelling the world to watch birds, or cooking, but rarely at the same time.
+
+
+
+
+
Continuous Testing for DevOps: Evolving Beyond Automation by Wayne Ariola
+
+Attend this session to learn why and how Continuous Testing's real-time objective assessment of an application's business risks is a critical component of DevOps:
+
+Throughout the process, business stakeholders have instant access to feedback on whether their expectations are being met, enabling them to make informed decisions.
+
+At the time of the critical "go/no go" decision, there is an instant, objective assessment of whether your organization's specific expectations are satisfied--reducing the business risk of a fully-automated Continuous Delivery process.
+
+Defects are eliminated at the point when they are easiest, fastest, and least costly to fix--a prime principle of being "lean."
+
+Continuous measurement vs. key metrics means continuous feedback, which can be shared and used to refine the process.
+
+Speaker
+
+Wayne Ariola, Chief Strategy Officer, leads the development and execution of Parasoft's long-term strategy. Ariola is a frequent contributor to publications as well as a sought-after speaker at key industry events. Ariola brings more than 20 years strategic consulting experience within the technology and software development industries.
+
+
+
+
+
Learning to fall by Rafael Ördög
+
+When people talk about advantages of microservices, easy scaling and resilience comes up frequently. What they don't usually tell you, is that robustness does not come for free. If you don't put extra effort into gracefully failing when one of your dependencies is down, microservices will only make your system even more brittle.
+
+In my presentation I will recount our journey from an instabile monolith to a robust set of microservices with a special focus on architectural patterns that helped us along the way.
+
+Speaker
+
+Rafael is a Lead Developer at Budapest-based Emarsys and popular speaker in the Hungarian software community. As a founding member of Emarsys CraftLab - the dedicated coaching team of Emarsys - he has taught university courses and lectured at numerous conferences. His passion for short feedback loops drove him to create Lean Poker, a workshop where developers have the opportunity to experiment with continuous delivery in an artificial environment.
+
+
+
+
+
War Games - flight training for DevOps by Jorge Salamero Sanz
+
+Here @ Server Density we monitor 100.000+ servers processing 2B metrics a day. Downtime is critical for us, that's why we keep training to react to incidents. We organize our internal War Games were all engineers practice the processes involved in incident handling. We have seen how this improves the associated human factors, our processes and our tools.
+
+Speaker
+
+Jorge co-founded Zentyal, a successful open source Exchange protocol interoperability company. He now drives Server Density evangelism, showing potential customers and community members best practices adopting DevOps practices and monitoring their infrastructure. When he's not writing monitoring plugins he's enjoying walks with his 2 dogs across the countryside.
+
+
+
+
+
Keep it simple, stupid! (A reminder to myself and a surprisingly accurate analogy to how (not) to build sustainable systems) by Moritz Rogalli
+
+The journey of how the idea of a simple personal blog turned into an unmanageable and expensive system, its similarities to unsustainable systems on a bigger scale and the importance of going back to square one.
+
+Speaker
+
+Moritz works as consultant at Init AB currently mainly working on building easily accessible (and simple) infrastructure systems and an interest in how to build strong and diverse teams and including environments.
+
+
+
+
+
The Challenges of Adopting DevOps by Bianca Heinemann
+
+A lot of companies underestimate the amount of change that adopting DevOps brings to the organization. What are the challenges for a company going DevOps? What should be expected in the realms of tools, methods and even culture? This presentation will try to shed some light on what is going to happen after someone says, "Let's do this DevOps thing.
+
+Speaker
+
+Bianca started her career and still works at IBM as a consultant and business analyst after finishing her master's degree in business computing. She helps various companies setting up and managing their software lifecycle projects. Her focus is on the interplay of humans, the tools they use and the methods they use to organize themselves.
+
+
+
+
+
Docker Container Lifecycles - Problem or Opportunity? by Baruch Sadogursky
+
+Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production?
+We will demonstrate how to implement a promotion model for docker images, and then show how to distribute them to any kind of consumer, being it a customer or a data center.
+
+Speaker
+
+Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate of JFrog, the home of Artifactory - the Universal Artifact Repository, and Bintray - the Universal Distribution Hub.
+
+For a living he hangs out with the JFrog tech leaders, writes some code around Artifactory and Bintray, and then speaks and blogs about all that. He does it repeatedly for the last dozen of years and enjoys every moment of it.
+
+
+
+
+
Rethinking Performance Engineering in the DevOps World by Felix Willnecker/André van Hoorn
+
+Researchers and practitioners know quite well how to handle performance in classical environments involving a strict separation between Dev and Ops. DevOps aims to merge these silos. So far, the community has failed to systematically integrate performance management practices into the DevOps world, even though modern software development paradigms provide great opportunities to do that. Only holistic performance management, integrating Dev and Ops throughout the whole life-cycle, leads to high-quality software.
+
+We have developed a blueprint for performance-aware DevOps processes and infrastructures, serving as a template for holistic performance management. The design rationale for this blueprint has been accompanied by an industry survey ascertaining current practices and tools. The blueprint is a result of a joint work by multiple institutions. This talk will outline the blueprint and give the opportunity to exchange views among DevOps-enthusiastic researchers and practitioners.
+
+Speaker
+
+Felix Willnecker studied computer science at the Technical University Munich. After several years of professional work experience as CTO of Weptun GmbH he started researching at fortiss. His research areas include application system performance and enterprise architecture management.
+
+Andre van Hoorn is the interim professor for Reliable Software Systems at the University of Stuttgart. His research interests include combining model-based and measurement-based performance evaluation.
+
+
+
+
+
Working in and with Open Source Communities by Bernd Erk
+
+Starting an open source project is very easy, especially in the days of GitHub. Push your code and see if somebody is interested in. If you are able to gain attention and interest for you project you feel motivated and work all night long. But on the other hand, people will start complaining about open bugs, missing features and your evil or non existing website. Believe it or not, but this will pursue you until your last user dies.
+
+One of the most important things for a successful open source project is to treat you community well. This talk will share some experiences made during the last 6 years with Icinga. Starting with basic concepts, it deals with tools and methods helping to increase and cultivate your community. It also covers internal organisation requirements for successful community work and upcoming challenges if you strike some new paths with your project.
+
+Speaker
+
+Bernd Erk is co-founder and community manager of the Icinga Project.
+
+In his day job he is CEO at NETWAYS, a German open source service company. As contributor to Linux Magazine and Admin Magazine, Bernd regularly publishes articles and presents on open source topics ranging from monitoring, configuration management to various open source datacenter solutions. He tries to spread the DevOps spirit wherever and whenever possible.
+
+
+
+
+
Scalable and clean build environments with Jenkins and Docker by Stefan Kahlhöfer
+
+By combining Jenkins CI server and Docker application containers you can provide dynamically created build environments that are free of old build fragments. There is not only one way to realize such scenario and we will show you three of them we have tried.
+
+Speaker
+
+Stefan supports teams in a variety of activities, with a strong understanding of both operational and development aspects. These activities range from setting and maintaining customer development environments and tools to acting as Agile Coach.
+
+
+
+
+
The (Un)Surprising Truth About DevOps Culture by Manuel Pais
+
<irony>Yes, this talk will tell you about all the right practices you need to adopt to become a successful DevOps organization!</>
+
+
<bummer>DevOps is highly contextual, there is no set of prescribed practices an enterprise can pick up and "become DevOps".</>
+
+
However, healthy organizations exhibit similar organizational and behavioral patterns that help them continuously learn and become better places to work while outperforming competitors.
+
+
In this talk we explore some of those patterns, why they might help in certain contexts while they might hurt in others.
+
+
We will also look at some surprising results from community-driven research on which practices contribute the most towards an environment of collaboration, sharing and ownership (of both successes and failures). In other words, what moves the needle towards DevOps? Is it infrastructure-as-code? Devs on-call? Blameless post-mortems?
+
+
Attend this ignite talk and get ready to be surprised!
+Speaker
+
+Manuel Pais is a DevOps advocate, with a mixed background as developer, build manager and QA lead. Jack of all trades, master of continuous improvement, Manuel enjoys helping organizations adopt test automation, continuous delivery and cloud, from both technical and human perspectives. He has worked on a range of technologies (Java, .Net, web, mobile) and industries (banking, telecom, defense and aviation).
+
+
+
+
+
Collect all the things with Beats
+
The ELK stack is widely used to collect logs with Logstash, analyze and search the data with Elasticsearch, and visualize what is happening in your system. Now there is a new platform for shipping many types of operational data: Beats. It can be used to collect, parse, and ship any type of data.
+
+This talk provides an overview of the Beats platform and dives into gathering system metrics, tapping your wire data, and using real-time file analytics. Finally, we take a look at building custom data shippers to get a complete overview of your infrastructure.
+Speaker
+
+Philipp is a Developer Advocate at Elastic, spreading the love and knowledge of full-text search, analytics, and real-time data. He is a frequent speaker at conferences and meetups about all things Elasticsearch, databases, cloud computing, and devops. Philipp lives in Vienna where he enjoys experimenting with software, organizing meetups, and sports.
+
+
+
+
+
DevOps and sharing
+
Tools aren't everything in DevOps, DevOps is also - if not mostly - about people. That's a truism... or is it? Even the best tools won't help you when you've got years of valuable knowledge stuck in the heads of long-term employees. Once you start digging, you'll be surprised how much of that knowledge is creating unnecessary bottlenecks. Some of your team mates even end up re-inventing the wheel. Don't be surprised if a lot of your time spent on restructuring an organization focuses on running from desk to desk and taking notes!
+
+In this talk we will look into the whys and hows of using so-called people skills. Why are they so important to maintain a healthy company culture? How can we facilitate sharing?
+
+Speaker
+
+Marta is an activist/project manager turned programming enthusiast. Currently she holds the position of DevOps Heroine at Acrolinx, where she makes sure developers work seamlessly, but mostly she works on redisigning the company's build infrastructure. Sche actively supports initiatives that make the tech community more inclusive, An occasional Rails Girls coach, she's a fan of Chef, alleycats and pizza.
+
+
+
+
+
Praise the "overwrite" - Why boring approaches are awesome!
+
A small practical story about building better systems with simple approaches.
+
+Speaker
+
+Florian Sellmayr is a consultant with ThoughtWorks in Hamburg, working in Software Development and Platform Engineering. He focuses on continuous delivery of large scale, critical software projects. He contributes to Open Source projects and is the maintainer of LambdaCD, a toolbox to create build pipelines in Clojure code.
+
diff --git a/exampleSite/content/events/2016-kiel/sponsor.md b/exampleSite/content/events/2016-kiel/sponsor.md
new file mode 100644
index 000000000..4a748d895
--- /dev/null
+++ b/exampleSite/content/events/2016-kiel/sponsor.md
@@ -0,0 +1,89 @@
++++
+City = "Kiel"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+**Sponsorship opportunities**
+
+DevOpsDays is a self-organizing non-profit conference for practitioners which depends on sponsorship to make the conference affordable to everyone. We do not have vendor booths, sell product presentations or distribute attendee contact lists. Depending on the sponsor packages you chose, there are different opportunities like booth tables, elevator pitches, logo on website and more. We encourage our sponsors to represent themselves by actively taking part and engaging with the attendees as peers. As a sponsor you are free to do anything like a lottery or what ever. Any attendee – and also the sponsors have the possibility to demo products/projects as a part of an open space. All sponsors are recommended to accept the code of conduct.
+
+In the name of all attendees and organizers we thank all sponsors for their support!
+
+If we have money left after the conference, it will be given to a social project for educating children in topics of computer sciences.
+
+
+
+
+
+
+###Gold Sponsor
+All Gold Sponsors get a full table to present their products and information. The logo will be presented on the website and all emails. They will also be mentioned in social media. Gold sponsors get a one minute pitch at the conference and will be named as gold sponsor. They are free to use the giveaway bags. 4 tickets are included.
+
+###Silver Sponsor
+All Silver Sponsors may present their information at a shared table (half table). The logo will be presented on the website and all emails. They will also be mentioned in social media. Silver Sponsors will be named as silver sponsor. They are free to use the giveaway bags. 2 tickets are included.
+
+###Evening Sponsor
+The Evening Sponsor gets a full table to present their products and information. The logo will be presented on the website and all emails. The Evening Sponsor will also be mentioned in social media and get a one minute pitch at the conference. The Evening Sponsor will be named as it during the whole and at the evening of the social event. They are free to use the giveaway bags. 6 tickets are included.
+
+###Speaker´s Dinner Sponsor
+The Speaker´s Dinner Sponsor gets a full table to present their products and information. The logo will be presented on the website and all emails. The Speaker´s Diner Sponsor will also be mentioned in social media and get a one minute pitch at the conference. The Speaker´s Diner Sponsor will be named as it during the whole and at the evening of the Speaker´s Diner. They are free to use the giveaway bags. 4 tickets are included.
+
+###Coffee Break Sponsor
+The Coffee Break Sponsor may present their information at a shared table (quarter). Their name will be listed on the website. The Coffee Break Sponsor will also be mentioned in social media. The Coffee Break Sponsor will be named as it during the day of sponsoring the coffee break and may put the logo on the buffet. They are free to use the giveaway bags. 1 ticket included.
+
+###T-Shirt Sponsor
+The T-Shirt Sponsor gets a shared table to present products and information (half). The logo will be presented on the website and all emails, and also on one arm of the conference T-Shirts. They will also be mentioned in social media. T-Shirt Sponsors get a one minute pitch at the conference and will be named as T-Shirt Sponsor. They are free to use the giveaway bags. 2 tickets are included.
+
+###Contributor
+Contributors get a shared table to present their information (1/8). They are named in the sponsors´ list on the website. They are free to use the giveaway bags.
+
+
+If you have any questions or want to become a sponsor of DevOpsDays Kiel 2016, please [drop us an email](mailto:<%= render(:partial => "/#{@eventhome}/_email_organizers") %>?subject=Sponsor devopsdays <%= @eventid %>).
diff --git a/exampleSite/content/events/2016-kiel/welcome.md b/exampleSite/content/events/2016-kiel/welcome.md
new file mode 100644
index 000000000..47f231c57
--- /dev/null
+++ b/exampleSite/content/events/2016-kiel/welcome.md
@@ -0,0 +1,46 @@
++++
+City = "Kiel"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-kiel"]
+
+
++++
+
+
+
DevOpsDays is coming to Kiel!
+
+## Thursday, May 12, 2016 - Friday, May 13, 2016
+
+
+
+
+
+
+The 1st DevOpsDays Kiel are over now. With the help of our wonderful speakers, all our sponsors and nice attendees we have had two awsome days full of DevOps topics!
+Thank you all!
+For helping you to keep the memory alive or for those, who weren't able to join DevOpsDays Kiel 2016 please follow the link photos or videos.
+
+Photos
+Videos
+
+{{< event_link page="location" text="Location" >}}
+{{< event_link page="contact" text="Email the Organizers" >}}
+
+To get updates about DevOpsDays Kiel 2017 follow us on Twitter.
+
+
+
+
+{{< event_twitter DevOpsDaysKiel >}}
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/conduct.md b/exampleSite/content/events/2016-london/conduct.md
new file mode 100644
index 000000000..b73a9cd29
--- /dev/null
+++ b/exampleSite/content/events/2016-london/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "London"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+**ANTI-HARASSMENT POLICY**
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+**CODE OF CONDUCT**
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-london/contact.md b/exampleSite/content/events/2016-london/contact.md
new file mode 100644
index 000000000..bf1ce5936
--- /dev/null
+++ b/exampleSite/content/events/2016-london/contact.md
@@ -0,0 +1,19 @@
++++
+City = "London"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-london/hackathon.md b/exampleSite/content/events/2016-london/hackathon.md
new file mode 100644
index 000000000..cc8890a84
--- /dev/null
+++ b/exampleSite/content/events/2016-london/hackathon.md
@@ -0,0 +1,96 @@
++++
+City = "London"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "hackathon"
+type = "event"
+
++++
+
+## DevOpsDays Hackathon
+### Summary
+As part of DevOpsDays London, supported by Microsoft and Chef.io, we have organised a Hackathon with a difference on the 21st of April, also at the Grange hotel (St. Paul’s). This will take place from 8am – 8pm with all food and beverages supplied.
+
+### Purpose of the Hackathon
+This isn’t a traditional Hackathon, we are looking to test the principles of DevOps against the clock and at the same time attempt to build a production quality Minimum Viable Product (MVP) that could facilitate the giving of small (micro) donations to a variety of charities so easy it becomes a way of life. The concept is to create a facility for retailers to offer their customers the option to round individual transaction to the nearest $, £, €,¥ etc., to see their donations update a fund real-time and to influence who benefits from it.
+We are looking for colleagues that:
+
+• Are committed to participating the whole day
+
+• Have technical skills which could help realise the vision – e.g. UX/CX, web and database development
+
+• Are familiar with DevOps concepts and have experience with automation tools
+
+If you are interested in participating in this unique event, and can take the day out to do so, please register via http://www.devopsdays.org/events/2016-london/registration/
+Live the Deming mantra ….this is your opportunity to make a difference and have fun!
+### Vision
+To produce a solution that will allow consumers to make micro donations at the point of sale so easy that it becomes a way of life.
+CONSUMERS donating will be able to decide / influence what their donations are being used for.
+RETAILERS offering the service will be able to see and use summary data relating to the fundraising they have facilitated.
+CHARITIES and people in need must receive these donations in an easy way, free of charge or at a minimum cost
+### Principles
+
+1) Atomic Micro donation transaction
+Description - From the customer view point the micro donation must feel like it's part of the transaction being carried out and completed as part of that.
+
+Implications - This rules out solutions which require collection of donations from the customer after the point of sale - this would also be difficult in terms of many thousands of invoices to issue and collect
+
+2) Retailer engagement
+
+Description - It's key for the retailer to contribute all be it with simple solution integration and minimum effort on their part. Retailers want to be good citizens too.
+
+Implications - So it requires some salesmanship but if we can get some buy in from enterprises closer to home its compelling for other retailers. In addition secure means of communications must be established between the retailers and charity organisation collecting the funds.
+
+3) Browser agnostic
+
+Description – Any solution must not be locked into specific browser technologies
+
+Implications – Helps to keep the technical implementation consistent but also rules out some options which might be easier for some technologies to implement such as Chrome plugins
+
+4) Not for profit
+
+Description – No profit is to be made out of the solutions delivered, the purpose is to help people in need not to make money.
+Implications – Minimal governance and support baked in from the outset
+
+### Some ideas regarding how to collect the micro donations
+Below are some suggestions to get the grey matter going….
+
+1) Retailer checkout "widget"
+
+Retailer embeds a simple JavaScript snippet that loads in a donation checkbox . This widget takes a "price" parameter so we can determine the rounded up amount. Checking the box and submitting the "checkout" page calls a web service on our end that informs us of the round-up which gets persisted by the charity collecting and distributing funds. The basket total is updated and the retailer collects the donation on our behalf. We then bill the retailer on a month basis for the sum of donations.
+
+2) Scheme holder integration
+Provide a solution at a different point in the process, i.e. As part of the Visa/Mastercard/Paypal transaction rather than the retailer transaction, although with their support.
+
+### Logistics
+
+#### What’s provided
+
+• The room at the Grange
+
+• Wifi – The best we could get
+
+• Plenty of food and drink
+
+• A DevOps platform hosted on Azure utilising GIT, Jenkins, SonarQube, Nexus, Chef, Selenium, Cucumber, Gerrit
+
+#### What you need to bring
+
+• A laptop/device to work on
+
+• Your imagination, desire, skills and knowledge
+### Collaborate
+Whilst not compulsory we expect some degree of collaboration although our guidance is to form teams no bigger than 8 people.
+### Objectives
+
+• To get coding ASAP!
+
+• To produce working software following DevOps good practice
+
+• To enjoy yourself
+
+• To make a difference
+
+### Questions
+Surely not…..ok send them into Barry.chandler@barclays.com
+
diff --git a/exampleSite/content/events/2016-london/location.md b/exampleSite/content/events/2016-london/location.md
new file mode 100644
index 000000000..abba15574
--- /dev/null
+++ b/exampleSite/content/events/2016-london/location.md
@@ -0,0 +1,50 @@
++++
+City = "London"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+## Conference location
+
+
diff --git a/exampleSite/content/events/2016-london/program/casey-west.md b/exampleSite/content/events/2016-london/program/casey-west.md
new file mode 100644
index 000000000..6c72b376c
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/casey-west.md
@@ -0,0 +1,38 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Casey West"
+type = "talk"
+
++++
+
+## Minimum Viable Platform: The 6 Characteristics of Operationally Mature Production Environments
+
+Operational maturity for a distributed-systems production environment requires a
+clear understanding of the 6 high-level characteristics common to
+operationally mature production environments:
+
+
Routing
+ and load balancing
+
Backing
+ services broker
+
Infrastructure
+ orchestration
+
Health
+ management, monitoring and recovery
+
Immutable
+ artefact repository
+
Log
+ aggregation
+
+
+In this interactive talk, we will explore the critical capabilities necessary to create a mature production platform with these charac
+teristics. We will present these capabilities in the form of a useful rubric for you to create your own Minimum Viable Platform effect
+ively.
+
+What's more, you will gain insights on what life is like in the day-of-the-life of teams who have the operational maturity of a Minimu
+m Viable Platform.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/claire-agutter.md b/exampleSite/content/events/2016-london/program/claire-agutter.md
new file mode 100644
index 000000000..a3729ee77
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/claire-agutter.md
@@ -0,0 +1,17 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Claire Agutter"
+type = "talk"
+
++++
+
+## Agile your ITIL - Bringing DevOps Benefits to IT Service Management
+
+Many large financial enterprises have spent years implementing frameworks, standards and methodologies to try and get IT 'right'. One of the most commonly adopted of these is ITIL, enabling organisations to put in place fundamental processes such as incident management and change management.
+The result of implementing of ITIL may lead to IT staff feeling overloaded and resist DevOps initiatives because they've only just 'finished' ITIL. What's more, the problem is that ITIL is typically restricted to operations while agile thinking remains exclusively limited within IT development.
+In this talk, we will focus on bringing elements of agile thinking to IT service management to provide the benefits of DevOps without overwhelming an organisation and its staff. In particular, we will be looking at ways to unite dev and ops, apply agile thinking to ITSM processes and redefine what we mean by 'service' and 'product'. The result will be a better understanding of how to adopt DevOps in large organisation by evolution, not revolution.
+
+
diff --git a/exampleSite/content/events/2016-london/program/gareth-rushgrove.md b/exampleSite/content/events/2016-london/program/gareth-rushgrove.md
new file mode 100644
index 000000000..b8c49e931
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/gareth-rushgrove.md
@@ -0,0 +1,24 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Gareth Rushgrove"
+type = "talk"
+
++++
+
+## Rate of Change, (Un)opinionated Platforms and Devops Coevolution
+
+There has been a recent explosion in new technologies for running software systems.
+
+Many architectures are now based on ever smaller (micro) services.
+
+The devops movement has crossed the chasm and become mainstream with operators and developers working more closely together than ever before.
+
+These three threads are the result of coevolution - where a change in one practice has a direct effect on others.
+
+Join us to gain insights on how the adoption of practices such as devops and microservices, and tools such as platform as a service, are interconnected. You'll also develop a better understanding of how devops emerged in widely different organisations. Last, but by no means least, we'll explore the power of coevolution which makes cause and effect bi-directional, making it possible to leverage what you do and how you do it to improve your organisation as a whole.
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/gene-kim.md b/exampleSite/content/events/2016-london/program/gene-kim.md
new file mode 100644
index 000000000..c1cf3dc74
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/gene-kim.md
@@ -0,0 +1,20 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Gene Kim"
+type = "talk"
+
++++
+
+## My Top Five Lessons Learned: DevOps In Large, Complex Organizations
+
+For me, nothing inspires more awe and more learning than studying how large, complex organizations that have been around for decades, or even centuries, are mobilizing around DevOps and getting the same amazing outcomes that we typically see in organizations like Amazon, Google, Netflix and Etsy. They are elevating the state of the engineering practice in organizations that often have thousands of development, test and operations engineers, improving organizational outcomes and making work more humane and fun.
+
+I can’t wait to share with the DevOpsDays community what I’ve learned, share the problem roadmap that’s been verbalized, and some of the things we’ve been working on to help people overcome those problems!
+
+See you there!
+
+[Slides](https://github.com/kramos/devopsdays-webby/blob/master/site/content/events/2016-london/program/slides/GeneKim-20160435mDevOpsDaysLondon-TopFiveLearnings.pptx)
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/jeromy-carriere.md b/exampleSite/content/events/2016-london/program/jeromy-carriere.md
new file mode 100644
index 000000000..a368bfed6
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/jeromy-carriere.md
@@ -0,0 +1,15 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Jeromy Carriere"
+type = "talk"
+
++++
+
+## Enterprise Ops Rising
+
+As enterprise organisations move to the cloud they are faced with numerous operational and security challenges. First, they need to manage and monitor large numbers of systems and microservices. Second, they need to ensure proper application functioning and compliance with relevant standards. Last, but by no means least, they need to do all of that in a hybrid model - bridging across infrastructure platforms and legacy applications.
+In this session, we will look at the changing requirements, opportunities, and challenges for the DevOps community as enterprises move to the cloud. In particular, we will examine the intersection of ops and governance and how we see practices evolving there as well as where gaps remain. We will conclude with insights from Google's own experience deploying applications on its cloud platform.
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/joanne-molesky.md b/exampleSite/content/events/2016-london/program/joanne-molesky.md
new file mode 100644
index 000000000..c219ddd36
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/joanne-molesky.md
@@ -0,0 +1,16 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Joanne Molesky"
+type = "talk"
+
++++
+
+## We are Great at DevOps but the Enterprise is Failing
+
+DevOps and Continuous Delivery (CD) allow us to deliver IT services and products faster and more reliable than product owners ever dreamed of. However, many enterprise management processes and practices are barricades that require dismantling to gain maximum benefit from this capability. In this session, we will talk about legacy management practices in Finance, IT Governance and Procurement and how they inhibit our ability to extend the benefits and create more value to our customers when we embrace DevOps and CD. We will provide examples from large enterprises that demonstrate how we can use Lean Thinking and Principles to break down these management barricades and deliver even more value to our customers.
+
+[Slides](https://github.com/kramos/devopsdays-webby/blob/master/site/content/events/2016-london/program/slides/DevOpsDaysLondon2016JMolesky.pdf)
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/john-clapham.md b/exampleSite/content/events/2016-london/program/john-clapham.md
new file mode 100644
index 000000000..545f51351
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/john-clapham.md
@@ -0,0 +1,15 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "John Clapham"
+type = "talk"
+
++++
+
+## Four things I learnt about DevOps when my car was engulfed by flames
+
+This is the story of the things I learnt when my car caught fire while driving through a less-than-salubrious area of Bristol one sunny afternoon. The whole experience lasted just half an hour and yet it was rich in learning, with uncanny parallels to the challenges we face encouraging DevOps in organisations.
+
+
diff --git a/exampleSite/content/events/2016-london/program/justin-cormack.md b/exampleSite/content/events/2016-london/program/justin-cormack.md
new file mode 100644
index 000000000..42a52fd38
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/justin-cormack.md
@@ -0,0 +1,22 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Justin Cormack"
+type = "talk"
+
++++
+
+## Let's talk about Security
+
+Having a conversation about security between developers, security professionals and ops requires a common language, and tools that respect that language.
+
+In this talk I discuss a conversational approach to defense, in depth approaches to application security, going from a high level language about what a program is intended to do, and applying this to tools that restrict behaviours.
+
+Appropriate language depends on the problem domain, so I will look at concrete examples. The first case is the OpenBSD pledge system, introduced last year. This has been the most successful rollout of a capability reduction system, with it applied to the majority of the programs in the base system within a few months. It is however successful because it targets the language of a particular problem domain, and is not necessarily directly applicable elsewhere.
+
+As a second example I will look at the ongoing work we are doing at Docker to apply the pledge model to make a language for describing containerised applications, looking at the differences in the domain languages for a different type of application.
+
+[Slides](https://github.com/kramos/devopsdays-webby/blob/master/site/content/events/2016-london/program/slides/DevOpsDaysLondon_LetstalkaboutSecurity.pdf)
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/kris-saxton.md b/exampleSite/content/events/2016-london/program/kris-saxton.md
new file mode 100644
index 000000000..bb2cb1f50
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/kris-saxton.md
@@ -0,0 +1,19 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Kris Saxton"
+type = "talk"
+
++++
+
+## Bimodal IT and Other Snakeoil
+
+Bimodal IT is being presented by some analysts and vendors as the strategic response to the supposedly intractable task of reforming legacy estates while continuing to innovate.
+
+In this talk, we will argue that this approach is a flawed oversimplification which, when adopted, results in lost opportunities, delays crucial decisions on how we evolve our legacy systems, and ultimately cripples the very ability to innovate we seek to protect.
+
+Based on the experience of 5 projects (4 within large retail or investment banks and 1 with a large reinsurer) over the past two years, we will attempt to show that agile and devops teams within large financial organisations cannot hope to succeed without dealing with legacy environments, but also provide reassurance that these teams already have everything they need to both innovate and evolve their legacy environments.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/oliver-wood.md b/exampleSite/content/events/2016-london/program/oliver-wood.md
new file mode 100644
index 000000000..5fa52cf1f
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/oliver-wood.md
@@ -0,0 +1,16 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Oliver Wood"
+type = "talk"
+
++++
+
+## You don't scale
+
+Back in 2008 I worked myself into hospital, collapsing a disc in my spine and ending up taking 3 months off work and having some surgery. I'd like to highlight how we all focus on scaling servers, but need to look after ourselves.
+
+
+[Slides](https://github.com/kramos/devopsdays-webby/blob/master/site/content/events/2016-london/program/slides/devops_days_2016_wood_oliver.pdf)
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/philippe-guenet.md b/exampleSite/content/events/2016-london/program/philippe-guenet.md
new file mode 100644
index 000000000..485ac7872
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/philippe-guenet.md
@@ -0,0 +1,17 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Philippe Guenet"
+type = "talk"
+
++++
+
+## From Lean in Automative to Lean IT
+
+There is much we can learn from Lean in the automative industry, dating back to Henry Ford and Toyota and looking forward to the now more modern iterations and implementation of Lean.
+
+In this talk, we will revisit fundamental Lean concepts and principles applicable to IT and explore how they can be applied to improve our organisations. The topics we will cover include Total Quality Management, organisation optimisation, simplification and improved time-to-market.
+
+[Slides](https://github.com/kramos/devopsdays-webby/blob/master/site/content/events/2016-london/program/slides/philippe.pdf)
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/simon-vans-colina.md b/exampleSite/content/events/2016-london/program/simon-vans-colina.md
new file mode 100644
index 000000000..6907343aa
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/simon-vans-colina.md
@@ -0,0 +1,15 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Simon Vans-Colina"
+type = "talk"
+
++++
+
+## The Mondo DevOps Experience
+
+What are some of the things you have to differently, when you're doing DevOps at a Startup Bank.
+
+[Slides](https://github.com/kramos/devopsdays-webby/blob/master/site/content/events/2016-london/program/slides/SimonVans-Colinadevopsdaysgpg.key)
+
+
+
diff --git a/exampleSite/content/events/2016-london/program/thiago-almeida.md b/exampleSite/content/events/2016-london/program/thiago-almeida.md
new file mode 100644
index 000000000..7a5c19dfb
--- /dev/null
+++ b/exampleSite/content/events/2016-london/program/thiago-almeida.md
@@ -0,0 +1,18 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Thiago Almeida"
+type = "talk"
+
++++
+
+## Inside Microsoft Engineering: DevOps Lessons Learned
+
+Many Microsoft teams are embracing organisational changes and culture shifts necessary for adopting DevOps including teams responsible for delivering Bing, PowerBI, Azure, Visual Studio, MSN and Microsoft Developer Network.
+
+In this session, we will share with you a multitude of DevOps transformation stories among the teams and provide details of their transformations, ranging from shifts in roles and accountabilities to mindset changes and metrics. We will also provide recommendations based on lessons learned and what we would do differently if we could do it again.
+
+
+
+
+
DevOpsDays is a series of global conferences where people get the opportunity to listen to presentations from key individuals leading the way in what is fast becoming an IT revolution, share stories on how DevOps is having an impact on their lives and the organisations they work for, meet like-minded people making it happen, network and see how technology is enabling these changes.
+
+
We anticipate the upcoming London event will have 300+ delegates attending along with approximately 100 executives and representatives from sponsors spanning various financial institutions, consultancies and technology providers.
+
+
In addition to this we are liaising with a number of companies in order for them to represent DevOpsDays London as our media sponsor/s. This will provide another opportunity for exposure for everyone involved.
+
+
The rise of DevOps, enabling the lean Enterprise
+
+
The emphasis of DevOpsDays London 2016 is on DevOps in the Enterprise with specific reference to the Financial Services Industry. With that said, the event is open to any delegate, and we especially encourage participation by Enterprises for whom DevOps may not yet seem a natural fit, intuitive or adding value.
+
+
To begin with we will look at the origins of DevOps, its various reference points, scope of application and why these new ways of working are changing, not just the IT delivery landscape, but the dynamic and interactions across the entire Enterprise.
+
+
We are then intending to explore what global Enterprises have to gain by embracing DevOps or lose by not doing so, and help them answer the question: “Are we doing enough DevOps yet?”.
+
+
DevOps doesn’t necessarily come easy to established organisations so looking at the challenges these Enterprises face and how they can be successfully overcome is important. We will offer vision from DevOps and Lean specialists, insights from industry leaders as well as practical approaches and guidance from technology specialists. Areas of interest include:
+
+
+
Legacy management – What is legacy in the context of DevOps and proven strategies for removing it from the Enterprise.
+
Regulatory compliance and DevOps – A look at of regulatory requirements for FinTechs and different ways to optimise the flow of change whilst remaining compliant.
+
Tactical thinking vs. Sustainability – How to challenge motivations for “Tactical” delivery and embedding Sustainability as the foundation of the Enterprise architecture.
+
Vendor relationships – How to apply DevOps principles and realise associated benefits with third party providers of software and/or services.
+
+
+
Having covered the “Why do DevOps across the Enterprise” we’ll also be looking at the “How to do it”. In addition to discussing the need to establish a goals-driven continuous improvement culture, we’d also like to look at:
+
+
+
The automation landscape – How various tools are being used to facilitate the flow of work.
+
Metrics strategies both during and after DevOps adoption in the Enterprise.
+
Setting the Enterprise DevOps context – Balancing innovation vs. estate management and making it easier to collaborate.
+
+
+
As well as presentations, ignites sessions (short presentations with Q&A) and open spaces (delegate driven breakouts) , we will be arranging panel sessions which will allow delegates to ask questions and see them debated by DevOps thought leaders, heads of industry and regulatory representatives.
+
+
Amongst the several DevOps and Lean experts attending DevOpsDays London 2016 we are very pleased to have Gene Kim (co-author of The Phoenix Project) and Joanne Molesky (co-author The Lean Enterprise) joining us. You will have the opportunity to meet them in person and hear them speak on a variety of subject matter aligned to the Enterprise theme.
+
+
The first day will conclude with networking drinks for all delegates. Platinum and Gold sponsors will also be invited to dine in the Hotel’s roof top restaurant along with the presenters, thought leaders, event organisers and fellow Platinum/Gold sponsors.
+
+
Sponsors are able to locate stands adjacent to the main conference room and the catering space. Your company logo will feature on merchandise, panels on the main stage and on an impressive digital column at the entrance to the venue. Lastly, a short presentation to the audience will also be offered in line with the sponsorship level (Platinum, Gold and Silver packages only).
+
+
We hope you are as excited about DevOpsDays London 2016 as we are and appreciate the opportunity sponsorship could bring you.
+
+
If you are interested in being a sponsor please confirm the package you would like to go for via email to barry.chandler@barclays.com who will issue an invoice with payment instructions. We recommend confirming your sponsorship ASAP as demand is high.
+
+
+
+
+
Sponsor Packages
+
+We are offering the following packages (all prices are excluding VAT @20%):
+
+
+
+
+
+
+
Contents
+
Bronze £1000 gbp
+
Silver £3000 gbp
+
Gold £7000 gbp
+
Platinum £20000 gbp
+
+
+
Event Representation
+
Complimentary tickets
1
2
5
15
+
Stand
Small
Medium
Large in prime location
+
Time to address the delegates
1 minute
3 minutes
5 minutes
+
+
Networking
+
Complimentary drinks reception after Day 1
✔
✔
✔
✔
+
Guests to attend meal with DevOps thought leaders,
+Conference organizers and other sponsors
1
5
+
+
Branding
+
Small logo on merchandise, digital pillar, stage panels and website
This event took place: Tuesday 19th April 2016 - Wednesday 20th April 2016 and was SOLD OUT!
+
It was followed by a Hackathon.
+
+
+ {{< event_logo >}}
+
+
+
The rise of DevOps, enabling the lean Enterprise
+
+
The emphasis of DevOpsDays London 2016 is on DevOps in the Enterprise with specific reference to the Financial Services Industry. With that said, the event is open to any delegate, and we especially encourage participation by Enterprises for whom DevOps may not yet seem a natural fit, intuitive or adding value.
+
+
To begin with we will look at the origins of DevOps, its various reference points, scope of application and why these new ways of working are changing, not just the IT delivery landscape, but the dynamic and interactions across the entire Enterprise.
+
+
We are then intending to explore what global Enterprises have to gain by embracing DevOps or lose by not doing so, and help them answer the question: “Are we doing enough DevOps yet?”.
+
+
DevOps doesn’t necessarily come easy to established organisations so looking at the challenges these Enterprises face and how they can be successfully overcome is important. We will offer vision from DevOps and Lean specialists, insights from industry leaders as well as practical approaches and guidance from technology specialists. Areas of interest include:
+
+
+
Legacy management – What is legacy in the context of DevOps and proven strategies for removing it from the Enterprise.
+
Regulatory compliance and DevOps – A look at of regulatory requirements for FinTechs and different ways to optimise the flow of change whilst remaining compliant.
+
Tactical thinking vs. Sustainability – How to challenge motivations for “Tactical” delivery and embedding Sustainability as the foundation of the Enterprise architecture.
+
Vendor relationships – How to apply DevOps principles and realise associated benefits with third party providers of software and/or services.
+
+
+
Having covered the “Why do DevOps across the Enterprise” we’ll also be looking at the “How to do it”. In addition to discussing the need to establish a goals-driven continuous improvement culture, we’d also like to look at:
+
+
+
The automation landscape – How various tools are being used to facilitate the flow of work.
+
Metrics strategies both during and after DevOps adoption in the Enterprise.
+
Setting the Enterprise DevOps context – Balancing innovation vs. estate management and making it easier to collaborate.
+
+
+
As well as presentations, ignites sessions (short presentations with Q&A) and open spaces (delegate driven breakouts) , we will be arranging panel sessions which will allow delegates to ask questions and see them debated by DevOps thought leaders, heads of industry and regulatory representatives.
+
+
+Amongst the several DevOps and Lean experts attending DevOpsDays London 2016 we are very pleased to have Gene Kim (co-author of The Phoenix Project) and Joanne Molesky (co-author The Lean Enterprise) joining us. You will have the opportunity to meet them in person and hear them speak on a variety of subject matter aligned to the Enterprise theme.
+
+
+
The first day will conclude with networking drinks for all delegates.
+
+{{< event_link page="registration" text="Register to attend the event!" >}}
+
+
+
+View the {{< event_link page="program" text="program" >}}!
+
+
+
+{{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to promote your organization.
+
+
+
+{{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-losangeles-1day/conduct.md b/exampleSite/content/events/2016-losangeles-1day/conduct.md
new file mode 100644
index 000000000..83ca24cf2
--- /dev/null
+++ b/exampleSite/content/events/2016-losangeles-1day/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-02T13:23:30-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-losangeles-1day/contact.md b/exampleSite/content/events/2016-losangeles-1day/contact.md
new file mode 100644
index 000000000..bed1f4e8b
--- /dev/null
+++ b/exampleSite/content/events/2016-losangeles-1day/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-02T13:23:30-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-losangeles-1day/location.md b/exampleSite/content/events/2016-losangeles-1day/location.md
new file mode 100644
index 000000000..5168ba880
--- /dev/null
+++ b/exampleSite/content/events/2016-losangeles-1day/location.md
@@ -0,0 +1,41 @@
++++
+date = "2016-05-02T13:23:30-05:00"
+title = "location"
+type = "event"
+
++++
+
+
+The convention center’s subterranean parking structure has plenty of available space. There are two entrances, (a) on Marengo Avenue, and (b) Euclid Avenue, both between Green Street and Cordova Street.
+
+Park costs $12 a day for up to 16 hours; $18 a day for in-and-out privileges.
+
+
+
Hotel Room Block
+
+
DevOpsDay LA and SCALE have arranged a discounted room
+rate of $119/night at The Westin Pasadena hotel, which is just a short walk away from the conference
+center. Rooms may be booked via the Westin website,
+or via telephone (626) 792-2727. If booking via telephone please mention SCALE14XEXPO to receive
+the group rate.
+
+
+The Westin Pasadena
+191 North Los Robles
+Pasadena, CA 91101
+United States
Haute Performance: Cracking the Flash Sale - Joel Salas
+
11:45-12:15
Open Source tools for distributed systems administration - Elizabeth K. Joseph
+
12:15-13:45
Lunch Break
+
13:45-14:15
Config Management Sucks - Justin Garrison
+
14:15-15:00
Open Space (Open Space) Open Space Opening
+
15:00-16:30
Open Space (Open Space) Open Space #1
+
15:30-16:00
Open Space (Open Space) Open Space #2
+
16:00-16:30
Open Space (Open Space) Open Space #3
+
16:30-17:00
Closing Circle
+
19:00-late
Expo Hall Reception
+
diff --git a/exampleSite/content/events/2016-losangeles-1day/propose.md b/exampleSite/content/events/2016-losangeles-1day/propose.md
new file mode 100644
index 000000000..948e439b0
--- /dev/null
+++ b/exampleSite/content/events/2016-losangeles-1day/propose.md
@@ -0,0 +1,51 @@
++++
+date = "2016-05-02T13:23:30-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+
+There are three types of session proposals we are reviewing:
+
+
A proposal for a talk/panel during the conference part : these are 20-45 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+How to submit a proposal:
+
+
If you are a registered speaker from a previous SCALE or DevOpsDay LA event, you can re-use your account from the previous submission with out signing up for a new account (and you can skip the next paragraphs).
+
+
For first-time submitters, "Create a new account". You will be asked to provide your name name, affiliation, bio, and an email address of the speaker. Please ensure that the personal biography is not more than 1000 characters; focus on relevant experience to your proposal topic and write from the third-person perspective.
+Once registration is complete, an email will be automatically sent to the email-address to set the password for subsequent access.
+
Enter the title for the talk, the intended audience, and select DevOps as the TOPIC. Then provide a brief description of the main points to be presented. Provide additional details in the space provided. Also, include the names of all speakers that will present this session. Each speaker must be registered with the system before they can be entered in the "speaker" field.
+
+
Once the talk has been submitted, further edits to the submission can be made, if necessary, up to the CFP closing date by logging into the account with the credentials provided during registration. Be sure to include an email for the primary contact for the presentation. Important information will sent to that address.
+
+
In the notes to reviewers section, please indicate if you are submitting a session, ignite talk,
+or open space session. Additionally please notify us if the presentation will require a special technical set-up. The standard setup provided will include:
+
+
+
microphone
+
projector
+
a laptop running Linux with a postscript viewer as well as OpenOffice (you may bring your own laptop if you prefer)
Proposal abstracts are reviewed by our organizing committee and evaluated solely on merit.
+Given the number of high quality submissions received every year, we request that submission dates
+be strictly honored in order to provide the committee enough time to choose the best set of
+proposals.
+
+Our main criteria to make it to the top selection are:
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
diff --git a/exampleSite/content/events/2016-losangeles-1day/sponsor.md b/exampleSite/content/events/2016-losangeles-1day/sponsor.md
new file mode 100644
index 000000000..16578c45a
--- /dev/null
+++ b/exampleSite/content/events/2016-losangeles-1day/sponsor.md
@@ -0,0 +1,19 @@
++++
+date = "2016-05-02T13:23:30-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
diff --git a/exampleSite/content/events/2016-losangeles-1day/welcome.md b/exampleSite/content/events/2016-losangeles-1day/welcome.md
new file mode 100644
index 000000000..71d17b95a
--- /dev/null
+++ b/exampleSite/content/events/2016-losangeles-1day/welcome.md
@@ -0,0 +1,33 @@
++++
+date = "2016-05-02T13:23:30-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-losangeles-1day"]
+
++++
+
+
+DevOps Days is returning to Los Angeles!
+
+Dates: January 22nd, 2016
+
+We are proud to announce 6th Annual DevOps Day LA, to be held Friday, January 22, 2016, co-located
+with SCALE 14x, at the Pasadena Convention Center.
+
+
+DevOps Day LA is a single day event dedicated to the DevOps community, and professionals who wish
+to improve the interaction and integration between these traditional silos of Development and
+Operations. We're looking for speakers interested in presenting to this forum. The theme for the
+conference this year is "Surprise!", a phrase that all too often fills devops
+teams with dread, but can also be positive.
+
+{{< event_link page="propose" text="Proposals" >}} for sessions, open spaces, and ignite style talks will be reviewed through Nov 30th.
+
+Register!
+ {{< event_link page="program" text="View the program" >}}!
+
+
+
+{{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to promote your organization.
+
+Email the organizers: {{< email_organizers >}}
diff --git a/exampleSite/content/events/2016-madison/conduct.md b/exampleSite/content/events/2016-madison/conduct.md
new file mode 100644
index 000000000..daa2e2687
--- /dev/null
+++ b/exampleSite/content/events/2016-madison/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-05T11:56:18-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-madison/contact.md b/exampleSite/content/events/2016-madison/contact.md
new file mode 100644
index 000000000..08c0ca8b2
--- /dev/null
+++ b/exampleSite/content/events/2016-madison/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-05T11:56:18-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-madison/location.md b/exampleSite/content/events/2016-madison/location.md
new file mode 100644
index 000000000..d03cb3db2
--- /dev/null
+++ b/exampleSite/content/events/2016-madison/location.md
@@ -0,0 +1,21 @@
++++
+date = "2016-05-05T11:56:18-05:00"
+title = "location"
+type = "event"
+
++++
+
+### Conference Location
+Overture Center for the Arts
+201 State St
+Madison, WI 53703
+
+{{< event_map >}}
+
+### Conference Hotel
+We have a small number of rooms held at our conference hotel for a limited time.
+DoubleTree by Hilton Hotel Madison
+525 W Johnson St
+Madison, WI 53703
+
+Booking link
diff --git a/exampleSite/content/events/2016-madison/program.md b/exampleSite/content/events/2016-madison/program.md
new file mode 100644
index 000000000..6237035a4
--- /dev/null
+++ b/exampleSite/content/events/2016-madison/program.md
@@ -0,0 +1,365 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
Title:
+Humane Treatment of OnCall Engineers: Stopping the burnout while firefighting
+
+
+
Description:
+
+
+It’s no secret, OnCall responsibilities suck. No one’s happy holding the pager and in the Ops world, that can be a real problem. The additional, unplanned, after-hours work leads to faster burnout among Engineers. By taking real steps to shift our perspectives of OnCall, we can reverse the problem.
+
+I probably am doing DevOps without even knowing it. When I discovered the DevOps Dictionary definition of “goat” I fell in love. My perspective on DevOps as a self-taught woman in technology and what the DevOps community could be more inclusive and accessible to me and other people I know.
+
Title:
+An Optimist’s Guide to Chaos Engineering
+
+
+
Description:
+
+
+Chaos Engineering ya or nah? Let’s discuss how CE can fit into your organization. Failure injection is not just for unicorns, and you don’t need a Simian Army to put resilience into your systems. Failure injection should be as simple as purposefully creating opportunities to learn about the system.
+
Title:
+The Fiery Flames of Production and Mellow Pastels of Staging: Distinguishing environments on instances
+
+
+
Description:
+
+
+You’re triaging an issue. Panic is set in, and you have ten different SSH sessions going in one terminal, on a variety of different boxes. How do you know where you are? Are you in staging? Production? Let’s talk about a simple way to distinguish environments with a little configuration and FIRE.
+
Title:
+Mining metrics from Source Code Meta Data
+
+
+
Description:
+
+
+Using the GitHub API, we can find and generate interesting metrics from our repository’s meta data. In this lightning talk, we’ll look at language diversity, discover collaboration and even analyze human conversation!
+
+Change is constant. We need to be able to adapt. What can we do to improve faster? What can we do to level up our teams? Understanding how the brain works can help put us on track to learn the skills we need to excel. We can use these techniques to improve ourselves, our teams and our processes.
+
+In the professional world when you decide to leave your job there is a whole process. Traditionally you’ll begin to transition tasks you worked on to another employee, your various accounts are terminated, you’ll go through an exit interview and then receive your final paycheck before being escorted from the building. But what happens when you decide to leave an open source project? Are you no longer a member of that community simply because you’re no longer actively contributing? Can you easily come back to the project? This talk will hopefully answer these and other questions.
+
+Superior technology does not sell itself. Transformations to your organization’s IT processes won’t happen by itself either. Tying all of potential value back to the business is a key part of getting buy in from upper management and can help solidify your value to the organization.
+
Title:
+Starting with C: Implementing DevOps from the Bottom Up
+
+
+
Description:
+
+
+Culture is the beginning of everything in DevOps. But many are stifled by a perceived need for management to change the culture. This talk explores things any employee at any level can do to influence culture change.
+
+Board games are not only fun; they are great for team building. Co-operative games are a great way to see how people operate under pressure. Your company may have a disaster recovery plan but most DR tests do not involve unknowns and stress. I hope to inspire you to incorporate gaming into work.
+
Title:
+case when devops = 1 then compliance = 'simplified' else compliance = 'pita' end
+
+
+
Description:
+
+
+This is a field report from two teams at a software company that tried to build a compliance program from scratch using two different approaches. The first team hired compliance experts from the outside and the second team combined existing dev and ops people. Only one team had a lasting impact.
+
Title:
+Don’t be a Security Bully: Strategies for Getting Security Picked First on the Developer Playground
+
+
+
Description:
+
+
+Security gets a reputation as naysayers who deliver bad news. Developers wonder why Security gets in the way, while Security are left wondering why Development won’t ask for help when a security issue arises. This talk will improve your collaboration by presenting a new perspective on how we work.
+
+The premise that dev and ops are at odds is a fallacy. These groups naturally align because they share a problem solving approach. My organization is driven by creativity, and it takes more than aligned incentives to create high-functioning teams. I’ll talk about the journey to empathy and trust.
+
Title:
+Welcome to the Brownfield: Where automation meets reality
+
+
+
Description:
+
+
+Automation is great when you have a clean slate, but most of us don’t. This talk will walk through an automation journey where applications and business are already happening. We’ll cover pitfalls, stories and thought process.
+
+I came to DevOps from being a DBA, which is one of the most resistant IT groups to automation. My talk will focus on how the journey I took was supported by management cultures and team cultures that foster individual growth and help increase and sustain diversity on DevOps teams.
+
Title:
+Tips for selling Continuous Delivery to your business (from a business person :))
+
+
+
Description:
+
+
+Explaining why businesses should do continuous delivery can be hard. As a product manager I want to share with you how you can convince your product managers and others in your business why you should practice continuous delivery.
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
diff --git a/exampleSite/content/events/2016-madison/speakers.md b/exampleSite/content/events/2016-madison/speakers.md
new file mode 100644
index 000000000..008436b74
--- /dev/null
+++ b/exampleSite/content/events/2016-madison/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-11-03T07:43:45-05:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-madison/sponsor.md b/exampleSite/content/events/2016-madison/sponsor.md
new file mode 100644
index 000000000..2e5cb964b
--- /dev/null
+++ b/exampleSite/content/events/2016-madison/sponsor.md
@@ -0,0 +1,41 @@
++++
+date = "2016-05-05T11:56:18-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please check out our prospectus or [send us an email](mailto:organizers-madison-2016@devopsdays.org?subject=Interested in Sponsoring DevOpsDays Madison 2016).
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Gold sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Bronze 1000 usd
+
Silver 2500 usd
+
Gold 4000 usd
+
+
+
included tickets
1
2
4
+
logo on event website/signage
+
logo on shared slide during breaks
+
1 minute pitch to full audience
+
booth/table space
1/2 Table
Full Table
+
+
+There are also opportunities for exclusive special sponsorships. Examples of this may include but are not limited to the evening event, lanyards, meals or snacks. If you are interested in special sponsorships or have a creative idea about how you can support the event, [send us an email](mailto:organizers-madison-2016@devopsdays.org?subject=Interested in Sponsoring DevOpsDays Madison 2016).
+
+
+
+ {{< event_link page="registration" text="Register to attend the conference!" >}}
+
+
+
+
+
+ Program
+
+
+ View the {{< event_link page="program" text="program." >}}
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter devopsdaysmsn >}}
diff --git a/exampleSite/content/events/2016-minneapolis/conduct.md b/exampleSite/content/events/2016-minneapolis/conduct.md
new file mode 100644
index 000000000..619a3241d
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Minneapolis"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-minneapolis/contact.md b/exampleSite/content/events/2016-minneapolis/contact.md
new file mode 100644
index 000000000..1e9a7a506
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Minneapolis"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-minneapolis/location.md b/exampleSite/content/events/2016-minneapolis/location.md
new file mode 100644
index 000000000..615a5c9a5
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/location.md
@@ -0,0 +1,16 @@
++++
+City = "Minneapolis"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+The conference will take place Wednesday July 20 and Thursday July 21, 2016 at the downtown Minneapolis Hilton. The Hilton has very few hotel rooms available, but there are many other hotels nearby.
+
+Last year, we worked with the hotel to make space available for nursing mothers, and if that would be useful for you, please let us know. We'd also be happy to accommodate any other accessibility needs. You can reach out on devops MSP Slack or via email.
+
+The recommended way to travel between the airport and downtown Minneapolis is via the light rail train to Nicollet Mall station. You can walk (under a mile), transfer to a free bus on the bus/bike/pedestrian Nicollet Mall in downtown, or take a short cab ride from the LRT. Uber & Lyft are also available, as is car2go.
+
+
+If you spend most of your time in places like Portland or Brooklyn, our metro will feel familiar, with its bike share stations, beautiful riverfront, and numerous craft brewery tap-rooms with food trucks in their parking lots.
diff --git a/exampleSite/content/events/2016-minneapolis/program.md b/exampleSite/content/events/2016-minneapolis/program.md
new file mode 100644
index 000000000..27963be30
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/program.md
@@ -0,0 +1,365 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+ With talks in the morning and attendee-suggested Open Space breakout discussions in the afternoon, we have two full days of content!
+
+
+
+
+
+
+
The Schedule
+
+
+
+
+
+
+
+
Wednesday July 20
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
Title:
+ Your Meetings Are Unbearable: Cheat Codes From Occupy
+
+
+
Description:
+
+
+Most work meetings are full of interruptions, repetitions and microaggressions. To make matters worse, they always seem to drag on forever. At Occupy, ain't nobody got time for that, so we adapted time-tested anarchist techniques and came up with a simple, efficient horizontal decision-making process. I would like to show you the hand gestures that go with these techniques; these alone are guaranteed to cut your meeting times in half and save 72% of your sanity.
+
Docker and Kubernetes provide delightful APIs to show various statuses of our applications. Whether CPU, Load average, HTTP response times, etc., we have all that we need to make sure our app is running healthily. When things are on fire, we Ops people twiddle some knobs like spin up more Pods to keep things going. We mostly use our experience and knowledge of the systems that we are running to know what to do.
+
+
+However, if you look at everyday things like your air conditioner and thermostat, they don't have an Ops team that gets paged to set the correct level of the coolant to set your room to the right temperature. They use some math called Control Theory to keep your room's temperature stable. In this talk, I will show how we can use the same concepts to autoscale and manage the health of our applications on Kubernetes.
+
Title:
+ Barriers to Entry: Educating Future Developers
+
+
+
Description:
+
+
+Often times going from non-developer to new developer isn't as much about the difficulty of the subject matter, but the life experiences--both past and present--that form the context for our learning environment.
+
Title:
+What if You Can’t Tear Down All The Silos?
+
+
+
Description:
+
+
+We keep hearing that to 'do DevOps right' we need to tear down all the silos in order to get everyone collaborating as well as just cooperating. How do we continue to benefit from DevOps practices when the silos are there for the foreseeable future and may actually have some benefit, even if only perceived?
+
+
+In a large enterprise, dedicated operations groups frequently serve multiple development groups, using the specialization of these groups to increase efficiency by having a smaller operations staff. These organizations use separation of duties to avoid real or apparent conflicts of interest and a higher level of security. Silos become firmly embedded because they work in these situations.
+
+
+When silos are entrenched and can’t be torn down, or even when they’re just dictated above our pay grades, how can we use DevOps to increase collaboration and empathy? What other concepts of DevOps can we use to reduce the pain? What can operations teach development and learn from development to make systems more reliable and IT more successful?
+
+
+In this session, I’ll present my version of the DevOps philosophy and how it can be applied in an enterprise environment without tearing down all the silos. I’ll tell success stories and failures as well as discussing continuing challenges to make improvements and change the culture in the trenches.
+
+
+
+
Title:
+Making good choices with software (and other impossible things) (Closing Keynote)
+
+
+
Description:
+
+
+Once upon a time there was a LAMP stack, and a data center, and making reasonably good technical decisions was a thing that ordinary mortals could do. Over the last few years we've seen an explosion of complexity -- composable infrastructure, polyglot persistence, and third-party platforms or services who claim they can solve your problems for you (sometimes this is even true!).
+
+
+
+What does this mean for you and me? It means that good technical judgment is both more challenging and more important than ever before. In this talk we will cover things like about when to use boring technology, versus when to take a flyer on something new and shiny. We'll also talk about how to resist software sprawl, gating new technologies into production, and how to balance speed of development vs operational impact over time. So don't despair! With just a little bit of discipline, we can still build systems that ordinary humans can understand and maintain, even in the face of skyrocketing complexity and problems of scale.
+
+College is the most well-known path to landing a professional job, and a four-year degree is frequently listed as a requirement on IT job postings. How else can one establish themselves as a professional nerd?
+
+I wanted to learn google cloud deployment with docker and kubernetes so that I can be more useful to my team. I picked a small side project that would be fun, could benefit my team, and was manageable to fail at without slowing anyone down. I made someone’s slackbot exercise trainer more polite and added cute gifs of baby animals for intermittent reinforcement. Now I’ve gained my team’s trust to deploy our much bigger project to gcloud.
+
Title:
+Intentional Design of Your Monitoring System
+
+
+
Description:
+
+
+A good monitoring stack is more than the software that says ‘monitoring’ on the label. Maybe your monitoring system is a bunch of cron scripts that send email when things happen. Maybe you dropped $100K on licensed software that can email reports and has its own mobile app. When used as part of systemic approach to monitoring, both approaches can lead your organization to success.
+
+
+
+Monitoring is a stack, and like most web applications there are discrete components that all systems have. Sometimes they’re automated, sometimes they’re 100% people-driven. What matters is that you have the system that works for you and your organization.
+
+
+
+We will cover what those components are and how they work together. What’s more, we’ll touch on the conversations you should have as you work to systematize your monitoring practices. We won’t tell you what technology you should use, that’s entirely up to you.
+
+
+A light comical talk surrounding the daily woes and benefits of reporting across an organization. Tough conversations, difficult personalities, unrealistic expectations.
+
+Your organization is rolling out DevOps and everyone is excited and on-board! Life is going to be perfect post-devops, because DevOps is the cure for all that ails your company. Because levels expectations and levels of disappointment seem to have a relationship, I’d like to talk to you about our experience with the DevOps transformation.
+
+
+Come join Jeff Smith as he walks through the trials and tribulations of destroying the silos in your organization. Buried inside all of the hype of DevOps are hurdles, people problems and mission creep that can derail your transformation. We’ll cover areas like:
+
+
+* Toolchain Paralysis - With all the tools out there to help you realize the DevOps dream, its easy to get caught up in the tools/solution hype cycle. Don’t let the community tell you what is a must-do. We’ll talk about making sure you solve your problems instead of Google’s or Facebook’s.
+
+
+* Skill set augmentation - DevOps chats are famous for the adage “Hire the Right People”. But I’m guessing you already thought you were doing that. How do you get developers and ops to gain skills in the other’s discipline?
+
+
+* On Call Support - When you disperse Ops staff into stream teams, you also have the potential to dilute the number of on-call people who can handle issues. There are tons of options and all of them have a downside.
+
+
+and more! Don’t think these hurdles are new or unique. You’ll get through them, and hopefully we’ll help show you how.
+
+
Title:
+ Confessions of a Former Professional Lego Master Builder
+
+
+
Description:
+
+
+John shares pictures and stories from his time being employed by LEGO Systems Inc. as a Professional Model Builder. Learn about how giant LEGO display models are designed and built.
+
+In 1944, the Office of Strategic Services—the predecessor of the post-war CIA—was concerned with sabotage directed against enemies of the US military. Among their ephemera, declassified and published today by the CIA, is a fascinating document called the Simple Sabotage Field Manual (PDF). It's not just about blowing things up; a lot of its tips are concerned with how sympathizers with the allied cause can impair enemy material production and morale.
+
Title:
+How Security Can Win Friends and Influence People
+
+
+
Description:
+
+
+Security 101 principles often conflict with how organizations function in the real world. Developers need flexibility in order to solve hard problems; companies need a stable product to satisfy customers. Employees don’t want to click through ten different screens to complete daily tasks; auditors and regulators demand logs and accountability.
+
+
+
+Legacy systems need to be monitored. New projects need to be nurtured. And, while you’re doing all of that, attackers are constantly rattling the doorknobs to find a foothold in your network. I’ll go over a few lessons I’ve learned about how security departments can lobby for continuous improvement, while collaborating with others and even occasionally saving the organization money.
+
+
+
+Over my career, I’ve worked in .com, retail, and academia. While the challenges in each of these realms are unique, there is a common thread in all of the successful outcomes I’ve witnessed. Effective security departments are optimists who play well with others.
+
+
+
+It's fun to pretend you're the smartest person in the room ... until no one wants to play with you. The “us versus the world” mindset isn’t constructive. In this talk I’ll illustrate how security can work for change without alienating everyone else on the playground.
+
+
Title:
+The Data on DevOps: Making the Case for Awesome
+
+
+
Description:
+
+
+What’s the value proposition of DevOps? Does culture change show up in the bottom line? What practices predict high IT performance? We hear many stories to inspire and inform us, but the plural of anecdote is not data. Let’s dive into the research and find out which DevOps practices drive optimal IT and business outcomes.
+
+
+
+The data shows that the best IT performers have the highest throughput and reliability while contributing to organizational profitability, productivity, and market share goals. Industry trends around security, containers, continuous delivery, and lean management relate to IT performance and quality: let’s talk about how.
+
+
+
+Management and practitioners alike will leave with a better understanding of how to achieve the best outcomes, while armed with the data they need to make the case for change.
+
+
Title:
+Marketing: your unexpected devops allies
+
+
+
Description:
+
+
+Development teams and sales/marketing teams aren't always BFFs. Too often, the relationship is downright dysfunctional: either marketing dictates what the product team builds based solely on what is "sellable" with little consideration to timelines or what non-customer-facing work needs to be done, or the product team does a bunch of random work with little consideration for creating a strong marketing "story". But it doesn't have to be this way.
+
+
+In the devops spirit of cross-team collaboration, why not recruit sales and marketing as your newest allies in the fight against workplace silos?
+
+
+This talk will cover practical and battle-tested ways to work together towards a higher-quality and more marketable piece of software. From semi-obvious things like information radiators, to deeper collaborations in roadmapping and release planning, there's a lot more you can do than just invite the sales team to your stand-ups.
+
+
Title:
+Positively preoccupied with Pokémon (and other timely topics)
+
+
+
Description:
+
+
+Are half the adults you know suddenly preoccupied with Pokémon? Today's teens may be as well, but, like adults, they also use tech in many other ways, for good or for ill. Let's talk about the negative influence technology can have on teens (e.g. cyberbullying) and ways that technology can make a positive impact on teenagers' lives.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-minneapolis/propose.md b/exampleSite/content/events/2016-minneapolis/propose.md
new file mode 100644
index 000000000..61fecf4e6
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/propose.md
@@ -0,0 +1,36 @@
++++
+City = "Minneapolis"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+
+
+
+The CFP for 30-minute talks is closed and the selected talks have been listed on the program.
+
+The CFP for Ignites is also closed and selected talks will be listed on the program as soon as all proposers have been notifed.
+
+
+Open Space breakout sessions
+
+If you'd like to lead a group discussion during the Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table.
+
+
+
+
+
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
+- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+- _original content_: We prefer talks not already presented at another event, especially another one in the local area or one available in recorded form.
+- _no third-party submissions_: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
+- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
+
+
+If your employer does not cover travel expenses you incur as a speaker at devopsdays Minneapolis, the conference can and will help; speakers receive free conference tickets and should not need to incur out-of-pocket travel expenses in order to participate.
diff --git a/exampleSite/content/events/2016-minneapolis/registration.md b/exampleSite/content/events/2016-minneapolis/registration.md
new file mode 100644
index 000000000..c2f0de53f
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/registration.md
@@ -0,0 +1,10 @@
++++
+City = "Minneapolis"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+At 700+ attendees, the conference is sold out!
diff --git a/exampleSite/content/events/2016-minneapolis/speakers.md b/exampleSite/content/events/2016-minneapolis/speakers.md
new file mode 100644
index 000000000..8e8e2e0d1
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-minneapolis/sponsor.md b/exampleSite/content/events/2016-minneapolis/sponsor.md
new file mode 100644
index 000000000..03f24bf92
--- /dev/null
+++ b/exampleSite/content/events/2016-minneapolis/sponsor.md
@@ -0,0 +1,61 @@
++++
+City = "Minneapolis"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+Platinum, Gold, and Silver sponsorship packages are detailed in our prospectus.
+All Platinum, Gold, and Silver Sponsorships for 2016 are sold out! Thank you for your support!
+
+Additional à la carte sponsorships are still available:
+
+
+
coffee ($1k) - 2 slots available - signage by the coffee displays with your logo throughout the day
+
breakfast ($2k) - 2 slots available - signage by the breakfast tables and in the eating area with your logo in the morning before sessions
+
snacks ($2k) - 4 slots available - signage by the snack area with your logo during the afternoon when snacks are available
+
lunch ($2k) - 1 slot available - signage by the lunch tables and in the eating area with your logo during lunch
+
evening happy hour ($4k) - 1 slot available - signage at the evening happy hour
+
lanyard - SOLD OUT
+
+
+These may be purchased in addition to (or in lieu of) the sponsorships in the prospectus.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+
+All sponsors get a full table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Silver* SOLD OUT
+
Gold* SOLD OUT
+
Platinum* SOLD OUT
+
+
+
3 included tickets
+
3 additional tickets (6 in total)
+
Full Table
+
Logo on DevOpsDays Minneapolis website, main room signage, and email communication.
+
Logo on shared slide during breaks
+
Logo on shared signage in breakout rooms
+
Logo on shared slide in recorded video pre-rolls
+
Logo on dedicated slide during breaks
+
Logo on dedicated signage in breakout rooms
+
Logo on dedicated slide in recorded video pre-rolls
+
1 minute pitch to full audience (including streaming)
+
5 minute pitch to full audience on Day 1 (including streaming)
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+{{< event_twitter devopsdaysmsp >}}
+
diff --git a/exampleSite/content/events/2016-nashville/conduct.md b/exampleSite/content/events/2016-nashville/conduct.md
new file mode 100644
index 000000000..eeff84dfd
--- /dev/null
+++ b/exampleSite/content/events/2016-nashville/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2000-01-01T01:01:01-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-nashville/contact.md b/exampleSite/content/events/2016-nashville/contact.md
new file mode 100644
index 000000000..10ec910db
--- /dev/null
+++ b/exampleSite/content/events/2016-nashville/contact.md
@@ -0,0 +1,16 @@
++++
+date = "2016-11-10T21:16:08-06:00"
+title = "Contact"
+type = "event"
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+Our local team
+
+{{< list_organizers >}}
+
+The core devopsdays organizer group
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-nashville/location.md b/exampleSite/content/events/2016-nashville/location.md
new file mode 100644
index 000000000..aedcf11d0
--- /dev/null
+++ b/exampleSite/content/events/2016-nashville/location.md
@@ -0,0 +1,14 @@
++++
+City = "Nashville"
+Year = "2016"
+date = "2016-06-01T11:24:00-05:00"
+title = "location"
+type = "event"
+
++++
+The conference will take place Thursday, November 10 and Friday, November 11, 2016 at aVenue in Downtown Nashville!
+
+
+
+
+There are plenty of hotel options in the immediate downtown area, as well as a short bus ride or Uber/Lyft ride away. Our team is currently securing a hotel block within walking distance of the event. Stay tuned for block rates.
diff --git a/exampleSite/content/events/2016-nashville/program.md b/exampleSite/content/events/2016-nashville/program.md
new file mode 100644
index 000000000..c8af7ea18
--- /dev/null
+++ b/exampleSite/content/events/2016-nashville/program.md
@@ -0,0 +1,368 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+As a social species, we’ve developed many tools for communication. Before there was written word, we were telling stories around communal fires to share the dangers and enforce societal values. As we’ve continued to develop faster and more efficient forms of communication, we’re missing out on the key thing that makes us human: The stories. Nothing in our lives has meaning except for the story behind it. If you’re sharing raw metric data about application performance, it means nothing if it doesn’t tell a story. Even if we’re just sending “No.” through text, we’re telling a story about more than just that response. Recognizing the stories we tell and honing our storytelling skills will improve communication, collaboration and community amongst our peers.
+
Title:
+ An ode to 'if-else': how this simple construct changed LinkedIn's engineering culture
+
+
+
Description:
+
+I was part of LinkedIn's engineering team from 2009-2013. In that period, I saw LinkedIn transform from a slow moving organization perpetually behind schedule to a team hyper focused on continuously delivering value to their customers. There were many factors that made this change possible. One of the simplest and elegant was the mandate that every new feature should be wrapped in an if-else statement. In this talk, I will share my love for this basic idea and tell the story of how it changed a culture.
+
+Everyone is looking for the secret techniques, the one true way. Devops never had secrets, with the possible exception of the secret everyone is hiding, devops is hard. The search for secrets leads to nowhere. Now we better get back to work.
+
+Communication is a bedrock of DevOps practices. Empathic communication among teams and stakeholders leads to better understanding, a shared vision, and ultimately healthier and more productive team dynamics.
+
+
+Interacting empathically with other humans is a skill worth practicing. In this talk we'll explore some common patterns, the underlying science, and supporting technologies that can help develop empathetic skills that you might not get to practice mindfully while doing the technical parts of your daily work.
+
+
+Even mimicking these behaviours, through the power of habit and neuroplasticity, can build empathy between team members leading to improve team dynamics and DevOps-y-ness.
+
Title:
+ Working in and with Open Source Communities
+
+
+
Description:
+
+Starting an open source project is very easy, especially in the days of GitHub. Push your code and see if somebody is interested in. If you are able to gain attention and interest for you project you feel motivated and work all night long. But on the other hand, people will start complaining about open bugs, missing features and your evil or non existing website. Believe it or not, but this will pursue you until your last user dies.
+
+
+One of the most important things for a successful open source project is to treat you community well. This talk will share some experiences made during the last 6 years with Icinga. Starting with basic concepts, it deals with tools and methods helping to increase and cultivate your community. It also covers internal organisation requirements for successful community work and upcoming challenges if you strike some new paths with your project.
+
+Even the best designed systems can and will have outages. No matter how well you’ve hardened your infrastructure and put in place failover or self-healing automation, something you didn’t see coming will wreak havoc in your special snowflake of a system. In many cases a human is likely to be a contributing factor. In fact, Gartner has predicted that in 2015, 80% of outages will be caused by people and process issues.
+
+Are you considering the Human element when revisiting incidents and outages with your infrastructure? If so, are you approaching it with a blameless mindset focused on removing the many forms of bias and searching for absolute truth. Do you believe that there is always a root cause to outages or is it more accurate to seek out additional aspects that may have contributed to the incident, especially with regard to the people and processes?
+
+
+Regardless of your approach, the point of a postmortem is to accurately describe the "story" about what took place in as much detail as possible. The good, the bad, those involved, conversations had, actions taken, related timestamps, who was on-call, etc. You want to know absolutely everything that took place that was related in some degree so that you can review the data and learn from it.
+
+
+How do we ensure that we are asking the right questions and seeking out relevant and important information that will help us understand what took place and ultimately how to become a better team, company, and product as a result?
+
+
+The blameless culture (specifically blameless postmortems) is a topic of interest to many in the middle of a DevOps transformation within their organization. I'll outline important best practices for conducting effective postmortems and demonstrate methods to measure benefits from adopting postmortems especially those of a "blameless" nature.
+
Title:
+ Raised This Way: DevOps Lessons I Learned from My Family
+
+
+
Description:
+
+There are and will always be ongoing debates over the definition of ‘Devops' and how to implement it in our highly technical world. As a member of the DevOps community for many years I know these opposing views intimately, but I can’t help thinking I came into this arena knowing a lot of the fundamental principles. Looking back, I realized that it’s because everything I know about DevOps I actually learned from my family. Sit back, relax and enjoy a little Jubinski family history and everything you’ve ever wanted to know about DevOps without discussing tech at all
+
+
+This presentation will cover a short history of the Devops movement and also give some insight to where the movement stands as we end 2016. We will also look at the future opportunities moving into 2017 and beyond.
+
+The ideas and tools within the DevOps community are increasing and evolving each day. The pace is fast and only seems to be getting faster. How can we as individuals keep up without getting distracted or overwhelmed by every new thing? How can we intentionally move ourselves forward in a sustainable way? Continuous improvement provides a mindset for approaching this ongoing challenge. At its core, continuous improvement is a way to focus on getting a little better each day. In this talk we will dive into practical techniques like removing mental overhead through fixing what bugs you. We will look at developing deep focus as a critical skill for problem solving. We will also explore some learning techniques that will allow us to approach new tools and ideas with confidence and effectiveness.
+
Title:
+ Please forgive me! – Confessions from a Silo and How I Learned to Believe in the Business Value of DevOps
+
+
+
Description:
+
+
+I humbly ask for your forgiveness. I was once the cause of your IT delivery issues. I made developers and application owners wait, sometimes, up to 4 weeks for a VM! And I am now pretty ashamed. Then when I became an application owner, the cruel joke was played on me. So I demanded and deployed without a care. Both times incentives and organizations were misaligned and misinformed. This is a story about living in those two extremes, the perspective gained from a business degree, and how I came to believe that DevOps is what Modern IT [Business] should look like.
+
+Have you ever been pressed in your career about whether you want to management or technical? I get asked this a lot. My answer is always, “why do I have to choose?” I’d like to dive into the root of this question and then cover ways in which you can be a leader and still be a technical contributor. It’s a challenge, but certainly possible. I’ll draw on my experience over the last five years at Puppet, Inc.
+
+Items Covered:
+
+Hey, I’m an application developer and I’m done managing my server infrastructure. Stop slowing me down.
+
+
+Application developers are sick and tired of being slowed down by having to learn new tasks and care about mundane details. I don’t care about server infrastructure. In fact, I hate DevOps! I don’t need to worry about the differences between cloud and a data center; the applications I create are brilliant, running them is not my job. Let’s talk about walls and boundaries. You do your job, I’ll do mine, and we can both get back to moving fast.
+
+
+This talk is inspired, in part, by http://thenewstack.io/serverless-computing-growing-quickly/. As someone practicing DevOps for a number of years it’s really easy to let quotes like this make you cry: "DevOps significantly adds to the development time as application builders are weighed down by the need to manage their server infrastructure at the same time."
+
+Last year I worked as a network and infrastructure engineer for the West Africa Ebola response and polio eradication efforts in Nigeria. Rather than talking about our projects or the not-so-special technology we used I'd like to talk about the unique organizational challenges my team faced. A lot of common approaches fall apart in the contexts we worked in. Particularly interesting is the limited connectivity and how that changes communication between different parts of the organization.
+
Title:
+ The first 500 nodes: The story of our journey at a Microsoft centric enterprise
+
+
+
Description:
+
+ Although DevOps is becoming increasingly mainstream in enterprises, examples of DevOps applied to traditional 3-tier Windows Architecture on premises scenarios are not as prevalent (Although Linux examples are numerous). Microsoft implementations typically focus on e-commerce scenarios and/or simple IIS demonstrations. The cultural challenges at Microsoft enterprises are unique and can be more difficult to overcome as the engineers/administrators are much more accustomed to the GUI and "right clicking".
+
+Although some DevOps implementations may start in the C-Suite due to some existential threat, many more DevOps movements start as a grass roots effort and build momentum. Columbia Sportswear attended a couple of technical conferences in 2014 without any idea how to get DevOps started...This talk will discuss how we implemented our first 500 servers (including SAP, BizTalk, Sharepoint, and others...) on CHEF. This talk will focus how we started our cultural transformation, change techniques, and sustained the change. The talk will also discuss the various challenges at Columbia Sportswear as we learned to work differently on our DevOps journey. In addition, the talk will offer pragmatic advice to practitioners that want to start this highly rewarding journey. Our belief is that any enterprise can start a DevOps effort with a handful of believers and a modest budget.
+
+
+Specific techniques to be discussed: CHEF, Microsoft DSC, automation, Hashicorp Terraform, powershell, PowerCLI, vmware, Kanban boards, stand ups, infrastructure as code, ChatOps, 3 Tier implementations, SAP, BizTalk, Tomcat, Ant, Java.
+
Title:
+What Color is This? How (not) to be a jerk to the colorblind.
+
+
+
Description:
+
+
+1 in 12 men and 1 in 200 women worldwide are colorblind. Following these few quick tips can help make sure you are not inadvertently pissing them off.
+
Title:
+ Tips for selling Continuous Delivery and DevOps to your business (from a business person)
+
+
+
Description:
+
+Explaining why businesses should do continuous delivery (CD) can be hard. Businesses have roadmaps and plans and getting them to do development or operations work for a practice they don’t understand can be daunting. As a product manager I want to share with you how you can convince people like me (product managers) and others in your business why you should practice continuous delivery and build a DevOps culture.
+
Title:
+ Building a HIPAA compliant analytics platform in AWS
+
+
+
Description:
+
+This is a case study of the tooling we are using to build out a HIPAA-compliant analytics infrastructure on AWS (at Juice).
+
+We'll cover some gotchas we've discovered where automation gets tricky. AWS roles are awesome. IAM is deep and vast, and some services have particular ways that policies need to be written. KMS integrates with a lot of things but not always in the same ways.
+
+Our goals:
+
+
Manage all infrastructure as code with appropriate review processes
+
Allow quickly bootstrapping new infrastructure for enterprise clients
+
Allow projects to define their own infrastructure as much as possible
+
Encrypt everything
+
Deal with chickens and eggs
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-nashville/propose.md b/exampleSite/content/events/2016-nashville/propose.md
new file mode 100644
index 000000000..acce339ea
--- /dev/null
+++ b/exampleSite/content/events/2016-nashville/propose.md
@@ -0,0 +1,54 @@
++++
+City = "Nashville"
+Year = "2016"
+date = "2016-05-31T17:37:24-05:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+Our CFP has now ended. Thank you to all those who submitted!
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
+
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
+- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+- _original content_: We prefer talks not already presented at another event, especially another one in the local area or one available in recorded form.
+- _no third-party submissions_: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
+- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
+
+
+If your employer does not cover travel expenses you incur as a speaker at devopsdays Nashville, the conference can and will help; speakers receive free conference tickets and should not need to incur out-of-pocket travel expenses in order to participate.
diff --git a/exampleSite/content/events/2016-nashville/registration.md b/exampleSite/content/events/2016-nashville/registration.md
new file mode 100644
index 000000000..5ab2a1a22
--- /dev/null
+++ b/exampleSite/content/events/2016-nashville/registration.md
@@ -0,0 +1,12 @@
++++
+date = "2016-11-10T21:28:23-06:00"
+title = "Registration"
+type = "event"
+
+
++++
+
+
+
diff --git a/exampleSite/content/events/2016-nashville/sponsor.md b/exampleSite/content/events/2016-nashville/sponsor.md
new file mode 100644
index 000000000..6a50c65d6
--- /dev/null
+++ b/exampleSite/content/events/2016-nashville/sponsor.md
@@ -0,0 +1,170 @@
++++
+City = "Nashville"
+Year = "2016"
+date = "2016-05-21T21:10:04-05:00"
+title = "sponsor"
+type = "event"
+
++++
+
+Thank you for being here, and for considering sponsorship of Nashville's inaugural DevOpsDays! Sponsors are what makes community events like this possible. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}. Gold, Silver, and Bronze packages are detailed in our prospectus.
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+All sponsors get a full table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+If you're feeling especially generous, you can sponsor now by using any of the PayPal Links. Our team has a payment processor setup, being managed by ConferenceOps, and they are handling all financial logistics. We are happy to go through standard company finance processes if need be, and the ConferenceOps team is equipped to help manage that process once your company agrees to sponsorship.
+
+Please do not hesitate to reach out to us at {{< email_organizers >}} if you have any questions we can answer for you.
+
+
+
+## Sponsorship Levels
+
+### Gold Sponsorship ($5,000)
+
+
+
Details
+
Sponsor Now
+
+
+
+
+
4 tickets to the event
+
Logo on DevOpsDays BNA event website
+
Logo on all DevOpsDays email communication
+
1 minute pitch to full audience (including streaming audience)
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter devopsdaysbna >}}
diff --git a/exampleSite/content/events/2016-newyork/conduct.md b/exampleSite/content/events/2016-newyork/conduct.md
new file mode 100644
index 000000000..6d15f0ef3
--- /dev/null
+++ b/exampleSite/content/events/2016-newyork/conduct.md
@@ -0,0 +1,47 @@
++++
+City = "NewYork"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+
+* Local law enforcement: New York City Police - call 911
+* Sexual assault hotlines: NYC Alliance Against Sexual Assault: (212) 229-0345
+* Medical Emergency: Call 911
+* Local car services: Carmel Car and Limo Service (212) 666-6666; Dial 7 Car and Limo Service (212) 777-7777
+* Devopsdays NYC Organizers: [organizers-nyc-2016@devopsdays.org]
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-newyork/contact.md b/exampleSite/content/events/2016-newyork/contact.md
new file mode 100644
index 000000000..cdc8e4d1a
--- /dev/null
+++ b/exampleSite/content/events/2016-newyork/contact.md
@@ -0,0 +1,19 @@
++++
+City = "NewYork"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+### Our local team
+
+{{< list_organizers >}}
+
+### The core devopsdays organizer group
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-newyork/location.md b/exampleSite/content/events/2016-newyork/location.md
new file mode 100644
index 000000000..1c074703f
--- /dev/null
+++ b/exampleSite/content/events/2016-newyork/location.md
@@ -0,0 +1,34 @@
++++
+City = "NewYork"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
Conference Location
+
+
Microsoft Technology Center
+11 Times Square, 7th Floor
+(Between 41st & 42nd Streets on 8th Ave.)
+New York, NY, 10036
Title:
+Don't Believe the Data! Data VS Intuition in Decision Making
+
+
+
Description:
+
+
+We are inundated with more and more data everyday. From system notifications, to alerts, SMS, to push, we're constantly notified of things happening. Additionally we're having to take more and more data into consideration in order to make a proper decision. When working in a business critical alerting environment where decisions can cost 1,000's of dollars in a matter of minutes, how do you take in all the data from multiple alerts and balance that data against what your 'gut' tells you? We'll look at how our brains process information, go back in time to look at our primitive brains, and use some insights about our modern brains to help provide some guidance on how to make that critical decision under pressure!
+
Title:
+SRE: An incomplete guide to cultural Narnia
+
+
+
Description:
+
+
+SRE is a topic that most recently has become a popular discussion across many companies I have interacted with. What is SRE? Who are SRE's? How do we get it? I, just like everyone else have opinions around this topic. However there is a common ground between us all. SRE is not only about tooling and tech, but it is primarily a CULTURAL shift within companies. Now, just as a disclaimer these are just my opinions and experiences with building organizations like this and talking to other companies who have implemented or are implementing this. There is no prescription to building SRE. Everyone will find a way that this fits their company and build this according to their current operating model. Forcing this in because it's the new fad is not the best approach but that's up to you...
+
Title:
+Pioneers, Settlers, and Town Planners of Catan
+
+
+
Description:
+
+
+No critique of bimodal IT is complete without a board game analogy; here's mine. What if Wardley maps were hex-based? In the game Settlers of Catan, players vie for longest road, largest army, and resource monopolies on the game board. But when the Cities and Knights expansion is added to the game, suddenly there are multiple paths to victory. In Accidental Empires, Robert X. Cringely's history of Silicon Valley, he talks about commandos, infantry, and police. Simon Wardley talks about pioneers, settlers, and town planners. The concept remains the same: some innovate, others turn the innovations into products, and still others make products into commodities. This talk will explain mapping of the enterprise IT journey by way of board games, with whimsical asides.
+
+In this talk, we will see what happens when we stop looking at our infrastructure development as just a bundle of scripts and start looking at it as an application. We will go over various concepts in the programming world that can be carried into infrastructure development, including local development, test-driven code, modular applications, and static code analysis. Out of this talk, I hope to give operations engineers a new way to build out systems and feel more confident in the stability of their infrastructure.
+
Title:
+How Can You Scale It If You Don't Trust It?
+
+
+
Description:
+
+
+When you scale up an infrastructure it is crucial that you can trust you have the right resources in play, the right code deployed and that information can only flow in a secure manner. When you scale the organization, trust is required amongst all of the people responsible for coding, testing, deploying and managing the applications that power the business. With all of the chatter around scaling, you would think someone would have told you the key ingredient necessary for creating and fostering the required trust. Unfortunately it is very easy to get to the end of the diving board, right on the edge of jumping into something like a hybrid cloud deployment, before you realize you need to figure this out on your own. This talk can help. We'll discuss some concrete ways you can engineer trust into the system (complete with examples) you are building or operating so that it works well for cloud-native and legacy applications. By the end, you'll have a good idea of the decision/enforcement points you'll need to consider to be able to create a system (and an organization) that can scale.
+
+3AM sure does seem to get a lot of flack. It's the timeframe of choice for horror stories of ailing infrastructure, broken backups, and overly caffeinated engineers. How often does 3AM get thrown under the bus? This tongue-in-cheek lightning talk will take a look at all of the ways that 3AM seems to get referenced both inside and outside of of the technology industry. Graphs may be involved, but not willingly.
+
+Six months ago my team decided to take a RESTful web service (Conqueso) and rewrite it in a more scalable, auditable, highly-available fashion (propsd). As operations people, this was our first foray into delivering a software product together. We flailed spectacularly, learned a lot, and got a thank you note in the end. This is a three-part story about the things we learned. Each part covers a chunk of the development cycle: design, coding, maintenance. We discovered that patterns that work in operations can become anti-patterns in development. During the design phase we found that "Divide & Conquer" works for patching servers but doesn't translate well into writing technical specifications. While coding we saw that "Lone Wolves" are a perfect fit for fixing on-call issues but a poor fit for collaborative development. In maintenance mode we "Monitored All the Things", but no one knew because we forgot to send out status updates. Because propsd is open source, our journey and learning is lovingly documented by code, comments, and pull requests. So maybe other operations teams figuring out how to do development don't have to go through the same pain? At least, that's my hope by telling this story.
+
Title:
+The Benefit of A Systems Lens : Giving & Receiving Feedback using Systems Thinking
+
+
+
Description:
+
+
+Understanding feedback through a systems lens has advantages. This pure feedback loop is more accurate, it moves us away from needless judgement, and it enhances accountability just to name a few. By taking a step back and examining the feedback and data we receive in three different ways, we can understand it much clearer. Those ways are: 1) Are differences between the giver and receiver creating friction for the feedback? 2) Is the feedback partly related to the differing roles between giver and receiver as it relates to the common "system"? 3) Are processes, policies, physical environment, or other factors within the system reinforcing problems with the feedback? Allowing ourselves to view feedback from a "Systems Thinking" model, we can begin to look for patterns, understand the feedback loop with more accuracy, and identify contributing factors to both failure and success.This quick (IGNITE-style) talk will discuss feedback from a "Systems Thinking" perspective.
+
Title:
+Things I learned about engineering from being a chef
+
+
+
Description:
+
+
+Although the jobs of software engineer and chef are vastly different, there are a lot of interesting similarities. I'll share a few valuable lessons on tools, technique, burnout and camaraderie that I learned while cooking in some of the world's best restaurants and how they apply to working in tech.
+
Title:
+More Than Hair, Nails & Makeup: Understanding how user experience design addresses unconscious biases in technology among young women of color
+
+
+
Description:
+
+
+How do young women of color see themselves in the products they are using in their everyday lives?" "What information should be included in technology tools that accurately reflect the cultural roots of girls of color?" "How can more young women of color interested in technology create a voice for the consumer?" These critical questions and several others will be addressed in this workshop that invites students to identify how social justice principles plays a role in technology advancement. Specifically, this session will expose students to the role of unconscious bias and how certain beliefs and assumptions influence their relationship with technological products and experiences. User experience is one approach to address issues of unconscious bias often times found in technology. User experience, a field rooted in diverse social science fields such as sociology and psychology, assesses the interaction and perceptions that people have when using a product of service. In this session, attendees will be introduced and be able to engage in practical application in the following UX fundamentals: user research and user design. Participants will learn how to understand and incorporate the needs of groups with detailed research and design a process that allows users to interact with a technological product and experience from moment to moment. Participants will be able to identify user experience (UX) design to overcome challenges in unconscious biases in technology both from an entrepreneurial and consumer perspective. Lessons learned and long-term implications for this approach will also be addressed.
+
+This talk will narrate my personal journey as a stay-at-home-cupcake-baking mom learning to code, rejoining the workforce, and finding a passion in devops engineering.
+
+In the past year Google, the NSA, and NIST have urged developers and theorists to get more serious about quantum computing. What are quantum computers, do they exist, and if so, how do we keep stuff secret from them? How does this change TLS/SSL? Also covering lots more benefits of researching post-quantum encryption today.
+
Title:
+Blue Grass in a Brown Field: Building Awesome People and a Culture of Learning
+
+
+
Description:
+
+
+Wouldn't we all want to work at an organization that values and rewards the contribution of knowledge workers? Wouldn't it be easier if our current organizations prioritized learning, experimentation, and collaboration as key success factors? Well...yes! But we must deal with the realities in front of us, not those wish to be. Even after ample research substantiating the benefits of organizations moving towards more autonomy, faster feedback and a culture of relentless learning, many orgs still hold on to the notion of power, while putting on a front of change and collaboration.
+
Title:
+Beyond Testing: Application Security in the Age of DevOps
+
+
+
Description:
+
+
+It's a common question from security practitioners in any development practice: how do I secure the code my development team is building? The challenge of answering this question in DevOps: the time between developer check-in and deployment is measured in minutes, not days or weeks. But focusing only on speed without understanding the goals of DevOps can lead to undesirable trade-offs, like unnecessarily shutting down the build pipeline. In this presentation, we establish five principles for securing DevOps development (Automate Security In, Integrate to Fail Quickly, No False Alarms, Build Security Champions, Keep Operational Visibility). We review the state of the art of application security practices and talk about ways to leverage the principles and practices of DevOps, such as quick feedback loops and feature toggling, to create more secure code. And we look at organizational, process, and technology innovations to secure applications in ways that incorporate, but go beyond, testing for vulnerabilities, by looking at what developers can do before checking in code and what application security looks like in production.
+
Title:
+Moving Fast Together: Test-Driven Infrastructure
+
+
+
Description:
+
+
+The DevOps world is all about speed. We ship fast, and we’re proud of that. But with our infrastructure changing every day, and the complexity, requirements, and size of projects getting greater, it has become challenging and time-consuming to meet the quality expectations. In order to work together and collaborate effectively in a high velocity environment, uncertainty and complexity needs to be reduced. This talk will cover a devops workflow that helps establish trust in your software development and release process.
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-newyork/propose.md b/exampleSite/content/events/2016-newyork/propose.md
new file mode 100644
index 000000000..152bb5004
--- /dev/null
+++ b/exampleSite/content/events/2016-newyork/propose.md
@@ -0,0 +1,44 @@
++++
+City = "NewYork"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+{{< cfp_dates >}}
+
+
diff --git a/exampleSite/content/events/2016-newyork/registration.md b/exampleSite/content/events/2016-newyork/registration.md
new file mode 100644
index 000000000..1b05239c1
--- /dev/null
+++ b/exampleSite/content/events/2016-newyork/registration.md
@@ -0,0 +1,18 @@
++++
+City = "NewYork"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+Registration info will be provided soon
+
+
diff --git a/exampleSite/content/events/2016-newyork/speakers.md b/exampleSite/content/events/2016-newyork/speakers.md
new file mode 100644
index 000000000..4639f6720
--- /dev/null
+++ b/exampleSite/content/events/2016-newyork/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-09-02T12:54:57-04:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-newyork/sponsor.md b/exampleSite/content/events/2016-newyork/sponsor.md
new file mode 100644
index 000000000..25905bb8c
--- /dev/null
+++ b/exampleSite/content/events/2016-newyork/sponsor.md
@@ -0,0 +1,94 @@
++++
+City = "NewYork"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this community event. If you are interested in sponsoring, please check out our prospectus below and drop us an email.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms. Gold sponsorships are limited due to venue space and will be handled on a first come, first serve basis. As of 6 July 2016 only Silver and Bronze sponsorships remain.
+
+
+
+
+
+
+
Packages
+
Bronze 1000 USD
+
Silver 2500 USD
+
Gold 5000 USD
+
+
+
+
+
[Email us](mailto:organizers-nyc-2016@devopsdays.org?subject=DevOpsDays New York 2016 Sponsorship) for availability and payment
+
+
+
Included tickets
+
1
+
2
+
3
+
+
+
Logo on event website
+
+
+
+
+
+
Logo on shared slide, rotating during breaks
+
+
+
+
+
+
Logo on all email communication
+
+
+
+
+
+
Logo on its own slide, rotating during breaks
+
+
+
+
+
+
Mention by MC at kickoff and close
+
+
+
+
+
+
1 minute pitch to full audience (including streaming audience)
+
+
+
+
+
+
Shared table for swag
+
+
+
+
+
+
Sponsor table space
+
+
+
+
+
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, send us an email.
+
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter devopsdaysNYC >}}
diff --git a/exampleSite/content/events/2016-newzealand/conduct.md b/exampleSite/content/events/2016-newzealand/conduct.md
new file mode 100644
index 000000000..477644e5f
--- /dev/null
+++ b/exampleSite/content/events/2016-newzealand/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-07T09:42:16-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-newzealand/contact.md b/exampleSite/content/events/2016-newzealand/contact.md
new file mode 100644
index 000000000..bbde2f7c7
--- /dev/null
+++ b/exampleSite/content/events/2016-newzealand/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-07T09:42:16-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-newzealand/location.md b/exampleSite/content/events/2016-newzealand/location.md
new file mode 100644
index 000000000..0aaddade2
--- /dev/null
+++ b/exampleSite/content/events/2016-newzealand/location.md
@@ -0,0 +1,12 @@
++++
+date = "2016-05-07T09:42:16-05:00"
+title = "location"
+type = "event"
+
++++
+
+### DevOpsDays Middle Earth will be held at the BNZ Harbour Quays
+
+
+
+
diff --git a/exampleSite/content/events/2016-newzealand/logo-wide.png b/exampleSite/content/events/2016-newzealand/logo-wide.png
new file mode 100644
index 000000000..6899545d3
Binary files /dev/null and b/exampleSite/content/events/2016-newzealand/logo-wide.png differ
diff --git a/exampleSite/content/events/2016-newzealand/logo.png b/exampleSite/content/events/2016-newzealand/logo.png
new file mode 100644
index 000000000..5b725357e
Binary files /dev/null and b/exampleSite/content/events/2016-newzealand/logo.png differ
diff --git a/exampleSite/content/events/2016-newzealand/program.md b/exampleSite/content/events/2016-newzealand/program.md
new file mode 100644
index 000000000..44a7af483
--- /dev/null
+++ b/exampleSite/content/events/2016-newzealand/program.md
@@ -0,0 +1,429 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
Title:
+Health is hard: A story about making healthcare less hard, and faster!
+
+
+
Description:
+
+
Can an elephant change its spots?
+
+
Does the early bird really gather no moss?
+
+
And what about that rolling stone, should we be trying to force it to drink?
+
+
Be the change you wish to see in the world
+
+
This is a talk about the elephants in the room (in my room, not this room). Its about charting the path from waterfall to agile scrum - and doing it properly and sustainably. Its about fostering a sense of aspirational desire to be better than we were yesterday - and making that desire scale.
+
+
What has this got to do with Dev Ops?
+
+
DevOps, for me, is about empathy. Its about working together rather than in competition, its about choosing something to do, be it integrating, delivering, learning, improving or whatever else you want, and doing it as quickly as humanly possible. Its about creating feedback loops in your code and in your people that lead you to the result you want. For the healthcare industry, it can be quite a sell.
+
+
I'll share my experiences building those feedback loops and engaging development and operations practices that have a long history of mutual antagonism. Learn about how I healed the rift between them, and turned a page so to speak. After all, who must do the hard things? The new dog. The old one couldnt learn tricks. And you.
Title:
+The story of a performance outage, and how we could have prevented it
+
+
+
Description:
+
+
+Dealing outages in production environments can be fraught with stress & tension, especially when your business users or customers are impacted.
+
+
Regardless of how fast you can release features into your production environments, unfortunately we caeterlikely that you will have to deal with a business impacting outage at some point. Having resilient mechanisms, and procedures in place means that 90% of these potential issues can be caught before they cause you true headaches, but in a true worst case scenario it's important to be able to quickly diagnose issues, and restore services.
+
+
+
Let me take you through a business impacting performance outage and share with you what happened, how we found it the root cause and how we could have found it earlier.
You're employed to get things done. So is everyone else in the company. But despite being "on the same team", everyone has their own idea of priorities, urgent tasks, and tasks they consider a waste of time. Different teams and departments have different goals, and when they clash, it slows everyone down and can be frustrating and demotivating. So what's the solution? How can you convince everyone to just let you do your job?
+
+
In this talk, I'll share some practical changes you can make to help fix this problem. Backed up by both research and personal experience, these tips will help you to avoid frustrations and focus on what you're employed to do. We'll discuss topics like wasteful meetings, interruptions, unplanned work, frequently changing priorities, and menial tasks. From small changes in your own team, to ways to influence large cultural changes, there's something here for everyone.
Title:
+Powering stuff.co.nz with DevOps goodness
+
+
+
Description:
+
+
+A large site like www.stuff.co.nz has piles of systems and technologies in use. In this talk we try to give you a taster of the various technologies we use and their capabilities. What are we doing with Varnish? Lambda? Newrelic? AWS? Codeship? The goal of this is to give you some ideas of what goes into a large site from a technology perspective and how these technologies are useful tools for a DevOps toolkit at scale.
+
Title:
+What were learning about burnout and how a DevOps culture can help
+
+
+
Description:
+
+
One of the most overlooked advantages of converting to a DevOps culture can be the reduction of stress. This could be due to sharing the load as a whole team, the feeling of joint ownership in solving a business problem, or many other things.
+
+
If youre asked to support somebody elses application without any insight to how it was built and what problems its trying to solve youre likely to experience more than a little stress. The same is true if youve toiled away creating the perfect application only to see it deployed in a way that makes it unable to perform.
+
+
The combination of stress and burnout is perhaps the biggest health threat in our industry. In fact, recent research has found that burnoutand the related concept of vital exhaustionincreases your risk of cardiovascular disease as much as body mass index, smoking and lipid levels. Unfortunately there are also well-known stories of burnout-related suicides in our industry, making this literally a life and death issue.
+
+
If that isnt reason enough to address the issue, we also know from the State of DevOps survey that the #1 indicator of company success is job satisfaction.
+
+
In this talk Ken will go over some of the leading research in the area of burnout. Well talk about some of the more common causes of burnout as identified by clinical research and talk about how you can learn from organizations with solid DevOps cultural practices to help alleviate them.
Devops is about changing technical culture. But technical culture isnt created in a vacuum it's nurtured and reinforced by the broader organisational culture our tech orgs are part of.
+
+
That culture comes from people our artifacts, beliefs, and assumptions. Unless we deepen our people's skills, knowledge, and experience, we'll get the culture change we deserve.
+
+
What does technical culture change look like, and how does it survive? And why are people the hardest but most important piece of the puzzle to change?
Title:
+Automatic discovery of service metadata for systems at scale.
+
+
+
Description:
+
+
Documentation is a painful yet necessary artifact of any software system. In a large microservices environment like Spotifys, where the number of services and teams grows quickly, automation and standardization of documentation is crucial.
+
+
However, maintaining any kind of quality documentation at this scale becomes a burden easily: it is a boring task, and an artifact that usually resides in a different place other than your code.
+
+
Discover how we solved this issue by including a metadata module in our main microservices framework, Apollo. Allowing automatic discovery of existing endpoints, service configuration, outgoing and incoming calls, and deployment information at runtime. All this information, is visualized in our systems management centralized tool. Making our systems documentation easy to maintain and ensuring we always display up-to-date service metadata.
+
+
We want you to know about our open source tool, Apollo and how we solved this common, painful issue with it.
DevOps, the term came from a need to classify a newer breed of developers in existing organisations, developers that refused to agree to an us than them mentality, that refused to fracture the tech teams of organisations based on if you worked on servers and infrastructure (Ops) vs if you wrote the client facing applications. With the birth of mainstream SaaS and Product Teams we had to tear down these walls, we had to make a stand.
+
+
This is the end of the beginning, were moving in to a new age of developers, were all devops now.
In **Movio** (NZ Hi-tech Awards 2016 Winners) we love **microservices in Docker**. But when you have a few hundreds of them how do you effectively manage them? How do you update them with zero downtime? How do you make them HA and scale them? How do you monitor and troubleshoot services running in a cluster? In this presentation you can see a real world example how to achieve all that with **open source cluster** management tool called **Kubernetes**. Apart from microservices I will also show you how to deploy tools like **Elasticsearch, Kafka, and Cassandra** in the same cluster and benefit from the centralised features.
DevOps is something we are, not something we do! Culture plays a significant role in our ability to continuously improve both ourselves and others. Creating a Strategy based on Culture as experienced in Deliberately Developmental Organisations (DDOs) provides an environment for continual growth.
+
+
People are encouraged to expose their 'backhands', seek support and help and expect to help others work on their 'backhands' every day. Growth does not compete with business goals it is seen as a vital contributor to the business objectives. Why is Culture so important? How does a focus on Culture as Strategy provide an environment in which businesses can thrive and even exceed business expectations.
Title:
+Health is hard: A story about making healthcare less hard, and faster!
+
+
+
Description:
+
+
Can an elephant change its spots?
+
+
Does the early bird really gather no moss?
+
+
And what about that rolling stone, should we be trying to force it to drink?
+
+
Be the change you wish to see in the world
+
+
This is a talk about the elephants in the room (in my room, not this room). Its about charting the path from waterfall to agile scrum - and doing it properly and sustainably. Its about fostering a sense of aspirational desire to be better than we were yesterday - and making that desire scale.
+
+
What has this got to do with Dev Ops?
+
+
DevOps, for me, is about empathy. Its about working together rather than in competition, its about choosing something to do, be it integrating, delivering, learning, improving or whatever else you want, and doing it as quickly as humanly possible. Its about creating feedback loops in your code and in your people that lead you to the result you want. For the healthcare industry, it can be quite a sell.
+
+
Ill share my experiences building those feedback loops and engaging development and operations practices that have a long history of mutual antagonism. Learn about how I healed the rift between them, and turned a page so to speak. After all, who must do the hard things? The new dog. The old one couldnt learn tricks. And you.
+
+
+
+
diff --git a/exampleSite/content/events/2016-newzealand/speakers.md b/exampleSite/content/events/2016-newzealand/speakers.md
new file mode 100644
index 000000000..847dccae0
--- /dev/null
+++ b/exampleSite/content/events/2016-newzealand/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-09-28T07:28:18+13:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-newzealand/sponsor.md b/exampleSite/content/events/2016-newzealand/sponsor.md
new file mode 100644
index 000000000..29050ce01
--- /dev/null
+++ b/exampleSite/content/events/2016-newzealand/sponsor.md
@@ -0,0 +1,66 @@
++++
+date = "2016-05-07T09:42:16-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+Additional à la carte sponsorships are still available:
+
+* coffee ($2.5k + GST) - 2 slots available - signage by the coffee displays with your logo throughout the day
+* lunch ($2k + GST) - 2 slots available - signage by the lunch tables and in the eating area with your logo during lunch
+* video ($5k + GST) - 1 slot available - your logo on all post produced videos, logo on website and dedicated slide during breaks, mentions on social media and by MC, opportunity to include something in the swag bag
+
+## Sponsorship Prospectus
+
+DevOps in New Zealand is hitting a critical mass, reaching all aspects of the technology space. From banking institutions to government departments, to SaaS providers to disruptive start ups - DevOps is the new black.
+
+Coming to Wellington for the first time, DevOpsDays brings an opportunity to expose your brand to the DevOps community across NZ - whether you're looking for talent, wanting to extend the reach of your brand or just show the latest and greatest wares. Sponsoring DevOpsDays in Wellington provides a unique occasion to interact with technology professionals and gives your representatives a chance to connect with participants.
+
+DevOpsDays Wellington will be held at BNZ Harbour Quays on the 29th & 30th September and we are expecting about 170 participants. Support DevOpsDays Wellington now to garner the attention you’ll receive for being an early sponsor.
+
+Sponsors are much appreciated for their financial assistance. Sponsorship is the main source of funding for the conference, with registration fees kept low to encourage broad community participation.
+
+Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session, but this is not 'that kind of conference' and heavy marketing will probably work against you when trying to make a good impression on the attendees. The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+[Our Sponsorship prospectus can be downloaded here](https://drive.google.com/open?id=0B0Fp3aq_FEwsQ3dOOFB1N0MyMEk)
+
+
+
+
+These may be purchased in addition to (or in lieu of) the sponsorships in the prospectus.
+
+
+
diff --git a/exampleSite/content/events/2016-newzealand/welcome.md b/exampleSite/content/events/2016-newzealand/welcome.md
new file mode 100644
index 000000000..47289c707
--- /dev/null
+++ b/exampleSite/content/events/2016-newzealand/welcome.md
@@ -0,0 +1,93 @@
++++
+date = "2016-05-07T09:42:16-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-newzealand"]
+
++++
+
+## DevOpsDays Middle Earth is in Wellington
+
+**It will be hosted at {{< event_location>}} on {{< event_start >}} - {{< event_end >}}**
+
+Sorry, the conference is now SOLD OUT, since the venue is limited to 175 attendees. A wait list is in operation for unallocated or returned tickets.
+
+If youre realising right now that you cannot attend, please let us know! There is a long waiting list. Were happy to give you a full refund or change the name/email on your ticket if you contact us by 11:59PM NZT on Tuesday 27 September.
+
+
+
+
+
+
+
+
+
+DevOps is all about Continuous Improvement - but what is meant by this? What are we improving? Why do we want to continuously improve?
+
+How do we continuously improve, when we have to deal with incumbent technologies, increased learning curves and ever-increasing business demand for new features?
+
+Technology is continuously changing, and the pace is only accelerating; there is no evidence of a plateau or slow-down any time soon. Therefore, there are new opportunities emerging all the time - activities that were previously done manually are now automated, and this automation is increasing in sophistication.
+
+So, is improvement then all about tools and technologies? Or the people (as individuals and teams) that use them? Or is it about organisations having the right investment in processes that support continuous improvement?
+
+At the 2016 DevOpsDays NZ conference we hope to cover all these aspects and answer the 'what, why and how' of improvement in any organisation that uses IT as part of its business.
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+ Register
+
+
+ At 175 attendees the conference is now sold out
+
+
+
+
+
+ Program
+
+
+ View our provisional {{< event_link page="program" text="program." >}} (session and speaker details to follow)
+
+
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+
CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-ohio/contact.md b/exampleSite/content/events/2016-ohio/contact.md
new file mode 100644
index 000000000..c87868570
--- /dev/null
+++ b/exampleSite/content/events/2016-ohio/contact.md
@@ -0,0 +1,32 @@
++++
+City = ""
+Year = ""
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+draft = false
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+Our local team
+
+Active
+
+{{< list_organizers >}}
+
+Historic
+
+
+
+Shadowbox Live! is located at 503 S Front St #260, Columbus, OH 43215.
+
+
+
+
+
+
+DevOpsDays Ohio will be paying for parking this year at the Grange garage located at 600 South Front St in the form of a parking voucher which will be provided during checkin. Other parking locations are available in the area but will not be paid for by the event.
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-ohio/logo.png b/exampleSite/content/events/2016-ohio/logo.png
new file mode 100644
index 000000000..64a3ab3a0
Binary files /dev/null and b/exampleSite/content/events/2016-ohio/logo.png differ
diff --git a/exampleSite/content/events/2016-ohio/program.md b/exampleSite/content/events/2016-ohio/program.md
new file mode 100644
index 000000000..04ad3b7e2
--- /dev/null
+++ b/exampleSite/content/events/2016-ohio/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
++++
+
+
+
+
+ If you are new to the Open Space concept you may want to read some more details.
+
+ This schedule is subject to change.
+
+
+
+
+
+
+
The Schedule
+
+
+
+
+
+
+
+
Day 1
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
Title: Reducing the burden of the OnCall rotation
+
+
+
+
Description:
+
+
It's no secret, on-call responsibilities generally suck. No one's happy to be "holding the pager" and in the Ops world, that can be a real problem. The additional, unplanned, after-hours work leads to faster burnout among Engineers. By taking real steps to shift our perspectives of OnCall, we can begin to reverse the problem.
Title: Lessons from The Phoenix Project in 5 minutes
+
+
+
+
+The Phoenix Project has been an introduction to Devops for many and is one of the books we all recommend for newcomers. We will quickly cover the main takeaways of the book in a quick five-minute setting.
It can be discouraging to implement technology in large enterprises. In financial services it's only compounded with legacy regulations and compliance. Add to that the risk, audit and internal security groups that want to be extremely proactive with process to ensure the company's safety. With all of that protection, much gets lost in translation when executing. Buildup of manual workflow, fear of change to processes that are proven to work, and the confusion with the number of communication points create a lengthy error-prone delivery process. Enterprises can be risk adverse adopting new things; this impacts the culture of engineering required to deliver reliable software quickly. At KeyBank, we have over-time created these issues with the standard support of legacy software, acquired complexity, and a continued focus on cost optimization. Luckily Key has great leaders that understand software delivery is a critical strength required to excel and technology is an important focus area
We just made all of our infrastructure into code, hooray! Wait….more code? But code goes bad, and is hard to write in a way we can maintain! Whether your team uses Puppet, Chef, Ansible, or something else in the Configuration Management space, you may have noticed that your code has a very short shelf-life before it starts causing harm by being out of date.
+
+
As a veteran from a hard to maintain language (Perl) I'll share the practices that affect maintainability, and insights into coding in the Operations domain. I learned a lot about the pressures on a codebase that make it harder or easier to maintain. As I moved into DevOps and configuration Management, a lot of those lessons came with me; but I saw the pressures greatly amplified, and the software engineering tools much weaker. I'll share tips on what to avoid entirely, what practices to invest in, and when to burn it all down and start over.
+
+
+
+
+
+
+
Title: DevOps Jargon: Your goat antifragiled my snowflake!
+
+
+
+
Description:
+
+
Are you a cow, a goat, a canary, or a unicorn? Are running K8S? Who the heck is Brent? Find out!
+
+
Welcome to DevOps, where we are all about breaking down walls. But, we've created a private dialect, full of familiar words with unfamiliar meanings, and in-jokes upon in-jokes. Many newcomers wish there was a glossary for the movement. Time to be inclusive!
+
+
In this fun session, we'll go over some of the more unintuitive terms (being a goat is a good thing!) and the backstories behind them.
Title: Humans are terrible compilers: A User's Guide
+
+
+
+
+
Description:
+
+
Humans are well known for their ability to be adaptable, flexible, and improvise as needed. However, they are often used as very oddly behaved compilers of written documents - run books for services, legal agreements, and pull requests / code reviews are a few examples.
+
+
This talk will cover several known issues with the current release of the Human 1.0 compiler, practical workarounds for these issues than anyone can use, and ways to debug when everything goes wrong.
Title: Introduction to Serverless Architecture
+
+
+
+
Description:
+
+
Are you worried about the scalability and availability of your application? Do you find you or your team spending a lot of time deploying and managing servers? With buzzwords like “Serverless”, “BaaS”, “FaaS”, and “cloud" getting thrown around almost interchangeably it’s easy to have some confusion on what “Serverless" really means. In this talk we’ll discuss these terms and show how a Serverless Architecture can help solve some of your problems. Lastly we’ll go through an example using AWS services (specifically Lambada and API Gateway).
Title: What I learned about engineering from being a chef
+
+
+
+
Description:
+
+
Although the jobs of software engineer and chef are vastly different, there are a lot of interesting similarities. I’ll share a few valuable lessons that I learned while cooking in some of the world’s best restaurants and how they apply to working in tech.
Title: You Don't Belong Here: Dealing with Impostor Syndrome
+
+
+
+
Description:
+
+
An estimated 70% of people will experience Impostor Syndrome at some point in their lives, despite having objective evidence of success in their field, sometimes in copious amounts. People in all fields of work experience pervasive psychological distress, believing that they are intellectual frauds and fearing being recognized as impostors. The objective of this presentation is to provide relief to those suffering from Impostor Syndrome by analyzing possible sources of this distress, exploring tactics to overcome these feelings, and recognizing that we have a community of peers sharing the same experience. Through scientific research and personal exploration, we'll dig deep into the root causes of this feeling and identify paths to successfully working through moments of Impostorism.
Title: The answer to the “where do we start” question
+
+
+
+
Description:
+
+
Where do we start? This is by far the question I’m asked the most when talking to people about implementing continuous delivery. Unlike other types of long journeys, the answer is rarely “at the beginning”.
+
+
One of the best ways to determine the best place to start is to figure out where you’re wasting the most resources, and one of the best ways to do that is to create a value stream map.
+
+
We’ll go over what a value stream map is, how you can create one, and how it can help you answer some important questions about your business. Questions like “where do we start?”.
Title: Getting Away from it All - Living an Unplugged Life as an IT
+
+
+
+
Description:
+
+
Most IT professionals spend some of their weekend on work stuff. Check email, work on a design, do some research, or on a "fun" project.
+
+
After 25 yrs in IT I finally realized that rarely does this help me get ahead. Mostly it makes me feel crushed, rushed, and stretched to the limit.
+
+
Not too long ago I started disconnecting for one day every week - totally unplugging. Not just me, but my whole family. Unsurprisingly, doing this did not drive us to the brink of madness.
With emergence of DevOps approach to application development, deployment and management developers get more and more involved in day-to-day system operations. Lately, there has been a popular point of view that developers should be included in oncall rotation on equal grounds with sys admins. While I don't fully subscribe to that mentality, there are certain processes that must be implemented by every organization to get developers involved in production operation of the software they built. In this talk I'll walk through different aspects of operational oncall responsibilities and discuss ways in which developers should (and should not) be involved in operation of production systems.
Oh, East is East, and West is West, and never the twain shall meet,
+ Till Earth and Sky stand presently at God’s great Judgment Seat;
+
+
But there is neither East nor West, Border, nor Breed, nor Birth,
+
+
When two strong men stand face to face, tho’ they come from the ends
+ of the earth! -- Kipling
+
+
ITIL has a bad name among Agile and DevOps practitioners.
+ But once you strip away the ceremony and the high priced consultants,
+ ITIL outlines a series of best practices for IT Service Management
+ (ITSM), such as change management, configuration management, problem
+ management, and process improvement. While these
+ are good ideas, conflict arises in the implementation and the
+ terminology used -- consultants charge by the syllable. Maybe it's all
+ the "managers", each with their own silo and layers of complexity.
+
+
Despite FUD and mis-communication, the two camps do not have to be enemies.
+
+
There is a common ground where Agile and ITIL can meet and work together as brothers in arms.
Title: Community, the secret ingredient for DevOps
+
+
+
+
Description:
+
+
Successful DevOps requires collaboration. Collaboration improves when you grow from colleagues to a community.
+
+
This is an exploration of the community-side of DevOps. How do you participate in the larger DevOps community? How do you build an “internal” community around DevOps practices? Open source?! how do I even start with contributing to the community?
+
+
Hear about some successful teams are incorporating lessons learned from open source, DevOps, and other communities. Leave with some ideas of things to try in your own environment.
+Trendy architectures often leave much to be desired in the way of operational visibility. Containers, unikernels, serverless - all of these promise DevOps nirvana but their promises often fall far short when it comes to operational needs in production. Chanting "cattle not pets" every time we shoot a cow in the head will ruin us if the herd is sick and we're wearing a blindfold. How do we regain insight and deep visibility into our brave new containerized world?
Software development is hard to boil down to one word. Software development takes TACT (trust, accountability, communication, and time). Come explore the tools and techniques that can help create more trust, more accountability, better communication, and respect for everyone's time. Whether your using tools and techniques, such as Git blame, "death by meeting", GTD or Pomodoro (tomato) time. Let's talk about why software development and DevOPs take TACT!
Automation is an obvious component to successful DevOps but often times it is implemented in pockets within a team or within a workflow. This session takes a look at some of the obstacles and solutions for full automation across the life cycle; identifying gaps and how to root out the resistance.
+
+
+
+
diff --git a/exampleSite/content/events/2016-ohio/proposals.md b/exampleSite/content/events/2016-ohio/proposals.md
new file mode 100644
index 000000000..466338c90
--- /dev/null
+++ b/exampleSite/content/events/2016-ohio/proposals.md
@@ -0,0 +1,13 @@
++++
+date = "2016-03-06T21:28:14-06:00"
+title = "DevOpsDays Ohio 2016 - Proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-ohio/propose.md b/exampleSite/content/events/2016-ohio/propose.md
new file mode 100644
index 000000000..71348fdab
--- /dev/null
+++ b/exampleSite/content/events/2016-ohio/propose.md
@@ -0,0 +1,38 @@
++++
+City = ""
+Year = ""
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+draft = false
++++
+
+ {{< cfp_dates >}}
+
+To propose, click here.
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal:Click here
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-ohio/speakers.md b/exampleSite/content/events/2016-ohio/speakers.md
new file mode 100644
index 000000000..4639f6720
--- /dev/null
+++ b/exampleSite/content/events/2016-ohio/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-09-02T12:54:57-04:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-ohio/sponsor.md b/exampleSite/content/events/2016-ohio/sponsor.md
new file mode 100644
index 000000000..4c92599ed
--- /dev/null
+++ b/exampleSite/content/events/2016-ohio/sponsor.md
@@ -0,0 +1,22 @@
++++
+City = ""
+Year = ""
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+draft = false
+
+
++++
+
+We greatly value sponsors for this open event.
+
+
+Sponsorship Prospectus.
+
+
+If you are interested in sponsoring this event in any way, please email us: {{< email_organizers >}}.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
diff --git a/exampleSite/content/events/2016-ohio/welcome.md b/exampleSite/content/events/2016-ohio/welcome.md
new file mode 100644
index 000000000..ac6171d6e
--- /dev/null
+++ b/exampleSite/content/events/2016-ohio/welcome.md
@@ -0,0 +1,96 @@
++++
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+City = "ohio"
+Year = "2016"
+aliases = ["/events/2016-Ohio"]
+draft = false
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+ {{< event_logo >}}
+
+
+Thank you to all of the attendees, sponsors, and Shadowbox Live for making DevOps Days Ohio 2016 a great success!
+
+You can now view all the wonderful presentations here
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter DevOpsDaysOhio >}}
+
+Tweets by DevOpsDaysOhio
diff --git a/exampleSite/content/events/2016-oslo/conduct.md b/exampleSite/content/events/2016-oslo/conduct.md
new file mode 100644
index 000000000..c8286f55f
--- /dev/null
+++ b/exampleSite/content/events/2016-oslo/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-oslo/contact.md b/exampleSite/content/events/2016-oslo/contact.md
new file mode 100644
index 000000000..6a0063efc
--- /dev/null
+++ b/exampleSite/content/events/2016-oslo/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-oslo/location.md b/exampleSite/content/events/2016-oslo/location.md
new file mode 100644
index 000000000..71b3db60f
--- /dev/null
+++ b/exampleSite/content/events/2016-oslo/location.md
@@ -0,0 +1,25 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "location"
+type = "event"
+
++++
+
+
Location
+
+Gamle Museet /The Old Museum is centrally located in Dronningensgate 4. It is close to public communication with all bus and tram lines in the immediate vicinity and 5 minute walk to Oslo central station. A parking garage is located within a two minute walk from the venue.
+
+
+
+
+
+
Accommodation
+Thon Hotel Oslo Panorama offer discounted rates for attendees and is just a two minute walk from the conference.
+
+
DevOps is about changing mindsets and organisations. It’s about making IT change with the business. Not being a road block to change. But if you try to fix the symptoms and not the root causes the results are just temporary at best. And the real issue is rarely technology.
+
+
I’ll take you through some of the organisational constraints, the human factors and some common anti-patterns. Recognisable and avoidable.
+
+
This talk will mostly be about the soft sides of DevOps. Technology is what I love to do. But using it to it’s full potential requires getting the most out of humans and organisations.
How to choose the right tools for the job, when there are many of them available?
+
+
Which criteria should you pay attention when deciding on tools to become productive? This ignite talk will not try to sell any product, but it will illustrate how to identify “red flags” (aka YAGNI principle) in tools and products used for various DevOps tasks.
Title:
+Communication in DevOps: A Fairy Tale or a Horror Story?
+
+
+
Abstract:
+
+
Even though agile actively seeks collaboration from all its
+stakeholders, most agile projects did not extend themselves toward the
+operations people. DevOps came to bridge that gap. DevOps aligns business
+requirements with IT performance, with the goal of adopting practices that
+allow a quick flow of changes to a production environment, while
+maintaining a high level of stability, reliability, and performance in
+these systems. DevOps improves the work through a collection of principles
+and practices, centered around close collaboration between Development and
+Operations personnel. However, both sides have paid little, to none at
+all, attention to issues faced by each other. When it comes down to sit
+together and plan a solution to better meet customer demand, the
+communication between Dev and Ops can go from a fairy tale for a horror
+story with a blink of an eye. Many variables can affect this
+communication, e.g., depending on the size of the team, people involved in
+the conversation, how mature people are, location of the teams, means of
+communication, etc. The main goal of our presentation is to shed some
+lights on the perceptions that different teams have on communication in
+DevOps, highlighting some of the bottlenecks that were brought to our
+attention and share a list of some practices que might help your team to
+achieve greatness together.
Title:
+How we built the Node.js Foundation with Open Open Source
+
+
+
Abstract:
+
+
Rewind to early 2013. Node.js v0.10 had just been released - this is the golden days of Node.js... and the beginning of the end. The BDFL-model and project stewardship have severely limited contribution (especially from larger corporations), and the lack of communication and transparency around decision making is making life as contributor to Node.js core intolerable. Stagnation of technical progress was unavoidable. Was Node.js doomed to fail before it could take off?
+
+
You probably know by now that Node.js did not fail, adoption and usage of Node.js has continued to grow each year. But how did this happen when the project was heading to a certain doom? In this talk I will use the backstory of how Node.js is built around the notion of openness and collaboration - known as Open Open Source - to mobilise the community (more than 450 members in the GitHub organisation) and activate more contributors! I also talk about how the Node.js Foundation is structured and how all the bits and pieces works on building Node.js - one way or another.
+
+
The Open Open Source mantra:
+
+
Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.
Title:
+Complaining is not a strategy. (How to make things better even if you're not the boss.)
+
+
+
Abstract:
+
+
A lot of people see ways that their organizations can be better. Maybe they want to spend more time on technical debt, maybe they want to adopt more agile type processes, maybe they want to see more of a DevOps culture. There are tonnes of kinds of improvements that can be made in a typical organization and developers are usually really good at spotting them. However, we are typically not that good about bringing them about. I'll share some tactics that have a good chance of working, as well as some that are sure-fire non-starters. Attendees will leave with some experience-proven strategies for effecting meaningful changes in their organizations.
Title:
+You Don't Belong Here: Dealing with Impostor Syndrome
+
+
+
Abstract:
+
+
An estimated 70% of people will experience Impostor Syndrome at some point in their lives, despite having objective evidence of success in their field, sometimes in copious amounts. People in all fields of work experience pervasive psychological distress, believing that they are intellectual frauds and fearing being recognized as impostors. The objective of this presentation is to provide relief to those suffering from Impostor Syndrome by analyzing possible sources of this distress, exploring tactics to overcome these feelings, and recognizing that we have a community of peers sharing the same experience.
In this talk we will follow a Norwegian insurance company over 6 years where they went from a very traditional to a completely automated on-premise infrastructure and continuous deployment model. As part of their transformation of Operations, Development, Deployment and Processes they identified and agreed on 9 DevOps principals. Some of these principals is still considered very controversial outside this company, even by todays DevOps standards. One of these principals is for instance "no branching"! These new practices and level of automation allowed them to eliminate any previous release barriers, in terms of both time and risk, and to dedicate focus to their customers and business to develop, improve and experiment with their software on a complete different level than before.
+
+
Parallel to this journey and in the same company, a new open source automation and infrastructure management tool specifically created for Windows emerged. Its name was ConDep and automate everything Windows for this and many other companies today.
+
+
By sharing what this company did and their experienced outcome, we hope this will give valuable input to others in a similar process or motivate to fight for the DevOps way if you're not. Not to mention shed light on some of the more controversial decisions, which we believe might benefit a lot more than you might first think.
Not a DevOps-fan? This Ignite talk will provide you with a surefire set of techniques for bringing down any DevOps initiative!
+
+
Great patterns for avoiding the DevOps pitfall come in all flavours from organizational, through managerial to architectural, and this summary of best practices will be instantly useful to any DevOps saboteur.
Breaking down the silos between development and operations is the starting point for devops adoption, but is this sufficient ? For a number of organisations adopting devops really is a full reorganisation with a lot of team members getting new roles. This talk will guide you trough a number of these changes. What roles dissapear, what skills remain, but in a different role? This talk is based on real changes in actual large organisations. It will cover merging teams, relocating teams, changing the management of a team, the new role of architects, and much more.
As one way of bringing the Ops closer to the Devs, we're using Cucumber to describe our systems from an operations perspective. Which application is dependent on which? How are they configured? How should they behave in network outages? It's all in the Gherkin.
Habitat was released as an open source project by Chef in June 2016. After a few months of it being "in the wild", we'll talk about some of the cool stuff and some of the challenges of this new application automation method.
Title:
+Breaking free from the DevOps security myths
+
+
+
Abstract:
+
+
The most important takeaway is that many big enterprises have got ways to address security that are based on a waterfall approach to development. However in DevOps traditional ways of addressing security is maybe not the best fit. I will try to reflect upon some of the misunderstandings that can arise and how to fix it in a way that in the end contributes to secure DevOps.
Title:
+How can we know if IT systems are working well?
+
+
+
Abstract:
+
+
+I will try to break down the learnings of 20 years of research, in IT operations, into a practical checklist of questions, under the umbrella of: can we promise a business or organization that its IT systems and services are working according to plan? The talk will touch on subjects like monitoring, policy, configuration, dependencies, scalability, and knowledge management.
+
Title:
+DevOps is dead (a story by the Jesus of DevOps)
+
+
+
Abstract:
+
+
When DevOps came, it brought hope to the tired masses, enprisoned in the nauseating siloses of their tiring existence. But now once-faithful disciples have proclaimed DevOps dead. The Dark Ages of #NoOps have arrived. Some people are rejoicing, others are weeping. Everyone is asking: will DevOps stay dead forever? Or will it be rediscovered and given a new name (just like containers and microservices) to bring hope to us all, once againg? Let's observe the original followers and the various sects that sprouted from the DevOps seed and try to determine if DevOps will indeed stay dead forever.
+
Title:
+Reaping the rewards of remote-friendly DevOps
+
+
+
Abstract:
+
+
This talk will discuss some of the difficulties and benefits of being a remote worker on a DevOps team. I will tell the story of my experience of being a DevOps Engineer at Rackspace, fully remote, for the last 3 years. I will also talk about how I have been living the digital nomad lifestyle since January of 2016, as a participant in the Remote Year program, living and working with 75 remote workers across three continents, in a different city each month. With these two narratives, I will present tips & tricks, share failures & successes (especially how contributing to open source has been useful as a remote worker), and give attendees a list of concrete takeaways they can use to work smarter, work remotely, and be successful.
+
+
+
diff --git a/exampleSite/content/events/2016-oslo/propose.md b/exampleSite/content/events/2016-oslo/propose.md
new file mode 100644
index 000000000..43a3ce007
--- /dev/null
+++ b/exampleSite/content/events/2016-oslo/propose.md
@@ -0,0 +1,40 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "propose"
+type = "event"
++++
+
+
+Call for papers is now closed, but you can still propose an ignite talk!
+
+
An Ignite talk will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session: even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
Students may apply for discounted or maybe even free tickets. {{< event_link page="contact" text="Drop us an email" >}} and we will contact you with a special offer.
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-oslo/speakers.md b/exampleSite/content/events/2016-oslo/speakers.md
new file mode 100644
index 000000000..c5643a953
--- /dev/null
+++ b/exampleSite/content/events/2016-oslo/speakers.md
@@ -0,0 +1,7 @@
++++
+date = "2016-06-23T12:14:14+01:00"
+heading = "DevOpsDays Oslo - Speakers"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-oslo/sponsor.md b/exampleSite/content/events/2016-oslo/sponsor.md
new file mode 100644
index 000000000..e5aa7ab63
--- /dev/null
+++ b/exampleSite/content/events/2016-oslo/sponsor.md
@@ -0,0 +1,51 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+DevopsDays is a self-organizing conference for practitioners. It brings together leaders in Software Development and IT Operations to collaborate and learn.
+
+
+
Why sponsor DevopsDays?
+Sponsoring DevopsDays will give you the opportunity to network and build relationships with developers, IT executives, Ops, DevOps, and managers within the burgeoning Scandinavian DevOps community.
+
+Our sponsorship package are constructed to offer our sponsors lead generation, networking, branding, and talent recruitment.
+
+
+DevopsDays is gathering IT practitioners, managers, developers, and influencers from all over Scandinavia and as a Gold Sponsor you will have an opportunity to be right there with them. Gold Sponsorships include opportunities to connect with each one of these attendees as we strategically drive traffic to your sponsor booth. Gold sponsors enjoy pre-event promotion through our social media as well as our website. The package costs NOK 35.000, EUR 3.800, USD 4.300, which includes:
+
+
Logo on event website
+
Logo on shared slide, displayed during breaks
+
Logo on email marketing
+
4 Included Tickets
+
Booth space in the main hall
+
1 minute pitch to the audience
+
Recognition on the website and social media before, during and after the event
+
+
+
Student sponsorship
+Students are the new breed of talent shaping the future of IT. We believe it is important that they get a chance to attend DevOpsDays. As a Student sponsor you will be helping students by sponsoring their ticket for the event. Student sponsors will get recognition by pre-event promotion through our social media as well as on our website. At a bare minimum you will have to sponsor three tickets for students, which amounts to NOK 8.250, EUR 895, USD 1.010 which includes:
+
+
Logo on event website
+
Logo on shared slide, displayed during breaks
+
Recognition on the website and social media before, during and after the event
+
+
+
Other exclusive special sponsorships
+There are also opportunities for other exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, {{< event_link page="contact" text="send us an email" >}}.
+
+
+
diff --git a/exampleSite/content/events/2016-oslo/welcome.md b/exampleSite/content/events/2016-oslo/welcome.md
new file mode 100644
index 000000000..6fd34c917
--- /dev/null
+++ b/exampleSite/content/events/2016-oslo/welcome.md
@@ -0,0 +1,122 @@
++++
+date = "2016-05-04T09:30:06+02:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-oslo"]
+
++++
+
+
DevOpsDays is a self-organizing conference for DevOps practitioners. It brings together leaders in Software Development and IT Operations to collaborate and learn from each other. It is both a technical conference and a conference focusing on culture, processes and structure within organizations. We encourage both technologists and business people to attend, learn and share experiences.
+
+
At a high-level, each day will consist of a mix of presentations, ignite presentations, and open spaces. There will be an evening party for all participants scheduled for the evening of September 5th. A great opportunity for networking, mingling and having a good time.
+
+
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Register
+
+
+ {{< event_link page="registration" text="Register to attend the event!" >}}
+
+ Call for papers is closed, but you can still {{< event_link page="propose" text="propose an ignite talk!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
diff --git a/exampleSite/content/events/2016-paris/conduct.md b/exampleSite/content/events/2016-paris/conduct.md
new file mode 100644
index 000000000..cf6dc5e76
--- /dev/null
+++ b/exampleSite/content/events/2016-paris/conduct.md
@@ -0,0 +1,60 @@
++++
+date = "2016-09-29T15:22:48+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## Politique anti-harcèlement
+
+Tous les participants, conférenciers, sponsors et volontaires pour notre conférence doivent accepter le code de conduite suivant. Les organisateurs s’attacheront à faire respecter ce code durant l’événement. Nous attendons de la part de chaque participant une coopération pour assurer un environnement sain pour tous.
+
+devops REX se veut une expérience sans harcèlement. Nous, organisateurs, et signataires de ce code de conduite, nous engageons à ne tolérer aucune forme de harcèlement, quelles qu’en soient les circonstances. Les visiteurs, sponsors et partenaires qui enfreindraient cette règle seront sanctionnés et exclus de la conférence sans aucune possibilité de remboursement, sur simple demande des organisateurs.
+
+Le harcèlement comprend les commentaires verbaux, écrits ou gestuels offensants, au sujet du genre, de l’orientation sexuelle, du handicap, de l’apparence physique, de l’ethnie ou de la religion. Est considéré comme du harcèlement le fait de suivre, observer, photographier, filmer, enregistrer, imposer un contact physique à une personne sans son consentement ou à son insu. Le harcèlement se définit également par tout comportement visant délibérément à intimider une personne, y compris par le fait de l’interrompre systématiquement dans ses activités et ses échanges avec les autres participants. De même, il ne sera toléré aucune avance à caractère sexuelle déplacée. Il est enfin interdit de diffuser tout contenu à caractère sexuel dans un espace public, ni d’entamer toute activité, gestuelle, annonce à caractère sexuel. Ce dernier point concerne également l’accoutrement sur les lieux de la conférence qui ne doivent en aucun cas être provocants ou contribuer à une sexualisation de la personne ainsi vêtue, et de la conférence en elle-même par extension.
+
+Si vous vous sentez harcelé(e), ou si vous remarquez que quelqu’un est en train de subir une situation de harcèlement, contactez immédiatement un membre de l’organisation identifiable grâce à un badge et un t-shirt spécifique mentionnant son statut.
+
+## Code de conduite
+
+I. En participant à devops REX, j’apprends et je partage mon expérience avec d’autres participants de devops REX, afin de faire progresser mes connaissances et celles des autres, pour un bénéfice individuel et collectif. Je co-crée l’expérience avec les autres participants, ainsi je suis préparé à contribuer par ma présence, ma sensibilité et mon énergie à la création de la meilleure expérience possible pour moi et pour les autres.
+
+II. Je viens à devops REX pour interagir avec les gens. Je comprends que les images et les propos suggestifs ou désobligeants peuvent offenser les autres participants, ce qui leur rendra l’expérience désagréable. Je comprends aussi que les gens peuvent avoir des sensibilités différentes des miennes. J’accepte sans réserve que quelque chose me soit rapporté comme offensant ou inacceptable dans le contexte de l’événement devops REX et j’adapte mon comportement et mes propos en conséquence.
+
+III. Je ne harcèle ou n’offense jamais intentionnellement un autre participant, en particulier sur la question du genre, de l’orientation sexuelle, du handicap, de l’apparence physique, de l’ethnie ou de la religion et ne tolère pas qu’un autre participant soit harcelé ou victime de harcèlement. Si je suis témoin d’une telle situation, j’informe l’auteur de la nature incorrecte de son comportement et j’avertis les organisateurs de devops REX.
+
+IV. Si je suis moi-même offensé ou harcelé, j’informe les gens autour de moi en qui j’ai confiance, ou d’une manière plus générale avec qui je me sens en sécurité, ainsi que les organisateurs de devops REX. Une fois en sécurité, je désigne aux organisateurs le ou les responsables de ce comportement inadapté, et je peux, si je le souhaite, informer moi-même le ou les concernés, dans l’espoir qu’il s’agisse uniquement d’une maladresse ignorante et non une démarche consciente et malintentionnée. Je ne suis cependant tenu à aucune obligation de le faire.
+
+V. Je comprends moi aussi que nous sommes tous différents et que ce qui est évidemment inconvenant pour moi ne l’est peut-être pas, ou pas autant, pour d’autres. Ainsi, j’essaye de pardonner aux autres les actions inopportunes qui auraient été commises en toute bonne foi, tout en gardant à l’esprit que ma priorité reste ma sécurité et celle des autres. Je réagis donc sans hésitation ni réserve en cas de situation inappropriée.
+
+VI. J’ai confiance en la capacité des organisateurs de devops REX mais aussi en celle des participants à créer ensemble la meilleure expérience possible pour tous, moi y compris. Je crois en la vocation de devops REX qui est de tous nous faire grandir techniquement, méthodologiquement et humainement, et je n’oublie pas qu’il est également de ma responsabilité de faire de cet événement une réussite enrichissante sur tous les plans. Si moi ou un autre participant adopte un comportement pouvant compromettre cet aspect de l’événement, je m’attends à ce que les organisateurs de la conférence prennent les mesures adéquates, y compris l’expulsion des responsables et le recours aux autorités appropriées.
+
+## *(en)* Anti-Harassment Policy
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## *(en)* Code of Conduct
+
+I. I am an attendee at devops REX, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-paris/contact.md b/exampleSite/content/events/2016-paris/contact.md
new file mode 100644
index 000000000..c72892917
--- /dev/null
+++ b/exampleSite/content/events/2016-paris/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-09-29T15:22:48+02:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-paris/location.md b/exampleSite/content/events/2016-paris/location.md
new file mode 100644
index 000000000..dafc5a4b1
--- /dev/null
+++ b/exampleSite/content/events/2016-paris/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-09-29T15:22:48+02:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2016-paris/program.md b/exampleSite/content/events/2016-paris/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2016-paris/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2016-paris/propose.md b/exampleSite/content/events/2016-paris/propose.md
new file mode 100644
index 000000000..67aa7c01d
--- /dev/null
+++ b/exampleSite/content/events/2016-paris/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-09-29T15:22:48+02:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
diff --git a/exampleSite/content/events/2016-paris/sponsor.md b/exampleSite/content/events/2016-paris/sponsor.md
new file mode 100644
index 000000000..c49aa3195
--- /dev/null
+++ b/exampleSite/content/events/2016-paris/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-09-29T15:22:48+02:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-paris/welcome.md b/exampleSite/content/events/2016-paris/welcome.md
new file mode 100644
index 000000000..b1a2d469f
--- /dev/null
+++ b/exampleSite/content/events/2016-paris/welcome.md
@@ -0,0 +1,114 @@
++++
+date = "2016-09-29T15:22:48+02:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-paris"]
+
++++
+
+
{{< event_start >}}
+
+L'équipe derrière devopsdays Paris 2013 et 2015, ainsi que les meetups Paris
+Devops, présente **devops REX** : une conférence d'un jour, 100% retours
+d'expériences concrets du terrain, comprenant présentations, questions-réponses
+et échanges informels, directement auprès des décideurs informatiques qui
+pilotent et conçoivent ces changements.
+
+**La langue principale de cette conférence sera le français.**
+
+*(en)* From the team that brought you devopsdays Paris 2013 and 2015, as well as the
+Paris Devops Meetup, comes **devops REX**: a one-day, single-track conference
+focusing on real world experience and feedback, featuring presentations, Q&A
+sessions, and discussions from industry practitioners and taste-makers.
+
+**The principal language of this conference will be French.**
+
+## Pour plus d'informations, veuillez visiter notre site principal: **https://www.devopsrex.fr/**
+
+
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
+{{< event_twitter devopsdaysrex >}}
diff --git a/exampleSite/content/events/2016-philadelphia/conduct.md b/exampleSite/content/events/2016-philadelphia/conduct.md
new file mode 100644
index 000000000..a52319183
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Philadelphia"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-philadelphia/contact.md b/exampleSite/content/events/2016-philadelphia/contact.md
new file mode 100644
index 000000000..137293bed
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Philadelphia"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-philadelphia/location.md b/exampleSite/content/events/2016-philadelphia/location.md
new file mode 100644
index 000000000..8b2aa4f49
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/location.md
@@ -0,0 +1,24 @@
++++
+City = "Philadelphia"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+## Chemical Heritage Foundation
+
+
+ Open Spaces Intro and Proposals
+ We'll describe the Open Spaces format, in which attendees propose their own breakout session topics. Then, attendees will form a consensus on which topics they'd like to discuss as groups, and we'll assign them to the following three time slots, with 5 tracks of varying sizes available.
+
+
+
+
+
+
+
+
+ Open Space
+ Breakout Session Time Slot #1
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+ Open Space
+ Breakout Session Time Slot #2
+
+
+
+
+
+
+
+
+ Open Space
+ Breakout Session Time Slot #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+
+ Evening Reception at CHF
+
+
+
+
+
+
+
+
+
+
+
+
+
Thursday October 27
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+ Open Space Proposals
+ Attendees will propose and vote on topics for our breakout sessions, and we'll assign them to the 3 time slots below, over 5 tracks.
+
Title:
+Application Secret Management with AWS KMS
+
+
+
Description:
+
+
+Managing application secrets, such as database passwords or API keys, can be a tricky problem in any environment. It becomes even trickier when we have an end-to-end Continuous Delivery pipeline, deploying an application with no human intervention. The question becomes: how do we maintain secrets in source control, along with the infrastructure and functional code, without exposing them to everyone? Additionally, CapitalOne, being a large financial institution, is subject to regulations like "segregation of duties", which prohibits developers from having admin access to production. Using a combination of AWS KMS, IAM, and iptables, we were able to design a simple, cheap, and scalable solution that satisfies our security needs, as well as the regulatory requirements.
+
+Cloud computing and the advancement of tools for resource management and infrastructure automation
+have created unconventional forms of processing massive amounts of data, both efficiently, reliably
+and cost effectively.
+The effects of cloud computing can be visible in everyday life.
+Academic research is one of the fields that can benefit greatly from cloud computing.
+Particularly, genomics projects have successfully adopted cloud computing in research, and some start-ups
+have been created to offer services for mapping gene information to find links to pathologies by using AWS.
+Beyond genomics research projects, there is a vast amount of geospatial, satellite imagery, weather, news and
+other types of data available for analysis (https://aws.amazon.com/public-data-sets). To date, most
+compute intensive research tasks are run in supercomputers; the implementation of cloud computing has not been
+as fast as in other areas.
+Here it is proposed the utilization of AWS to analyze a set of data, automating the deployment of
+infrastructure and trigger analysis when a set of data is uploaded.
+This example shows scalability and elasticity of public clouds and
+can be easily applied to other types of analytics.
+
+Devops is culture enabled by tools, which are necessary but not sufficient. I touch on the history of devopsdays and the motivations that lead orgs to devops, while encouraging orgs to collaborate, communicate, and iterate towards increasing value for their orgs.
+
+Well-funded tech companies are hiring consultants or high-level leaders to help them create inclusive work cultures. But if you don't have the budget for a consultant or a Chief Diversity Officer, we can walk you through some tried and true DIY steps to creating a more inclusive work environment. We will focus on the four pillars of workplace inclusion: hiring, retention, promotion, and culture. Whether you're a 4-person start-up or a 200-person international tech company, a CEO or an entry-level developer, our DIY guide will provide you with the tools to create a more inclusive environment that will benefit employees and an organization's bottom line.
+
+In this talk, we will see what happens when we stop looking at our infrastructure development as just a bundle of scripts and start looking at it as an application. We will go over various concepts in the programming world that can be carried into infrastructure development, including local development, test-driven code, modular applications, and static code analysis. Out of this talk, I hope to give operations engineers a new way to build out systems and feel more confident in the stability of their infrastructure.
+
Title:
+Do You Know If Your Service Is Working Properly? A Guide To Being Paranoid.
+
+
+
Description:
+
+
+End-to-end monitoring, testing, and validation of an application or service can be helpful to both development and the business if done properly. It lets you answer the age old question "Is $APP up?" with confidence. Especially when individual service-owning teams are part of a larger whole, having a way to rapidly iterate and verify your changes is vital.
+
+This talk will go over background & history on end-to-end testing efforts, then discuss best practices for care and feeding of such systems, and pitfalls to avoid, with references.
+
+A brief History of Linux containers to provide understanding of where the technology came from. The history will be able to shed some light on the development of containers, and help with the understanding of the current implementations.
+
Title: The answer to the “where do we start” question
+
+
+
+
Description:
+
+
Where do we start? This is by far the question I’m asked the most when talking to people about implementing continuous delivery. Unlike other types of long journeys, the answer is rarely “at the beginning”.
+
+
One of the best ways to determine the best place to start is to figure out where you’re wasting the most resources, and one of the best ways to do that is to create a value stream map.
+
+
We’ll go over what a value stream map is, how you can create one, and how it can help you answer some important questions about your business. Questions like “where do we start?”.
+Behind the extensive downtimes I witness every holiday, I see a corporate failure to change the archaic processes to match the change in business models. Technology space has evolved. Businesses, however, especially larger ones, have a natural aversion to change, that is often justified by risk and cost factors. However, processes are put in place for exactly that reason — to save time and money. If they don’t accomplish those two goals or worse, contributing to the opposite – they need to be changed. In this talk I'll discuss a real world example of Black Friday 8 hour downtime of a large e-commerce website and discuss key anti-DevOps patterns contributing to the failure.
+
+Leaving the comfort zone of throwing code over the wall so the OPS team can deploy takes either guts or insanity. Developers should care more about how their products reach customers and one of the best ways to do this is to get into DevOps and involve themselves in the process of making sure the code is doing it's best being a good citizen in the actual environment. We'll see some of the hops, prejudices and issues developers have to face when they start their journey into the DevOps land and how this will improve their skill set and the final experience customers have actually using the product.
+
+I was the regular enterprise sysadmin: network administrator & datacenter systems engineer in an ISP, IT operation support administrator in a retail company and IT systems engineer in a software development company. I spent time on choosing cool names for my servers. I knew the exact location of a server in the datacenter. I felt sad when their lights stopped blinking. I felt more sad it that happened on a weekend night.
+
+And then I joined a team adopting the DevOps mindset. Let me be honest: change was scary! But it was also a great learning experience. This talk will share what was challenging and what worked for me in my transition from being a regular sysadmin to living and breathing DevOps.
+
+With the rise in telecommuting as an effective business strategy, we all deal with remote workers at some point during our work hours -- whether they are teammates or clients. Learn some tips and tricks I’ve picked up over several years as a remote worker working with teammates and clients from afar.
+
Title:
+Buzzword Bingo: Architecting a Cloud-Native Wayback Machine
+
+
+
Description:
+
+
+Have you ever played buzz-word bingo at a conference before? Attend this interactive session (with real Bingo!) where Ross Kukulinski, a NodeJS Evangelist, container enthusiast, and NodeSource technical product manager will share his cloud-native implementation of the Internet Archive’s Wayback Machine.
+
+Ross will share his goals, architecture, and technology stack choices to implement a scalable, containerized, microservice implementation of the Wayback Machine using Node.JS, Docker, and Kubernetes.
+Topics covered in the talk will include:
+Architecture
+Scaling
+Monitoring
+CI/CD
+Live demo
+
Title:
+How CI/CD helped us "Bill Pay team" to deliver features faster to customers
+
+
+
Description:
+
+
+Earlier bill pay services were scattered in different regions, delivered in different release cycles by different teams. Consolidating all those services to a Microservice, integrated with CI/CD to deploy on AWS made it convenient and faster for team to deliver bug fixes or new services faster to client.
+
+Conway's Law tells us "organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations." When organizations are healthy and dynamic, adaptability and high-quality software result. Unhealthy organizations “ship the org chart”, producing software that reflects dysfunctional practices.
+
+What if we turn Conway's law around and make technology choices that improve our culture? Can bad software choices create new rifts? Are we selecting tech that disempowers developers and keeps operations up at night? Is our software architecture secretly encoding new divisions between our teams? I've run containers in production, written microservices, and operated all manner of infrastructure from established favorites to the latest hipster trends. Let's talk about how all the usual technological suspects (and maybe a few surprising ones) can shape the organizational culture in startups and enterprises alike.
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-philadelphia/proposals.md b/exampleSite/content/events/2016-philadelphia/proposals.md
new file mode 100644
index 000000000..2cd7a014e
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/proposals.md
@@ -0,0 +1,15 @@
++++
+City = "Philadelphia"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-philadelphia/propose.md b/exampleSite/content/events/2016-philadelphia/propose.md
new file mode 100644
index 000000000..771b92184
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/propose.md
@@ -0,0 +1,52 @@
++++
+City = "Philadelphia"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+
+
+Call for proposals extended to Friday July 8th 12am Eastern.
+Selected proposals will be announced within a few weeks of the closing date.
+
+
+
+Devopsdays Philadelphia is a single track, two day event. The format will include main track presentations, Ignite talks, and Open Spaces sessions. We're soliciting proposals for 30 minute presentations and Ignite style lightning talks.
+
+A selection committee will review all proposed talks. Submitters will receive an email update before the program is announced. All proposals must be received by Friday July 8th night into Saturday at 12am Eastern. Selected proposals will be announced within a few weeks of the closing date.
+
+Are you new to public speaking? We can provide guidance/coaching for new speakers upon request.
+
+There are three types of sessions that you can propose. This call for proposals covers types 1 and 2.
+
+
+
Talk/panel for the conference main track. These are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room.
+
Open Space session. We welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Selection Guidelines
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+* Broad appeal: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+* New local presenters: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local Philadelphia area communities.
+* Under-represented voices: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+* Original content: We prefer talks not already presented at another event, especially another one in the local area or one available in recorded form.
+* No third-party submissions: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
+* No vendor pitches: We value vendors and sponsors, however we cannot accept a talk that appears to be a pitch for your product. If you'd like to demo your product or service, please consider sponsoring the event to secure your company a table.
+
+### Code of Conduct
+
+Please review the event code of conduct.
+
+### Travel Expenses
+
+If your employer does not cover travel expenses you incur as a speaker at Devopsdays Philadelphia the conference will help. Speakers receive free conference tickets and should not incur out-of-pocket travel expenses in order to participate.
diff --git a/exampleSite/content/events/2016-philadelphia/registration.md b/exampleSite/content/events/2016-philadelphia/registration.md
new file mode 100644
index 000000000..e17fcaded
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/registration.md
@@ -0,0 +1,10 @@
++++
+City = "Philadelphia"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+
diff --git a/exampleSite/content/events/2016-philadelphia/speakers.md b/exampleSite/content/events/2016-philadelphia/speakers.md
new file mode 100644
index 000000000..56ef042af
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-08-26T09:17:15"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-philadelphia/sponsor.md b/exampleSite/content/events/2016-philadelphia/sponsor.md
new file mode 100644
index 000000000..9ed432229
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/sponsor.md
@@ -0,0 +1,57 @@
++++
+City = "Philadelphia"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}. Gold, Silver, and Bronze sponsorship packages are detailed in our prospectus.
+
+Additional à la carte sponsorships are also possible:
+
+
+
coffee - signage by the coffee displays with your logo throughout the day
+
breakfast - signage by the breakfast tables and in the eating area with your logo in the morning before sessions
+
snacks - signage by the snack area with your logo during the afternoon when snacks are available
+
lunch - signage by the lunch tables and in the eating area with your logo during lunch
+
evening reception - signage at the evening happy hour
+
lanyards
+
room and session sponsorships
+
logo and t-shirt design
+
+
+These may be purchased in addition to (or in lieu of) the sponsorships in the prospectus.
+
+Please email us at {{< email_organizers >}} for more information.
+
+
+
+
+
+
+
packages
+
Bronze $1,000
+
Silver $3,000
+
Gold $5,000
+
+
+
2 included tickets
+
1 additional tickets (3 in total)
+
2 additional tickets (4 in total)
+
Full Table
+
Shared Table
+
Logo on DevOpsDays Philadelphia website and on event signage.
+
Logo on all attendee email.
+
1 minute pitch to all attendees
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
diff --git a/exampleSite/content/events/2016-philadelphia/welcome.md b/exampleSite/content/events/2016-philadelphia/welcome.md
new file mode 100644
index 000000000..6eca0efb7
--- /dev/null
+++ b/exampleSite/content/events/2016-philadelphia/welcome.md
@@ -0,0 +1,79 @@
++++
+City = "Philadelphia"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-philadelphia"]
+
+
++++
+
+
+ {{< event_logo >}}
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+ Register
+
+
+ {{< event_link page="registration" text="Register to attend the conference!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter devopsdaysphl >}}
diff --git a/exampleSite/content/events/2016-portland/conduct.md b/exampleSite/content/events/2016-portland/conduct.md
new file mode 100644
index 000000000..7dffbf8de
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-portland/contact.md b/exampleSite/content/events/2016-portland/contact.md
new file mode 100644
index 000000000..395bb1d6a
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+## Our local team
+
+{{< list_organizers >}}
+
+## The core devopsdays organizer group
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-portland/location.md b/exampleSite/content/events/2016-portland/location.md
new file mode 100644
index 000000000..f3fa4f802
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/location.md
@@ -0,0 +1,14 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+### DevOpsDays Portland will be held at the Oregon Convention Center!
+
+
+
+The Oregon Convention Center is in Northeast Portland and is easily accessible via public transit. They also have parking available for whatever you might want to drive in. See directions for both at their site.
diff --git a/exampleSite/content/events/2016-portland/program.md b/exampleSite/content/events/2016-portland/program.md
new file mode 100644
index 000000000..3ef7df48a
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program.md
@@ -0,0 +1,384 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+ [DevOps: A History (Nell Shamrell-Harrington)](/events/2016-portland/program/nell-shamrell-harrington)
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+ [DevOps vs. SRE: Fight! (wait, I mean learn!) (David Blank-Edelman)](/events/2016-portland/program/david-blank-edelman)
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+ [Metrics, Gauges, Counters and Ratios: designing and implementing quality metrics (Caskey Dickson)](/events/2016-portland/program/caskey-dickson)
+
+
+
+
+
+
+
+
+ Open Spaces Opening
+
+
+
+
+
+
+
+
+ Lunch
+
+
+
+
+
+
+
+
+ Ignites
+
+
[McRouter: Over 100 billion Memcache GETs served (Dan Young)](/events/2016-portland/program/dan-young)
+
[Bots Not Cattle (Josh Berkus)](/events/2016-portland/program/josh-berkus)
+
[Docker Provides Convenience with Hidden Complexity - How Can We Cope? (Matthew Barker)](/events/2016-portland/program/matthew-barker)
+
[Being an introvert and at a conference, not as hellish as you think it is (JJ Asghar)](/events/2016-portland/program/jj-asghar)
+
+
+
+
+
+
+
+
+
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space #3
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+ [What we’re learning about burnout and how a DevOps culture can help (Ken Mugrage)](/events/2016-portland/program/ken-mugrage)
+
+
+
+
+
+
+
+
+ Closing Remarks
+
+
+
+
+
+
+
+
+ Evening Event hosted by New Relic
+
+
+
+
+
+
+
Day 2 - August 10
+
+
+
+
+
+
+
+
+ Registration and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+ [Everything is Terrible: Three Perspectives on Building, Configuring, and Securing Software (Chris Barker, Adrien Thebo, Ben Hughes)](/events/2016-portland/program/chris-barker)
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+ [Defending against CDD: Chaos-Driven Delivery (Julia Wester)](/events/2016-portland/program/julia-wester)
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+ [Why won't my DevOps team talk to my Security team? (Ben Hughes)](/events/2016-portland/program/ben-hughes)
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+ [Monitor the Unmeasureable (Jennifer Davis)](/events/2016-portland/program/jennifer-davis)
+
+
+
+
+
+
+
+
+ Open Spaces Opening
+
+
+
+
+
+
+
+
+ Lunch
+
+
+
+
+
+
+
+
+ Ignites
+
+
[DevOpsing Your Resume (E Dunham)](/events/2016-portland/program/e-dunham)
+
[Carbon: PowerShell automation for Windows computers, websites, and services (Aaron Jensen)](/events/2016-portland/program/aaron-jensen)
+
[Are you talking to me? (Ben Burry)](/events/2016-portland/program/ben-burry)
diff --git a/exampleSite/content/events/2016-portland/program/aaron-jensen.md b/exampleSite/content/events/2016-portland/program/aaron-jensen.md
new file mode 100644
index 000000000..20049e512
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/aaron-jensen.md
@@ -0,0 +1,14 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "Aaron Jensen"
+type = "talk"
++++
+
+**Title:** Carbon: PowerShell automation for Windows computers, websites, and services
+
+**Description:**
+
+Carbon is a PowerShell module for automating the configuration of Windows computers, websites, services, and more. Come see all the cool problems it has already solved so you don't have to.
+
diff --git a/exampleSite/content/events/2016-portland/program/adrien-thebo.md b/exampleSite/content/events/2016-portland/program/adrien-thebo.md
new file mode 100644
index 000000000..de720eda9
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/adrien-thebo.md
@@ -0,0 +1,29 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Adrien Thebo"
+type = "talk"
++++
+
+**Title:** Everything is Terrible: Three Perspectives on Building, Configuring, and Securing Software
+
+**Description:**
+
+Developers, operations, and security all have differing agendas and benchmarks for success. One is tasked with building new features, the next with delivering and making them available, and the third is tasked with mitigating the risks associated with the previous two.
+
+Core to the DevOps movement is the idea of building empathy with people in other teams in order to align for business success. Expanding this idea to Dev, Ops, and Security, three engineers who have each lived primarily one of these will be providing their perspective in working collaboratively to try not to kill each other. They will talk about their backgrounds, provide practical examples from daily experiences, and share suggestions on building common tooling that minimizes friction and enhances collaboration.
+
+This talk will discuss
+
+* The misalignment of priorities that organisations often force upon these groups
+* Struggles with collaboration and working cultures
+* Common bottlenecks associated with release cycles and security processes
+* Building empathy and optimizing for communication that doesn't involve fisticuffs (or other 19th century combat styles)
+
+The audience will come away with:
+
+* Ideas for handling these complicated situations
+* Approaches for building workflows and possible tooling suggestions to minimize the tire fires
+* A new appreciation for those on the other sides of the silo walls
+
diff --git a/exampleSite/content/events/2016-portland/program/ben-burry.md b/exampleSite/content/events/2016-portland/program/ben-burry.md
new file mode 100644
index 000000000..a111f6b4d
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/ben-burry.md
@@ -0,0 +1,24 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Ben Burry"
+type = "talk"
++++
+
+**Title:** Are you talking to me?
+
+**Description:**
+
+### How carrying out our lives over video is affecting us and our teams
+
+As organisations have begun to embrace remote working, we've gained more flexibility in where and how we can work. Voice and video remain the most efficient way to communicate while working distant from your colleagues, but doing this effectively while also feeling part of a team can carry with it some side effects.
+
+In this talk I'll take a look at the unexpected impact that video conversations may be having on our professional and personal relationships. We’ll focus on the things that are in your control to make working over video better (and share some feelings about the stuff that’s not).
+
+The talk will:
+
+* help you more quickly spot the nuances of remote communication within your team
+* cover some of the research into the psychological effect this can have on us as individuals, and as teams
+* explore what you and your organisation can do to mitigate against these
+
diff --git a/exampleSite/content/events/2016-portland/program/ben-hughes.md b/exampleSite/content/events/2016-portland/program/ben-hughes.md
new file mode 100644
index 000000000..6897210a2
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/ben-hughes.md
@@ -0,0 +1,19 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Ben Hughes"
+type = "talk"
++++
+
+**Title:** Why won't my DevOps team talk to my Security team?
+
+**Description:**
+
+So you bought yourself a nice new shiny devops team, and everything is running swell. Productivity is up, high fives are up, that strange graph on Github has an awful lot of green on it, as does Nagios. Tea and medals for all.
+
+But there's a problem. Your security team are hiding in their bunker silo, refusing to come out until everyone agrees to their hourly password rotation policy demands, and you'd really like your micro-scooter wielding DevOps team to talk to them about this new social 401k via Snapchat through bitcoins product you're launching next week.
+
+What to do, what to do?
+
+In this, now fantastically elaborately set up talk, I will discuss who's fault this all is, what we've done at Etsy to have hundreds of security engineers around the clock, and why you should really use WhatsApp over Snapchat.
diff --git a/exampleSite/content/events/2016-portland/program/caskey-dickson.md b/exampleSite/content/events/2016-portland/program/caskey-dickson.md
new file mode 100644
index 000000000..fd83ea333
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/caskey-dickson.md
@@ -0,0 +1,15 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Caskey Dickson"
+type = "talk"
++++
+
+**Title:** Metrics, Gauges, Counters and Ratios; designing and implementing quality metrics
+
+**Description:**
+
+The only thing worse than no metrics are bad and/or misleading ones. Well-designed metrics enable you to quickly know the state of your service and have confidence that your systems are healthy. Poor metrics distract you from finding root causes of outages and extend downtime. Unfortunately it isn't always obvious what counts and how to count it.
+
+This talk will cover the essential attributes needed in quality metrics and walk participants through the steps needed to capture them in a useful format while avoiding common pitfalls in metric design. The principles of metric design, types of metrics, and when to use the common types will be covered. Come learn about ratios, gauges, counters; primary, secondary, proxy and derived metrics; as well as intervals, ordinals and more.
diff --git a/exampleSite/content/events/2016-portland/program/chris-barker.md b/exampleSite/content/events/2016-portland/program/chris-barker.md
new file mode 100644
index 000000000..c3a8c5dbd
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/chris-barker.md
@@ -0,0 +1,28 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Chris Barker"
+type = "talk"
++++
+
+**Title:** Everything is Terrible: Three Perspectives on Building, Configuring, and Securing Software
+
+**Description:**
+
+Developers, operations, and security all have differing agendas and benchmarks for success. One is tasked with building new features, the next with delivering and making them available, and the third is tasked with mitigating the risks associated with the previous two.
+
+Core to the DevOps movement is the idea of building empathy with people in other teams in order to align for business success. Expanding this idea to Dev, Ops, and Security, three engineers who have each lived primarily one of these will be providing their perspective in working collaboratively to try not to kill each other. They will talk about their backgrounds, provide practical examples from daily experiences, and share suggestions on building common tooling that minimizes friction and enhances collaboration.
+
+This talk will discuss
+
+- The misalignment of priorities that organisations often force upon these groups
+- Struggles with collaboration and working cultures
+- Common bottlenecks associated with release cycles and security processes
+- Building empathy and optimizing for communication that doesn't involve fisticuffs (or other 19th century combat styles)
+
+The audience will come away with:
+
+- Ideas for handling these complicated situations
+- Approaches for building workflows and possible tooling suggestions to minimize the tire fires
+- A new appreciation for those on the other sides of the silo walls
diff --git a/exampleSite/content/events/2016-portland/program/dan-young.md b/exampleSite/content/events/2016-portland/program/dan-young.md
new file mode 100644
index 000000000..57b45bb1b
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/dan-young.md
@@ -0,0 +1,16 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Dan Young"
+type = "talk"
++++
+
+**Title:** McRouter: Over 100 billion Memcache GETs served
+
+**Description:**
+
+New Relic uses [McRouter](https://github.com/facebook/mcrouter), a [Memcache](https://memcached.org/) proxy/router, for scaling our cache infrastructure. This Ignite talk will cover what McRouter is and how we use it to scale out Memcache for our microservices.
+
+McRouter (created by Facebook) supports sharding, replication, connection pooling, cache warming, and flexible routing. I'll show some of the basics and a few examples of how rich routing policies let us design our caching infrastructure.
+
diff --git a/exampleSite/content/events/2016-portland/program/david-blank-edelman.md b/exampleSite/content/events/2016-portland/program/david-blank-edelman.md
new file mode 100644
index 000000000..014f40f76
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/david-blank-edelman.md
@@ -0,0 +1,13 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "David Blank-Edelman"
+type = "talk"
++++
+
+**Title:** DevOps vs. SRE: Fight! (wait, I mean Learn!)
+
+**Description:**
+
+Just within the last ten years (+-3), we have seen at least two separate communities evolve from the generic idea of Systems Administration/Operations. The first, DevOps, grew up very much in public, the second happened more within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. They have a number of priorities in common but also diverge in some very interesting ways. In this talk we’ll explore the key things we can learn from each group and see what might happen if we cross the streams.
diff --git a/exampleSite/content/events/2016-portland/program/e-dunham.md b/exampleSite/content/events/2016-portland/program/e-dunham.md
new file mode 100644
index 000000000..6dd62fc9b
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/e-dunham.md
@@ -0,0 +1,25 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "E Dunham"
+type = "talk"
++++
+
+**Title:** DevOpsing Your Resume
+
+**Description:**
+
+Despite the infamous shortage of engineers in our field, job hunting is
+
+rarely regarded as a pleasant experience. Even the most competent engineers often regard their resumes as minefields of technical debt.
+
+In this quick tour of how to apply some DevOps best practices to your resume or CV, we'll discuss:
+
+* Choosing the right tools for the job
+* The importance of version control
+* Organization and formatting to meet the users' needs
+* Continuous delivery
+* Where & how to reuse content
+
+Recognizing that your resume is just another piece of code can reduce the uncertainty of job hunting, free up time for the projects you care about, and help you strengthen your personal brand.
diff --git a/exampleSite/content/events/2016-portland/program/eric-passmore.md b/exampleSite/content/events/2016-portland/program/eric-passmore.md
new file mode 100644
index 000000000..aba6cea9f
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/eric-passmore.md
@@ -0,0 +1,15 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Eric Passmore"
+type = "talk"
++++
+
+**Title:** Stop doing Failure Mode Analysis and Start doing Checklists
+
+**Description:**
+
+Cultural changes are hard, and educating large teams in DevOps takes time. Half the time we feel like we are in the Rebel Alliance trying to overthrow the empire. There is a better way. Ignore the cultural changes, stop doing failure mode analysis and start doing checklists. Checklist work because people learn by doing. Teams do not push back because everyone is doing the work.
+
+Learn why failure mode analysis does not work, how to build a checklist, and how to roll out a checklist.
diff --git a/exampleSite/content/events/2016-portland/program/jennifer-davis.md b/exampleSite/content/events/2016-portland/program/jennifer-davis.md
new file mode 100644
index 000000000..9805f3178
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/jennifer-davis.md
@@ -0,0 +1,17 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Jennifer Davis"
+type = "talk"
++++
+
+**Title:** Monitor the Unmeasureable
+
+**Description:**
+
+From system performance to application metrics, we continue to further our understanding of what to monitor, why, and how to present it appropriately to the various audiences who need to act on this information. Yet there are things across our environment that we agree we can't measure because they are unquantifiable. That doesn't mean that there is zero signal to be analyzed and monitored.
+
+We can look at open source software that is in wide use, yet becomes stale and unusable after years due to the atrophy of maintainers keeping it up to date with security and integrations with other software, or implementation of new features that keep it useful. How do you measure the health of your current implemented software solutions so that you know when to start planning change, or committing intentional time to a project?
+
+In this talk, I'll tackle these questions in addition to sharing other observations about monitoring within our environments with the goal of inspiring others to examine available signals, their impact, and the value of monitoring.
diff --git a/exampleSite/content/events/2016-portland/program/jj-asghar.md b/exampleSite/content/events/2016-portland/program/jj-asghar.md
new file mode 100644
index 000000000..b4fa67595
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/jj-asghar.md
@@ -0,0 +1,17 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "JJ Asghar"
+type = "talk"
++++
+
+**Title:** Being an introvert and at a conference, not as hellish as you think it is.
+
+**Description:**
+
+I'd like to give some advice on how to deal with conferences as an introvert.
+
+Over the last couple years I've grown and learned to engage with the tech community in ways that an introvert would find challenging. This talk will hopefully help the audience avoid some of the landmines that I have stepped on.
+
+I want to help out my fellow introverts to realize that it's OK to be an introvert at big conferences. We can enjoy them too.
diff --git a/exampleSite/content/events/2016-portland/program/josh-berkus.md b/exampleSite/content/events/2016-portland/program/josh-berkus.md
new file mode 100644
index 000000000..c78c8c61c
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/josh-berkus.md
@@ -0,0 +1,13 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Josh Berkus"
+type = "talk"
++++
+
+**Title:** Bots Not Cattle Ignite
+
+**Description:**
+
+"Cattle Not Pets" got us to the first generation of microservice infrastructures. Now it's time for a second generation metaphor: "Bots Not Cattle." Intelligent, autonomous microservices which "just do the right thing" which permit us to go beyond the current limits of orchestration and configuration management are not only achievable, but easier than you'd expect.
diff --git a/exampleSite/content/events/2016-portland/program/julia-wester.md b/exampleSite/content/events/2016-portland/program/julia-wester.md
new file mode 100644
index 000000000..c6d48e305
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/julia-wester.md
@@ -0,0 +1,15 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Julia Wester"
+type = "talk"
++++
+
+**Title:** Defending against CDD: Chaos-Driven Delivery
+
+**Description:**
+
+Have you heard of TDD? Well, many teams struggle with CDD: Chaos-Driven Delivery. That is, teams struggle with how to handle the constant onslaught of overwhelming amounts of work and begin to lose hope. The good news is that if you understand operating systems, you already know a great deal about how to tame the chaos!
+
+Process management is an integral part of an operating system. The OS makes decisions about scheduling, sharing information between jobs, handling interrupts and multi-tasking. It also has to manage the resources of a process and be concerned with process synchronization, just as we mere humans do. This presentation will show you how to apply common concepts from operating system process management to the way teams process work. Attend and help your team kick CDD to the curb!
diff --git a/exampleSite/content/events/2016-portland/program/kelsey-hightower.md b/exampleSite/content/events/2016-portland/program/kelsey-hightower.md
new file mode 100644
index 000000000..435c8caf4
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/kelsey-hightower.md
@@ -0,0 +1,13 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Kelsey Hightower"
+type = "talk"
++++
+
+**Title:** No Ops
+
+**Description:**
+
+TBA
diff --git a/exampleSite/content/events/2016-portland/program/ken-mugrage.md b/exampleSite/content/events/2016-portland/program/ken-mugrage.md
new file mode 100644
index 000000000..21025f1d3
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/ken-mugrage.md
@@ -0,0 +1,21 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Ken Mugrage"
+type = "talk"
++++
+
+**Title:** What we’re learning about burnout and how a DevOps culture can help
+
+**Description:**
+
+One of the most overlooked advantages of converting to a DevOps culture can be the reduction of stress. This could be due to “sharing the load” as a whole team, the feeling of joint ownership in solving a business problem, or many other things.
+
+If you’re asked to support somebody else’s application without any insight to how it was built and what problems it’s trying to solve you’re likely to experience more than a little stress. The same is true if you’ve toiled away creating the perfect application only to see it deployed in a way that makes it unable to perform.
+
+The combination of stress and burnout is perhaps the biggest health threat in our industry. In fact, recent research has found that burnout--and the related concept of "vital exhaustion"--increases your risk of cardiovascular disease as much as body mass index, smoking and lipid levels. Unfortunately there are also well-known stories of burnout-related suicides in our industry, making this literally a life and death issue.
+
+If that isn’t reason enough to address the issue, we also know from the State of DevOps survey that the #1 indicator of company success is job satisfaction.
+
+In this talk Ken will go over some of the leading research in the area of burnout. We’ll talk about some of the more common causes of burnout as identified by clinical research and talk about how you can learn from organizations with solid DevOps cultural practices to help alleviate them.
diff --git a/exampleSite/content/events/2016-portland/program/matthew-barker.md b/exampleSite/content/events/2016-portland/program/matthew-barker.md
new file mode 100644
index 000000000..1520ef4aa
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/matthew-barker.md
@@ -0,0 +1,13 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Matthew Barker"
+type = "talk"
++++
+
+**Title:** Docker Provides Convenience with Hidden Complexity - How Can We Cope?
+
+**Description:**
+
+Using a container as the new unit of deployment greatly simplifies things on the surface. You no longer have your application and all the components in it. You don’t need to worry about the runtime environment. Or the operating system? It is all there. You just have the containers. But hold on. Think again. Things are a lot easier to manage - but you still have all those parts. You still have an operating system. And a runtime environment like e.g. a Java VM. And your application. It consists of a bunch of third party, open source libraries for the web frontend. Oh.. yeah and persistence is handled by that ORM library. And then there is this command line tool we have in the container to manage a few tasks. Learn how you can apply supply chain principles to get a better understanding of your container and all its parts. Improve the workflows around them, optimize the parts and manage it all efficiently. And take advantage of a number of emerging tools to keep it manageable.
diff --git a/exampleSite/content/events/2016-portland/program/nell-shamrell-harrington.md b/exampleSite/content/events/2016-portland/program/nell-shamrell-harrington.md
new file mode 100644
index 000000000..c79488a01
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/nell-shamrell-harrington.md
@@ -0,0 +1,13 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Nell Shamrell-Harrington"
+type = "talk"
++++
+
+**Title:** DevOps: A History
+
+**Description:**
+
+In the midst of buzzwords like "devops", "containers", "continuous delivery", "IAAS", and even "cloud" it can be easy to forget the problems these concept were created to solve. It is impossible to fully understand DevOps as it is now without understanding where it came from. This talk will take you through a journey of each stage of the DevOps movement - from the very beginning to the most bleeding edge tools and concepts of today. At each stage I will thoroughly cover the "how" and "why" - including personal testimonials from those involved - Devops evolved the way it did. Go beyond the buzzwords and gain a new understanding of the how and why of Devops. You will walk away with a new understanding of why we used to do things - what problems we were trying to solve, what brought DevOps to where it is now, and it’s potential for the future.
diff --git a/exampleSite/content/events/2016-portland/program/terrence-ryan.md b/exampleSite/content/events/2016-portland/program/terrence-ryan.md
new file mode 100644
index 000000000..d3dded3c0
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/program/terrence-ryan.md
@@ -0,0 +1,13 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-07-09T09:00:00-08:00"
+title = "Terrence Ryan"
+type = "talk"
++++
+
+**Title:** Driving Technical Change
+
+**Description:**
+
+Ever been to a conference, get inspired, try to bring what you learned back to the office, only to be stymied by co-workers who aren't interested in rocking the status quo? It turns out that people tend to resist change in patterns, and like any pattern they can be overcome by using other people's experiences with those skeptics. This session will teach you how to identify the skeptics, how to counter them, and give you a strategic framework to convince your whole office.
diff --git a/exampleSite/content/events/2016-portland/proposals.md b/exampleSite/content/events/2016-portland/proposals.md
new file mode 100644
index 000000000..0873048e0
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/proposals.md
@@ -0,0 +1,15 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-portland/propose.md b/exampleSite/content/events/2016-portland/propose.md
new file mode 100644
index 000000000..208684ec0
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/propose.md
@@ -0,0 +1,37 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+1. A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+1. An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room.
+1. Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+Our main criteria to make it to the top selection are:
+
+- Talks will be reviewed blind, meaning that the committee will not see proposals with names attached.
+- Original talks, and/or a fresh angle on relevant topics, are encouraged.
+- Vendor pitches will not be selected. Sales pitches are much better suited for sponsor booths, and sponsors at or above the Gold level will have an opportunity to give short pitches between talks.
+- We’d love to hear from new speakers, local folks, and underrepresented voices in tech.
+
+How to submit a proposal for a talk/panel: Fill out the form here..
+
+We will open a CFP for ignite talks closer to the event.
+
+Rules:
+
+- Be specific... we aren't mind readers (a description of about 20 lines is about right)
+- Detail is good... but not as important as explaining why your proposal would be interesting
+- Propose your own talk; don't have someone else do it for you.
+- Talks submitted for a third party will be summarily rejected. If your organization requires someone else propose for you, please contact us via email (organizers-portland-2016@devopsdays.org), and we’ll figure something out.
+- Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+- Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-portland/speakers.md b/exampleSite/content/events/2016-portland/speakers.md
new file mode 100644
index 000000000..8e8e2e0d1
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-portland/sponsor.md b/exampleSite/content/events/2016-portland/sponsor.md
new file mode 100644
index 000000000..1092a6a84
--- /dev/null
+++ b/exampleSite/content/events/2016-portland/sponsor.md
@@ -0,0 +1,119 @@
++++
+City = "Portland"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
packages
+
Bronze 1000 USD
+
Silver 3000 USD
+
Gold SOLD OUT!
+
Platinum* 10000 USD
+
+
+
+
+ Please contact us to inquire about sponsorship at any level.
+
+
+
+
included tickets
+
1
+
3
+
5
+
7
+
+
+
logo on DevOpsDays Portland event website
+
+
+
+
+
+
+
sponsorship blurb on website
+
+
+
+
+
+
+
logo on all email communication
+
+
+
+
+
+
+
logo on banner at venue during event
+
+
+
+
+
+
+
mention by MC at kickoff and close
+
+
+
+
+
+
+
1 minute pitch to full audience
+
+
+
+
+
+
+
premium table space
+
+
+
+
+
+
+
dedicated table space
+
+
+
+
+
+
+
shared table for swag
+
+
+
+
+
+
+ * Limited Platinum sponsorships available, contact us if you're interested in one!
+
+
+ Sponsors are responsible for providing high-res logos for use on the website and in promotional materials. The preferred file formats are EPS or AI.
+
+
+
+ There are also opportunities for exclusive special sponsorships. We have sponsorships available for an evening event and a speakers' dinner with special privileges for the sponsors of these events. We also have a lanyard sponsorship available. If you are interested in special sponsorships or have a creative idea about how you can support the event, send us an email.
+
+
+
+ View the {{< event_link page="program" text="program." >}}
+
+
+
+
+
+ Speakers
+
+
+ Check out the {{< event_link page="speakers" text="speakers!" >}}
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+{{< event_twitter devopsdayspdx >}}
+
+
+If you'd like to be notified about DevOpsDays PDX 2016, we've got the mailing list for you. We won't ever sell the addresses on the list, we'll never let sponsors email it, it's just for us to let you know what's going on.
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/chamada.md b/exampleSite/content/events/2016-portoalegre/chamada.md
new file mode 100644
index 000000000..abd97a69f
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/chamada.md
@@ -0,0 +1,31 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "chamada"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+Existem três formas para propor sua sessão:
+
+
Proposta para palestra/painel : 30 minutos com a atenção de todos os presentes.
+
Palestra relâmpago que serão apresentadas durante a sessão relâmpago. São intervalos de 5 minutos com slides trocando a cada 15 segundos (20 slides no total) que serão apresentados para todos os presentes.
+
Sessões de espaço aberto : Mesmo que você não tenha preparado uma apresentação, você é bem vindo para discutir e interagir propondo uma sessão ao vivo nos espaços abertos. Veja a explicação de espaços abertos para maiores informações.
+
+
+Nosso critério para escolha de propostas são:
+
+- _conteúdo original_: Conteúdo ainda não apresentado em outras conferências, ou um novo ângulo de um problema existente
+- _novos palestrantes_: Pessoas novas e que tem coisas interessante a dizer; Nós precisamos ouvir todos
+- _sem vendas_: Nós valorizamos fornecedores e patrocinadores, nos apenas não achamos que é o melhor local para isso. Você pode demonstrar em sua mesa.
+
+Regras:
+
+
Seja específico... nós não somos leitores de mente ( uma descrição com ao menos 20 linhas é algo desejável)
+
Detalhes são bons... explique porque sua palestra é interessante
+
Proponha sua própria palestra
+
Indicações são bem vindas... Se você conhece alguém com conteúdo/relevância em DevOps, por favor nos indique através do email {{< email_organizers >}}
+
Múltiplas propostas são bem vindas... apenas sigas todas as outras regras
+
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/conduta.md b/exampleSite/content/events/2016-portoalegre/conduta.md
new file mode 100644
index 000000000..f96f901e1
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/conduta.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "conduta"
+type = "event"
+
++++
+
+## Código de conduta
+
+O DevOpsDays é um evento sem fins lucrativos cujo principal objetivo é promover a troca de experiências entre os pessoas sobre a cultura DevOps no Brasil.
+
+Este Código de Conduta será aplicado para todos enquanto participantes desse evento para proteger o público de danos e perigos morais.
+
+Nos dedicamos a promover um evento respeitoso e livre de assédio para todos. Não toleramos qualquer forma de assédios ou intimidações de qualquer participante.
+
+Não devem utilizar imagens, atividades ou materiais de conteúdo sexual, homofóbico, pejorativo e/ou discriminatório de qualquer natureza.
+
+Por assédio entende-se sem limitação:
+
+
Comentários ofensivos, verbais ou eletrônicos, relacionados a características pessoais, origem racial, orientação sexual, identidade de gênero, bem como comentários ou imagens sexuais, racistas, homofóbicas ou discriminatórias de qualquer natureza em espaços públicos ou digitais;
+
Intimidação deliberada;
+
Bullying;
+
Perseguição;
+
Encalço;
+
Fotografias ou gravações que gerem embaraço;
+
Interrupções reiteradas de palestras, bate-papos, reuniões eletrônicas, reuniões físicas ou outros eventos;
+
Contato físico inadequado ou atenção sexual indesejada.
+
+Espera-se que os participantes cumpram imediatamente solicitações para descontinuar qualquer assédio ou comportamento de bullying. Sejam gentis com os outros. Não insultem ou ofendam outros participantes. Lembrem-se de que piadas de assédio, sexismo, racismo ou exclusão não são aceitas pela sociedade, muito menos para nosso evento.
+
+Qualquer participante que violar tais regras pode ser convidado a se retirar, a critério exclusivo dos organizadores do evento.
+
+Se um participante se engajar em comportamento de assédio, os organizadores do evento podem tomar medidas que considerem adequadas, desde alertas ao infrator até a vedação de sua participação em demais eventos promovidos pelos membros da organização individual ou coletivamente.
+
+Se você for assediado, perceber que alguém está sendo assediado, ou tem outras preocupações, por favor aja para interceptar ou peça ajuda aos organizadores. Estamos certos de que essa política ajudará a fazer do DevOpsDays um espaço mais acolhedor, inclusivo, e integrador para todos.
+
+Este Código de Conduta foi adaptado a partir do código de conduta utilizado pela comunidade GTC - Grupo de Testes Carioca, que foi adaptado pelo evento LinguÁgil, que foi adaptado pelo evento Agile Trends, que foi adaptado a partir dos códigos de conduta utilizados pelo Ideias em Produção, adaptados a partir do Python Brasil 9, este por sua vez adaptados dos códigos de conduta utilizados pela Plone Foundation e pela PyCon US, e estão licenciados sob a Creative Commons Attribution-Share Alike 3.0 Unported.
diff --git a/exampleSite/content/events/2016-portoalegre/contato.md b/exampleSite/content/events/2016-portoalegre/contato.md
new file mode 100644
index 000000000..5c8df982c
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/contato.md
@@ -0,0 +1,17 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "contato"
+type = "event"
+
+
++++
+
+Se você deseja falar conosco por e-mail: {{< email_organizers >}}
+
+**Nosso time local**
+
+{{< list_organizers >}}
+
+**O grupo central de organizadores do devopsdays**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-portoalegre/inicio.md b/exampleSite/content/events/2016-portoalegre/inicio.md
new file mode 100644
index 000000000..a32d548c6
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/inicio.md
@@ -0,0 +1,48 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "inicio"
+type = "event"
+aliases = ["/events/2016-portoalegre"]
+
++++
+
+## Sábado - 09 de julho de 2016
+
+DevOps Days será em {{< event_location >}}!
+
+
+
+
+
+
Localização
+
{{< event_location >}}
+
+
+
+
+
+
Patrocinadores
+
{{< event_link page="patrocinio" text="Patrocine o nosso evento" >}} Essa é uma grande forma de atrair novos talentos e promover sua organização.
+
+
+
Contatos
+
{{< event_link page="contato" text="Esteja em contato com os organizadores" >}}
+
+
+
+
+ {{< event_twitter poadevopsday >}}
+
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/local.md b/exampleSite/content/events/2016-portoalegre/local.md
new file mode 100644
index 000000000..2a3baf64e
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/local.md
@@ -0,0 +1,16 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "localização"
+type = "event"
+
++++
+
+O evento acontecerá na UniRitter, que fica na Rua Orfanotrófio, 515 - Alto Teresópolis, Porto Alegre.
+
+
+
+Auditório do Prédio C (subsolo), próximo a entrada do prédio C.
+
+Para mais informações sobre o local, veja nesse link
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/patrocinio.md b/exampleSite/content/events/2016-portoalegre/patrocinio.md
new file mode 100644
index 000000000..a2cd3ce23
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/patrocinio.md
@@ -0,0 +1,58 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "patrocínio"
+type = "event"
+aliases = ["/events/2016-portoalegre/sponsor"]
+
+
++++
+
+Se você está interessado em nos patrocinar, entre em contato pelo email [{{< email_organizers >}}].
+
+Material de patrocinadores:
+
+
+
+Para a proposta executiva completa, acesse esse link
+
+
+Alguns chamam DevOps de um fenômeno de transformação da cultura de como administrar e desenvolver serviços, outros acreditam que seja apenas uma metodologia ágil de administrar sistemas, mas uma coisa não há de se questionar. O termo DevOps foi cunhado em 2009, na cidade de Gante, que fica na Bélgica, em um evento chamado DevOpsDays.
+Desde então esse evento tem acontecido em várias cidades ao redor do mundo. Sempre tendo como objetivo principal disseminar essa nova metodologia/cultura sobre como os desenvolvedores e infraestrutura (operadores) devem trabalhar juntos para oferecer um resultado mais rápido, seguro e eficiente.
+
+DevOps é tido como um fenômeno por conta da rapidez como isso vem se espalhando pelo mundo. É possível perceber que essa tendência trouxe ótimos resultados para as organizações que a praticam, sempre proporcionado uma vantagem competitiva, segurança e agilidade na entrega do seu negócio.
+
+Empresas como Facebook, Rackspace, DigitalOcean, Google e muitas outras tem a cultura tão “enraizadas” que muitas vezes não se consegue perceber uma distinção entre os famosos papéis de “desenvolvedor” e “operador de infraestrutura”. A ideia é atuar como um time e assim proporcionar uma maior eficiência na entrega e manutenção.
+
+Por outro lado, a novidade do DevOps não se limita a novas práticas, pois com a mudança no paradigma da atividade proporcionou a criação de diversas ferramentas para auxiliar esse novo modelo de trabalho. E assim ferramentas de automação de infraestrutura, integração contínua, ambiente “self service” e muitas outras foram apresentadas até então, todas elas fortalecendo essa nova tendência.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/programa/bluegreen.md b/exampleSite/content/events/2016-portoalegre/programa/bluegreen.md
new file mode 100644
index 000000000..ce3cf3e6d
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/programa/bluegreen.md
@@ -0,0 +1,30 @@
++++
+City = "Porto Alegre"
+Year = "2016"
+title = "Pedro Cavalheiro"
+type = "talk"
+
++++
+
+
+
+
Palestra:
+ Blue-Green Deployment com Docker
+
+
+
Resumo:
+
+
+Blue-Green Deployment é uma técnica robusta e segura, que consiste em manter dois ambientes de produção identicos rodando em paralelo (blue e green), alternando o tráfego entre eles, conforme a necessidade. Esta abordagem permite uma redução no downtime durante o deploy, com a segurança de rollback no caso de falhas, mas exige mais máquinas e um complexo sistema de orquestração. Nesta palestra, é demonstrado como realizar deploys sem downtime através do Docker, que torna o processo incrivelmente fácil e simplificado.
+
+
+
Palestrante:
+Pedro Cavalheiro
+
+
+
+Trabalha com desenvolvimento de software há 6 anos, em sua maioria com PHP e Ruby (Rails). Durante este tempo, desenvolveu habilidades com diferentes linguagens e plataformas, sempre buscando testar abordagens diferentes, não se prendendo ao comum. Já trabalhou com Softwares ERP, agências digitais e software houses. Atualmente trabalha na Startup Me Salva!, um ambiente onde a inovação, comunicação e adaptação rápida fazem parte do dia-a-dia.
+
+Aplicações Web são o novo "normal" do mercado, todas as grandes idéias que surgem a cada dia invariávelmente possuem um endpoint exposto para a internet de forma pública, ainda mais impulsionados pela facilidade que os cloud providers oferecem para colocar uma aplicação no ar em minutos. Politica, concorrência e "diversão" são motivos pelos quais hoje tempos ataques de negação de serviço com amplitudes de 400Gb/s, e acredite a sua infraestrutura um dia terá que enfrentar esse cenário. Nesta palestra vamos abordar algumas das melhores práticas para garantir a resiliência da sua infraestrutura utilizando os recursos da AWS, quando tiver que segurar algumas requisições a mais.
+
+
+
Palestrante:
+Joao Palma
+
+
+
+Arquiteto de Soluções com foco em Cloud Computing. Viciado em estudar novas tecnologias e soluções inovadoras. Um dia foi um DBA Oracle, mas vamos falar de coisas boas, como NoSQL ! Me divirto na ilegra a 5 anos e no Movimento Escoteiro 10!
+
+Uma breve introdução sobre DevOps e algumas técnicas e ferramentas para ajudar a praticar DevOps em seu projeto e acelerar a sua entrega de software já! Nessa palestra serão abordadas algumas dicas sobre como captar oportunidades para praticar devOps em seu projeto bem como uma análise de caso de uso para ferramentas de automação de infra.
+
+
+
Palestrante:
+Fernanda Martins
+
+
+
+Atualmente desenvolvedora de software na TW, Fernanda atuou muito tempo como sysadmin lutando a favor da automatização e com o surgimento de DevOps encontrou seu chão. Seu objetivo é sempre automatizar de forma que tudo funcione com o aperto de um botão.
+
+
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/programa/dockerci.md b/exampleSite/content/events/2016-portoalegre/programa/dockerci.md
new file mode 100644
index 000000000..1a5598dbd
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/programa/dockerci.md
@@ -0,0 +1,50 @@
++++
+City = "Porto Alegre"
+Year = "2016"
+title = "Vinícius Fernandes de Jesus e Rodrigo Morais"
+type = "talk"
+
++++
+
+
+
+
Palestra:
+ Docker em CI
+
+
+
Resumo:
+
+
+Acabou de dockerizar a sua aplicação? Mas roda o CI com um outro ambiente? Que tal dar o próximo passo?
+
+
+Esta palestra mostra como reutilizar seu ambiente Docker de desenvolvimento no seu CI.
+
+
+Independente se o seu projeto é público ou privado, Docker sempre é uma boa opção para usar em todos os seus ambientes. Nessa palestra iremos mostrar como rodar suas tarefas no CI no mesmo ambiente docker utilizado no desenvolvimento.
+
+
+Para os projetos privados iremos apresentar a ferramenta DroneCI, demonstrando de como instalar, configurar e utilizar no seu projeto.
+
+
+Já para os projetos públicos a ferramenta apresentada será o popular Travis CI, exibindo como configurar e utilizar a mesma em seu projeto.
+
+
+
Palestrante:
+Rodrigo Morais
+
+
+
+Desenvolvedor de software com mais de 15 anos de experiência trabalhando com back e front-end. Aprendendo mais sobre info-estrutura e com a cultura DevOps, interessado em aplicar boas práticas na automaçāo de tarefas. Atualmente trabalhando na ThoughtWorks e aplicando os novos conhecimentos.
+
+
+
Palestrante:
+Vinícius Fernandes de Jesus
+
+
+
+Desenvolvedor de software, com experiência em desenvolvimento web, especialmente em Java e JavaScript, tanto front-end quanto backend. Recentemente tenho aprendido mais sobre a cultura DevOps e as ferramentas que a viabilizam.
+
+
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/programa/elk.md b/exampleSite/content/events/2016-portoalegre/programa/elk.md
new file mode 100644
index 000000000..5f418099b
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/programa/elk.md
@@ -0,0 +1,30 @@
++++
+City = "Porto Alegre"
+Year = "2016"
+title = "Waldemar Neto e Jefferson Stachelski"
+type = "talk"
+
++++
+
+
+
+
Palestra:
+ Métricas real-time com ELK
+
+
+
Resumo:
+
+
+O que é ELK e por que optamos por ele na hora de analisar as métricas de nossas APIs real-time.
+
+
+
Palestrante:
+Waldemar Neto e Jefferson Stachelski
+
+
+
+Consultores de software na ThoughtWorks, trabalham com APIs de alta disponibilidade.
+
+Nem sempre é possível adotar a cultura DevOps em um organização, principalmente em organizações com estruturas muito verticais e antiquadas, mas é possível pelo menos transformar a realidade do seu time.
+
+
+O modelo infra ágil é fortemente inspirado em DevOps mas tem foco em evoluir o modo de como os times de infraestrutura funcionam, proporcionando melhoria, controle e visibilidade de suas ações através de tecnologias modernas e métodos ágeis.
+
+
+Nesta palestra vamos falar da transição de uma infraestrutura clássica para uma infraestrutura ágil, abordando seis eixos de infraestrutura (Automação, Orquestração, Provisionamento, Deploy, Métricas e Pessoas) que precisam ser repensados e renovados para que sua infraestrutura se torne realmente ágil. Serão apresentados cases reais (Governo e iniciativa privada) de como isso funciona na prática.
+
+
+
Palestrante:
+Guto Carvalho
+
+
+
+Consultor, instrutor e especialista em TI com foco em automação e infraestrutura ágil. Entusiasta da cultura DevOps, procura adaptar métodos ágeis para tornar a infraestrutura de seus clientes mais eficientes e autônoma. Possui mais de 15 anos de experiência em TI em operação de datacenters governamentais e privados, mora atualmente em Brasília/DF. É arquiteto de automação e sócio na empresa Instruct Infraestrutura Ágil.
+
+
+
Palestrante:
+Miguel Di Ciurcio Filho
+
+
+Co-fundador da comunidade Puppet Brasil e foi o primeiro profissional certificado Puppet da América Latina. Participou do Google Summer Of Code no projeto QEMU e contribuiu com diversos projetos open source via patches, palestras e eventos. Em 2011 fundou a Instruct Infraestrutura Ágil e desde então dedica-se a oferecer consultoria e treinamentos sobre infraestrutura e automação em seu país. A Instruct é a única representante da Puppet e GitLab no Brasil oferecendo treinamentos, projetos e produtos.
+
Palestra:
+ Dissecando e entendendo pipelines de entrega de software
+
+
+
Resumo:
+
+
+Nesta palestra, pretendo abrir a mente dos profissionais que atuam no ciclo de desenvolvimento de software. Em 2016, ainda existe quem acredite que instalar um servidor de integracao continua e buildar o seu código fonte a cada commit é o suficiente.
+
+
+Alguns topicos a serem abordados na palestra:
+
+
+Como uma pipeline esta relacionada com DevOps/CD?
+
+
+Possíveis etapas de um pipeline:
+
+
+Verificacao de sintaxe
+
+
+Execução de testes unitários
+
+
+Compilação
+
+
+Métricas relacionadas ao código
+
+
+Testes funcionais automatizados
+
+
+Testes de historia de usuário
+
+
+Testes de aceitação automatizados
+
+
+Testes de funcionalidade
+
+
+Testes de comportamento
+
+
+Testes de componentes
+
+
+Testes de interfaces
+
+
+Testes isolados (mocks e stubs)
+
+
+Testes de integração
+
+
+Testes não funcionais automatizados
+
+
+Testes de segurança e performance
+
+
+Testes de verificação de deploy e de versão
+
+
+Testes de rede
+
+
+
+
Palestrante:
+Guilherme Motta
+
+
+
+Motta vem trabalhando com desenvolvimento de software desde 2005. Parte dessa jornada foi tecnica, dedicada ao desenvolvimento de software e a automacao de infraestrutura, gestao de ambientes, pipelines e como conciliar estrategias de testes automatizados com o ciclo de desenvolvimento.
+
Palestra:
+ Produção nove vezes ao dia - Como um time da rackspace torna isso possivel?
+
+
+
Resumo:
+
+
+Vamos apresentar quais técnicas e ferramentas são usadas no nosso time para garantir que as entregas em produção de um projeto com 5 anos de vida tenham valor e qualidade e sejam feitas 9 vezes ao dia, 5 dias por semana, 12 meses ao ano.
+
+
+
Palestrante:
+Bárbara Hartmann
+
+
+
+Programadora, técnica em Informática e aspirante a cientista da computação pela UFRGS. É consultora de desenvolvimento na ThoughtWorks, trabalhando com agilidade e linguagens como Ruby e Javascript, e participando de projetos como Rails Girls, Django Girls e Ignite Intertational Girls Hackaton. Acredita no poder de um código bem escrito e na mudança social através da tecnologia.
+
+
+
Palestrante:
+Eduardo Aquiles Radanovitsck
+
+
+Desenvolvedor na ThoughtWorks Brasil desde 2010, já andou pelos mundos do Java, .Net, Clojure e Javascript, automatizando tudo que passa pelo caminho. Nesse meio tempo, acabou trabalhando em NYC, Dallas, Charlotte, Glasgow, além de Porto Alegre.
+
+Nos nossos mais de 15 anos de experiência atuando diretamente em infraestrutura, observamos e participamos das evoluções, nos moldando conforme elas e buscando cada dia mais ser um diferencial no mercado. Nesta palestra temos como objetivo trazer este passado, presente e futuro a vocês não dando um caminho que vai levar ao sucesso mas sim como evitar alguns percalços que já passamos.
+
+
+Os dias de manutenção manual em sistemas de TI estão definitivamente terminados em grandes empresas, e cada vez mais assim também nas médias e pequenas. Hoje a infraestrutura é dinâmica, codificada, às vezes imutável, outras bem maleável, e os usuários esperam que as mudanças tenham efeito imediatamente, e que eles mesmos possam estar aptos a fazer a maioria dessas mudanças.
+
+
+A próxima geração de sysadmins precisa ter um perfil "Engenheiro de Infraestrutura" e vai implantar, configurar e dar manutenção a aplicações complexas e serviços através de uma amplitude de servidores, clientes, clouds, tablets, smartphones, torradeiras, carros etc etc etc. A sua infraestrutura precisa de ferramentas que empoderem o sysadmin para que ele adquira e expresse conhecimento escalável, compreensivo e ágil.
+
+
+
Palestrante:
+Diego Morales
+
+
+
+Diego Morales tem 15 anos de experiência em infraestrutura de TI e descobriu um pouco atrasado que deram o nome DevOps ao que ele praticava. Trabalha na Propus desenhando, implantando e operando soluções para ambientes corporativos de pequeno à grande porte, desbravando novos mundos com MongoDB e RabbitMQ, e automatizando tudo o que pode pela frente. Palestrante no FISL em 2013 e 2009. Co-coordenador das trilhas NoSQL no TDC Floripa 2016 e Infraestrutura ágil no TDC São Paulo 2016.
+
+
+
Palestrante:
+Christiano Linuxmen
+
+
+
+Sysadmin na Leme Consultoria, onde é responsável pela infraestrutura e por manter ambientes virtualizados. Fundador da Comunidade Ubuntu São Paulo, ajudou a fomentar a comunidade software livre no Brasil. Responsável pelo monitoramento de sistemas na ToolsCloud, garantindo um ambiente estável para desenvolvedores em todo o pais. Christiano idealizou e organizou o evento Desktop Livre, é colaborador assíduo de eventos de Software Livre tais como FISL, Latinoware, TDC, Campus Party etc.
+
+Esta apresentação visa mostrar como montar uma suite de testes que garanta qualidade com uma granularidade mais baixa e que não quebrem a cada refactoring.
+
+
+A aplicação usada é um orquestrador/API que iterage com dezena de interfaces, protocolos, módulos, componente e pode ser testada/executada na máquina no desenvolvedor ("oi, vc disse docker?")
+
+
+
Palestrante:
+Marcelo Adamatti
+
+
+
+Mais de 15 anos atuando com programação. Experiencia com JavaEE, Groovy, Node, JME, ESB, programação web.
+Líder tecnico na Ilegra.
+
+Manter todos seus arquivos de configuração de servidores em um sistema de versionamento é muito bom, inclusive arquivos com senhas, chaves de api e etc. Mas como fazer isso com segurança? A resposta é criptografia!
+Nessa palestra irei falar sobre Ansible Vault. Ferramenta que permite criptografar e descriptografar arquivos sensíveis que são usados pelos seus playbooks ansible.
+
+
+
Palestrante:
+Iury Alves de Souza
+
+
+
+Formado em Análise e Desenvolvimento de Sistemas pela Fatec São José dos Campos. Atualmente trabalho com python e DevOps na startup QMágico.
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/uniritter.jpg b/exampleSite/content/events/2016-portoalegre/uniritter.jpg
new file mode 100644
index 000000000..af2316290
Binary files /dev/null and b/exampleSite/content/events/2016-portoalegre/uniritter.jpg differ
diff --git a/exampleSite/content/events/2016-portoalegre/welcome.md b/exampleSite/content/events/2016-portoalegre/welcome.md
new file mode 100644
index 000000000..8958aeb20
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/welcome.md
@@ -0,0 +1,81 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "inicio"
+type = "event"
+aliases = ["/events/2016-portoalegre"]
+
++++
+
+## Sábado - 09 de julho de 2016
+
+DevOps Days será em {{< event_location >}}!
+
+
+
+
+
+
+ Localização
+
+
+ {{< event_location >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Patrocinadores
+
+
+ {{< event_link page="patrocinio" text="Patrocine o nosso evento" >}} Essa é uma grande forma de atrair novos talentos e promover sua organização.
+
+
+
+
+
+ Contatos
+
+
+ {{< event_link page="contato" text="Esteja em contato com os organizadores" >}}
+
+
+
+{{< event_twitter poadevopsday >}}
diff --git a/exampleSite/content/events/2016-raleigh/conduct.md b/exampleSite/content/events/2016-raleigh/conduct.md
new file mode 100644
index 000000000..082aab430
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/conduct.md
@@ -0,0 +1,42 @@
++++
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## HB2
+
+In light of the recent passage of House Bill 2, the organizers of DevOpsDays Raleigh would like to affirm our support of the DevOpsDays Code of Conduct. We are all personally committed to a policy of non-discrimination and will be taking that commitment seriously over the course of the event. The code of conduct will be prominently displayed upon registration and at various locations around the event to remind attendees that this will be a safe space for all.
+
+To make it easier for those who are considering attending, we are working to provide a list of local businesses (restaurants, hotels, etc.) that have identified as LGBTQA friendly. If you have any questions or concerns, please do not hesitate to reach out to the organizers: {{< email_organizers >}}
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-raleigh/contact.md b/exampleSite/content/events/2016-raleigh/contact.md
new file mode 100644
index 000000000..37c4e5f62
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/contact.md
@@ -0,0 +1,16 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-raleigh/location.md b/exampleSite/content/events/2016-raleigh/location.md
new file mode 100644
index 000000000..bb3f972a6
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/location.md
@@ -0,0 +1,41 @@
++++
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
Venue
+
+McKimmon Conference & Training Center
+ 1101 Gorman Street
+ Raleigh, NC 27606
+
+
Map/directions
+From I-40 traveling east from airport:
+ Take Gorman Street Exit #295.
+ Turn left onto Gorman Street.
+ Go approximately 1 mile.
+ McKimmon Center is on the right past Avent Ferry Road, before Western Boulevard.
+
+From I-40 traveling west:
+ Take Gorman Street Exit #295.
+ Turn right onto Gorman Street.
+ Go approximately 1 mile.
+ McKimmon Center is on the right past Avent Ferry Road, before Western Boulevard.
+
+Parking in the front lots of the McKimmon Center is free and usually plentiful. There are three smaller parking lots on each side of the Center that are reserved for University employees. Visitors are asked to park in designated visitor parking spaces in order to avoid ticketing.
+
+
Hotel Information
+We have secured a block of hotel rooms at the DoubleTree Brownstone at a reduced rate of $129/night. This offer expires on September 14th, 2016. Please use this link to reserve for the discounted price.
+
+Hotel Information:
+1707 Hillsborough Street
+Raleigh, North Carolina 27605
+USA
+Tel: +1-919-828-0811
+
+
+
Title:
+Context & Contingency: Patterns for choosing good tools
+
+
+
Description:
+
At Kickstarter, the Ops Engineering team recently deployed Elasticsearch/Logstash/Kibana to centralize application logs. I’ll use our implementation of the ELK stack as a case-study to examine our process for choosing tools, particularly:
+
+
+
when to build vs. buy
+
what features we need in the initial version, and what can wait until later
+
when to invest effort in an elegant solution, or when to get by with a hack.
+
+
This talk will discuss what factors influenced our decisions (context); and what future changes could lead to a different choice (contingency).
+
+
By capturing the context and contingency of our choices, we can more easily adapt to changes in our organization and the tech community.
+
+
I’ll show how our implementation decisions impacted the processes and behaviors of our team; which in turn influenced and reflected our organization’s culture.
+
+
+
+
+
+
+
Title:
+Code Is Communication
+
+
+
Description:
+
This is an invocation to give everyone in your organization access to your code and version control.
+
+
Version control brings radical transparency and context to our work. Let’s not keep it to ourselves! At Kickstarter, we’ve invited our entire staff to GitHub: customer support, HR, legal staff, everyone!
+
+
These teams contribute to the product and make pull requests. Our engineering team has benefited from having more inclusive conversations.
+
+
And the whole organization has benefited from embracing a culture of transparency and inclusion.
+
Professional Golf and Tennis tournaments plan all year to deliver a global sporting experience for several days or weeks. The computing infrastructure must be continuously available for millions of visitors that produce hundreds of thousands of concurrent sessions. IBM’s team that serves digital sporting experiences has transformed and adopted DevOps principals to build a multi-region hybrid public and private cloud. This hybrid cloud Infrastructure delivers Wimbledon, The French Open, Australian Open, The US Open, and The Masters.
+
+
+This talk will show you how to enable rapid and safe changes to critical cloud services when the world is watching your infrastructure.
+
+Your servers are purring like lolcats and you’ve got it all down to a science - but now everyone is talking about these new-fangled “containers”. Learn about integrating containers into a mature environment: new infrastructure and workflows, pitfalls, “ah-ha” moments, and re-considering the last decade or two of system administration practices.
Title:
+Your goat antifragiled my snowflake!: Demystifying DevOps Jargon
+
+
Description:
+
Are you a cow, a goat, a canary, or a unicorn? Are running K8S? Who the heck is Brent? Find out!
+
+Welcome to DevOps, where we are all about breaking down walls. But, we've created a private dialect, full of familiar words with unfamiliar meanings, and in-jokes upon in-jokes. Many newcomers wish there was a glossary for the movement. Time to be inclusive!
+
+In this fun session, we'll go over some of the more unintuitive terms (being a goat is a good thing!) and the backstories behind them.
+
Title:
+Customer Success: The Missing Link in the Feedback Loop to Engineering
+
+
+
Description:
+
Being responsible for the success of 10,000+ customers is a big challenge. This is especially true when success cannot be generalized to fit every customer.
+
+Using principles adopted from DevOps and Agile, we developed and implemented a new strategy to focus on our customers’ success. As a result, we discovered better insight into customer behavior, shortened feedback loops from customers to our product developers, and increased transparency between internal business units. This was all in an effort to better meet the needs of our customers and has been a huge success.
+
+In this talk, I’ll define Customer Success, show philosophical similarities to DevOps, and outline challenges we faced implementing Success into our organization.
+
+Audience members will learn:
+
+
+
How to strategically sell the idea and value of Customer Success internally. What it is, what it is not and how it affects each department in your organization
+
How to generate dynamic visuals with tailored data for business experts
+
How to promote internal collaboration through information transparency
+
How to turn a vision into reality by working as the hub of the wheel between engineering, product, marketing, sales and support
Title:
+"Is there any strong objection?" - How to have a (relatively) stress free time during an outage.
+
+
+
Description:
+
Major outages, incident calls, war rooms, whatever you want to label them, can be stressful and frustrating experiences. However, we aren't the only industry to have run into these problems. What can we learn from others on how to have a relatively stress free experience? How can we shorten the time that it takes to get back to a working state when things are broken?
+
+This talk will provide some comparisons to responses in other industries, and then go through several patterns and processes any team or company can use to have a quick, visible, and easy time responding to problems.
+
Do you need DevOps? Of course you do but how do you sell it to your team, managers and higher? With data! By telling a story with data we can analyze where the workflow is failing currently and if we can improve it and by how much! Focus on meaningful metrics and conversations rather than anecdotes
+
Infrastructure automation gets hairy when it comes to your databases, but it's also very important! Replication, sharding, fail-over, backup, and migration all need to be repeatable and testable. I'll introduce you to some of the yaks I've shaved to accomplish all this using Terraform and Ansible.
Title:
+How to be more open, collaborative, and inclusive at work
+
+
Description:
+
There are foundational reasons why collaboration and communication is highly valued by the Agile and DevOps communities. However, much of the industry focuses on software tooling, rather than providing foundations to help with improving culture. When the industry thinks about the human parts of Agile and DevOps, they often think about things like Scrum, Kanban, Extreme Programming, or alternatively, how much they will not do one of those things. Yet experienced practitioners will tell you that the standard methodologies like Scrum and Kanban are significantly less important than the method you use to communicate with your coworkers.
+
+This session will explore the Open Decision Framework, a FOSS project management and decision-making resource built upon the foundational principles of open source: transparency, collaboration, community, rapid prototyping, and meritocracy.
+
+You will get tips and ideas for how to gain support and buy-in for your ideas, manage conflicting opinions and priorities, limit unintended impacts, and help improve the overall trust across your team and organization by focusing on transparent decision-making.
+
Title:
+How to Evolve Ops Skills to a DevOps World
+
+
Description:
+
DevOps certainly changes the way software is developed, tested, and delivered. This has put new challenges on IT operations whether it be managing new cloud offerings, or having to learn new skills to enable success. This session provides focus for attendees who may hold traditional operations roles. We'll discuss how traditional operations skills, both soft and technical, are applied to enable a DevOps culture, and ultimately provide more value to the organization.
+
With emergence of DevOps approach to application development, deployment and management developers get more and more involved in day-to-day system operations. Lately, there has been a popular point of view that developers should be included in oncall rotation on equal grounds with sys admins. While I don't fully subscribe to that mentality, there are certain processes that must be implemented by every organization to get developers involved in production operation of the software they built. In this talk I'll walk through different aspects of operational oncall responsibilities and discuss ways in which developers should (and should not) be involved in operation of production systems.
Title:
+My Gaming Days Weren’t Wasted: How Gaming Trained Me for Testing in DevOps
+
+
Description:
+
Recognize me from my EA game credits? After many years as a gamer and in game testing, I began working as a QA engineer for a Boulder tech startup focused on DevOps.
+
+In this talk I’ll explain how I applied my game testing experience to test and improve enterprise software applications. Participants will take away helpful tips from game testing that they can use in their own environment. In the talk, I’ll share:
+
+
+
Why it helps to have a background in testing games when testing a DevOps application
+
How gamers and enterprise software customers have similar traits and needs
Title:
+Speaking for the Dead: Is "Waterfall" and "Monolithic" Actually Good?
+
+
+
Description:
+Computer technology is often cyclical. In the past, we've seen serial and parallel cable transports alternate. We've seen a resurgence in technology originally popularized in mainframes, and then abandoned. We've seen old dusty languages become cool and popular. For this talk, we'll focus on something a bit different - we are currently in the middle of a push towards a multitude of microservices and hyper-agile development methodologies, often deeply interlinked. Yet, for some reason, we still struggle for efficiency, to hit deadlines, and more - and these approaches themselves pose new challenges.
+
+
+What if more monolithic applications and more planned development processes wasn't a bad thing? Can we strip the reality from the connotation of these words? In this presentation, Michael will attempt to prove there are some good lessons left to pull from the 90s and early 2000s, and will share a few reasons why you may also want to get off his lawn.
+
Need to make a proposal to a decision maker to justify a Devops investment? Participate in a discussion on how to propose, describe and justify an investment in Devops practices to a skeptical executive audience. We will discuss how to break down potential benefits into business outcomes as well as the perspective of the typical IT executive.
+
+We will anticipate common objections you might face and how to prepare for them. We will also identify some typical goals and common assumptions. Finally, we will outline a simple business case as an example.
+
There are foundational reasons why collaboration and communication is highly valued by the Agile and DevOps communities. However, much of the industry focuses on software tooling, rather than providing foundations to help with improving culture. When the industry thinks about the human parts of Agile and DevOps, they often think about things like Scrum, Kanban, Extreme Programming, or alternatively, how much they will not do one of those things. Yet experienced practitioners will tell you that the standard methodologies like Scrum and Kanban are significantly less important than the method you use to communicate with your coworkers.
+
+This session will explore the Open Decision Framework, a FOSS project management and decision-making resource built upon the foundational principles of open source: transparency, collaboration, community, rapid prototyping, and meritocracy.
+
+You will get tips and ideas for how to gain support and buy-in for your ideas, manage conflicting opinions and priorities, limit unintended impacts, and help improve the overall trust across your team and organization by focusing on transparent decision-making.
+
During this Ignite talk we will demystify some common misconceptions about DevOps. We will help answer such questions as "What about change control?", "What stops a developer from releasing unacceptable code?", and hush the phrases "but that's that's my job" or "that's not my job".
+
Title:
+Continuous Integration: a bittersweet love story
+
+
+
Description:
+
This is the bittersweet story of Continuous Integration. CI is practice that we fell in love with, embraced and then never fully committed to. I’ll share with you the current state of CI, what we think we are doing when we say CI and what we are really doing in terms of CI. Then I’ll remind us all why we fell in love with CI in the first place and make some suggestions on how to get back to the good stuff.
+
Tech company culture has a reputation for it's lavish benefits, but in many ways it's all a facade. Ping pong and free lunches are cool and can be great for recruitment, but that's not what makes people stay. So what does? Treating each other like adults.
+
+
+
diff --git a/exampleSite/content/events/2016-raleigh/proposals.md b/exampleSite/content/events/2016-raleigh/proposals.md
new file mode 100644
index 000000000..a35357aa1
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/proposals.md
@@ -0,0 +1,13 @@
++++
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-raleigh/propose.md b/exampleSite/content/events/2016-raleigh/propose.md
new file mode 100644
index 000000000..e312bced6
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/propose.md
@@ -0,0 +1,31 @@
++++
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
diff --git a/exampleSite/content/events/2016-raleigh/speakers.md b/exampleSite/content/events/2016-raleigh/speakers.md
new file mode 100644
index 000000000..c835e3d1a
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-10-06"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-raleigh/sponsor.md b/exampleSite/content/events/2016-raleigh/sponsor.md
new file mode 100644
index 000000000..f70d58b4e
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/sponsor.md
@@ -0,0 +1,76 @@
++++
+
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+
Sponsorship Packages
+
+
Platinum Sponsor ($5000) - SOLD OUT
+
+* 3 tickets included
+* Table Space
+* Logo on Website, Main Room Signage & Email Communications
+* 3 Minute Pitch to Full Audience on Day One
+
+
Gold Sponsor ($3000) - SOLD OUT
+
+* 2 tickets included
+* Table Space
+* Logo on Website, Main Room Signage & Email Communications
+
+
Silver Sponsor ($1000)
+
+* 2 tickets included
+* Logo on Website, Main Room Signage & Email Communications
+
+
+
A la carte opportunities (also available without sponsorship purchase):
+
+* Cocktail hour ‐ $5000
+* Logo on conference bag ‐ $2500
+* Lanyard sponsor ‐ $500
+* Bag inserts ‐ $250
+* Other opportunities available upon request
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-raleigh/volunteer.md b/exampleSite/content/events/2016-raleigh/volunteer.md
new file mode 100644
index 000000000..df4ae7620
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/volunteer.md
@@ -0,0 +1,14 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "volunteer"
+type = "event"
+
++++
+
+## Volunteer for DevOpsDays Raleigh 2016
+
+Many hands make light(er) work. We need a few good folks to come and help make DevOpsDays Raleigh really awesome. If you're interested in helping with registration, helping with Open Spaces, or more – please fill out this form and we'll be in touch!
+
+
+
+
diff --git a/exampleSite/content/events/2016-raleigh/welcome.md b/exampleSite/content/events/2016-raleigh/welcome.md
new file mode 100644
index 000000000..b54708648
--- /dev/null
+++ b/exampleSite/content/events/2016-raleigh/welcome.md
@@ -0,0 +1,88 @@
++++
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-raleigh"]
+
++++
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2016-saltlakecity/welcome.md b/exampleSite/content/events/2016-saltlakecity/welcome.md
new file mode 100644
index 000000000..41a599fc8
--- /dev/null
+++ b/exampleSite/content/events/2016-saltlakecity/welcome.md
@@ -0,0 +1,50 @@
++++
+City = "SaltLakeCity"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-saltlakecity"]
+
+
++++
+
+## DevOps Days is coming to the Silicon Slopes!
+
+**For the most up to date information, visit our official page by clicking the image below**
+
Sponsor the event! It's a great way to attract new talent and promote your organization.
+
+
+
Contact
+
{{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+ {{< event_twitter devopsdaysslc >}}
+
+
+
diff --git a/exampleSite/content/events/2016-seattle/conduct.md b/exampleSite/content/events/2016-seattle/conduct.md
new file mode 100644
index 000000000..7819340a6
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-03-06T21:17:08-06:00"
+title = "DevOpsDays Seattle 2016 - Code of Conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-seattle/contact.md b/exampleSite/content/events/2016-seattle/contact.md
new file mode 100644
index 000000000..bf107a5ef
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "DevOpsDays Seattle 2016 - Contact Information"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+** Our local team**
+
+{{< list_organizers >}}
+
+** The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-seattle/location.md b/exampleSite/content/events/2016-seattle/location.md
new file mode 100644
index 000000000..16661a625
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/location.md
@@ -0,0 +1,12 @@
++++
+date = "2016-03-06T21:17:00-06:00"
+title = "DevOpsDays Seattle 2016 - Location"
+type = "event"
+
++++
+
+The 2016 event was held at Sheraton Seattle Metropolitan Ballroom - 1400 6th Ave, Seattle, WA 98101
+
+We want to thank everyone at the venue, especially Anthony, Riley and Cory for helping us make the event as smooth as possible!
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-seattle/program.md b/exampleSite/content/events/2016-seattle/program.md
new file mode 100644
index 000000000..b5af4ee68
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/program.md
@@ -0,0 +1,146 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "DevOpsDays Seattle 2016 - Program"
+type = "event"
+
++++
+
+
Open Space Opening Introduction and session nominations
+
+
14:00-14:45
attendee-suggested Open Space breakout discussions Open Space #1
+
+
15:00-15:45
attendee-suggested Open Space breakout discussions Open Space #2
+
+
16:00-16:45
attendee-suggested Open Space breakout discussions Open Space #3
+
+
17:00
Close Day & Farewell
+
+
+
diff --git a/exampleSite/content/events/2016-seattle/proposals.md b/exampleSite/content/events/2016-seattle/proposals.md
new file mode 100644
index 000000000..411e53054
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals.md
@@ -0,0 +1,13 @@
++++
+date = "2016-03-06T21:28:14-06:00"
+title = "DevOpsDays Seattle 2016 - Proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-seattle/proposals/An_unlikely_happy_couple_DevOps_and_IT_Audit.md b/exampleSite/content/events/2016-seattle/proposals/An_unlikely_happy_couple_DevOps_and_IT_Audit.md
new file mode 100644
index 000000000..78038286c
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/An_unlikely_happy_couple_DevOps_and_IT_Audit.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-13T12:14:21-07:00"
+title = "An unlikely happy couple, DevOps and IT Audit"
+type = "talk"
+
++++
+
+**Abstract:**
+
+Some of us may be surprised to hear that DevOps and Continuous Delivery are not necessarily an IT auditor's nightmare. In fact, reducing organizational risk a the primary goal that is shared between GRC and delivery teams using DevOps and Continuous Delivery. In this session, Joanne will walk you through the things you should be doing and thinking about as a delivery team to demonstrate to GRC and audit teams that this is a better way to work to reduce overall organizational risk.
+
+**Speaker:** Joanne Molesky
diff --git a/exampleSite/content/events/2016-seattle/proposals/Being_an_introvert_at_a_conference_is_not_as_hellish_as_you_think.md b/exampleSite/content/events/2016-seattle/proposals/Being_an_introvert_at_a_conference_is_not_as_hellish_as_you_think.md
new file mode 100644
index 000000000..c62093e03
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Being_an_introvert_at_a_conference_is_not_as_hellish_as_you_think.md
@@ -0,0 +1,18 @@
++++
+date = "2016-04-16T10:10:21-07:00"
+title = "Being an introvert at a conference is not as hellish as you think"
+type = "talk"
+
++++
+
+**Abstract:**
+
+I'd like to give some advice on how to deal with conferences as an introvert.
+Over the last couple years I've grown and learned to engage with the tech community
+in ways that an introvert would find challenging. This talk will hopefully help
+the audience avoid some of the landmines that I have stepped on.
+
+I want to help out my fellow introverts to realize that it's OK to be an introvert
+at big conferences. We can enjoy them too.
+
+**Speaker:** JJ Asghar
diff --git a/exampleSite/content/events/2016-seattle/proposals/Building_an_Enterprise_DevOps_Community.md b/exampleSite/content/events/2016-seattle/proposals/Building_an_Enterprise_DevOps_Community.md
new file mode 100644
index 000000000..e98fc49be
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Building_an_Enterprise_DevOps_Community.md
@@ -0,0 +1,14 @@
++++
+date = "2016-04-13T12:14:41-07:00"
+title = "Building an Enterprise DevOps Community"
+type = "talk"
+
++++
+
+**Abstract:**
+
+Enterprises can sprawl across many different verticals, with unique challenges such as compliance, seasonal demand and sudden market shifts. Under these challenges however are some commonalities that enable the creation of a broader community which can unify them.
+
+I will share my experiences with helping to build DevOps cultures and principles in ten business units and how building a broader community helped to bring them together. Looking at culture, process and tools I will share the approaches that enabled higher levels of engagement and support for all involved.
+
+**Speaker:** Pauly Comtois
diff --git a/exampleSite/content/events/2016-seattle/proposals/Combat_Chaos_Driven_Delivery_by_thinking_like_an_OS.md b/exampleSite/content/events/2016-seattle/proposals/Combat_Chaos_Driven_Delivery_by_thinking_like_an_OS.md
new file mode 100644
index 000000000..175595f8a
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Combat_Chaos_Driven_Delivery_by_thinking_like_an_OS.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-16T10:10:21-07:00"
+title = "Combat Chaos-Driven Delivery by thinking like an OS"
+type = "talk"
+
++++
+
+**Abstract:**
+
+Have you heard of TDD? Well, many teams struggle with CDD: Chaos-Driven Delivery. That is, teams struggle with how to handle the constant onslaught of overwhelming amounts of work and begin to lose hope. The good news is that if you understand operating systems, you already know a great deal about how to tame the chaos!
+
+**Speaker:** Julia Wester
diff --git a/exampleSite/content/events/2016-seattle/proposals/DevOps_at_Expedia_Local_Expert.md b/exampleSite/content/events/2016-seattle/proposals/DevOps_at_Expedia_Local_Expert.md
new file mode 100644
index 000000000..89cb7a6c9
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/DevOps_at_Expedia_Local_Expert.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-16T10:10:21-07:00"
+title = "DevOps at Expedia Local Expert"
+type = "talk"
+
++++
+
+**Abstract:**
+
+Expedia Local Expert started with no API over 3 years ago and a very small web footprint, however in the last few years we’ve created a development and operations organization which runs on the fuel of the DevOps fundamentals. This has allowed our business to grow at a phenomenally rate and redefine IT in the Expedia culture and share that with the community
+
+**Speaker:** Chad Buffett
diff --git a/exampleSite/content/events/2016-seattle/proposals/How_Container_Clusters_like_Kubernetes_change_operations.md b/exampleSite/content/events/2016-seattle/proposals/How_Container_Clusters_like_Kubernetes_change_operations.md
new file mode 100644
index 000000000..049b42bb0
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/How_Container_Clusters_like_Kubernetes_change_operations.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "How Container Clusters, like Kubernetes, change operations"
+type = "talk"
+
++++
+
+**Abstract:**
+
+One of the core principles of the project is that it decouples operations and operations roles via abstraction layers that enable specialization and focus that both reduces the cost of operations as well as increasing the quality.
+
+**Speaker:** Brendan Burns
diff --git a/exampleSite/content/events/2016-seattle/proposals/How_DevOps_could_have_saved_the_Super_Sonics.md b/exampleSite/content/events/2016-seattle/proposals/How_DevOps_could_have_saved_the_Super_Sonics.md
new file mode 100644
index 000000000..96e3da153
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/How_DevOps_could_have_saved_the_Super_Sonics.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "How DevOps Could’ve Saved the SuperSonics"
+type = "talk"
+
++++
+
+**Abstract:**
+
+This is a touchy subject but if only the NBA had been employing some DevOps principles, perhaps Seattle would still have a basketball team. Failed communication? Huge silos unwilling to work together? No empathy? Holes in the culture? Seattle team leadership and the community had a lack of collaboration, resulting in no new plans for a stadium and an eventual relocation. A hungry buyer wanting a team in OKC saw the opportunity, snatched them up and moved them. It sounds like the SuperSonics had a few issues that might have been helped by DevOps concepts. In this talk, I’ll look at how these principles have helped other area sports teams (ex. Sounders) and how they can ensure your team doesn’t suffer the same outcome.
+
+**Speaker:** Adam Lefkowitz
diff --git a/exampleSite/content/events/2016-seattle/proposals/How_to_survive_and_thrive_in_a_big_company.md b/exampleSite/content/events/2016-seattle/proposals/How_to_survive_and_thrive_in_a_big_company.md
new file mode 100644
index 000000000..312d02355
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/How_to_survive_and_thrive_in_a_big_company.md
@@ -0,0 +1,15 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "How to survive and thrive in a Big Company"
+type = "talk"
+
++++
+
+**Abstract:**
+
+If you work at a small, cool company, you can skip this talk. The rest of us in large, slow moving companies that rely on meetings, email, and inbox 2,000 to get the daily work done need some therapy and advice for thriving in big, "dumb" companies. I've worked in such companies and figured out how to thrive in the "back to back meetings" world we're taught to avoid. I'll tell you my tactics.
+Ideally, you’d adapt the no manager GitHub dream, adapt the Spotify and Netflix cultures of awesomeness. Indeed. However, oftentimes there are good reasons to stay in the relatively dysfunctional companies you’re at. They’re big, slow moving, and seem to use Microsoft Office as their core innovation engine.
+If people at your work always talk about “aircraft carriers” this is the talk for you.
+For whatever reasons you’re there, why not make the best of it and learn how to get along and even thrive instead of letting your head explode in rage. This talk will go over what I’ve learned working in large companies from my strange adventure working with a bunch of MBAs in corporate strategy at Dell, to working with large companies as an industry analyst, to working with marketing and product people at large companies.
+
+**Speaker:** Michael Coté
diff --git a/exampleSite/content/events/2016-seattle/proposals/Living_in_a_Hybrid_World.md b/exampleSite/content/events/2016-seattle/proposals/Living_in_a_Hybrid_World.md
new file mode 100644
index 000000000..384c4f4a3
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Living_in_a_Hybrid_World.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "Living in a Hybrid World"
+type = "talk"
+
++++
+
+**Abstract:**
+
+We have been on a journey to transition to a modern tech stack for our customer-facing product teams. I will share how we are evolving our culture, mindsets, behaviors, processes, and technology to achieve the outcome of increased speed to value.
+
+**Speaker:** Courtney Kissler
diff --git a/exampleSite/content/events/2016-seattle/proposals/Moving_from_SysAdmin_to_DevOps.md b/exampleSite/content/events/2016-seattle/proposals/Moving_from_SysAdmin_to_DevOps.md
new file mode 100644
index 000000000..94dfbaa52
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Moving_from_SysAdmin_to_DevOps.md
@@ -0,0 +1,14 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "Everything you always wanted to know about moving from a regular sysadmin role to a DevOps role (but were afraid to ask)"
+type = "talk"
+
++++
+
+**Abstract:**
+
+I was the regular enterprise sysadmin: network administrator & datacenter systems engineer in an ISP, IT operation support administrator in a retail company and IT systems engineer in a software development company. I spent time on choosing cool names for my servers. I knew the exact location of a server in the datacenter. I felt sad when their lights stopped blinking. I felt more sad it that happened on a weekend night.
+
+And then I joined a team adopting the DevOps mindset. Let me be honest: change was scary! But it was also a great learning experience. This talk will share what was challenging and what worked for me in my transition from being a regular sysadmin to living and breathing DevOps.
+
+**Speaker:** Oguz Pastirmaci
diff --git a/exampleSite/content/events/2016-seattle/proposals/My_First_Year_at_Chef_Measuring_All_the_Things.md b/exampleSite/content/events/2016-seattle/proposals/My_First_Year_at_Chef_Measuring_All_the_Things.md
new file mode 100644
index 000000000..e85a07f85
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/My_First_Year_at_Chef_Measuring_All_the_Things.md
@@ -0,0 +1,13 @@
++++
+date = "2016-04-13T10:56:22-07:00"
+title = "My First Year at Chef: Measuring All the Things"
+type = "talk"
+
++++
+
+**Abstract:**
+
+
+So what happens when you're brought in to a team and asked to "introduce a metrics culture" or "measure all the things?" This talk will cover just that: how to assess the state of affairs in your team or organization regarding measurement, how to decide what things to measure for maximum impact, and how to best communicate and iterate those measurements throughout the journey. The talk will cover these topics using my own journey at Chef as well as journeys I see at other companies that I meet and consult with.
+
+**Speaker:** Nicole Forsgren
diff --git a/exampleSite/content/events/2016-seattle/proposals/Past_The_Hype_A_Better_Way_To_Think_About_Big_Data.md b/exampleSite/content/events/2016-seattle/proposals/Past_The_Hype_A_Better_Way_To_Think_About_Big_Data.md
new file mode 100644
index 000000000..5d6863eee
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Past_The_Hype_A_Better_Way_To_Think_About_Big_Data.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "Past The Hype: A Better Way To Think About Big Data"
+type = "talk"
+
++++
+
+**Abstract:**
+
+The Big Data hype is over and it’s time to actually get results. Not easy when Big Data has been so overhyped, Berkeley University compiled a list of 40 competing, contradictory definitions. But to those who really understand Big Data, it’s a competitive advantage on par with computers or the internet itself. The key is to understand that Big Data is really a collection of different technologies all vaguely clumped together by those who either don't know better or vendors who thinks ambiguity helps sales. As Thomas Davenport said, "Vendors and consultants will take any new, hot term and apply it to their existing offerings…and that has already happened in spades with Big Data." In this talk, Big Nimble founder Michael Kauffman cuts through the techno-babble and marketing fog to explain what Big Data actually is and how to use it.
+
+**Speaker:** Michael Kauffman
diff --git a/exampleSite/content/events/2016-seattle/proposals/The_Power_of_A3_Thinking_in_Action.md b/exampleSite/content/events/2016-seattle/proposals/The_Power_of_A3_Thinking_in_Action.md
new file mode 100644
index 000000000..d75c2e64a
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/The_Power_of_A3_Thinking_in_Action.md
@@ -0,0 +1,16 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "The Power of A3 Thinking in Action"
+type = "talk"
+
++++
+
+**Abstract:**
+
+LEAN concepts have penetrated all layers of business over the last 30 years, particularly: PDCA, Kaizen, Continuous Improvement, and Continuous Learning. These 4 things are in fact one in the same, but they are often seperated and confused by different groups. Those from the world of frameworks, best practice, and compliance see PDCA as a project management tool. DevOps champions the Retrospective as a means for Continious Learning and Improvement. The LEAN and Six Sigma purists invoke Kaizen as a "events" in which improvement can be sought out.
+
+Sadly few practitioners have ever looked deeply at the practices of Toyota and the philosophies which lead to their great achievements which came to be known in America as "LEAN". In this talk we'll peer deeply into the greatest power tool available to practitioners and managers alike, the A3 Report, which has the extraordinary power to clarify, organize, and execute on the problems that you face day to day.
+
+Whether your bedroom is a mess or your Operations team seems to be running in circles, the simple power of A3 Thinking can provide the framework you need to stop trying and start doing.
+
+**Speaker:** Ben Rockwood
diff --git a/exampleSite/content/events/2016-seattle/proposals/The_first_50_nodes_the_story_of_our_journey_at_a_Windows-centric_enterprise.md b/exampleSite/content/events/2016-seattle/proposals/The_first_50_nodes_the_story_of_our_journey_at_a_Windows-centric_enterprise.md
new file mode 100644
index 000000000..0c6c392fd
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/The_first_50_nodes_the_story_of_our_journey_at_a_Windows-centric_enterprise.md
@@ -0,0 +1,21 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "The first 50 nodes... the story of our journey at a Windows-centric enterprise"
+type = "talk"
+
++++
+
+**Abstract:**
+
+In this talk we’ll discuss our own journey at Columbia Sportswear including:
+* Overcoming the “yeah windows can already do everything you want us to do”
+* Overcoming the “we don’t run Linux and this can’t work here"
+* Getting Engineers to buy in that they current skillset will not sustain them
+* Finding a couple of early adopters
+* Finding allies (peers) in the organization
+* Using a series of experiments to incrementally converge on version control, exposing work, kanbans, demos, etc.
+* Optimizing the automation to be as inviting as possible (yes we did some hard coding at times)
+* Starting the organization on the path to becoming a learning organization
+* Tempering enthusiasm to keep the entire team moving forward
+
+**Speaker:** Scott Nasello
diff --git a/exampleSite/content/events/2016-seattle/proposals/Understanding_Cognitive_Bias_Found_In_Judgement_and_Choice.md b/exampleSite/content/events/2016-seattle/proposals/Understanding_Cognitive_Bias_Found_In_Judgement_and_Choice.md
new file mode 100644
index 000000000..fccd53242
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Understanding_Cognitive_Bias_Found_In_Judgement_and_Choice.md
@@ -0,0 +1,12 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "Understanding Cognitive Bias Found In Judgement & Choice"
+type = "talk"
+
++++
+
+**Abstract:**
+
+There are distinctive patterns in the errors that all of us make. Systematic mistakes known as biases, along with impressions and thoughts, form within our conscious experience. This occurs naturally without us knowing they are even there or how they came about. The mental work that produces these impressions, intuitions, and decisions takes place silently within our mind. However, mistakes recur predictably under particular circumstances. Those circumstances are what we’ll focus on in this talk. Heuristics, (or mental shortcuts), are an intuitive judgements based on experiences and impressions from our past. We rely on those heuristics to approach problem solving, and especially within the context of decision making under uncertainty. Such as dealing with service disruptions or some other incident related to availability. Reliance on those heuristics often cause predictable errors in our reasoning, decision making, predictions and any common puzzle. We are often extremely confident even when we are blatantly wrong. When the constraints and pressures of “Time To Repair” influence our cognitive efforts, systematic errors are introduced into our judgements and choices. Our minds are easily susceptible to bias, and considerations of efficiency over thoroughness can amplify these errors even more. The goal of this talk is to improve the ability to identify and understand errors in judgement and choice. Through a deeper understanding of heuristics and of the biases to which they lead, improvements in judgement and decision-making under situations of uncertainty, such as a system-wide outage should be gained.
+
+**Speaker:** Jason Hand
diff --git a/exampleSite/content/events/2016-seattle/proposals/Why_Weekends_Matter.md b/exampleSite/content/events/2016-seattle/proposals/Why_Weekends_Matter.md
new file mode 100644
index 000000000..d559ca589
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/proposals/Why_Weekends_Matter.md
@@ -0,0 +1,14 @@
++++
+date = "2016-04-13T12:18:48-07:00"
+title = "Why Weekends Matter"
+type = "talk"
+
++++
+
+**Abstract:**
+
+Excluding weekends from your metrics reports may sound appealing when the goal is to reduce lead-time and/or cycle-time in your workflow. From a reporting perspective, it’s nice to show improvement, so why not exclude times when people aren’t thought to be working? This strongly opinionated ignite talk exposes three serious reasons why excluding weekends from time metrics reporting can get you into deep kimchi.
+
+Disclosure: I am an organizer for Devopsdays Seattle and therefore ineligible to participate in the discussion or voting of this proposed ignite talk.
+
+**Speaker:** Dominica DeGrandis
diff --git a/exampleSite/content/events/2016-seattle/propose.md b/exampleSite/content/events/2016-seattle/propose.md
new file mode 100644
index 000000000..a8c9b5e91
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/propose.md
@@ -0,0 +1,13 @@
++++
+date = "2016-03-06T22:47:24-06:00"
+title = "DevOpsDays Seattle 2016 - Propose a talk"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+
+
Call for proposals is now closed.
+
Check out our selected talks and ignites on our program
+
diff --git a/exampleSite/content/events/2016-seattle/registration.md b/exampleSite/content/events/2016-seattle/registration.md
new file mode 100644
index 000000000..74b9a15b6
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/registration.md
@@ -0,0 +1,11 @@
++++
+date = "2016-03-06T21:28:23-06:00"
+title = "DevOpsDays Seattle 2016 - Registration"
+type = "event"
+
++++
+
+We're all done!
+----
+
+We hope to see you in 2017! If you're in the Pacific Northwest and can't wait, check out DevOpsDays Portland in August 2016.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-seattle/sponsor.md b/exampleSite/content/events/2016-seattle/sponsor.md
new file mode 100644
index 000000000..242773e5c
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/sponsor.md
@@ -0,0 +1,11 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "DevOpsDays Seattle 2016 - Sponsor Information"
+type = "event"
+
++++
+
+Thank you sponsors!
+====
+
+It is no exaggeration to say that we could not have run the event without the generous support from our sponsors. With their support, we were able to keep the cost of a ticket lower than the actual cost for food & beverage alone for an individual. We were also able to make the event available to others who might not have otherwise been able to attend.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-seattle/welcome.md b/exampleSite/content/events/2016-seattle/welcome.md
new file mode 100644
index 000000000..9ec80d4c4
--- /dev/null
+++ b/exampleSite/content/events/2016-seattle/welcome.md
@@ -0,0 +1,24 @@
++++
+date = "2016-03-06T21:15:25-06:00"
+title = "DevOpsDays Seattle 2016"
+type = "event"
+aliases = ["/events/2016-seattle"]
+
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+ {{< event_logo >}}
+
+Seattle's first DevOpsDays is "in the books". If you were able to attend, we hope you enjoyed it as much as we did!
+
+Videos of the event will be posted here in the coming weeks.
+
+Thank you to our great speakers!
+
+Thank you to our great sponsors!
+
+{{< event_twitter DevOpsDaysSEA >}}
+
diff --git a/exampleSite/content/events/2016-siliconvalley/conduct.md b/exampleSite/content/events/2016-siliconvalley/conduct.md
new file mode 100644
index 000000000..0a7a38cb5
--- /dev/null
+++ b/exampleSite/content/events/2016-siliconvalley/conduct.md
@@ -0,0 +1,42 @@
++++
+date = "2016-04-30T23:16:05-07:00"
+title = "conduct"
+type = "event"
++++
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+* Local law enforcement: Mountain View Police - call 911
+* Sexual assault hotlines: YWCA SV (408) 295-4011 ext 232
+* Medical Emergency: Call 911
+* Local taxi companies: Yellow Taxi Cab (650) 993-3500
+
+##ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+##CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-siliconvalley/contact.md b/exampleSite/content/events/2016-siliconvalley/contact.md
new file mode 100644
index 000000000..fc2e6cc96
--- /dev/null
+++ b/exampleSite/content/events/2016-siliconvalley/contact.md
@@ -0,0 +1,16 @@
++++
+date = "2016-04-30T23:13:44-07:00"
+title = "contact"
+type = "event"
++++
+
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+** Our local team**
+
+{{< list_organizers >}}
+
+** The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-siliconvalley/location.md b/exampleSite/content/events/2016-siliconvalley/location.md
new file mode 100644
index 000000000..521ab75c1
--- /dev/null
+++ b/exampleSite/content/events/2016-siliconvalley/location.md
@@ -0,0 +1,22 @@
++++
+date = "2016-04-30T23:15:12-07:00"
+title = "location"
+type = "event"
++++
+
DevOpsDays Silicon Valley 2016 Diversity Scholarship
+
+
+DevOpsDays Silicon Valley believes that diversity is critical to a healthy community and its growth. So one of our goals is to address the lack of diversity in attendees at our conference.
+
+
+We realize that one barrier to attending conferences is that people may not have the privilege of working at a job that affords conference attendance. To that end, we are announcing scholarship tickets to DevOpsDays Silicon Valley. We do have some funds for additional assistance (such as airfare, lodging, childcare or gas) so please let us know if you have those needs in the form below!
+
+
+
We will also have a Conference Liaison who can assist on site.
+
+
+
+
diff --git a/exampleSite/content/events/2016-siliconvalley/sponsor.md b/exampleSite/content/events/2016-siliconvalley/sponsor.md
new file mode 100644
index 000000000..2befdb9e2
--- /dev/null
+++ b/exampleSite/content/events/2016-siliconvalley/sponsor.md
@@ -0,0 +1,18 @@
++++
+date = "2016-04-30T23:16:15-07:00"
+title = "sponsor"
+type = "event"
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}} or sign up directly here.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold and Silver sponsors get a full table where they can interact with those interested to come visit during breaks. In addition Gold sponsors will be invited to 2 minute pitch on the main stage to the full audience (including streaming). Bronze sponsors will get a shared shared swag table. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+For more details please click HERE to download the full sponsor prospectus for DevOpsDays Silicon Valley 2016!
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
diff --git a/exampleSite/content/events/2016-siliconvalley/welcome.md b/exampleSite/content/events/2016-siliconvalley/welcome.md
new file mode 100644
index 000000000..18edfc4cc
--- /dev/null
+++ b/exampleSite/content/events/2016-siliconvalley/welcome.md
@@ -0,0 +1,83 @@
++++
+City = "Silicon Valley"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-siliconvalley"]
+
++++
+
+## devopsdays returns to Silicon Valley June 24-June 25!
+
+
+ View the {{< event_link page="program" text="program." >}}
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+
+ Scholarship
+
+
+ {{< event_link page="scholarship" text="Apply for a Scholarship" >}}
+
+
+
+
+{{< event_twitter devopsdayssv >}}
+
diff --git a/exampleSite/content/events/2016-singapore/conduct.md b/exampleSite/content/events/2016-singapore/conduct.md
new file mode 100644
index 000000000..11cfda06d
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Singapore"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-singapore/contact.md b/exampleSite/content/events/2016-singapore/contact.md
new file mode 100644
index 000000000..3a3deb2fd
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/contact.md
@@ -0,0 +1,24 @@
++++
+City = "Singapore"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+## Important addresses
+
+* Email address for organizers: {{< email_organizers >}}
+* Singapore Emergency Contact list: [http://www.e101.gov.sg/learn_contacts.html](http://www.e101.gov.sg/learn_contacts.html)
+* Local law enforcement: Singapore Police Force - call 999
+* Sexual assault hotline: 1800 774 5935
+
+## Our local team
+
+{{< list_organizers >}}
+
+## The core devopsdays organizer group
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-singapore/location.md b/exampleSite/content/events/2016-singapore/location.md
new file mode 100644
index 000000000..3802b80ac
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/location.md
@@ -0,0 +1,42 @@
++++
+City = "Singapore"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+# The Venue
+
+Atrium Ballroom
+Level 4, Raffles City Convention Centre
+Fairmont Singapore & Swissôtel The Stamford
+80 Bras Basah Road | Singapore 189560
+MRT station: [City Hall](http://www.smrt.com.sg/Trains/NetworkMap/CityHall) Exit A.
+
+We’re on level 4. Follow the signs to ‘Convention Centre’.
+
+
+
+
+ Latency analysis is the act of blaming components for causing user perceptible delay. In today's world of microservices, this can be tricky as requests can fan out across polyglot components and even data-centers.
+
+ This session will overview how to debug latency and better understand your production environment with Zipkin. You'll see a demo and leave knowing how to get started with distributed tracing.
+
+ Standards and Best Practices - everyone talks about them but how do you get a team of 30 engineers to follow standards? How do you ensure, that while following standards, innovation is not stifled?
+
+
+ Devops is equally top-down, as it is bottom-up. It is the central body that aims to reduce the pain points of developers, while delivering a reliable and mostly predictable system.
+
Are we bridging the cultural divide that is necessary for DevOps to succeed
+
+ Discussion about the pitfalls and problems we are facing when trying to implement DevOps either bottom up or top down. Putting tools aside, in my travels across APAC I see breakdowns occurring with organizations that are not executing well when it comes to DevOps. For instance in India and China and Korea and Japan it is very slow, in Singapore and Australia and NZ it is picking up, but still with lots of room for improvement. How can we all together get better adoption of DevOps and ultimately get better code into production to support business outcomes.
+
DevOps: A cultural primer and practical lessons learnt
+
+ DevOps is a complicated topic. It’s not enough and sometimes harmful to just form a DevOps team. There is no such thing as a DevOps Cure-all. But, if your development and operations teams start to collaborate you are on the right track!
+
+
+ This talk will break DevOps down into its core ideas with an emphasis on learning from mistakes constructively and organizing teams effectively with supporting data from our annual State of DevOpsReport. Primarily a process and culture talk, the audience should come with an interest in DevOps and the talk is meant for both software and operations engineers as well as their management. A mix is best as aligning business goals is key to success
+
+ Shows how you can explain the difference between simple, complicated and complex environments - and how certain ways of managing them fit their nature - to your team/management who still think DevOps is a hipe and will go away if you just wait long enough. In short: yes, you can try to manage a complex environment with your simple environment strategies and tools. But you will fail. Change your strategy and call it what you like - but change!
+
+ Lessons learnt from our internal DevOps transformation. Learn how Microsoft’s Developer Division transformed from an organization that shipped software every few years, to one that delivers value to customers every three weeks.
+
+ This talk will focus on the journey to adopting DevOps within your organisation. Many conversations we have with our customers start with “How will this deliver business value?”. We will aim to answer this question and show you steps of which you can take to truly understand what the DevOps culture is really about. We will also provide some quick wins that any organisation can begin to adopt without the big “DevOps transformation project”. To begin to quantify and justify the feasibility of a DevOps transformation, we will delve into the different areas required to help you build a business case to ensure you get your ROI.
+
Workshop - Creating a Continuous Delivery Pipeline: A Hands-On Workshop
+
+ Although continuous delivery (CD) and DevOps are growing in popularity, not much practical information is available about how to get started. This hands-on technical tutorial is the place to get your feet wet and your questions answered.
+
+
+ Bring a laptop with the appropriate software installed (see note below), and Ken Mugrage will provide everything else you need for this workshop. You will configure a complete continuous delivery pipeline from source code commit through deployment. Learn when to run each common type of automated test for the fastest possible feedback and how to run tests in parallel for shorter cycle times. Moving from practice to theory, Ken explores industry studies and peer-reviewed scientific research that show the value of practicing continuous delivery and adopting a DevOps culture. He describes how the need for CD developed and then fed the requirements for culture change to support DevOps and CD practices.
+
+
+ In this workshop, learn how to create and then practice creating a continuous delivery pipeline—from the ground up.
+
+
+
When
+
+
+
Audience
+ Anyone.
+
+
Requirements
+ Laptop Required — This workshop, designed for software professionals, requires no continuous delivery or DevOps experience. Delegates should bring a laptop with the latest versions of Virtualbox and Vagrant installed.
+
+ Beyond containerization and configuration management, the horizon for DevOps suggests a need for real-time, reactive and reflexive automation patterns that can adapt an infrastructure to changing conditions. What will this look like and how will we achieve it?
+
+ For years we all worked under the (incorrect) assumption that going faster meant breaking things. After several years of science-ing, Nicole has identified the key elements that enable not just higher throughput but also higher stability and quality, lower cost, and happier teams. Discover how continuous delivery and lean management practices produce higher IT performance (and indeed what we might mean by IT performance), along with how to measure culture and its impact on IT and organizational culture.
+
+
+ Find out how we actually ensure our results are reliable and meaningful. Learn the patterns and practices used by high performing organizations to outcompete their peers.
+
Building Infrastructure for Massive Open Online Course
+
+ DevOps is about bringing Development and Operations together, with my talk the audience will learning how to build MOOC architecture that run on the web platform using the last technologies like Django, Celery, Ansible, WebAPI, ect.
+
+
+ MOOC is future of education, learn comprehensive guide to building the architecture is one of the requirement to bring good technology for future education.
+
Workshop - Modern Infrastructure with Terraform & Consul
+
+ This is a comprehensive, engineer-led course that covers two of HashiCorp's tools - Consul and Terraform. Topics include provisioning and managing infrastructure with Terraform, monitoring infrastructure with Consul, building reactive infrastructure with Consul tools, and using Atlas to manage and monitor infrastructure in a team environment.
+
+ Example subjects include:
+
+ More and more companies are switching to Agile and DevOps methodologies to enable continuous delivery. And while development is becoming faster and faster and new features are released on a daily basis, application security is struggling to keep up. For the most part application security seems to be stuck in the dark ages of waterfall.
+
+
In this talk I will discuss a new approach to application security that enables Agile development teams to ship software at DevOps speed.
+
+ With it's 300 microservices architecture, each with their own types of messaging queue and datastores. There was a need to have an interface between the application developers and devops so that we could provide numerous services such as autoscale, recovery, backup, monitoring and security along with maximum visibility into our systems. The talk will describe this "interface" and how it's used to provide "ops as a service".
+
+
When
+
+
+
diff --git a/exampleSite/content/events/2016-singapore/proposals.md b/exampleSite/content/events/2016-singapore/proposals.md
new file mode 100644
index 000000000..8c7cb9a04
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/proposals.md
@@ -0,0 +1,38 @@
++++
+City = "Singapore"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+This page lists the talk proposals and workshops we have chosen.
+
+# Keynotes
+
+1. [Mitchell Hashimoto - Keynote](/events/2016-singapore/program/mitchell-hashimoto)
+2. [Nicole Forsgren - Keynote - Sciencing the Crap Out of DevOps](/events/2016-singapore/program/nicole-forsgren)
+
+# Conference Talks
+
+3. [Adrian Cole - An Introduction to Distributed Tracing and Zipkin](/events/2016-singapore/program/adrian-cole)
+4. [Jason Man - I want DevOps, but how do I justify it?](/events/2016-singapore/program/jason-man)
+5. [Mike Place - Event-driven automation](/events/2016-singapore/program/mike-place)
+6. [Brett Gray - DevOps: A cultural primer and practical lessons learnt](/events/2016-singapore/program/brett-gray)
+
+# Ignite Talks
+
+1. [Clemri Steyn - 7 Habits of successful DevOps](/events/2016-singapore/program/clemri-steyn)
+2. [Benjamin Henshall - Are we bridging the cultural divide that is necessary for DevOps to succeed](/events/2016-singapore/program/benjamin-henshall)
+3. [Stefan Streichsbier - Security in an Agile World OR Security at DevOps Speed](/events/2016-singapore/program/stefan-streichsbier)
+4. [Ion Mudreac - Beyond DevOps ?](/events/2016-singapore/program/ion-mudreac)
+5. [Angad Singh - Devops and Standards](/events/2016-singapore/program/angad-singh)
+6. [Seth Vargo - 10 Tips to Create a Toxic Tech Team](/events/2016-singapore/program/10-tips-to-create-toxic-tech-team)
+7. [Clemens Perz - Can't keep it simple, stupid!](/events/2016-singapore/program/clemens-perz)
+
+# Workshops
+
+1. [HashiCorp - Modern Infrastructure with Terraform & Consul](/events/2016-singapore/program/seth-vargo)
+2. [ThoughtWorks - Creating a Continuous Delivery Pipeline: A Hands-On Workshop](/events/2016-singapore/program/ken-mugrage)
+3. [Ansible - From Zero to Best Practices](/events/2016-singapore/program/will-thames)
diff --git a/exampleSite/content/events/2016-singapore/propose.md b/exampleSite/content/events/2016-singapore/propose.md
new file mode 100644
index 000000000..89194ea4c
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/propose.md
@@ -0,0 +1,14 @@
++++
+City = "Singapore"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+
+
+
Call for proposals is closed
+
+The program is {{< event_link page="program" text="announced." >}}
+
diff --git a/exampleSite/content/events/2016-singapore/registration.md b/exampleSite/content/events/2016-singapore/registration.md
new file mode 100644
index 000000000..64fac50b2
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/registration.md
@@ -0,0 +1,12 @@
++++
+City = "Singapore"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+
+
+
diff --git a/exampleSite/content/events/2016-singapore/speakers.md b/exampleSite/content/events/2016-singapore/speakers.md
new file mode 100644
index 000000000..cb9106679
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-09-07T22:15:03+08:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-singapore/sponsor.md b/exampleSite/content/events/2016-singapore/sponsor.md
new file mode 100644
index 000000000..9b766c779
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/sponsor.md
@@ -0,0 +1,269 @@
++++
+City = "Singapore"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email or [download the prospectus](https://drive.google.com/open?id=0B-L7Gu-eJct3em15bzFreGZWMU5jVnZ6S2pyckl2TGpZY053) right away.
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute the attendee contact lists.
+
+Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+## Why Sponsor Us?
+
+The DevOpsDays event mandate is to bring the highest quality speakers, experts, and the curious together.
+
+Singapore is not only one of the fastest growing startup hubs in the world but is also a trusted healthcare, telecom, and financial services nexus in Asia with strong investment in technology from the Government. We aim to attract representation from large enterprises and the startup community alike.
+
+By sponsoring DevOpsDays, you will be exposing your organizations brand and services to Singapore and Southeast Asia’s top talent in this rapidly growing space.
+
+Sponsoring DevOpsDays Singapore connects your company to some of the greatest technical and business minds in the industry who are influencing decisions in security, monitoring, operations, engineering, quality, and organisational change.
+
+## The Venue
+
+DevOpsDays Singapore 2016 will be held at the [Atrium Ballroom in the Raffles City Convention Centre](http://www.swissotel.com/hotels/singapore-stamford/meeting-events/ballrooms/atrium-ballroom/) ([80 Bras Basah Road, Level 4](https://www.google.com/maps/place/Raffles+City/@1.2938362,103.8529555,17z/data=!4m2!3m1!1s0x0000000000000000:0xcfcde1c1d52b371c)), in the middle of one of Singapore’s numerous cultural hubs. Many attractions are within walking distance and the location is well connected with public transport ([map](https://www.google.com/maps/place/Raffles+City/@1.2938362,103.8529555,17z/data=!4m2!3m1!1s0x0000000000000000:0xcfcde1c1d52b371c)).
+
+
+
+## Booth Space
+
+Gold and Platinum sponsors receive booth space at the event. This is the perfect spot for your engineers to meet other tech geeks. Your booth space will have a booth table (185 cm x 80 cm) and two chairs. You can set up your table as you like, be it to display signage, products, materials, or swag giveaways. We encourage sponsors to send engineers to interact with attendees during session breaks.
+
+Large displays and oversized marketing material are not allowed in the exhibitor space. Please check with the organizers if your items fall under the restricted category. You may ship your booth materials to the venue prior to the event day.
+
+
+
+
+# SPONSORSHIP PACKAGES
+
+Our sponsorship packages are structured around how you can help be part of the conference.
+
+
+
+
+
Packages
+
Silver 1500 SGD
+
Gold 5,000 SGD
+
Platinum 12,500 SGD
+
+
+
# available
+
+ unlimited
+
+
+ 6
+
+
+
+ 2
+
+
+
+
+
Logo on {{< event_link page="welcome" text="DevOpsDays Singapore" >}} event website
Complimentary attendee tickets (workshops not included*)
+
1
+
3
+
6
+
+
+
Logo on shared slide, rotating during breaks
+
+
+
+
+
+
No. of mentions in social media and outgoing material
+
1
+
2
+
4
+
+
+
Logo size in print program
+
+
Regular
+
Large
+
+
+
No. of swag in goodie bag - requires approval
+
+
1
+
2
+
+
+
Dedicated Booth/table space
+
+
+
+
+
+
Discount on add-on sponsor packs
+
10%
+
25%
+
40%
+
+
+ * Please reach out to us if you would like to purchase workshop passes. We have workshop only special pricing for our sponsors.
+
SPONSOR PACK ADD-ONS
+ In addition to the main sponsorship levels described in the table above, below are the add-on packages that can be purchased in addition to a core sponsorship package.
+
+
+
+
+
Packages
+
Description
+
# available
+
Cost
+
+
+
Lunch time talk
+
Give a 15 minute talk during lunch hour on day one of the conference. Content to be approved by organisers
+
2
+
2500 SGD
+
+
+
Drink Sponsor
+
Sponsor the drinks for the social event happy hour and have your signage and logo at the bar
+
2
+
1500 SGD
+
+
+
Logo on attendee badge
+
Your logo will be placed on the attendee name badge. Size and placement to be determined by organizers.
+
+
+## THE SMALL PRINT
+
+WE CANNOT RELEASE ATTENDEE INFORMATION; SIZE & PLACEMENT OF LOGOS VARY ACCORDING TO SPONSORSHIP; PLEASE PROVIDE US WITH A VECTOR / HIGH RESOLUTION LOGO FOR THE PRINT PROGRAM. ALL INCLUDING GST.
+
+TO ALLOW US SUFFICIENT TIME TO PREPARE FOR AND ORGANISE THE MARKETING AND OTHER RELEVANT ACTIVITIES, PLEASE PROVIDE IN A TIMELY MANNER YOUR LOGO AND OTHER RELEVANT MATERIALS OR INFORMATION REQUIRED FOR SUCH PURPOSES.
+
+
+## Sponsor FAQ
+
+### Can you send me a floor plan?
+
+You can find the floor plan and directions to the venue here.
+
+### How big is our booth space?
+
+Gold and Platinum sponsors receive booth space at the event. You will receive a table (185 x 80 cm) and two chairs that you can decorate as you like. This is how the standard table looks like:
+
+
+
+### When can we pick our booth spot?
+
+Booths are not selectable. Our team will assign your table. Assignments will be made two weeks before the conference date.
+
+You can enter the venue Saturday morning at 7:30 am to set up your table.
+
+### How many scanners (and which type) do we get?
+
+None. The booth is a place to talk to people during breaks and this conference is not a typical conference or convention.
+
+We have seen that sponsors benefit the most when they bring engineers to the conference and interact with the attendees during the sessions. You are responsible to collect any information you want in person if you want to do giveaways.
+
+### Can we bring a 1m roll-up as our back wall?
+
+Whatever you bring must fit behind or on your table (185 x 80 cm).
+
+### Will we have any chairs at our booth?
+
+Each booth comes with 2 chairs.
+
+### Will there be a company sign at our booth? When do you need the graphics?
+
+You must bring your own signage and all signage must either fit on or behind the table.
+
+### Do we get any sponsored talks?
+
+No, but you are welcome to submit a proposal for consideration through our CfP form.
+
+### How many talk tracks do you have?
+
+It's a single-track program. You find more details on the program on {{< event_link page="program" text="our program page" >}}.
+
+### Do we get electricity connection for out booth?
+
+Yes, you will get a power strip (Plug Type G).
+
+### Will wifi connection be good enough for showing demos?
+
+We do not provide Wifi. Wifi has to be booked as extra on the venue.
+
+### Do we get an advertising in the program? When do you need the graphics?
+
+We will be using the logos that are sent by you.
+
+### Do we get a dedicated email blast?
+
+No, even better: we will give you a Twitter shout out.
+
+### Who should I send?
+
+Not marketing folks. Send your techie geeks that can interact with attendees during the sessions and the breaks.
+
+### How do I pay the sponsorship package?
+
+Invoices will be handled by our conference partner. You will receive an invoice including GST, if applicable.
+
+For this, we need the official business address, full name of your contact and GST number.
+
+### How do we register our sponsor tickets?
+
+Once payment is complete, we will send you an email requesting registration details of the attendees that will use the tickets associated with your sponsorship level.
+
+### How many people do you expect?
+
+We are planning for 150 attendees.
+
+### What kind of attendees will come to the conference?
+
+We are focusing on people who are architecting and building distributed applications or doing migration projects, especially those away from monolithic software. This will typically include Architects, Lead Developers, and IT-Operations.
+
+### Do you have media partners who will cover the conference?
+
+No; however, if you have an idea to support the event in the media, please let us know!
+
+### Can we ship stuff ahead?
+
+Yes. Please send us an email so we can work out the details.
+
+### Can we lock things at the venue during the event?
+
+Yes. There is a shared room where you can stash stuff. Access is organized by the venue itself.
+
+### My question is not covered here. What can I do?
+
+If you have any questions not answered above, please do not hesitate to send us an email at organizers-singapore-2016@devopsdays.org
+.
diff --git a/exampleSite/content/events/2016-singapore/the_sponsor_area.jpg b/exampleSite/content/events/2016-singapore/the_sponsor_area.jpg
new file mode 100755
index 000000000..83c0c6ed9
Binary files /dev/null and b/exampleSite/content/events/2016-singapore/the_sponsor_area.jpg differ
diff --git a/exampleSite/content/events/2016-singapore/the_venue.jpg b/exampleSite/content/events/2016-singapore/the_venue.jpg
new file mode 100755
index 000000000..202cd5c31
Binary files /dev/null and b/exampleSite/content/events/2016-singapore/the_venue.jpg differ
diff --git a/exampleSite/content/events/2016-singapore/welcome.md b/exampleSite/content/events/2016-singapore/welcome.md
new file mode 100644
index 000000000..38b29e318
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/welcome.md
@@ -0,0 +1,91 @@
++++
+City = "Singapore"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-singapore"]
+
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+This 2-day event brings together development and operations professionals from Singapore and around the world. It is organized by people who care about DevOps, for people who care about collaboration, automation, measurement, and improvement.
+
+DevOpsDays are are organized frequently around the globe and this is the first conference in Singapore designed to bridge the gap between development and operations, providing a platform to
+
+- Share Experiences and Ideas
+- Get Advice
+- Learn from your Peers
+- Check out New Tools
+- And much more!
+
+
+ View the {{< event_link page="program" text="program." >}}
+
+
+
+
+
+ Speakers
+
+
+ Check out the {{< event_link page="proposals" text="speakers!" >}}
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+ {{< event_twitter devopsdayssg >}}
+
+
diff --git a/exampleSite/content/events/2016-sydney/conduct.md b/exampleSite/content/events/2016-sydney/conduct.md
new file mode 100644
index 000000000..d3b8bc4c2
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-08-23T19:14:51+10:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-sydney/contact.md b/exampleSite/content/events/2016-sydney/contact.md
new file mode 100644
index 000000000..6ea13b28e
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-08-23T19:14:51+10:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-sydney/location.md b/exampleSite/content/events/2016-sydney/location.md
new file mode 100644
index 000000000..ba0cdd11f
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-08-23T19:14:51+10:00"
+title = "location"
+type = "event"
+
++++
+
+### DevOpsDay Sydney 2016 will be held at the Sydney SMC Conference and Function Centre
+
+
diff --git a/exampleSite/content/events/2016-sydney/program.md b/exampleSite/content/events/2016-sydney/program.md
new file mode 100644
index 000000000..2283ddbcc
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/program.md
@@ -0,0 +1,349 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
The Schedule
+
+
+
+
+
+
+
+
Day 1
+
+
+
+
+
+
+
+
+ Registration Arrival tea & coffee
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+ Opening Keynote
+ {{< program_link speaker="bridget-kromhout" title="Containers will not fix your broken culture (and other hard truths)">}}
+ Bridget Kromhout
+
+
+
+
+
+
+
+
+ {{< program_link speaker="hannah-browne-steve-mactaggart" title="Why?: the forgotten word of DevOps" >}}
+ Hannah Browne & Steve Mactaggart
+
+
+
+
+
+
+
+
+ Open spaces brainstorm
+
+
+
+
+
+
+
+
+ Morning tea
+
+
+
+
+
+
+
+
+ {{< program_link speaker="patrick-robinson" title="10 rules of automation" >}}
+ Patrick Robinson
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Lunch
+
+
+
+
+
+
+
+
+ Open Spaces intro
+
+
+
+
+
+
+
+
+ Open Space #1
+ Room 1: Ops Team planning/Tracking Metrics
+ Room 2: How to sell the "Why" to our organisations
+ Room 3: How to run integration tests with microservices
+
+
+
+
+
+
+
+
+ Open Space #2
+ Room 1: Teaching Ops
+ Room 2: Infra as code with multiple teams
+ Room 3: Patching all the immutable things \o/
+
+
+
+
+
+
+
+
+ Afternoon tea
+
+
+
+
+
+
+
+
+ Open Space #3
+ Room 1: How to do documentation right
+ Room 2: Improving Communication & Mentoring Junior team members
+ Room 3: Container orchestration
+
+
+
+
+
+
+
+
+ Closing Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration Arrival tea & coffee
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+ {{< program_link speaker="lindsay-holmwood" title="Deepening our people, to weather the org" >}}
+ Lindsay Holmwood
+
+
+
+
+
+
+
+
+ {{< program_link speaker="peter-hall" title="Functions as a Service: Beyond the rainbow" >}}
+ Peter Hall
+
+
+
+
+
+
+
+
+ Open spaces brainstorm
+
+
+
+
+
+
+
+
+ Morning tea
+
+
+
+
+
+
+
+
+ {{< program_link speaker="mujtaba-hussain" title="Do small data sets dream of big data?" >}}
+ Mujtaba Hussain
+
+
+
+
+
+
+
+
+ {{< program_link speaker="donny-nadolny" title="Three years of breaking things to make them better" >}}
+ Donny Nadolny
+
+
+
+
+
+
+
+
+ Lunch
+
+
+
+
+
+
+
+
+ Closing Keynote
+ {{< program_link speaker="nigel-kersten" title="Abstractions and Metaphors: words matter in operations" >}}
+ Nigel Kersten
+
+
+
+
+
+
+
+
+ Open Spaces intro
+
+
+
+
+
+
+
+
+ Open Space #1
+ Main Stage: Arrested DevOps Podcast
+ Room 1: More 'dev' in the 'ops'
+ Room 2: What is tradional project management
+ Room 3: DevOps for DB admin
+
+
+
+
+
+
+
+
+ Afternoon tea
+
+
+
+
+
+
+
+
+ Open Space #2
+ Room 1: War Stories
+ Room 2: Management and Leadership
+ Room 3: Building better containers with Habitat
+
+
+
+
+
+
+
+
+ Open Space #3
+ Room 1: Security and DevOps
+ Room 2: Hiring Best Practice
+ Room 3: Convincing the business to retire the old stuff
+
+
+
+
+
+
+
+ Closing Day & Farewell
+ Followed by Conference Retro
+
Title:
+Containers will not fix your broken culture (and other hard truths)
+
+
+
Description:
+Containers will not fix your broken culture. Microservices won’t prevent your two-pizza teams from needing to have conversations with one another over that pizza. No amount of industrial-strength job scheduling makes your organization immune to Conway's Law.
+
+Does this mean that devops has failed? Not in the slightest. It means that while the unscrupulous might try to sell us devops, we can't buy it. We have to live it; change is a choice we make every day, through our actions of listening empathetically and acting compassionately. Iterative improvement starts somewhere for us all; let’s talk about it.
+
+Tools are essential, but how we implement the tools and grow the culture and practices in our organizations needs even more attention. Whether you’re just starting to implement technical and organizational change, or facing the prospect that you already have legacy microservices, it's worth considering the why and the how of our behaviors, not just the what.
+
+
Title:
+Three years of breaking things to make them better
+
+
+
Description:
+
+
+For three years PagerDuty has run "Failure Friday", a weekly exercise that uses simple failures like killing a process or adding network latency to expose problems in our systems and alerting. This talk will share what we've learned in that time: how our fault injection techniques have changed, the best way to get started injecting failures in your own environment, and how you can use it to improve your software as well as your people.
+
+We all know DevOps is not about the tools or the process, it’s about a deeper cultural movement. But all too often we think about what DevOps is, and miss the focus on Why we do it in the first place.
+
+
In this presentation we explore:
+
+
+
The organisational context that is most likely to support a successful DevOps initiative
+
What questions you should be asking and how to frame the conversation when engaging with organisational leaders and non technical colleagues
+
How to connect the key values a DevOps initiative can generate with real business problems
Title:
+Deepening our people, to weather the org
+
+
+
Description:
+
+
+Devops is about changing technical culture. But technical culture isn’t created in a vacuum – it's nurtured and reinforced by the broader organisational culture our tech orgs are part of.
+
+
+That culture comes from people – our artifacts, beliefs, and assumptions. Unless we deepen our people's skills, knowledge, and experience, we'll get the culture change we deserve.
+
+
+What does technical culture change look like, and how does it survive? And why are people the hardest but most important piece of the puzzle to change?
+
+As a startup, it's imperative to have a firm grasp of the way your user base interacts with your product in order to progress and improve. In this talk, I will outline how we at Fillr, went from spending money on Facebook to get users, to using data from our own users to get more users, and save a whole heap of money along the way. At the end of the presentation, the attendees will hopefully have a better understanding of the challenges that this approach poses, and the benefits of taking them head on like:
+
+
+
How to work with a very small user base to generate usage patterns.
+
Why advertising on Facebook was of no consequence to us.
+
How to setup data visualisation mechanisms and save money while doing it.
+
Using usage patterns to further expand and improve your product.
+
Building retention patterns to check your assumptions and fail quick.
+
Introduce experimentation, rapid failure to every facet of your product lifecycle based on data accumulated.
+
Investing in your team to improve both their skills and your product.
+
Why learnings is not a word.
+
How to remove gut feel and guesswork from your workplace.
+
+
+This presentation will have a very big emphasis on
+
+
+
Open source software, both taking from and contributing back.
+
Real world examples of collaborating across the business between UX, engineering and our CEO.
+
Using Elasticsearch, Cornelius, d3js to set up a system of data visualisation to enable the entire business to analyse our growth.
+
Explanation of what Gandalf could have learnt from the DevOPS movement.
Title:
+Abstractions and Metaphors: words matter in operations
+
+
+
Description:
+
+
+Is a retrospective better than a post-mortem? Is an incident room better than a war-room? Working in the automation/operations space we deal with abstractions and metaphors constantly, even when it's unconscious. In this talk we'll be taking a quick tour through some interesting linguistic theories around metaphor and abstraction, and discuss how our thoughts and actions in our space are shaped by the metaphors we use.
+
+The basis of the talk comes from Patrick's experience automating the wrong way, and the things he's learned doing it again. It's easy to look at a problem and think "I know I'll automate it!". This can be an easy trap to fall into. Automation does not make robust maintainable platforms; but when combined with a well grounded knowledge of building systems (particularly distributed systems) is a powerful tool.
+Patrick will explore the common pitfalls:
+
+
+
automating error prone processes
+
choosing the wrong tool
+
overly complex automation
+
automating pets
+
placing your automation at the wrong end of the pipeline
+
+
+In the end Patrick hopes to show participants how automation, used judiciously, can be extremely effective. Patrick will likely also delve into a recent project he worked on, successfully migrating an Alexa top 1000 site to AWS.
+
Title:
+Functions as a Service: Beyond the rainbow
+
+
+
Description:
+
+
+Serverless and AWS lambda is generating a lot of attention at the moment. But what is it really like to live with services without the servers? What does this new deployment style mean for development teams trying to get things done? What about operations? Do we even need dedicated ops people when this becomes the norm? At REA we have been experimenting with Lambda for quite some time now, in this talk I’ll share some experiences and lesions we have learnt along the way. I’ll also try and answer the above questions and where I see this going from here.
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-sydney/propose.md b/exampleSite/content/events/2016-sydney/propose.md
new file mode 100644
index 000000000..ee067a235
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/propose.md
@@ -0,0 +1,35 @@
++++
+date = "2016-08-23T19:14:51+10:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-sydney/registration.md b/exampleSite/content/events/2016-sydney/registration.md
new file mode 100644
index 000000000..ffc2f8f74
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/registration.md
@@ -0,0 +1,11 @@
++++
+date = "2016-08-23T19:14:51+10:00"
+title = "registration"
+type = "event"
+
+
++++
+
+
+
+
diff --git a/exampleSite/content/events/2016-sydney/speakers.md b/exampleSite/content/events/2016-sydney/speakers.md
new file mode 100644
index 000000000..5d6d143b1
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-11-03T22:49:01+10:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2016-sydney/sponsor.md b/exampleSite/content/events/2016-sydney/sponsor.md
new file mode 100644
index 000000000..756de8373
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/sponsor.md
@@ -0,0 +1,50 @@
++++
+date = "2016-08-23T19:14:51+10:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us
+ an email at [ [sponsors-sydney-2016@devopsdays.org](mailto:sponsors-sydney-2016@devopsdays.org) ]
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-sydney/welcome.md b/exampleSite/content/events/2016-sydney/welcome.md
new file mode 100644
index 000000000..9d32b09d5
--- /dev/null
+++ b/exampleSite/content/events/2016-sydney/welcome.md
@@ -0,0 +1,82 @@
++++
+date = "2016-08-23T19:14:51+10:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-sydney"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+ Register
+
+
+ {{< event_link page="registration" text="Register to attend the conference!" >}}
+
+
+
+
+
+ Program
+
+
+ {{< event_link page="program" text="View the program." >}}
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+{{< event_twitter devopsdownunder >}}
diff --git a/exampleSite/content/events/2016-telaviv/conduct.md b/exampleSite/content/events/2016-telaviv/conduct.md
new file mode 100644
index 000000000..7103de5fb
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-06-15T13:34:21+03:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-telaviv/contact.md b/exampleSite/content/events/2016-telaviv/contact.md
new file mode 100644
index 000000000..67f141afc
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-06-15T13:34:21+03:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-telaviv/location.md b/exampleSite/content/events/2016-telaviv/location.md
new file mode 100644
index 000000000..63d27c98e
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/location.md
@@ -0,0 +1,32 @@
++++
+date = "2016-06-15T13:34:21+03:00"
+title = "location"
+type = "event"
+
++++
+
+Tel Aviv Convention Center, 101 Rokach Blvd.
+
+{{< event_map >}}
+
+Exhibition Grounds website:
+http://www.fairs.co.il/en/map/
+
+
+
+
+
Directions
+
The Tel Aviv Convention Center is located at the most strategic spot in the metropolis, which allows for quick and easy access to it from any spot in Israel. The major traffic arteries (Ayalon Freeways, Kvish Geha, Kvish Ha’Hof, Kvish Hamesh) flow directly to it, the nearest train station is located within walking distance of the venue, as well as plentiful bus stations.
+That, and more – adjacent to the various pavilions visitors can enjoy the hundreds of upper and lower tier parking spaces, with thousands more parking spaces within the perimeter.
+
+
+By Car:
+Ayalon Darom: For those arriving from the north exit left at the Rokach interchange
+Ayalon Darom: For those arriving from the south exit right at the Rokach interchange
+Exit at the Convention Center interchange and follow the signs
+
+By public transport: please use Moovit below
+
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/program.md b/exampleSite/content/events/2016-telaviv/program.md
new file mode 100644
index 000000000..5e0d55255
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program.md
@@ -0,0 +1,463 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+
Monday, Dec 12, 2016
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
Title:
+ Build Serverless Architectures with AWS
+
+
+
Description:
+
+
Innovation is about what you do different. Serverless gives innovative way of delivering cloud services however there is not enough information in you can find around. We (Cloud Innovation Labs at Accenture) are one of the first massive adopters of Serverless architectures and we are happy to share our story and our recipes with the community. Planned structure:
+
+- Serverless Motivation
+- Quick intro to tool chain for Serverless: Terraform, Apex, Swagger
+LIVE coding
+- Deploy static web app
+- Extend it with dynamic web app
+- Extend it with git server acting as CMS"
+
Bio:
+
+
On field Cloud Architect, DevOps and Developer advocate with 15 years experience in DEV area. Was one of the first infra-structure-as-code practitioners in Accenture. Has passion to discover new technologies and search for new use cases it can give.
"I've been building and delivering software for the last 15 years. I've helped establish Continuous Delivery and DevOps practices in various enterprise and startup companies and I love speaking about this stuff.
+
+A firm believer in Continuous Improvement and organisational transparency.
+
+http://otomato.link"
Avishai Ish-Shalom is a veteran Ops and a survivor of many production skirmishes. As an independent consultant, Avishai helps companies deal with web era operations and scale. In his spare time, Avishai is spreading weird ideas and conspiracy theories such as DevOps and contributing to various open source projects.
Title:
+ Boaz Shuster - Hack docker for fun and profit
+
+
+
Description:
+
+
+ "Introduction:
+ - What's Docker? - in case no one knows what it does
+ - The Project History - details about Docker
+
+Before Hands-On: This part gives what you need to know/have before starting playing with the source code. I will also show basic stuff that are sufficient to start hacking.
+ - Go language
+ - Git basic understanding
+ - installing Docker
+
+Background:
+ - Understand the APIs: The basic APIs to communicate with the Docker daemon
+ - Understand the CLI part: Go over the command line commands and look at their code.
+
+Hands-On:
+ - One of these:
+ * Add a new flag to one of the command lines
+ * Change the way names are assigned to containers
+ - Run the changes inside a container
+
+Testing: How to test that your change didn't break Docker
+ - Running unit-tests
+ - Running integration tests
+ - Running validation tests"
+
+
Title:
+ A Young Lady's Illustrated Primer to Technical Decision-Making
+
+
+
Description:
+
+
Over the last few years we’ve seen an explosion of complexity, in everything from polyglot storage to composable infrastructure, containerization and microservices, config management vs immutable infrastructure. Even as recently as five years ago, there was still a set of widely accepted best practices. Now every element of your stack is a never-ending rabbit hole of possibilities and questions. What's an engineer or architect or manager to do?
+ Solid technical judgment is more important than ever. You can’t anticipate every problem, but you can identify and head off many of them in advance. We'll talk about how to identify and prioritize where to be boring and where to innovate -- and what to do when you accidentally make the wrong call.
+
+
+
Bio:
+
+
Charity Majors is the cofounder and CTO of Honeycomb, a new startup focused on mining machine data. Previously, Charity ran infrastructure at Parse and was an engineering manager at Facebook. She also worked with the RocksDB team to build and deploy the world’s first Mongo + Rocks in production. Charity likes single malt scotch.
"Evolution of Elasticsearch - from unstructured to structured data
+ 1. Search
+ 2. Logging
+ 3. Metrics
+
+Technical deep dive on 1 - 2 features that allowed this evolution, probably:
+ - Columnar storage (doc values)
+ - Number storage (BKD trees)
+
+Beats - open source framework for building agents/shippers/forwarders to collect and forward data
+ 1. Logs (Filebeat, Winlogbeat)
+ 2. Passive packet capture (Packetbeat)
+ 2. Metrics (existing modules for Top, Apache/Nginx, Mysql/Postgresql, Redis, Cassandra, Docker, and many more)
+
+Live demo of Packetbeat: running on my laptop, capturing live HTTP requests to websites I visit, all data including URLs, HTTP headers, etc. are immediately in Elasticsearch and are visualised with Kibana."
+
+
Bio:
+
+
Christoph is the Channel Solutions Architect for Elastic in EMEA. He advises system integrators, platform and product companies in how to use and integrate with the Elastic Stack. On his travels around the continents Christoph is always on the lookout for hummus that tastes as good as it does in Israel. Needless to say he's still looking.
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/program/closing.md b/exampleSite/content/events/2016-telaviv/program/closing.md
new file mode 100644
index 000000000..e7f788042
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/closing.md
@@ -0,0 +1,3 @@
+Closing words from your local organizers:
+
+{{< list_organizers >}}
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-telaviv/program/coreyquinn.md b/exampleSite/content/events/2016-telaviv/program/coreyquinn.md
new file mode 100644
index 000000000..befe9c1f2
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/coreyquinn.md
@@ -0,0 +1,24 @@
++++
+City = "Tel Aviv"
+Year = "2016"
+title = "Corey Quinn"
+type = "talk"
++++
+
+
+
+
Title:
+ The Stories We Tell and the Failures We've Lived
+
+
+
Description:
+
+
Most conference talks center around success stories. In this lighthearted yet sincere talk, Corey discusses some of his more embarrassing professional failures.
+
Bio:
+
+
"Corey has a long and storied history as a consultant -- long, in that every year he did it felt like three years, and storied, in that he's got a few. Prior to his current role as Director of DevOps at FutureAdvisor, he spent most of the past few years at a Bay Area consulting firm, where he served as a systems architect, ad-hoc recruiter, advocate for driving transformational change throughout organizations, and (due to a misunderstanding around what a ""standup meeting"" really was) an improvisational comic. One of the early developers behind Saltstack, Corey also has a rich history of contributing to various open source projects.
+
+Corey's hobbies include motorcycles, building custom keyboards, and drinking whiskey-- it's a shame that they all don't work well together. He lives in San Francisco with his wife and two rodents of unusual size masquerading as dogs."
"We all know that team members need to evaluate candidates for hiring, but we don't often address how interviewing works, or how we can do it better. Using real-world examples, Crystal Huff will provide laughs, some key takeaways, and some points to ponder. Crystal encourages people to address unconscious bias in their processes, which is proven to increase the diversity of their team as well as improve retention of employees once hired."
Have you ever been assigned a legacy project ? Were you happy about it ? probably not. We all know that maintaining a legacy project can be hard and challenging. In this talk i will share best practices I've learned from my experience of maintaining legacy projects @ Wix and give some tips so that your task of maintaining such projects can be a big success
+
Bio:
+
+
"I'm an experienced software engineer, writing server code has been my passion and my career for the last 10 years.
+
+I believe that keeping your code simple and readable is the key to easily maintaining it over time"
The popularity of containers has driven the need for distributed systems that have the ability to manage resources, place workloads and adapt to faults. These so-called Container Orchestrators have seen a rise in popularity in the enterprise that is reminiscent of the early container adoption. Open-source projects such as Docker Swarm, Kubernetes and Marathon make it easy for anyone to manage their container workloads using their cloud-based or on-premise infrastructure
+
+Unfortunately, a lot of these orchestrator systems have not been architected with security in mind. In particular, compromise of a less-privileged node usually allows an attacker to escalate privileges to either gain control of the whole system, or to access resources it shouldn't have access to.
+
+Given the popularity of containers in the enterprise, it is critical that we start designing orchestrators that are designed with security in mind, and follow the principle of least-privilege, where any participant of the system only has access to the resources that are strictly necessary for its legitimate purpose. No more, no less.
+
+
+
Bio:
+
+
Diogo Mónica is the security lead at Docker, an open platform for building, shipping and running distributed applications. He was an early employee at Square where he led the platform security team, has a BSc, MSc and PhD degrees in Computer Science, serves on the board of advisors of several security startups, and is a long-time IEEE Volunteer.
+ We all know the power of parallel computation, and aspire to use it whenever we can to improve performance.
+ Often we need to calculate a statistical attribute of our data, such as: average, variance or percentiles.
+
+ In this workshop we will define what is required of a statistical attribute in order to be able to calculate in parallel, and go over several such implementations.
+ We will also go over a few measurements from the world of click-stream analysis and evaluate if we can parallelize their calculation.
+
+
+
+
"So you heard of ChatOps right? Ever pondered to take the leap?
+We'll discuss how BigPanda went from boring deploying manually using ssh to boss level smooth Slack EPICNESS deploying process, How it improved our operations workflows, and finally how it became easy and fun for our developers to improve our operations."
+
+
Bio:
+
+
Love all things code, strong believer in AUTOMATE ALL THE THINGZ.
+ "DadOps supreme, been doing web since FrontPage98, Operations since .bat was extreme and all around geek passionate about ALL THE THINGZ.
+Has a tendency to get as excited about working log pipelines, elegant code and amazing MEMEz."
+
+ Devops is almost always responsible for documenting their own stuff, and frequently they are moving so quickly that this step gets shortcut or omitted. I want to give people in devops some simple, straightforward, repeatable, testable tools to make sure that all the mission-critical data is not dependent on one person or role.
+ We're going to have to do much more nimble, flexible documentation methods than remembering to enter things in Confluence. I'm going to use post-its, commit messages, slack emojis, and crowd suggestions to show you how to do good-enough documentation without slowing your organization down.
+
+Outline:
+
+
Problem statement
+
+
Critical people
+
Cognitive (over)load
+
Onboarding is an apprenticeship, not an orientation
+
+
Solutions
+
+
Automation
+
Collation
+
Sprints
+
+
How you know it worked
+
+
Chaos monkey
+
Onboarding
+
Vacations
+
+
+
+
+
Bio:
+
+
Heidi is a widely experienced technical writer with an interest in writing herself out of work. She specializes in creating entire documentation suites for new companies and products in less time than you would believe possible. She speaks on topics like search-led writing, starting new documentation products, and whistleblowing as a technical writer.
Title:
+ Debugging Skynet: A Machine Learning Approach to Log Analysis
+
+
+
Description:
+
+
"We present a novel system for log forensics that is based on Machine Learning. The system enables classification of log entries in realtime and alerting in case of impending production failures.
+
+The system is designed for high scalability and realtime performance. In order to achieve this, a linear classification engine was trained on features extracted from user behavior, real world user queries and Community Q&A sites.
+
+The ML tools used in the system include principles from Deep Learning, as well as Support Vector Machines (SVM). The realtime engine was implemented using linear SVM and random forests. Training of these supervised algorithms was bootstrapped using human intelligence and several simple heuristics and was later refined by incorporating user feedback into the training stages.
+
+The system takes advantage of the BIg Data that is now available on the web and relies on modern scalable solutions such as Spark, EMR and Hadoop in order to achieve a fully elastic and scalable solution."
+
Bio:
+
+
Ianir Ideses heads the algorithms research and development at Logz.io. Prior to Logz.io, Ianir was Chief Scientist at Shine Security and Algorithm System Architect at Superfish. Ianir holds a Ph.D. from Tel-Aviv University and specializes in machine learning, computer vision, and image processing.
Title:
+ Effectively Culturing a Healthy Culture and Workflow
+
+
+
Description:
+
+
Often, the most difficult part of moving towards a highly-integrated development environment is not any technical issues, but cultural issues within the engineering organization. In this talk, attendees will learn effective techniques to make the cultural changes needed to get a smooth, integrated workflow implemented.
+
Bio:
+
+
"Jeff Pierce has a wealth of experience in the realm of systems operations and DevOps, and has worked and consulted for companies like Apple, Citigroup, Change.org, and others. Jeff is also the project lead and a developed on Cassabon (https://github.com/jeffpierce/cassabon), which makes graphite not suck!
+
+He is especially interested in development culture and statistics, learning new ways of doing things, developing and playing video games, and occasionally speaking in front of large groups of people."
Title:
+ "We'll do it Live!" - Why you should test your software in production
+
+
+
Description:
+
+
"We'll do it Live!" - Why you should test your software in production
+
Bio:
+
+
I've been working full-time as a software engineer for over eight years, and at PagerDuty for the last three and half years. I'm currently a member of the Core Team at PagerDuty, a team with the mandate to build software services and libraries that other Engineering teams at PagerDuty can leverage.
Title:
+ There’s An App For That: Why Every Team Has Their Own Tools
+
+
+
Description:
+
+
Why do companies seem to collect monitoring solutions like pokemon cards? Because it's easier for a group to buy their own tool than to try to work with another group and share an existing system, and at the end of the day they are only going to trust the system that they "own". The good news is that fear and trust issues are two things which DevOps culture is designed to combat and overcome!
+
Bio:
+"Leon Adato is a Head Geek and technical evangelist at SolarWinds®, and is a Cisco® Certified Network Associate (CCNA), MCSE and SolarWinds Certified Professional. His experience spans financial, healthcare, food and beverage, and other industries.
+
+Before he was a SolarWinds Head Geek, Adato was a SolarWinds user for over a decade. His expertise in IT began in 1989 and has led him through roles in classroom training, desktop support, server support, and software distribution."
Title:
+ Machine Learning concepts for software monitoring
+
+
+
Description:
+
+
"Cloud environments and Open Source software have lowered the bar for anyone to implement software solutions.
+Complex relationships between system components are frequently missed by the human eye, and small but important changes are neglected. This, along with the sheer amount of monitoring data, call for a new approach.
+"
+
Bio:
+
+
Lior Redlus is the Chief Scientist and Co-founder @ Coralogix. He holds a B.Sc and an M.Sc degrees in Neuroscience and Information Processing from Bar-Ilan University, and has been a statistics advisor for a variety of scientific research papers. Lior is enthusiastic about science and technology, and likes everything pixel-perfect. Including pictures.
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/program/lunchsponsor.md b/exampleSite/content/events/2016-telaviv/program/lunchsponsor.md
new file mode 100644
index 000000000..3b124789e
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/lunchsponsor.md
@@ -0,0 +1,3 @@
+We don't have a sponsor for lunch yet, interested?
+
+email us at {{< email_organizers >}}
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-telaviv/program/mikeplace.md b/exampleSite/content/events/2016-telaviv/program/mikeplace.md
new file mode 100644
index 000000000..e81892b27
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/mikeplace.md
@@ -0,0 +1,22 @@
++++
+City = "Tel Aviv"
+Year = "2016"
+title = "Mike Place"
+type = "talk"
++++
+
+
+
+
Title:
+ Event-Driven Automation: Full Stack Monitoring
+
+
+
Description:
+
+
Event-Driven Automation: Full Stack Monitoring
+
Bio:
+
+
I am on the core engineering team at SaltStack and am currently the principle maintainer of the project. I help to manage one of the largest Python developer communities in the world!
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/program/nathenharvey.md b/exampleSite/content/events/2016-telaviv/program/nathenharvey.md
new file mode 100644
index 000000000..3203671a6
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/nathenharvey.md
@@ -0,0 +1,23 @@
++++
+City = "Tel Aviv"
+Year = "2016"
+title = "Nathen Harvey and Adam Jacob"
+type = "talk"
++++
+
+
+
+
Title:
+ The Evolution of Automation
+
+
+
Description:
+
+
We’ll talk about the fundamentals of automation, what we’ve learned over multiple generations of tooling and research, and discuss the path forward.
+
+
Bio:
+
+
Nathen Harvey, VP of Community Development at Chef, helps the community whip up an awesome ecosystem built around the Chef platform. Nathen also spends much of his time helping people learn about the practices, processes, and technologies that support DevOps, continuous delivery, and high velocity organizations. Nathen is a co-host of the Food Fight Show, a podcast about Chef and DevOps. He is also an occasional farmer who loves eggs and #hugops.
+
Adam Jacob is a co-founder of Chef Software and the creator of the Chef IT automation platform. Adam is a leading voice and pioneer in DevOps and the digital economy, with a passion for empowering businesses to delight customers with technology. Prior to Chef, he founded HJK Solutions, an automated infrastructure consultancy. During two years at HJK, he built new infrastructures for 15 different startups. Including his time at HJK, Adam has 13 years of experience as a systems administrator, systems architect, and tools developer. He has been responsible for large production infrastructures, internal corporate automation, and Sarbanes-Oxley compliance efforts.
During the last few years, I've been constantly challenging myself to do things which terrified me. Not big things like jumping off planes, or hunting lions in the savanna, but small ones: like asking for help, and speaking publicly. In this talk, I’ll share the experience I gained leaving my comfort zone, why tackling scary tasks is crucial for your engineering career, and tips that will help you on your journey.
+
+
+
Bio:
+
+
Production Engineer at SimilarWeb, fighting manual labor with code and vengeance. Previous experience includes: operations consultancy, software development, *nix administration and security research in the Intelligence corps and multiple startup companies.
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/program/opening.md b/exampleSite/content/events/2016-telaviv/program/opening.md
new file mode 100644
index 000000000..c294a437c
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/opening.md
@@ -0,0 +1,3 @@
+Opening words from your local organizers:
+
+{{< list_organizers >}}
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-telaviv/program/rakefet.md b/exampleSite/content/events/2016-telaviv/program/rakefet.md
new file mode 100644
index 000000000..575ce838b
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/rakefet.md
@@ -0,0 +1,22 @@
++++
+City = "Tel Aviv"
+Year = "2016"
+title = "Rackefet Jackoby Galazan"
+type = "talk"
++++
+
+
+
+
Title:
+ Building successful apps using application telemetry and data-driven insights
+
+
+
Description:
+
+
Building successful apps is hard! Whether you build a service or an app, there is fierce competition, and success requires data-driven decision making. It requires detecting and resolving issues before your customers do, and knowing how your product is being used to decide where to invest next. In this talk, we’ll see how APM and Analytics tools can help in building successful apps.
Title:
+ Production Engineering - There is no Spoon
+
+
+
Description:
+ A couple of years ago Facebook bought the Israeli company Onavo. During Onavo's migrating into FB we decided to migrate not only our servers and tooling, but also the methodology.
+One of the things we noticed was the mentality - there is no real difference between a software engineer and production engineer in terms of owning code in production. Surprisingly this works very well.
+My talk purpose is to:
+1. describe the process we went through from the time we realized that we need to change something and what was the trigger.
+2. what other solutions we could have chose to do
+3. why we chose the PE way
+4. how we applied it
+5. what we could have done better
+6. our takeaways notes
+7. QnA
+
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/program/tbd.md b/exampleSite/content/events/2016-telaviv/program/tbd.md
new file mode 100644
index 000000000..b4553af68
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/tbd.md
@@ -0,0 +1,2 @@
+We have a great talk that is yet to be confirmed!
+Check back again soon for updates!
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-telaviv/program/yaronamir.md b/exampleSite/content/events/2016-telaviv/program/yaronamir.md
new file mode 100644
index 000000000..ee69fd991
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/yaronamir.md
@@ -0,0 +1,28 @@
++++
+City = "Tel Aviv"
+Year = "2016"
+title = "Yaron Amir"
+type = "talk"
++++
+
+
+
+
Title:
+ Culture bottom up - Culture driven by employees.
+
+
+
Description:
+
+
In most organizations the organizational culture is the dictated by management and executed via HR.
+What happens to a company when everyone, managers, developers and DBAs drives the culture?
+At Outbrain we tried it and the results are :-)
+
Bio:
+
+ OpsSchool Manager at Outbrain
+
In the last years Yaron was leading the Outbrain ops data team, managing thouseds of data servers with big Data technologies such as cassandra, mysql and hadoop.
+ Yaron found his passion in passing the knowledge to others and decided to start the OpsSchool from within Outbrain.
+ "
+
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/program/yaronamirorilahav.md b/exampleSite/content/events/2016-telaviv/program/yaronamirorilahav.md
new file mode 100644
index 000000000..a7963f1ed
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/program/yaronamirorilahav.md
@@ -0,0 +1,33 @@
++++
+City = "Tel Aviv"
+Year = "2016"
+title = "Yaron Amir and Ori Lahav"
+type = "talk"
++++
+
+
+
+
Title:
+ Culture bottom up
+Culture driven by employees.
+
+
+
Description:
+
+
In most organizations the organizational culture is the dictated by management and executed via HR.
+What happens to a company when everyone, managers, developers and DBAs drives the culture?
+At Outbrain we tried it and the results are :-)
+
Bio:
+
Ori:
+ Ori Lahav is Co-Founder and General Manager, Israel at Outbrain, and he oversees the company's R&D center located in Netanya, Israel. Prior to co-founding Outbrain, Ori led the R&D groups in search and classification at Shopping.com, which was acquired by eBay for $634 million. Ori also previously led the video streaming server group at technology company Vsoft. A practical engineer from the Rupin Academic Institute Ori is also a Major (reserve) officer in the Israeli Navy.
+
+
+
Yaron:
+ OpsSchool Manager at Outbrain
+ In the last years Yaron was leading the Outbrain ops data team, managing thouseds of data servers with big Data technologies such as cassandra, mysql and hadoop.
+ Yaron found his passion in passing the knowledge to others and decided to start the OpsSchool from within Outbrain.
+ "
+
We're proud to say that we have already sold out of tickets for this excellent annual conference.
+
+
PLEASE NOTE: Due to capacity issues and fire code regulations, we will not be able to offer any more tickets at all. If you would like to get onto the waitlist, please fill out the Google Form below and we will notify you on a first come first served basis should there be any changes. Your information will be kept in our database for future DevOpsDays events in Israel only and will not be shared with any other lists.
+
+
+
+
diff --git a/exampleSite/content/events/2016-telaviv/speakers.md b/exampleSite/content/events/2016-telaviv/speakers.md
deleted file mode 100644
index e536e7b60..000000000
--- a/exampleSite/content/events/2016-telaviv/speakers.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-Title = "Speakers for Ponyville"
-date = "2016-12-08T20:55:58-06:00"
-PublishDate = "2016-12-08T20:55:58-06:00"
-type = "speakers"
-+++
diff --git a/exampleSite/content/events/2016-telaviv/sponsor.md b/exampleSite/content/events/2016-telaviv/sponsor.md
new file mode 100644
index 000000000..6f6bc8066
--- /dev/null
+++ b/exampleSite/content/events/2016-telaviv/sponsor.md
@@ -0,0 +1,44 @@
++++
+date = "2016-06-15T13:34:21+03:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+Sponsorships are SOLD OUT!
+
+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, send us an email at [{{< email_organizers >}}].
+
+
+
+
+
+
+
+
+
+
packages
+
Silver 1500 usd
+
Gold 3500 usd
+
Platinum (Max 2 Sponsors) 5000 usd
+
+
+
2 included tickets
+
logo on event website
+
logo on shared slide, rotating during breaks
+
logo on all email communication
+
logo on its own slide, rotating during breaks
+
5 minute pitch to full audience (including streaming audience)
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+ Propose
+
+
+ {{< event_link page="propose" text="Propose a talk!" >}}
+
+
+
+
+
+
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+{{< event_twitter devopsdaystlv >}}
diff --git a/exampleSite/content/events/2016-toronto/conduct.md b/exampleSite/content/events/2016-toronto/conduct.md
new file mode 100644
index 000000000..d713e19d7
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-toronto/contact.md b/exampleSite/content/events/2016-toronto/contact.md
new file mode 100644
index 000000000..bbb58b54c
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core DevOpsDays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-toronto/location.md b/exampleSite/content/events/2016-toronto/location.md
new file mode 100644
index 000000000..d55dd7a52
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/location.md
@@ -0,0 +1,32 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+### Conference location:
+DevOps Days Toronto is being hosted at the Glenn Gould Studio located at corner of Front and John in the Canadian Broadcasting Centre. The Studio and its washrooms are wheelchair accessible.
+Glenn Gould Studios: 250 Front St West, Toronto, ON. M5V 3G5 - (416) 205-5000
+
+
+
+
+
+### Public Transportation
+Glenn Gould Studio is easily accessible by public transit. From the TTC and Go Transit stops at Union Station, you can walk west three blocks to the Canadian Broadcasting Centre on the north side of Front Street. Glenn Gould Studio is connected to the PATH underground walkway via St. Andrews subway station. Visit the Toronto Transit Commission (TTC) or GO Transit websites for transit directions or use Google Maps as a starting point for finding transit information.
+
+### Planes, Trains and Automobiles
+Toronto has two airports: Toronto Pearson International Airport and Billy Bishop Toronto City Airport. Check Expedia.ca for flight information.
+
+Via Rail and GO Transit trains connect at Union Station, the main station for Toronto. Union Station connects with public transit.
+
+There are a number of parking lots near the Canadian Broadcasting Centre. Please review Glenn Gould Parking Map for all of the options. The nearest Green P lot is Carpark 52 at 40 York Street. Daytime rate (7am - 7pm) is $20.00 and night time rates (5pm - 7am) is $8.00.
+
+### Accommodations
+Toronto is a world class city with a multitude of accomodation options near Glenn Gould Studios. We are investigating group space at a nearby hotel. More details will be shared in the near future.
+
+### Tourism
+Come to Toronto for DevOps Days, but check Tourism Toronto for more information on tourist packages and hotels. Sometimes a package deal can make travel less expensive and more fun. What is your interest: opera, ballet, live theatre, art gallery, museums, shopping, music, sports?
diff --git a/exampleSite/content/events/2016-toronto/program.md b/exampleSite/content/events/2016-toronto/program.md
new file mode 100644
index 000000000..de73def8e
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/program.md
@@ -0,0 +1,168 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
DevOpsDays is a grass-roots event taking place in cities all around the world. It is organized entirely by volunteers and enthusiasts of DevOps philosophies, processes, and tools who are excited to be a part of the movement.
+
+
Each day has four primary speakers presenting 30 minute talks. Presentations range from cultural ideas to specific details and experiences implementing and managing a broad spectrum of DevOps and Agile related issues. Additionally, there is a 30 minute block of IGNITE style talks (5 minute auto-advancing slides) providing a good mix of content delivered quickly and on point.
+
+
The last part of each event consists of "Open Spaces". These self-suggested and self-run discussions provide an open forum for participants to engage in deeper and meaningful conversations with their peers, presenters, and vendors. Discussions are often extensions of points and ideas brought up in early presentations, but can be about any subject interesting to a participant. If you are new to the Open Space concept you can learn more about the format here.
+
+
Also remember that some of the best learning moments can happen when you least expect them. Whether it's hallway conversations or over lunch be ready to share and learn with your fellow attendees, speakers and sponsors.
+
+
Take a look at the videos from DevOpsDays Toronto 2015 to see how the different formats work.
+
+
While you're at the conference remember that learning and understanding DevOps and the ideas and methodologies that it brings is a spiral path. You will hear ideas and concepts repeated over and over and over. Each time at a different level. There's no such thing as being "done with DevOps". Frustration and rewards are found along each level on the path.
Attendee-suggested breakout discussions Open Space #1
+
+
15:25-15:40
Break
+
+
15:40-16:25
Attendee-suggested breakout discussions Open Space #2
+
+
16:25-16:40
Break
+
+
16:40-17:25
Attendee-suggested breakout discussions Open Space #3
+
+
17:30-17:45
Closing Day & Farewell
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals.md b/exampleSite/content/events/2016-toronto/proposals.md
new file mode 100644
index 000000000..4540ffee6
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals.md
@@ -0,0 +1,15 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-toronto/proposals/Agile databases.md b/exampleSite/content/events/2016-toronto/proposals/Agile databases.md
new file mode 100644
index 000000000..c9804386f
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Agile databases.md
@@ -0,0 +1,33 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Jeff Zohrab"
+
++++
+
+### Agile Databases
+
+**Abstract:**
+
+Databases are almost always a pain point for development, especially when it comes to agile. In this talk, I'll discuss what I feel are the main points that need to be considered for successful database development:
+
++ each dev should have their own development database, and should create database change scripts
++ changes should be easily integrated
++ baselining
++ the difference between reference and test data
++ handling schema vs code changes
++ testing
++ backwards compatibility checks
++ database refactoring
+
+For lack of a better tool (at least, at the time!), I wrote a cross-platform database development tool in Python that can/should be able to work with any database for which suitable drivers exist, and implementations are available for MySQL and Postgres. I'll use that as a demo. With this tool (version 0.1 of it, anyway), I had a team of 6 devs destroying and rebuilding their dev databases as needed with a single click, running their dev tests on their dedicated instances, and deploying to multiple QA and integration environments.
+
+I think that this topic is interesting in general as it highlights the need to pull pain points forward and deal with them. Paraphrasing Jez Humble -- or maybe exactly quoting him per Continuous Integration – If Something Hurts, Do It More Often -- database things hurt, and so they need to be done as much as possible. Unfortunately, many tools don't address these needs, and advice on the net can end up being problematic (eg the tip "your db change script should check if a column exists before adding it" can end up avoiding one trouble but causing another).
+
+**Speaker:**
+
+Jeff Zohrab
+
+I've been in tech for a few decades now, and was an early adopter with XP designed testing frameworks for VB and C++. I've worked on small, big, and huge projects on the development side as dev, team lead, and architect, and have recently started working with a Japanese company to instill DevOps practices into their culture.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Are YOU the Change Agent your Organization is Looking For.md b/exampleSite/content/events/2016-toronto/proposals/Are YOU the Change Agent your Organization is Looking For.md
new file mode 100644
index 000000000..d684071fd
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Are YOU the Change Agent your Organization is Looking For.md
@@ -0,0 +1,20 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Drew Nienaber"
+
++++
+
+### Are YOU the Change Agent your Organization is Looking For…?
+
+**Abstract:**
+
+For most organizations, DevOps means a change, both to your process and your way of thinking. Change is hard and being the one to introduce change into your organization is even more difficult. In this Ignite, I’ll talk about the assumptions we make about change, the universal truths we accept about change, the questions to ask yourself before initiating change and four approaches to bringing it. With the help of the book Change Anything: The New Science of Personal Success, I’ll show how you can be the transformer & revolutionary you’ve always dreamed of being.
+
+**Speaker:**
+
+Drew Nienaber, @DrewNienaber
+
+I'm (Drew) a sales guy, but don't hate me for that. I'm also a craft beer aficionado, a dad and a Nawlins boy desperately looking for Zapps chips in Colorado.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Being an introvert and at a conference not as hellish as you think it is.md b/exampleSite/content/events/2016-toronto/proposals/Being an introvert and at a conference not as hellish as you think it is.md
new file mode 100644
index 000000000..90e85342d
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Being an introvert and at a conference not as hellish as you think it is.md
@@ -0,0 +1,33 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "JJ Asghar"
+
++++
+
+### Being an introvert and at a conference, not as hellish as you think it is
+
+**Abstract:**
+
+I'd like to give some advice on how to deal with conferences as an introvert.
+Over the last couple years I've grown and learned to engage with the tech community
+in ways that an introvert would find challenging. This talk will hopefully help
+the audience avoid some of the landmines that I have stepped on.
+
+I want to help out my fellow introverts to realize that it's OK to be an introvert
+at big conferences. We can enjoy them too.
+
+**Speaker:**
+
+JJ Asghar, @jjasghar
+
+JJ is a Sr. Partner Engineer at Chef, he was also the PTL for the Openstack-Chef
+project. He lives in Austin, Texas and has been part of the OpenStack community since Diablo's release.
+
+He enjoys a good strong stout, hoppy IPA, and some Dwarf Fortress. He's a member
+of the Church of Emacs, and usually chooses Ubuntu over CentOS.
+
+He's a father and husband, if he's not trying to automate his job away he's
+trying to convince his daughters to "let the bot's do the work for them."
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Containers will not fix your broken culture (and other hard truths).md b/exampleSite/content/events/2016-toronto/proposals/Containers will not fix your broken culture (and other hard truths).md
new file mode 100644
index 000000000..a13929dcb
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Containers will not fix your broken culture (and other hard truths).md
@@ -0,0 +1,28 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Bridget Kromhout"
+
++++
+
+### Containers will not fix your broken culture (and other hard truths)
+
+**Abstract:**
+
+Containers will not fix your broken culture. Microservices won’t prevent your two-pizza teams from needing to have conversations with one another over that pizza. No amount of industrial-strength job scheduling makes your organization immune to Conway's Law.
+
+Does this mean that devops has failed? Not in the slightest. It means that while the unscrupulous might try to sell us devops, we can't buy it. We have to live it; change is a choice we make every day, through our actions of listening empathetically and acting compassionately. Iterative improvement starts somewhere for us all; let’s talk about it.
+
+Tools are essential, but how we implement the tools and grow the culture and practices in our organizations needs even more attention. Whether you’re just starting to implement technical and organizational change, or facing the prospect that you already have legacy microservices, it's worth considering the why and the how of our behaviors, not just the what.
+
+Making thoughtful decisions about tools and architecture can help. Containers prove to be a useful boundary object, and deconstructing systems to human-scale allows us to comprehend their complexity. We succeed when we share responsibility and have agency, when we move past learned helplessness to active listening. But there is no flowchart, no checklist, no shopping list of ticky boxes that will make everything better. "Anyone who says differently is selling something", as The Princess Bride teaches us. Instead, let’s talk about practical, actionable steps that will help. How do we evaluate our progress? How do we know when to course-correct? How do we react when it seems like there's always something new we should have done last month?
+
+Part rant, part devops therapy, this talk will explain in the nerdiest of terms why CAP theorem applies to human interactions too, how oral tradition is like never writing state to disk, and what we can do to avoid sadness as a service.
+
+**Speaker:**
+
+Bridget Kromhout, @bridgetkromhout
+
+Bridget Kromhout is a Principal Technologist for Cloud Foundry at Pivotal. Her CS degree emphasis was in theory, but she now deals with the concrete (if 'cloud' can be considered tangible). After years in site reliability operations (most recently at DramaFever), she traded in oncall for more travel. A frequent speaker at tech conferences, she helps organize the AWS and devops meetups at home in Minneapolis, serves on the program committee for Velocity, and acts as a global core organizer for devopsdays. She podcasts at Arrested DevOps, occasionally blogs at bridgetkromhout.com, and is active in a Twitterverse near you.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Devops Evolution at Nulogy.md b/exampleSite/content/events/2016-toronto/proposals/Devops Evolution at Nulogy.md
new file mode 100644
index 000000000..725832ee8
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Devops Evolution at Nulogy.md
@@ -0,0 +1,32 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Ian Penney"
+
++++
+
+### Devops Evolution at Nulogy
+
+**Abstract:**
+
+At Nulogy, our operations are supported by our Infrastructure team, colloquially known as the "Computer Friends and Justin"
+We are proud to have brought together a team of five veteran hackers with diverse academic and other backgrounds.
+
+We've recently been through a banner year of growth - having aggressively tackled quick wins to greatly improve the reliability of our flagship SaaS Logistics product to the point where it can be sold to large multinational corporations with a real need for "four nines" of uptime.
+
+Everyone on the team is a great fit with our well rounded company culture, but none of us started out in life as Devops Experts. We've learned it, and we want to help you learn it, too.
+
+The company had already been in operation for over ten years by the time we began to embrace DevOps and related practices. How is it possible to beat down technical debt with so many legacy systems, high SLA requirements and entrenched customers practices.
+And more to the point: how will this work make your work/life balance better?
+
+**Speaker:**
+
+Ian Penney, @cr03
+
+Ian Penney has been working as a Systems Administrator and Systems Manager for over 15 years. He's worked at large companies like the Canadian Broadcasting Corporation and other enterprises through an IBM business partner, as well as with over 200 startups, from coast to coast.
+
+A few years ago, he realized Infrastructure as Code was the future, and so he began focusing on using tools like Chef, Puppet and Ansible.
+
+Most recently he's celebrated his first happy anniversary at Nulogy as the lead of their Infrastructure Team during a rapid transition towards "moar devops" and less risk.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Feeling the burn.md b/exampleSite/content/events/2016-toronto/proposals/Feeling the burn.md
new file mode 100644
index 000000000..2e380ded7
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Feeling the burn.md
@@ -0,0 +1,18 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Jason Harley"
+
++++
+
+### Feeling the burn?
+
+**Abstract:**
+
+Burnout is often thought to be limited to Silicon Valley, but it's a very real problem here in the GTA. In this five minute talk, we'll explore the signs and symptoms of burnout, talk about the guilt, second guessing, and other feelings associated with it and what you can do to help yourself, your co-workers, and your friends in the community.
+
+**Speaker:**
+
+Jason Harley, @redmind
diff --git a/exampleSite/content/events/2016-toronto/proposals/From Commit To Production And Beyond - The Continuous Delivery Pipeline.md b/exampleSite/content/events/2016-toronto/proposals/From Commit To Production And Beyond - The Continuous Delivery Pipeline.md
new file mode 100644
index 000000000..2eda134c1
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/From Commit To Production And Beyond - The Continuous Delivery Pipeline.md
@@ -0,0 +1,24 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Arthur Maltson"
+
++++
+
+### From Commit To Production And Beyond - The Continuous Delivery Pipeline
+
+**Abstract:**
+
+You've probably heard about Continuous Delivery, and you have definitely heard of DevOps (it is a DevOps conference after all), but how are the two related? Throughout this talk you will learn what Continuous Delivery is and why your organization should strive to achieve it. You will then embark on a Continuous Delivery journey that will highlight the level of DevOps maturity an organization should be at to safely deliver to production on a regular basis and keep it running for the long term.
+
+This talk will give you some ideas of what a Continuous Delivery pipeline looks like and a workflow the Dev, QA and Ops groups may want to follow. Particular attention will be paid to the application life after deployment and ways of managing the complexity of an ever more distributed system.
+
+**Speaker:**
+
+Arthur Maltson, @amaltson
+
+Arthur Maltson is a Software Developer who's 70% Dev and 30% Ops. He's currently practicing DevOps during the day and, as a husband and father he's also doing DadOps at night. Arthur embodies the Full Stack developer with his passion for infrastructure automation, API crafting, front end development and making work fun by introducing and/or building new tools.
+
+In his spare time Arthur spends far too much time trying to keep up with the latest tech. He also occasionally blogs, Tweets and commits to OSS.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/How Brazil's government kept us up at night.md b/exampleSite/content/events/2016-toronto/proposals/How Brazil's government kept us up at night.md
new file mode 100644
index 000000000..4e09c60f4
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/How Brazil's government kept us up at night.md
@@ -0,0 +1,20 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Hany Fahim"
+
++++
+
+### How Brazil's government kept us up at night
+
+**Abstract:**
+
+On the evening of December 16th, 2015, Brazil's government decided to ban the use of the popular WhatsApp platform. Over 93% of Brazil's internet population, roughly 93 million, use WhatsApp as part of their daily lives. The ban forced an uprising and lash back on social media, and the more savvy users began finding ways of circumventing. This talk tells the story of how this ban affected our own team and kept us up all night!
+
+**Speaker:**
+
+Hany Fahim, @iHandroid
+
+Hany Fahim is the Founder and CEO of VM Farms, a 24×7 Operations Team and Cloud Provider. Hany has over 10 years of operations experience, both in building and supporting private and public cloud platforms, as well as Linux and OSS environments. You can reach Hany at @iHandroid and the folks of VM Farms @vmfarms.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Public Postmortem on After Hours Maintenance Gone Awry.md b/exampleSite/content/events/2016-toronto/proposals/Public Postmortem on After Hours Maintenance Gone Awry.md
new file mode 100644
index 000000000..8a80f7f1e
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Public Postmortem on After Hours Maintenance Gone Awry.md
@@ -0,0 +1,20 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Jason Shaw"
+
++++
+
+### Public Postmortem on After Hours Maintenance Gone Awry
+
+**Abstract:**
+
+We needed to add some capacity to a Redis cluster, which would have customer impact, so it was scheduled for after hours. 20 minutes into a 30 minute window, wanted to close open connections, so we stopped a bunch of services. One of them had had some init changes recently, and it turns out they weren't tested and made it to production. What do you do when you're an Admin but the problem is dev code and it's 1am?
+
+**Speaker:**
+
+Jason Shaw, @jasonious
+
+Long time Linux SysAdmin with too much empathy for the BOfH style. Currently working on continuous integration and deployment at FreshBooks.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Scaling out Continuous Delivery.md b/exampleSite/content/events/2016-toronto/proposals/Scaling out Continuous Delivery.md
new file mode 100644
index 000000000..e2a25388c
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Scaling out Continuous Delivery.md
@@ -0,0 +1,25 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "John Arthorne"
+
++++
+
+### Scaling out Continuous Delivery
+
+**Abstract:**
+
+Continuous delivery can be a simple practice when you are a small development team with a low scale web application. However, as teams scale up in size, commit and test volumes increase, and production architecture becomes more complex, continuous delivery becomes harder to achieve. Tools that once handled the load begin to fail, individual steps in the delivery process that were once fast turn into bottlenecks, and cultural practices and processes break down.
+
+This talk will describe how Shopify faced these scaling challenges as the team and its application infrastructure grew. A year ago, it could take hours for a developer to go from commit to fully deployment application. In response, the team re-architected its entire delivery pipeline to hand these scaling challenges. We cover how moving to a container-based build and creating the open source Shipit deployment tool allowed the team to regain its continuous delivery cadence.
+
+Today, every developer on a team of hundreds can deliver a change from commit to production in ten minutes. Each deploy includes execution of over 45,000 tests in a massively parallel build farm, and deploying the application to hundreds of servers in multiple data centres. Thirty or more production releases now run in a typical workday, and developer happiness has increased. We will cover the steps taken to get here, the technology choices made, and the stumbling blocks faced along the way.
+
+**Speaker:**
+
+John Arthorne, @jarthorne
+
+
+John works on the Shopify Production Engineering team, with a specific focus on creating developer tooling to accelerate application delivery. John is a frequent speaker at technical conferences in both Europe and North America, serves on conference program committees, is a JavaOne Rock Star, and frequently writes blogs and articles on technical topics. His current interests are in tools and practices for Continuous Delivery, and in highly scalable cloud architectures. Before joining Shopify, John led a team building cloud-based developer tooling for IBM Bluemix, and was a prominent leader within the Eclipse open source community.
diff --git a/exampleSite/content/events/2016-toronto/proposals/Supporting Developers Through DevOps.md b/exampleSite/content/events/2016-toronto/proposals/Supporting Developers Through DevOps.md
new file mode 100644
index 000000000..9d9136a82
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Supporting Developers Through DevOps.md
@@ -0,0 +1,20 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Roderick Randolph"
+
++++
+
+### Supporting Developers Through DevOps
+
+**Abstract:**
+
+Devs write code while Ops deploys and supports it, right? That's still the common belief among many developers. How do you change this behavior in a DevOps environment? To influence this change, it starts with setting expectations, education, and equipping developers with tools they actually want to use. Hiring a team of developers and expecting them to embrace DevOps practices won't happen without giving them the proper tools and support they need. During this talk we'll discuss the DevOps journey Capital One is on, the challenges we face, and how we're changing behaviors one developer at a time.
+
+**Speaker:**
+
+Roderick Randolph
+
+Roderick is a Lead Software Engineer at Capital One where he leads all things DevOps for the Capital One Canada business including building, automating, and migrating infrastructure to the cloud. He currently lives in Toronto but is originally from a small town in the State of Virginia.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Waterboy - our robot coworker.md b/exampleSite/content/events/2016-toronto/proposals/Waterboy - our robot coworker.md
new file mode 100644
index 000000000..f9235be34
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Waterboy - our robot coworker.md
@@ -0,0 +1,29 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Sean Walberg"
+
++++
+
+### Waterboy - our robot coworker
+
+**Abstract:**
+
+Waterboy is our Hubot instance that provides helpful information for both operations and developers. Our organization is somewhat atypical -- we are an external infrastructure consulting practice embedded into a development organization. This talk will cover:
+
++ How we introduced a chatbot into the organization
++ How we manage the robot and encourage people to contribute
++ How we figure out what goes into the robot
++ How we use ChatOps to facilitate communication between ourselves, and between us and the client.
+
+People attending this talk will get a different perspective on the use of chat in a collaborative environment. It's not just shortcuts to memes, nor is it "hubot please go deploy the site and make me coffee". Chat can be a CLI to your organization. One that empowers employees and helps spread knowledge.
+
+**Speaker:**
+
+Sean Walberg, @seanwalberg
+
+I'm a problem solver. A software developer that loves applying software principles to infrastructure automation and web applications.
+
+I wanted to program most of my life, realized I didn't like it during my first job, spent 13 years as a network guy that wrote a lot of code, joined an awesome web startup as a web developer, and have rediscovered my joy for software development. After that ended, I moved into a more devops type role where I can have my feet in both camps. I'm currently with a consulting company that's responsible for the infrastructure and applications at a large American sporting league.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Why We Threw 5 Months of Work in the Trash or How we Failed at adopting DevOps.md b/exampleSite/content/events/2016-toronto/proposals/Why We Threw 5 Months of Work in the Trash or How we Failed at adopting DevOps.md
new file mode 100644
index 000000000..5481c49d6
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Why We Threw 5 Months of Work in the Trash or How we Failed at adopting DevOps.md
@@ -0,0 +1,20 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Sina Jahan"
+
++++
+
+### Why We Threw 5 Months of Work in the Trash; or How we Failed at adopting DevOps
+
+**Abstract:**
+
+Last summer we started an engineering enablement engagement in Seattle. Very quickly we decided DevOps enablement had a lot of potential and started our work...5 months later the "DevOps" part of work was shot down by management due to lack of result. We will take a look at three main reasons that we failed. These are pitfalls that can happen in any company and any project.
+
+**Speaker:**
+
+Sina Jahan
+
+I'm a developer at ThoughtWorks. I tend to focus on work in the cloud and continuous delivery space, more recently focusing on the use of microservice architectures. I love learning new things and helping people build better systems. I love presenting ideas, meeting people and learning new things, and I find conferences a great way to help that. I've also written a few articles along the way.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/Why we should be excited about Azure Stack.md b/exampleSite/content/events/2016-toronto/proposals/Why we should be excited about Azure Stack.md
new file mode 100644
index 000000000..9b708fcfc
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/Why we should be excited about Azure Stack.md
@@ -0,0 +1,18 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Max Yermakhanov"
+
++++
+
+### Why we should be excited about Azure Stack
+
+**Abstract:**
+
+With the upcoming release of Microsoft Azure Stack to the public, we'll talk why we should be excited about this new hybrid cloud platform product that enables your organization to deliver Azure services from your own datacenter to help you achieve more. With Azure Stack, you decide where to keep your data and applications—in your own datacenter or with a hosting service provider. Get the power of cloud services, yet maintain control of your datacenter for true hybrid cloud agility. Azure Stack as a single platform and a single set of APIs across your own data center and the cloud greatly simplifies the process of moving workloads between your own data center and Azure (or maybe add some capacity in the cloud as needed.) There is a lot to be excited about...
+
+**Speaker:**
+
+Max Yermakhanov, @yermax
diff --git a/exampleSite/content/events/2016-toronto/proposals/dotfiles.CI.md b/exampleSite/content/events/2016-toronto/proposals/dotfiles.CI.md
new file mode 100644
index 000000000..6774d6ba6
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/dotfiles.CI.md
@@ -0,0 +1,20 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "Will Weaver"
+
++++
+
+### dotfiles.CI
+
+**Abstract:**
+
+Do you have Continuous Integration, or DevOps on your resume or LinkedIn? Do you have years of maintaining a solid deployment pipeline and nothing to show prospective employers on your Github profile. For many companies seeing is believing. In this talk I'll show you how I built tests and a CI pipeline around my dotfiles for prospective clients.
+
+**Speaker:**
+
+Will Weaver, @buildingbananas
+
+As a DevOps Consultant and Philosopher, Will Weaver helps others learn to love change. Will works with teams to implement and realize the benefits of practices like continuous integration, delivery, and deployment. As an avid practitioner of pair development, he demonstrates and educates others on practices that manage the risk of change.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/proposals/keynote.md b/exampleSite/content/events/2016-toronto/proposals/keynote.md
new file mode 100644
index 000000000..2806daf91
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/proposals/keynote.md
@@ -0,0 +1,30 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:07-06:00"
+type = "event"
+title = "John Willis"
+
++++
+
+### Devops Enterprise State of the Union
+
+**Abstract:**
+
+Coming soon.
+
+**Speaker:**
+
+John Willis, @botchagalupe
+
+John Willis has worked in the IT management industry for more than 35 years.
+
+Currently he is an Evangelist at Docker Inc.
+
+Prior to Docker Willis was the VP of Solutions for Socketplane (sold to Docker) and Enstratius (sold to Dell).
+
+Prior to to Socketplane and Enstratius Willis was the VP of Training & Services at Opscode where he formalized the training, evangelism, and professional services functions at the firm.
+
+Willis also founded Gulf Breeze Software, an award winning IBM business partner, which specializes in deploying Tivoli technology for the enterprise.
+
+Willis has authored six IBM Redbooks for IBM on enterprise systems management and was the founder and chief architect at Chain Bridge Systems.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/propose.md b/exampleSite/content/events/2016-toronto/propose.md
new file mode 100644
index 000000000..a9b915346
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/propose.md
@@ -0,0 +1,42 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+
+### Equal Opportunity
+
+DevOpsDays Toronto is committed to creating a diverse environment and is proud to invite people of all backgrounds and profiles to submit presentation proposals. All potential speakers will receive consideration without regard to race, colour, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, ability or age.
+
+For more information, please see our published {{< event_link page="conduct" text="Code of Conduct" >}}.
+
+### Proposals
+
+There are three ways to propose a session:
+
+1. __A proposal for a talk/panel__ during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+2. __An Ignite talk__ that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+3. __Open Space session__ : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+- __Broad appeal__: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+- __New local presenters__: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
+- __Under-represented voices__: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+- __Original content__: We prefer talks not already presented at another event, especially another one in the local area or one available in recorded form.
+- __No third-party submissions__: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
+- __No vendor pitches__: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
+
+### Submit
+
+To submit a talk create an account on our OpenCFP and click the _Submit a talk_ button.
+
+- Be specific... we aren't mind readers (a description of about 20 lines is about right)
+- Detail is good... but not as important as explaining why your proposal would be interesting
+- Multiple proposals welcome... just follow the other rules
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/register.md b/exampleSite/content/events/2016-toronto/register.md
new file mode 100644
index 000000000..67d872798
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/register.md
@@ -0,0 +1,10 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+title = "register"
+type = "event"
+
++++
+
+DevOpsDays Toronto is sold out. Be sure to watch out for next year's event.
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-toronto/sponsor.md b/exampleSite/content/events/2016-toronto/sponsor.md
new file mode 100644
index 000000000..b22dfe249
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/sponsor.md
@@ -0,0 +1,25 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+
+ {{< event_logo >}}
+
+
+Why Sponsor Us?
+
+The DevOps Days event mandate is to bring the highestquality speakers, experts and the curious together.
+By sponsoring DevOps Days, you will be exposing your company’s brand and services to Toronto’s top talent
+in this rapidly growing space. (And feel great about it, too!)
+We greatly value sponsors for this open event. If you are interested in sponsoring {{< email_organizers >}}.
+
+Please click HERE to download the full sponsor prospectus for DevOpsDays Toronto 2016!
+
+
+
+DevOpsDays is a self-organizing conference for DevOps enthusiasts and evangelists that depends on your sponsorship and participation to happen.
diff --git a/exampleSite/content/events/2016-toronto/welcome.md b/exampleSite/content/events/2016-toronto/welcome.md
new file mode 100644
index 000000000..a20427b47
--- /dev/null
+++ b/exampleSite/content/events/2016-toronto/welcome.md
@@ -0,0 +1,72 @@
++++
+City = "Toronto"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-toronto"]
+
+
++++
+
+
+ {{< event_logo >}}
+ Be part of the third DevOpsDays Toronto in May 2016!
+
+
+
+
+
Dates
+
{{< event_start >}} - {{< event_end >}}
+
+
+
Location
+
{{< event_location >}}
+
+
+
Speakers
+
Call for proposals is closed. Thanks to all who submitted such great ideas!
+
+
+
Register
+
DevOpsDays Toronto is sold out. Be sure to watch out for next year's event.
+
+
+
Program
+
The {{< event_link page="program" text="program" >}} is jam-packed with DevOps goodness!
+
+
+
Sponsors
+
{{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
Contact
+
{{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+
+
+ {{< event_twitter DevOpsDaysTO >}}
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2016-vancouver/conduct.md b/exampleSite/content/events/2016-vancouver/conduct.md
new file mode 100644
index 000000000..33ef72075
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/conduct.md
@@ -0,0 +1,38 @@
++++
+City = "Vancouver"
+Year = "2016"
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+##ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+##CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-vancouver/contact.md b/exampleSite/content/events/2016-vancouver/contact.md
new file mode 100644
index 000000000..bb21cd4c3
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Vancouver"
+Year = "2016"
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+** Our local team**
+
+{{< list_organizers >}}
+
+** The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-vancouver/livestream.md b/exampleSite/content/events/2016-vancouver/livestream.md
new file mode 100644
index 000000000..0fc9f726f
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/livestream.md
@@ -0,0 +1,32 @@
++++
+City = "Vancouver"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+title = "livestream"
+type = "event"
+
++++
+
+
+## Live Stream
+
+
+
+
Day One
+
+
+
+
+
+
+
Day Two
+
+
+
+
+
Brought to you by XE Live Broadcast
+
DevOpsDays Vancouver would like to thank XE Live Broadcast for their support in setting up the livestream.
+
XE Live Broadcast is a not-for-profit media company that helps events and movements reach their global audience.
diff --git a/exampleSite/content/events/2016-vancouver/proposals.md b/exampleSite/content/events/2016-vancouver/proposals.md
new file mode 100644
index 000000000..8e4057373
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/proposals.md
@@ -0,0 +1,15 @@
++++
+City = "Vancouver"
+Year = "2016"
+date = "2016-03-06T21:28:14-06:00"
+title = "proposals"
+type = "event"
+
++++
+
+This page lists the proposals we have received. Help the presenters with your feedback!
+
+
+
Conference Talks
+
+TBD - need to create a template/shortcode for finding all the proposals
diff --git a/exampleSite/content/events/2016-vancouver/propose.md b/exampleSite/content/events/2016-vancouver/propose.md
new file mode 100644
index 000000000..cfd3ae6ce
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/propose.md
@@ -0,0 +1,40 @@
++++
+City = "Vancouver"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-vancouver/registration.md b/exampleSite/content/events/2016-vancouver/registration.md
new file mode 100644
index 000000000..9c4474f6a
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/registration.md
@@ -0,0 +1,28 @@
++++
+City = "Vancouver"
+Year = "2016"
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+## What's Included?
+
+Your ticket to DevOpsDays Vancouver 2016 includes:
+
+* entrance to the event
+* a light breakfast with coffee each morning
+* catered lunch on site both days
+* entrance to the Friday party, including 2 drink vouchers and some food
+
+### If money is a problem
+
+Devopsdays is a volunteer-organized event - literally by and for the Vancouver devops community. We want to make sure that our event welcomes everyone in our community. That’s why we take our [code of conduct](http://www.devopsdays.org/events/2016-vancouver/conduct/) seriously, for example. It is also why we offer grants to people for whom money is a barrier.
+
+If the ticket price of the conference is outside of your means, [write to us and explain your situation.](mailto:organizers-vancouver-2016@devopsdays.org) We might very well be able to help.
+
+## Buy Tickets
+
Tickets are available for purchase through Eventbrite:
diff --git a/exampleSite/content/events/2016-vancouver/sponsor.md b/exampleSite/content/events/2016-vancouver/sponsor.md
new file mode 100644
index 000000000..0a21bf0b1
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/sponsor.md
@@ -0,0 +1,162 @@
++++
+City = "Vancouver"
+Year = "2016"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+## Apologies but we are no longer accepting sponsorships - Sponsorship goals for 2016 have been met!
+
+Thank you for your interest in sponsoring DevOpsDays Vancouver - without your support we could not put such a great event together.
+
+At this time we are no longer accepting Sponsorships for anything but the "Friends" level. We have successfully reached our sponsorship goals for the year, and are shifting efforts to focus on speakers and other day-of tasks to make this the best event yet.
+
+## Sponsor DevOpsDays Vancouver 2016
+
+You can help sponsor this event and connect your company to local technical and business minds who influence security, monitoring, operations, engineering, quality, and process.
+
+Become a sponsor now by emailing [organizers-vancouver-2016@devopsdays.org](mailto:organizers-vancouver-2016@devopsdays.org).
+
+## Why participate in DevOpsDays?
+DevOpsDays is targeted at development and operations IT professionals who wish to improve the interactions between these traditional silos. By taking advantage of this great local event you can:
+
+* Progress alignment between your development and operations teams with open and constructive talk about their solutions and vision.
+* Encourage team members to collaborate and work together more closely in order to increase end to end velocity and keep focused on project success.
+* Help bring DevOps leaders to Vancouver allows the Pacific NorthWest community to interact with experts in the field, to learn what works (and doesn’t) elsewhere.
+* Raise awareness of the great challenges your people are tackling, and share our local experiences out to the wider DevOps community...
+
+## How can you help DevOpsDays?
+DevOpsDays is a self-organizing conference for DevOps practitioners. We hope you will help support this event with one of the sponsor packages.
+
+
+
+### Friends Package
+It can be difficult for small organizations to show their support and dedication to the community. The Friends of Devopsdays package is priced and restricted for small organizations to participate and bring their team!
+
+* Only companies or organizations with fewer than 20 employees may use this package
+* Up to three regular tickets included
+* Up to three more tickets at discounted price of $50 each
+* Your organization name and a URL to your landing page will be included in a “thank you” email to all attendees, naming you a “friend of Devopsdays”
+
+Friends Package price: $500
+
+
+### Bronze Package
+* Total of two included tickets
+* Your logo will be posted on the DevOpsDays web site as a Bronze sponsor
+* Your logo will be featured on all email communication to attendees
+* You’ll be able to demo a product for up to 5 minutes during the open spaces sessions
+* You will be included in the “thank you” email with your company name, a URL to your landing page, and identifying your company as a Bronze sponsor
+
+Bronze Package price: $1000
+
+### Silver Package
+* Total of four included tickets
+* Your logo will be posted on the DevOpsDays web site as a Silver sponsor
+* Your logo will be featured on all email communication to attendees
+* You’ll be able to demo a product for up to 5 minutes during the open spaces sessions
+* We’ll provide a table for the Silver sponsors to share, put collateral on, and talk with attendees at.
+* You will be included in the “thank you” email with your company name, a URL to your landing page, and identifying your company as a Silver sponsor
+
+Silver Package price: $3000
+
+### Gold Package
+* Total of six included tickets
+* Your logo will be posted on the DevOpsDays web site as a Gold sponsor
+* Your logo will be featured on all email communication to attendees
+* You’ll be able to demo a product for up to 5 minutes during the open spaces sessions
+* You’ll be able to deliver a one minute presentation or pitch to the entire audience including streaming video viewers
+* We’ll provide a dedicated table for your company to put collateral on, stand or sit at, and talk with attendees at.
+* You will be included in the “thank you” email with your company name, a URL to your landing page, and identifying your company as a Gold sponsor.
+
+Gold Package price: $5000
+
+
+### Lanyards Sponsorship
+* Have your company logo co-branded with DevOpsDays on the conference name tag lanyard
+
+Gold Sponsorhip price: $1500
+
+
+### Happy Hour Packages
+On the evening of the first day of sponsorship, we will be booking space at Steamworks for attendees to mingle over drinks and food. This is the big social event of the conference and has been a huge hit with attendees in the past.
+
+* There is one sponsorship opportunity to sponsor the food, and one opportunity to sponsor the drinks at this event.
+* Sponsoring either the food or the drinks will allow entrance tickets for up to three people to the happy hour event. These can be upgraded to full conference tickets for $50/person.
+* Your logo will be posted on the DevOpsDays web site as an Evening Event sponsor
+* Each sponsor will be allowed one vertical banner and one table for collateral
+* One company can choose to sponsor both food and drink. If you wish to sponsor both food and drink at this event, you may decorate the space however you wish (subject to the limits imposed by Steamworks). You will also be allowed to bring up to 6 people to the happy hour event (upgradable to full conference tickets for $50/person)
+* You will receive 4 tickets to the full conference
+* You will be included in the “thank you” email with your company name, a URL to your landing page, and identifying your company as the happy hour drinks and/or food sponsor.
+
+Food and drink sponsorship opportunities are $5000 each.
+
+### Amenities Sponsorships
+We have a number of sponsorship opportunities for coffee, breakfast, and lunch. If you wish to sponsor these amenities, we will prominently place a sign with featuring your company’s logo which will inform attendees that the coffee, breakfast, or lunch are brought to them by your company’s generous sponsorship. Your company will also be thanked in the final “thank you” email with a URL to your landing page.
+
+For each of the two days of the conference, there is one opportunity to sponsor each of the following:
+
+* Coffee sponsorship: $1000
+* Breakfast sponsorship: $2000
+* Snacks sponsorship: $2000
+* Lunch sponsorship: $2000
+
+### Streaming Video Sponsorship
+DevOpsDays will publish a free, live video stream of the main conference proceedings from 9AM to 12PM on each day of the conference. The video will be archived for free future viewing. Your company will be recognized by the MC once per conference day thanking your company for sponsoring the streaming video. Your company will be recognized in the final “thank you” email along with a URL to your landing page.
+
+* Your company logo will be shown, full-frame, on interstitial images between conference segments
+* The archived video will note that streaming was sponsored by your company.
+
+Video sponsorship cost: $2500
+
+
+## Sponsor FAQ
+
+### Can you send me a floor plan?
+Yes, we will be sending this out when we have one. The general floor plan can be found [here](http://robsonsquare.ubc.ca/facility-rentals/rooms/floor-plans/), we will sending an event specfic one out once we have it finalized.
+
+### How big is our booth space?
+For Gold Sponsors, you will receive a table and two chairs. Silver sponsors share a swag table where they can lay out printed materials, stickers or other swag. For silver sponsors, keep in mind this is a shared table so please be a good neighbour and plan accordingly. In any event - we encourage sponsors to send engineers to interact with attendees during session breaks, and to avoid large displays and heavy marketing materials.
+
+### Can we choose our booth location?
+Booths are not selectable. Our team will assign your table. Assignments will be made two weeks from conference date.
+
+### Do we get an electricital connection for our booth?
+Yes. A power strip (more importantly, one attached to actual power) will be provided.
+
+### Will there be a company sign at our booth? When do you need graphics?
+You must bring your own signage and all signage must either fit on the table or behind it. If you have a dedicated table feel free to bring a 1m roll up or other backdrop materials that fit, but for the most part - this conference is not about the booth!
+
+### Will the wifi connection be good enough for showing demos?
+Yes, depending on what’s being demonstrated! If you have particular needs, please let us know that you will be accommodating your own network requirements.
+
+### Will there be scanners (and which type), and what about giveaways?
+No scanners. The booth is a place to talk to people during breaks and this conference is not a typical conference or convention. We have seen that sponsors benefit the most when they bring engineers to the conference and interact with the attendees during the sessions--not just at the booth. You are responsible to collect any info you want in person if you want to do giveaways. On the final day at closing session, we will give a time slot for a giveaway.
+
+### What does the one minute pitch (for applicable sponsors) entail?
+Between sessions, Gold Sponsors are given one minute to introduce themselves and their company to the full audience. The emcee will invite a small number to make an introduction during transitions between sessions on either day 1 or day two, depending on the final schedule. In addition to the full audience, your one-minute pitch will be broadcast to the audience watching the live Internet video feed, which will also be posted up to the site afterwards. No slides will be displayed, there is not sufficient time in sixty seconds.
+
+### What does the five minute demo during open space sessions entail?
+[General information about open space format](/pages/open-space-format/)
+
+We will have a space set aside for sequential demos from sponsors. During the "Open space Opening", participants put forth and vote on ideas for discussion topics. If you have prepared a five minute demo, your demonstrator can add a topic "Demo by " to the board. We will announce the location of the demo space when we get ready to disperse participants to the open space sessions, and participants can choose to attend the demos as they see fit.
+
+### Do we get any sponsored talks?
+No, but you are welcome to submit a proposal like everyone else.
+
+### Do we get an ad in the program? When do you need graphics?
+Send us a URL to your logo. When you do, we’ll download the image, size it appropriately, and include it on our web site.
+
+### Do we get a dedicated email blast?
+No. As a Sponsor, you will be included in the Thank You email at the end of the conference, along with a URL to your landing page. You are responsible to collect any info you want in person if you wish to contact participants.
+
+### Who should I send to DevOpsDays?
+Send your technical folks that can interact with the attendees during sessions, Open Spaces, and breaks. All experience levels are welcome.
+
+### What are the demographics of the attendees?
+Technologists, architects, technology managers.
+
+## Sponsor DevOpsDays!
+Become a sponsor now by emailing [organizers-vancouver-2016@devopsdays.org](mailto:organizers-vancouver-2016@devopsdays.org).
diff --git a/exampleSite/content/events/2016-vancouver/welcome.md b/exampleSite/content/events/2016-vancouver/welcome.md
new file mode 100644
index 000000000..ddd9942a9
--- /dev/null
+++ b/exampleSite/content/events/2016-vancouver/welcome.md
@@ -0,0 +1,136 @@
++++
+City = "Vancouver"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-vancouver"]
+
+
++++
+
+
+ {{< event_logo >}}
+
+
+
+
DevOpsDays Vancouver 2016
+
+
+
+
Friday April 15 to Saturday April 16
+
UBC Robson Square
+
DevOpsDays is returning to Vancouver in 2016.
+
DevOpsDays is a self-organizing conference for DevOps practitioners.
diff --git a/exampleSite/content/events/2016-warsaw/conduct.md b/exampleSite/content/events/2016-warsaw/conduct.md
new file mode 100644
index 000000000..d7be291fe
--- /dev/null
+++ b/exampleSite/content/events/2016-warsaw/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-08-11T19:04:13+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2016-warsaw/contact.md b/exampleSite/content/events/2016-warsaw/contact.md
new file mode 100644
index 000000000..22ec39008
--- /dev/null
+++ b/exampleSite/content/events/2016-warsaw/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-08-11T19:04:13+02:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-warsaw/location.md b/exampleSite/content/events/2016-warsaw/location.md
new file mode 100644
index 000000000..29b170667
--- /dev/null
+++ b/exampleSite/content/events/2016-warsaw/location.md
@@ -0,0 +1,15 @@
++++
+date = "2016-08-11T19:04:13+02:00"
+title = "location"
+type = "event"
+
++++
+
+DevOpsDays Warsaw 2016 will be held in Gromada Hotel Airport
+
+Gromada Warsaw Airport Hotel ***
+17 Stycznia Street No. 32
+02 - 148 Warsaw
+
+
+{{< event_map >}}
diff --git a/exampleSite/content/events/2016-warsaw/program.md b/exampleSite/content/events/2016-warsaw/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2016-warsaw/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+Join DevOpsDays Warsaw as a speaker and give a talk in front of hundreds of DevOps enthusiasts.
+We are announcing the Call for Papers. Deadline for submitting the
+applications expires on September, the 30th.
+
+
+
As a speaker you will:
+
+
get a free entry for the conference,
+
get feedback, pictures and video recordings of your talk,
+
enjoy your visit in Warsaw
+
reach eternal fame and glory
+
+
+
+ There are two types of talks you can give: Regular and Ignite.
+
+
+
Regular presentation is 30 minutes long and includes Q&A session
+
Ignite talk is 5 minutes long (20 slides; 15 seconds each)
+
+
Case studies of DevOps code creation or moving your company to this culture will be the most welcome.
+
+
To apply for regular presentation, please in the form on our website (fields marked with * are obligatory).
+
+
To apply for ignite talk, please in the form on our website (fields marked with * are obligatory).
+
diff --git a/exampleSite/content/events/2016-warsaw/sponsor.md b/exampleSite/content/events/2016-warsaw/sponsor.md
new file mode 100644
index 000000000..d14df36d7
--- /dev/null
+++ b/exampleSite/content/events/2016-warsaw/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-08-11T19:04:13+02:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-warsaw/welcome.md b/exampleSite/content/events/2016-warsaw/welcome.md
new file mode 100644
index 000000000..f9934550f
--- /dev/null
+++ b/exampleSite/content/events/2016-warsaw/welcome.md
@@ -0,0 +1,100 @@
++++
+date = "2016-08-11T19:04:13+02:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-warsaw"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+
+We are coming back with DevOpsDays in Poland.
+ We are extremely excited and would like to invite everyone from Europe and outside to attend, participate, and perhaps become a speaker.
+ Join us to share the adventure!
+
+ On the separate website you can find all the information about DevOpsDays Warsaw 2016.
+
+
+ {{< event_link page="propose" text="Propose a talk!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2016-washington-dc/DevOpsDaysDC_2016_attendees.png b/exampleSite/content/events/2016-washington-dc/DevOpsDaysDC_2016_attendees.png
new file mode 100644
index 000000000..b32e7bf44
Binary files /dev/null and b/exampleSite/content/events/2016-washington-dc/DevOpsDaysDC_2016_attendees.png differ
diff --git a/exampleSite/content/events/2016-washington-dc/conduct.md b/exampleSite/content/events/2016-washington-dc/conduct.md
new file mode 100644
index 000000000..dd8c1805d
--- /dev/null
+++ b/exampleSite/content/events/2016-washington-dc/conduct.md
@@ -0,0 +1,72 @@
++++
+date = "2016-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+## Conference Code of Conduct
+
+All attendees, speakers, sponsors and volunteers at our conference are required
+to agree with the following code of conduct. organizers will enforce this code
+throughout the event. We are expecting cooperation from all participants to help
+ensuring a safe environment for everybody. A strong community benefits everyone.
+To that end, please consider as a goal that you should always try to benefit the
+community by encouraging participation, open-mindedness, learning, and safety in
+every interaction. Behaviour outside of our community guidelines is unacceptable
+and should and will not be tolerated by anyone.
+
+
+
+ tl;dr: Don’t be a Jerk
+
+
+
+## The Quick Version
+
+Our conference is dedicated to providing a harassment-free conference experience
+for everyone, regardless of gender, age, sexual orientation, disability,
+physical appearance, body size, race, or religion (or lack thereof.) We do not
+tolerate harassment of conference participants in any form. Sexual language and
+imagery is not appropriate for any conference venue, including talks, workshops,
+parties, Twitter and other online media. Conference participants violating these
+rules may be sanctioned or expelled from the conference without a refund at the
+discretion of the conference organizers.
+
+## The Less Quick Version
+
+Harassment includes offensive verbal comments related to gender, age, sexual
+orientation, disability, physical appearance, body size, race, religion, sexual
+images in public spaces, deliberate intimidation, stalking, following, harassing
+photography or recording, sustained disruption of talks or other events,
+inappropriate physical contact, and unwelcome sexual attention.
+
+Participants asked to stop any harassing behavior are expected to comply
+immediately.
+
+Sponsors are also subject to the anti-harassment policy. In particular, sponsors
+should not use sexualized images, activities, or other material. Booth staff
+(including volunteers) should not use sexualized clothing/uniforms/costumes, or
+otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may
+take any action they deem appropriate, including warning the offender or
+expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have
+any other concerns, please contact a member of conference staff immediately.
+Conference staff can be identified as they'll be wearing branded t-shirts.
+
+Conference staff will be happy to help participants contact hotel/venue security
+or local law enforcement, provide escorts, or otherwise assist those
+experiencing harassment to feel safe for the duration of the conference. We
+value your attendance.
+
+We expect participants to follow these rules at conference and workshop venues
+and conference-related social events.
+
+### Need to reach the organizers?
+
+We will have organizers on-call throughout the conference to respond to any
+issues you may have. On-call organizer contact information will be posted closer
+to the event date. For now, if you have questions or concerns, please mail us at
+.
diff --git a/exampleSite/content/events/2016-washington-dc/contact.md b/exampleSite/content/events/2016-washington-dc/contact.md
new file mode 100644
index 000000000..0ede4c0ce
--- /dev/null
+++ b/exampleSite/content/events/2016-washington-dc/contact.md
@@ -0,0 +1,25 @@
++++
+date = "2016-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+Follow [@devopsdaysdc](https://twitter.com/devopsdaysdc) on twitter.
+
+What questions can we answer for you? Drop us an email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+{{< event_twitter devopsdaysdc >}}
+
+
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2016-washington-dc/location.md b/exampleSite/content/events/2016-washington-dc/location.md
new file mode 100644
index 000000000..978ad85e8
--- /dev/null
+++ b/exampleSite/content/events/2016-washington-dc/location.md
@@ -0,0 +1,41 @@
++++
+date = "2016-03-06T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+DevOpsDays DC 2016 was held at [The United States Patent and Trademark
+Office](http://www.uspto.gov/)'s Madison Auditorium at 600 Dulany Street,
+Alexandria, Virginia, just outside the District (but inside the Beltway!) Please
+see [USPTO's directions
+page](http://www.uspto.gov/about/contacts/locations/directions.jsp) for driving
+directions and parking information.
+
+View the [site layout](https://drive.google.com/open?id=0BwBlCaTaiDH-dnVTRXJfT3NBbEU)
+to see the sponsor tables, registration, and lunch area.
+
+## Local Hotels
+
+There are a number of hotels near the US Patent and Trademark Office. Some
+options include:
+
+* [The Westin Alexandria](http://www.westinalexandria.com/) - official hotel of
+DevOpsDays DC.
+* [Residence Inn Alexandria Old Town/Duke Street](http://www.marriott.com/hotels/travel/wasdk-residence-inn-alexandria-old-town-duke-street/)
+* [Hilton Alexandria Old Town](http://www3.hilton.com/en/hotels/virginia/hilton-alexandria-old-town-DCAOTHF/index.html)
+* [Wyndham Old Town Alexandria](https://www.extraholidays.com/washington-dc/wyndham-old-town-alexandria.aspx)
+
+DC and Northern Virginia traffic is consistently rated among the worst in the
+nation, so we recommend that you do not drive, especially if you are visiting
+from out of town. Instead, take [Metro](http://www.wmata.com/) to the event.
+USPTO is located a few blocks from the [King Street/Old
+Town](http://www.wmata.com/rail/station_detail.cfm?station_id=48) station, which
+is served by Blue and Yellow line trains. It's also a short ride from [National
+Airport (DCA)](http://www.flyreagan.com/dca/reagan-national-airport), our
+recommended airport for visitors from out of town. If you're arriving at Dulles
+(IAD), Baltimore (BWI), or Amtrak's Union Station, Metro's [trip
+planner](http://wmata.com/rider_tools/tripplanner/tripplanner_form_solo.cfm) can
+help you get to the event.
+
+
diff --git a/exampleSite/content/events/2016-washington-dc/program.md b/exampleSite/content/events/2016-washington-dc/program.md
new file mode 100644
index 000000000..25e05fb65
--- /dev/null
+++ b/exampleSite/content/events/2016-washington-dc/program.md
@@ -0,0 +1,30 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+### Wednesday, June 8
+
+* 7:30 - 9:00 - Registration
+* 9:00 - 12:05 - Keynote Presentations
+* 12:05 - 12:20 - Ignite Presentations
+* 12:00 - 1:00 - Create Open Space Agenda
+* 1:00 - 2:00 - Lunch
+* 2:00 - 2:15 - Ignite Presentations
+* 2:20 - 4:50 - Open spaces
+* 4:50 - 5:15 - Evening News
+* 7:00 - 9:00 - Happy Hour
+
+### Thursday, June 9
+
+* 8:00 - 9:00 - Registration
+* 9:00 - 11:55 - Keynote Presentations
+* 11:55 - 12:25 - Ignite Presentations
+* 12:25 - 1:00 - Create Open Space Agenda
+* 1:00 - 2:00 - Lunch
+* 2:00 - 4:15 - Open spaces
+* 4:15 - 5:00 - DevOpsDays Podcast
+
+[Full schedule details](http://devopsdaysdc2016.busyconf.com/schedule).
diff --git a/exampleSite/content/events/2016-washington-dc/propose.md b/exampleSite/content/events/2016-washington-dc/propose.md
new file mode 100644
index 000000000..0c2b2c279
--- /dev/null
+++ b/exampleSite/content/events/2016-washington-dc/propose.md
@@ -0,0 +1,38 @@
++++
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2016-washington-dc/sponsor.md b/exampleSite/content/events/2016-washington-dc/sponsor.md
new file mode 100644
index 000000000..85181525f
--- /dev/null
+++ b/exampleSite/content/events/2016-washington-dc/sponsor.md
@@ -0,0 +1,128 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+**DevOpsDays DC 2016 has ended.** Would you like to [sponsor DevOpsDays
+Baltimore](http://www.devopsdays.org/events/2016-baltimore/sponsor/)?
+
+
+
+
+
+
Packages
+
Silver
+
Gold
+
Platinum
+
+
+
+
SOLD OUT
+
SOLD OUT
+
SOLD OUT
+
+
+
2 included tickets
+
+
+
+
+
+
Logo on shared slide, rotating during breaks
+
+
+
+
+
+
Logo on DevOpsDays DC 2016 event website
+
+
+
+
+
+
Logo on all email communication
+
+
+
+
+
+
1 minute pitch to full audience (including streaming audience)
+
+
+
+
+
+
1 additional tickets (3 in total)
+
+
+
+
+
+
3 additional tickets (5 in total)
+
+
+
+
+
+
Shared table for swag
+
+
+
+
+
+
Dedicated table in preferred location for swag
+
+
+
+
+
+
+
+### Silver - SOLD OUT
+
+* 2 included tickets
+* Logo on shared slide, rotating during breaks
+* Logo on DevOpsDays Washington, DC 2016 event website
+
+### Gold - SOLD OUT
+
+* All benefits of Silver sponsors
+* Logo on all email communication
+* 1 additional ticket, 3 in total
+* Shared table for swag
+
+### Platinum - SOLD OUT
+
+* All benefits of Gold sponsors
+* 1 minute pitch to full audience, including streaming audience
+* 3 additional tickets, 5 in total
+* Dedicated table for swag
+
+We greatly value sponsors for this open event.
+
+Although DevOpsDays DC 2016 has ended, there will be another
+DevOpsDays in the area later this Summer. Checkout the [sponsorship
+opportunities for DevOpsDays
+Baltimore](http://www.devopsdays.org/events/2016-baltimore/sponsor/).
+
+---
+
+DevOpsDays is a self-organizing conference for DevOps practitioners that depends
+on your sponsorships to happen. However, because of the nature of the event, we
+do not have vendor booths or book product pitches.
+
+Gold sponsors do get a table they can hang out at and put materials on for
+interested people to come visit during breaks, and of course all attendees are
+welcome to propose any subject they want during the open spaces, but this is not
+'that kind of conference' and heavy marketing will probably work against you
+when trying to make a good impression on the attendees. The best thing to do is
+send engineers to interact with the experts at DevOpsDays on their own terms.
+
diff --git a/exampleSite/content/events/2016-washington-dc/welcome.md b/exampleSite/content/events/2016-washington-dc/welcome.md
new file mode 100644
index 000000000..97d84214c
--- /dev/null
+++ b/exampleSite/content/events/2016-washington-dc/welcome.md
@@ -0,0 +1,62 @@
++++
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-washington-dc"]
+
+
++++
+
+
+## DevOpsDays DC 2016 - June 8 & 9
+
+
+
+### A house divided against itself cannot stand.
+
+**_Change is in session!_**
+DevOpsDays DC was held **June 8 and 9, 2016** at the {{< event_link page="location"
+text="US Patent and Trademark Office" >}} in Alexandria, Virginia.
+
+## Review The Video
+
+
+
+Courtesy of our Platinum and Venue Sponsor, the [US Patent and Trademark
+Office](http://www.uspto.gov/). Archived video is available via
+[Livestream.com](http://livestream.com/uspto/Devops2016).
+
+## Why Attend?
+
+Whether you're in government, academia, or the private sector, _DevOpsDays is
+for you._
+
+Whether you're in operations, development, QA, security, or any other
+department, _DevOpsDays is for you._
+
+Whether you want to learn about DevOps, share your experiences, or just talk
+shop with DevOps practitioners, _DevOpsDays is for you._
+
+DevOpsDays are a mix of keynote sessions and [open
+spaces](http://en.wikipedia.org/wiki/Open_Space_Technology).
+
+## About Washington, DC
+
+If all you know of Washington, DC is what you see on C-SPAN or _House of Cards_,
+you're missing out. While its importance as the Nation's Capital and center of
+government is undisputed, the "DMV" (District, Maryland, and Virginia) is also
+home to innovative startups, leading universities, and world-class arts and
+culture.
+
+If you're local, you already know the diversity of our DevOps community. If
+you're coming in from elsewhere, prepare to mix with DevOps leaders from every
+segment of our vibrant local scene. And, of course, take some time to check out
+everything else the Nation's Capital has to offer, from the many free
+Smithsonian museums to great food and drink!
+
+For those coming from out of town, there are flights from just about everywhere
+to our three local airports, and there are several hotels nearby. More details
+are on the {{< event_link page="location" text="location page" >}}.
+
diff --git a/exampleSite/content/events/2017-amsterdam/conduct.md b/exampleSite/content/events/2017-amsterdam/conduct.md
new file mode 100644
index 000000000..61e283a95
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-08-10T20:18:13+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-amsterdam/contact.md b/exampleSite/content/events/2017-amsterdam/contact.md
new file mode 100644
index 000000000..945f1e372
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/contact.md
@@ -0,0 +1,16 @@
++++
+date = "2016-08-10T20:18:13+02:00"
+title = "contact"
+type = "event"
+tags = ["amsterdam","amsterdam-2017"]
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-amsterdam/location.md b/exampleSite/content/events/2017-amsterdam/location.md
new file mode 100644
index 000000000..e28c25e14
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/location.md
@@ -0,0 +1,47 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+heading = "devopsdays Amsterdam - Event Location"
+title = "Event Location"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+
+### Conference Location
+
+The conference is located at [Pakhuis de Zwijger](http://www.dezwijger.nl/ "Website of Pakhuis de Zwijger")
+
+Piet Heinkade 179
+1019 HC Amsterdam
+The Netherlands
+
+{{< event_map >}}
+
+## Getting there and accommodation
+
+### Transportation
+
+Amsterdam has a fantastic public transportation system.
+- Buses [48](http://maps.gvb.nl/en/lijnen/48), [246](http://maps.gvb.nl/en/lijnen/246) and [759](http://maps.gvb.nl/en/lijnen/759) stop right in front of the conference.
+- Tram [26](http://maps.gvb.nl/en/lijnen/26), departing from Amsterdam Centraal Station (main train station in the city).
+
+More information can be obtained by using the [GVB](http://en.gvb.nl/) or [9292](http://9292.nl/en) websites. Both have excellent apps in the iOS ([GVB](https://itunes.apple.com/nl/app/gvb/id370393784) & [9292](https://itunes.apple.com/nl/app/9292/id556557690)) and Google Play ([GVB](https://play.google.com/store/apps/details?id=nl.moopmobility.gvb&hl=en)) & [9292](https://play.google.com/store/apps/details?id=nl.negentwee&hl=en)) store. Other apps (like Google Maps) have great integration as well.
+
+##### A note to out of towners in in regards to obtaining a reloadable card for public transportation.
+
+You can purchase an "OV chipkaart" at Amsterdam Centraal and most large metro stations (including Schiphol). Note that the unattended machines do not handle non-EU issued (e.g. Chip+Signature) cards well. Some U.S. Credit Unions now offer Chip+Pin technology on their *debit* card (note: not *credit* card). If your card doesn't work or want to use Euros (other than coins), there is a customer service center located on the "IJ side" of Amsterdam Centraal where you can purchase a chipkaart in person at the [Service Office](https://www.nsinternational.nl/en/tickets-services/opening-hours-ticket-and-service-shops "Link to NS International Service Office"). If you're arriving via Schiphol - a similar service is offered in the main train hall
+
+#### Alternative methods of transportation
+- [Uber](https://www.uber.com/)
+- [Rent A Bike](http://www.iamsterdam.com/en/visiting/plan-your-trip/getting-around/rental/bike-hire)
+- And if you want must -- [Taxis](http://www.iamsterdam.com/en/visiting/plan-your-trip/getting-around/taxis)
+
+
+### Accommodations
+Amsterdam has amazing hotels and incredible amount of Airbnbs spread out all over the city that allows you to experience life as an Amsterdammer (Beware of the dark red bike paths!). Besides Airbnbs, here is a list of hotels that are near to the [Pakhuis de Zwijger](http://www.dezwijger.nl/ "Website of Pakhuis de Zwijger").
+
+* [Mövenpick Hotel Amsterdam City Centre](http://www.movenpick.com/en/europe/netherlands/amsterdam/hotel-amsterdam/overview/)
+* [DoubleTree by Hilton Hotel Amsterdam Centraal Station](http://doubletree3.hilton.com/en/hotels/netherlands/doubletree-by-hilton-amsterdam-centraal-station-AMSCSDI/index.html)
+* [Hotel NH Barbizon Place](http://www.nh-hotels.nl/hotel/nh-collection-amsterdam-barbizon-palace)
+* [Inntel Hotels Amsterdam Centre](http://www.inntelhotelsamsterdamcentre.nl/)
diff --git a/exampleSite/content/events/2017-amsterdam/program.md b/exampleSite/content/events/2017-amsterdam/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-amsterdam/propose.md b/exampleSite/content/events/2017-amsterdam/propose.md
new file mode 100644
index 000000000..b8a998eed
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-08-10T20:18:13+02:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-amsterdam/sponsor.md b/exampleSite/content/events/2017-amsterdam/sponsor.md
new file mode 100644
index 000000000..5037a6e72
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-08-10T20:18:13+02:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-amsterdam/welcome.md b/exampleSite/content/events/2017-amsterdam/welcome.md
new file mode 100644
index 000000000..a4d0ba8b9
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/welcome.md
@@ -0,0 +1,94 @@
++++
+date = "2016-08-10T20:18:13+02:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-amsterdam"]
+tags = ["amsterdam","amsterdam-2017"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-atlanta/conduct.md b/exampleSite/content/events/2017-atlanta/conduct.md
new file mode 100644
index 000000000..ce2e46b6b
--- /dev/null
+++ b/exampleSite/content/events/2017-atlanta/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-atlanta/contact.md b/exampleSite/content/events/2017-atlanta/contact.md
new file mode 100644
index 000000000..eeb9de263
--- /dev/null
+++ b/exampleSite/content/events/2017-atlanta/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-atlanta/location.md b/exampleSite/content/events/2017-atlanta/location.md
new file mode 100644
index 000000000..aac3e5e66
--- /dev/null
+++ b/exampleSite/content/events/2017-atlanta/location.md
@@ -0,0 +1,31 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "location"
+type = "event"
+
++++
+
+**devopsdays Atlanta 2017** will be held at the Historic Academy of Medicine at Georgia Tech:
+
+875 West Peachtree St., NW
+Atlanta, GA 30309
+
+## Driving
+
+Parking will be provided free of charge.
+
+
+
+[View on Google Maps](https://goo.gl/maps/QjHRM8LhG8L2)
+
+## Airport
+
+There is a taxi stand outside of the baggage claim at the airport. Most taxi companies have a flat, standard rate from the airport to Midtown of $32. You may pay a little less or a little more, but please be aware about the taxi that you choose: ensure that it’s a legitimate taxi company and agree upon how the price will be determined (flat rate or meter) before putting your luggage inside. If you need help, do not hesitate to ask an airport employee; we’re known to be polite here in Georgia! Unfortunately, [ride-share companies like Uber](http://www.marketplace.org/2015/11/24/business/taxi-and-uber-fight-curb-atlanta-airport) are not allows to pick-up customers at the airport.
+
+## Public Transportation
+
+[MARTA](http://www.itsmarta.com/) serves the Historic Academy of Medicine. Follow the signs from baggage claim at the airport to get to the MARTA station. From Hartsfield International Airport take MARTA to the Midtown Station. The Historic Academy of Medicine is less than a quarter-mile walk from the MARTA station, or ride the [Georgia Tech Trolly](http://pts.gatech.edu/Documents/trolley%20rambler%2014%2015%20map.pdf).
+
+## Lodging
+
+There are lots of popular hotels in Midtown. We have not reserved any special rates.
diff --git a/exampleSite/content/events/2017-atlanta/program.md b/exampleSite/content/events/2017-atlanta/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-atlanta/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-atlanta/propose.md b/exampleSite/content/events/2017-atlanta/propose.md
new file mode 100644
index 000000000..7745c0011
--- /dev/null
+++ b/exampleSite/content/events/2017-atlanta/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-atlanta/sponsor.md b/exampleSite/content/events/2017-atlanta/sponsor.md
new file mode 100644
index 000000000..be527062c
--- /dev/null
+++ b/exampleSite/content/events/2017-atlanta/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-atlanta/welcome.md b/exampleSite/content/events/2017-atlanta/welcome.md
new file mode 100644
index 000000000..2d2ca688e
--- /dev/null
+++ b/exampleSite/content/events/2017-atlanta/welcome.md
@@ -0,0 +1,93 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-atlanta"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-austin/contact.md b/exampleSite/content/events/2017-austin/contact.md
new file mode 100644
index 000000000..f10f439ab
--- /dev/null
+++ b/exampleSite/content/events/2017-austin/contact.md
@@ -0,0 +1,19 @@
++++
+City = "Austin"
+Year = "2017"
+date = "2016-08-25T06:01:53-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-austin/sponsor.md b/exampleSite/content/events/2017-austin/sponsor.md
new file mode 100644
index 000000000..44c7fa32a
--- /dev/null
+++ b/exampleSite/content/events/2017-austin/sponsor.md
@@ -0,0 +1,12 @@
++++
+City = "Austin"
+Year = "2017"
+date = "2016-08-25T06:01:53-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+
+We greatly value sponsors for this open event. If you are interested in sponsoring [view our sponsor packages](http://www.devopsdaysaustin.com/#sponsors).
diff --git a/exampleSite/content/events/2017-austin/welcome.md b/exampleSite/content/events/2017-austin/welcome.md
new file mode 100644
index 000000000..a0b58320e
--- /dev/null
+++ b/exampleSite/content/events/2017-austin/welcome.md
@@ -0,0 +1,24 @@
++++
+City = "Austin"
+Year ="2017"
+date = "2016-08-25T06:01:53-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-austin"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+Watch [www.devopsdaysaustin.com](http://www.devopsdaysaustin.com) for more up to date information as it becomes available.
+
+
+ {{< event_logo >}}
+
+
+
+
+
+ Location: Darrel K. Royal Texas Memorial Stadium
+
diff --git a/exampleSite/content/events/2017-baltimore/conduct.md b/exampleSite/content/events/2017-baltimore/conduct.md
new file mode 100644
index 000000000..92b8defd0
--- /dev/null
+++ b/exampleSite/content/events/2017-baltimore/conduct.md
@@ -0,0 +1,40 @@
++++
+date = "2016-05-20T09:31:15-04:00"
+title = "conduct"
+type = "event"
+aliases = [
+ "/events/2017-baltimore/conduct",
+ "/events/2016-baltimore/conduct"
+]
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-baltimore/contact.md b/exampleSite/content/events/2017-baltimore/contact.md
new file mode 100644
index 000000000..49a6b93da
--- /dev/null
+++ b/exampleSite/content/events/2017-baltimore/contact.md
@@ -0,0 +1,31 @@
++++
+date = "2016-05-20T09:31:15-04:00"
+title = "contact"
+type = "event"
+aliases = [
+ "/events/2017-baltimore/contact",
+ "/events/2016-baltimore/contact"
+]
+
++++
+
+Follow [@DevOpsDaysBmore](https://twitter.com/devopsdaysbmore) on twitter.
+
+What questions can we answer for you? Drop us an email: {{< email_organizers >}}
+
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+{{< event_twitter devopsdaysbmore >}}
+
+
+
+
+
+[Full schedule details](http://devopsdaysbaltimore2017.busyconf.com/schedule).
diff --git a/exampleSite/content/events/2017-baltimore/registration.md b/exampleSite/content/events/2017-baltimore/registration.md
new file mode 100644
index 000000000..494ec83ab
--- /dev/null
+++ b/exampleSite/content/events/2017-baltimore/registration.md
@@ -0,0 +1,9 @@
++++
+date = "2016-05-20T09:31:15-04:00"
+title = "registration"
+type = "event"
+
+
++++
+
+[Register Now](https://devopsdaysbaltimore2017.busyconf.com/bookings/new)!
diff --git a/exampleSite/content/events/2017-baltimore/sponsor.md b/exampleSite/content/events/2017-baltimore/sponsor.md
new file mode 100644
index 000000000..afcaf1e13
--- /dev/null
+++ b/exampleSite/content/events/2017-baltimore/sponsor.md
@@ -0,0 +1,206 @@
++++
+date = "2016-05-20T09:31:15-04:00"
+title = "sponsor"
+type = "event"
+aliases = [
+ "/events/2017-baltimore/sponsor",
+ "/events/2016-baltimore/sponsor"
+]
+
++++
+
+We greatly value sponsors for this open event. Have questions about sponsoring?
+Please contact us at {{< email_organizers >}}.
+
+[Sponsor DevOpsDays Baltimore now](https://devopsdaysbaltimore2017.busyconf.com/bookings/new?discount=SPONSOR).
+
+
+
+
+
+
Packages
+
Community
+
Media
+
Silver
+
Gold
+
Platinum
+
+
+
+
$0 USD
+
$0 USD
+
$1,000 USD
+
$3,000 USD
+
$5,000 USD
+
+
+
1 included ticket
+
+
+
+
+
+
+
+
Logo on shared slide, rotating during breaks
+
+
+
+
+
+
+
+
Logo on DevOpsDays Baltimore 2017 event website
+
+
+
+
+
+
+
+
Logo on all email communication
+
+
+
+
+
+
+
+
1 minute pitch to full audience (including streaming audience)
+
+
+
+
+
+
+
+
1 additional ticket (2 in total)
+
+
+
+
+
+
+
+
2 additional tickets (3 in total)
+
+
+
+
+
+
+
+
4 additional tickets (5 in total)
+
+
+
+
+
+
+
+
Shared table for swag
+
+
+
+
+
+
+
+
Dedicated table in preferred location for swag
+
+
+
+
+
+
+
+
+
+We greatly value sponsors for this open event. If you are interested in other
+types of sponsorships, please contact us directly at {{< email_organizers >}}.
+
+DevOps Days is not 'that kind of conference' and heavy marketing will probably
+work against you when trying to make a good impression on the attendees. Contact
+{{< email_organizers >}} for some ideas about how to make the most of
+your sponsorship.
+
+[Sponsor DevOpsDays Baltimore now](https://devopsdaysbaltimore2017.busyconf.com/bookings/new?discount=SPONSOR).
+
+### Community - $0
+
+The community sponsorship is ideal for local meetups, co-working spaces, and
+other communities who support DevOps. This sponsorship is free but we ask that
+you share information about DevOpsDays Baltimore with your members in order to
+become a Community Sponsor.
+
+* 1 ticket
+* 10% discount code to share with your members
+* Logo on shared slide, rotating during breaks
+* Logo on DevOpsDays Baltimore 2017 event website
+* Please contact {{< email_organizers >}} for details about becoming a community
+sponsor.
+
+### Media - $0
+
+The media sponsorship is ideal for podcasts, blogs, news outlets, and other
+media who support DevOps. This sponsorship is free but we ask that you share
+information about DevOpsDays Baltimore with your audience in order to become a
+Community Sponsor.
+
+* 1 ticket
+* 10% discount code to share with your audience
+* Logo on shared slide, rotating during breaks
+* Logo on DevOpsDays Baltimore 2017 event website
+* Please contact {{< email_organizers >}} for details about becoming a media
+sponsor.
+
+### Silver - $1,000
+
+* 2 included tickets
+* Logo on shared slide, rotating during breaks
+* Logo on DevOpsDays Baltimore 2017 event website
+* Become a Silver sponsor now.
+
+### Gold - $3,000
+
+* All benefits of Silver sponsors
+* Logo on all email communication
+* 1 additional ticket, 3 in total
+* Shared table for swag
+* Become a Gold sponsor now.
+
+### Platinum - $5,000
+
+* All benefits of Gold sponsors
+* 1 minute pitch to full audience, including streaming audience
+* 2 additional tickets, 5 in total
+* Dedicated table for swag
+* Become a Platinum sponsor now.
+
+We greatly value sponsors for this open event. If you are interested in other
+types of sponsorships, please contact us directly at {{< email_organizers >}}.
+
+---
+
+DevOpsDays is a self-organizing conference for DevOps practitioners that depends
+on your sponsorships to happen. However, because of the nature of the event, we
+do not have vendor booths or book product pitches.
+
+Platinum sponsors do get a table they can hang out at and put materials on for
+interested people to come visit during breaks, and of course all attendees are
+welcome to propose any subject they want during the open spaces, but this is not
+'that kind of conference' and heavy marketing will probably work against you
+when trying to make a good impression on the attendees. The best thing to do is
+send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+We greatly value sponsors for this open event. If you are interested in
+sponsoring, please drop us an email at {{< email_organizers >}} or [sponsor
+DevOpsDays Baltimore
+now](https://devopsdaysbaltimore2017.busyconf.com/bookings/new?discount=SPONSOR).
diff --git a/exampleSite/content/events/2017-baltimore/welcome.md b/exampleSite/content/events/2017-baltimore/welcome.md
new file mode 100644
index 000000000..557bc5705
--- /dev/null
+++ b/exampleSite/content/events/2017-baltimore/welcome.md
@@ -0,0 +1,139 @@
++++
+date = "2016-05-20T09:31:15-04:00"
+title = "welcome"
+type = "event"
+aliases = [
+ "/events/2017-baltimore",
+ "/events/2016-baltimore",
+ "/events/2017-baltimore/welcome",
+ "/events/2016-baltimore/welcome"
+]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+ {{< event_logo >}}
+
+
+
+
+
+ DevOpsDays is a unique conference for anyone interested in building or
+ operating a high-velocity, software-driven business or agency. The
+ program
+ includes keynote talks, Ignite talks, and participant-organized open space
+ discussions on the topics most important to the attendees.
+
diff --git a/exampleSite/content/events/2017-beijing/conduct.md b/exampleSite/content/events/2017-beijing/conduct.md
new file mode 100644
index 000000000..745bc3a6e
--- /dev/null
+++ b/exampleSite/content/events/2017-beijing/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-12-12T09:30:11+08:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-beijing/contact.md b/exampleSite/content/events/2017-beijing/contact.md
new file mode 100644
index 000000000..958b1f579
--- /dev/null
+++ b/exampleSite/content/events/2017-beijing/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-12-12T09:30:11+08:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-beijing/location.md b/exampleSite/content/events/2017-beijing/location.md
new file mode 100644
index 000000000..e0010f15a
--- /dev/null
+++ b/exampleSite/content/events/2017-beijing/location.md
@@ -0,0 +1,13 @@
++++
+date = "2016-12-12T09:30:11+08:00"
+title = "location"
+type = "event"
+
++++
+
+We have an exciting new venue for our 2017 conference, [Sofitel Wanda Beijing hotel](http://www.sofitel.com)
+93 Jianguo Road Tower C Wanda Plaza Chaoyang District,100022 BEIJING,CHINA
+
+
+
+
diff --git a/exampleSite/content/events/2017-beijing/program.md b/exampleSite/content/events/2017-beijing/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-beijing/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-beijing/propose.md b/exampleSite/content/events/2017-beijing/propose.md
new file mode 100644
index 000000000..ec419eeba
--- /dev/null
+++ b/exampleSite/content/events/2017-beijing/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-12-12T09:30:11+08:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-beijing/sponsor.md b/exampleSite/content/events/2017-beijing/sponsor.md
new file mode 100644
index 000000000..ff4d5c615
--- /dev/null
+++ b/exampleSite/content/events/2017-beijing/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-12-12T09:30:11+08:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-beijing/welcome.md b/exampleSite/content/events/2017-beijing/welcome.md
new file mode 100644
index 000000000..f35013313
--- /dev/null
+++ b/exampleSite/content/events/2017-beijing/welcome.md
@@ -0,0 +1,99 @@
++++
+date = "2016-12-12T09:30:11+08:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-beijing"]
+
++++
+
+
+
+ {{< event_logo >}}
+
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**DevOpsDays is coming to {{< event_location >}}!**
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-charlotte/agenda.md b/exampleSite/content/events/2017-charlotte/agenda.md
new file mode 100644
index 000000000..e27ce9a18
--- /dev/null
+++ b/exampleSite/content/events/2017-charlotte/agenda.md
@@ -0,0 +1,8 @@
++++
+date = "2017-01-10T10:34:20-04:00"
+title = "agenda"
+type = "event"
+
++++
+View the DevOpsDays Charlotte 2017 schedule & directory.
+
diff --git a/exampleSite/content/events/2017-charlotte/conduct.md b/exampleSite/content/events/2017-charlotte/conduct.md
new file mode 100644
index 000000000..126c59bbc
--- /dev/null
+++ b/exampleSite/content/events/2017-charlotte/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-09-22T10:34:20-04:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-charlotte/contact.md b/exampleSite/content/events/2017-charlotte/contact.md
new file mode 100644
index 000000000..736fb18cc
--- /dev/null
+++ b/exampleSite/content/events/2017-charlotte/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-09-22T10:34:20-04:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-charlotte/location.md b/exampleSite/content/events/2017-charlotte/location.md
new file mode 100644
index 000000000..d85641755
--- /dev/null
+++ b/exampleSite/content/events/2017-charlotte/location.md
@@ -0,0 +1,14 @@
++++
+date = "2016-09-22T10:34:20-04:00"
+title = "location"
+type = "event"
+
++++
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-charlotte/propose.md b/exampleSite/content/events/2017-charlotte/propose.md
new file mode 100644
index 000000000..d6330ef05
--- /dev/null
+++ b/exampleSite/content/events/2017-charlotte/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-09-22T10:34:20-04:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-charlotte/sponsor.md b/exampleSite/content/events/2017-charlotte/sponsor.md
new file mode 100644
index 000000000..15032091f
--- /dev/null
+++ b/exampleSite/content/events/2017-charlotte/sponsor.md
@@ -0,0 +1,88 @@
++++
+date = "2016-09-22T10:34:20-04:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
Sponsorship Levels
+
+
Gold Sponsorship ($5,000)
+
Details
+
+
5 tickets to the event
+
Logo on event website
+
Logo on all email communication
+
Logo on Eventbrite registration page
+
Logo on slides during breaks
+
1 minute pitch to full audience
+
Booth/Table space
+
Shoutout via Twitter with $100 promoted tweet campaign
+
+
+
+DevOpsDays is coming to {{< event_location >}} in Charlotte!
+
+DevOpsDays is at the forefront of shared knowledge, collaboration, culture and inclusion of developers, operations and anyone involved with technology. The conference will include a mix of presentations, ignite talks, ignite karaoke and open spaces covering a broad range of culture, devops and technical topics. Your ticket includes breakfast, lunch, drinks and conference swag.
+
+
+
+
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+ Register
+
+
+ {{< event_link page="registration" text="Register to attend the event here!" >}}
+
Charity Majors is the cofounder and CTO of Honeycomb, a new startup focused on mining machine data. Previously, Charity ran infrastructure at Parse and was an engineering manager at Facebook. She also worked with the RocksDB team to build and deploy the world’s first Mongo + Rocks in production. Charity likes single malt scotch.
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-chicago/conduct.md b/exampleSite/content/events/2017-chicago/conduct.md
new file mode 100644
index 000000000..086a7711e
--- /dev/null
+++ b/exampleSite/content/events/2017-chicago/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-10-17T08:26:34-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-chicago/contact.md b/exampleSite/content/events/2017-chicago/contact.md
new file mode 100644
index 000000000..06a603c27
--- /dev/null
+++ b/exampleSite/content/events/2017-chicago/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-10-17T08:26:34-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-chicago/location.md b/exampleSite/content/events/2017-chicago/location.md
new file mode 100644
index 000000000..1d3f3c5d3
--- /dev/null
+++ b/exampleSite/content/events/2017-chicago/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-10-17T08:26:34-05:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-chicago/program.md b/exampleSite/content/events/2017-chicago/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-chicago/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-chicago/propose.md b/exampleSite/content/events/2017-chicago/propose.md
new file mode 100644
index 000000000..46de56e81
--- /dev/null
+++ b/exampleSite/content/events/2017-chicago/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-10-17T08:26:34-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-chicago/sponsor.md b/exampleSite/content/events/2017-chicago/sponsor.md
new file mode 100644
index 000000000..9eac97307
--- /dev/null
+++ b/exampleSite/content/events/2017-chicago/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-10-17T08:26:34-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-chicago/welcome.md b/exampleSite/content/events/2017-chicago/welcome.md
new file mode 100644
index 000000000..3524d2d39
--- /dev/null
+++ b/exampleSite/content/events/2017-chicago/welcome.md
@@ -0,0 +1,92 @@
++++
+date = "2016-10-17T08:26:34-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-chicago"]
+
++++
+
+
+
+
+Welcome! The group that brought you DevOpsDays Chicago 2014-2016 is back together and planning the 2017 event. We're encouraged by the feedback from previous year's events and are determined to bring an improved experience and continue the DevOps conversation for 2017 in Chicago.
+
+
+ {{< event_logo >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-dallas/conduct.md b/exampleSite/content/events/2017-dallas/conduct.md
new file mode 100644
index 000000000..e067a7e85
--- /dev/null
+++ b/exampleSite/content/events/2017-dallas/conduct.md
@@ -0,0 +1,43 @@
++++
+date = "2016-12-24T11:00:07-07:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-dallas/contact.md b/exampleSite/content/events/2017-dallas/contact.md
new file mode 100644
index 000000000..697ef4831
--- /dev/null
+++ b/exampleSite/content/events/2017-dallas/contact.md
@@ -0,0 +1,24 @@
++++
+date = "2016-12-24T11:00:07-07:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-dallas/location.md b/exampleSite/content/events/2017-dallas/location.md
new file mode 100644
index 000000000..fe050a271
--- /dev/null
+++ b/exampleSite/content/events/2017-dallas/location.md
@@ -0,0 +1,17 @@
++++
+date = "2016-12-24T11:00:07-07:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-dallas/program.md b/exampleSite/content/events/2017-dallas/program.md
new file mode 100644
index 000000000..32073ae54
--- /dev/null
+++ b/exampleSite/content/events/2017-dallas/program.md
@@ -0,0 +1,355 @@
++++
+date = "2016-12-24T11:00:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-dallas/propose.md b/exampleSite/content/events/2017-dallas/propose.md
new file mode 100644
index 000000000..1c399668d
--- /dev/null
+++ b/exampleSite/content/events/2017-dallas/propose.md
@@ -0,0 +1,44 @@
++++
+date = "2016-12-24T11:00:07-07:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-dallas/sponsor.md b/exampleSite/content/events/2017-dallas/sponsor.md
new file mode 100644
index 000000000..3ac146c7e
--- /dev/null
+++ b/exampleSite/content/events/2017-dallas/sponsor.md
@@ -0,0 +1,56 @@
++++
+date = "2016-12-24T11:00:07-07:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-dallas/welcome.md b/exampleSite/content/events/2017-dallas/welcome.md
new file mode 100644
index 000000000..f895b3064
--- /dev/null
+++ b/exampleSite/content/events/2017-dallas/welcome.md
@@ -0,0 +1,102 @@
++++
+date = "2016-12-24T11:00:07-07:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-dallas"]
+
++++
+
+
+
+
+**DevOpsDays was a huge success that it is returning to {{< event_location >}} in 2017!**
+
+
+ {{< event_logo >}}
+
+
+We're still working out all the details. If you'd like to help out, email us!
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-denver/conduct.md b/exampleSite/content/events/2017-denver/conduct.md
new file mode 100644
index 000000000..219dbffe8
--- /dev/null
+++ b/exampleSite/content/events/2017-denver/conduct.md
@@ -0,0 +1,48 @@
++++
+City = "Denver"
+Year = "2017"
+date = "2017-03-06T21:17:08-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+
+Please read the anti-harassment policy and code of conduct following the important contact information:
+
+* Local law enforcement: Denver Police - Non-Emergency Help [720-913-2000](tel:720-913-2000), Emergency call 911
+* Sexual assault hotlines: The Blue Bench: English [303-322-7273](tel:303-322-7273), Spanish [303-329-0031](tel:303-329-0031), [1-888-394-8044](tel:1-888-394-8044)
+* Medical Emergency: Call 911
+* Local taxi companies: [Yellow Cab](http://www.denveryellowcab.com) - [303-777-7777](tel:303-777-7777),
+[Metro Taxi](http://www.metrotaxidenver.com/) [303-333-3333](tel:303-333-3333)
+
+##ANTI-HARASSMENT POLICY
+
+DevOpsDays Denver is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+##CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
+
diff --git a/exampleSite/content/events/2017-denver/contact.md b/exampleSite/content/events/2017-denver/contact.md
new file mode 100644
index 000000000..dc87270a2
--- /dev/null
+++ b/exampleSite/content/events/2017-denver/contact.md
@@ -0,0 +1,21 @@
++++
+City = "Denver"
+Year = "2017"
+date = "2017-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+{{< event_twitter devopsdaysrox >}}
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+### Our local team
+
+{{< list_organizers >}}
+
+### The core devopsdays organizer group
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-denver/location.md b/exampleSite/content/events/2017-denver/location.md
new file mode 100644
index 000000000..91b8ff0b0
--- /dev/null
+++ b/exampleSite/content/events/2017-denver/location.md
@@ -0,0 +1,16 @@
++++
+City = "Denver"
+Year = "2017"
+date = "2017-01-10T11:29:13-07:00"
+title = "location"
+type = "event"
+
++++
+
+### Conference location:
+
+DevOpsDays Denver will moving out of the data center and into the cloud! The part of the cloud will be played by the EXDO event center.
+
+[Exdo Event Center](http://www.exdoevents.com/) 1399 35th St. Denver, CO 80205
+
+
diff --git a/exampleSite/content/events/2017-denver/propose.md b/exampleSite/content/events/2017-denver/propose.md
new file mode 100644
index 000000000..b349422d4
--- /dev/null
+++ b/exampleSite/content/events/2017-denver/propose.md
@@ -0,0 +1,43 @@
++++
+City = "Denver"
+Year = "2017"
+date = "2017-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+---
+
+Submit your talk today! The submission form can be found [Here](http://bit.ly/DODROXCFP2017)
+
+---
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+
+How to submit a proposal: [Fill out our handy form](http://bit.ly/DODROXCFP2017) with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
diff --git a/exampleSite/content/events/2017-denver/sponsor.md b/exampleSite/content/events/2017-denver/sponsor.md
new file mode 100644
index 000000000..aedb315f7
--- /dev/null
+++ b/exampleSite/content/events/2017-denver/sponsor.md
@@ -0,0 +1,48 @@
++++
+City = "Denver"
+Year = "2017"
+date = "Mon Jan 9 22:24:46 MST 2017"
+title = "sponsor"
+type = "event"
+
++++
+
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]({{< email_organizers >}}).
+
+## Sponsorship Packages
+
+For more information about sponsorship checkout our [Sponsorship Prospectus](https://drive.google.com/file/d/0B2ne1nlfYmP-R0VYb0VGV2tDbjg)
+
+### Gold Sponsorship
+
+* 4 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* 1 minute pitch to full audience (including streaming audience)
+* Demo a product (10 min) during Open Space Session
+* Booth/Table space
+
+### Silver Sponsorship
+
+* 4 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* Booth/Table space
+* Display of your roll-up/pop-up banner in the venue near high traffic areas
+
+### Bronze Sponsorship
+* 2 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Shared table for giveaways
+
+### Social Hour Sponsorship – Availability 1
+
+* 2 tickets to the event
+* 6 tickets to the event
+* Logo on DevOpsDays Rockies event website
+* Logo on all email communication
+* 1 minute pitch to full audience (including streaming audience)
+* Demo a product (10 min) during Open Space Session
+* Booth/Table space
+* Full access to decorate bar and host activities during Happy Hour
diff --git a/exampleSite/content/events/2017-denver/welcome.md b/exampleSite/content/events/2017-denver/welcome.md
new file mode 100644
index 000000000..4f1e7d5b7
--- /dev/null
+++ b/exampleSite/content/events/2017-denver/welcome.md
@@ -0,0 +1,37 @@
++++
+City = "Denver"
+Year ="2017"
+date = "2017-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-denver"]
+
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+ {{< event_logo >}}
+
+
+DevOpsDays is back for its 3rd anual event in the Rocky Mountains {{< event_start >}} - {{< event_end >}}
+
+
+
+ Location
+
+
+ {{< event_link page="location" text="Exdo Event Center, Denver" >}}
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+{{< event_twitter devopsdaysrox >}}
diff --git a/exampleSite/content/events/2017-detroit/conduct.md b/exampleSite/content/events/2017-detroit/conduct.md
new file mode 100644
index 000000000..80a9cc987
--- /dev/null
+++ b/exampleSite/content/events/2017-detroit/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-12-11T14:38:53-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-detroit/contact.md b/exampleSite/content/events/2017-detroit/contact.md
new file mode 100644
index 000000000..f0c28cd96
--- /dev/null
+++ b/exampleSite/content/events/2017-detroit/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-12-11T14:38:53-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-detroit/location.md b/exampleSite/content/events/2017-detroit/location.md
new file mode 100644
index 000000000..a03d08ca7
--- /dev/null
+++ b/exampleSite/content/events/2017-detroit/location.md
@@ -0,0 +1,18 @@
++++
+date = "2016-12-11T14:38:53-05:00"
+title = "location"
+type = "event"
+
++++
+
+
Conference Location
+DevOpsDays Detroit 2017 is being held at the College for Creative Studies, A. Alfred Taubman Center for Design Education. The building address is: 460 W. Baltimore Ave, Detroit, MI 48202. Maps and Directions
+The A. Alfred Taubman Center for Design Education is an educational complex devoted to creativity. It houses a learning community, focused on art and design, extending from middle school through graduate school and beyond into the professional realm. It houses several departments for the College of Creative Studies, a library, dormitory, gymnasium, book store, cafe, and conference space. The building, formerly known as the Argonaut building, was designed by Albert Kahn for General Motors.
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-detroit/propose.md b/exampleSite/content/events/2017-detroit/propose.md
new file mode 100644
index 000000000..cb766ac3b
--- /dev/null
+++ b/exampleSite/content/events/2017-detroit/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-12-11T14:38:53-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-detroit/sponsor.md b/exampleSite/content/events/2017-detroit/sponsor.md
new file mode 100644
index 000000000..6dbd36269
--- /dev/null
+++ b/exampleSite/content/events/2017-detroit/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-12-11T14:38:53-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-detroit/welcome.md b/exampleSite/content/events/2017-detroit/welcome.md
new file mode 100644
index 000000000..389722e10
--- /dev/null
+++ b/exampleSite/content/events/2017-detroit/welcome.md
@@ -0,0 +1,90 @@
++++
+date = "2016-12-11T14:38:53-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-detroit"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**DevOpsDays is returning to Detroit!**
+
+
+ {{< event_logo >}}
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+{{< event_twitter devopsdaysdet >}}
diff --git a/exampleSite/content/events/2017-hartford/conduct.md b/exampleSite/content/events/2017-hartford/conduct.md
new file mode 100644
index 000000000..26cb4c587
--- /dev/null
+++ b/exampleSite/content/events/2017-hartford/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2017-01-09T10:01:31-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-hartford/contact.md b/exampleSite/content/events/2017-hartford/contact.md
new file mode 100644
index 000000000..d23fed884
--- /dev/null
+++ b/exampleSite/content/events/2017-hartford/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2017-01-09T10:01:31-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-hartford/location.md b/exampleSite/content/events/2017-hartford/location.md
new file mode 100644
index 000000000..22dfba367
--- /dev/null
+++ b/exampleSite/content/events/2017-hartford/location.md
@@ -0,0 +1,10 @@
++++
+date = "2017-01-09T10:01:31-05:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-hartford/program.md b/exampleSite/content/events/2017-hartford/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-hartford/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-hartford/propose.md b/exampleSite/content/events/2017-hartford/propose.md
new file mode 100644
index 000000000..72d708724
--- /dev/null
+++ b/exampleSite/content/events/2017-hartford/propose.md
@@ -0,0 +1,35 @@
++++
+date = "2017-01-09T10:01:31-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+
+There are three ways to propose a topic at devopsdays:
+
+
A 30-minute talk presented during the conference, usually in the mornings.
+
An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
+
Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table.
+
+
+
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
+- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen.
+- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process.
+- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
+
+
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Type (presentation, panel discussion, ignite)
+
Proposal Title (can be changed later)
+
Description (several sentences explaining what attendees will learn)
+
diff --git a/exampleSite/content/events/2017-hartford/sponsor.md b/exampleSite/content/events/2017-hartford/sponsor.md
new file mode 100644
index 000000000..9aa442df4
--- /dev/null
+++ b/exampleSite/content/events/2017-hartford/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2017-01-09T10:01:31-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-hartford/welcome.md b/exampleSite/content/events/2017-hartford/welcome.md
new file mode 100644
index 000000000..370482d75
--- /dev/null
+++ b/exampleSite/content/events/2017-hartford/welcome.md
@@ -0,0 +1,91 @@
++++
+date = "2017-01-09T10:01:31-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-hartford"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+{{< event_twitter devopsdayshfd >}}
diff --git a/exampleSite/content/events/2017-indianapolis/conduct.md b/exampleSite/content/events/2017-indianapolis/conduct.md
new file mode 100644
index 000000000..eb85e7ce1
--- /dev/null
+++ b/exampleSite/content/events/2017-indianapolis/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-12-16T15:40:27-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-indianapolis/contact.md b/exampleSite/content/events/2017-indianapolis/contact.md
new file mode 100644
index 000000000..9ed25d685
--- /dev/null
+++ b/exampleSite/content/events/2017-indianapolis/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-12-16T15:40:27-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-indianapolis/location.md b/exampleSite/content/events/2017-indianapolis/location.md
new file mode 100644
index 000000000..e84d5ee77
--- /dev/null
+++ b/exampleSite/content/events/2017-indianapolis/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-12-16T15:40:27-05:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-indianapolis/program.md b/exampleSite/content/events/2017-indianapolis/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-indianapolis/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-indianapolis/propose.md b/exampleSite/content/events/2017-indianapolis/propose.md
new file mode 100644
index 000000000..b559032d8
--- /dev/null
+++ b/exampleSite/content/events/2017-indianapolis/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-12-16T15:40:27-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-indianapolis/sponsor.md b/exampleSite/content/events/2017-indianapolis/sponsor.md
new file mode 100644
index 000000000..d1b634941
--- /dev/null
+++ b/exampleSite/content/events/2017-indianapolis/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-12-16T15:40:27-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-indianapolis/welcome.md b/exampleSite/content/events/2017-indianapolis/welcome.md
new file mode 100644
index 000000000..4cb8a6a7d
--- /dev/null
+++ b/exampleSite/content/events/2017-indianapolis/welcome.md
@@ -0,0 +1,93 @@
++++
+date = "2016-12-16T15:40:27-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-indianapolis"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-london/conduct.md b/exampleSite/content/events/2017-london/conduct.md
new file mode 100644
index 000000000..ce2e46b6b
--- /dev/null
+++ b/exampleSite/content/events/2017-london/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-london/contact.md b/exampleSite/content/events/2017-london/contact.md
new file mode 100644
index 000000000..eeb9de263
--- /dev/null
+++ b/exampleSite/content/events/2017-london/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-london/location.md b/exampleSite/content/events/2017-london/location.md
new file mode 100644
index 000000000..78edc642c
--- /dev/null
+++ b/exampleSite/content/events/2017-london/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-london/logo.png b/exampleSite/content/events/2017-london/logo.png
new file mode 100644
index 000000000..f69440cc2
Binary files /dev/null and b/exampleSite/content/events/2017-london/logo.png differ
diff --git a/exampleSite/content/events/2017-london/program.md b/exampleSite/content/events/2017-london/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-london/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-london/propose.md b/exampleSite/content/events/2017-london/propose.md
new file mode 100644
index 000000000..7745c0011
--- /dev/null
+++ b/exampleSite/content/events/2017-london/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-london/sponsor.md b/exampleSite/content/events/2017-london/sponsor.md
new file mode 100644
index 000000000..be527062c
--- /dev/null
+++ b/exampleSite/content/events/2017-london/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-12-17T13:55:35-05:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-london/welcome.md b/exampleSite/content/events/2017-london/welcome.md
new file mode 100644
index 000000000..0ee3c8ec0
--- /dev/null
+++ b/exampleSite/content/events/2017-london/welcome.md
@@ -0,0 +1,93 @@
++++
+date = "2016-12-21T13:55:35-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-london"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-minneapolis/conduct.md b/exampleSite/content/events/2017-minneapolis/conduct.md
new file mode 100644
index 000000000..095ebf90c
--- /dev/null
+++ b/exampleSite/content/events/2017-minneapolis/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-08-24T11:29:13-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-minneapolis/contact.md b/exampleSite/content/events/2017-minneapolis/contact.md
new file mode 100644
index 000000000..fa60461d7
--- /dev/null
+++ b/exampleSite/content/events/2017-minneapolis/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-08-24T11:29:13-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-minneapolis/location.md b/exampleSite/content/events/2017-minneapolis/location.md
new file mode 100644
index 000000000..cc6b07a70
--- /dev/null
+++ b/exampleSite/content/events/2017-minneapolis/location.md
@@ -0,0 +1,14 @@
++++
+date = "2016-12-16T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+The conference will take place Tuesday July 25 and Wednesday July 26, 2017 at the downtown Minneapolis Hilton.
+
+In past years, we worked with the hotel to make space available for nursing mothers, and if that would be useful for you, please let us know. We'd also be happy to accommodate any other accessibility needs. You can reach out on devops MSP Slack or via email.
+
+The recommended way to travel between the airport and downtown Minneapolis is via the light rail train to Nicollet Mall station. You can walk (under a mile), transfer to a free bus on Hennepin Ave, walk on the pedestrian Nicollet Mall in downtown, or take a short cab ride from the LRT. Uber & Lyft are also available.
+
+
+If you spend most of your time in places like Portland or Brooklyn, our metro will feel familiar, with its bike share stations, beautiful riverfront, and numerous craft brewery tap-rooms with food trucks in their parking lots.
diff --git a/exampleSite/content/events/2017-minneapolis/propose.md b/exampleSite/content/events/2017-minneapolis/propose.md
new file mode 100644
index 000000000..940c6fdfd
--- /dev/null
+++ b/exampleSite/content/events/2017-minneapolis/propose.md
@@ -0,0 +1,30 @@
++++
+date = "2016-12-16T21:17:00-06:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+
+There are three ways to propose a topic at devopsdays Minneapolis:
+
+
A 30-minute talk presented during the conference, in the mornings. We're currently accepting proposals for 30-minute talks via the form below.
+
An Ignite talk presented during the Ignite sessions (scheduling varies; in 2016 we had Ignites at our evening event). These are 5 minutes slots with slides changing every 15 seconds (20 slides total). We will open the call for Ignite talks closer to the time of the conference.
+
Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table.
+
+
+
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
+- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen.
+- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process.
+- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
+
+
+
+
diff --git a/exampleSite/content/events/2017-minneapolis/registration.md b/exampleSite/content/events/2017-minneapolis/registration.md
new file mode 100644
index 000000000..a964c2aa8
--- /dev/null
+++ b/exampleSite/content/events/2017-minneapolis/registration.md
@@ -0,0 +1,8 @@
++++
+date = "2016-03-06T21:28:23-06:00"
+title = "registration"
+type = "event"
+
++++
+
+
diff --git a/exampleSite/content/events/2017-minneapolis/sponsor.md b/exampleSite/content/events/2017-minneapolis/sponsor.md
new file mode 100644
index 000000000..d1318348c
--- /dev/null
+++ b/exampleSite/content/events/2017-minneapolis/sponsor.md
@@ -0,0 +1,59 @@
++++
+date = "2016-12-17T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+Platinum, Gold, and Silver sponsorship packages are detailed in our prospectus. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+Additional à la carte sponsorships are available:
+
+
+
coffee ($1k) - 2 slots available - signage by the coffee displays with your logo throughout the day
+
breakfast ($2k) - 2 slots available - signage by the breakfast service with your logo in the morning before sessions
+
snacks ($1k) - 2 slots available - signage by the snack area with your logo during the afternoon when snacks are available
+
lunch ($2k) - 2 slots available - signage by the lunch service with your logo during lunch
+
evening happy hour ($4k) - 1 slot available - signage at the evening happy hour
+
lanyard - ($5k) - 1 slot available - your logo on the lanyards
+
+
+These may be purchased in addition to (or in lieu of) the sponsorships in the prospectus.
+
+
+
+Devopsdays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers.
+
+
+All sponsors get a full table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms.
+
+
+
+
+
+
+
packages
+
Silver $5,000
+
Gold $7,000
+
Platinum* $10,000
+
+
+
3 included tickets
+
3 additional tickets (6 in total)
+
Full Table
+
Logo on devopsdays Minneapolis website, main room signage, and email communication.
+
Logo on shared slide during breaks
+
Logo on dedicated slide during breaks
+
Logo on shared slide in recorded video pre-rolls
+
Logo on dedicated slide in recorded video pre-rolls
+
1 minute pitch to full audience (including streaming if applicable)
+
5 minute pitch to full audience on Day 1 (including streaming if applicable)
+
+
+* There are a limited number of Platinum sponsorships available.
+
+
+
+
diff --git a/exampleSite/content/events/2017-minneapolis/welcome.md b/exampleSite/content/events/2017-minneapolis/welcome.md
new file mode 100644
index 000000000..8a6d128c7
--- /dev/null
+++ b/exampleSite/content/events/2017-minneapolis/welcome.md
@@ -0,0 +1,85 @@
++++
+date = "2016-08-24T11:29:13-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-minneapolis"]
+
++++
+
+**devopsdays is returning to {{< event_location >}} for a fourth year!**
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+ Register
+
+
+ {{< event_link page="registration" text="Register to attend the conference!" >}}
+
+
+
+
+
+ Propose
+
+
+ {{< event_link page="propose" text="Propose a talk!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+{{< event_twitter devopsdaysmsp >}}
+
diff --git a/exampleSite/content/events/2017-moscow/conduct.md b/exampleSite/content/events/2017-moscow/conduct.md
new file mode 100644
index 000000000..379b74970
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-09-05T09:42:50+03:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-moscow/contact.md b/exampleSite/content/events/2017-moscow/contact.md
new file mode 100644
index 000000000..8755ded5f
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-09-05T09:42:50+03:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-moscow/location.md b/exampleSite/content/events/2017-moscow/location.md
new file mode 100644
index 000000000..22c715dde
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-09-05T09:42:50+03:00"
+title = "location"
+type = "event"
+
++++
+
+Technopolis "Moscow", congress-center (Volgogradsky prospect, 42\5)
+
+{{< event_map >}}
diff --git a/exampleSite/content/events/2017-moscow/program.md b/exampleSite/content/events/2017-moscow/program.md
new file mode 100644
index 000000000..fcef826b4
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/program.md
@@ -0,0 +1,250 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+ If you are new to the Open Space concept you may want to read some more details.
+ Right now we are focused on creating a great DevOps program & schedule. If you have some ideas how to help it happen, or you want to become a speaker, then send us a letter: {{< email_organizers >}}.
+
+Otherwise, check back later, and you will be surprised (in a good way :) ).
+
+
+ Если вы впервые сталкиваетесь с концепцией Open Space мероприятий, предлагаем вам прочитать немного вводной информации.
+ В данный момент расписание конференции находится в процессе создания. Будут добавляться новые лекции, докладчики и новые форматы выступлений. Если у вас есть идея, как нам помочь, или вы хотите прочитать доклад – напишите нам письмо на почту: {{< email_organizers >}}.
+
+Или просто загляните чуть попозже, и вы будете приятно удивлены нашей программе :)
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-moscow/program/alexleyn.md b/exampleSite/content/events/2017-moscow/program/alexleyn.md
new file mode 100644
index 000000000..2886a536d
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/program/alexleyn.md
@@ -0,0 +1,68 @@
++++
+date = "2016-12-16T14:40:46+03:00"
+linktitle = "alexleyn"
+title = "Alexander Leyn"
+type = "talk"
+
++++
+
+
+
+
Title:
+Deployment automatization
+
+
+
Description:
+
+
+• Why delivery code for 4 days is not cool.
+• Typical problems of delivery.
+• High priority tasks for integration continuos delivery.
+• Good test coverage. Quick rollback if we have errors. Full automatization. Deploy without maintenance. Feedback in real time.
+• Jenkins integration with JIRA Software.
+• Work with git.
+• Testing in cloud systems.
+• Consistent transitions to new version.
+• Full processes monitoring.
+• Notifications system.
+• Rollback system at this moment.
+Total - 25 minutes from push to deploy on the production.
+
+
+
+
+
+
Тема:
+Автоматизация деплоя
+
+
+
Описание:
+
+
+• Почему доставлять код за 4 дня уже не круто.
+• Типичные проблемы доставки.
+• Что важно для внедрения Continuous Delivery.
+• Хорошее покрытие тестами. Быстрый откат в случае ошибок. Полная автоматизация. Деплой без простоя. Моментальная обратная связь.
+• Интеграция Jenkins и JIRA.
+• Работа с git.
+• Запуск тестов в облаке.
+• Последовательный переход на новую версию.
+• Мониторинг всего и вся.
+• Система оповещений.
+• Откат релиза за доли секунды.
+Итог - 25 минут от пуша до выгрузки на бой в любое время дня и ночи.
+
+
+HeadHunter is a site, where job seekers find vacancies and employers find employees.
+In the daytime we receive 3K requests per second (without static content), that turn into 25K RPS to backends and 50K RPS to databases.
+Earlier our uptime could be lower than 99%. Now - it is 99.9% and better.
+
+In the presentation I will describe how do we constantly making the reliability of the site better and better.
+Particulary:
+- allocation of responsibility between operations, SRE and other teams;
+- how do we measure uptime / downtime;
+- what do we do when the site is down;
+- what tools do we use to quickly find the cause of the downtime;
+- how do we stress test production to find bottlenecks.
+
+In order not to be too abstract and boring, I'll explain some particular cases:
+- how do we scale database replicas;
+- why did we remove PgBouncer (this is a connection pool in front of PostgreSQL);
+- why Graylog did not fit for us and how do we search through logs in a much more simple way;
+- what problems are there with retries;
+- etc.
+
+
+
+
+
+
Тема:
+Как команда SRE делает HeadHunter стабильным
+
+
+
Описание:
+
+
+HeadHunter - сайт, где соискатели находят работу, а работодатели - сотрудников.
+Днем к нам приходит 3K запросов в секунду (без статики), что превращается в 25K rps к бэкендам и 50K rps к базам данных.
+Раньше стабильность сайта могла быть ниже 99%. Теперь - это 99.9% и лучше.
+
+В докладе расскажу о том, как мы постоянно улучшаем стабильность сайта.
+В частности:
+- как распределяем ответственность между эксплуатацией, командой SRE и другими командами;
+- как мы определяем, когда сайт работает, а когда - нет;
+- что делаем, когда сайт лежит;
+- какие инструменты используем, чтобы быстро находить причину проблемы;
+- как нагружаем продакшн, чтобы заранее выявить узкое место.
+
+Чтобы не было абстрактно и скучно, расскажу о конкретных кейсах:
+- как мы масштабировали реплики базы данных;
+- почему отказались от PgBouncer (это такой пул соединений перед PostgreSQL);
+- почему нам не подошел Graylog, и как мы ищем в логах другим гораздо более простым способом;
+- какие проблемы есть с ретраями;
+- и др.
+
+
+Если верить Джин Киму - автору девопс-бестселлера "Проект Феникс" - усиление потока (flow) есть первый благородный путь методологии девопс. Концепт потока не так сложен для понимания - это количество конструктивных изменений, количество произведенной ценности движущейся сквозь трубопровод нашей компании. От творческой идеи в наших головах до её реализации в виде услуги или продукта доставленного клиенту. Да доставленного так, чтоб клиент остался не просто доволен, а восхищен нашей способностью делать вещи быстро и качественно. Задача ясна, цель обозначена. Но дорога к улучшению ухабиста и извилиста. Никто не прыгает зараз от одного релиза в месяц к 10 релизам в день. Постоянное улучшение достигается ежедневными экспериментами, анализом результатов и действиями основанными на конкретных измерениях. Так как-же измерить поток? На что смотреть? Где взять данные?
+В этом докладе я представлю систему из 12-ти индикаторов измерения потока которую мы выстроили для работы с большими технологическими компаниями и расскажу о возможных методологиях их сбора, внедрения и обработки для постоянного улучшения в истинном духе девопс.
+
+
Title:
+When program developing goes well or the best practices of secure code development.
+
+
+
Description:
+
+
+Stress-mode code development is a normal in modern software industry. The ever conflicting demand of quality, price and speed commands even successful IT-companies. There were a lot of words said about effective testing, deployment and what reaction should be on the different incidents but the quality-price-speed triangle is still alive and dominates the development.
+We will present our practical experience in secure software code development in Solar. We organized our software development based on the best world practices. We adopted them to our specifics blended together SDLC practice and security testing. We will present our support and first and second lines help desk services. Also our various motivation and stimulation aspects will be discussed.
+
+
+
+
+
Тема:
+Когда разработка идет как надо или практика построения процесса разработки защищенного программного кода.
+
+
+
Описание:
+
+
+Сегодня разработка программного обеспечения обычно происходит в стрессовом режиме. Вечный конфликт между качеством, скоростью и стоимостью разработки командует даже в самых успешных IT-компаниях. Сказано много слов о том, как надо проводить различное тестирование, организовывать выдачу программного кода в промышленную эксплуатацию, как реагировать на инциденты, однако треугольник качество-скорость-стоимость продолжает жить и угнетать разработку программного кода.
+В нашем докладе мы попробуем рассмотреть практику успешного внедрения технологии разработки защищенного программного кода, основываясь на лучших международных практиках. Процесс разработки мы строили, взяв лучшее и наиболее подходящее именно для специфики разработки нашего ПО, соединив практику SDLC, тестирования по требованиям информационной безопасности, различных методик тестирования. Также мы покажем, как у нас организовано сопровождение разработки, первая и вторая линия поддержки, разделение времени разработчиков на сопровождение и разработку, а также различные мотивационные аспекты, стимулирующие работу разработчиков и отдела контроля качества.
+
+
+
Title:
+Building a PaaS with Docker, Consul and Python
+
+
+
Description:
+
+
+I'm currently single-handedly building a Database-As-A-Service platform. And the problem of where and how to run database instances has been successfully solved in favor of Docker. But there still remain 2 problems: how to link containers on different hosts across the network and how to orchestrate a large pool of running instances.
+
+You may find lots of different IaaS offerings and schedulers like Mesos and Kubernetes on the market, but all of them have a steep learning curve. Plus they don't handle stateful and non-SOA services very well.
+
+In this talk I'll be walking you over how one can build a simple PaaS based on Docker, consul and a custom orchestration service in Python. My experience in building such system shows that it can be reproduced by the effort of one developer.
+
+A list of topics I will cover:
+- Consul as a reliable distributed storage
+- Connecting containers between hosts without an overlay network
+- Allocating IP addresses and maintaining their pool in Consul KV
+- Correctly registering services and health checks
+- How to approach writing basic orchestrator based on gevent + writing trivial admin UI for it
+- Adding failover, scaling and service reallocation to the orchestrator
+- Delayed tasks (backup, analytics, etc...)
+- Monitoring the system (Consul + Prometheus)
+
+Almost all code of the system, including ansible playbooks, is available on GitHub.
+
+
+
+
+
Тема:
+Как сделать PaaS при помощи Docker, Consul и обвязки на Python
+
+
+
Описание:
+
+
+Сейчас я в одиночку работаю над созданием Database-As-A-Service решения. И вопрос "как и где запускать" успешно решился в пользу Docker. Проблемы возникли в двух местах: как соединять контейнеры по сети для репликации данных, и как автоматизированно управлять большим парком запущенных инстансов.
+
+На рынке есть много решений для организации IaaS, и всяких шедулеров вроде Mesos и Kubernetes. Но у всех у них довольно крутой learning curve. К тому же они не очень хорошо работают с сервисами, сдизайненными не по SOA.
+
+В своем докладе я расскажу, как можно сделать (и как я в итоге сделал) для своей компании небольшой PaaS на основе Docker, Consul и обвязки на Python в качестве оркестратора. Это вполне воспроизводимо силами одного человека.
+
+Вот о чем мы поговорим:
+- Consul как надежное распределенное хранилище
+- Делаем связь контейнеров между хостами без overlay сети
+- Выделение IP адресов и организация их пула в Consul KV
+- Как правильно регистрировать сервисы и health check-и
+- Делаем оркестратор на gevent + простую админку к нему на Flask
+- Делаем failover, масштабирование и переезд сервисов
+- Отложенные задания (бэкап, аналитика и т.д.)
+- И немного про мониторинг всего этого хозяйства (Consul + Prometheus)
+
+Почти весь, включая ansible скрипты, доступен на GitHub.
+
+
+Identifying and fixing issues in new code before deploying it to production is important for every software development cycle. However, relying on traditional testing methods in the age of Internet-scale data driven problems may prove to be incomplete. Identifying and fixing the issues in production quickly is crucial, but it requires insight into usage patterns and trends across the whole architecture and application logic. In this talk I touch on inefficiencies of some of the most common testing methods, provide real world examples of discovering odd edge cases with monitoring and offer recommendations on top-down metric instrumentation to help DevOps organizations with identifying and acting on business-effecting problems.
+
+
+
+
+
Тема:
+Тестирование и мониторинг в production
+
+
+
Описание:
+
+
+Выявление и устранению проблем в новом коде имеет важное значение для каждого цикла разработки программного обеспечения. Тем не менее, опираясь на традиционные методы тестирования в эпоху масштабных Интернет-проблем может оказаться недостаточным. В этом докладе я покрою темы неэффективности некоторых из наиболее распространенных методов тестирования и дам реальные примеры обнаружения проблем в production, с рекомендациями по стратегии имплементации мониторинга, чтобы помочь организациям быстро обнаружить и устранить критичные проблемы.
+
+
+There are plenty of materials on getting development and operations to work together. More conversations are happening around inclusion of other technology groups, such as DBAs and QA testers, into DevOps processes. That said, DevOps conversations has been largely devoid of talk about BizOps place at the table. The goal for any tech-centric group is not to build and/or architect the best technology, but rather to effectively support business. Yet, many of those groups are either not privy to or don't bother understanding the business goals and overarching effects of the technical decisions made. In this talk I'll discuss key areas and feedback points in every DevOps process fit for inclusion of business units in order to align technology and business goals and make your life easier.
+
+
+
+
+
Тема:
+BizOps и ты
+
+
+
Описание:
+
+
+Есть достаточно материалов о присоединении разных технологических групп в DevOps, таких групп как администраторов баз данных и QA тестеров. Тем не менее, DevOps темы в основном лишены разговоров о том как включить НЕ-технологические группы. Обычно люди забывают что цель любой тех-группы это не программирование кода или постройка новейших систем, а эффективная поддержки бизнеса. Тем не менее, многие из этих групп либо не принимают участия в обсуждении бизнеса либо не пытаются понять целей бизнеса и, как результат, последствия технических решений. В этом докладе я планирую обсудить ключевые точки в каждом процессе DevOps организации пригодный для включения бизнес групп с целью согласования технологических и бизнес целей.
+
+
Title:
+From Zero to Hero: Firing up a holistic Continuous Delivery pipeline, with DevOps tools
+
+
+
Description:
+
+
+In this interactive session we’ll quickly code and package a web application. Its development versions will be inspected with SonarQube, shipped with Docker, and deployed to Artifactory. Jenkins 2 with its native delivery pipeline features serves as a backbone of our delivery ecosystem. Final releases are published to Bintray, the distribution management platform. Operations (e.g. uploads) on the final releases are gathered by JFrog Firehose Events API. Monitoring with the ELK stack does polish the overall DevOps tool chain. After the interactive session, you know nuts and bolts of setting up a scalable, high-end Delivery Pipeline, using DevOps tools, and Cloud, microservices, and container technologies.
+
+You think you're a DevOps engineer? I have some bad news for you - you actually don't exist. This is where you would say, "But the recruiter told me..." Really? Maybe you know PHP, C++, Python, Java, C#, XSLT? Perhaps even Excel? Wake up, Neo! I offer your the pill. Yes. Just one. There is no choice. There is no “DevOps Engineer”. However, you have a chance. A chance to find yourself. To understand yourself and your role. To know who you are. In the world of DevOps.
+
+
+
+
+
Тема:
+Как перестать быть DevOps инженером
+
+
+
Описание:
+
+
+Понятие и рынок DevOps. Как правильно себя позиционировать и при этом не выглядеть глупо. Как объяснить другим Вашу роль и чем Вы так полезны команде, как представитель DevOps культуры.
+
+
Title:
+Problems I faced while building just another Docker PaaS
+
+
+
Description:
+
+
+Docker made Linux Containers (LXC) technology available to everyone. However, using Docker for production deployment still involves traditional devops tasks like logs, monitoring, backups setup, periodic OS updates, ensuring availability and security. These tasks feel a bit different if we try to turn our own solution into a Docker PaaS. I'll tell the story of dockhero.io to demonstrate the difference between using Docker in production "for myself" and building Docker PaaS "for others".
+
+
+
+
+
Тема:
+Проблемы, с которыми я столкнулся при создании очередной Docker PaaS
+
+
+
Описание:
+
+
+Благодаря Docker'у, технология Linux-контейнеров стала доступна всем и каждому. Однако, чтобы развернуть production-систему на Docker'е, нужно решить ряд инфраструктурных задач: логи, мониторинг, бэкапы, отказоустойчивость, апдейты, безопасность. Эти задачи выглядят несколько по-иному, когда мы пытаемся превратить свое решение в Docker PaaS. В своем докладе на примере dockhero.io я покажу разницу между использованием Docker'а в продакшне "для себя" и создании Docker PaaS "для других".
+
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-moscow/propose.md b/exampleSite/content/events/2017-moscow/propose.md
new file mode 100644
index 000000000..256b3c67b
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/propose.md
@@ -0,0 +1,74 @@
++++
+date = "2016-09-05T09:42:50+03:00"
+title = "propose"
+type = "event"
++++
+
+
+We are calling for enthusiastic speakers and great lectures! If you want to take part in our event and become a speaker, please fill the “Talk proposal” form at the bottom of the page, OR drop us an e-mail at {{< email_organizers >}}.
+
+Мы ищем классных спикеров и зажигательные доклады! Если вы хотите принять участие в конференции и прочитать доклад, заполните форму “Предложить доклад” внизу страницы, или же напишите нам на почту: {{< email_organizers >}}.
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: fill out the “Talk proposal” form at the bottom of the page and we will get in touch with you shortly. If you have additional questions, send an email to {{< email_organizers >}}
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
+
+
+
+Вы можете предложить несколько типов докладов:
+
+
Доклад для основного трека: у вас будет 30 минут и концентрированное внимание всей аудитории.
+
Доклад в стиле Ignite: особый доклад на 5 минут. Такие доклады идут один за другим в течении 30-40 минут. Цель – максимально сжато и лаконично объяснить то, что вы хотите донести до аудитории.
+
Доклад на Open Space – сессии: даже если у вас нет готовой презентации, мы готовы предложить вам слот в Open space сессии: это время, когда участники могут общаться между собой, делать собственные мини-питчи и доклады, а также обсуждать последние новости DevOps. Для более детальной информации по данному формату, смотрите ссылку
+
+
+
+
+Критерии хорошего доклада DevOpsDays:
+
+- **_Оригинальный контент_**: если контент еще не был представлен на других конференциях, или это новый взгляд на старые вещи – то это хороший контент;
+- **_Новые лица_**: мы уверены, что у каждого человека есть сказать что-то интересное. Не стесняйтесь, даже если вы выступаете в первый раз – мы это оценим и поддержим;
+- **_Никаких рекламных докладов продуктов спонсоров_**: мы очень ценим наших спонсоров мероприятия, но концепция мероприятия не допускает рекламных докладов и обзоров различных (пусть даже отличных) продуктов. Однако если вы спонсор – не отчаивайтесь, у вас будет время во время Open space – сессии, что бы рассказать о себе.
+
+Как стать докладчиком: заполните форму “Предложить доклад” внизу страницы, и мы свяжемся с вами. Если у вас есть дополнительные вопросы, отправьте нам письмо на почту {{< email_organizers >}}
+
+
Придумайте тему доклада;
+
Выберите тип доклада (см выше);
+
Сделайте короткое описание сути доклада;
+
Присылайте это все на нашу почту: (почта) и мы обязательно вам ответим!
+
+Правила:
+
+
Будьте конкретны – мы не умеем читать между строк (пока). Постарайтесь дать как можно больше деталей вашего доклада.
+
Детали – это хорошо. Но не настолько хорошо, насколько описание того, почему ваш доклад окажется интересным для остальных.
+
Предлагайте ваш собственный доклад – не позволяйте никому делать это за вас.
+
Приведи друга. Если вы думаете, что кто-то может сделать отличный доклад – покажите на него, и мы попробуем с ним связаться.
+
Больше – лучше. Если у вас несколько докладов – мы не против, пока вы следуете остальным правилам.
+
+
+The official registration will be available soon. Meanwhile, you can fill the “Pre-registration” form at the bottom of the page, and we will send you a link to the official registration directly! Also, if you send us a pre-registration, you will get a special discount for your ticket.
+
+
+Друзья, совсем скоро будет доступна официальная регистрация на мероприятие. Что бы ее открыть, нам нужно окончательно зафиксировать даты и наполнить сетку мероприятия интересным докладами и спикерами.
+
+Однако уже сейчас вы можете ознакомиться с ценовой политикой мероприятия. Обратите внимание, что для тех, кто сейчас будет готов потратить несколько секунд и отправить предварительную регистрацию, будет доступна большая скидка.
+
+Наша конференция некоммерческая, по этому цены на билеты мы держим максимально низкими. Благодаря поддержки спонсоров и самых активных участников комьюнити DevOps билеты остаются доступным абсолютно для всех желающих посетить конференцию.
+
+Форму предварительной регистрации вы можете найти внизу страницы.
+
+
+
+
+
+ Time (Время)
+
+
+ Предварительная регистрация До конца Декабря
+
+
+
+ Ранняя регистрация До конца Января
+
+
+
+ Полный билет Февраль
+
+
+
+
+
+ Базовый билет:
+
+
Базовый пакет участника
+
Все доклады + мастер-классы
+
Кофе, печенье + обед
+
+
+
+ 5000 3500
+
+
+
+ 5000 4000
+
+
+ 5000
+
+
+
+
+ VIP билет
+
+
Расширенный пакет участника
+
Подарки от спонсоров мероприятия
+
Все доклады + мастер-классы
+
Кофе, печенье + обед
+
Ужин с докладчиками и спонсорами после мероприятия
+
+
+
+ 16000 12000
+
+
+
+ 16000 14000
+
+
+ 16000
+
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-moscow/speakers.md b/exampleSite/content/events/2017-moscow/speakers.md
new file mode 100644
index 000000000..9ed1f05ed
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/speakers.md
@@ -0,0 +1,6 @@
++++
+date = "2016-12-16T14:40:24+03:00"
+title = "speakers"
+type = "speakers"
+
++++
diff --git a/exampleSite/content/events/2017-moscow/sponsor.md b/exampleSite/content/events/2017-moscow/sponsor.md
new file mode 100644
index 000000000..fc8641b45
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/sponsor.md
@@ -0,0 +1,44 @@
++++
+date = "2016-09-05T09:42:50+03:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}} or click here to download our special sponsor presentation to see the options.
+
+
+Мы очень ценим и рассчитываем на спонсоров данного мероприятия. Если вы заинтересованы в спонсировании мероприятия, отправьте нам письмо на почту: {{< email_organizers >}}, или нажмите сюда что бы посмотреть спонсорскую презентацию и узнать про доступные опции.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-moscow/welcome.md b/exampleSite/content/events/2017-moscow/welcome.md
new file mode 100644
index 000000000..909e30dd0
--- /dev/null
+++ b/exampleSite/content/events/2017-moscow/welcome.md
@@ -0,0 +1,103 @@
++++
+date = "2016-09-05T09:42:50+03:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-moscow"]
+
++++
+
+
{{< event_start >}}
+
+
+**DevOpsDays is coming to {{< event_location >}}!**
+**Конференция DevOpsDays приходит в {{< event_link page="location" text="Москву!" >}}**
+
+
+ {{< event_logo >}}
+
+
+
+
+ Dates (Дата проведения):
+
+
+ {{< event_start >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Speakers (Спикеры):
+
+
+ Want to become a speaker? Tell us! Хотите стать спикером? Напишите нам! {{< email_organizers >}}
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+ {{< event_link page="contact" text="Свяжитесь с организаторами!" >}}
+
+
+
+
+
+ Registration (Регистрация)
+
+
+ {{< event_link page="registration" text="Fill a pre-registration form and get tickets at a special price!" >}}
+
+ {{< event_link page="registration" text="Заполните форму предварительной регистрации и получите билеты по специальной цене!" >}}
+
+
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+
CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-ohio/contact.md b/exampleSite/content/events/2017-ohio/contact.md
new file mode 100644
index 000000000..196ccd4d7
--- /dev/null
+++ b/exampleSite/content/events/2017-ohio/contact.md
@@ -0,0 +1,33 @@
++++
+City = "Ohio"
+Year = "2017"
+date = "2017-03-06T21:16:08-06:00"
+title = "contact"
+type = "event"
+draft = false
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+Our local team
+
+Active
+
+{{< list_organizers >}}
+
+Historic
+
+
+
Dan Sajner
+
Faye Thompson
+
Matt Stratton
+
+
+
+The core devopsdays organizer group
+
+{{< list_core >}}
+
+
diff --git a/exampleSite/content/events/2017-ohio/logo.png b/exampleSite/content/events/2017-ohio/logo.png
new file mode 100644
index 000000000..64a3ab3a0
Binary files /dev/null and b/exampleSite/content/events/2017-ohio/logo.png differ
diff --git a/exampleSite/content/events/2017-ohio/sponsor.md b/exampleSite/content/events/2017-ohio/sponsor.md
new file mode 100644
index 000000000..3e5168b15
--- /dev/null
+++ b/exampleSite/content/events/2017-ohio/sponsor.md
@@ -0,0 +1,22 @@
++++
+City = "Ohio"
+Year = "2017"
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+draft = false
+
+
++++
+
+We greatly value sponsors for this open event.
+
+
+Sponsorship Prospectus.
+
+
+If you are interested in sponsoring this event in any way, please email us: {{< email_organizers >}}.
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distributee attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
diff --git a/exampleSite/content/events/2017-ohio/welcome.md b/exampleSite/content/events/2017-ohio/welcome.md
new file mode 100644
index 000000000..fdb46bccc
--- /dev/null
+++ b/exampleSite/content/events/2017-ohio/welcome.md
@@ -0,0 +1,98 @@
++++
+date = "2017-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+City = "ohio"
+Year = "2017"
+aliases = ["/events/2016-Ohio"]
+draft = false
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+ {{< event_logo >}}
+
+
+DevOps Days will be coming back to Columbus, Ohio in 2017!
+
+More information on the event will be coming soon.
+In the mean time, check out the 2016 Program and
+Videos.
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the event!" >}} It's a great way to attract new talent and promote your organization.
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the Organizers" >}}
+
+
+
+{{< event_twitter DevOpsDaysOhio >}}
+
+Tweets by DevOpsDaysOhio
diff --git a/exampleSite/content/events/2017-paris/conduct.md b/exampleSite/content/events/2017-paris/conduct.md
new file mode 100644
index 000000000..bc6e1253e
--- /dev/null
+++ b/exampleSite/content/events/2017-paris/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-10-11T18:48:25+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-paris/contact.md b/exampleSite/content/events/2017-paris/contact.md
new file mode 100644
index 000000000..a3f098da7
--- /dev/null
+++ b/exampleSite/content/events/2017-paris/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-10-11T18:48:25+02:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-paris/location.md b/exampleSite/content/events/2017-paris/location.md
new file mode 100644
index 000000000..f3dd2eb46
--- /dev/null
+++ b/exampleSite/content/events/2017-paris/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-10-11T18:48:25+02:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-paris/program.md b/exampleSite/content/events/2017-paris/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-paris/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-paris/propose.md b/exampleSite/content/events/2017-paris/propose.md
new file mode 100644
index 000000000..46bb11eb5
--- /dev/null
+++ b/exampleSite/content/events/2017-paris/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-10-11T18:48:25+02:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-paris/sponsor.md b/exampleSite/content/events/2017-paris/sponsor.md
new file mode 100644
index 000000000..d2ce0cbdc
--- /dev/null
+++ b/exampleSite/content/events/2017-paris/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-10-11T18:48:25+02:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-paris/welcome.md b/exampleSite/content/events/2017-paris/welcome.md
new file mode 100644
index 000000000..18acb61d4
--- /dev/null
+++ b/exampleSite/content/events/2017-paris/welcome.md
@@ -0,0 +1,89 @@
++++
+date = "2016-10-11T18:48:25+02:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-paris"]
+
++++
+
+
+
+
devopsdays is coming to {{< event_location >}} in Spring 2017!
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+{{< event_twitter devopsdaysparis >}}
diff --git a/exampleSite/content/events/2017-portland/conduct.md b/exampleSite/content/events/2017-portland/conduct.md
new file mode 100644
index 000000000..745518a84
--- /dev/null
+++ b/exampleSite/content/events/2017-portland/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-08-28T14:00:07-07:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-portland/contact.md b/exampleSite/content/events/2017-portland/contact.md
new file mode 100644
index 000000000..629d94452
--- /dev/null
+++ b/exampleSite/content/events/2017-portland/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-08-28T14:00:07-07:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-portland/location.md b/exampleSite/content/events/2017-portland/location.md
new file mode 100644
index 000000000..e3ad1cd14
--- /dev/null
+++ b/exampleSite/content/events/2017-portland/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-08-28T14:00:07-07:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-portland/program.md b/exampleSite/content/events/2017-portland/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-portland/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-portland/propose.md b/exampleSite/content/events/2017-portland/propose.md
new file mode 100644
index 000000000..01ac0c3ad
--- /dev/null
+++ b/exampleSite/content/events/2017-portland/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-08-28T14:00:07-07:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-portland/sponsor.md b/exampleSite/content/events/2017-portland/sponsor.md
new file mode 100644
index 000000000..97e6a8e9a
--- /dev/null
+++ b/exampleSite/content/events/2017-portland/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-08-28T14:00:07-07:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-portland/welcome.md b/exampleSite/content/events/2017-portland/welcome.md
new file mode 100644
index 000000000..bfdc2ff65
--- /dev/null
+++ b/exampleSite/content/events/2017-portland/welcome.md
@@ -0,0 +1,95 @@
++++
+date = "2016-08-28T14:00:07-07:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-portland"]
+
++++
+
+
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+ {{< event_logo >}}
+
+
+We're still working out all the details. If you'd like to help out, email us!
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-saint-louis/conduct.md b/exampleSite/content/events/2017-saint-louis/conduct.md
new file mode 100644
index 000000000..6a9c61d9c
--- /dev/null
+++ b/exampleSite/content/events/2017-saint-louis/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-12-14T09:04:16-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-saint-louis/contact.md b/exampleSite/content/events/2017-saint-louis/contact.md
new file mode 100644
index 000000000..441b67f90
--- /dev/null
+++ b/exampleSite/content/events/2017-saint-louis/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-12-14T09:04:52-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-saint-louis/location.md b/exampleSite/content/events/2017-saint-louis/location.md
new file mode 100644
index 000000000..b7e22da8d
--- /dev/null
+++ b/exampleSite/content/events/2017-saint-louis/location.md
@@ -0,0 +1,17 @@
++++
+City = "Saint Louis"
+Year = "2017"
+date = "2016-12-14T09:05:46-06:00"
+title = "location"
+type = "event"
+
++++
+
+## Conference Location
+
+
TBA
+
Saint Louis Missouri USA
+
+
+
+
diff --git a/exampleSite/content/events/2017-saint-louis/sponsor.md b/exampleSite/content/events/2017-saint-louis/sponsor.md
new file mode 100644
index 000000000..b4a079e6e
--- /dev/null
+++ b/exampleSite/content/events/2017-saint-louis/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-12-14T10:10:42-06:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-saint-louis/welcome.md b/exampleSite/content/events/2017-saint-louis/welcome.md
new file mode 100644
index 000000000..937679b54
--- /dev/null
+++ b/exampleSite/content/events/2017-saint-louis/welcome.md
@@ -0,0 +1,54 @@
++++
+date = "2016-12-14T09:07:19-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-saint-louis"]
+
++++
+
+
+
+
+
+
+
+
DevOpsDays Saint Louis 2017
+
+
+
+
+
+
DevOpsDays is coming to Saint Louis in 2017!
+
This will mark the first year the event will be held in Saint Louis. It'll be a great
+ opportunity to share knowledge and stories, socialize and promote our great technical
+ community.
+
More details to come soon!
+
+
+
diff --git a/exampleSite/content/events/2017-salt-lake-city/conduct.md b/exampleSite/content/events/2017-salt-lake-city/conduct.md
new file mode 100644
index 000000000..0a37a45ec
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-10-18T19:59:04-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-salt-lake-city/contact.md b/exampleSite/content/events/2017-salt-lake-city/contact.md
new file mode 100644
index 000000000..da3faef7e
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-10-18T19:59:04-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-salt-lake-city/location.md b/exampleSite/content/events/2017-salt-lake-city/location.md
new file mode 100644
index 000000000..7f82e8729
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/location.md
@@ -0,0 +1,15 @@
++++
+date = "2016-10-18T19:59:04-06:00"
+title = "location"
+type = "event"
+
++++
+
+We have an exciting new venue for our 2017 conference, [Noah's Event Venue](http://www.noahseventvenue.com)
+
+Did you get a chance to attend our inaugural 2016 DevOps Days Event held here in beautiful Salt Lake City? If not, we understand, you maxed the location capacity of 250 attendees, which meant a LOT of you were left out (75 + waitlisted, a bunch of “please just let me in,” and only 5 no shows).
+
+We heard your request for this year’s capacity-bigger. Good thing because, in our sophomore year, Salt Lake DevOps Days 2017 is set to have over 400+ attendees. Yup, 400+.
+
+
+
diff --git a/exampleSite/content/events/2017-salt-lake-city/program.md b/exampleSite/content/events/2017-salt-lake-city/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-salt-lake-city/propose.md b/exampleSite/content/events/2017-salt-lake-city/propose.md
new file mode 100644
index 000000000..3ad531bc0
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/propose.md
@@ -0,0 +1,24 @@
++++
+date = "2016-10-18T19:59:04-06:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Instructions for submitting your proposal will be made available once the call for proposals is open. In the meantime, get those proposals ready!
diff --git a/exampleSite/content/events/2017-salt-lake-city/registration.md b/exampleSite/content/events/2017-salt-lake-city/registration.md
new file mode 100644
index 000000000..7bafa4b41
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/registration.md
@@ -0,0 +1,13 @@
++++
+date = "2016-10-18T19:59:04-06:00"
+title = "registration"
+type = "event"
+
+
++++
+
+
+
+Embed registration iframe/link/etc.
+
+
diff --git a/exampleSite/content/events/2017-salt-lake-city/sponsor.md b/exampleSite/content/events/2017-salt-lake-city/sponsor.md
new file mode 100644
index 000000000..fbc7eef5e
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-10-18T19:59:04-06:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-salt-lake-city/welcome.md b/exampleSite/content/events/2017-salt-lake-city/welcome.md
new file mode 100644
index 000000000..a0052ceef
--- /dev/null
+++ b/exampleSite/content/events/2017-salt-lake-city/welcome.md
@@ -0,0 +1,103 @@
++++
+date = "2016-10-18T19:59:04-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-salt-lake-city"]
+
++++
+
+
+
DevOpsDays is returning to Salt Lake City in May!
+
+
+**This year with a bigger, better location! {{< event_location >}}!**
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+ Theme
+
+
+Humans and Tooling: Building reliability into your DevOps Organization
+The beauty of a Continuous Delivery pipeline and all of its components is knowing your monitoring and feedback loops are consistent. Implementing a good setup and proper maintenance you can consider them reliable, but machines are the easy part. Tools are always easy, humans are complex and it is the human which works with other teams, to collaborate, gather and validate the requirements for the pipeline. To create a welcoming culture and successful CD pipeline, a new team formation is essential. Thus DevOps was born to bring together groups previously pitted against each other via conflicting bonus plans, timelines, and business drivers. SLC DOD 2017 is all about this: you can’t create reliable feedback tools without recovering the human trust. How do we tool up and trust rapidly to prove we can rely on both.
+
+
+
+
+
+**devopsdays está vindo para {{< event_location >}}!**
+
+
+
+
+
+ Datas
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Patrocinadores
+
+
+ {{< event_link page="sponsor" text="Patrocine este Evento!" >}}
+
+
+
+
+
+ Contato
+
+
+ {{< event_link page="contact" text="Entre em contato com os organizadores" >}}
+
+
+
+
+
+{{< event_twitter devopsdayssp >}}
diff --git a/exampleSite/content/events/2017-sao-paulo/chamada.md b/exampleSite/content/events/2017-sao-paulo/chamada.md
new file mode 100644
index 000000000..8e88bf925
--- /dev/null
+++ b/exampleSite/content/events/2017-sao-paulo/chamada.md
@@ -0,0 +1,29 @@
++++
+date = "2016-12-08T16:35:49-05:00"
+title = "chamada"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+Existem três formas para propor sua sessão:
+
+
Proposta para palestra/painel : 30 minutos com a atenção de todos os presentes.
+
Palestra relâmpago que serão apresentadas durante a sessão relâmpago. São intervalos de 5 minutos com slides trocando a cada 15 segundos (20 slides no total) que serão apresentados para todos os presentes.
+
Sessões de espaço aberto : Mesmo que você não tenha preparado uma apresentação, você é bem vindo para discutir e interagir propondo uma sessão ao vivo nos espaços abertos. Veja a explicação de espaços abertos para maiores informações.
+
+
+Nosso critério para escolha de propostas são:
+
+- _conteúdo original_: Conteúdo ainda não apresentado em outras conferências, ou um novo ângulo de um problema existente
+- _novos palestrantes_: Pessoas novas e que tem coisas interessante a dizer; Nós precisamos ouvir todos
+- _sem vendas_: Nós valorizamos fornecedores e patrocinadores, nos apenas não achamos que é o melhor local para isso. Você pode demonstrar em sua mesa.
+
+Regras:
+
+
Seja específico... nós não somos leitores de mente ( uma descrição com ao menos 20 linhas é algo desejável)
+
Detalhes são bons... explique porque sua palestra é interessante
+
Proponha sua própria palestra
+
Indicações são bem vindas... Se você conhece alguém com conteúdo/relevância em DevOps, por favor nos indique através do email {{< email_organizers >}}
+
Múltiplas propostas são bem vindas... apenas sigas todas as outras regras
+
diff --git a/exampleSite/content/events/2017-sao-paulo/conduta.md b/exampleSite/content/events/2017-sao-paulo/conduta.md
new file mode 100644
index 000000000..ef884d5d3
--- /dev/null
+++ b/exampleSite/content/events/2017-sao-paulo/conduta.md
@@ -0,0 +1,37 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "conduta"
+type = "event"
+
++++
+
+## Código de conduta
+
+O DevOpsDays é um evento sem fins lucrativos cujo principal objetivo é promover a troca de experiências entre as pessoas sobre a cultura DevOps no Brasil.
+
+Este Código de Conduta será aplicado para todos enquanto participantes desse evento para proteger o público de danos e perigos morais.
+
+Nos dedicamos a promover um evento respeitoso e livre de assédio para todos. Não toleramos quaisquer formas de assédios ou intimidações de qualquer participante.
+
+Imagens, atividades ou materiais de conteúdo sexual, homofóbico, pejorativo e/ou discriminatório de qualquer natureza não são aceitos.
+
+Por assédio entende-se sem limitação:
+
+
Comentários ofensivos, verbais ou eletrônicos, relacionados a características pessoais, origem racial, orientação sexual, identidade de gênero, bem como comentários ou imagens sexuais, racistas, homofóbicas ou discriminatórias de qualquer natureza em espaços públicos ou digitais;
+
Intimidação deliberada;
+
Bullying;
+
Perseguição;
+
Encalço;
+
Fotografias ou gravações que gerem embaraço;
+
Interrupções reiteradas de palestras, bate-papos, reuniões eletrônicas, reuniões físicas ou outros eventos;
+
Contato físico inadequado ou atenção sexual indesejada.
+
+Espera-se que os participantes cumpram imediatamente solicitações para descontinuar qualquer assédio ou comportamento de bullying. Sejam gentis com os outros. Não insultem ou ofendam outros participantes. Lembrem-se de que piadas de assédio, sexismo, racismo ou exclusão não são aceitas pela sociedade, muito menos para nosso evento.
+
+Qualquer participante que violar tais regras pode ser convidado a se retirar, a critério exclusivo dos organizadores do evento.
+
+Se um participante se engajar em comportamento de assédio, os organizadores do evento podem tomar medidas que considerem adequadas, desde alertas ao infrator até a vedação de sua participação em demais eventos promovidos pelos membros da organização individual ou coletivamente.
+
+Se você for assediado, perceber que alguém está sendo assediado, ou tem outras preocupações, por favor aja para interceptar ou peça ajuda aos organizadores. Estamos certos de que essa política ajudará a fazer do DevOpsDays um espaço mais acolhedor, inclusivo, e integrador para todos.
+
+Este Código de Conduta foi adaptado a partir do código de conduta utilizado pelo DevOpsDays Porto Alegre 2016, que foi adaptado pela comunidade GTC - Grupo de Testes Carioca, que foi adaptado pelo evento LinguÁgil, que foi adaptado pelo evento Agile Trends, que foi adaptado a partir dos códigos de conduta utilizados pelo Ideias em Produção, adaptados a partir do Python Brasil 9, este por sua vez adaptados dos códigos de conduta utilizados pela Plone Foundation e pela PyCon US, e estão licenciados sob a Creative Commons Attribution-Share Alike 3.0 Unported.
diff --git a/exampleSite/content/events/2017-sao-paulo/contato.md b/exampleSite/content/events/2017-sao-paulo/contato.md
new file mode 100644
index 000000000..c689bd2a8
--- /dev/null
+++ b/exampleSite/content/events/2017-sao-paulo/contato.md
@@ -0,0 +1,18 @@
++++
+date = "2016-12-08T16:35:49-05:00"
+title = "contato"
+type = "event"
+aliases = ["/events/2017-sao-paulo/contact"]
+
+
++++
+
+Se você deseja falar conosco por e-mail: {{< email_organizers >}}
+
+**Nosso time local**
+
+{{< list_organizers >}}
+
+**O grupo central de organizadores do devopsdays**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-sao-paulo/local.md b/exampleSite/content/events/2017-sao-paulo/local.md
new file mode 100644
index 000000000..6a0cd067f
--- /dev/null
+++ b/exampleSite/content/events/2017-sao-paulo/local.md
@@ -0,0 +1,11 @@
++++
+date = "2016-12-08T16:35:49-05:00"
+title = "local"
+type = "event"
+aliases = ["/events/2017-sao-paulo/location"]
+
++++
+
+Informações sobre o local, incluindo endereço, mapa / direção, estacionamento / trânsito, etc. estarão aqui.
+
+
diff --git a/exampleSite/content/events/2017-sao-paulo/patrocinio.md b/exampleSite/content/events/2017-sao-paulo/patrocinio.md
new file mode 100644
index 000000000..c7fbd21ec
--- /dev/null
+++ b/exampleSite/content/events/2017-sao-paulo/patrocinio.md
@@ -0,0 +1,13 @@
++++
+date = "2016-12-08T16:35:49-05:00"
+title = "patrocínio"
+type = "event"
+aliases = ["/events/2017-sao-paulo/sponsor"]
+
+
++++
+
+Se você está interessado em nos patrocinar, entre em contato pelo email [{{< email_organizers >}}].
+
+
+
diff --git a/exampleSite/content/events/2017-sao-paulo/programacao.md b/exampleSite/content/events/2017-sao-paulo/programacao.md
new file mode 100644
index 000000000..3d64c117e
--- /dev/null
+++ b/exampleSite/content/events/2017-sao-paulo/programacao.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "Programação"
+type = "event"
+
++++
+
+
+
diff --git a/exampleSite/content/events/2017-seattle/conduct.md b/exampleSite/content/events/2017-seattle/conduct.md
new file mode 100644
index 000000000..7d2e98a4c
--- /dev/null
+++ b/exampleSite/content/events/2017-seattle/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-09-20T21:46:51+01:00"
+title = "DevOpsDays Seattle 2017 Code of Conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-seattle/contact.md b/exampleSite/content/events/2017-seattle/contact.md
new file mode 100644
index 000000000..b4c333dc6
--- /dev/null
+++ b/exampleSite/content/events/2017-seattle/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-09-20T21:46:51+01:00"
+title = "DevOpsDays Seattle 2017 Contact Information"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-seattle/location.md b/exampleSite/content/events/2017-seattle/location.md
new file mode 100644
index 000000000..80fa080e9
--- /dev/null
+++ b/exampleSite/content/events/2017-seattle/location.md
@@ -0,0 +1,27 @@
++++
+date = "2016-09-20T21:46:51+01:00"
+title = "DevOpsDays Seattle 2017 Location"
+type = "event"
+
++++
+
+
+
+
+
+
+___[Marion Oliver McCaw Hall](https://www.mccawhall.com/plan-your-event/event-spaces/nesholm-family-lecture-hall) at Seattle Center is the region’s premier performance venue.___
+
+McCaw Hall opened in June 2003 as a $127 million renovation of the Seattle Opera House, made possible by a partnership between the Hall’s two world-class resident performing arts tenants, Pacific Northwest Ballet and Seattle Opera, along with Seattle Center and the Seattle Center Foundation. This partnership secured $55 million in public funds and over $72 million in private philanthropic gifts to make the Hall a reality. The Hall is owned by the City of Seattle and operated by Seattle Center, in accordance with a unique 25-year Operating Agreement with its resident tenants, which provides them with on-going oversight and shared responsibility for its operations and budget.
+
+
+
+McCaw Hall encompasses the state-of-the-art 2,900-seat Susan Brotman Auditorium, the 380-seat Nesholm Family Lecture Hall, Prelude Café, elegant lobbies fronted by a luminous five-story serpentine glass wall, two beautiful donor/special function rooms, and a 17,800-square-foot public plaza (the Kreielsheimer Promenade) that serves as an entry into McCaw Hall and the Seattle Center campus. Designed by local architectural firm LMN, the Hall’s design emphasizes elegance balanced with flexibility and functionality. Its open, airy lobbies strive to minimize the separation between exterior and interior, inviting the community to view and join the anticipation of audiences prior to a performance. As well, the Hall incorporates a number of environmentally sustainable design features which minimize its use of resources, waste generation and carbon footprint.
+
+
+
+Each year the Ballet and Opera present approximately 150 performances in McCaw Hall. In addition, the Hall hosts two productions of the Seattle Men’s Chorus annually, as well as a wide range of popular music concerts, lectures, corporate meetings, receptions, weddings, festival performances, community, and non-profit events.
+
+
+
+
diff --git a/exampleSite/content/events/2017-seattle/program.md b/exampleSite/content/events/2017-seattle/program.md
new file mode 100644
index 000000000..22d161fea
--- /dev/null
+++ b/exampleSite/content/events/2017-seattle/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "DevOpsDays Seattle 2017 Program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-seattle/propose.md b/exampleSite/content/events/2017-seattle/propose.md
new file mode 100644
index 000000000..94fafa76c
--- /dev/null
+++ b/exampleSite/content/events/2017-seattle/propose.md
@@ -0,0 +1,41 @@
++++
+date = "2016-09-20T21:46:51+01:00"
+title = "DevOpsDays Seattle 2017 Call for Proposals"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
diff --git a/exampleSite/content/events/2017-seattle/sponsor.md b/exampleSite/content/events/2017-seattle/sponsor.md
new file mode 100644
index 000000000..927174d44
--- /dev/null
+++ b/exampleSite/content/events/2017-seattle/sponsor.md
@@ -0,0 +1,123 @@
++++
+date = "2016-09-20T21:46:51+01:00"
+title = "DevOpsDays Seattle 2017 Sponsorship Info"
+type = "event"
+
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+
+ This year's event will be held at McCaw Hall in Seattle. This venue should allow great interaction with attendees throughout
+ the event.
+
+
+
+ DevOpsDays is a volunteer organized event for practitioners that depends on sponsorships. All of the talks are
+ selected via an open CFP in order to present the highest quality conference possible. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+
+
+
+ Gold sponsors have the opportunity to have short elevator pitches during the program. All sponsors will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers.
+
+
+
+ Most sponsors find they get the best response by sending engineers to interact with the experts at DevOpsDays on their own terms.
+
{{< event_link page="propose" text="The CFP is now open! Click here to propose a talk!" >}}
+
+
+
+We're very excited to bring DevOpsDays back to Seattle in 2017. This year the event will be held at
+{{< event_link page="location" text="McCaw Hall" >}} in the Seattle Center. This theater style venue
+will be great for both speakers and attendees.
+
+
+
+
+
+
+
+
+ {{< event_link page="registration" text="Register to attend the conference!" >}}
+
+
+
+
+
+ Propose
+
+
+ {{< event_link page="propose" text="Propose a talk!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-stockholm/conduct.md b/exampleSite/content/events/2017-stockholm/conduct.md
new file mode 100644
index 000000000..b9a541929
--- /dev/null
+++ b/exampleSite/content/events/2017-stockholm/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-11-28T22:36:47+01:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-stockholm/contact.md b/exampleSite/content/events/2017-stockholm/contact.md
new file mode 100644
index 000000000..ded322e77
--- /dev/null
+++ b/exampleSite/content/events/2017-stockholm/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-11-28T22:36:47+01:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-stockholm/location.md b/exampleSite/content/events/2017-stockholm/location.md
new file mode 100644
index 000000000..24755f1a9
--- /dev/null
+++ b/exampleSite/content/events/2017-stockholm/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-11-28T22:36:47+01:00"
+title = "location"
+type = "event"
+
++++
+
+Information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-stockholm/program.md b/exampleSite/content/events/2017-stockholm/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-stockholm/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-stockholm/propose.md b/exampleSite/content/events/2017-stockholm/propose.md
new file mode 100644
index 000000000..807eadd62
--- /dev/null
+++ b/exampleSite/content/events/2017-stockholm/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-11-28T22:36:47+01:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-stockholm/sponsor.md b/exampleSite/content/events/2017-stockholm/sponsor.md
new file mode 100644
index 000000000..099d64257
--- /dev/null
+++ b/exampleSite/content/events/2017-stockholm/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-11-28T22:36:47+01:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-stockholm/welcome.md b/exampleSite/content/events/2017-stockholm/welcome.md
new file mode 100644
index 000000000..fd55150e8
--- /dev/null
+++ b/exampleSite/content/events/2017-stockholm/welcome.md
@@ -0,0 +1,93 @@
++++
+date = "2016-11-28T22:36:47+01:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-stockholm"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-tokyo/conduct.md b/exampleSite/content/events/2017-tokyo/conduct.md
new file mode 100644
index 000000000..8f60ef258
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2017-01-06T11:12:21-06:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-tokyo/contact.md b/exampleSite/content/events/2017-tokyo/contact.md
new file mode 100644
index 000000000..e0821066a
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2017-01-06T11:12:21-06:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-tokyo/location.md b/exampleSite/content/events/2017-tokyo/location.md
new file mode 100644
index 000000000..8ab8162dd
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/location.md
@@ -0,0 +1,10 @@
++++
+date = "2017-01-06T11:12:21-06:00"
+title = "location"
+type = "event"
+
++++
+
+Coming soon: information about the venue including address, map/direction, parking/transit, and any hotel group discount codes.
+
+
diff --git a/exampleSite/content/events/2017-tokyo/program.md b/exampleSite/content/events/2017-tokyo/program.md
new file mode 100644
index 000000000..581bd82a3
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/program.md
@@ -0,0 +1,14 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+ Coming soon! Currently, we are thinking of a single day event, with possibly a second hackathon or workshop day.
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-tokyo/propose.md b/exampleSite/content/events/2017-tokyo/propose.md
new file mode 100644
index 000000000..c34f3319e
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/propose.md
@@ -0,0 +1,12 @@
++++
+date = "2017-01-06T11:12:21-06:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+
+We're still working on writing up the theme of DevOps Days Tokyo (both in English and 日本語), so we aren't quite ready to open the CPF yet.
+
+We plan to have both regular talks and presentations, as well as Ignite/lightening talks.
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-tokyo/registration.md b/exampleSite/content/events/2017-tokyo/registration.md
new file mode 100644
index 000000000..9e7aca263
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/registration.md
@@ -0,0 +1,14 @@
++++
+date = "2017-01-06T11:12:21-06:00"
+title = "registration"
+type = "event"
+
+
++++
+
+
+
+TBD.
+
+
+
diff --git a/exampleSite/content/events/2017-tokyo/sponsor.md b/exampleSite/content/events/2017-tokyo/sponsor.md
new file mode 100644
index 000000000..b5eee44c9
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/sponsor.md
@@ -0,0 +1,9 @@
++++
+date = "2017-01-06T11:12:21-06:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We're still working on defining the sponsorship details, but if you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
diff --git a/exampleSite/content/events/2017-tokyo/welcome.md b/exampleSite/content/events/2017-tokyo/welcome.md
new file mode 100644
index 000000000..36c686475
--- /dev/null
+++ b/exampleSite/content/events/2017-tokyo/welcome.md
@@ -0,0 +1,93 @@
++++
+date = "2017-01-06T11:12:21-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-tokyo"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-toronto/conduct.md b/exampleSite/content/events/2017-toronto/conduct.md
new file mode 100644
index 000000000..095ebf90c
--- /dev/null
+++ b/exampleSite/content/events/2017-toronto/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-08-24T11:29:13-05:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-toronto/contact.md b/exampleSite/content/events/2017-toronto/contact.md
new file mode 100644
index 000000000..258ca27b6
--- /dev/null
+++ b/exampleSite/content/events/2017-toronto/contact.md
@@ -0,0 +1,19 @@
++++
+date = "2016-08-24T11:29:13-05:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+(and more to be confirmed!)
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-toronto/location.md b/exampleSite/content/events/2017-toronto/location.md
new file mode 100644
index 000000000..5fc881583
--- /dev/null
+++ b/exampleSite/content/events/2017-toronto/location.md
@@ -0,0 +1,37 @@
++++
+City = "Toronto"
+Year = "2017"
+date = "2017-12-08T20:00:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+### Conference location:
+
+DevOps Days Toronto is being hosted at the Glenn Gould Studio located at corner of Front and John in the Canadian Broadcasting Centre. The Studio and its washrooms are wheelchair accessible.
+Glenn Gould Studios: 250 Front St West, Toronto, ON. M5V 3G5 - (416) 205-5000
+
+
+
+
+
+### Public Transportation
+
+Glenn Gould Studio is easily accessible by public transit. From the TTC and Go Transit stops at Union Station, you can walk west three blocks to the Canadian Broadcasting Centre on the north side of Front Street. Glenn Gould Studio is connected to the PATH underground walkway via St. Andrews subway station. Visit the Toronto Transit Commission (TTC) or GO Transit websites for transit directions or use Google Maps as a starting point for finding transit information.
+
+### Planes, Trains and Automobiles
+
+Toronto has two airports: Toronto Pearson International Airport and Billy Bishop Toronto City Airport. Check Expedia.ca for flight information.
+
+Via Rail and GO Transit trains connect at Union Station, the main station for Toronto. Union Station connects with public transit.
+
+There are a number of parking lots near the Canadian Broadcasting Centre. Please review Glenn Gould Parking Map for all of the options. The nearest Green P lot is Carpark 52 at 40 York Street. Daytime rate (7am - 7pm) is $20.00 and night time rates (5pm - 7am) is $8.00.
+
+### Accommodations
+
+Toronto is a world class city with a multitude of accomodation options near Glenn Gould Studios. We are investigating group space at a nearby hotel. More details will be shared in the near future.
+
+### Tourism
+
+Come to Toronto for DevOps Days, but check Tourism Toronto for more information on tourist packages and hotels. Sometimes a package deal can make travel less expensive and more fun. What is your interest: opera, ballet, live theatre, art gallery, museums, shopping, music, sports?
diff --git a/exampleSite/content/events/2017-toronto/propose.md b/exampleSite/content/events/2017-toronto/propose.md
new file mode 100644
index 000000000..a9b915346
--- /dev/null
+++ b/exampleSite/content/events/2017-toronto/propose.md
@@ -0,0 +1,42 @@
++++
+City = "Toronto"
+Year = "2016"
+date = "2016-03-06T22:47:24-06:00"
+title = "propose"
+type = "event"
+
++++
+ {{< cfp_dates >}}
+
+
+
+### Equal Opportunity
+
+DevOpsDays Toronto is committed to creating a diverse environment and is proud to invite people of all backgrounds and profiles to submit presentation proposals. All potential speakers will receive consideration without regard to race, colour, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, ability or age.
+
+For more information, please see our published {{< event_link page="conduct" text="Code of Conduct" >}}.
+
+### Proposals
+
+There are three ways to propose a session:
+
+1. __A proposal for a talk/panel__ during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+2. __An Ignite talk__ that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+3. __Open Space session__ : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+- __Broad appeal__: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+- __New local presenters__: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
+- __Under-represented voices__: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+- __Original content__: We prefer talks not already presented at another event, especially another one in the local area or one available in recorded form.
+- __No third-party submissions__: If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process. This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees.
+- __No vendor pitches__: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
+
+### Submit
+
+To submit a talk create an account on our OpenCFP and click the _Submit a talk_ button.
+
+- Be specific... we aren't mind readers (a description of about 20 lines is about right)
+- Detail is good... but not as important as explaining why your proposal would be interesting
+- Multiple proposals welcome... just follow the other rules
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-toronto/register.md b/exampleSite/content/events/2017-toronto/register.md
new file mode 100644
index 000000000..e0b5f5069
--- /dev/null
+++ b/exampleSite/content/events/2017-toronto/register.md
@@ -0,0 +1,10 @@
++++
+date = "2016-12-22T21:17:14-06:00"
+title = "register"
+type = "event"
+
++++
+
+Registration for DevOpsDays Toronto is now open. If you have any questions please contact us at {{< email_organizers >}}.
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-toronto/sponsor.md b/exampleSite/content/events/2017-toronto/sponsor.md
new file mode 100644
index 000000000..a982ced69
--- /dev/null
+++ b/exampleSite/content/events/2017-toronto/sponsor.md
@@ -0,0 +1,12 @@
++++
+date = "2016-03-06T21:17:14-06:00"
+title = "sponsor"
+type = "event"
+
++++
+
+The DevOps Days event mandate is to bring the highestquality speakers, experts and the curious together. By sponsoring DevOps Days, you will be exposing your company’s brand and services to Toronto’s top talent in this rapidly growing space. (And feel great about it, too!)
+
+Download our prospectus to see the features of the various sponsorship options.
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please email us at {{< email_organizers >}}.
diff --git a/exampleSite/content/events/2017-toronto/welcome.md b/exampleSite/content/events/2017-toronto/welcome.md
new file mode 100644
index 000000000..547dd7ede
--- /dev/null
+++ b/exampleSite/content/events/2017-toronto/welcome.md
@@ -0,0 +1,114 @@
++++
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-toronto"]
+
+
++++
+
+
+ {{< event_logo >}}
+ Be part of the fourth DevOpsDays Toronto in May 2017!
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+
+
+ Propose
+
+
+ {{< event_link page="propose" text="Propose a talk!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsor
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
+
+
+ {{< event_twitter DevOpsDaysTO >}}
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-vancouver/conduct.md b/exampleSite/content/events/2017-vancouver/conduct.md
new file mode 100644
index 000000000..ad136d287
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-11-09T22:35:17-08:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-vancouver/contact.md b/exampleSite/content/events/2017-vancouver/contact.md
new file mode 100644
index 000000000..8bc4ed76b
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/contact.md
@@ -0,0 +1,17 @@
++++
+date = "2016-11-09T22:35:17-08:00"
+title = "contact"
+type = "event"
+
+
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-vancouver/location.md b/exampleSite/content/events/2017-vancouver/location.md
new file mode 100644
index 000000000..d41a5edac
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/location.md
@@ -0,0 +1,20 @@
++++
+City = "Vancouver"
+Year = "2017"
+date = "2016-11-13T21:17:00-06:00"
+title = "location"
+type = "event"
+
++++
+
+## Conference Location
+
+
diff --git a/exampleSite/content/events/2017-vancouver/policies.md b/exampleSite/content/events/2017-vancouver/policies.md
new file mode 100644
index 000000000..33186cbdd
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/policies.md
@@ -0,0 +1,34 @@
++++
+date = "2016-11-09T22:35:17-08:00"
+title = "policies"
+type = "event"
+
++++
+
+## Ticket Policies
+
+### Early bird tickets
+Once they’re gone they’re gone.
+
+### Discounts
+Unfortunately we are not able to offer discounts for volume purchases.
+
+### What is the refund policy?
+There are no refunds for DevopsDays Vancouver 2017.
+
+### What? Why not?
+We are a volunteer run conference and have limited capacity to offer refunds. We apologize for the inconvenience.
+
+### The name on the registration/ticket doesn't match the attendee. Is that okay?
+
+If there is an error with the ticket, please reach out to us and we will try to rectify it. 45 days before the event we will lock down the registration list but feel free to send someone else to claim your ticket with your registration (this is OK).
+
+
+## Sponsorship tickets
+
+If you’re attending as part of a sponsor group, your company representative will have a promo code for you to claim your ticket. Please contact them for assistance.
+
+### Sponsorship ticket contact
+
+Please contact organizers-vancouver-2017@devopsdays.org for assistance if you are the company representative and need assistance
+
diff --git a/exampleSite/content/events/2017-vancouver/program.md b/exampleSite/content/events/2017-vancouver/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-vancouver/propose.md b/exampleSite/content/events/2017-vancouver/propose.md
new file mode 100644
index 000000000..183dba222
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/propose.md
@@ -0,0 +1,40 @@
++++
+date = "2016-11-09T22:35:17-08:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+Talk submission form
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 25 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+### Even if you don't propose, please consider {{< event_link page="proposals" text="commenting on proposals submitted by others" >}}
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-vancouver/sponsor.md b/exampleSite/content/events/2017-vancouver/sponsor.md
new file mode 100644
index 000000000..ddbf725c9
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-11-09T22:35:17-08:00"
+title = "sponsor"
+type = "event"
+
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
+
+
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors have the opportunity to have short elevator pitches during the program and will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
+
+The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-vancouver/welcome.md b/exampleSite/content/events/2017-vancouver/welcome.md
new file mode 100644
index 000000000..237f59af5
--- /dev/null
+++ b/exampleSite/content/events/2017-vancouver/welcome.md
@@ -0,0 +1,141 @@
++++
+date = "2017-11-09T22:35:17-08:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-vancouver"]
+
++++
+
+
+ {{< event_logo >}}
+
+
+
+
DevOpsDays Vancouver 2017
+
+
+
+
+
{{< event_start >}} - {{< event_end >}}
+
UBC Robson Square
+
DevOpsDays is returning to Vancouver in 2017.
+
DevOpsDays is a self-organizing conference for DevOps practitioners.
diff --git a/exampleSite/content/events/2017-washington-dc/conduct.md b/exampleSite/content/events/2017-washington-dc/conduct.md
new file mode 100644
index 000000000..f0d448e78
--- /dev/null
+++ b/exampleSite/content/events/2017-washington-dc/conduct.md
@@ -0,0 +1,73 @@
++++
+date = "2016-09-26T12:57:27-04:00"
+title = "conduct"
+type = "event"
+
++++
+
+## Conference Code of Conduct
+
+All attendees, speakers, sponsors and volunteers at our conference are required
+to agree with the following code of conduct. organizers will enforce this code
+throughout the event. We are expecting cooperation from all participants to help
+ensuring a safe environment for everybody. A strong community benefits everyone.
+To that end, please consider as a goal that you should always try to benefit the
+community by encouraging participation, open-mindedness, learning, and safety in
+every interaction. Behaviour outside of our community guidelines is unacceptable
+and should and will not be tolerated by anyone.
+
+
+
+ tl;dr: Don’t be a Jerk
+
+
+
+## The Quick Version
+
+Our conference is dedicated to providing a harassment-free conference experience
+for everyone, regardless of gender, age, sexual orientation, disability,
+physical appearance, body size, race, or religion (or lack thereof.) We do not
+tolerate harassment of conference participants in any form. Sexual language and
+imagery is not appropriate for any conference venue, including talks, workshops,
+parties, Twitter and other online media. Conference participants violating these
+rules may be sanctioned or expelled from the conference without a refund at the
+discretion of the conference organizers.
+
+## The Less Quick Version
+
+Harassment includes offensive verbal comments related to gender, age, sexual
+orientation, disability, physical appearance, body size, race, religion, sexual
+images in public spaces, deliberate intimidation, stalking, following, harassing
+photography or recording, sustained disruption of talks or other events,
+inappropriate physical contact, and unwelcome sexual attention.
+
+Participants asked to stop any harassing behavior are expected to comply
+immediately.
+
+Sponsors are also subject to the anti-harassment policy. In particular, sponsors
+should not use sexualized images, activities, or other material. Booth staff
+(including volunteers) should not use sexualized clothing/uniforms/costumes, or
+otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may
+take any action they deem appropriate, including warning the offender or
+expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have
+any other concerns, please contact a member of conference staff immediately.
+Conference staff can be identified as they'll be wearing branded t-shirts.
+
+Conference staff will be happy to help participants contact hotel/venue security
+or local law enforcement, provide escorts, or otherwise assist those
+experiencing harassment to feel safe for the duration of the conference. We
+value your attendance.
+
+We expect participants to follow these rules at conference and workshop venues
+and conference-related social events.
+
+### Need to reach the organizers?
+
+We will have organizers on-call throughout the conference to respond to any
+issues you may have. On-call organizer contact information will be posted closer
+to the event date. For now, if you have questions or concerns, please mail us at
+.
diff --git a/exampleSite/content/events/2017-washington-dc/contact.md b/exampleSite/content/events/2017-washington-dc/contact.md
new file mode 100644
index 000000000..75f607bfe
--- /dev/null
+++ b/exampleSite/content/events/2017-washington-dc/contact.md
@@ -0,0 +1,24 @@
++++
+date = "2016-09-26T12:57:27-04:00"
+title = "contact"
+type = "event"
+
+
++++
+Follow [@devopsdaysdc](https://twitter.com/devopsdaysdc) on twitter.
+
+What questions can we answer for you? Drop us an email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+{{< event_twitter devopsdaysdc >}}
+
+
+
diff --git a/exampleSite/content/events/2017-washington-dc/sponsor.md b/exampleSite/content/events/2017-washington-dc/sponsor.md
new file mode 100644
index 000000000..9be9cf08e
--- /dev/null
+++ b/exampleSite/content/events/2017-washington-dc/sponsor.md
@@ -0,0 +1,185 @@
++++
+date = "2016-09-26T12:57:27-04:00"
+title = "sponsor"
+type = "event"
+
+
++++
+We greatly value sponsors for this open event. Have questions about sponsoring?
+Please contact us at {{< email_organizers >}}.
+
+
+
+
+
+
Packages
+
Community
+
Media
+
Silver
+
Gold
+
Platinum
+
+
+
+
$0 USD
+
$0 USD
+
$1,000 USD
+
$3,000 USD
+
$5,000 USD
+
+
+
1 included ticket
+
+
+
+
+
+
+
+
Logo on shared slide, rotating during breaks
+
+
+
+
+
+
+
+
Logo on DevOpsDays DC 2017 event website
+
+
+
+
+
+
+
+
Logo on all email communication
+
+
+
+
+
+
+
+
1 minute pitch to full audience
+
+
+
+
+
+
+
+
1 additional tickets (2 in total)
+
+
+
+
+
+
+
+
3 additional tickets (4 in total)
+
+
+
+
+
+
+
+
Shared table for swag
+
+
+
+
+
+
+
+
Dedicated table in preferred location for swag
+
+
+
+
+
+
+
+
+
+We greatly value sponsors for this open event. If you are interested in other
+types of sponsorships, please contact us directly at {{< email_organizers >}}.
+
+DevOps Days is not 'that kind of conference' and heavy marketing will probably
+work against you when trying to make a good impression on the attendees. Contact
+{{< email_organizers >}} for some ideas about how to make the most of
+your sponsorship.
+
+### Community - $0
+
+The community sponsorship is ideal for local meetups, co-working spaces, and
+other communities who support DevOps. This sponsorship is free but we ask that
+you share information about DevOpsDays DC with your members in order to become a
+Community Sponsor.
+
+* 1 ticket
+* 10% discount code to share with your members
+* Logo on shared slide, rotating during breaks
+* Logo on DevOpsDays DC 2017 event website
+* Please contact {{< email_organizers >}} for details about becoming a community
+sponsor.
+
+### Media - $0
+
+The media sponsorship is ideal for podcasts, blogs, news outlets, and other
+media who support DevOps. This sponsorship is free but we ask that you share
+information about DevOpsDays DC with your audience in order to become a
+Community Sponsor.
+
+* 1 ticket
+* 10% discount code to share with your audience
+* Logo on shared slide, rotating during breaks
+* Logo on DevOpsDays DC 2017 event website
+* Please contact {{< email_organizers >}} for details about becoming a media
+sponsor.
+
+### Silver - $1,000
+
+* 1 included ticket
+* Logo on shared slide, rotating during breaks
+* Logo on DevOpsDays DC 2017 event website
+
+### Gold - $3,000
+
+* All benefits of Silver sponsors
+* Logo on all email communication
+* 1 additional ticket, 2 in total
+* Shared table for swag
+
+### Platinum - $5,000
+
+* All benefits of Gold sponsors
+* 1 minute pitch to full audience, including streaming audience
+* 2 additional tickets, 4 in total
+* Dedicated table for swag
+
+We greatly value sponsors for this open event. If you are interested in other
+types of sponsorships, please contact us directly at {{< email_organizers >}}.
+
+---
+
+DevOpsDays is a self-organizing conference for DevOps practitioners that depends
+on your sponsorships to happen. However, because of the nature of the event, we
+do not have vendor booths or book product pitches.
+
+Platinum sponsors do get a table they can hang out at and put materials on for
+interested people to come visit during breaks, and of course all attendees are
+welcome to propose any subject they want during the open spaces, but this is not
+'that kind of conference' and heavy marketing will probably work against you
+when trying to make a good impression on the attendees. The best thing to do is
+send engineers to interact with the experts at DevOpsDays on their own terms.
+
+
+We greatly value sponsors for this open event. If you are interested in
+sponsoring, please drop us an email at {{< email_organizers >}}.
diff --git a/exampleSite/content/events/2017-washington-dc/welcome.md b/exampleSite/content/events/2017-washington-dc/welcome.md
new file mode 100644
index 000000000..d3c44e430
--- /dev/null
+++ b/exampleSite/content/events/2017-washington-dc/welcome.md
@@ -0,0 +1,101 @@
++++
+date = "2016-09-26T12:57:27-04:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-washington-dc"]
+
++++
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+**devopsdays is coming to {{< event_location >}}!**
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
+
+
diff --git a/exampleSite/content/events/2017-zurich/conduct.md b/exampleSite/content/events/2017-zurich/conduct.md
new file mode 100644
index 000000000..5b710d908
--- /dev/null
+++ b/exampleSite/content/events/2017-zurich/conduct.md
@@ -0,0 +1,101 @@
++++
+date = "2016-07-20T13:45:44+02:00"
+title = "conduct"
+type = "event"
+
++++
+# CODE OF CONDUCT
+
+## Reporting Guidelines
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
+
+#### Twitter (Transparent for everyone):
+{{< event_twitter devopszh >}}
+
+#### Via Email to the organizer team:
+
+
+#### Directly at the conference
+
+We will wear special crew shirts and we try to be always around, please reach us out even if we look busy.
+
+{{< list_organizers >}}
+
+## Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the organizer of the conference with a concise description of your grievance. We will have a full disclosure policy and we will report every violations publicly (just the violation, no personal details).
+
+## Reward respectful and helpful behavior
+
+A supplemental goal of this Code of Conduct is to increase open tech citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
+
+If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know. Please share Kudos via Twitter or with our special Kudo Cards (just look for our Kudo boxes http://www.happymelly.com/the-art-of-saying-thank-you/)
+
+{{< event_twitter devopszh >}}
+
+## Purpose
+
+A primary goal of DevOpsDays Zürich is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in DevOpsDays Zürich to help us create safe and positive experiences for everyone.
+
+### Expected Behavior
+
+The following behaviors are expected and requested of all community members:
+
+Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+Exercise consideration and respect in your speech and actions.
+Attempt collaboration before conflict.
+Refrain from demeaning, discriminatory, or harassing behavior and speech.
+Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+
+### Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+Violence, threats of violence or violent language directed against another person.
+Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+Posting or displaying sexually explicit or violent material.
+Posting or threatening to post other people’s personally identifying information ("doxing").
+Personal insults, particularly those related to gender, sexual orientation, ethnicity, religion, or disability.
+Inappropriate photography or recording.
+Inappropriate physical contact. You should have someone’s consent before touching them.
+Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+Deliberate intimidation, stalking or following (online or in person).
+Advocating for, or encouraging, any of the above behavior.
+Sustained disruption of community events, including talks and presentations.
+
+### Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning and without refund.
+
+
+### Scope
+
+We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business.
+
+This code of conduct and its related procedures also applies to unacceptable behavior occuring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
+
+### Contact info
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Logistics
+
+
+
+
+
+
+
+
+ Evening Event
+
+
+
+
+
+
+
+
+
+
+
+
+
Day 2
+
+
+
+
+
+
+
+
+ Registration, Breakfast, and Sponsor Booths Open
+
+
+
+
+
+
+
+
+ Opening Welcome
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Break
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lunch (catered)
+
+
+
+
+
+
+
+
+ Ignites
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space Opening
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #1
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #2
+
+
+
+
+
+
+
+
+ Open Space
+ Open Space #3
+
+
+
+
+
+
+
+
+ Close Day & Farewell
+
+
+
+
diff --git a/exampleSite/content/events/2017-zurich/propose.md b/exampleSite/content/events/2017-zurich/propose.md
new file mode 100644
index 000000000..51cf0a452
--- /dev/null
+++ b/exampleSite/content/events/2017-zurich/propose.md
@@ -0,0 +1,37 @@
++++
+date = "2016-07-20T13:45:44+02:00"
+title = "propose"
+type = "event"
++++
+ {{< cfp_dates >}}
+
+
+There are three ways to propose a session:
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
+
Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
+
+
+
+
+Our main criteria to make it to the top selection are:
+
+- _original content_: content not yet presented at other conferences, or a new angle to an existing problem
+- _new presenters_: people who are new to the space and have insightful stuff to say; we want to hear everybody's voice
+- _no vendor pitches_: as much as we value vendors and sponsors, we just don't think this is the right forum. You can demo at your table or during Open Space.
+
+How to submit a proposal: Send an email to [{{< email_proposals >}}] with the following information
+
+
Proposal working title (can be changed later)
+
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
+
Description or abstract
+
+Rules:
+
+
Be specific... we aren't mind readers (a description of about 20 lines is about right)
+
Detail is good... but not as important as explaining why your proposal would be interesting
+
Propose your own talk; don't have someone else do it for you.
+
Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
+
Multiple proposals welcome... just follow the other rules
+
diff --git a/exampleSite/content/events/2017-zurich/sponsor.md b/exampleSite/content/events/2017-zurich/sponsor.md
new file mode 100644
index 000000000..fd1e8650a
--- /dev/null
+++ b/exampleSite/content/events/2017-zurich/sponsor.md
@@ -0,0 +1,112 @@
++++
+date = "2016-07-20T13:45:44+02:00"
+title = "sponsor"
+type = "event"
+
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at {{< email_organizers >}}.
+
+Please keep in mind, that you accept our Code of Conduct with sponsoring this event: {{< event_link page="conduct" text="Please read the Code of Conduct" >}}
+
+### Sponsoring packages
+
+
+
Packages
+
Bronze 1500 CHF
+
Silver 3000 CHF
+
Gold 6000 CHF
+
+
+
+
+
Four Sponsortickets in total
+
+
+
+
+
+
+
Two Sponsortickets in total
+
+
+
+
+
+
+
One Sponsortickets in total
+
+
+
+
+
+
+
Dedicated table/booth
+
+
+
+
+
+
+
shared table for swag
+
+
+
+
+
+
+
logo on its own slide, rotating during breaks
+
+
+
+
+
+
+
logo on all email communication
+
+
+
+
+
+
+
+
+
+
+
+
+
+
logo on shared slide, rotating during breaks
+
+
+
+
+
+
+
+
+
+
+
+
+
+
thank you tweet
+
+
+
+
+
+
+
logo on event website
+
+
+
+
+
+
+### Why DevOpsDays?
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+
+Gold sponsors get a full table and Silver sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject their topics during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees.
\ No newline at end of file
diff --git a/exampleSite/content/events/2017-zurich/welcome.md b/exampleSite/content/events/2017-zurich/welcome.md
new file mode 100644
index 000000000..1e29818b8
--- /dev/null
+++ b/exampleSite/content/events/2017-zurich/welcome.md
@@ -0,0 +1,92 @@
++++
+date = "2016-07-20T13:45:44+02:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2017-zuerich"]
+
++++
+
+
+{{< event_twitter devopszh >}}
+
+**DevOpsDays is coming to {{< event_location >}}**
+
+
{{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+ Dates
+
+
+ {{< event_start >}} - {{< event_end >}}
+
+
+
+
+
+
+
+ Location
+
+
+ {{< event_location >}}
+
+
+
+
+
+
+
+ Propose
+
+
+ {{< event_link page="propose" text="Propose a talk!" >}}
+
+
+
+
+
+
+
+
+
+ Sponsors
+
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}}
+
+
+
+
+
+ Contact
+
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}}
+
+
\ No newline at end of file
diff --git a/exampleSite/content/page/conduct.md b/exampleSite/content/page/conduct.md
new file mode 100644
index 000000000..75c0191cc
--- /dev/null
+++ b/exampleSite/content/page/conduct.md
@@ -0,0 +1,15 @@
++++
+date = "2016-08-19T00:00:00-06:00"
+title = "devopsdays code of conduct"
+
++++
+
+Respect and empathy are core devops values. Devopsdays is dedicated to providing an environment where everyone in the devops community can learn and share in respectful, considerate collaboration.
+
+Every devopsdays event has a code of conduct, and we expect the organizer community before, during, and after the conferences to follow a similar code of conduct.
+
+Devopsdays is dedicated to providing a harassment-free experience for every participant, regardless of gender, sexual orientation, disability, physical appearance, body size, race, religion, or any other personal characteristics. We do not tolerate harassment of anyone in any form. Sexual language and imagery is not appropriate for any devopsdays venue, including Slack, GitHub, and email. Participants violating these rules may be sanctioned or expelled from the organization at the discretion of the core organizers.
+
+Harassment includes offensive verbal or written comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please [contact a member of core organizers](http://www.devopsdays.org/contact/) immediately.
diff --git a/exampleSite/content/page/devops-gives-back.md b/exampleSite/content/page/devops-gives-back.md
new file mode 100644
index 000000000..f370d2a80
--- /dev/null
+++ b/exampleSite/content/page/devops-gives-back.md
@@ -0,0 +1,72 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2016-04-14T11:38:41-05:00"
+title = "Devopsdays Gives Back"
+aliases = "/pages/organizing/charity"
+
++++
+
+
Introduction
+
+
Below is a small summary of an open space that took place at Devopsdays Ghent (October, 2014). The goal of the open space was to find ways on how Devopsdays organizers and attendees can contribute to NGOs or other good causes.
+
+
Two prior Devopsdays events donated some of the profits to charity. Devopsdays NY 2014 donated to the drilling of a well in Cambodia. Devopsdays Belgium 2014 donated to Manbarnootaaf VZW.
+
+
Both initiatives came from persons who were on the organizing committee. As there are many Devopsdays it maybe isn't clear that profits can be donated. Or that some other activity can be organized. It could also be that organizers think too late of the possibility of
+donating. This document tries to give them a head start.
+
+
Rationale
+
+
Many western countries have been hit hard by a global recession for the past few years. While many in our countries and others have struggled, the tech sector has been experiencing a rapid boom with many jobs available which has fueled a surge in salaries, benefits, etc. This has led to increased spending on recruiting, marketing, etc. in order to attracted the best talent and investment.
+
+
The idea of giving back through DevOpsDays and other conferences is fueled by the recognition that we can use our very privileged status to help those in need. The implications have the potential to be felt globally and a rising tide lifts all boats so everyone stands to benefit.
+
+
We hope that if conferences can adopt some of the principles below, it will not only help the targets of that help, but also raise awareness within our own community of the plight of others, the impact we can have, and increase our diversity and understanding of the benefits of diversity which will help everyone.
+
+
Methods
+
+
There are several ways for organizers and attendees to give back. What follows is a list of possible ways of doing that.
+
+
But don’t limit yourselves --- as a Devopsdays organizer --- to the list below. Other ways of contributing are suitable too. It’s not bad to ask yourself the question how you can maximise number of people who benefit of the conference. Inside and outside our communities.
+
+
Direct attendee commitment
+
+
+
Instead of giving each attendee a conference t-shirt, use that money for a donation. An alternative could be to let attendees choose: take the t-shirt, or allow that money to be donated - this decision would need to be made before the t-shirts were produced, of course.
+
Provide a 'charity table'. A local charity can then install themselves in the sponsor area and try to raise money/recruit volunteers that way.
+
Let attendees bring canned foods which can be donated to the local food bank. An alternative could be clothes which can be donated too.
+
Some charities need manual work. Putting things in bags or boxes (e.g. rice, pasta). Provide a space during open spaces for attendees to help with that.
+
+
+
Indirect attendee commitment
+
+
By leveraging the attendee or sponsor fees time or space can be used to engage the attendees.
+
+
+
Let a charity give a short pitch so their work is visible.
+
Reach out to the local community and sponsor a person from a community underrepresented in tech to attend the conference.
+
Provide scholarships for local or foreign students, NGOs, non-profits, etc.
diff --git a/exampleSite/content/page/events.md b/exampleSite/content/page/events.md
new file mode 100644
index 000000000..dbb3ad2ba
--- /dev/null
+++ b/exampleSite/content/page/events.md
@@ -0,0 +1,11 @@
++++
+date = "2015-11-29T00:00:00-06:00"
+title = "devopsdays events"
+type = "events-list"
+aliases = ["/calendar", "/events/calendar", "/devops-calendar", "/presentations"]
+
++++
+
+Learn how to [organize your own devopsdays event](/pages/organizing)!
+
+After each event, local organizers link to the slides and videos from their event; check individual event program pages for more info. The [devopsdays vimeo account](https://vimeo.com/devopsdays/albums) contains many videos from past events.
diff --git a/exampleSite/content/page/ignite-talks-format.md b/exampleSite/content/page/ignite-talks-format.md
new file mode 100644
index 000000000..4f8ae6efc
--- /dev/null
+++ b/exampleSite/content/page/ignite-talks-format.md
@@ -0,0 +1,17 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2016-04-14T11:33:39-05:00"
+title = "Devopsdays - ignite talks format"
+aliases = ["/pages/ignite-talks-format/"]
+
++++
+
+If you have a strong devops-related message that you really want to share with the DevOps world, we encourage you to send us a proposal for an Ignite presentation.
+
+These are 5 minute talks with 20 slides which auto-advance. If you aren't familiar with the format, good examples can be found at [http://igniteshow.com/](http://igniteshow.com)
+
+Tell us about tools, processes, tips, tricks, war stories, whatever... make us laugh, make us cry, show us how to be more awesome...
+
+The only rule is don't give a straight sales pitch. That's not even a rule we'll enforce, everyone will just think you are uncool... that is punishment enough.
diff --git a/exampleSite/content/page/open-space-format.md b/exampleSite/content/page/open-space-format.md
new file mode 100644
index 000000000..78d8baccf
--- /dev/null
+++ b/exampleSite/content/page/open-space-format.md
@@ -0,0 +1,66 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2016-04-14T11:28:51-05:00"
+title = "Devopsdays - openspace concept"
+aliases = ["/pages/open-space-format/"]
+
+
++++
+
+
Open space is the simplest meeting format that could possibly work.
+
+ It is based on (un)common sense of what people do naturally in productive meetings.
+
+Principles (from Wikipedia on Open_Space_Technology):
+
While the mechanics of Open Space provide a simple means to self-organize, it is the underlying principles that make it effective both for meetings and as a guidepost for individual and collective effectiveness.
+
+The Law of Two Feet — a foot of passion and a foot of responsibility — expresses the core idea of taking responsibility for what you love. In practical terms, the law says that if you’re neither contributing nor getting value where you are, use your two feet (or available form of mobility) and go somewhere where you can. It is also a reminder to stand up for your passion.
+
+From the law flow four principles:
+
+
Whoever comes is the right people
+
Whatever happens is the only thing that could have
+
Whenever it starts is the right time
+
When it’s over, it’s over
+
+
+The open space rallying cry is:
+
+
+
+Open Space Mechanics
+
+Since the meeting is supposed to be self-organizing, the conveners put their energy not in running the meeting but creating a setting that gets everyone’s creative energy flowing.
+
+Opening:
+
+
Show the timeline, how the event breaks down into Opening, Marketplace of ideas, Break-out sessions, Closing.
+
Sponsor introduces the theme. Briefly. One or two minutes max. Long openings drain the energy of the meeting quickly. Get participants to work ASAP.
+
Facilitators introduce the principles and the format. Explain how the marketplace of ideas works.
+
+Marketplace of ideas:
+
+
Participants write ‘issues’ on pieces of paper. Preferably with bold markers, so they are easy to read from a distance.
+
Participants choose a timeslot for their topic on the agenda wall.
+
One by one, participants explain their issue to the others, with the aim of drawing the right people to their break-out-session.
+
+Break-out sessions:
+Once people do not come up with new issues (wait a little bit, and ask ‘are we done?’. I find the silence that often happens at the beginning and end of the marketplace the scariest. However, this silence seems to be very productive.
+
+You may ask people to put their name on sessions they want to attend. More than one session per slot is OK… (law of two feet ). This gives conveners an idea of how busy their session is going to be. It gives participants an image of how the break-out session is going.
+
+People may shuffle sessions around, or merge sessions as they are deciding where to go. Have a wiki where people can record outcomes of sessions, or provide paper forms for note-taking during sessions (recording who attended, a summary of the session and outcomes/questions for further work) that you can collect into a ‘book of proceedings’.
+
+The facilitators’ role in this bit of the conference is to answer questions, and make sure everyone has the materials they need to run their break-out session. They do not (in principle) intervene in the sessions - the participants are supposed to self-organize.
+
+Closing:
+Have everyone back in the circle. A simple and effective way to close is to have the participants pass a ‘talking stick’ around, and let them (briefly, e.g. in a sentence or a word) say what they feel about the day.
+
+Bumblebees and butterflies:
+Bumblebees internalize the law of two feet quickly, and constantly flit from meeting to meeting, pollinating, cross-fertilizing, and adding richness and variety.
+
+Butterflies may never get into any meeting. They are focal points of quiet and beauty. If you watch them, every once in a while you'll see them engage in conversation. Those conversations often are significant.
+
+(from Pono consultants)
diff --git a/exampleSite/content/page/organizing.md b/exampleSite/content/page/organizing.md
new file mode 100644
index 000000000..09ce5c5ea
--- /dev/null
+++ b/exampleSite/content/page/organizing.md
@@ -0,0 +1,522 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2015-11-22T01:21:47-06:00"
+title = "Devopsdays - Organizing Guide"
+aliases = ["/pages/organizing/"]
++++
+
+---
+
+## Introduction
+Congratulations! The fact that you have reached this page means you at least have an interest in spreading the devops love to the world. Back in 2009 when we organized the first event, we were probably as excited as you are now. But we were also bit scared and full of questions: how does this work? how do we get sponsors? what is the first thing we have to do?
+
+Years later, we can offer some advice from our experiences. Even though every event is a bit unique in its own way, we've come to a more or less standard approach for organizing these events. With this document we want to support you and make you feel at ease in organizing one yourself. Don't worry; we'll be there along the way!
+
+We recommend that at least one person on your team attend another devopsdays first, and then get in touch with the [core organizers](/contact) to tell us about where you'd like to organize your own!
+
+---
+
+## Assembling a team
+
+In the devops spirit of collaboration, find people in your region that want to help you run the next awesome event.
+
+- Talk to people at your local devops or related community meetups.
+- Tweet that you'd be interested in running one in your region. (Use the #devopsdays hashtag.)
+- [Email the global core organizers](mailto:info@devopsdays.org) and we'll try to connect you to other people in your region
+
+You're going to need people from different organizations on your local organizing team, so you have a broader base of support and involvement from the community.
+
+---
+
+## Website, Email, and Slack
+
+When you have your initial team, [email the global core organizers](mailto:info@devopsdays.org) and we'll schedule a kickoff meeting with you. After chatting, we'll set up the @devopsdays.org mail aliases for your team. This will let you have a standard email for organizer contact and proposals. We'll also invite you to the Slack team so you can meet other organizers and share ideas. (Slack has an XMPP gateway if you'd prefer that.)
+
+We prefer the city name for the actual email and site. Wider regional terms are less preferable since someone in a nearby city may want to have a devopsdays in a following year. Fun nicknames require too much dereferencing of pointers and so are best kept for slogans and t-shirt designs.
+
+One thing you'll want to do as soon as possible is get your event listed on the website by submitting a pull request to https://github.com/devopsdays/devopsdays-web. The most up-to-date instructions can always be found on that repo's [README](https://github.com/devopsdays/devopsdays-web/blob/master/README.md).
+
+It's fine if you just list the organizers, the city, and say "coming soon". You don't have to have the date & venue set or open registration & the CFP right away.
+
+The [devopsdays code of conduct](/conduct) is based on the one from the [Geek Feminism Wiki](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) as well additions by Andrew Clay Shafer for [devopsdaysPGH 2014](/events/2014-pittsburgh/conduct/). You will need to have a code of conduct before your initial pull request will be merged.
+
+---
+
+## Rules
+
+Every devopsdays event is different, but there are a few rules to keep in mind if you'd like your event to be listed on devopsdays.org:
+
+- Inclusiveness and respect for differences are core devops values, and we invite you to help us make each devopsdays event a place that is welcoming and respectful to all participants. Your event will need to have a code of conduct.
+- These are community events, so your event must have an open call for proposals and accept registrations from the general public. Internal devops events focused on a specific organization or curated events with all speakers privately selected are wonderful and we encourage them, but they won't be listed as "devopsdays" events on this site.
+- These events are not for individual or corporate profit. If you have money left over, you can use it for your next event, to help other devopsdays events directly or via sending participants, or for [charity](/devops-gives-back/). The global core team does not have any ability to accept your money, but neither should it be making its way into anyone's pockets.
+- Sponsors are much appreciated for their financial assistance, and they are welcome to participate in devopsdays events. They are never given attendee contact info by a devopsdays event's organizers, nor are they allowed to purchase speaking slots for talks or ignites at a devopsdays.
+
+---
+
+## Handling Money
+
+Part of organizing the event is handling of the local event's money. This will be needed for:
+
+- Invoicing sponsors and accepting their payments.
+- Accepting money from and (as needed) sending official invoices to people that register
+- Paying suppliers like the venue, catering, T-shirts, etc.
+
+You cannot announce a date until you know you have a way to handle money. Realizing too late that you cannot process money has led to rescheduled or canceled events in the past.
+
+The way many events have handled this is to find a local company that is willing to handle these logistics. In some countries, a local company is the only way to handle taxes. Some events register a local not-for-profit entity; there is no such central entity.
+
+Depending on the size of the event, you might want to give them a Silver or Gold sponsorship in return. Make sure they understand they will need to generate invoices and accept/make payments with a fast turn-around.
+
+If a local company is not an option, we've worked with a few companies in the past that are willing to help you for a fee:
+
+- US Based: Laura from Conference Ops
+- EU Based: Bernd from Netways
+
+If you would like to use this method, contact us to get more details.
+
+To make invoicing smooth, it helps to use that company's paypal account for registration (on eventbrite or equivalent) and to use paypal (or equivalent) buttons generated by them for sponsor packages.
+
+---
+
+## Selecting a date
+
+Now that you have assembled your team, the next step is choosing a date. We usually take the following into consideration to find a good date:
+
+- Avoid overlapping dates with other devopsdays, especially nearby. We want to spread the events out; think of it as loadbalancing. All devopsdays events with their dates scheduled will be shown on the front page of [devopsdays.org](/).
+- Avoid overlap in dates with other important local events: with other events happening at the same time, your attendance rate might be affected negatively
+- 'Piggyback' after/before other events: it's a great way to get started, and as people might have traveled already, they can be potentially be interested in a pre or post event conference
+- Take a look at the [devops conferences site](http://devopsconferences.org/) so as to avoid accidentally scheduling during a time it may be more challenging to get the speakers and sponsors you want.
+- You cannot announce a date until you have two things: an agreement with a venue, and a way to handle money.
+- Look at a few two-day choices you can accept. When talking to a venue, you might find that they can accommodate you better during some parts of the week than others. Sometimes they may be fully booked a given week, but available the next.
+- Consider that if you schedule one or more day on a weekend, you are likely to see a significant drop-off of attendance on the weekend day(s). DevOps is part of people's work life, and the weekends are typically used for refreshing energy with family. We recommend choosing weekdays.
+
+---
+
+## Budgeting
+
+Your budget is going to be refined and adjusted as you determine how many attendees you think you'll get and how much you're going to commit to spending up-front. You're not going to know all these numbers immediately, but it's valuable to start thinking about them as you're choosing a venue.
+
+Categories to consider:
+
+Income:
+
+- Sponsors (could be up to 75% of your income, depending on sponsorship levels)
+- Registrations (make sure to set this such that you're covering per-attendee costs)
+
+Expenses:
+
+- Venue for talks & open space discussions
+- Internet for attendees
+- Livestream/recording of talks
+- Catering for breakfast/coffee breaks/lunches (some venues require the use of their caterer)
+- Evening event
+- T-shirts/other swag
+- Badges/lanyards
+- Signage
+- Speakers dinner
+- Speaker gifts (small token)
+- Insurance/taxes
+- Payment for accounting services
+
+---
+
+## Selecting a venue
+
+When you have some idea of when you want to run and how much you want to spend, you can start talking to potential venues.
+
+Venue space considerations:
+
+- A (big) room where everybody can sit comfortably and listen to the talks. This of course depends on the number of attendees you expect. Events have ranged from 70 to 700 people. Assess the numbers usually attending your best-attended local meetups; you might get 2-3x that.
+- A number of break-out rooms for the afternoon sessions:
+ - it's nice to be able to put the chairs in a circle for better discussions
+ - you can be creative by splitting the big room in smaller rooms but in practice, separate rooms are less noisy
+ - we usually go for a few smaller (10-20) and few bigger (20-40) rooms
+ - it's helpful if the rooms are close to one another, making it easier to move between open space rooms.
+ - you can use the big room for open space too
+- Room to hang out: not everybody attends sessions, and some are more interested in the hallway track. If there is some room for the food or a quiet room that's a plus.
+- Sponsor space: Gold sponsors (at a minimum) get a table to have a presence. Make sure they have a nice spot at the event (typically close to the food or hangout space).
+
+Aside from having enough space, there are other things to consider:
+
+- Is the venue easily reachable by public transit and/or does it have sufficient parking, depending on the transit options in your local area?
+- Are there (affordable) hotel accommodations nearby? (Running the event in a hotel makes it easy for out-of-town guests.)
+- Does the venue allow for catering by other parties, or what are the options for food?
+- Does the venue have enough wifi/internet capacity, or can more be added? Attendees will likely expect it.
+- Can the video be streamed with enough capacity (if livestreaming is an option)?
+
+A final big space differentiator is the pricing: as the price of devopsdays is typically relatively low, we look for affordable venue space:
+
+- looking for (free) innovation centers or educational venues (universities...)
+- finding local companies that can act as a host with their facilities
+- finding a host sponsor that is willing to pay for a venue for you
+
+Don't overcommit on the number of people coming and don't do a pre-payment for the venue until you must. The same goes for food: it's always easier to add a few extra plates as opposed to having too much food ordered.
+
+If you have some legal entity created for the event, have the details at hand (legal name, contact details, business number etc.). Some venues may require this information to put in a hold for your chosen date(s).
+
+---
+
+## Designing a local event's devopsdays logo
+
+The devopsdays logo with the gears in the brain has become recognizable for the overall devopsdays brand. For each individual devopsdays event you can take elements from the devopsdays brand logo. This is optional, but recommended. The goal should be to design something that denotes your city specifically.
+
+Note different existing logos:
+
+- [Seattle 2016 - Needle using the gears with a backdrop of mountains](https://www.devopsdays.org/events/2016-seattle/logo.png)
+- [Chicago 2016 - A local take on the gears in the brain](https://www.devopsdays.org/events/2016-chicago/logo.png)
+- [Cape Town 2016 - The characteristic Table Mountain skyline, using the gears](https://www.devopsdays.org/events/2016-capetown/logo.png)
+
+A simple exercise to do with your organizers would be to ask for one word descriptions of your city and then review and vote on the list.
+
+---
+
+## Announce your event
+
+Once you have a time and place, you can announce your event to the world! It's great if you've had a chance to open your CFP and registration, though those aren't essential to announce your dates.
+
+### Website
+
+Update your data file for your event to add your start & end dates; this adds your event to the map on the front page!
+
+### Twitter
+
+Tweet with the hashtag #devopsdays and if desired, set up an event-specific Twitter account such as @devopsdaysmsp. If you PR your event Twitter handle onto your site, your tweets will be included in the Twitter feed on devopsdays.org.
+
+---
+
+## Distributing the work
+
+On your local organizing team, it's best to discuss the following tasks. Of course this is not set in stone, but it helps for people to focus on different areas.
+
+- Person/Pair handling talk proposals
+- Person/Pair handling ignite proposals
+- Person/Pair handling website updates
+- Person/Pair handling sponsors
+- Person/Pair handling registration, invoicing, questions
+- Person/Pair handling venue, catering, local things, hotel
+- Person/Pair handling t-shirts
+- Person/Pair handling evening event logistics
+
+---
+
+## Call for proposals
+
+When you're ready to open your call for proposals, you'll want to include the date it opens, the date it closes, and the date by which people will be informed of your decisions. People will usually need at least 4-6 weeks to arrange for travel or time off, and you'll want your call to be open for at least a month, and you'll want at least 2 weeks to consider proposals and fill in any gaps. This means that you should open your CFP as soon as possible, and close it at least 6-8 weeks before your event.
+
+Set an official theme if one beyond "devops" is desired. Within the context of this theme (but other proposals can work too):
+
+- **no speaker spots can be bought by sponsors: not ever - period.**
+- encourage new content: if the content has already been presented/published online we will consider it but it's less attractive. We want to stimulate the creation of new content as much as we can, as part of the goal is to record and spread the ideas from these sessions
+- a good balance between local and out-of-town speakers. building the local community is just as important as bringing in new ideas from the wider community.
+- favor new speakers: devopsdays is a supportive environment to encourage new voices in our space
+- encourage bold subjects: we don't want to hear the same things over and over, do we? This avoids us becoming an echo-chamber of ideas
+- shy away from specific technology/product talks: always try to elevate it to the conceptual part
+balance between technical and cultural content: for specific tools talk, there are open spaces not the main conference talks
+
+Events usually have 4 30-min talks per day + ignite talks. Open space sessions are scheduled during the conference, not ahead of time.
+
+For people to respond to the call for proposals we create a specific address (proposals-yourlocation-year@devopsdays.org). You can also use a third-party CFP tool.
+
+Keep in mind that under-represented people in tech are much less likely to respond to your CFP. If you would like to encourage diverse viewpoints from voices other than those you hear the most often, you will need to reach out into those communities and encourage participation.
+
+Talk selection doesn't have to be finished when you announce a schedule; it's ok to leave to space until the end. Still, we found that a finished schedule helps for attendees to make the case for them to attend. Remember that announcing only a few speakers can lead to unwarranted assumptions about your demographics.
+
+Don't be surprised if proposals don't flow in quickly at first. People usually wait a bit before sending them in and need some extra calls. It's good to have a backup plan and contact individual speakers as well. You're not required to create your schedule solely from responses to your CFP. You should also provide speaker support according to your budget; at a minimum, all speakers should receive a free event ticket.
+
+It works best if you dedicate a person/pair to respond to proposals/speakers and handle communication. This is best for both ignite and conference talks. While your local team is going to select your event's talks, the core organizers may weigh in to help you make a more balanced schedule having less overlap with other devopsdays.
+
+---
+
+## Sponsorship packages
+
+Overall [guidelines for sponsorship](http://www.devopsdays.org/sponsor/) are available. Sponsor packages are decided upon by the local organizing team for a city. The global core team does not offer sponsor packages, so any sponsors will work directly with the devopsdays event(s) they'd like to sponsor. You can use the examples in the template to help you make your decisions. Here are some typical offerings:
+
+- Host (cost of venue): if a company sponsors the venue/food they will be acknowledged as a Host sponsor. Their logo will be directly visible on the main event page. They also have the opportunity to do a pre/post event meetup that will get promoted. And of course they get the same benefits as Gold and Silver sponsors
+- Gold (around 5000 Euro/USD): 6 included tickets + a 'promo' spot during talk intermissions + the ability to have a simple table/sponsor presence at the venue.
+- Silver (around 3000 Euro/USD): 4 included tickets, sometimes half a table depending on the local event's choices, sometimes just a single shared swag table.
+- Bronze (around 1000 Euro/USD): 2 included tickets, sometimes can leave stickers/flyers/etc in public spaces
+- Community Sponsor: get logo on the site and acknowledgement on social media. Used for media outlets and other conferences that are interested in cross-promotion with you. Sometimes they'll provide giveaways; usually you will not ask them to provide cash.
+
+We want to avoid the traditional high-priced model for sponsors. We believe that the more companies that sponsor, the better: it amplifies the ideas and shows that many companies subscribe to the devops idea.
+
+We believe the pricing is low compared to the value sponsors get compared to what other conferences are charging. Also, you may want to refrain from deviations from the standard package. Exceptions take extra CPU cycles. Best to be avoided.
+
+Other offerings might be:
+
+- A lanyard sponsor
+- An evening event sponsor
+- A lunch or breaks sponsor
+
+As a reminder:
+
+- we do NOT offer speaker slots in return for sponsorship, and we want to maintain a standard policy on the pricing inside a given event.
+- we do NOT ever sell contact details of attendees. You can share demographics in aggregate to give sponsors a feel for what kind of crowd will attend.
+
+---
+
+## Finding/Handling Sponsors
+
+Sponsors pay the bills. You rely on them. So what can you do to find them and keep them satisfied?
+
+- post on Twitter and other social media
+- find local meetups/companies that can help you
+- if you're looking for a contact of a specific company that sponsored before, ping the devopsdays core organizers to see if they can help.
+- talk to the other organizers on Slack - many of them work at sponsors!
+- write a blog on the website to promote your event.
+
+Sponsors will usually ask you the following; best to have this information ready.
+
+- Projected number of attendees
+- Industries/Companies represented (share only in aggregate)
+- What they get with what level of sponsorship (refer them to your sponsor page)
+- If they can buy a speaker spot (NO, but they can submit a talk, ignite or open space topic)
+- If you provide a badge-scanning mechanism (no)
+- If they will have electricity & network at the venue
+- If they can get a monitor (let them bring their own or rent one themselves)
+- Where to ship their stuff and pick it up (don't take responsibility and let them handle that directly with venue)
+- What size of table they have? Find out from the venue and say it has to fit behind the one table
+- Where their table will be located (produce a map and let them choose in the order they signed up)
+
+From experience, we found that it helps to have a single local organizer act as the contact with the sponsors to track prospects, payment, and giving them discount codes.
+
+When they sponsor they need to supply:
+
+- a logo for the website
+- a URL to link it to
+- an email address of a contact you can reach
+- a Twitter handle for you to thank (optionally)
+- the invoice details (including VAT in Europe)
+
+In return you'll :
+
+- put the logo online
+- link it on the website
+- send the official invoice (as applicable)
+- once payment has been received, provide the registration discount code
+
+On the registration page, have them select the special sponsor ticket with their discount. Many of the sponsor contacts are traveling from event to event, you'll have to follow up with them a bit so they sign up their crew in time for your badge printing. Make sure you make the invoices "due on receipt" or provide Paypal links so sponsors don't wait months to pay you.
+
+
+---
+
+## Tickets and pricing
+
+We want to ensure that anyone who's interested in attending a devopsdays is able to, and that price is not a barrier. So, you'll want to keep your prices relatively low compared to many industry conferences.
+
+### Free registration
+
+Experience has taught us that 'free' events come with a cost:
+
+- about 30-40% of the people 'grabbing' a free ticket don't show up in the end
+- this makes it harder to plan logistically: how many people will actually show up?
+- people who could have attended are left out because the event appears 'full'
+
+### Minimal Cost
+
+Asking a minimal fee (covering about food cost for two days - about 100USD or 100 Euro) gives us the best of both worlds:
+
+- The numbers are more accurate that way and more people feel happy about it.
+- The financial risk for venue/catering cost is spread
+
+The downside is that this will require 'official' invoices:
+
+- It requires time to create the invoices (although it's pretty much automated if you use [http://eventbrite.com](http://eventbrite.com))
+- It might cost some accounting time because of the administration
+- Specifically in the EU region:
+ - if a EU company organizes an event in another country, it will have to request a Tax-ID in that other country. The costs of doing that would take a significant portion of the event money.
+ - charges for the event needs to be in the currency of the country where the event will take place
+
+Bottom line: if you want to charge a fee (which gives you better financial protection), make sure you have considered that in your handling of the money.
+
+To encourage people to register early it's advised to offer discounted **early-bird** registration.
+
+Because getting time away from work may already be a barrier for under-represented people in tech, offering free tickets to those individuals may make it more possible for them to secure workplace buy-in on their participation. If your budget has room, this is a good place to spend some of the extra money. Be sure you comply with all local laws that may apply in regards to demographic information and the uses thereof.
+
+---
+
+## Setting up registration
+
+Once pricing has been decided you're ready to set up registration. We've had good experiences with [Eventbrite](http://www.eventbrite.com) integrated with [PayPal](http://paypal.com) payments. The paypal account for payment needs to be linked directly to the company that does the invoicing.
+(Note: if using Eventbrite, use Paypal, not "Eventbrite payment processing", or you'll have to wait for Eventbrite to disperse funds after your event.)
+
+The core organizers will not run registration for you, but we can suggest things that will be useful to you in your registration process.
+
+Specifically on eventbrite we usually:
+
+- ask for employer name (optional) if people want it printed on their badge
+- ask for Twitter handle (optional) to help attendees connect with one another
+- ask for T-shirt sizes (make sure you offer more than S-M-L-XL "unisex")
+- (in Europe) ask if they require an invoice; if yes ask more details like VAT number if needed
+- ask if they are interested in attending the evening event on the first night (optionally)
+- disable the facebook integration
+- don't allow people to see who is coming
+- set up hidden ticket types for sponsors, organizers, speakers, etc
+- create access codes for hidden ticket types
+
+*Attendee email or direct-contact information should never be visible on the website or given out to vendors.* We value privacy and anti-spam a lot!
+
+---
+
+## Setting your program
+
+We recommend a two day single-track program with the following structure:
+
+- talks in the morning: this follows the traditional format of a speaker or panel
+- There is usually an introduction of about 15 minutes at the beginning of the conference from the organizers
+- We find that talks of about 30 minutes have the right balance for content.
+- You'll want to let the Gold sponsors speak for a minute between the 30-minute talks as that gives presenters time to set up their laptops
+- allow for rest and discussion breaks
+- You may break for lunch before the Ignite talks if that works best for your schedule.
+- You'll have a set of several ignite talks: 5 minute talks with 20 slides that auto-advance (More detail on Ignite format)
+- openspaces in the afternoon: a self-organizing part where everybody gets to propose a session (More detail on OpenSpace Format)
+
+We provide a sample schedule in the event template.
+
+You can usually draw on different sources to get speakers:
+
+- the call for proposals
+- ask on Twitter for people to retweet your CFP announcement
+- reach out to local meetups and organizations
+- contact desired speakers directly
+
+A few words of advice:
+
+- No sponsor should be able to buy their way into the program. The schedule should be decided by your local organizers.
+- Usually you will receive more tools talks vs cultural talks. We believe it's important to keep the balance right.
+- Tool talks should be at the conceptual level, not at the individual day-to-day level
+- We prefer new speakers to come on board
+- We prefer new content that was not presented yet (or was already recorded)
+- Avoid inviting only prominent out-of-town speakers; we need to make sure that local content/ideas get picked up and spread to the community
+
+---
+
+## T-shirts and other swag
+
+Printing shirts is entirely optional. Some events choose to donate to charity instead, while others go with a different kind of swag. If you decide to do shirts, bear in mind that at registration time, attendees can help you know what their body shapes and sizes mean for their preferences. Ask! Do not just guess, or you will find you've inadvertently made some attendees feel excluded.
+
+While some shirt styles only go to 2XL, there will be attendees who (given the option) will choose 3XL, 4XL, or 5XL. Women will sometimes be happier with a fitted shirt (which is not the same as a "girl" shirt - those are typically a "junior" size). Avoid making your extended sizes and your fitted shirts significantly different from the "S-2XL unisex" shirt in color or design.
+
+Keep in mind that you want your design to be appealing on a wide range of humans, not just those who happen to have smaller torsos without many curves. If you want soft, comfortable shirts that can fit many people, consider something like a tri-blend instead of a 100% cotton shirt.
+
+If you're ordering shirts a few weeks before your event, consider padding the counts by up to 30% of each size/style. Having a few extra shirts is way better than anyone going home sad.
+
+You may also want to order stickers or other items. Give yourself plenty of lead time.
+
+---
+
+## A word on hotels
+
+There will almost certainly be a few speakers and sponsors who will travel to your event and will appreciate having a discounted rate at the most conveniently located affordable hotel you can manage.
+
+If you're holding your event in a hotel, they will likely give you a "courtesy" room block that guarantees a discounted rate for your attendees.
+
+If you're not using the hotel's meeting rooms and catering, they may want you to guarantee at least 80% or so of the room nights you block off for your group will be used. This isn't as risky as it sounds if you want to start with a very small block (5 rooms or so, for the night before day one and the night between day one and day two - don't expect people to stay overnight the evening of day two). Usually the hotel will also let you add more rooms to the block as it fills.
+
+If you make your group rate code available on your website, keep on eye on who registers with it (the hotel should be able to provide this info), and ensure that you have enough space for all the out-of-town people you expect. You may have to remind some people to register, as the group rate usually expires a month or so before an event.
+
+---
+
+## Venue logistics
+
+You will want a local organizer acting as the primary contact person with the venue. You will need to arrange things like the chair layout, table arrangement, audio-visual needs, etc. The catering deadline (by which time you'll need to provide numbers) is usually a couple weeks or so before your event.
+
+Make sure you ask the venue how soon sponsors can start shipping items there, get the correct address/routing info, and ask what fees they might incur. Find out exact times you'll have access to your space, and find out whether you'll have secure overnight storage (because both you and definitely the sponsors will need that).
+
+Your venue may require some form of insurance. See what they require, and look into something like TULIP event insurance depending on what's available for your local area.
+
+You will want some members of your local organizing team to be tasked with...
+
+- finalizing venue details
+- running the registration check-in desk
+- preparing and posting signs
+- printing and assembling badges
+- etc.
+
+---
+
+## Evening event
+
+Most devopsdays host a social gathering the evening after the first day of the two-day event. This is a great place for attendees to get to know one another better. There's some sort of food and drink, but usually a full dinner is not provided. Having fun activities to participate in (bowling, trivia, other games, etc) is recommended. While alcohol is enjoyable, it should not be the only activity, and it's important to remember the needs of attendees who aren't choosing to drink alcohol. It's also not required for your event to pay for any alcohol; if it's not free, it is more socially acceptable to refrain from choosing it.
+
+Often the evening event will be at a different location than the venue for the talks. It's a good idea to make it within walking distance or provide transportation if possible. Running it at the same venue can lead to higher attendance, especially if you provide some content such as the Ignite talks.
+
+Offering a family-inclusive evening event will allow more people to participate; unlike at a destination conference, many local devopsdays events occur within commuting distance. While people who work outside the home typically have a daycare arrangement in place, it probably does not extend into the evening.
+
+---
+
+## Running registration
+
+You are going to want a place where people can check in and get their badges when they arrive. They may also pick up T-shirts there. If you use Eventbrite, there is an app which makes check-in much easier than using paper, but it may not be necessary to do more than just give the badges out (as you can see which ones are left at the end.) Sort the badges ahead of time alphabetical by last, then first name. If you separate out the sponsor ones, keep in mind that some people might not realize if they fell into the "sponsor" tickets or a "regular attendee" ticket according to how their company registered them.
+
+Sort shirts by style and size, and then let attendees just tell you which size they wanted. If you built in enough margin of error, this won't cause any problems and will be the most efficient way to deal with it, rather than looking up what they ordered.
+
+You may want to staff the registration desk at all times if you want to be able to help attendees with their questions. As the conference organizers may want to attend talks, it's wise to call in favors from friends and family who aren't interested in the subject matter of the talks and won't mind missing them all. Make sure any such staff have a way of getting ahold of the organizer on duty for any questions they can't answer on their own.
+
+---
+
+## Video - recording and streaming
+
+Whether or not you're able to livestream, it's important to record all the talks. This is invaluable for your speakers, and it's great for the community. Your audiovisual company should be able to provide a camera or cameras and record the feed off the board into a computer. If you have no budget for recording talks, a smartphone is better than nothing.
+
+If you're going to livestream, rehearse ahead of time, and then assign at least one person to run it during the event.
+
+- For past events we have used [livestream](https://new.livestream.com/live-video-tools#mobile-broadcasting). The software can be installed on Windows or OS X.
+- You may need [producer software](https://new.livestream.com/producer/software).
+- You can create a free account at livestream to experiment. Create it as **new.livestream.com** and NOT at livestream.com.
+- We have mainly used it on a Mac; there, it will read any video device supported and record it both on your local computer + stream.
+- Find out if you can hook up your camera equipment directly to a computer and have the software detect it.
+
+---
+
+## Running the event itself
+
+- Prepare and share a team playbook of exactly what is scripted to happen when.
+ - Assign one or more MCs to kick off and orchestrate the event
+ - Assign people to introduce specific speakers
+- Consider assigning "on duty" shifts so one person isn't the SPOF for all last-minute decision-making in crisis mode
+
+---
+
+## Running Ignites
+
+Running Ignites can be a challenge: people tend to submit them last minute, or they didn't understand the format too well. Here are few tips on making this process run more smoothly:
+
+- Require the Ignite presenters to send the slides ahead of time
+- Inform the Ignite presenters that there are no presenter notes during their talks
+- Animations (gifs or slide transitions) and videos may not work due to the conversion process
+- PDF is the easiest format to collect all presentations
+ - An option is to use a Dropbox shared directory
+- You can run either :
+ - `impressive -a 15` [http://impressive.sourceforge.net/](http://impressive.sourceforge.net/)
+ - Adobe Acrobat Reader in [auto-advance mode](http://malektips.com/adobe_reader_7_0019.html); ask presenters to add empty slide to the end as Reader doesn't exit after last slide
+- Don't let them run on their own laptops
+- Use a dedicated laptop (avoid any popups etc...)
+- Mention again on the day itself.
+ - "Just so you know, your slides will auto advance every 15 seconds; you can't advance them yourself"
+ - Remind the presenters again that there are no presenter notes
+- Have Ignite presenters queue next to the stage and either:
+ -start the slidedeck for them.
+ - or even build all slides in Slidedeck and build in a bio slide as a interludium and have that autoadvance as well
+
+[Ignite format page](/ignite-talks-format/)
+
+---
+
+## Running Open Space
+
+There is a wealth of detail on the [Open Space format page](/open-space-format/). Consider both a physical schedule grid and an easily-updated shared spreadsheet you can link from your event page. Also consider posting the open space choices for a specific room outside that room.
+
+---
+
+## Website updates
+
+- The core organizers want the devopsdays website to be a central reference for all content produced during your event.
+ - Embed links to each of your speakers' slides on your program page. (Ask them to post slides on slideshare, speakerdeck, etc.)
+ - Upload the videos to youtube or your video site of choice, then embed them on your program page.
+- Surveying your attendees and blogging about the results is optional, but strongly recommended.
+
+---
+
+If you have further questions, chat with the other organizers on Slack, and have fun! It's going to be great!
diff --git a/exampleSite/content/page/privacy.md b/exampleSite/content/page/privacy.md
new file mode 100644
index 000000000..8e8d29b95
--- /dev/null
+++ b/exampleSite/content/page/privacy.md
@@ -0,0 +1,10 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2016-08-19T18:40:18-05:00"
+title = "Privacy Policy"
+
++++
+
+{{< privacy_policy >}}
diff --git a/exampleSite/content/page/speaking.md b/exampleSite/content/page/speaking.md
new file mode 100644
index 000000000..d409f9104
--- /dev/null
+++ b/exampleSite/content/page/speaking.md
@@ -0,0 +1,11 @@
++++
+date = "2015-11-29T00:00:00-06:00"
+title = "speaking at devopsdays"
+type = "cfp"
+
++++
+
+The call for participation for a devopsdays event helps each city's local organizers find speakers for their event. Follow the talk proposal submission process for a given city if you'd like to submit an idea to their CFP!
+
+These are the cities which currently have an open call for participation.
+
diff --git a/exampleSite/content/page/sponsor.md b/exampleSite/content/page/sponsor.md
new file mode 100644
index 000000000..cca6dd120
--- /dev/null
+++ b/exampleSite/content/page/sponsor.md
@@ -0,0 +1,57 @@
++++
+Categories = []
+Description = ""
+Tags = []
+Date = "2016-05-03T13:04:25-05:00"
+Title = "Sponsor devopsdays"
+
++++
+
+Devopsdays is a community-organized not-for-profit conference series for practitioners. It began in Ghent, Belgium with one conference in 2009, and has grown to more than 30 events planned worldwide for 2016.
+
+Sponsoring devopsdays conferences gives your organization an opportunity to speak with practitioners, managers, and executives from companies of all sizes and industries. Whether your goals include recruiting new talent, opening new markets, or connecting with your existing customers, this event will be the place to have those conversations with experts and leaders in tech innovation.
+
+
+**Code of Conduct**
+
+All devopsdays events have a code of conduct and require sponsors to follow it. This applies to giveaways, items and images at your table, behavior of your staff, etc. See the specific city's site for the details of their code of conduct.
+
+
+**How to sponsor**
+
+All devopsdays events are independently organized. No multi-city sponsorships are available; when you decide which cities to sponsor, you need to contact each city's organizing team individually.
+
+Events set their own rates and can tell you about their expected attendance in terms of numbers and communities represented. Sometimes they will offer additional special sponsorships for more visibility, such as lanyard, evening event, etc. They typically are charging exactly what they need to run the event; nobody's making any money off these events, so discounts are generally not available.
+
+The vast majority of events do not have a legal tax-deductible status. Most sponsors fund this sponsorship either out of their marketing budget or recruiting budget, depending on their goals for sponsorship. Because these events are organized by volunteers who usually have no legal entity, contracts are generally not used. However, most events employ some form of professional accounting, so you usually have the option of paypal/credit card or invoice followed by check or bank transfer.
+
+
+**Staffing & participation onsite**
+
+Most sponsorship packages include a number of conference tickets for you to send employees. If you're sponsoring at a level which comes with a table presence, you'll need to line up people to staff it. Since traffic at the table is minimal during the single track of talks in the morning, they can attend the talks and then take turns staffing the table versus attending participatory breakout sessions in the afternoon.
+
+Most devopsdays conferences also include an evening networking event, which is a great place for informal continued conversations.
+
+If your goal is recruiting, consider sending engineering managers. If you are a vendor, send your sales engineers as well as your technical product marketing, and even some engineers.
+
+All attendees including sponsors are welcome to propose any subject they would like to discuss in a group, during the afternoon proposals of breakout discussions known as "open space". Sponsors are encouraged to actively participate and engage with the other attendees as peers.
+
+Demos at your table are one good way to show off your org. It's usually possible to bring or rent monitors, though be sure to check with a given event about the exact mechanism at their venue.
+
+You don't need to ship your own booth or tables; devopsdays will provide table and chairs corresponding to your sponsorship level. You'll likely want to ship a table cloth, banner/background, giveaways, etc.
+
+
+**Speaking & Attendee contact info**
+
+Devopsdays does not sell conference speaking slots; sponsors' employees are welcome to submit talk proposals in the same call for proposals as anyone else. The talks are videorecorded and freely available online after the fact, and occasionally livestreamed, which is a great takeaway for the speakers and their orgs. Most events have an opportunity for sponsors to make a short elevator pitch for their services (generally in the order of a minute or two); this makes it to the livestream but usually not into the edited recordings.
+
+Devopsdays does not ever distribute attendee contact information. Do not expect badge scanning of any sort. Most events don't even collect information about job title. _Sometimes_ company affiliation is on the badges, and sometimes it's not.
+
+If you want to collect leads, you'll have to talk directly with individuals and request their contact info. Vendors also often raffle off prizes ranging from large Lego sets to tablets and other desirable items, collecting contact info in the process.
+
+
+**When will a devopsdays conference happen in some specific place?**
+
+New cities start a devopsdays event each year, and some cities run regularly. When planning out your sponsorship budget for the year, it's a good idea to assume that at least one or two must-sponsor devopsdays will crop up after you've already starting reaching out and sponsoring the early announcers.
+
+If one hasn't happened near you, and you wish it would, you can always look into [running your own event](/pages/organizing)!
diff --git a/exampleSite/data/events/2017-charlotte.yml b/exampleSite/data/events/2017-charlotte.yml
index 89a792b53..113481491 100644
--- a/exampleSite/data/events/2017-charlotte.yml
+++ b/exampleSite/data/events/2017-charlotte.yml
@@ -1,7 +1,6 @@
name: "2017-charlotte" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Charlotte" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
@@ -21,10 +20,11 @@ location: "Mint Museum Uptown" # Defaults to city, but you can make it the venue
nav_elements: # List of pages you want to show up in the navigation of your page.
- name: welcome
# - name: program
-# - name: propose
-# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
-# - name: location
-# - name: registration
+ - name: propose
+ url: https://www.papercall.io/dod-clt
+ - name: location
+ - name: agenda
+ - name: registration
- name: sponsor
- name: contact
- name: conduct
@@ -53,10 +53,34 @@ proposal_email: "proposals-charlotte-2017@devopsdays.org" # Put your proposal em
sponsors:
- id: sumologic
level: gold
- - id: thoughtworks-products
- level: gold
+ - id: gocd
+ level: gold
+ - id: opsgenie
+ level: gold
+ - id: pivotal
+ level: gold
+ - id: ns1
+ level: gold
- id: split-software
level: silver
+ - id: netapp
+ level: silver
+ - id: honeycomb
+ level: silver
+ - id: actifio
+ level: silver
+ - id: techtowntraining
+ level: silver
+ - id: victorops
+ level: silver
+ - id: deis
+ level: bronze
+ - id: sonatype
+ level: bronze
+ - id: versionone
+ level: bronze
+ - id: spoken
+ level: bronze
- id: city-of-charlotte
level: community
diff --git a/exampleSite/data/events/2017-chicago.yml b/exampleSite/data/events/2017-chicago.yml
index 4373b4efb..852948f25 100644
--- a/exampleSite/data/events/2017-chicago.yml
+++ b/exampleSite/data/events/2017-chicago.yml
@@ -1,7 +1,6 @@
name: "2017-chicago" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Chicago" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
diff --git a/exampleSite/data/events/2017-dallas.yml b/exampleSite/data/events/2017-dallas.yml
new file mode 100644
index 000000000..3321cd8f8
--- /dev/null
+++ b/exampleSite/data/events/2017-dallas.yml
@@ -0,0 +1,85 @@
+name: "2017-dallas" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Dallas" # The displayed city name of the event. Capitalize it.
+friendly: "2017-dallas" # Four digit year and the city name in lower-case. Don't forget the dash!
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted YYYY-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Dallas / Ft. Worth" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Mike Rosado"
+ twitter: "MikeRosTX"
+ - name: "Michael Hedgpeth"
+ twitter: "michaelhedgpeth"
+ employer: "NCR"
+ - name: "Annie Hedgpeth"
+ twitter: "anniehedgie"
+ employer: "10th Magnitude"
+ - name: "Ben Johnson"
+ twitter: "benjohnson77"
+ employer: "Particle41"
+ - name: "Mark Saum"
+ twitter: "msaum"
+ employer: "Fidelis Consulting"
+ - name: "Jack Teoh"
+ twitter: "jaxteoh"
+ employer: "Alkami Technology"
+ - name: "Gokul Sridharan"
+ twitter: "ConsultGokul_CA"
+ employer: "CA Technologies"
+organizer_email: "organizers-dallas-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-dallas-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: platinum
+ label: Platinum
+ max: 4
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-denver.yml b/exampleSite/data/events/2017-denver.yml
new file mode 100644
index 000000000..78e5a89f4
--- /dev/null
+++ b/exampleSite/data/events/2017-denver.yml
@@ -0,0 +1,50 @@
+name: "2017-denver" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: 2017 # The year of the event. Make sure it is in quotes.
+city: "Denver" # The city name of the event. Capitalize it.
+friendly: "2017-denver" # Four digit year and the city name in lower-case. Don't forget the dash!
+status: "current" # Options are "past" or "current".
+startdate: 2017-04-10 # The start date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+enddate: 2017-04-11 # The end date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+cfp_date_start: 2017-01-13
+cfp_date_end: 2017-02-17
+cfp_date_announce: 2017-03-01
+coordinates: "39.739236, -104.990251" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Denver" # The name of your location
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+ - name: sponsor
+ - name: propose
+ - name: contact
+ - name: conduct
+ - name: location
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Tavis Aitken"
+ - name: "Jason Hand"
+ - name: "Beau Christensen"
+ - name: "Joe Thompson"
+ - name: "Hannah Klemme"
+ - name: "Nick Huanca"
+ - name: "Ryan Koch"
+
+
+organizer_email: "organizers-denver-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-denver-2017@devopsdays.org" # Put your proposal email address here
+sponsors: # List all of your sponsors here along with what level of sponsorship they have.
+ - id: victorops
+ level: social
+
+sponsor_levels: # In this section, list the level of sponsorships and the label to use.
+ - id: social
+ label: Social
+ max: 1
+ - id: lanyard
+ label: Lanyard
+ - id: gold
+ label: Gold
+ - id: silver
+ label: Silver
+ - id: bronze
+ lable: Bronze
diff --git a/exampleSite/data/events/2017-detroit.yml b/exampleSite/data/events/2017-detroit.yml
new file mode 100644
index 000000000..bde2874f0
--- /dev/null
+++ b/exampleSite/data/events/2017-detroit.yml
@@ -0,0 +1,67 @@
+name: "2017-detroit" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Detroit" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+status: "current"
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: 2017-09-27
+enddate: 2017-09-28
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "42.331034, -83.046382" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "A. Alfred Taubman Center for Design Education, College for Creative Studies" # The name of your location
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+ - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: Ben Chess
+ employer: Yelp
+ - name: "Jamie Begin"
+ employer: RightBrain Networks
+ - name: "Brian Nuszkowski"
+ employer: Uber
+ - name: "Joe Arnet"
+ employer: Barracuda Networks
+ - name: "Trevor Smith"
+ - name: "Allison Green"
+organizer_email: "organizers-detroit-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-detroit-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 0
+ - id: silver
+ label: Silver
+ max: 0
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-hartford.yml b/exampleSite/data/events/2017-hartford.yml
new file mode 100644
index 000000000..1f60842cd
--- /dev/null
+++ b/exampleSite/data/events/2017-hartford.yml
@@ -0,0 +1,75 @@
+name: "2017-hartford" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Hartford" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2016-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.763711, -72.685093" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Hartford" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Dave Long"
+ twitter: davejlong
+ employer: "Cage Data, Inc."
+ - name: "Aaron Aldrich"
+ twitter: crayzeigh
+ employer: "Cage Data, Inc."
+ - name: "Scott Russel"
+ twitter: sergeography
+ employer: "Core Informatics"
+ - name: "Jose Andrade"
+ twitter: jandrade
+ employer: "Yale University"
+ - name: Eric Loveland
+ twitter: elovelan
+ - name: Serena Ness
+organizer_email: "organizers-hartford-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "organizers-hartford-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-indianapolis.yml b/exampleSite/data/events/2017-indianapolis.yml
new file mode 100644
index 000000000..d03c03c42
--- /dev/null
+++ b/exampleSite/data/events/2017-indianapolis.yml
@@ -0,0 +1,67 @@
+name: "2017-indianapolis" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Indianapolis" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate:
+enddate:
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Indianapolis" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Byron Schaller"
+ twitter: "byronschaller"
+ - name: "Shane Weinbrecht"
+ twitter: "shizrah"
+ - name: "Rob Nelson"
+ - name: "Andrew Poland"
+ - name: "Greg Swallow"
+organizer_email: "organizers-indianapolis-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-indianapolis-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-london.yml b/exampleSite/data/events/2017-london.yml
new file mode 100644
index 000000000..0ea7213e8
--- /dev/null
+++ b/exampleSite/data/events/2017-london.yml
@@ -0,0 +1,72 @@
+name: "2017-london" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "London" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+#startdate: 2017-04-18
+#enddate: 2017-04-19
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "51.507351, -0.127758" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "London" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "bob walker"
+ twitter: "rjw1"
+ - name: "Dean Wilson"
+ twitter: "unixdaemon"
+ - name: "Paula Kennedy"
+ twitter: "PaulaLKennedy"
+ - name: "Dawn Foster"
+ twitter: "geekygirldawn"
+ - name: "Markos Rendell"
+ twitter: "markosrendell"
+ - name: "Barry Chandler"
+ twitter: "bdc101"
+ - name: "Hannah Foxwell"
+ twitter: "HannahFoxwell"
+organizer_email: "organizers-london-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-london-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-minneapolis.yml b/exampleSite/data/events/2017-minneapolis.yml
index 1fd5a2987..2c4bcea5e 100644
--- a/exampleSite/data/events/2017-minneapolis.yml
+++ b/exampleSite/data/events/2017-minneapolis.yml
@@ -1,14 +1,13 @@
name: "2017-minneapolis"
year: "2017"
city: "Minneapolis"
-status: "current"
startdate: 2017-07-25
enddate: 2017-07-26
-cfp_date_start:
-cfp_date_end:
-cfp_date_announce:
+cfp_date_start: 2016-12-22
+cfp_date_end: 2017-04-09
+cfp_date_announce: 2017-05-07
coordinates: "44.972610,-93.272960"
location: "Minneapolis"
@@ -17,9 +16,9 @@ nav_elements:
- name: welcome
# - name: program
# - name: speakers
-# - name: propose
-# - name: location
-# - name: registration
+ - name: propose
+ - name: location
+ - name: registration
- name: sponsor
- name: contact
- name: conduct
@@ -48,6 +47,14 @@ proposal_email: "proposals-minneapolis-2017@devopsdays.org"
sponsors:
- id: arresteddevops
level: community
+ - id: pivotal
+ level: platinum
+ - id: deis
+ level: silver
+ - id: hackthegap
+ level: community
+ - id: saucelabs
+ level: silver
sponsors_accepted : "yes"
diff --git a/exampleSite/data/events/2017-moscow.yml b/exampleSite/data/events/2017-moscow.yml
index 150804871..667cfc7d0 100644
--- a/exampleSite/data/events/2017-moscow.yml
+++ b/exampleSite/data/events/2017-moscow.yml
@@ -4,12 +4,12 @@ city: "Moscow" # The displayed city name of the event. Capitalize it.
status: "current" # Options are "past" or "current". Use "current" for upcoming.
# All dates are in unquoted 2016-MM-DD, like this: variable: 2016-01-05
-startdate: 2017-02-11 # The start date of your event. Leave blank if you don't have a venue reserved yet.
-enddate: 2017-02-11 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+startdate: 2017-03-11 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2017-03-11 # The end date of your event. Leave blank if you don't have a venue reserved yet.
# Leave CFP dates blank if you don't know yet, or set all three at once.
-cfp_date_start: # start accepting talk proposals.
-cfp_date_end: # close your call for proposals.
-cfp_date_announce: # inform proposers of status
+cfp_date_start: 2016-12-01 # start accepting talk proposals.
+cfp_date_end: 2017-02-17 # close your call for proposals.
+cfp_date_announce: 2017-02-17 # inform proposers of status
# Location
#
@@ -31,21 +31,43 @@ nav_elements: # List of pages you want to show up in the navigation of your page
# These are the same people you have on the mailing list and Slack channel.
team_members: # Name is the only required field for team members.
+ - name: "Alexander Titov"
- name: "Boris Zlobin"
- name: "Michael Krivilev"
- name: "Vitaly Mosin"
+ - name: "Vladimir Turovtsev"
- name: "Vladislav Zavisnov"
- - name: "Alexander Titov"
organizer_email: "organizers-moscow-2017@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-moscow-2016@devopsdays.org" # Put your proposal email address here
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
+# media
+ - id: Express42
+ level: media
+ - id: Logrocon
+ level: media
+ - id: superjob
+ level: media
+ - id: avito
+ level: media
- id: samplesponsorname
level: gold
- id: arresteddevops
- level: community
+ level: media
+ - id: pcweek
+ level: media
+ - id: logo_vox
+ level: media
+ - id: unicraft
+ level: media
+ - id: oktell
+ level: media
+ - id: globalcio
+ level: media
+ - id: hh
+ level: hrsponsor
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
@@ -54,13 +76,18 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
# sponsorship for a specific level, it is best to remove the level.
sponsor_levels:
+ - id: platinum
+ label: Platinum
- id: gold
label: Gold
max: 10
- id: silver
label: Silver
max: 0 # This is the same as omitting the max limit.
- - id: bronze
- label: Bronze
+ - id: hrsponsor
+ label: HR
+ - id: media
+ label: Media
- id: community
label: Community
+
diff --git a/exampleSite/data/events/2017-ohio.yml b/exampleSite/data/events/2017-ohio.yml
new file mode 100644
index 000000000..ef03cd8f0
--- /dev/null
+++ b/exampleSite/data/events/2017-ohio.yml
@@ -0,0 +1,33 @@
+name: "2017-ohio" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: 2017 # The year of the event. Make sure it is in quotes.
+city: "Ohio" # The city name of the event. Capitalize it.
+friendly: "2017-ohio" # Four digit year and the city name in lower-case. Don't forget the dash!
+status: "past" # Options are "past" or "current".
+startdate: "" # The start date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+enddate: "" # The end date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+cfp_date_start: ""
+cfp_date_end: ""
+cfp_date_announce: ""
+coordinates: "40.038877, -82.874830" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "" # The name of your location
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+ - name: contact
+ - name: conduct
+ - name: sponsor
+team: ["Ben Blanquera", "Bill Schwanitz", "David Laulusa", "Kyle Jenkins", "John Lusk", "Mark Goodmanson", "Michael Ducy", "Michael Swartzbaugh", "Rob Kinyon", "Warner Moore"]
+organizer_email: "organizers-ohio-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "organizers-ohio-2017@devopsdays.org" # Put your proposal email address here
+sponsors: # List all of your sponsors here along with what level of sponsorship they have.
+ - id: test
+ level: gold
+
+sponsor_levels: # In this section, list the level of sponsorships and the label to use.
+ - id: gold
+ label: Gold
+ - id: silver
+ label: Silver
+ - id: bronze
+ label: Bronze
+ - id: support
+ label: Community and Supporting
diff --git a/exampleSite/data/events/2017-paris.yml b/exampleSite/data/events/2017-paris.yml
index e54609c8f..8b037a48a 100644
--- a/exampleSite/data/events/2017-paris.yml
+++ b/exampleSite/data/events/2017-paris.yml
@@ -1,7 +1,6 @@
name: "2017-paris" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Paris" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
diff --git a/exampleSite/data/events/2017-portland.yml b/exampleSite/data/events/2017-portland.yml
index 93af87a83..d121640f4 100644
--- a/exampleSite/data/events/2017-portland.yml
+++ b/exampleSite/data/events/2017-portland.yml
@@ -2,7 +2,6 @@ name: "2017-portland" # The name of the event. Four digit year with the city nam
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Portland" # The displayed city name of the event. Capitalize it.
friendly: "2017-portland"
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
diff --git a/exampleSite/data/events/2017-saint-louis.yml b/exampleSite/data/events/2017-saint-louis.yml
new file mode 100644
index 000000000..62b8109ab
--- /dev/null
+++ b/exampleSite/data/events/2017-saint-louis.yml
@@ -0,0 +1,70 @@
+name: "2017-saint-louis" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Saint Louis" # The displayed city name of the event. Capitalize it.
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: "DevOpsDays is coming to Saint Louis in 2017! It'll be a great opportunity to share knowledge, socialize, and have fun with other memnbers of our great technical community." # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # 2017-03-31 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # 2017-04-01 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # 2016-12-01 # start accepting talk proposals.
+cfp_date_end: # 2017-02-01 # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "38.7084, -90.4390" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Saint Louis" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: https://trello.com/b/qtP2nsVm/presentations # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+# - name: policies
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Sabree Blackmon"
+ twitter: "heavypackets"
+ - name: "Phil Cryer"
+ twitter: "fak3r"
+ - name: "Jim Hopkins"
+ - name: "Jess Jackson"
+ twitter: "jess_d_jackson"
+ - name: "Sayam Masood"
+ twitter: "mixpix3ls"
+ - name: "Matthew Perry"
+ twitter: "mlperry81"
+
+organizer_email: "organizers-saint-louis-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-saint-louis-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors: {}
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-salt-lake-city.yml b/exampleSite/data/events/2017-salt-lake-city.yml
index 15e066d7b..3e7bc03f1 100644
--- a/exampleSite/data/events/2017-salt-lake-city.yml
+++ b/exampleSite/data/events/2017-salt-lake-city.yml
@@ -1,16 +1,15 @@
name: "2017-salt-lake-city" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Salt Lake City" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: "DevOpsDays returns to the Silicon Slopes!"# A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
startdate: 2017-05-16 # The start date of your event. Leave blank if you don't have a venue reserved yet.
enddate: 2017-05-17 # The end date of your event. Leave blank if you don't have a venue reserved yet.
# Leave CFP dates blank if you don't know yet, or set all three at once.
-cfp_date_start: # start accepting talk proposals.
-cfp_date_end: # close your call for proposals.
-cfp_date_announce: # inform proposers of status
+cfp_date_start: 2016-12-14 # start accepting talk proposals.
+cfp_date_end: 2017-02-15 # close your call for proposals.
+cfp_date_announce: 2017-03-01 # inform proposers of status
# Location
#
@@ -21,13 +20,16 @@ location: "Noah's Event Venue" # Defaults to city, but you can make it the venue
nav_elements: # List of pages you want to show up in the navigation of your page.
- name: welcome
# - name: program
-# - name: propose
-# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
-# - name: location
-# - name: registration
+ - name: propose
+ url: https://www.papercall.io/slc-dev-ops-days
+ - name: location
+ - name: registration
+ url: http://slcdevopsdays.org/tc-events/slc-devops-days-2917/
- name: sponsor
+ url: http://slcdevopsdays.org/our-sponsors/
- name: contact
- name: conduct
+ url: http://slcdevopsdays.org/code-of-conduct/
# These are the same people you have on the mailing list and Slack channel.
team_members: # Name is the only required field for team members.
@@ -52,6 +54,9 @@ team_members: # Name is the only required field for team members.
employer: "HealthEquity"
twitter: "alexinslc"
- name: "Lindley White"
+ - name: "Brett Palmer"
+ - name: "Johnny Martinez"
+ - name: "Claron Twitchel"
organizer_email: "organizers-saltlakecity-2017@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-saltlakecity-2017@devopsdays.org" # Put your proposal email address here
@@ -59,6 +64,10 @@ proposal_email: "proposals-saltlakecity-2017@devopsdays.org" # Put your proposal
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
+ - id: morpheus_data
+ level: greencircle
+ - id: deis
+ level: blackdiamond
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
# In this section, list the level of sponsorships and the label to use.
@@ -68,6 +77,8 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
sponsor_levels:
- id: eveningsocial
label: Evening Social
+ - id: doubleblackdiamond
+ label: Double Black Diamond
- id: blackdiamond
label: Black Diamond
- id: bluesquare
diff --git a/exampleSite/data/events/2017-sao-paulo.yml b/exampleSite/data/events/2017-sao-paulo.yml
new file mode 100644
index 000000000..b4eee1b28
--- /dev/null
+++ b/exampleSite/data/events/2017-sao-paulo.yml
@@ -0,0 +1,75 @@
+name: "2017-sao-paulo" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "São Paulo" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "-23.551261, -46.634345" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "São Paulo" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: bem vindo
+ url: ../bemvindo
+# - name: programacao
+# - name: chamada
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: local
+# - name: inscricao
+ - name: patrocinio
+ - name: contato
+ - name: conduta
+
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Diógenes Rettori"
+ twitter: "rettori"
+ - name: "Fernando Ike"
+ - name: "Luciano Ramalho"
+ - name: "Luis Albinati Jr"
+ - name: "Melina Deraldo"
+ twitter: "melderaldo"
+ - name: "Rafael Gomes"
+ twitter: "gomex"
+ - name: "Thiago Araki"
+ - name: "Ana Paula Maia"
+ - name: "Frederico Moreira"
+# employer: "Acme Anvil Co."
+organizer_email: "organizers-sao-paulo-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-sao-paulo-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-seattle.yml b/exampleSite/data/events/2017-seattle.yml
index 3c3da2e98..22876c8c6 100644
--- a/exampleSite/data/events/2017-seattle.yml
+++ b/exampleSite/data/events/2017-seattle.yml
@@ -1,7 +1,6 @@
name: "2017-seattle" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Seattle" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: "DevOpsDays is returning to Seattle in 2017" # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
@@ -14,7 +13,7 @@ cfp_date_announce: 2017-02-07 # inform proposers of status
# Location
#
-coordinates: "47.606209, -122.332071" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+coordinates: "47.623948, -122.350088" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
location: "Seattle" # Defaults to city, but you can make it the venue name.
#
@@ -46,8 +45,20 @@ proposal_email: "proposals-seattle-2017@devopsdays.org" # Put your proposal emai
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
- - id: thoughtworks-products
+ - id: gocd
level: gold
+ - id: sumologic
+ level: gold
+ - id: deis
+ level: gold
+ - id: slalom
+ level: gold
+ - id: pivotal
+ level: gold
+ - id: opsgenie
+ level: gold
+ - id: spoken
+ level: bronze
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
diff --git a/exampleSite/data/events/2017-stockholm.yml b/exampleSite/data/events/2017-stockholm.yml
new file mode 100644
index 000000000..e8e79b94e
--- /dev/null
+++ b/exampleSite/data/events/2017-stockholm.yml
@@ -0,0 +1,66 @@
+name: "2017-stockholm" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Stockholm" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "59.329323, 18.068581" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Stockholm" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Andrey Devyatkin"
+ - name: "Björn Sundling"
+ - name: "Cecilia Wirén"
+ - name: "Fredrik Nilsson"
+ - name: "Lowe Schmidt"
+ - name: "Niklas Åkerlund"
+organizer_email: "organizers-stockholm-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-stockholm-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: praqma
+ level: silver
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-tokyo.yml b/exampleSite/data/events/2017-tokyo.yml
new file mode 100644
index 000000000..d0b26fac4
--- /dev/null
+++ b/exampleSite/data/events/2017-tokyo.yml
@@ -0,0 +1,68 @@
+name: "2017-tokyo" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Tokyo" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "35.689488, 139.691706" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Tokyo" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Ippei Suzuki"
+ employer: "Creationline"
+ - name: "Alex Papadimoulis"
+ employer: "Inedo"
+ twitter: "apapadimoulis"
+ - name: "Yasunobu Kawaguchi"
+ employer: "Rakuten"
+
+organizer_email: "organizers-tokyo-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-tokyo-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+# - id: samplesponsorname
+# level: gold
+# - id: arresteddevops
+# level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+# - id: gold
+# label: Gold
+# max: 10
+# - id: silver
+# label: Silver
+# max: 0 # This is the same as omitting the max limit.
+# - id: bronze
+# label: Bronze
+# - id: community
+# label: Community
diff --git a/exampleSite/data/events/2017-toronto.yml b/exampleSite/data/events/2017-toronto.yml
index 7d27622a2..293ff9918 100644
--- a/exampleSite/data/events/2017-toronto.yml
+++ b/exampleSite/data/events/2017-toronto.yml
@@ -1,30 +1,29 @@
name: "2017-toronto" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Toronto" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
-startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
-enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+startdate: 2017-05-25 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2017-05-26 # The end date of your event. Leave blank if you don't have a venue reserved yet.
# Leave CFP dates blank if you don't know yet, or set all three at once.
-cfp_date_start: # start accepting talk proposals.
-cfp_date_end: # close your call for proposals.
-cfp_date_announce: # inform proposers of status
+cfp_date_start: 2016-12-21 # start accepting talk proposals.
+cfp_date_end: 2017-01-31 # close your call for proposals.
+cfp_date_announce: 2017-02-28 # inform proposers of status
# Location
#
-coordinates: "43.6532,-79.3831" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
-location: "Toronto" # The name of your location
+coordinates: "43.644489,-79.388044" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Glenn Gould Studio" # The name of your location
#
nav_elements: # List of pages you want to show up in the navigation of your page.
- name: welcome
# - name: program
-# - name: propose
+ - name: propose
# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
-# - name: location
-# - name: registration
+ - name: location
+ - name: register
- name: sponsor
- name: contact
- name: conduct
@@ -50,6 +49,8 @@ proposal_email: "proposals-toronto-2017@devopsdays.org" # Put your proposal emai
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
+ - id: nocompany #HACK - add a sponsor at a non-existent level to force levels to show.
+ level: community
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
@@ -60,11 +61,15 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
sponsor_levels:
- id: gold
label: Gold
- max: 10
+ max: 14
+ - id: happyhour
+ label: Happy Hour
+ max: 1
+ - id: lunch
+ label: Lunch
+ max: 2
- id: silver
label: Silver
max: 0 # This is the same as omitting the max limit.
- id: bronze
label: Bronze
- - id: community
- label: Community
diff --git a/exampleSite/data/events/2017-vancouver.yml b/exampleSite/data/events/2017-vancouver.yml
new file mode 100644
index 000000000..9bd2a6762
--- /dev/null
+++ b/exampleSite/data/events/2017-vancouver.yml
@@ -0,0 +1,67 @@
+name: "2017-vancouver" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Vancouver" # The displayed city name of the event. Capitalize it.
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: 2017-03-31 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2017-04-01 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: 2016-12-01 # start accepting talk proposals.
+cfp_date_end: 2017-02-01 # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "49.282729, -123.120738" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Vancouver" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+ - name: program
+ - name: propose
+ url: "https://docs.google.com/forms/d/e/1FAIpQLSddTit30OVfFcbrRNXyIIqPRwX-USUbQWMzNpM9meBEi1DB7g/viewform"
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+ - name: location
+ - name: registration
+ url: "https://www.eventbrite.ca/e/devops-days-vancouver-2017-mar-31st-apr-1st-tickets-29634403298"
+ - name: sponsor
+ - name: contact
+ - name: conduct
+ - name: policies
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Kelly Shkuratoff"
+ - name: "Michael Collins"
+ - name: "Ronald Bow"
+ - name: "Vincent Janelle"
+ twitter: "randomfrequency"
+ - name: "Saem Ghani"
+ - name: "Chris Demwell"
+organizer_email: "organizers-vancouver-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-vancouver-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors: {}
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-washington-dc.yml b/exampleSite/data/events/2017-washington-dc.yml
new file mode 100644
index 000000000..ce2e85672
--- /dev/null
+++ b/exampleSite/data/events/2017-washington-dc.yml
@@ -0,0 +1,80 @@
+name: "2017-washington-dc" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Washington, DC" # The displayed city name of the event. Capitalize it.
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Washington, DC" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Nathen Harvey"
+ twitter: "nathenharvey"
+ employer: "Chef"
+ - name: "Alan Kraft"
+ employer: "United States Patent and Trademark Office (USPTO)"
+ - name: "Michael Barbine"
+ twitter: "BigNerdLoLz"
+ employer: "Barbine Worldwide"
+ - name: "Mike DelNegro"
+ twitter: "radiocats"
+ employer: "Deltek"
+ - name: "Greg Elin"
+ twitter: "gregelin"
+ employer: "GovReady"
+ - name: "Jeff Gallimore"
+ twitter: "jgallimore"
+ employer: "Excella Consulting"
+ - name: "James Martin"
+ twitter: "grepless"
+ employer: "3M"
+ - name: "Ramez Mourad"
+ twitter: "ramezjm"
+ employer: "Cvent"
+organizer_email: "organizers-washington-dc-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-washington-dc-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: platinum
+ label: Platinum
+ - id: gold
+ label: Gold
+ - id: silver
+ label: Silver
+ - id: media
+ label: Media
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-zurich.yml b/exampleSite/data/events/2017-zurich.yml
index 5a1a06f6d..a5170be78 100644
--- a/exampleSite/data/events/2017-zurich.yml
+++ b/exampleSite/data/events/2017-zurich.yml
@@ -2,14 +2,13 @@ name: "2017-zurich" # The name of the event. Four digit year with the city name
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Zürich" # The city name of the event. Capitalize it.
friendly: "2017-zurich" # Four digit year and the city name in lower-case. Don't forget the dash!
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
startdate: 2017-05-03
enddate: 2017-05-04
# Leave CFP dates blank if you don't know yet, or set all three at once.
cfp_date_start: 2016-11-01 # start accepting talk proposals.
-cfp_date_end: 2017-03-01 # close your call for proposals.
+cfp_date_end: 2017-02-01 # close your call for proposals.
cfp_date_announce: 2017-04-01 # inform proposers of status
# Location
@@ -51,6 +50,7 @@ team_members: # Name is the only required field for team members.
- name: "Tobias Brunner"
twitter: "tobruzh"
employer: "VSHN AG"
+ - name: "Vittorio Boccone"
organizer_email: "organizers-zuerich-2017@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-zuerich-2017@devopsdays.org" # Put your proposal email address here
@@ -60,7 +60,7 @@ proposal_email: "proposals-zuerich-2017@devopsdays.org" # Put your proposal emai
sponsors:
- id: swisscom
level: gold
- - id: glenfis
+ - id: pontine
level: gold
- id: redhat
level: gold
@@ -68,8 +68,14 @@ sponsors:
level: gold
- id: chef
level: gold
+ - id: gocd
+ level: gold
- id: vshn
level: bronze
+ - id: dectris
+ level: bronze
+ - id: atos
+ level: gold
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
sponsor_levels: # In this section, list the level of sponsorships and the label to use.
diff --git a/exampleSite/data/speakers/2016/amsterdam/adam-jacob.yml b/exampleSite/data/speakers/2016/amsterdam/adam-jacob.yml
new file mode 100644
index 000000000..3fa307a28
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/adam-jacob.yml
@@ -0,0 +1,3 @@
+name: "Adam Jacob"
+twitter: "adamhjk"
+bio: "Adam Jacob is the creator of Chef and co-founder of Chef, Inc. in 2008 and currently serves as its Chief Technology Officer. Prior to Chef, Inc. Adam founded HJK Solutions, an automated infrastructure consultancy. During two years at HJK, Adam built new infrastructures for 15 different startups. Including Adam's time at HJK, Adam has 13 years of experience as a systems administrator, systems architect, and tools developer."
diff --git a/exampleSite/data/speakers/2016/amsterdam/andrew-farley.yml b/exampleSite/data/speakers/2016/amsterdam/andrew-farley.yml
new file mode 100644
index 000000000..949b2a65d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/andrew-farley.yml
@@ -0,0 +1,3 @@
+name: "Andrew Farley"
+twitter: ""
+bio: "Farley is a Senior DevOps Engineer and consultant for OlinData. He has experience with high-scalability systems both in bare metal and in the cloud for the last 12 years and on AWS for over 6 years now. He's founded a handful of startups and been doing consulting for a wide range of companies in Silicon Valley and around the world. He is passionate about high-scalability and redundant, systems, automation, agile and continuous deployment, documentation, diagramming and open-source software. He has no associations with Amazon other than being a passionate user of their platform and holding an AWS Associate Certification. Farley's interests don’t end at managing servers, he's authored and launched over 30 mobile applications, numerous games, he’s launched or been an early employee at a dozen startups, and has years of experience designing and consuming APIs using various languages. And for fun he plays with microelectronics and designs & flies racing quad-copters in his free time."
diff --git a/exampleSite/data/speakers/2016/amsterdam/arnold-van-wijnbergen.yml b/exampleSite/data/speakers/2016/amsterdam/arnold-van-wijnbergen.yml
new file mode 100644
index 000000000..000defaee
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/arnold-van-wijnbergen.yml
@@ -0,0 +1,3 @@
+name: "Arnold van Wijnbergen"
+twitter: "bsmconsultant"
+bio: "Arnold van Wijnbergen is an independent advisor, coach and consultant from Devoteam. He specializes in Monitoring and Automation topics to improve quality and efficiency of operational control of IT4IT business. To achieve this he combines Lean principles with DevOps culture, because he strongly believes in the power of culture and self-steering teams. His broad experience in Monitoring and Automation tooling implementations ranges from midsize till enterprise scale, formed mainly in the banking, insurance, governance, retail, telco and service provider branches. At ING he is management consultant within the ING Automate monitoring stream, which is responsible for advising, training and coaching DevOps teams with improving their monitoring capabilities."
diff --git a/exampleSite/data/speakers/2016/amsterdam/avishai-ish-shalom.yml b/exampleSite/data/speakers/2016/amsterdam/avishai-ish-shalom.yml
new file mode 100644
index 000000000..8637c1699
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/avishai-ish-shalom.yml
@@ -0,0 +1,3 @@
+name: "Avishai Ish-Shalom"
+twitter: "nukemberg"
+bio: "Avishai Ish-Shalom is a veteran Ops and a survivor of many production skirmishes. Currently an independent consultant, Avishai helps companies deal with web era operations and scale. In his spare time Avishai is spreading weird ideas and conspiracy theories such as DevOps."
diff --git a/exampleSite/data/speakers/2016/amsterdam/bas-meijer.yml b/exampleSite/data/speakers/2016/amsterdam/bas-meijer.yml
new file mode 100644
index 000000000..a57b1024e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/bas-meijer.yml
@@ -0,0 +1,3 @@
+name: "Bas Meijer"
+twitter: "bbaassssiiee"
+bio: "Bas is a systems engineer and software developer and wasted decades on latenight hacking. He is currently helping out 2 enterprises with continuous delivery and devops."
diff --git a/exampleSite/data/speakers/2016/amsterdam/bernd-erk.yml b/exampleSite/data/speakers/2016/amsterdam/bernd-erk.yml
new file mode 100644
index 000000000..88a6e8cb9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/bernd-erk.yml
@@ -0,0 +1,3 @@
+name: "Bernd Erk"
+twitter: "gethash"
+bio: "Bernd Erk is co-founder and community manager of the Icinga Project. In his day job he is CEO at NETWAYS, a German open source service company. As contributor to Linux Magazine and Admin Magazine, Bernd regularly publishes articles and presents on open source topics ranging from monitoring, configuration management to various open source datacenter solutions. He tries to spread the DevOps spirit wherever and whenever possible."
diff --git a/exampleSite/data/speakers/2016/amsterdam/christoph-andreas-torlinsky.yml b/exampleSite/data/speakers/2016/amsterdam/christoph-andreas-torlinsky.yml
new file mode 100644
index 000000000..f2560e71c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/christoph-andreas-torlinsky.yml
@@ -0,0 +1,3 @@
+name: "Christoph Andreas Torlinsky"
+twitter: "nuagenetworks"
+bio: "Hello, i work for a Startup called Nuage Networks in EMEA and we are actively trying to change how Software interacts with the Network. Check us out, I've been working for a number of companies prior to Nuage in the Networking and Linux and Operating Space."
diff --git a/exampleSite/data/speakers/2016/amsterdam/daniel-van-gils.yml b/exampleSite/data/speakers/2016/amsterdam/daniel-van-gils.yml
new file mode 100644
index 000000000..5f8db3e3e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/daniel-van-gils.yml
@@ -0,0 +1,3 @@
+name: "Daniël van Gils"
+twitter: "foldingbeauty"
+bio: "Daniël van Gils is a polyglot developer advocate at Cloud 66. He helps other polyglot developers craft ruby (on rails) web applications and container based microservice architectures with ♥, to deploy on any server or public cloud. He’s been involved in the web development, creative technologies, and gaming industries. An accomplished creative technologist, Daniel has vast and varied experience in application development, agile workflows, lecturing and building container technologies at scale. In his spare time he experiments with strawberries in his backyard, likes to surf and practices improvisation theater."
diff --git a/exampleSite/data/speakers/2016/amsterdam/dave-van-herpen.yml b/exampleSite/data/speakers/2016/amsterdam/dave-van-herpen.yml
new file mode 100644
index 000000000..f65b25b60
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/dave-van-herpen.yml
@@ -0,0 +1,3 @@
+name: "Dave van Herpen"
+twitter: "daveherpen"
+bio: "Dave van Herpen is management coach (Enterprise Agility & DevOps) at Sogeti Netherlands. In his role as practitioner, coach, trainer and change agent, Dave has been supporting his customers to organize for end-to-end agility for the past 15 years."
diff --git a/exampleSite/data/speakers/2016/amsterdam/desmond-delissen.yml b/exampleSite/data/speakers/2016/amsterdam/desmond-delissen.yml
new file mode 100644
index 000000000..895522e46
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/desmond-delissen.yml
@@ -0,0 +1,3 @@
+name: "Desmond Delissen"
+twitter: ""
+bio: "Desmond started his career at a big consultancy company. Via this company he got the change to join a mobile app project in the beginning of 2012. Desmond enjoined this so much that he decided to start working for IceMobile and become a expert in testing mobile apps and their backend systems."
diff --git a/exampleSite/data/speakers/2016/amsterdam/erica-baker.yml b/exampleSite/data/speakers/2016/amsterdam/erica-baker.yml
new file mode 100644
index 000000000..b48f228b0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/erica-baker.yml
@@ -0,0 +1,3 @@
+name: "Erica Baker"
+twitter: "EricaJoy"
+bio: "Erica is a Senior Engineer at Slack Technologies and advocate for diversity and inclusion in tech, and expanding access to tech education. Erica's career in tech began fourteen years ago doing domain administration for the University of Alaska Statewide System, before becoming a Googler in 2006. Erica's role grew and shifted within Google, growing from Support Technician to Site Reliability Engineer. She joined Slack in 2015, where she focuses on Build and Release Engineering. Erica is on the Advisory Boards for Atipica and Hack the Hood, and is a Tech Mentor for Black Girls Code. Erica is currently based in Oakland, California."
diff --git a/exampleSite/data/speakers/2016/amsterdam/gopal-ramachandran.yml b/exampleSite/data/speakers/2016/amsterdam/gopal-ramachandran.yml
new file mode 100644
index 000000000..fb7375d5e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/gopal-ramachandran.yml
@@ -0,0 +1,3 @@
+name: "Gopal Ramachandran"
+twitter: "goposky"
+bio: "Gopal is an experienced engineer/consultant who is passionate about Devops. The last few years he has been busy creating CD pipelines, implementing configuration management, and automating stuff at few large companies in the Netherlands. Prior to that he has been a hosting engineer, and also a Java developer."
diff --git a/exampleSite/data/speakers/2016/amsterdam/guy-podjarny.yml b/exampleSite/data/speakers/2016/amsterdam/guy-podjarny.yml
new file mode 100644
index 000000000..56b74c57c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/guy-podjarny.yml
@@ -0,0 +1,3 @@
+name: "Guy Podjarny"
+twitter: "guypod"
+bio: "Guy Podjarny is a cofounder at Snyk.io focusing on securing open source code. Guy was previously CTO at Akamai and founder of Blaze.io, and worked on the first web app firewall & security static code analyzer. Guy is a frequent conference speaker, the author of 'Responsive & Fast', 'High Performance Images' and the upcoming 'Securing Third Party Code' (via O’Reilly), and the creator of Mobitest."
diff --git a/exampleSite/data/speakers/2016/amsterdam/hannah-foxwell.yml b/exampleSite/data/speakers/2016/amsterdam/hannah-foxwell.yml
new file mode 100644
index 000000000..a17bd78df
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/hannah-foxwell.yml
@@ -0,0 +1,3 @@
+name: "Hannah Foxwell"
+twitter: "hannahfoxwell"
+bio: "While culture and sharing are at the heart of DevOps, Infrastructure Automation is the technical backbone. That’s one of the reasons why Hannah co-founded Pendrica, a consultancy specialising in Platform Automation with Chef and Microsoft. Hannah’s background and experience in managing large scale software programmes naturally lead to a keen interest in Agile, Continuous Delivery and the DevOps movement as a way of building collaborative, highly-performing teams. As a coach and mentor she continues this work today, helping teams improve how they work together in the fast-moving world of automation. Outside of work you can generally find Hannah in her local pub enjoying a craft beer while planning her next adventure."
diff --git a/exampleSite/data/speakers/2016/amsterdam/harm-weites.yml b/exampleSite/data/speakers/2016/amsterdam/harm-weites.yml
new file mode 100644
index 000000000..418b8b86b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/harm-weites.yml
@@ -0,0 +1,3 @@
+name: "Harm Weites"
+twitter: "wehkamp"
+bio: "Harm is committed to engineering the Wehkamp e-commerce platform, making sure it scales and performs to meet customer and business demands. He is passionate about automation and is part of Wehkamp’s SRE team."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jan-de-vries.yml b/exampleSite/data/speakers/2016/amsterdam/jan-de-vries.yml
new file mode 100644
index 000000000..b8e004892
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jan-de-vries.yml
@@ -0,0 +1,3 @@
+name: "Jan de Vries"
+twitter: ""
+bio: "Jan de Vries is a senior business IT consultant and a trusted advisor in the fields of requirements engineering, business information management, application management and DevOps. He is a BiSL, ASL, ITIL, ISM and FSM trainer and convenor of the Enterprise DevOps working group that unites members of the ASL BiSL Foundation and the Agile Consortium. He founded Blue Ocean Recon to do research that focuses on Blue Oceans and Lean Startups."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jan-kaan.yml b/exampleSite/data/speakers/2016/amsterdam/jan-kaan.yml
new file mode 100644
index 000000000..b79e82ea5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jan-kaan.yml
@@ -0,0 +1,3 @@
+name: "Jan Kaan"
+twitter: "jankaan81"
+bio: "Jan Kaan runs the Expert Partner Program for Atlassian within the Benelux & Nordics. With a background in Intercultural Awareness and 15 years of experience within the IT space he has fulfilled various roles from Recruitment to Sales in primarily large international organizations."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jason-yee.yml b/exampleSite/data/speakers/2016/amsterdam/jason-yee.yml
new file mode 100644
index 000000000..4ecbdd537
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jason-yee.yml
@@ -0,0 +1,3 @@
+name: "Jason Yee"
+twitter: "gitbisect"
+bio: "Jason is a community builder, developer, traveller and chef. He's passionate about connecting people and ideas to build a better world."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jim-leitch.yml b/exampleSite/data/speakers/2016/amsterdam/jim-leitch.yml
new file mode 100644
index 000000000..5b2c250a9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jim-leitch.yml
@@ -0,0 +1,3 @@
+name: "Jim Leitch"
+twitter: ""
+bio: "Jim is a family man, guitarist and dog lover. Having lived in the Netherlands for the last 22 years he knows where the best stroopwafels are."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jody-wolfborn.yml b/exampleSite/data/speakers/2016/amsterdam/jody-wolfborn.yml
new file mode 100644
index 000000000..0be2e7794
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jody-wolfborn.yml
@@ -0,0 +1,3 @@
+name: "Jody Wolfborn"
+twitter: "joderita"
+bio: "Jody is a theatre major-turned-technologist with a passion for languages of all kinds and a soft-spot for animals of the canine variety. Since entering the tech realm, she’s had many years of experience living with and attempting to overcome Impostor Syndrome; through observation, research, and experimentation, she’s collected resources to help combat this psychological self-sabotage."
diff --git a/exampleSite/data/speakers/2016/amsterdam/karleen-wijsman.yml b/exampleSite/data/speakers/2016/amsterdam/karleen-wijsman.yml
new file mode 100644
index 000000000..c1ddda3c3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/karleen-wijsman.yml
@@ -0,0 +1,3 @@
+name: "Karleen Wijsman"
+twitter: ""
+bio: "Karleen Wijsman is an all-round IT Specialist and has many years of experience in providing training and workshops in the field of personal development and organisational change. Her NLP Practitioner and NLP Master background give her a solid foundation to motivate, engage and energize people and organizations"
diff --git a/exampleSite/data/speakers/2016/amsterdam/ken-mugrage.yml b/exampleSite/data/speakers/2016/amsterdam/ken-mugrage.yml
new file mode 100644
index 000000000..4991a6439
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/ken-mugrage.yml
@@ -0,0 +1,3 @@
+name: "Ken Mugrage"
+twitter: "kmugrage"
+bio: "Ken Mugrage has 25 years of experience in the IT industry, spending the last 7 at ThoughtWorks. During his entire career, Ken has focused on using technology to increase business effectiveness, as opposed to using the ‘latest cool thing’. Ken has been focused on Continuous Delivery and DevOps for most of the past decade, working with organizations all over the world, ranging from startups to Fortune 50 companies. He now uses this experience to teach others how to get better at building, testing and deploying software."
diff --git a/exampleSite/data/speakers/2016/amsterdam/marco-ceppi.yml b/exampleSite/data/speakers/2016/amsterdam/marco-ceppi.yml
new file mode 100644
index 000000000..d28909f08
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/marco-ceppi.yml
@@ -0,0 +1,3 @@
+name: "Marco Ceppi"
+twitter: "marcoceppi"
+bio: "Marco Ceppi is a devops engineer working for Canonical - the company behind Ubuntu. When not behind a computer, he often enjoys sailing, restoring cars, and voiding warranties."
diff --git a/exampleSite/data/speakers/2016/amsterdam/mark-van-holsteijn.yml b/exampleSite/data/speakers/2016/amsterdam/mark-van-holsteijn.yml
new file mode 100644
index 000000000..7a4d3a7e8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/mark-van-holsteijn.yml
@@ -0,0 +1,3 @@
+name: "Mark van Holsteijn"
+twitter: ""
+bio: "Mark van Holsteijn is Principal Consultant at Xebia specialized in cloud software architectures with open-source technologies."
diff --git a/exampleSite/data/speakers/2016/amsterdam/melanie-rieback.yml b/exampleSite/data/speakers/2016/amsterdam/melanie-rieback.yml
new file mode 100644
index 000000000..32c9e7f29
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/melanie-rieback.yml
@@ -0,0 +1,3 @@
+name: "Melanie Rieback"
+twitter: ""
+bio: "Melanie Rieback is the CEO/Co-founder of Radically Open Security. She is also a former Asst. Prof. of Computer Science at the Vrije Universiteit Amsterdam who performed RFID security research (RFID Virus and RFID Guardian), that got worldwide press coverage, and won several awards (VU Mediakomeet, ISOC Award finalist, NWO I/O award, IEEE Percom Best Paper, USENIX Lisa Best Paper). Melanie also worked as a Sr. Engineering Manager on XenClient at Citrix, where she led the Citrix Vancouver office. She was also a Sr. Managing Consultant in the Cyber Crime Expertise and Response Team (CCERT) at ING Bank, where she set up the CCERT Analysis Lab and was the lead technical project manager of the ING Core Threat Intelligence Systems. For fun, she founded the Dutch Girl Geek Dinner in 2008. Melanie was also named 2010 ICT Professional of the Year (Finalist) by WomeninIT, and one of the “400 most successful women in the Netherlands” by Viva Magazine (Viva400) in 2010."
diff --git a/exampleSite/data/speakers/2016/amsterdam/michael-ducy.yml b/exampleSite/data/speakers/2016/amsterdam/michael-ducy.yml
new file mode 100644
index 000000000..d27997ef9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/michael-ducy.yml
@@ -0,0 +1,3 @@
+name: "Michael Ducy"
+twitter: "mfdii"
+bio: "Michael Ducy currently works as a Manager for Solutions Architects at Chef focusing on helping companies understand Chef, DevOps, and IT transformation. Previously, Michael focused on designing and implementing automation solutions for customer’s Cloud, IT Automation, and Continuous Delivery needs. Michael has also worked in a variety of roles in his career including Cloud Architecture, Systems Engineering , Performance Engineering, and IT Instructor. Michael holds a Masters in Computer Science from the University of Chicago and an MBA from The Ohio State University."
diff --git a/exampleSite/data/speakers/2016/amsterdam/michael-friedrich.yml b/exampleSite/data/speakers/2016/amsterdam/michael-friedrich.yml
new file mode 100644
index 000000000..617d9d894
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/michael-friedrich.yml
@@ -0,0 +1,3 @@
+name: "Michael Friedrich"
+twitter: ""
+bio: "Michael has been an Icinga core developer for more than 7 years. He is currently leading the Icinga 2 development together with Gunnar. In addition to the exciting core architecture work he likes to play with Vagrant. Docker and Dashing. You’ll also find him active over at monitoring-portal.org, most recently as administrator too. In his spare time Michael loves to build LEGO models and enjoys Nuremberg with his Austrian dialect."
diff --git a/exampleSite/data/speakers/2016/amsterdam/nati-cohen.yml b/exampleSite/data/speakers/2016/amsterdam/nati-cohen.yml
new file mode 100644
index 000000000..33e2b752f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/nati-cohen.yml
@@ -0,0 +1,3 @@
+name: "Nati Cohen"
+twitter: "nocoot"
+bio: "Nati Cohen is a Production Engineer at SimilarWeb, fighting manual labor with code and vengeance. Previous experience includes: operations consulting, software development, *nix administration and security research in the Intelligence corps as well as in multiple startup companies."
diff --git a/exampleSite/data/speakers/2016/amsterdam/pavel-chunyayev.yml b/exampleSite/data/speakers/2016/amsterdam/pavel-chunyayev.yml
new file mode 100644
index 000000000..e6948c9b6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/pavel-chunyayev.yml
@@ -0,0 +1,3 @@
+name: "Pavel Chunyayev"
+twitter: "PavelChunyayev"
+bio: "Pavel Chunyayev is a Continuous Delivery Architect at Levi9 IT Services. With 12 years of experience he moved a year and a half ago to Amsterdam to continue working with Levi9’s customers to help them create or optimize the way they deliver their applications to production. Pavel is a regular speaker at local meetups promoting ideas of continuous delivery, programmable infrastructure and automated testing."
diff --git a/exampleSite/data/speakers/2016/amsterdam/philipp-krenn.yml b/exampleSite/data/speakers/2016/amsterdam/philipp-krenn.yml
new file mode 100644
index 000000000..39b219189
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/philipp-krenn.yml
@@ -0,0 +1,3 @@
+name: "Philipp Krenn"
+twitter: "xeraa"
+bio: "Philipp is a Developer Advocate at Elastic, spreading the love and knowledge of full-text search, analytics, and real-time data. He is a frequent speaker at conferences and meetups about all things search & analytics, databases, cloud computing, and devops. Philipp lives in Vienna where he enjoys experimenting with software, organizing meetups, and sports."
diff --git a/exampleSite/data/speakers/2016/amsterdam/remi-bergsma.yml b/exampleSite/data/speakers/2016/amsterdam/remi-bergsma.yml
new file mode 100644
index 000000000..0aebf2be3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/remi-bergsma.yml
@@ -0,0 +1,3 @@
+name: "Remi Bergsma"
+twitter: "remibergsma"
+bio: "Remi Bergsma is an engineer with a pasion for automation. He works for Schuberg Philis, a Mission Critical outsourcing company in NL. Since about 2,5 years Remi works in the Mission Critical Cloud Team at Schuberg Philis. In this role he and his colleagues make sure their Mission Critical Cloud simply works. That is truly DevOps: from ordering, racking and automatically configuring hardware all the way to developing new features and fixing bugs in the Java and Python code. Remi is an Apache CloudStack committer/PMC member and was Release Manager for CloudStack 4.6, 4.7 and 4.8. Nowadays Remi is one of the committers in the Cosmic Cloud project. He did several talks and workshops on conferences and enjoys teaching others new stuff."
diff --git a/exampleSite/data/speakers/2016/amsterdam/robert-den-broeder.yml b/exampleSite/data/speakers/2016/amsterdam/robert-den-broeder.yml
new file mode 100644
index 000000000..358a6060f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/robert-den-broeder.yml
@@ -0,0 +1,3 @@
+name: "Robert den Broeder"
+twitter: ""
+bio: "Robert den Broeder is owner of Trigono BV and is a certified trainer / coach in IT Service Management and Organizational Behavior Management (OBM). Organizational Behavior Management (OBM) is a management approach that demonstrably increases team performance and motivation. Robert supports organizations with implementing and improving service management processes, with special attention for behavioral change, using OBM techniques and principles."
diff --git a/exampleSite/data/speakers/2016/amsterdam/simon-fisher.yml b/exampleSite/data/speakers/2016/amsterdam/simon-fisher.yml
new file mode 100644
index 000000000..32ae36622
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/simon-fisher.yml
@@ -0,0 +1,3 @@
+name: "Simon Fisher"
+twitter: "simfish85"
+bio: "Simon is a Solutions Architect at Chef, he has spent the past few years helping customers solve their Continuous Delivery problems with a variety of products and methods. In his spare time he also develops and maintains DAFNE Online, a site for people with Type 1 Diabetes in the UK. He also enjoys watching rugby, attempting to learn the piano, and learning how to be a new dad."
diff --git a/exampleSite/data/speakers/2016/amsterdam/stefan-stolzle.yml b/exampleSite/data/speakers/2016/amsterdam/stefan-stolzle.yml
new file mode 100644
index 000000000..82fa553f9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/stefan-stolzle.yml
@@ -0,0 +1,3 @@
+name: "Stefan Stolzle"
+twitter: ""
+bio: "Stefan has been a software developer, teacher and consultant for over 10 years, he believes \"code is beautiful\" and achieving it through collaboration. On the https://services.github.com team at GitHub his focus lies in helping companies to implement and migrate Git and GitHub, and to learn about the https://guides.github.com/introduction/flow/ to write beautiful software."
diff --git a/exampleSite/data/speakers/2016/amsterdam/takahiko-ito.yml b/exampleSite/data/speakers/2016/amsterdam/takahiko-ito.yml
new file mode 100644
index 000000000..5e203ec54
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/takahiko-ito.yml
@@ -0,0 +1,3 @@
+name: "Takahiko Ito"
+twitter: "takahi_i_en"
+bio: "Takahiko Ito received his Ph.D. in Engineering at the Nara Institute of Science and Technology, specializing in graph mining. He worked at FAST's (now Microsoft) R&D group as an Asian language NLP expert before joining Recruit Technologies as an R&D engineer."
diff --git a/exampleSite/data/speakers/2016/amsterdam/tiziano-perrucci.yml b/exampleSite/data/speakers/2016/amsterdam/tiziano-perrucci.yml
new file mode 100644
index 000000000..a02e2c397
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/tiziano-perrucci.yml
@@ -0,0 +1,3 @@
+name: "Tiziano Perrucci"
+twitter: "tizianoperrucci"
+bio: I'm an independent Italian software engineer working in the software industry for more than a decade. My expertise lies in backend and system integration, never the less I've a strong background (and passion) in automation and devops. I'm a co-founder of the StarterSquad community where I take part in several teams. We earn our living working for several startups around the world. I'm a collaborative problem solver with strong analytical skills and committed to a continuous improvement process."
diff --git a/exampleSite/data/speakers/2016/amsterdam/victoria-jeffrey.yml b/exampleSite/data/speakers/2016/amsterdam/victoria-jeffrey.yml
new file mode 100644
index 000000000..64e953bb8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/victoria-jeffrey.yml
@@ -0,0 +1,3 @@
+name: "Victoria Jeffrey"
+twitter: ""
+bio: "As a software engineer at Chef, Victoria has developed on Delivery and Compliance, spending her days in her code cave battling whatever dragons come her way. Prior to joining Chef, she was an assistant teacher at her son’s school, where she spent her days getting dirty in gardens and playing games. When she’s not hiding out in her code cave, you can find her hanging with family, admiring the baby lizards in the backyard, and wishing she had a koala pet."
diff --git a/exampleSite/data/speakers/2016/amsterdam/warner-moore.yml b/exampleSite/data/speakers/2016/amsterdam/warner-moore.yml
new file mode 100644
index 000000000..b970a8f49
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/warner-moore.yml
@@ -0,0 +1,3 @@
+name: "Warner Moore"
+twitter: "warnermoore"
+bio: "Warner Moore is a technology and information security leader who is passionate about innovation and entrepreneurship having worked with tech-focused businesses nearly his entire career. When not scaling platforms and teams at CoverMyMeds, he contributes back to the community by organizing Ohio LinuxFest and DevOpsDays Ohio. Additionally, he is co-founder of the LOPSA Columbus chapter and chairs the Leadership Committee."
diff --git a/exampleSite/data/speakers/2016/amsterdam/will-button.yml b/exampleSite/data/speakers/2016/amsterdam/will-button.yml
new file mode 100644
index 000000000..8270f97c4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/will-button.yml
@@ -0,0 +1,3 @@
+name: "Will Button"
+twitter: "wfbutton"
+bio: "Will Button is a DevOps advocate for Trax Technologies, working to integrate DevOps methods and ideology into development and operations teams. When not at work, he can be found sharing his knowledge through lessons at http://egghead.io and http://www.pluralsight.com as well as his blog and public speaking engagements."
diff --git a/exampleSite/data/speakers/2016/berlin/alexander-schwartz.yml b/exampleSite/data/speakers/2016/berlin/alexander-schwartz.yml
new file mode 100644
index 000000000..87a5baaa6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/alexander-schwartz.yml
@@ -0,0 +1,3 @@
+name: "Alexander Schwartz"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/anthony-stanton.yml b/exampleSite/data/speakers/2016/berlin/anthony-stanton.yml
new file mode 100644
index 000000000..8a6599cea
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/anthony-stanton.yml
@@ -0,0 +1,3 @@
+name: "Anthony Stanton"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/anup-bishnoi.yml b/exampleSite/data/speakers/2016/berlin/anup-bishnoi.yml
new file mode 100644
index 000000000..f75cc863b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/anup-bishnoi.yml
@@ -0,0 +1,3 @@
+name: "Anup Bishnoy"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/avishai-ish-shalom.yml b/exampleSite/data/speakers/2016/berlin/avishai-ish-shalom.yml
new file mode 100644
index 000000000..8927be7ea
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/avishai-ish-shalom.yml
@@ -0,0 +1,3 @@
+name: "Avishai Ish-Shalom"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/blerim-sheqa.yml b/exampleSite/data/speakers/2016/berlin/blerim-sheqa.yml
new file mode 100644
index 000000000..dc8f5b13c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/blerim-sheqa.yml
@@ -0,0 +1,3 @@
+name: "Blerim Sheqa"
+twitter: ""
+bio: "My name is Blerim Sheqa and I work as Senior Systems Engineer at NETWAYS. In the Managed Services department I am responsible for an infrastructure that hosts multiple customer setups. In the last couple of years I spent my time on creating a fully monitored environment by using Open Source tools like Icinga2, Puppet, Graphite and Logstash. Starting from now I will support the Icinga Team in the matter of implementation of interfaces and managing technical partnerships."
diff --git a/exampleSite/data/speakers/2016/berlin/david-schmitt.yml b/exampleSite/data/speakers/2016/berlin/david-schmitt.yml
new file mode 100644
index 000000000..89dd0df44
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/david-schmitt.yml
@@ -0,0 +1,3 @@
+name: "David Schmitt"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/eric-maxwell.yml b/exampleSite/data/speakers/2016/berlin/eric-maxwell.yml
new file mode 100644
index 000000000..b6cebaf5f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/eric-maxwell.yml
@@ -0,0 +1,3 @@
+name: "Eric Maxwell"
+twitter: ""
+bio: "Eric Maxwell is a Success Engineer at Chef Software and is focused on making companies more awesome by helping them 'do the DevOps' and enabling them to ship at velocity. In past lives, Eric was a back-end C# engineer, a big-data engineer playing in the Hadoop ecosystem, and a professional social engineer working in the InfoSec world."
diff --git a/exampleSite/data/speakers/2016/berlin/francois-le-droff.yml b/exampleSite/data/speakers/2016/berlin/francois-le-droff.yml
new file mode 100644
index 000000000..c9b36983c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/francois-le-droff.yml
@@ -0,0 +1,3 @@
+name: "François Le Droff"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/gerald-schmidt.yml b/exampleSite/data/speakers/2016/berlin/gerald-schmidt.yml
new file mode 100644
index 000000000..762e2ff67
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/gerald-schmidt.yml
@@ -0,0 +1,3 @@
+name: "Gerald Schmidt"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/hannah-foxwell.yml b/exampleSite/data/speakers/2016/berlin/hannah-foxwell.yml
new file mode 100644
index 000000000..621b5f0f8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/hannah-foxwell.yml
@@ -0,0 +1,3 @@
+name: "Hannah Foxwell"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/james-shubin.yml b/exampleSite/data/speakers/2016/berlin/james-shubin.yml
new file mode 100644
index 000000000..b2eca69b3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/james-shubin.yml
@@ -0,0 +1,3 @@
+name: "James Shubin"
+twitter: "purpleidea"
+bio: "James is a DevOps/Config mgmt. hacker and physiologist from Montreal, Canada. He often goes by @purpleidea on the internet, and writes 'The Technical Blog of James'. He currently works for Red Hat doing research and prototyping within systems engineering. He started a Next Generation Config Management prototype called mgmt. He studied Physiology at university and sometimes likes to talk about cardiology."
diff --git a/exampleSite/data/speakers/2016/berlin/johannes-nicolai.yml b/exampleSite/data/speakers/2016/berlin/johannes-nicolai.yml
new file mode 100644
index 000000000..b70cb1a50
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/johannes-nicolai.yml
@@ -0,0 +1,3 @@
+name: "Johannes Nicolai"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/konrad-hosemann.yml b/exampleSite/data/speakers/2016/berlin/konrad-hosemann.yml
new file mode 100644
index 000000000..a1e9375d5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/konrad-hosemann.yml
@@ -0,0 +1,3 @@
+name: "Konrad Hosemann"
+twitter: ""
+bio: "I’m a software engineer leading ImmobilienScout24's cloud team. We are paving the way for all our services into the public cloud. The team consists of operation managers, system engineers and software developers."
diff --git a/exampleSite/data/speakers/2016/berlin/kris-buytaert.yml b/exampleSite/data/speakers/2016/berlin/kris-buytaert.yml
new file mode 100644
index 000000000..40731b2b1
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/kris-buytaert.yml
@@ -0,0 +1,3 @@
+name: "Kris Buytaert"
+twitter: "KrisBuytaert"
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/martin-thalmann.yml b/exampleSite/data/speakers/2016/berlin/martin-thalmann.yml
new file mode 100644
index 000000000..2579d0f2a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/martin-thalmann.yml
@@ -0,0 +1,3 @@
+name: "Martin Thalmann"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/michael-huettermann.yml b/exampleSite/data/speakers/2016/berlin/michael-huettermann.yml
new file mode 100644
index 000000000..5fd866731
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/michael-huettermann.yml
@@ -0,0 +1,3 @@
+name: "Michael Hüttermann"
+twitter: ""
+bio: "Author of 'Agile ALM' and 'DevOps for Developers'"
diff --git a/exampleSite/data/speakers/2016/berlin/michal-bryxi.yml b/exampleSite/data/speakers/2016/berlin/michal-bryxi.yml
new file mode 100644
index 000000000..15ef7a46b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/michal-bryxi.yml
@@ -0,0 +1,3 @@
+name: "Michal Bryxi"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/nathen-harvey.yml b/exampleSite/data/speakers/2016/berlin/nathen-harvey.yml
new file mode 100644
index 000000000..96c0b9a64
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/nathen-harvey.yml
@@ -0,0 +1,3 @@
+name: "Nathen Harvey"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/peter-varhol.yml b/exampleSite/data/speakers/2016/berlin/peter-varhol.yml
new file mode 100644
index 000000000..fcbe43482
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/peter-varhol.yml
@@ -0,0 +1,3 @@
+name: "Peter Varhol"
+twitter: ""
+bio: "Peter Varhol is a well-known writer and speaker on software and technology topics, having authored dozens of articles and spoken at a number of industry conferences and webcasts. He has advanced degrees in computer science, applied mathematics, and psychology, and is currently a community evangelist at Dynatrace, an international software testing and application monitoring company. His past roles include technology journalist, software product manager, software developer, and university professor."
diff --git a/exampleSite/data/speakers/2016/berlin/rodrigo-campos.yml b/exampleSite/data/speakers/2016/berlin/rodrigo-campos.yml
new file mode 100644
index 000000000..9f786da87
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/rodrigo-campos.yml
@@ -0,0 +1,3 @@
+name: "Rodrigo Campos"
+twitter: ""
+bio: "I work as a Production Engineering manager at Facebook in London"
diff --git a/exampleSite/data/speakers/2016/berlin/romain-pelisse.yml b/exampleSite/data/speakers/2016/berlin/romain-pelisse.yml
new file mode 100644
index 000000000..49b849915
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/romain-pelisse.yml
@@ -0,0 +1,3 @@
+name: "Romain Pelisse"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/tp-honey.yml b/exampleSite/data/speakers/2016/berlin/tp-honey.yml
new file mode 100644
index 000000000..bc2be4b9e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/tp-honey.yml
@@ -0,0 +1,3 @@
+name: "TP Honey"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/boise/-kelsey-hightower.yml b/exampleSite/data/speakers/2016/boise/-kelsey-hightower.yml
new file mode 100644
index 000000000..8a194d4c2
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/-kelsey-hightower.yml
@@ -0,0 +1,12 @@
+---
+ name: Kelsey Hightower
+ twitter: kelseyhightower
+ bio: |
+ Kelsey has worn every hat possible throughout his career in tech and
+ enjoys leadership roles focused on making things happen and shipping
+ software.
+
+ Kelsey is a strong open source advocate focused on building simple tools
+ that make people smile. When he is not slinging Go code you can catch
+ him giving technical workshops covering everything from Programming,
+ System Administration and Kubernetes.
diff --git a/exampleSite/data/speakers/2016/boise/-vm-brasseur.yml b/exampleSite/data/speakers/2016/boise/-vm-brasseur.yml
new file mode 100644
index 000000000..8d7b7c130
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/-vm-brasseur.yml
@@ -0,0 +1,12 @@
+---
+ name: VM Brasseur
+ twitter: vmbrasseur
+ bio: |
+ VM Brasseur (aka Vicky) is a manager of technical people, projects,
+ processes, products, and p^Hbusinesses. In her nearly 20 years in the
+ tech industry, Vicky has been an analyst, programmer, product manager,
+ software engineering manager, technical business consultant, and
+ director of software engineering. Currently, she is a senior
+ engineering manager at Hewlett Packard Enterprise, serving a team of
+ developers 100% dedicated to upstream open source development on
+ OpenStack. Vicky [occasionally blogs](http://anonymoushash.vmbrasseur.com/).
diff --git a/exampleSite/data/speakers/2016/boise/alan-kraft.yml b/exampleSite/data/speakers/2016/boise/alan-kraft.yml
new file mode 100644
index 000000000..e2931ac6d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/alan-kraft.yml
@@ -0,0 +1,9 @@
+---
+ name: "Alan Kraft"
+ twitter: ""
+ bio: |
+ After an early career in UNIX and Linux system administration, Alan now
+ works on hybrid cloud computing, Linux Containers, and DevOps at USPTO.
+ His current interests include infrastructure as code, systems thinking
+ & learning organizations, and the application of concepts from safety
+ science and complexity theory to DevOps.
diff --git a/exampleSite/data/speakers/2016/boise/baruch-sadogursky.yml b/exampleSite/data/speakers/2016/boise/baruch-sadogursky.yml
new file mode 100644
index 000000000..97e13fbff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/baruch-sadogursky.yml
@@ -0,0 +1,15 @@
+---
+ name: "Baruch Sadogursky"
+ twitter: "jbaruch"
+ bio: |
+ Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate of JFrog,
+ the creators of Artifactory Binary Repository, the home of Bintray, and
+ JavaOne 2011 Duke Choice Awards winner.
+
+ For a living he hangs out with the JFrog tech leaders, writes some code
+ around Artifactory and Bintray, and then speaks and blogs about all
+ that. He does it repeatedly for the last 10 years and enjoys every
+ moment of it.
+
+ Baruch is [@jbaruch](https://twitter.com/jbaruch) on twitter and mostly
+ blogs on http://blog.bintray.com and http://blogs.jfrog.org.
diff --git a/exampleSite/data/speakers/2016/boise/ben-rockwood.yml b/exampleSite/data/speakers/2016/boise/ben-rockwood.yml
new file mode 100644
index 000000000..3665dce20
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/ben-rockwood.yml
@@ -0,0 +1,12 @@
+---
+ name: "Ben Rockwood"
+ twitter: "benr"
+ bio: |
+ Ben Rockwood is the Director of IT & Operations at Chef. He has been a
+ UNIX System Administrator for over 20 years and an Operations
+ Management junkie for the last 8. Between 2006 and 2014 he was the
+ Director of Operations at Joyent, one of the first IaaS Cloud
+ providers. He recently moved to Seattle with his super-hot wife and
+ their 5 children.
+
+ Ben blogs at http://cuddletech.com/.
diff --git a/exampleSite/data/speakers/2016/boise/caskey-dickson.yml b/exampleSite/data/speakers/2016/boise/caskey-dickson.yml
new file mode 100644
index 000000000..daa80415e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/caskey-dickson.yml
@@ -0,0 +1,16 @@
+---
+ name: "Caskey Dickson"
+ twitter: "caskey"
+ bio: |
+ Caskey L. Dickson is a Site Reliability Engineer at Microsoft where he
+ is part of the leadership team reinventing operations at Azure. Before
+ that he was at Google where he worked as an SRE/SWE writing and
+ maintaining monitoring services that operate at “Google scale” as well
+ as a few business intelligence pipelines and maybe a script or two. He
+ has worked in online services since 1995 when he turned up his first
+ web server and has been online ever since. Before working at Google, he
+ was a senior developer at Symantec, wrote software for various Internet
+ tartups such as CitySearch and CarsDirect, ran a consulting company,
+ and even taught undergraduate and graduate computer science at Loyola
+ Marymount University. He has a B.S. in Computer Science, a Masters in
+ Systems Engineering, and an M.B.A from Loyola Marymount.
diff --git a/exampleSite/data/speakers/2016/boise/corey-quinn.yml b/exampleSite/data/speakers/2016/boise/corey-quinn.yml
new file mode 100644
index 000000000..543f9ef32
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/corey-quinn.yml
@@ -0,0 +1,13 @@
+---
+ name: Corey Quinn
+ twitter: QuinnyPig
+ bio: |
+ Principal at The Quinn Advisory Group, Corey has a history as an
+ engineering manager, public speaker, and advocate for business
+ resilience through processes that aren't actively ridiculous. He
+ specializes in helping FinTech companies leverage cloud technologies
+ while managing and mitigating risk.
+
+ Outside of his professional work, Corey is known for overdressing,
+ telling entertaining stories, and carrying a cigarette case full of
+ drink umbrellas.
diff --git a/exampleSite/data/speakers/2016/boise/dan-isla.yml b/exampleSite/data/speakers/2016/boise/dan-isla.yml
new file mode 100644
index 000000000..c9da15713
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/dan-isla.yml
@@ -0,0 +1,13 @@
+---
+ name: "Dan Isla"
+ twitter: "danisla"
+ bio: |
+ Dan Isla is a Data Scientist in the Office of Chief Technology and
+ Innovation at NASA's Jet Propulsion Laboratory. For the past 7 years,
+ Isla has worked on the teams that build, launch and operate robotic
+ spacecraft throughout the solar system. Legacy is everywhere in
+ Aerospace and after seeing the scale of the data problems and
+ challenges that face our missions, Isla has now dedicated his time to
+ infusing the latest big data tools, cloud computing solutions, and
+ container platforms to revolutionize how we operate interplanetary
+ spacecraft.
diff --git a/exampleSite/data/speakers/2016/boise/darryl-bowler.yml b/exampleSite/data/speakers/2016/boise/darryl-bowler.yml
new file mode 100644
index 000000000..665483b5e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/darryl-bowler.yml
@@ -0,0 +1,11 @@
+---
+ name: "Darryl Bowler"
+ twitter: "darrylbowler"
+ bio: |
+ Darryl is a manager within Accenture DevOps practice and his working
+ roles include project management, product development, engagement
+ management and architecture. In the last six years, Darryl’s primary
+ focus has been delivering client value through agile methodologies and
+ DevOps. Currently, he is responsible for establishing a DevOps
+ capability within a digital transformation program for a major mobile
+ communications provider.
diff --git a/exampleSite/data/speakers/2016/boise/dave-hahn.yml b/exampleSite/data/speakers/2016/boise/dave-hahn.yml
new file mode 100644
index 000000000..16b91d6a0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/dave-hahn.yml
@@ -0,0 +1,7 @@
+---
+ name: "Dave Hahn"
+ twitter: "relix42"
+ bio: |
+ Dave Hahn is a Sr SRE on the Critical Operations & Reliability
+ Engineering team at Netflix. The CORE team is on the fore front of
+ availability for Netflix streaming service. Dave is very serious.
diff --git a/exampleSite/data/speakers/2016/boise/dave-harrison.yml b/exampleSite/data/speakers/2016/boise/dave-harrison.yml
new file mode 100644
index 000000000..0e3735b43
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/dave-harrison.yml
@@ -0,0 +1,15 @@
+---
+ name: Dave Harrison
+ twitter: ""
+ bio: |
+ Dave is an Application Development Manager at Microsoft where he
+ utilizes his expertise and technical background to help solve dev team
+ maturity bottlenecks and help clients deliver better software, faster
+ to add more business value.
+
+ At heart he's a developer and loves solving problems creatively. Coming
+ from the relational database/data warehousing ranks, he's been writing
+ applications for about 20 years now with strong experience in a broad
+ variety of tools within the Microsoft stack. He's crazy about ALM/SDLC
+ and DevOps concepts and frequently gives presentations and chalktalks
+ on implementing Agile in the real world.
diff --git a/exampleSite/data/speakers/2016/boise/gareth-greenaway.yml b/exampleSite/data/speakers/2016/boise/gareth-greenaway.yml
new file mode 100644
index 000000000..68ab391c4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/gareth-greenaway.yml
@@ -0,0 +1,5 @@
+---
+ name: "Gareth Greenaway"
+ twitter: "garethgreenaway"
+ bio: |
+ Lead DevOps Engineer at Croscon & Core contributor to Salt Stack.
diff --git a/exampleSite/data/speakers/2016/boise/gerie-owen.yml b/exampleSite/data/speakers/2016/boise/gerie-owen.yml
new file mode 100644
index 000000000..fc424e22c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/gerie-owen.yml
@@ -0,0 +1,15 @@
+---
+ name: "Gerie Owen"
+ twitter: "GerieOwen"
+ bio: |
+ Gerie Owen is a test architect at Eversource Energy, Certified
+ ScrumMaster, conference presenter, and author on testing/test
+ management topics. She is developing a test center of excellence and
+ consults on test processes and tools. Gerie manages large, complex
+ projects involving multiple applications; coordinates test teams across
+ multiple time zones; and delivers high-quality projects on time and
+ within budget. She enjoys mentoring new QA leads and brings a cohesive
+ team approach to testing. Learn more about Gerie on her
+ [website](http://gerieowen.com/), her
+ [Software Testing in the Trenches](http://testinggirl.wordpress.com/)
+ blog, and on Twitter [@GerieOwen](https://twitter.com/gerieowen).
diff --git a/exampleSite/data/speakers/2016/boise/jason-hand.yml b/exampleSite/data/speakers/2016/boise/jason-hand.yml
new file mode 100644
index 000000000..907b2e016
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jason-hand.yml
@@ -0,0 +1,12 @@
+---
+ name: "Jason Hand"
+ twitter: "jasonhand"
+ bio: |
+ DevOps Evangelist at VictorOps, organizer of DevOpsDays - Rockies,
+ author of "ChatOps for Dummies", and host of a number of DevOps related
+ events in the Denver/Boulder area. Jason has spent the last 8 months
+ presenting and building content on a number of DevOps topics such as
+ Blameless Post-mortems, ChatOps, and the value of context within
+ incident management. A frequent speaker at DevOps events around the
+ country, Jason enjoys talking to audiences large and small on a variety
+ of technical and non-technical subjects.
diff --git a/exampleSite/data/speakers/2016/boise/jean-bennett.yml b/exampleSite/data/speakers/2016/boise/jean-bennett.yml
new file mode 100644
index 000000000..22f08ed35
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jean-bennett.yml
@@ -0,0 +1,4 @@
+---
+ name: "Jean Bennett"
+ twitter: "JeanBennett01"
+ bio: ""
diff --git a/exampleSite/data/speakers/2016/boise/jeff-anderson.yml b/exampleSite/data/speakers/2016/boise/jeff-anderson.yml
new file mode 100644
index 000000000..7f8ffe2d8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jeff-anderson.yml
@@ -0,0 +1,7 @@
+---
+ name: "Jeff Anderson"
+ twitter: "programm3rq"
+ bio: |
+ Jeff Anderson is a Developer Support Engineer at Docker. He has a
+ background in Linux system operations, configuration management, and
+ automation.
diff --git a/exampleSite/data/speakers/2016/boise/jonah-horowitz.yml b/exampleSite/data/speakers/2016/boise/jonah-horowitz.yml
new file mode 100644
index 000000000..c08757de8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jonah-horowitz.yml
@@ -0,0 +1,8 @@
+---
+ name: "Jonah Horowitz"
+ twitter: "jonahhorowitz"
+ bio: |
+ Jonah Horowitz is a Senior Site Reliability Architect at Netflix with
+ over 20 years of experience keeping servers and sites online. He
+ started with a home-built BBS and has worked at both large and small
+ tech companies including Walmart.com, Looksmart, and Quantcast.
diff --git a/exampleSite/data/speakers/2016/boise/leonid-igolnik.yml b/exampleSite/data/speakers/2016/boise/leonid-igolnik.yml
new file mode 100644
index 000000000..5b4dd9842
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/leonid-igolnik.yml
@@ -0,0 +1,19 @@
+---
+ name: "Leonid Igolnik"
+ twitter: "ligolnik"
+ bio: |
+ Leonid is technologist blending product development, product management
+ and product operations at scale. In his current role as a Vice
+ President of Engineering with CA Technologies he is responsible for
+ product development of SaaS applications for the Enterprise Security
+ space. He has spend his entire professional career building on-line
+ applications starting his career at one of the earliest internet
+ service providers in Israel. Leonid first started building large scale
+ applications in Java in 2002 while working for the 2nd largest domain
+ registrar at the time at Tucows/OpenSRS where he led the platform team.
+ Subsequently to that he held several technology leadership roles with
+ companies in Canada and US. Most recently Leonid has been responsible
+ for engineering teams at Taleo (acquired by Oracle) building
+ applications that help millions of people find jobs that have
+ propelled the company to a position of one of the 4 largest SaaS
+ companies in the world.
diff --git a/exampleSite/data/speakers/2016/boise/mary-younce.yml b/exampleSite/data/speakers/2016/boise/mary-younce.yml
new file mode 100644
index 000000000..b9eff73aa
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/mary-younce.yml
@@ -0,0 +1,9 @@
+---
+ name: Mary Younce
+ bio: |
+ As information technology risk and compliance professional, Mary has
+ had the good fortune to lead teams of talented technologists on
+ devising solutions that reduce risk and meet company goals. She’s
+ contributed over 20 years in IT operations and security roles. Mary
+ encourages technical and professional resiliency to balance
+ requirements and safeguards.
diff --git a/exampleSite/data/speakers/2016/boise/matthew-barker.yml b/exampleSite/data/speakers/2016/boise/matthew-barker.yml
new file mode 100644
index 000000000..48d60a00f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/matthew-barker.yml
@@ -0,0 +1,10 @@
+---
+ name: "Matthew Barker"
+ twitter: "matthewabq"
+ bio: |
+ As a experienced Solutions Architect and Sales Engineer, Matthew helps
+ companies efficiently secure their applications. His broad-based
+ experience in open source software and rapid application development
+ combined with background in software security enables him to provide
+ insightful, technical guidance to companies desiring to produce secure
+ applications of high quality and with minimal license risk.
diff --git a/exampleSite/data/speakers/2016/boise/peter-varhol.yml b/exampleSite/data/speakers/2016/boise/peter-varhol.yml
new file mode 100644
index 000000000..029c10f24
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/peter-varhol.yml
@@ -0,0 +1,15 @@
+---
+ name: "Peter Varhol"
+ twitter: "pvarhol"
+ bio: |
+ Peter Varhol is principal technology evangelist at Technology Strategy
+ Research and a consulting QA lead for a leading digital design firm. An
+ accomplished and frequent speaker at technology conferences and user
+ groups, Peter’s topics cover software development to testing and
+ application lifecycle. As a technology journalist and thought leader,
+ he has authored hundreds of articles, white papers, and blog posts on
+ software development, testing, and related topics. His past roles
+ include technology journalist, software product manager, software
+ developer, and university professor. Learn more about Peter on his
+ [Cutting Edge Computing blog](https://pvarhol.wordpress.com/) and on
+ Twitter [@pvarhol](https://twitter.com/pvarhol).
diff --git a/exampleSite/data/speakers/2016/boise/seth-falcon.yml b/exampleSite/data/speakers/2016/boise/seth-falcon.yml
new file mode 100644
index 000000000..86ab6c539
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/seth-falcon.yml
@@ -0,0 +1,12 @@
+---
+ name: "Seth Falcon"
+ twitter: "sfalcon"
+ bio: |
+ A product focused engineering leader who builds teams that consistently
+ deliver valuable, high quality software at velocity.
+
+ Seth believes the essential elements for a high performing team are
+ trust, commitment to learning and experimentation, mechanisms for
+ measuring outcomes, and clear communication. He's helped teams increase
+ their effectiveness as an individual contributor, an engineering
+ manager, and as a leader of managers.
diff --git a/exampleSite/data/speakers/2016/boston/andreas-grabner.yml b/exampleSite/data/speakers/2016/boston/andreas-grabner.yml
new file mode 100644
index 000000000..957614464
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/andreas-grabner.yml
@@ -0,0 +1,12 @@
+bio: "Andreas Grabner is a performance enthusiast who has been working in this field\
+ \ for the last fifteen+ years. He was a developer, tester, architect and product\
+ \ evangelist for several testing and diagnostics companies such as Segue, Borland,\
+ \ Compuware and Dynatrace. In these days Andreas helps organizations finding the\
+ \ performance, scalability and architectural problems in their applications. He\
+ \ is taking his knowledge to teach others on how to spot and avoid these problems.\
+ \ He is doing that by speaking at different meetups, user groups and international\
+ \ conferences such as Star, STPCon, Agile Testing Days, Swiss Testing Day, Java\
+ \ South Africa, JavaOne, \u2026 "
+name: Andreas Grabner
+twitter: grabnerandi
+website: http://blog.dynatrace.com
diff --git a/exampleSite/data/speakers/2016/boston/andy-rosequist.yml b/exampleSite/data/speakers/2016/boston/andy-rosequist.yml
new file mode 100644
index 000000000..fe145571a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/andy-rosequist.yml
@@ -0,0 +1,5 @@
+bio: Andy is the Director of IT Operations at Zipcar. He's very passionate about collaboration
+ and transparency, as well as beards.
+name: Andy Rosequist
+twitter: blond_baron
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/anjuan-simmons.yml b/exampleSite/data/speakers/2016/boston/anjuan-simmons.yml
new file mode 100644
index 000000000..86548766a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/anjuan-simmons.yml
@@ -0,0 +1,20 @@
+bio: "Anjuan Simmons is a technologist with a successful track record of delivering\
+ \ technology solutions from the user interface to the database. He is currently\
+ \ a software project manager and Certified Scrum Master at a leading construction\
+ \ software manufacturer, and he has previously worked as an executive for Accenture,\
+ \ Deloitte, and Infosys, all multi-billion dollar technology services companies\
+ \ with hundreds of clients around the world. \r\n\r\nAnjuan is also an energetic\
+ \ and informative speaker who often presents at conferences, seminars, schools,\
+ \ and community events. He is a sought after thought leader on Agile software development,\
+ \ design, diversity, and leadership. Drawing from his work experience as well as\
+ \ his educational background, Anjuan delivers presentations that focus on facts\
+ \ and provide simple explanations of complex ideas. \r\n\r\nAnjuan has an undergraduate\
+ \ degree in electrical engineering from the University of Texas at Austin and an\
+ \ MBA from Texas A&M University (where he was the first person voted by his fellow\
+ \ MBA students to serve as Student Speaker during their graduation ceremony). He\
+ \ lives in Houston with his beautiful wife and three amazing kids. Anjuan's hobbies\
+ \ include reading, writing, travel, and exercise. His has vowed to never again speak\
+ \ the name of his favorite member of One Direction aloud."
+name: Anjuan Simmons
+twitter: anjuan
+website: http://www.AnjuanSimmons.com
diff --git a/exampleSite/data/speakers/2016/boston/barak-chamo.yml b/exampleSite/data/speakers/2016/boston/barak-chamo.yml
new file mode 100644
index 000000000..45fa67c4e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/barak-chamo.yml
@@ -0,0 +1,8 @@
+bio: "Barak is a passionate software developer, entrepreneur and digital artist. He's\
+ \ been working with and building startups in Tel-Aviv, London and New-York for the\
+ \ past 6 years.\r\n\r\nAn avid web developer and creative coder, he enjoys exploring\
+ \ the connection between art and technology in audio, visual and physical form and\
+ \ creates new and exciting digital experiences."
+name: Barak Chamo
+twitter: barakchamo
+website: http://github.com/barakchamo
diff --git a/exampleSite/data/speakers/2016/boston/corey-quinn.yml b/exampleSite/data/speakers/2016/boston/corey-quinn.yml
new file mode 100644
index 000000000..b9cf57619
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/corey-quinn.yml
@@ -0,0 +1,14 @@
+bio: "Corey has a long and storied history as a consultant -- long, in that every\
+ \ year he did it felt like three years, and storied, in that he's got a few. Prior\
+ \ to his current role as Director of DevOps at FutureAdvisor, he spent most of the\
+ \ past few years at a Bay Area consulting firm, where he served as a systems architect,\
+ \ ad-hoc recruiter, advocate for driving transformational change throughout organizations,\
+ \ and (due to a misunderstanding around what a \"standup meeting\" really was) an\
+ \ improvisational comic. One of the early developers behind Saltstack, Corey also\
+ \ has a rich history of contributing to various open source projects.\r\n\r\nCorey's\
+ \ hobbies include motorcycles, building custom keyboards, and drinking whiskey--\
+ \ it's a shame that they all don't work well together. He lives in San Francisco\
+ \ with his wife and two rodents of unusual size masquerading as dogs."
+name: Corey Quinn
+twitter: QuinnyPig
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/david-blank-edelman.yml b/exampleSite/data/speakers/2016/boston/david-blank-edelman.yml
new file mode 100644
index 000000000..b5fec2dd0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/david-blank-edelman.yml
@@ -0,0 +1,10 @@
+bio: David is the Technical Evangelist at Apcera. He has spent close to thirty years
+ in the systems administration/DevOps/SRE field in large multiplatform environments
+ including Brandeis University, Cambridge Technology Group, MIT Media Laboratory
+ and Northeastern University. He is the author of the O'Reilly Otter book (Automating
+ System Administration with Perl) and is a frequent invited speaker at conferences
+ in the field. David is honored to serve on the USENIX Board of Directors. He prefers
+ to pronounce Evangelist with a hard 'g'.
+name: David Blank-Edelman
+twitter: otterbook
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/david-fredricks.yml b/exampleSite/data/speakers/2016/boston/david-fredricks.yml
new file mode 100644
index 000000000..d0f1e7fa0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/david-fredricks.yml
@@ -0,0 +1,10 @@
+bio: 'David provides consultative services to organizations on how to
+ successfully grow technical teams. His services help leaders understand current
+ candidate markets and offer realistic solutions for solving critical hiring
+ challenges. David helps clients by creating SMART personalized plans and
+ delivery models to successfully on board the right engineers. If you are
+ struggling to identify, attract and hire technical folks. Give him a call to
+ set up a meeting and discuss your situation.'
+name: David Fredricks
+twitter: 'dfreddy76'
+website: https://www.linkedin.com/pulse/devops-needs-great-managers-david-fredricks?trk=mp-author-card
diff --git a/exampleSite/data/speakers/2016/boston/elliot-murphy.yml b/exampleSite/data/speakers/2016/boston/elliot-murphy.yml
new file mode 100644
index 000000000..5bf1dfac7
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/elliot-murphy.yml
@@ -0,0 +1,10 @@
+name: "Eliot Murphy"
+twitter: "sstatik"
+bio: "Elliot is the CEO of Kindly Ops, a DevOps and security firm focused on\
+ \ reducing the cost of healthcare innovation. Over the last year he has assisted\
+ \ organizations with operation, scaling, and 3rd party risk assessment of mission\
+ \ critical systems that conduct medical research, perform real time malware\
+ \ defense, process prescription refills, deliver therapy, and store psychiatric\
+ \ records.
He has real-world deployment experience with Kubernetes, Mesos, ECS\
+ \ and Amazon, Google and Azure clouds."
+website: "http://blog.elliotmurphy.com/"
diff --git a/exampleSite/data/speakers/2016/boston/james-meickle.yml b/exampleSite/data/speakers/2016/boston/james-meickle.yml
new file mode 100644
index 000000000..cd4dfadc8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/james-meickle.yml
@@ -0,0 +1,6 @@
+bio: "Site Reliability Engineer at the Center for Brain Science at Harvard University
\
+ \
+ \ As an engineer with a background in psychology and political science, James has a strong interest in combining code optimizations and people optimizations. He currently works as a site reliability engineer at the Center for Brain Science at Harvard University where he is responsible for managing fMRI brain scan data, architecting processing pipelines, and deploying statistical software. Past roles include developer evangelist at web performance startup AppNeta and release engineer at Romney for President ’12. In his spare time, James is also a conference organizer for DevOpsDays Boston."
+name: James Meickle
+twitter: jmeickle
+website: http://www.test.com
diff --git a/exampleSite/data/speakers/2016/boston/jill-jubinski.yml b/exampleSite/data/speakers/2016/boston/jill-jubinski.yml
new file mode 100644
index 000000000..53ad26a9f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/jill-jubinski.yml
@@ -0,0 +1,4 @@
+name: "Jill Jubinski"
+twitter: "jilljubs"
+bio: "Jill Jubinski is a recruiting veteran with over 6 years of recruiting experience in the community. She received her Masters in Industrial/Organizational Psychology with plans to change the way organizations treated their employees. When that didn’t work out she started recruiting ;-) Jill leans on her strength in relationship building as a jumping off point to help organizations build amazing teams and genuinely cares about the health and wellness of an organization's culture. She is also known to chat incessantly about her dogs and give hugs like they are going out of style."
+website: "https://theunrecruiter.wordpress.com/"
diff --git a/exampleSite/data/speakers/2016/boston/john-downey.yml b/exampleSite/data/speakers/2016/boston/john-downey.yml
new file mode 100644
index 000000000..14ae32e16
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/john-downey.yml
@@ -0,0 +1,8 @@
+bio: John Downey is the Security Lead at Braintree (which is owned by PayPal). Braintree
+ helps businesses accept credit card payments online with great development tools
+ and first class support. There he has worked on their highly available infrastructure
+ and integrations into the banking system. In his free time he contributes to open
+ source projects and mentors high school students in the FIRST Robotics Competition.
+name: John Downey
+twitter: jtdowney
+website: http://jtdowney.com
diff --git a/exampleSite/data/speakers/2016/boston/kirsten-hunter.yml b/exampleSite/data/speakers/2016/boston/kirsten-hunter.yml
new file mode 100644
index 000000000..0e7f413bf
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/kirsten-hunter.yml
@@ -0,0 +1,9 @@
+bio: Kirsten Hunter is an unapologetic hacker and passionate advocate for the development
+ community. Her technical interests range from graph databases to cloud services,
+ and her experience supporting and evangelizing REST APIs has given her a unique
+ perspective on developer success. In her copious free time she's a gamer, fantasy
+ reader, and all around rabble-rouser. Code samples, recipes, and philosophical musings
+ can be found at http://www.princesspolymath.com.
+name: Kirsten Hunter
+twitter: synedra
+website: http://www.princesspolymath.com
diff --git a/exampleSite/data/speakers/2016/boston/leon-fayer.yml b/exampleSite/data/speakers/2016/boston/leon-fayer.yml
new file mode 100644
index 000000000..47bd96baa
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/leon-fayer.yml
@@ -0,0 +1,14 @@
+bio: Leon's two decades of expertise were concentrated on architecting and operating
+ complex, web-based systems to withstand crushing traffic (often unexpectedly). Over
+ the years, he's had a somewhat unique opportunity to design and build systems that
+ run some of the most visited websites in the world. While his core expertise is
+ in application development, he works his way around the whole technology stack from
+ system architecture to databases design and optimization to front/back-end programming.
+ He's considered a professional naysayer by peers and has the opinion that nothing
+ really works until it works for at least a million people. In his current role Leon
+ advises companies about critical aspects of project strategies and and concentrates
+ on educating others by writing and speaking about industry trends and best practices,
+ sharing his experience as related to designing and operating architectures at scale.
+name: Leon Fayer
+twitter: papa_fire
+website: http://fayerplay.com
diff --git a/exampleSite/data/speakers/2016/boston/liz-frost.yml b/exampleSite/data/speakers/2016/boston/liz-frost.yml
new file mode 100644
index 000000000..5345a2d31
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/liz-frost.yml
@@ -0,0 +1,6 @@
+bio: Liz is a queer trans woman with pink hair and a taste for sour candy. She's a
+ software engineer at Heroku, previously at Activision, and in her spare time likes
+ walking her dog and taking selfies. You can find her on Twitter at @stillinbeta.
+name: Liz Frost
+twitter: stillinbeta
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/matthew-barr.yml b/exampleSite/data/speakers/2016/boston/matthew-barr.yml
new file mode 100644
index 000000000..ca5cfe2c2
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/matthew-barr.yml
@@ -0,0 +1,6 @@
+bio: Matthew Barr is an architect for the Developer Productivity at Akamai. In the
+ past, he's worked as a sysadmin & "devops engineer" for banks & startups, large
+ & small companies.
+name: Matthew Barr
+twitter: matthewbarr
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/michael-kristan.yml b/exampleSite/data/speakers/2016/boston/michael-kristan.yml
new file mode 100644
index 000000000..cac2fa595
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/michael-kristan.yml
@@ -0,0 +1,10 @@
+bio: "Michael Kristan is a Software Systems Engineer at MITRE's Center for National\
+ \ Security. Michael currently serves as a thought leader in cloud computing and\
+ \ DevOps. He regularly consults on a variety of projects and provides guidance,\
+ \ support, and systems engineering expertise as people explore and transform their\
+ \ IT and software development efforts to ones that leverage continuous delivery\
+ \ and elastic compute environments. He has been featured as a session lead at the\
+ \ Federal Cloud Computing Summit.\r\n\r\nhttps://www.mitre.org/careers/working-at-mitre/employee-voices/mitre-engineers-versatility-garners-results"
+name: Michael Kristan
+twitter: ''
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/rafael-benevides.yml b/exampleSite/data/speakers/2016/boston/rafael-benevides.yml
new file mode 100644
index 000000000..b1bc75d19
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/rafael-benevides.yml
@@ -0,0 +1,10 @@
+bio: Rafael Benevides is a Director of Developer Experience at Red Hat. In his current
+ role he helps developers worldwide to be more effective in software development,
+ and he also promotes tools and practices that help them to be more productive. He
+ worked in several fields including application architecture and design. Besides
+ that, he is a member of Apache DeltaSpike PMC - a Duke's Choice Award winner project.
+ And a speaker in conferences like JUDCon, TDC, JavaOne and Devoxx. [Twitter](https://twitter.com/rafabene)
+ | [LinkedIn](https://www.linkedin.com/in/rafaelbenevides) | [rafabene.com](http://rafabene.com/about/)
+name: Rafael Benevides
+twitter: rafabene
+website: http://rafabene.com/
diff --git a/exampleSite/data/speakers/2016/boston/sara-jarjoura.yml b/exampleSite/data/speakers/2016/boston/sara-jarjoura.yml
new file mode 100644
index 000000000..7bcbf2b6e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/sara-jarjoura.yml
@@ -0,0 +1,7 @@
+bio: 'I''m a DevOps Engineer, and I''m happiest when spawning invisible computers
+ in "the cloud." I started out in the tech field in 2007 when I attended my first
+ web development meetup in Providence and learned what "WYSIWYG" meant. Nowadays
+ you can find me at DevOps meetups or hanging around in the Seaport district. '
+name: Sara Jarjoura
+twitter: saranicole
+website: http://sarastreeter.com
diff --git a/exampleSite/data/speakers/2016/boston/spencer-krum.yml b/exampleSite/data/speakers/2016/boston/spencer-krum.yml
new file mode 100644
index 000000000..872d40a36
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/spencer-krum.yml
@@ -0,0 +1,12 @@
+bio: "Spencer (nibalizer) Krum (http://spencerkrum.com) has been sysoping Linux since\
+ \ 2010. He works for IBM contributing upstream to OpenStack and Puppet. Spencer\
+ \ is a core contributor to the OpenStack Infrastructure Project. Spencer coordinates\
+ \ the local DevOps user group in Portland and volunteers for an ops-training program\
+ \ at Portland State University called the Braindump. Spencer is a published author\
+ \ and frequent speaker at technical conferences. Spencer is a maintainer for the\
+ \ voxpupuli effort(https://voxpupuli.org), which attempts to bring together a network\
+ \ of Puppet developers, modules, and infrastructure.\r\n\r\nSpencer lives and works\
+ \ in Portland, Oregon where he enjoys tennis, cheeseburgers and StarCraft II."
+name: Spencer Krum
+twitter: nibalizer
+website: http://spencerkrum.com
diff --git a/exampleSite/data/speakers/2016/boston/steve-faulkner.yml b/exampleSite/data/speakers/2016/boston/steve-faulkner.yml
new file mode 100644
index 000000000..e3821dacd
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/steve-faulkner.yml
@@ -0,0 +1,5 @@
+bio: Steve Faulkner once went to the South Pole. Now he is Director of Systems Engineering
+ at Bustle. A bunch of stuff happened in between! Life is crazy like that.
+name: Steve Faulkner
+twitter: southpolesteve
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/tracy-osborn.yml b/exampleSite/data/speakers/2016/boston/tracy-osborn.yml
new file mode 100644
index 000000000..478651ffa
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/tracy-osborn.yml
@@ -0,0 +1,7 @@
+bio: Tracy Osborn is a designer, developer, and entreprenerd living in the California
+ Bay Area. She's a part of the developer relations team at DreamFactory, the author
+ of Hello Web App, and creator of WeddingLovely. She's also an avid outdoorswoman
+ and would love to go on a hike with you.
+name: Tracy Osborn
+twitter: limedaring
+website: http://limedaring.com
diff --git a/exampleSite/data/speakers/2016/brasilia/arthur-furlan.yml b/exampleSite/data/speakers/2016/brasilia/arthur-furlan.yml
new file mode 100644
index 000000000..def9fe315
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/arthur-furlan.yml
@@ -0,0 +1,3 @@
+name: "Arthur Furlan"
+twitter: "arthurfurlan"
+bio: "Formado em Ciência da Computação pela UFPR, trabalha com tecnologia há mais de 12 anos e com DevOps desde 2010. Já contribuiu como SysAdmin em diversos projetos de Software Livre como BrOffice.org, PostgreSQL-BR, Mozila-BR, Django Brasil, FLISOL e desde 2013 atua como empreendedor na Configr."
diff --git a/exampleSite/data/speakers/2016/brasilia/barbara-hartmann.yml b/exampleSite/data/speakers/2016/brasilia/barbara-hartmann.yml
new file mode 100644
index 000000000..0fc89bf45
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/barbara-hartmann.yml
@@ -0,0 +1,3 @@
+name: "Bárbara Hartmann"
+twitter: "bahartmann"
+bio: "Bárbara é técnica em informática, desenvolvedora e consultora na ThoughtWorks. Já atuou com clientes de dentro e fora do Brasil, com times remotos e co-locados. Desenvolve em linguagens como Ruby e Javascript. Além disso, busca participar de projetos que fortaleçam a diversidade na TI. Bárbara acredita no poder de um código bem escrito e na mudança social através da tecnologia."
diff --git a/exampleSite/data/speakers/2016/brasilia/cezar-sa-spinola.yml b/exampleSite/data/speakers/2016/brasilia/cezar-sa-spinola.yml
new file mode 100644
index 000000000..678b391c9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/cezar-sa-spinola.yml
@@ -0,0 +1,3 @@
+name: "Cézar Sá Spinola"
+twitter: "cezarsa"
+bio: "Cezar Sá Espinola é um desenvolvedor com mais de 10 anos de experiência e contribuição em vários projetos open-source. Hoje faz parte da equipe do tsuru e atua tanto em seu desenvolvimento como no suporte ao seu uso dentro da Globo.com. Apesar de ser mais Dev do que Ops o trabalho no tsuru e na infraestrutura da Globo.com equilibra bem isso e faz enxergar que Devops deveria mesmo ser uma palavra só."
diff --git a/exampleSite/data/speakers/2016/brasilia/diego-dorgam-aguilera.yml b/exampleSite/data/speakers/2016/brasilia/diego-dorgam-aguilera.yml
new file mode 100644
index 000000000..3c3dbcc3b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/diego-dorgam-aguilera.yml
@@ -0,0 +1,3 @@
+name: "Diego Dorgam Aguilera"
+twitter: "diegodorgam"
+bio: "Diego é um experiente gestor de projetos que vive em Brasília. Fã de tecnologias, programação e desenvolvimento web, também interessa em inovação e política. Atualmente tem se envolvido com projetos e consultoria em Puppet, GitLab e Rocket.Chat (ChatOps)."
diff --git a/exampleSite/data/speakers/2016/brasilia/douglas-barbosa-alexandre.yml b/exampleSite/data/speakers/2016/brasilia/douglas-barbosa-alexandre.yml
new file mode 100644
index 000000000..a7f309abe
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/douglas-barbosa-alexandre.yml
@@ -0,0 +1,3 @@
+name: "Douglas Barbosa Alexandre"
+twitter: "dbalexandre"
+bio: "Douglas is a software developer that found Ruby in 2007 and fell in love with the language and the open-source community surrounding it. He enjoys to improve people’s lives with the product he is working on, so GitLab was a perfect match to him. In his free time, he loves to drink beer and, spend time with his friends."
diff --git a/exampleSite/data/speakers/2016/brasilia/edson-yanaga.yml b/exampleSite/data/speakers/2016/brasilia/edson-yanaga.yml
new file mode 100644
index 000000000..6fac89414
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/edson-yanaga.yml
@@ -0,0 +1,3 @@
+name: "Edson Yanaga"
+twitter: "yanaga"
+bio: "Edson Yanaga, Diretor de Experiência do Desenvolvedor da Red Hat, é Java Champion e Microsoft MVP. Também é um autor reconhecido internacionalmente e palestrante frequente em eventos internacionais, discutindo Java, Cloud Computing, DevOps, Microservices e Software Craftsmanship."
diff --git a/exampleSite/data/speakers/2016/brasilia/fernando-ike.yml b/exampleSite/data/speakers/2016/brasilia/fernando-ike.yml
new file mode 100644
index 000000000..626cad930
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/fernando-ike.yml
@@ -0,0 +1,3 @@
+name: "Fernando Ike"
+twitter: "fernandoike"
+bio: "Fernando Ike é engenheiro de solução da Highwinds e levemente curioso por sistemas distribuídos, resilientes e qualquer coisa que puder melhorar a performance; Colaborou com alguns projetos de Software Livre como Debian, PostgreSQL, PGVM e Zabbix; Também colaborou com os podcasts como GDHcast e Navaranda Podcast."
diff --git a/exampleSite/data/speakers/2016/brasilia/fernando-moraes.yml b/exampleSite/data/speakers/2016/brasilia/fernando-moraes.yml
new file mode 100644
index 000000000..44a9a058a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/fernando-moraes.yml
@@ -0,0 +1,3 @@
+name: "Fernando Moraes"
+twitter: "fasmoraes"
+bio: "Fernando é formado em Engenharia de Computação pela Unicamp e possui MBA em Marketing pela ESPM. Tem experiência internacional como analista e arquiteto de software, e nos últimos cinco anos tem se dedicado ao desenho e gestão de áreas de PSPEAKERBIOD e Inovação corporativos. Foi Product Owner de produtos nas áreas de mineração de dados e processos (analytics), visualização de dados e monitoração de dados em tempo próximo ao real. Como Gerente de Inovação da Daitan, sua missão é fomentar e apoiar os times da empresa na criação e transformação de conhecimento técnico em thought leadership e oportunidades de negócio."
diff --git a/exampleSite/data/speakers/2016/brasilia/gustavo-hoyer.yml b/exampleSite/data/speakers/2016/brasilia/gustavo-hoyer.yml
new file mode 100644
index 000000000..1eb5119cb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/gustavo-hoyer.yml
@@ -0,0 +1,3 @@
+name: "Gustavo Hoyer"
+twitter: "gustavohoyer"
+bio: "Engenheiro da computação por formação, já atuei como analista de sistemas na empresa Autotrac Comércio e Telecom S.A, onde era um dos responsáveis pelo desenvolvimento do sistema de bilhetagem e faturamento da empresa. Desde 2011 estou na Dataprev, onde tive a oportunidade de atuar como responsável técnico do Data Center DF pela impantação de ferramentas de monitoramento, gestão, conformidade e service desk. Tive o meu primeiro contato com o universo DevOps no ano passado quando atuei como um dos responsáveis técnicos pela implantação da solução de gestão centralizada de logs com o ELK na empresa e atualmente estou atuando como líder de uma equipe com a missão de agilizar o provisionamento e entrega de ambientes na Dataprev. Para nos ajudar neste desafio é claro que escolhemos o Puppet!"
diff --git a/exampleSite/data/speakers/2016/brasilia/gutocarvalho.yml b/exampleSite/data/speakers/2016/brasilia/gutocarvalho.yml
new file mode 100644
index 000000000..6cba23f84
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/gutocarvalho.yml
@@ -0,0 +1,3 @@
+name: "gutocarvalho"
+twitter: "gutocarvalho"
+bio: "Guto é especialista em automação e infraestrutura ágil. Possui mais de 16 anos de experiência em TI na operação de datacenters governamentais e privados. É entusiasta da cultura DevOps e palestrante regular em eventos de TI no Brasil. Em sua carreira ele sempre procura adaptar métodos ágeis para tornar a infraestrutura de seus clientes mais eficiente e autônoma. Desde 2014 é sócio, consultor e arquiteto de automação na empresa Instruct Infraestrutura Ágil. A Instruct é pioneria em automação e parceira exclusiva Puppet e GitLab no Brasil a oferecer treinamentos, projetos e soluções ágeis de infraestrutura."
diff --git a/exampleSite/data/speakers/2016/brasilia/jonathan-baraldi.yml b/exampleSite/data/speakers/2016/brasilia/jonathan-baraldi.yml
new file mode 100644
index 000000000..0e33a70aa
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/jonathan-baraldi.yml
@@ -0,0 +1,3 @@
+name: "Jonathan Baraldi"
+twitter: "baraldijonathan"
+bio: "Trabalho na empresa BRCloud Services como especialista em nuvem e infraestrutura, somos parceiros da Rancher no Brasil para consultoria, projetos e implantações desta tecnologia de orquestração de containers, para ambientes multi-nuvem, resilientes e distribuídos. Procuro desenvolver cada vez mais a cultura de DevOps através da automação da gestão da infra estrutura de containers e também da nuvem."
diff --git a/exampleSite/data/speakers/2016/brasilia/matheus-petronillio-hernandes.yml b/exampleSite/data/speakers/2016/brasilia/matheus-petronillio-hernandes.yml
new file mode 100644
index 000000000..ee4f9f8d6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/matheus-petronillio-hernandes.yml
@@ -0,0 +1,3 @@
+name: "Matheus Petronillio Hernandes"
+twitter: ""
+bio: "Especialista em Criptografia pela Universidade Federal Fluminense, bacharel em Ciência da Computação pela Universidade Federal do Ceará e técnico em Eletroeletrônica pelo Instituto Federal de Educação, Ciência e Tecnologia do Ceará. Atualmente está liderando o time de automação de infraestrutura do TCU utilizando a tecnologia Puppet."
diff --git a/exampleSite/data/speakers/2016/brasilia/miguel-di-ciurcio.yml b/exampleSite/data/speakers/2016/brasilia/miguel-di-ciurcio.yml
new file mode 100644
index 000000000..6cce0525d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/brasilia/miguel-di-ciurcio.yml
@@ -0,0 +1,3 @@
+name: "Miguel Di Ciurcio"
+twitter: "mciurcio"
+bio: "Eu sou o primeiro Certified Puppet Professional na América Latina e também um dos fundadores da comunidade Puppet Brasil. Durante a universidade, participei do Google Summer of Code, trabalhando no projeto QEMU. Trabalhei como administrador de sistemas e instrutor boa parte da minha carreira, contribuindo em diversos projetos open source com patches e palestrando em conferências e eventos. Em 2011 fundei a Instruct. Desde então, a empresa já realizou muitos projetos e treinamentos como única qualificada para ser Puppet Authorized Training e Channel Partner do Brasil e também GitLab Resseller."
diff --git a/exampleSite/data/speakers/2016/capetown/dale-humby.yml b/exampleSite/data/speakers/2016/capetown/dale-humby.yml
new file mode 100644
index 000000000..80e32e489
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/dale-humby.yml
@@ -0,0 +1,3 @@
+name: "Dale Humby"
+twitter: "dalehumby"
+bio: "Dale Humby is the Chief Technical Officer of Nomanini, a South African-based technology provider dedicated to building the tools needed to facilitate cash payments in informal markets. He is an electro-mechanical engineer with a wealth of experience in embedded systems and back-end system design. In 2014, Dale was named a Developer Expert for the Google Cloud platform. Dale leads Nomanini’s team of software developers, hardware engineers and industrial designers, and is responsible for the technical operations of Nomanini’s payments platform. Before joining Nomanini, Dale was the founding member of One Over Zero, which developed a wide range of products. He lead development on various bespoke embedded and M2M electronics and software projects for agricultural and FMCG markets."
diff --git a/exampleSite/data/speakers/2016/capetown/daniel-maher.yml b/exampleSite/data/speakers/2016/capetown/daniel-maher.yml
new file mode 100644
index 000000000..d560a5486
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/daniel-maher.yml
@@ -0,0 +1,3 @@
+name: "Daniel Maher"
+twitter: "phrawzty"
+bio: "Daniel Maher is a Senior Devops Engineer at Mozilla. He's also been a small business owner, a university lecturer, and a day labourer. Send wine suggestions to him via Twitter."
diff --git a/exampleSite/data/speakers/2016/capetown/david-rubin.yml b/exampleSite/data/speakers/2016/capetown/david-rubin.yml
new file mode 100644
index 000000000..2b6ed5198
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/david-rubin.yml
@@ -0,0 +1,3 @@
+name: "David Rubin"
+twitter: "drubin87"
+bio: "David is an engineer and loves making developers’ lives easier and to keep VPCs purring like kittens. Currently working at OLX bringing his startup experience into handling and building OLX’s technology platform. For the last 7 years he has worked for the FireID group on various products including being part of the original team that built SnapScan, CEO of Swiftly, CTO of FitKey. He takes pride in his few fast failures along the way too. David currently lives in Stellenbosch, the wine capital of South Africa."
diff --git a/exampleSite/data/speakers/2016/capetown/eric-maxwell.yml b/exampleSite/data/speakers/2016/capetown/eric-maxwell.yml
new file mode 100644
index 000000000..8e82b2475
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/eric-maxwell.yml
@@ -0,0 +1,3 @@
+name: "Eric Maxwell"
+twitter: "iamericmaxwell"
+bio: "Eric Maxwell is a Success Engineer at Chef Software and is focused on making companies more awesome by helping them \"do the DevOps\" and enabling them to ship at velocity. In past lives, Eric was a back-end C# engineer, a big-data engineer playing in the Hadoop ecosystem, and a professional social engineer working in the InfoSec world. "
diff --git a/exampleSite/data/speakers/2016/capetown/jp-viljoen.yml b/exampleSite/data/speakers/2016/capetown/jp-viljoen.yml
new file mode 100644
index 000000000..318b97a47
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/jp-viljoen.yml
@@ -0,0 +1,5 @@
+name: "JP Viljoen"
+twitter: "froztbyte"
+bio: "A computer farmer and packet herder by trade, JP spent years working in the broadcast and telecoms industries. The founder of Featherlight Consulting, JP adheres to the philosophy that things can, and most likely will, break. He spends much of his time caring about meaningful insights into systems, engineering reliability where needed, and delivering bespoke solutions in a number of problem domains.
+
+JP picks Python as the first hammer in his toolbox (although he writes whatever is necessary), learns Haskell for fun, reads filesystems whitepapers while drinking beer, and plays with IP video streams and Internet routing protocols when bored."
diff --git a/exampleSite/data/speakers/2016/capetown/noa-resare.yml b/exampleSite/data/speakers/2016/capetown/noa-resare.yml
new file mode 100644
index 000000000..22ae83088
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/noa-resare.yml
@@ -0,0 +1,3 @@
+name: "Noa Resare"
+twitter: "blippie"
+bio: "Noa Resare is an engineer with a long background in both in operations and development in organisations large and small. He currently holds a position as Production Engineer at Facebook in London, before that he brought music to the world at Spotify in Stockholm, Sweden."
diff --git a/exampleSite/data/speakers/2016/capetown/seth-vargo.yml b/exampleSite/data/speakers/2016/capetown/seth-vargo.yml
new file mode 100644
index 000000000..adf35ecc6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/seth-vargo.yml
@@ -0,0 +1,3 @@
+name: "Seth Vargo"
+twitter: "sethvargo"
+bio: "Seth Vargo is the Director of Evangelism at HashiCorp. Previously, Seth worked at Chef (Opscode), CustomInk, and a few Pittsburgh-based startups. He the author of Learning Chef and is passionate about reducing inequality in technology. When he is not writing, working on open source, or speaking at conferences, Seth enjoys spending time with his friends and advising non-profits. He loves all things bacon."
diff --git a/exampleSite/data/speakers/2016/capetown/spencer-krum.yml b/exampleSite/data/speakers/2016/capetown/spencer-krum.yml
new file mode 100644
index 000000000..5b3b552a7
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/spencer-krum.yml
@@ -0,0 +1,5 @@
+name: "Spencer Krum"
+twitter: "nibalizer"
+bio: "Spencer (nibalizer) Krum (http://spencerkrum.com) has been sysoping Linux since 2010. He works for IBM contributing upstream to OpenStack and Puppet. Spencer is a core contributor to the OpenStack Infrastructure Project. Spencer coordinates the local DevOps user group in Portland and volunteers for an ops-training program at Portland State University called the Braindump. Spencer is a published author and frequent speaker at technical conferences. Spencer is a maintainer for the voxpupuli effort(https://voxpupuli.org), which attempts to bring together a network of Puppet developers, modules, and infrastructure.
+
+Spencer lives and works in Portland, Oregon where he enjoys tennis, cheeseburgers and StarCraft II."
diff --git a/exampleSite/data/speakers/2016/capetown/tim-haak.yml b/exampleSite/data/speakers/2016/capetown/tim-haak.yml
new file mode 100644
index 000000000..0ef9c5b96
--- /dev/null
+++ b/exampleSite/data/speakers/2016/capetown/tim-haak.yml
@@ -0,0 +1,3 @@
+name: "Tim Haak"
+twitter: "tim_haak"
+bio: "Tim Haak is a Docker Captain by night and an independent contractor by day. He is also one of the organisers for Johannesburg Php Meetup. He has spent to many years playing and working in the web, networking and linux world. Tim specialises in the Web Application sphere though mainly backend focused."
diff --git a/exampleSite/data/speakers/2016/chicago/abejide-ayodele.yml b/exampleSite/data/speakers/2016/chicago/abejide-ayodele.yml
new file mode 100644
index 000000000..16a654117
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/abejide-ayodele.yml
@@ -0,0 +1,3 @@
+name: "Àbéjídé Àyodélé"
+twitter: "bjhaid"
+bio: "I work for Braintree. At Braintree I have worn several hats from writing merchant facing software to racking servers, configuring routers and load balancers."
diff --git a/exampleSite/data/speakers/2016/chicago/adam-jacob.yml b/exampleSite/data/speakers/2016/chicago/adam-jacob.yml
new file mode 100644
index 000000000..3fa307a28
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/adam-jacob.yml
@@ -0,0 +1,3 @@
+name: "Adam Jacob"
+twitter: "adamhjk"
+bio: "Adam Jacob is the creator of Chef and co-founder of Chef, Inc. in 2008 and currently serves as its Chief Technology Officer. Prior to Chef, Inc. Adam founded HJK Solutions, an automated infrastructure consultancy. During two years at HJK, Adam built new infrastructures for 15 different startups. Including Adam's time at HJK, Adam has 13 years of experience as a systems administrator, systems architect, and tools developer."
diff --git a/exampleSite/data/speakers/2016/chicago/alison-stanton.yml b/exampleSite/data/speakers/2016/chicago/alison-stanton.yml
new file mode 100644
index 000000000..dc1760aed
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/alison-stanton.yml
@@ -0,0 +1,3 @@
+name: "Alison Stanton"
+twitter: "alison985"
+bio: "As Founder and Chief Problem Solver at Stanton Ventures, Alison Stanton focuses on business intelligence reporting, product measurement, and process improvement through automation. She makes data accessible, discoverable, and actionable for Operations teams, Product Managers, and clients. Currently, her main languages are SQL, Python, and LookML. She also provides diversity and inclusion consulting related to LGBTQ and women in tech communities upon request. She loves knitting, working to retain women in tech, and using technology to empower audacious ideas."
diff --git a/exampleSite/data/speakers/2016/chicago/allie-richards.yml b/exampleSite/data/speakers/2016/chicago/allie-richards.yml
new file mode 100644
index 000000000..48f37a8f5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/allie-richards.yml
@@ -0,0 +1,3 @@
+name: "Allie Richards"
+twitter: "hpuxgirl"
+bio: "Senior DevOps Engineer with 16 years experience. Feminist. Cat lover."
diff --git a/exampleSite/data/speakers/2016/chicago/angela-dugan.yml b/exampleSite/data/speakers/2016/chicago/angela-dugan.yml
new file mode 100644
index 000000000..e48d3ee23
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/angela-dugan.yml
@@ -0,0 +1,3 @@
+name: "Angela Dugan"
+twitter: "OakParkGirl"
+bio: "Angela Dugan is a Principal Consultant and Practice Manager for Polaris Solutions, a small technology based consulting firm based out of Chicago, Denver, and St. Louis. Angela has been in software development since 1999, filling roles including business analyst, developer, tester, project manager, and agile coach. Angela also runs the Chicago ALM user group, is an active organizer and speaker at several local conferences including CCC and ThatConference, is a Microsoft ALM MVP, CSM, and SPC."
diff --git a/exampleSite/data/speakers/2016/chicago/brian-henerey.yml b/exampleSite/data/speakers/2016/chicago/brian-henerey.yml
new file mode 100644
index 000000000..d09f7e1fc
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/brian-henerey.yml
@@ -0,0 +1,3 @@
+name: "Brian Henerey"
+twitter: "bhenerey"
+bio: "VP/D of Technical Operations at OneMain Financial."
diff --git a/exampleSite/data/speakers/2016/chicago/heidi-waterhouse.yml b/exampleSite/data/speakers/2016/chicago/heidi-waterhouse.yml
new file mode 100644
index 000000000..a51635f5a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/heidi-waterhouse.yml
@@ -0,0 +1,3 @@
+name: "Heidi Waterhouse"
+twitter: "wiredferret"
+bio: "Heidi is a widely experienced technical writer with an interest in writing herself out of work. She specializes in creating entire documentation suites for new companies and products in less time than you would believe possible. She speaks on topics like search-led writing, starting new documentation products, and whistleblowing as a technical writer."
diff --git a/exampleSite/data/speakers/2016/chicago/jamesha-fisher.yml b/exampleSite/data/speakers/2016/chicago/jamesha-fisher.yml
new file mode 100644
index 000000000..a7847a74f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/jamesha-fisher.yml
@@ -0,0 +1,3 @@
+name: "Jamesha Fisher"
+twitter: "jamfish728"
+bio: "Jamesha Fisher has worked in the Tech industry for over 10 years, with a keen eye towards security. Currently a Security Operations Engineer at GitHub, she has lent her security expertise throughout her career in Operations and Systems Engineering to other companies including Google and CloudPassage. In her spare time she is a maker of things musical, delicious, and objects that use binary numbers. You can find her on twitter as @jamfish728."
diff --git a/exampleSite/data/speakers/2016/chicago/jeff-smith.yml b/exampleSite/data/speakers/2016/chicago/jeff-smith.yml
new file mode 100644
index 000000000..12a699fe8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/jeff-smith.yml
@@ -0,0 +1,3 @@
+name: "Jeff Smith"
+twitter: "DarkAndNerdy"
+bio: "Jeff Smith has been in the technology field for over 15 years, oscillating between manager and individual contributor. He currently serves as the Manager of Site Reliability Engineering at GrubHub. Jeff enjoys discussing the psychological aspect of problems in organizations. Jeff is also one of the co-founders of the Chicago Nerd Social Club."
diff --git a/exampleSite/data/speakers/2016/chicago/jeremy-edberg.yml b/exampleSite/data/speakers/2016/chicago/jeremy-edberg.yml
new file mode 100644
index 000000000..18685d726
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/jeremy-edberg.yml
@@ -0,0 +1,3 @@
+name: "Jeremy Edberg"
+twitter: "jedberg"
+bio: "Jeremy is an angel investor and advisor for various incubators and startups, and is the cofounder of MinOps. Jeremy was the founding Reliability Engineer for Netflix, and before that he ran ops for reddit. Jeremy also tech-edited the highly acclaimed AWS for Dummies. His expertise is in serverless computing, distributed computing, availability, rapid scaling, and cloud computing. He holds a Cognitive Science degree from UC Berkeley."
diff --git a/exampleSite/data/speakers/2016/chicago/jill-jubinski.yml b/exampleSite/data/speakers/2016/chicago/jill-jubinski.yml
new file mode 100644
index 000000000..8d4e38984
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/jill-jubinski.yml
@@ -0,0 +1,3 @@
+name: "Jill Jubinski"
+twitter: "jilljubs"
+bio: "Jill Jubinski is an recruiting veteran with over 6 years of recruiting experience in the community. She received her Masters in Industrial/Organizational Psychology with plans to change the way organizations treated their employees. When that didn’t work out she started recruiting ;-) Jill leans on her strength in relationship building as a jumping off point to help organizations build amazing teams and genuinely cares about the health and wellness of an organizations culture."
diff --git a/exampleSite/data/speakers/2016/chicago/joel-vasallo.yml b/exampleSite/data/speakers/2016/chicago/joel-vasallo.yml
new file mode 100644
index 000000000..430cdc689
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/joel-vasallo.yml
@@ -0,0 +1,3 @@
+name: "Joel Vasallo"
+twitter: "__jvasallo__"
+bio: "Joel is currently a DevOps Engineer at Gogo. He's been at Gogo for 4 years improving cloud infrastructure and developing infrastructure tools. Primarily works with Python, the cloud is his immutable datacenter, and loves exploring his home city Chicago from time to time."
diff --git a/exampleSite/data/speakers/2016/chicago/joshua-zimmerman.yml b/exampleSite/data/speakers/2016/chicago/joshua-zimmerman.yml
new file mode 100644
index 000000000..027c4bbee
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/joshua-zimmerman.yml
@@ -0,0 +1,3 @@
+name: "Joshua Zimmerman"
+twitter: "thejewberwocky"
+bio: "Joshua has worked for the University of Wisconsin - Madison Libraries for the past decade, playing a variety of roles ranging from helpdesk support, web developer, and Windows systems administration. For the past four years, Joshua has been part of a team of administrators architecting and maintaining an ever-growing Linux server environment for applications both developed in house and procured from vendors. In his spare time, Joshua co-organizes the Madison DevOps meetup and devopsdays Madison."
diff --git a/exampleSite/data/speakers/2016/chicago/ken-mugrage.yml b/exampleSite/data/speakers/2016/chicago/ken-mugrage.yml
new file mode 100644
index 000000000..77057daec
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/ken-mugrage.yml
@@ -0,0 +1,3 @@
+name: "Ken Mugrage"
+twitter: "kmugrage"
+bio: "Ken Mugrage started his own web development company in 1994. Since then he’s held almost every position in a software development company, from developer to system administrator, sales engineer to development manager. This varied experience enables Ken to look at issues with a holistic view. Ken is currently a Technology Evangelist at ThoughtWorks, responsible for teaching others about DevOps and Continuous Delivery."
diff --git a/exampleSite/data/speakers/2016/chicago/michael-stahnke.yml b/exampleSite/data/speakers/2016/chicago/michael-stahnke.yml
new file mode 100644
index 000000000..10e71974d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/michael-stahnke.yml
@@ -0,0 +1,3 @@
+name: "Michael Stahnke"
+twitter: "stahnma"
+bio: "Michael Stahnke is Director of Engineering at Puppet, Inc. He's held a few roles there, and been a part of the company growing from 35 to 440+ employees. While staying near the domains of release engineering, operations, and community, he’s been in leadership for most of the last decade. His primary joy comes from building teams, mentoring team members, and, just recently, playing Hot Wheels cars with his son. He came to Puppet Labs from Caterpillar, Inc. where he was an infrastructure architect."
diff --git a/exampleSite/data/speakers/2016/chicago/morgan-rhodes.yml b/exampleSite/data/speakers/2016/chicago/morgan-rhodes.yml
new file mode 100644
index 000000000..ed5b7188c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/morgan-rhodes.yml
@@ -0,0 +1,3 @@
+name: "Morgan Rhodes"
+twitter: "KnittyNerd"
+bio: "Morgan started working as a module engineer at Puppet in Spring of 2014 and joined the release engineering team in October 2015. Before that she had been part of the Puppet community for over four years, largely using Puppet as a system administrator. Outside of work, she can be found biking, cooking delicious vegan fare, curling like a boss (or Canadian), and hanging out with her cats."
diff --git a/exampleSite/data/speakers/2016/chicago/nell-shamrell-harrington.yml b/exampleSite/data/speakers/2016/chicago/nell-shamrell-harrington.yml
new file mode 100644
index 000000000..8ac574f82
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/nell-shamrell-harrington.yml
@@ -0,0 +1,3 @@
+name: "Nell Shamrell Harrington"
+twitter: "nellshamrell"
+bio: "Nell Shamrell-Harrington is a Software Development Engineer at Chef, focusing on the Supermarket open source product. She also sits on the advisory board for the University of Washington Certificates in Ruby Programming and DevOps. She specializes in Chef, Ruby, Rails, Regular Expressions, and Test Driven Development and has traveled the world speaking on these topics. Prior to entering the world of software development, she studied and worked in the field of theatre. The world of theatre prepared her well for the dynamic world of creating software applications. In both, she strives to create a cohesive and extraordinary experience. In her free time she enjoys practicing the martial art Naginata."
diff --git a/exampleSite/data/speakers/2016/chicago/rebecca-miller-webster.yml b/exampleSite/data/speakers/2016/chicago/rebecca-miller-webster.yml
new file mode 100644
index 000000000..e16415410
--- /dev/null
+++ b/exampleSite/data/speakers/2016/chicago/rebecca-miller-webster.yml
@@ -0,0 +1,3 @@
+name: "Rebecca Miller-Webster"
+twitter: "rmillerwebster"
+bio: "Rebecca Miller-Webster is a software engineer, conference organizer, and educator. She is the founder of [Write/Speak/Code](http://www.writespeakcode.com) and CTO at [Polymathic](http://teampolymathic.com/). Rebecca has been developing software professionally for over a decade, previously organized [GORUCO](http://goruco.com), and was the founding teacher at Dev Bootcamp NYC. Rebecca's hobbies include drinking Diet Coke, wearing trousers, telling computers what to do, dogs, & swearing."
diff --git a/exampleSite/data/speakers/2016/dallas/allison-pollard.yml b/exampleSite/data/speakers/2016/dallas/allison-pollard.yml
new file mode 100644
index 000000000..822a953de
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/allison-pollard.yml
@@ -0,0 +1,3 @@
+name: "Allison Pollard"
+twitter: "allison_pollard"
+bio: "Allison Pollard is an Agile Coach with Improving in Dallas who helps people discover and develop their agile instincts. She enjoys mentoring others to become great Scrum Masters, coaching managers to grow teams that deliver amazing results, and fostering communities that provide sustainability for agile transformations. Allison is also a Certified Professional Co-Active Coach, an organizer of the Dallas-Fort Worth Scrum user group, a foodie, and a trebuchet builder. "
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/dallas/franklin-mosley.yml b/exampleSite/data/speakers/2016/dallas/franklin-mosley.yml
new file mode 100644
index 000000000..8e95e9853
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/franklin-mosley.yml
@@ -0,0 +1,3 @@
+name: "Franklin Mosley"
+twitter: ""
+bio: "Franklin has 15 years experience as an information security professional, and prior to that, was a software engineer, which makes him perfectly suited for his passionate focus on Application Security. At Ellucian, a leader in higher education technology, his mission is to help effectively and efficiently develop, deliver and support the most secure platform possible. He received his MS and BS in Computer Science, is an active participant in various security groups, still likes to write code, and enjoys participating in capture the flag challenges. Aside from technology and security, Franklin is a tennis player, enjoys traveling and photography."
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/dallas/jeffrey-snover.yml b/exampleSite/data/speakers/2016/dallas/jeffrey-snover.yml
new file mode 100644
index 000000000..f595c4e1e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/jeffrey-snover.yml
@@ -0,0 +1,9 @@
+name: "Jeffrey Snover"
+twitter: "jsnover"
+bio: "Jeffrey Snover is a Technical Fellow at Microsoft and the Chief Architect for the Enterprise Cloud Group which includes Azure Stack, Windows Server, System Center and Operations Management Suite.
+
+Snover is the inventor of Windows PowerShell, an object-based distributed automation engine, scripting language, and command line shell. Snover joined Microsoft in 1999 as divisional architect for the Management and Services Division, providing technical direction across Microsoft's management technologies and products.
+
+Snover has over 30 years of industry experience with a focus on management technologies and solutions. He was an architect in the office of the CTO at Tivoli and a development manager at NetView. He has worked also as a consulting engineer and development manager at DEC, where he led various network and systems management projects.
+
+Snover is a frequent speaker at industry and research conferences on a variety of cloud, management and language topics."
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/dallas/kevin-witherstine.yml b/exampleSite/data/speakers/2016/dallas/kevin-witherstine.yml
new file mode 100644
index 000000000..92247bc4d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/kevin-witherstine.yml
@@ -0,0 +1,3 @@
+name: "Kevin Witherstine"
+twitter: "CumulusKevin"
+bio: "Kevin Witherstine is a Systems Engineer at Cumulus Networks with over 20 years of networking industry experience and a recent focus on SDN and virtual networking. Previous to Cumulus, Kevin has had stints with industry giants such as VMware, Cisco, and Juniper. "
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/dallas/marissa-levy-lerer.yml b/exampleSite/data/speakers/2016/dallas/marissa-levy-lerer.yml
new file mode 100644
index 000000000..e31d0cb77
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/marissa-levy-lerer.yml
@@ -0,0 +1,8 @@
+name: "Marissa Levy Lerer"
+twitter: "marissalevy"
+bio: "Marissa Levy Lerer is a technologist, musician, cake decorator and mom. She grew up in Bethesda, Maryland and then moved to New York City where she received a BS in Music Education and an MA in Graphic Communications, Management and Technology. During her time at NYU she began writing music and has since released three albums.
+
+Marissa started her career in technology as a graphic designer for MTV before transitioning into management. Eventually she began coding as a senior developer at The Chopping Block and then at BBDO. She is currently managing a team of developers, as Vice President of Technology at COMPOSE[D], a digital creative and development agency in New York.
+
+Marissa prides herself on being a “cool nerd” who likes to get her hands in everything. When she decided she wanted to learn to decorate cakes, instead of taking classes she let the internet be her guide. She made one cake a week for an entire year chronicling the experience on 52cakes.com. She is also an accomplished singer/songwriter who has released three albums and shared the stage with talented musicians such as Matt Nathanson, Lisa Loeb and Gavin DeGraw. She has also participated in the 2012 StartupBus and was on the winning team of the 2012 International Space Apps Challenge. She is passionate about mentorship, especially for women in tech. In addition to teaching programing at the School of Visual Arts she is also a regular panelist at Pace Path Live and recently mentored Girl Scouts at a SXSW event sponsored by Twitter and Dove."
+
diff --git a/exampleSite/data/speakers/2016/dallas/michael-cote.yml b/exampleSite/data/speakers/2016/dallas/michael-cote.yml
new file mode 100644
index 000000000..27edb41bf
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/michael-cote.yml
@@ -0,0 +1,3 @@
+name: "Michael Coté"
+twitter: "cote"
+bio: "Michael Coté works at Pivotal in technical marketing. He’s been an industry analyst at 451 Research and RedMonk, worked in corporate strategy and M&A at Dell in software and cloud, and was a programmer for a decade before all that. He blogs and podcasts at Cote.io and is @cote in Twitter."
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/dallas/michael-hedgpeth.yml b/exampleSite/data/speakers/2016/dallas/michael-hedgpeth.yml
new file mode 100644
index 000000000..9986ddd6e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/michael-hedgpeth.yml
@@ -0,0 +1,3 @@
+name: "Michael Hedgpeth"
+twitter: "michaelhedgpeth"
+bio: "Michael Hedgpeth has been automating all the things for over a decade at NCR by implementing devops and testing automation for their hospitality and is currently working with the development organization to implement Chef as NCR Hospitality's configuration management platform. Over the years, Michael has developed a passion for test-driven development, Kanban, good design, organizational effectiveness, Texas BBQ and mountain biking."
diff --git a/exampleSite/data/speakers/2016/dallas/nathen-harvey.yml b/exampleSite/data/speakers/2016/dallas/nathen-harvey.yml
new file mode 100644
index 000000000..f93a8df92
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/nathen-harvey.yml
@@ -0,0 +1,3 @@
+name: "Nathen Harvey"
+twitter: "nathenharvey"
+bio: "Nathen Harvey, VP of Community Development at Chef, helps the community whip up an awesome ecosystem built around the Chef platform. Nathen also spends much of his time helping people learn about the practices, processes, and technologies that support DevOps, continuous delivery, and high velocity organizations. Prior to joining Chef, Nathen spent a number of years managing operations and infrastructure for a diverse range of web applications. Nathen is a co-host of the Food Fight Show, a podcast about Chef and DevOps."
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/dallas/shazad-brohi.yml b/exampleSite/data/speakers/2016/dallas/shazad-brohi.yml
new file mode 100644
index 000000000..568f50f3c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/shazad-brohi.yml
@@ -0,0 +1,3 @@
+name: "Shazad Brohi"
+twitter: ""
+bio: "Shazad Brohi is a dedicated, highly driven, and team-oriented software engineer with extensive experience working with 3-tier enterprise and web applications. Shazad is also a self-starter that can pick up and learn new technologies at a fast pace. Shazad possesses a strong understanding of the software development life-cycle and the technical acumen to execute it."
diff --git a/exampleSite/data/speakers/2016/dallas/zach-cannon.yml b/exampleSite/data/speakers/2016/dallas/zach-cannon.yml
new file mode 100644
index 000000000..3a3d6f82c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/dallas/zach-cannon.yml
@@ -0,0 +1,3 @@
+name: "Zach Cannon"
+twitter: ""
+bio: "Zachary Cannon is a Technology Consultant with Improving out of the Dallas headquarters. His passion lies in helping others define and achieve their goals, both personally and professionally. An avid supporter of Agile and Lean programming principles, Zach believes that empowering team members and giving them the freedom to creatively solve their problems will lead to rapid delivery of a quality product. He embodies the motto “Lead From Any Chair” and encourages others to do the same. In his time out of the office, Zach is a health and fitness nut, a coffee enthusiast, and a fan of good conversation."
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/ghent/bart-blommaerts.yml b/exampleSite/data/speakers/2016/ghent/bart-blommaerts.yml
new file mode 100644
index 000000000..0ad93579c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/bart-blommaerts.yml
@@ -0,0 +1,3 @@
+name: "Bart Blommaerts"
+twitter: "DaggieBe"
+bio: "Bart Blommaerts is a passionate Software Architect at Ordina, who believes closing the model-code gap is essential to make rapid, agile delivery sustainable. Bart has a strong focus on API design, reuse, automation and security. He is always looking for technical challenges. Bart also is the chairman of the different JWorks Competence Leads at Ordina. Before Ordina, Bart led the EMEA Java Community at HP and was chairman of the HP Java Governance Board in the Benelux."
diff --git a/exampleSite/data/speakers/2016/ghent/bart-vanbrabant.yml b/exampleSite/data/speakers/2016/ghent/bart-vanbrabant.yml
new file mode 100644
index 000000000..37e328545
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/bart-vanbrabant.yml
@@ -0,0 +1,3 @@
+name: "Bart Vanbrabant"
+twitter: "bartvanbrabant"
+bio: "Bart Vanbrabant worked from 2008 until 2015 at the KU Leuven in the iMinds-DistriNet research group, where he obtained a PhD in 2014 on managing large scale distributed systems. In Januari 2016 he founded Inmanta with two fellow colleagues, his PhD advisor and the KU Leuven. Inmanta is a KU Leuven spin-off that develops an integrated orchestration and configuration management tool. Inmanta is currently in the process of open sourcing this tool."
diff --git a/exampleSite/data/speakers/2016/ghent/berry-kersten.yml b/exampleSite/data/speakers/2016/ghent/berry-kersten.yml
new file mode 100644
index 000000000..ff2265031
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/berry-kersten.yml
@@ -0,0 +1,3 @@
+name: "Berry Kersten"
+twitter: "scrumoloog"
+bio: "Berry is an experienced software testing professional. In the last seven years, he gained knowledge about Agile themes such as Scrum and Devops. As an certified Agile practitioner Berry speaks at Dutch conferences like TestNet and writes articles about several topics relating to Agile, Quality and Learning. And last but not least, Berry is a DJ on a local radio broadcast station."
diff --git a/exampleSite/data/speakers/2016/ghent/frederic-descamps.yml b/exampleSite/data/speakers/2016/ghent/frederic-descamps.yml
new file mode 100644
index 000000000..69d229fb2
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/frederic-descamps.yml
@@ -0,0 +1,3 @@
+name: "Frédéric Descamps"
+twitter: "lefred"
+bio: "OpenSource consultant and evangelist for many years and devops believer since the early ages, I joined recently the MySQL Community Team. http://about.me/lefred"
diff --git a/exampleSite/data/speakers/2016/ghent/joseph-pierri.yml b/exampleSite/data/speakers/2016/ghent/joseph-pierri.yml
new file mode 100644
index 000000000..cd0bae3ae
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/joseph-pierri.yml
@@ -0,0 +1,3 @@
+name: "Joseph Pierri"
+twitter: ""
+bio: "Joseph Pierri is a Senior Software Engineer at PagerDuty, based in Toronto. He is a member of the Core Team at PagerDuty, and has had the opportunity to work on a variety of interesting projects over the 3+ years that he’s been there, ranging from feature-work to backend systems to infrastructure components. Joseph has worked as a full-time software professional for over 8 years, in both the Finance and SaaS industries. In his spare time, he likes running and poring over baseball statistics."
diff --git a/exampleSite/data/speakers/2016/ghent/karel-de-smet.yml b/exampleSite/data/speakers/2016/ghent/karel-de-smet.yml
new file mode 100644
index 000000000..5a8f5cde7
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/karel-de-smet.yml
@@ -0,0 +1,6 @@
+name: "Karel De Smet"
+twitter: ""
+bio: "Karel developed a love for \"all things digital\" during his studies at the EHSAL Management School. After working at the water company for 2 years he joined a web agency as a content manager. Now he's part of the marketing & sales team at Openminds, a hosting company with a strong focus on managed hosting, configuration management and DevOps.
+
+As a passionate marketeer, he's ready for a new challenge every day. But most of all, he just likes to meet new people, talk and have fun!
+"
diff --git a/exampleSite/data/speakers/2016/ghent/martin-goodwell.yml b/exampleSite/data/speakers/2016/ghent/martin-goodwell.yml
new file mode 100644
index 000000000..253a26253
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/martin-goodwell.yml
@@ -0,0 +1,3 @@
+name: "Martin Goodwell"
+twitter: "MartinGoodwell"
+bio: "Passionate about life, technology, and the people behind both of them. Started with Commodore 8-bit, tinkered with MS-DOS and WfW 3.11 on i386 and i486 and finally went into software engineering and architecture for about a decade; mainly via Java and the Web. Holds a degree in Business Informatics from the University of Linz, Austria. Now, at Dynatrace Innovation Lab as a Tech Lead, speaks at conferences, writes blog posts and loves to dig in to new technology. In his other life, he loves running, biking, good food and beer and binge watching. Most of all, he’s a family guy."
diff --git a/exampleSite/data/speakers/2016/ghent/nick-boucart.yml b/exampleSite/data/speakers/2016/ghent/nick-boucart.yml
new file mode 100644
index 000000000..5d21e8700
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/nick-boucart.yml
@@ -0,0 +1,10 @@
+name: "Nick Boucart"
+twitter: "nickboucart"
+bio: "Nick Boucart is senior technology advisor Software Engineering and ICT at Sirris.
+
+His main goal is to help software entrepreneurs grow, by working on the crossroads of technology, business and engineering. Brainstorming about new concepts, products and services, searching for ways to validate and implement these ideas, finding public funding and research opportunities, these are just a few of the things Nick does for his clients.
+
+He is especially interested in helping software entrepreneurs transform their current business models into SaaS format, whilst taking into account the latest in agile, lean startup and developer tools and practices.
+
+His background as a developer helps him understand the technical implications of putting a software product to the market. He is an interim CTO for startups that lack in-house technical skills. He’s a junior growth hacker especially interested in engineered, data-driven product management.
+"
diff --git a/exampleSite/data/speakers/2016/ghent/quentin-adam.yml b/exampleSite/data/speakers/2016/ghent/quentin-adam.yml
new file mode 100644
index 000000000..c9d2fcbff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/quentin-adam.yml
@@ -0,0 +1,3 @@
+name: "Quentin Adam"
+twitter: "waxzce"
+bio: "Quentin ADAM is the CEO of Clever Cloud : a Platform as a Service company allowing you to run java, scala, ruby, node.js, php, python or go applications, with auto scaling and auto healing features. This position allow him to study lots of applications, code, practice, and extract some talks and advises. Regular speaker at various tech conference, he’s focused to help developers to deliver quickly and happily good applications."
diff --git a/exampleSite/data/speakers/2016/ghent/terrence-ryan.yml b/exampleSite/data/speakers/2016/ghent/terrence-ryan.yml
new file mode 100644
index 000000000..b4b716316
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ghent/terrence-ryan.yml
@@ -0,0 +1,3 @@
+name: "Terrence Ryan"
+twitter: "tpryan"
+bio: "Terry Ryan is a Developer Advocate for the Google Cloud Platform team. He has 15 years of experience working with the web - both front end and back. Before working for technology shops like Google and Adobe he worked in roles that combined development with system administration at the Wharton School of Business. He also wrote Driving Technical Change for Pragmatic Bookshelf, a book that arms technology professionals with the tools to convince reluctant co-workers to adopt new tools and technology."
diff --git a/exampleSite/data/speakers/2016/kansascity/aaron-blythe.yml b/exampleSite/data/speakers/2016/kansascity/aaron-blythe.yml
new file mode 100644
index 000000000..0b64df8f4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/aaron-blythe.yml
@@ -0,0 +1,3 @@
+name: "Aaron Blythe"
+twitter: "ablythe"
+bio: "Aaron Blythe has worked in Software for over a decade. He is currently a Sr. Automation and Release Engineer at Hearst Business Media. He is genuinely curious and interested in understanding things and making them better. Aaron went to college at both the University of Illinois and Griffith University in Australia. While in Australia he mostly skipped classes to surf. Aaron loves observing how people interact within the software process and modeling those interactions in search of improvements. He is constantly experimenting with new ways of interacting both in person and with technology. Aaron currently loves Ruby, Rails, and Chef. He has co-organized the Kansas City DevOps community for the past few years."
diff --git a/exampleSite/data/speakers/2016/kansascity/aj-bowen.yml b/exampleSite/data/speakers/2016/kansascity/aj-bowen.yml
new file mode 100644
index 000000000..53b70771c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/aj-bowen.yml
@@ -0,0 +1,6 @@
+name: "AJ Bowen"
+twitter: "s0ulshake"
+bio: |
+ AJ Bowen is on a mission to containerize all the things and help others to do the same. In the past, AJ has done technical support, evangelism, and customer and developer advocacy at [Gandi.net](https://www.gandi.net).
+ Her other experience includes heavy involvement in the Occupy movement in Kansas City, where she discovered the delightful and complicated world of horizontal organization in groups of passionate people with wildly diverse political perspectives, and humanitarian work in Haiti. AJ doesn’t like being told what to do—or telling others what to do—and is on a constant mission to eliminate unnecessary hierarchy.
+ For the truly curious: `curl cv.soulshake.net`
diff --git a/exampleSite/data/speakers/2016/kansascity/alyssa-nicoll.yml b/exampleSite/data/speakers/2016/kansascity/alyssa-nicoll.yml
new file mode 100644
index 000000000..e2e224880
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/alyssa-nicoll.yml
@@ -0,0 +1,3 @@
+name: "Alyssa Nicoll"
+twitter: "AlyssaNicoll"
+bio: "I am an energetic, über passionate developer. I am a Google Developer Expert, Web Dev at WeaveUp and I have some Front-End and Angular courses on Code School. I love to learn new things and then share them with others. I Scuba Dive and have a toothless dog named 'Gummy'. My name is Alyssa, come talk sometime."
diff --git a/exampleSite/data/speakers/2016/kansascity/ashmita-sarma.yml b/exampleSite/data/speakers/2016/kansascity/ashmita-sarma.yml
new file mode 100644
index 000000000..6606b742e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/ashmita-sarma.yml
@@ -0,0 +1,3 @@
+name: "Ashmita Sarma"
+twitter: "mitimita"
+bio: "Ashmita Sarma is a senior at Wayzata High School in Minnesota. Over the summer, she interned on the Systems Engineering Team at SPS Commerce, where she experienced the DevOps culture at a large scale company. She is currently does robotics research at the University of Minnesota under the guidance of Dr. Maria Gini. She volunteers as a mentor at CoderDojo, as well as a mentor at Camp KidsCode. Her passions include cloud computing, robotics, anything Python, web development, and unicycling."
diff --git a/exampleSite/data/speakers/2016/kansascity/baruch-sadogursky.yml b/exampleSite/data/speakers/2016/kansascity/baruch-sadogursky.yml
new file mode 100644
index 000000000..6f1c6e285
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/baruch-sadogursky.yml
@@ -0,0 +1,3 @@
+name: "Baruch Sadogursky"
+twitter: "jbaruch"
+bio: "Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate at JFrog where he has made a profession of speaking about the company’s products: Artifactory, the Universal Artifact Repository; Bintray - the Universal Distribution Platform; Xray, Universal Component Analysis and Mission Control, Centralized Control and Management. For a living he hangs out with JFrog’s tech leaders, writes code around the JFrog Platform and its ecosystem, and then speaks and blogs about it all. He has been doing this for the last dozen years or so, and enjoys every minute of it. Baruch is @jbaruch on twitter and mostly blogs on http://www.jfrog.com/blog/ and http://blog.bintray.com.He is a professional conference speaker on DevOps, Java and Groovy topics, and is a regular at the industry’s most prestigious events including JavaOne (where he was awarded a Rock Star award), Devoxx, DevOps Days, OSCON, QCON and many others. His full speaker history is available on Lanyrd: http://lanyrd.com/profile/jbaruch/sessions/"
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/kansascity/caleb-hyde.yml b/exampleSite/data/speakers/2016/kansascity/caleb-hyde.yml
new file mode 100644
index 000000000..16e620c02
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/caleb-hyde.yml
@@ -0,0 +1,3 @@
+name: Caleb Hyde
+twitter: hedonistica
+bio: After a tour of duty at a certain large telecom during the recession, I have been the entire DevOps team at small companies, and have worked on DevOps teams supporting multiple developer teams. I aspire to Steve Yegge’s Done, and Gets Things Smart.
diff --git a/exampleSite/data/speakers/2016/kansascity/charles-butler.yml b/exampleSite/data/speakers/2016/kansascity/charles-butler.yml
new file mode 100644
index 000000000..543e32f4a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/charles-butler.yml
@@ -0,0 +1,3 @@
+name: "Charles Butler"
+twitter: "lazypower"
+bio: "Chuck is a hacker, software engineer and Linux enthusiast. He works for Canonical, the company that brings you Ubuntu. His day job is working on the Juju Ecosystem team. When not at work, you can find Chuck in his audio lab; creating or destroying things."
diff --git a/exampleSite/data/speakers/2016/kansascity/cynthia-thomas.yml b/exampleSite/data/speakers/2016/kansascity/cynthia-thomas.yml
new file mode 100644
index 000000000..785d419ef
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/cynthia-thomas.yml
@@ -0,0 +1,3 @@
+name: "Cynthia Thomas"
+twitter: "_techcet_"
+bio: "Cynthia Thomas is a systems engineer at Midokura, a global network virtualization software company. She enjoys highlighting the emerging technologies in network virtualization as application needs evolve. Her background in networking hardware spans from Telecommunications to Data Center and Campus/Enterprise solutions. She is a frequent speaker at cloud conferences such as the OpenStack Summit, OpenStack meetups and the IT Cloud Computing Conference (IC3). Cynthia received her B. Sc. (Eng) and M. Sc. (Eng) from Queen’s University in Kingston, Canada."
diff --git a/exampleSite/data/speakers/2016/kansascity/david-blank-edelman.yml b/exampleSite/data/speakers/2016/kansascity/david-blank-edelman.yml
new file mode 100644
index 000000000..68e4a7bd1
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/david-blank-edelman.yml
@@ -0,0 +1,3 @@
+name: "David N. Blank-Edelman"
+twitter: "otterbook"
+bio: "David is the Technical Evangelist at Apcera. He has spent close to thirty years in the systems administration/DevOps/SRE field in large multiplatform environments including Brandeis University, Cambridge Technology Group, MIT Media Laboratory and Northeastern University. He is the author of the O'Reilly Otter book (Automating System Administration with Perl) and is a frequent invited speaker at conferences in the field. David is honored to serve on the USENIX Board of Directors. He prefers to pronounce Evangelist with a hard 'g'."
diff --git a/exampleSite/data/speakers/2016/kansascity/jeffrey-sykes.yml b/exampleSite/data/speakers/2016/kansascity/jeffrey-sykes.yml
new file mode 100644
index 000000000..c8a7197e8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/jeffrey-sykes.yml
@@ -0,0 +1,3 @@
+name: "Jeffrey Sykes"
+twitter: "sykesjs"
+bio: "Jeffrey Sykes is the Director of WebOps at VML. Jeffrey leads a team of around 20 across VML's North American offices. During his time at VML, Jeffrey has worked across many of VML's largest clients supporting high-volume web sites utilizing many different technologies, including custom .NET sites, Sitecore, AEM (CQ) and custom Java applications. His assignments have included designing the server and cloud infrastructure for sites along with the actual implementation of the projects. As a team leader, Jeffrey has worked to help spread the adoption of DevOps methodologies across VML. Other projects include collaborative efforts to develop a company wide architectural assessments for all projects. Prior to VML, Jeffrey worked in various IT roles in Higher education. Outside of work, Jeffrey enjoys soccer, cooking and sharks."
diff --git a/exampleSite/data/speakers/2016/kansascity/kevin-obrien.yml b/exampleSite/data/speakers/2016/kansascity/kevin-obrien.yml
new file mode 100644
index 000000000..a352d3850
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/kevin-obrien.yml
@@ -0,0 +1,2 @@
+name: "Kevin O'Brien"
+bio: "Kevin is a Human Factors Engineer with extensive experience developing useful and usable technology. Kevin founded O’Brien Consulting in Cupertino CA in 1998. Working with clients like HP, Sun Microsystems, Brocade, Emerson Process Management, and Palm on projects including provisioning tools, systems and network administration, system monitoring, and geographic information systems. Kevin earned a Ph.D. in Cognitive Psychology from University of Kansas followed by stints at NASA’s Johnson Space Center and Pacific Bell. When not doing that stuff Kevin spends time helping his kids with homework, playing jazz (sax), reading physics, astronomy, and maths."
diff --git a/exampleSite/data/speakers/2016/kansascity/kyle-sexton.yml b/exampleSite/data/speakers/2016/kansascity/kyle-sexton.yml
new file mode 100644
index 000000000..c78d6222e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/kyle-sexton.yml
@@ -0,0 +1,3 @@
+name: "Kyle Sexton"
+twitter: "mocker"
+bio: "Kyle Sexton is a DevOps Engineer for New Context, a pioneer in lean security. He has been managing servers for over 15 years and has his RHSA, LPIC and dCAP certifications. He stinks at writing personal bios."
diff --git a/exampleSite/data/speakers/2016/kansascity/leon-fayer.yml b/exampleSite/data/speakers/2016/kansascity/leon-fayer.yml
new file mode 100644
index 000000000..2e6cb498f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/leon-fayer.yml
@@ -0,0 +1,3 @@
+name: "Leon Fayer"
+twitter: "papa_fire"
+bio: "Leon's two decades of expertise were concentrated on architecting and operating complex, web-based systems to withstand crushing traffic (often unexpectedly). Over the years, he's had a somewhat unique opportunity to design and build systems that run some of the most visited websites in the world. While his core expertise is in application development, he works his way around the whole technology stack from system architecture to databases design and optimization to front/back-end programming. He's considered a professional naysayer by peers and has the opinion that nothing really works until it works for at least a million people."
diff --git a/exampleSite/data/speakers/2016/kansascity/pauly-comtois.yml b/exampleSite/data/speakers/2016/kansascity/pauly-comtois.yml
new file mode 100644
index 000000000..b562e9a9c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/pauly-comtois.yml
@@ -0,0 +1,3 @@
+name: "Pauly Comtois"
+twitter: "paulycomtois"
+bio: "Pauly Comtois is VP of DevOps for Hearst Business Media. This role provides full time consulting to ten business units within Hearst focusing on continuous improvement and community building through culture, process and tools. Pauly has over 20 years' experience in building, developing and leading high performing IT, Support, Operations and Development teams in rapidly growing organizations. Pauly is a seasoned leader of cultural change efforts in unifying Development and Operations through training and mentorship in Incident Management, Blameless Post Mortems, Value Stream Mapping, Continuous Integration and Continuous Deployment. His current focus is on building Agile and DevOps communities within the business units at Hearst Business Media and a broader community that binds those business units together. This effort is underpinned by Agile and DevOps methodologies and cultural concepts. Pauly is based in Seattle, WA."
diff --git a/exampleSite/data/speakers/2016/kansascity/scott-howell.yml b/exampleSite/data/speakers/2016/kansascity/scott-howell.yml
new file mode 100644
index 000000000..9b37127f1
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/scott-howell.yml
@@ -0,0 +1,3 @@
+name: "Scott Howell"
+twitter: "sdhowell3"
+bio: "Scott is a hacker and doer, currently a DevOps Engineer at Pinsight Media. He’s previously held multiple positions from back-end developer to project manager. Scott found his current role in DevOps after serving as the lead front-end developer for all marketing sites at Pinsight. He enjoys mapping chaos into organized systems and integrating complex processes into automated tasks. When Scott isn’t working, he can be found serving on multiple nonprofit boards, pursuing his favorite hobby of Native American beadwork, or catching up on the latest trends in DevOps."
diff --git a/exampleSite/data/speakers/2016/kansascity/scott-smerchek.yml b/exampleSite/data/speakers/2016/kansascity/scott-smerchek.yml
new file mode 100644
index 000000000..1485f3723
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/scott-smerchek.yml
@@ -0,0 +1,3 @@
+name: "Scott Smerchek"
+twitter: "smerchek"
+bio: "Scott is a software engineer working at a small medication adherence company called SMRxT. Formerly he worked as a .NET developer and more recently as a node.js/javascript developer. However, Scott has most recently been drawn to functional, typed languages like Elm and Haskell. Scott enjoys working for small healthcare businesses building software that can change lives for the better. Working with new technologies and constantly learning are a bonus."
diff --git a/exampleSite/data/speakers/2016/kansascity/suzie-prince.yml b/exampleSite/data/speakers/2016/kansascity/suzie-prince.yml
new file mode 100644
index 000000000..bc5c13299
--- /dev/null
+++ b/exampleSite/data/speakers/2016/kansascity/suzie-prince.yml
@@ -0,0 +1,3 @@
+name: "Suzie Prince"
+twitter: "pm_suzie"
+bio: "Suzie Prince is currently the product manager for a software-as-a-service continuous integration and continuous delivery tool for software engineering teams. Her team practices continuous integration and continuous delivery everyday to deliver quality software to their users. She likes pushing buttons to release software, feature toggles and pager duty. She also like burritos, beer and hiking."
diff --git a/exampleSite/data/speakers/2016/london/andi-mann.yml b/exampleSite/data/speakers/2016/london/andi-mann.yml
new file mode 100644
index 000000000..2963e27ff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/andi-mann.yml
@@ -0,0 +1,3 @@
+name: "Andi Mann"
+twitter: "AndiMann"
+bio: ""
diff --git a/exampleSite/data/speakers/2016/london/benjamin-wootton.yml b/exampleSite/data/speakers/2016/london/benjamin-wootton.yml
new file mode 100644
index 000000000..ba51b1b56
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/benjamin-wootton.yml
@@ -0,0 +1,3 @@
+name: "Benjamin Wootton"
+twitter: "benjaminwootton"
+bio: "Benjamin Wootton is a co-founder of Sendachi, a consultancy that help organisations apply DevOps, Continuous Delivery and Pragmatic Agile practices to improve the outcomes of software delivery projects. He is also the organiser of Docker London Meetup."
diff --git a/exampleSite/data/speakers/2016/london/casey-west.yml b/exampleSite/data/speakers/2016/london/casey-west.yml
new file mode 100644
index 000000000..466dac777
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/casey-west.yml
@@ -0,0 +1,6 @@
+name: "Casey West"
+twitter: "caseywest"
+bio: "Casey West is a Principal Technologist focused on Pivotal's Cloud Foundry Platform and lives in Pittsburgh raising three sarcastic children.
+
+
+Working with Internet infrastructure, web app security, and design taught Casey to be a paranoid, UX-oriented, problem solving Internet plumber; his earliest contributions to Perl live to this day on your Mac. Casey's speaking and writing ranges from open source communities and culture to technical architecture and automation tips and tricks."
diff --git a/exampleSite/data/speakers/2016/london/claire-agutter.yml b/exampleSite/data/speakers/2016/london/claire-agutter.yml
new file mode 100644
index 000000000..5d28c6655
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/claire-agutter.yml
@@ -0,0 +1,6 @@
+name: "Claire Agutter"
+twitter: "claireagutter"
+bio: "Claire Agutter is the director of ITSM Zone, providers of high quality e-learning for IT professionals. Claire uses her background in service management operations and consultancy to blend old and new best practice to give organizations the toolkit they need to deliver business value. From ITIL to DevOps, OBASHI and Agile Service Management, Claire believes in sharing knowledge and experience between organizations, and hosts the popular ITSM Crowd hangouts that provide practical advice to professionals around the world.
+
+
+[Blog](http://itsm.zone/knowledge-desk)"
diff --git a/exampleSite/data/speakers/2016/london/gareth-rushgrove.yml b/exampleSite/data/speakers/2016/london/gareth-rushgrove.yml
new file mode 100644
index 000000000..e7e2fe80e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/gareth-rushgrove.yml
@@ -0,0 +1,6 @@
+name: "Gareth Rushgrove"
+twitter: "garethr"
+bio: "Gareth Rushgrove is a senior software engineer at Puppet Labs. He works remotely from Cambridge (UK) building interesting tools for people to better manage infrastructure. Previously he worked for the UK Government Digital Service focused on infrastructure, operations and information security.
+
+
+When not working he can be found writing the Devops Weekly newsletter or hacking on software in new-fangled programming languages."
diff --git a/exampleSite/data/speakers/2016/london/gene-kim.yml b/exampleSite/data/speakers/2016/london/gene-kim.yml
new file mode 100644
index 000000000..b51c3968d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/gene-kim.yml
@@ -0,0 +1,11 @@
+name: "Gene Kim"
+twitter: "RealGeneKim"
+bio: "Gene is a multiple award winning CTO, researcher and author. He was founder and CTO of Tripwire for 13 years. He has written three books, including “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win,” “The Visible Ops Handbook” and the upcoming “DevOps Handbook.”
+
+
+Gene is a huge fan of IT operations, and how it can enable developers to maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. In 2007, ComputerWorld added Gene to the “40 Innovative IT People Under The Age Of 40” list, and was given the Outstanding Alumnus Award by the Department of Computer Sciences at Purdue University for achievement and leadership in the profession.
+
+
+
+[Blog](http://itrevolution.com/devops-blog/)"
+
diff --git a/exampleSite/data/speakers/2016/london/jeromy-carriere.yml b/exampleSite/data/speakers/2016/london/jeromy-carriere.yml
new file mode 100644
index 000000000..e2632cce9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/jeromy-carriere.yml
@@ -0,0 +1,3 @@
+name: "Jeromy Carriere"
+twitter: "sjcarriere"
+bio: "Jeromy Carrier works an Engineering Director at Google. He specialises in Software and systems architecture, architecture evaluation, architecture-based software development lifecycle design."
diff --git a/exampleSite/data/speakers/2016/london/joanne-molesky.yml b/exampleSite/data/speakers/2016/london/joanne-molesky.yml
new file mode 100644
index 000000000..fa82d40bf
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/joanne-molesky.yml
@@ -0,0 +1,17 @@
+name: "Joanne Molesky"
+twitter: "jemolesky"
+bio: "Joanne Molesky is a Principal Associate at ThoughtWorks and is coauthor of _The Lean Enterprise: How High Performance Organizations Innovated at Scale_. She specializes in IT Governance, Risk and Compliance and has led our global practice team for Continuous Delivery and the internal Information Security team.
+
+
+Since publishing the book with co-authors Jez Humble and Barry O'Reilly, she has been traveling the globe, presenting to executives how the principles behind the Lean movement can be applied to the use of information technology to improve their organization's performance.
+
+
+Joanne is recognised by HP Enterprise as one of the five women IT leaders to watch in 2016.
+
+
+
+[@leanenterprise](https://twitter.com/leanenterprise)
+
+
+
+[Blog](https://www.thoughtworks.com/insights)"
diff --git a/exampleSite/data/speakers/2016/london/john-clapham.yml b/exampleSite/data/speakers/2016/london/john-clapham.yml
new file mode 100644
index 000000000..feff1150f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/john-clapham.yml
@@ -0,0 +1,6 @@
+name: "John Clapham"
+twitter: "johnC_Bristol"
+bio: "John Clapham is an independent coach, trainer and consultant. Founder of Cotelic, he specialises in DevOps and Agile, helping teams to build great products, and organisations to become more effective, productive and enjoyable to work in. His broad experience in software development ranges from start-up to enterprise scale, formed in the publishing, telecommunications, commerce, defense and public sector arenas.
+
+
+John’s initiatives are fuelled by coffee, Lego and Bristol's frequent inclement weather. He occasionally surfaces as @JohnC_Bristol, and has been rumoured to blog at [johnclapham.wordpress.com](http://johnclapham.wordpress.com)."
diff --git a/exampleSite/data/speakers/2016/london/justin-cormack.yml b/exampleSite/data/speakers/2016/london/justin-cormack.yml
new file mode 100644
index 000000000..4651c288e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/justin-cormack.yml
@@ -0,0 +1,3 @@
+name: "Justin Cormack"
+twitter: "justincormack"
+bio: "Justin Cormack is an engineer at Docker, and co-author of Docker in Production: Lessons from the Trenches. He worked for Unikernel Systems, and now Docker in Cambridge UK. He is interested in how we can make systems software adapt to modern devops practices, as it is one of the last areas to aspire to the monolithic and slow moving."
diff --git a/exampleSite/data/speakers/2016/london/kris-saxton.yml b/exampleSite/data/speakers/2016/london/kris-saxton.yml
new file mode 100644
index 000000000..5b506c441
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/kris-saxton.yml
@@ -0,0 +1,6 @@
+name: "Kris Saxton"
+twitter: "KrisSaxton"
+bio: "Kris has been a UNIX systems engineer for more than 10 years, with more than half of that time spent building ISPs and ASPs. A technical authority on all things data centre, he has held CTO positions and worked on automating server estates comprised of tens of thousands of machines.
+
+
+A London School of Economics graduate and erstwhile Mountaineer, proprietary software is his mistress, but his heart lies with open source software."
diff --git a/exampleSite/data/speakers/2016/london/oliver-wood.yml b/exampleSite/data/speakers/2016/london/oliver-wood.yml
new file mode 100644
index 000000000..a7fd5334b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/oliver-wood.yml
@@ -0,0 +1,3 @@
+name: "Oliver Wood"
+twitter: "coldclimate"
+bio: ""
diff --git a/exampleSite/data/speakers/2016/london/philippe-guenet.yml b/exampleSite/data/speakers/2016/london/philippe-guenet.yml
new file mode 100644
index 000000000..f29052f23
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/philippe-guenet.yml
@@ -0,0 +1,9 @@
+name: "Philippe Guenet"
+twitter: "WeAreLeanIT"
+bio: "Philippe joined GFT (previously as Rule Financial) in 2011 and has worked on the Operational Excellence of IT delivery in the Financial sector.
+
+
+With a view to scale Agile adoption, Philippe has focused on Lean and DevOps and the transformation of Banks to continuous delivery. Beyond the technology, Philippe is interested in the Management aspects: organisation, governance, management information, continuous improvement programmes, Enterprise and Solution Architectures.
+
+
+Outside of work, Philippe loves spending time with family, is a motorsport enthusiast (owning several motorcycles) and thrill seeker practicing off-piste skiing and BMX racing."
diff --git a/exampleSite/data/speakers/2016/london/simon-vans-colina.yml b/exampleSite/data/speakers/2016/london/simon-vans-colina.yml
new file mode 100644
index 000000000..4269ecf1a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/simon-vans-colina.yml
@@ -0,0 +1,3 @@
+name: "Simon Vans-Colina"
+twitter: "simonvc"
+bio: "Simon is a DevOps, Infrastructure, and Platform engineer at Mondo, a StartUp building a bank."
diff --git a/exampleSite/data/speakers/2016/london/thiago-almeida.yml b/exampleSite/data/speakers/2016/london/thiago-almeida.yml
new file mode 100644
index 000000000..1c55afa06
--- /dev/null
+++ b/exampleSite/data/speakers/2016/london/thiago-almeida.yml
@@ -0,0 +1,6 @@
+name: "Thiago Almeida"
+twitter: "nzthiago"
+bio: "Thiago grew up in Brazil and lived in New Zealand for a long time before joining the Microsoft team in Redmond. He's part of the team that drives adoption of new technologies, focusing on cloud computing, open source, and DevOps practices.
+
+
+[Blog](http://talmeida.net)"
diff --git a/exampleSite/data/speakers/2016/madison/aaron-aldrich.yml b/exampleSite/data/speakers/2016/madison/aaron-aldrich.yml
new file mode 100644
index 000000000..fb7c1e46b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/aaron-aldrich.yml
@@ -0,0 +1,7 @@
+name: "Aaron Aldrich"
+twitter: "crayzeigh"
+bio: "Having some personal struggles with identity and mental wellness I recognize how important it is to reinforce the message that “Your Story Matters” as often and as broadly as possible. The DevOps message that we all have a story to share has resonated loudly with me and encouraged me to continue to share my own.
+
+My career path has always been hurdled towards technology, but my heart has always been with the people. No matter where I’ve been, the people are always the thing that I love above the labor. But nevertheless, the labor has consistently caused extra stress and burnout. Over 10 years I’ve worked in four different companies and dealt with 4 different types of on-call responsibility and 4 different types of burnout. It’s time to stop the burn and start healing the industry.
+
+Besides work and DevOps, I have a wife and 4 kids at home. I’m a musician and I love games of all types because of their unique power to bring diverse people together to a single purpose. Nothing breaks down barriers faster than collaborative creative efforts or a game of Mario Kart."
diff --git a/exampleSite/data/speakers/2016/madison/alison-stanton.yml b/exampleSite/data/speakers/2016/madison/alison-stanton.yml
new file mode 100644
index 000000000..ce503f592
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/alison-stanton.yml
@@ -0,0 +1,3 @@
+name: "Alison Stanton"
+twitter: "alison985"
+bio: "As Chief Problem Solver at Stanton Ventures Alison focuses on business intelligence reporting, product measurement, process improvement through automation, and technical training. She makes data accessible, discoverable, and actionable for Operations teams, Product Managers, and clients. Currently, her main languages are SQL, Python, and LookML. She loves knitting and using technology to empower audacious ideas."
diff --git a/exampleSite/data/speakers/2016/madison/andy-fleener.yml b/exampleSite/data/speakers/2016/madison/andy-fleener.yml
new file mode 100644
index 000000000..60386aead
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/andy-fleener.yml
@@ -0,0 +1,3 @@
+name: "Andy Fleener"
+twitter: "andyfleener"
+bio: "Andy Fleener is a Humanist, and a New View Safety Nerd who believes software is as much about the people building and running it as it is the people using it. He is a Senior Software Engineer at SportsEngine where he’s been doing a mix of development and operations for the last 5 years. Andy enjoys music, football, sushi, oxford commas, and laughing at all the things millennials are ruining."
diff --git a/exampleSite/data/speakers/2016/madison/bridget-kromhout.yml b/exampleSite/data/speakers/2016/madison/bridget-kromhout.yml
new file mode 100644
index 000000000..de1378824
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/bridget-kromhout.yml
@@ -0,0 +1,3 @@
+name: "Bridget Kromhout"
+twitter: "bridgetkromhout"
+bio: "Bridget Kromhout is a Principal Technologist for Cloud Foundry at Pivotal. Her CS degree emphasis was in theory, but she now deals with the concrete (if ‘cloud’ can be considered tangible). After years as an operations engineer (most recently at DramaFever), she traded in oncall for more travel. A frequent speaker at tech conferences, she helps organize tech meetups at home in Minneapolis, serves on the program committee for Velocity, and acts as a global core organizer for devopsdays. She podcasts at Arrested DevOps, occasionally blogs at bridgetkromhout.com, and is active in a Twitterverse near you."
diff --git a/exampleSite/data/speakers/2016/madison/cea-stapleton.yml b/exampleSite/data/speakers/2016/madison/cea-stapleton.yml
new file mode 100644
index 000000000..0f63634d4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/cea-stapleton.yml
@@ -0,0 +1,3 @@
+name: "Cea Stapleton"
+twitter: "ceaess"
+bio: "Cea fights fire and makes infrastructure from python code at healthfinch. She transitioned relatively recently from full-stack dev to ops engineer, and has been loving every minute of her new role."
diff --git a/exampleSite/data/speakers/2016/madison/christian-weber.yml b/exampleSite/data/speakers/2016/madison/christian-weber.yml
new file mode 100644
index 000000000..a367bed5f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/christian-weber.yml
@@ -0,0 +1,3 @@
+name: "Christian Weber"
+twitter: ""
+bio: "Christian Weber is a Problem Solver at GitHub. Previously spending the last 6 years in various flavors of Finance and I.T., Christian focuses on Developer Enablement and applying Open Source methodology in the Enterprise world."
diff --git a/exampleSite/data/speakers/2016/madison/dakota-dux.yml b/exampleSite/data/speakers/2016/madison/dakota-dux.yml
new file mode 100644
index 000000000..cd43b547e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/dakota-dux.yml
@@ -0,0 +1,3 @@
+name: "Dakota dux"
+twitter: "ddux"
+bio: "Dakota Dux is an engineer at Nextpoint, a Chicago and Madison based company that provides an online document management platform for litigators. Dakota is passionate about building flexible systems and not deploying on Fridays. With 10+ years of writing ruby, he’s seen a few things. When he’s not slinging code, he moonlights as the head coach for the University of Wisconsin Alpine Ski Team. He likes to describe his coaching philosophy as Extreme Fundamentals. If you see him around ask him to tell you the penguin joke."
diff --git a/exampleSite/data/speakers/2016/madison/emily-dowdle.yml b/exampleSite/data/speakers/2016/madison/emily-dowdle.yml
new file mode 100644
index 000000000..6fe01ff94
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/emily-dowdle.yml
@@ -0,0 +1,3 @@
+name: "Emily Dowdle"
+twitter: "editingemily"
+bio: "Emily is a full-stack engineer at Wazee Digital. She specializes in DevOps, back-end architecture and team management. Emily is a competitive powerlifter and can deadlift 265 lbs. She’s active in the Denver tech community, is a frequent speaker and blogs at emilydowdle.com."
diff --git a/exampleSite/data/speakers/2016/madison/gareth-greenaway.yml b/exampleSite/data/speakers/2016/madison/gareth-greenaway.yml
new file mode 100644
index 000000000..37a91665f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/gareth-greenaway.yml
@@ -0,0 +1,3 @@
+name: "Gareth Greenaway"
+twitter: "garethgreenaway"
+bio: ""
diff --git a/exampleSite/data/speakers/2016/madison/james-jones.yml b/exampleSite/data/speakers/2016/madison/james-jones.yml
new file mode 100644
index 000000000..43cc9a9d4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/james-jones.yml
@@ -0,0 +1,3 @@
+name: "James Jones"
+twitter: "velocity303"
+bio: "James Jones is a Technical Solutions Engineer at Puppet. He joined Puppet in 2014 after working at Oracle as an Operations Engineer for several years. Focusing on environments that are both dynamic and include different operating systems and technologies he looks to bring his experience to customers getting started with building out automation solutions with Puppet Enterprise."
diff --git a/exampleSite/data/speakers/2016/madison/jeff-smith.yml b/exampleSite/data/speakers/2016/madison/jeff-smith.yml
new file mode 100644
index 000000000..ed53e5b0f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/jeff-smith.yml
@@ -0,0 +1,3 @@
+name: "Jeff Smith"
+twitter: "DarkAndNerdy"
+bio: "Jeff Smith has been working in the Technology field for almost 15 years. He has a love for Open Source software and workflow management. Jeff currently serves as the Manager for the Site Reliability Engineering group at GrubHub."
diff --git a/exampleSite/data/speakers/2016/madison/joe-laha.yml b/exampleSite/data/speakers/2016/madison/joe-laha.yml
new file mode 100644
index 000000000..abe654ca4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/joe-laha.yml
@@ -0,0 +1,3 @@
+name: "Joe Laha"
+twitter: "joelaha"
+bio: "Joe Laha is an organizer of devopsdays Minneapolis He lives in Minneapolis’ North Loop neighborhood with his partner, Bridget Kromhout, their cats Iria & Nimoy, and way too much cycling-themed art. Aside from cycling, Joe enjoys homebrew, heavy metal guitar, and arguing about sci-fi TV of the 1990s."
diff --git a/exampleSite/data/speakers/2016/madison/joe-nuspl.yml b/exampleSite/data/speakers/2016/madison/joe-nuspl.yml
new file mode 100644
index 000000000..f57d4bf67
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/joe-nuspl.yml
@@ -0,0 +1,5 @@
+name: "Joe Nuspl"
+twitter: "JoeNuspl"
+bio: "I am a senior operations engineer at Workday. One of the DevOpsDays Portland 2016 organizers. Author of the zap cookbook for Chef. Aspiring culinary chef.
+
+http://nvwls.github.io/ https://github.com/nvwls https://boardgamegeek.com/collection/user/nvwls"
diff --git a/exampleSite/data/speakers/2016/madison/kevan-bard.yml b/exampleSite/data/speakers/2016/madison/kevan-bard.yml
new file mode 100644
index 000000000..6bd654d2f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/kevan-bard.yml
@@ -0,0 +1,3 @@
+name: "Kevan Bard"
+twitter: "swisskbar"
+bio: ""
diff --git a/exampleSite/data/speakers/2016/madison/kevin-babcock.yml b/exampleSite/data/speakers/2016/madison/kevin-babcock.yml
new file mode 100644
index 000000000..ad1adabe3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/kevin-babcock.yml
@@ -0,0 +1,3 @@
+name: "Kevin Babcock"
+twitter: ""
+bio: "Kevin Babcock is Principal Security Engineer at PagerDuty, the enterprise incident resolution service. He has over 15 years of experience in the information security field, including application security, authentication, encryption, Web security, anti-spam, and network security. He has worked with organizations such as Symantec, SafeWeb, and Box. Babcock is a native of Sun Prairie, holds a B.S. in Engineering and Applied Science from the California Institute of Technology, and is a Certified Information Systems Security Professional (CISSP)."
diff --git a/exampleSite/data/speakers/2016/madison/michael-lanyon.yml b/exampleSite/data/speakers/2016/madison/michael-lanyon.yml
new file mode 100644
index 000000000..a83bccf22
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/michael-lanyon.yml
@@ -0,0 +1,5 @@
+name: "Michael Lanyon"
+twitter: "lanyonm"
+bio: "Hi. I’m Mike. I’m a VP of Engineering at Critical Mass. In my role at CM I lead teams that work on the systems and data that power customer experiences. I started as our first application developer in the United States, and after my first “worked fine in dev” experience, have been trying to make delivering value to our clients’ customers as routine and predictable as possible. Automation, measurement, and team building are my passions.
+
+Outside of work I’m a competitive cyclist and a DevOpsDays Chicago organizer. I was first introduced to DevOps back in 2011 and had my mind blown by a few luminaries of the DevOps movement. I find the passion and enthusiasm for iterative improvement in technology absolutely irresistible."
diff --git a/exampleSite/data/speakers/2016/madison/michael-stahnke.yml b/exampleSite/data/speakers/2016/madison/michael-stahnke.yml
new file mode 100644
index 000000000..be5361794
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/michael-stahnke.yml
@@ -0,0 +1,3 @@
+name: "Michael Stahnke"
+twitter: "stahnma"
+bio: "Michael Stahnke is Director of Engineering at Puppet Labs. He’s had a few roles at Puppet, and been a part of the company growing from 35 to 440+ employees. He’s been heavily involved with release engineering and community throughout his tenure. He came to Puppet Labs from Caterpillar, Inc. where he was an infrastructure architect, system administration team lead, and open source evangelist. Michael also helped get the Extra Packages for Enterprise Linux (EPEL) repository off the ground in 2005, is the author of Pro OpenSSH (Apress, 2005), and rants continuously about technology and computers, while striving to learn more about them."
diff --git a/exampleSite/data/speakers/2016/madison/rhea-ghosh.yml b/exampleSite/data/speakers/2016/madison/rhea-ghosh.yml
new file mode 100644
index 000000000..23438f7dc
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/rhea-ghosh.yml
@@ -0,0 +1,3 @@
+name: "Rhea Ghosh"
+twitter: ""
+bio: "Rhea is a DevOps Engineer at HERE (formerly known as NAVTEQ) in Chicago in their Highly Automated Driving division, working on automating infrastructure in AWS. Prior to becoming a DevOps Engineer, Rhea started her career as a high school math teacher before transitioning to technology consulting. A consultant for 7 years, Rhea made the decision to follow her gut to be a DBA at Spot Trading, which is where her interest in DevOps started. When she’s not devopsing, she lives at the wood shop, creating furniture and turning functional and decorative “art” with occasional breaks to see her cats and dog."
diff --git a/exampleSite/data/speakers/2016/madison/suzie-prince.yml b/exampleSite/data/speakers/2016/madison/suzie-prince.yml
new file mode 100644
index 000000000..c9398e665
--- /dev/null
+++ b/exampleSite/data/speakers/2016/madison/suzie-prince.yml
@@ -0,0 +1,5 @@
+name: "Suzie Prince"
+twitter: "pm_suzie"
+bio: "Suzie Prince is Head of Product for ThoughtWorks product division building pioneering tools for software development teams. She has over ten years experience as a product manager designing and delivering software that is valuable, usable, feasible, and desirable.
+
+She likes pushing buttons to deploy, feature toggles and pager duty. She also likes burritos, beer and hiking."
diff --git a/exampleSite/data/speakers/2016/minneapolis/aj-bowen.yml b/exampleSite/data/speakers/2016/minneapolis/aj-bowen.yml
new file mode 100644
index 000000000..86cfead40
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/aj-bowen.yml
@@ -0,0 +1,3 @@
+name: "AJ Bowen"
+twitter: "s0ulshake"
+bio: "AJ Bowen is on a mission to containerize all the things and help others to do the same. In the past, AJ has done technical support, evangelism, and customer and developer advocacy at Gandi. Her other experience includes heavy involvement in the Occupy movement in Kansas City, where she discovered the delightful and complicated world of horizontal organization in groups of passionate people with wildly diverse political perspectives, and humanitarian work in Haiti. AJ doesn’t like being told what to do—or telling others what to do—and is on a constant mission to eliminate unnecessary hierarchy."
diff --git a/exampleSite/data/speakers/2016/minneapolis/allan-espinosa.yml b/exampleSite/data/speakers/2016/minneapolis/allan-espinosa.yml
new file mode 100644
index 000000000..27a4b19e4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/allan-espinosa.yml
@@ -0,0 +1,3 @@
+name: "Allan Espinosa"
+twitter: "AllanEspinosa"
+bio: "Allan works at Engineyard where he supports customers' Deis, Docker and Kubernetes infrastructures in production. Prior to that, he worked on managing one of the world's largest CloudFoundry deployments using Chef.\n Allan is also the author of _Docker High Performance_ from Packt Publishing. The book contains some worked examples and high level concepts on how to get Docker up and running in production."
diff --git a/exampleSite/data/speakers/2016/minneapolis/antoinette-smith.yml b/exampleSite/data/speakers/2016/minneapolis/antoinette-smith.yml
new file mode 100644
index 000000000..729e14721
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/antoinette-smith.yml
@@ -0,0 +1,3 @@
+name: "Antoinette Smith"
+twitter: "ant_auth"
+bio: "Antoinette is an instructor at Prime Digital Academy, an 18-week coding bootcamp in scenic Bloomington, MN. In her free time, she co-organizes events for the Blacks in Technology Twin Cities chapter and looks forward to completing a dual masters in business administration and software engineering at the end of this year."
diff --git a/exampleSite/data/speakers/2016/minneapolis/ben-zvan.yml b/exampleSite/data/speakers/2016/minneapolis/ben-zvan.yml
new file mode 100644
index 000000000..67e4ba118
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/ben-zvan.yml
@@ -0,0 +1,3 @@
+name: "Ben Zvan"
+twitter: "BenZvan"
+bio: "Ben Zvan is an IT professional who has been using Linux since 1996. He started his professional Ops career at the University of Minnesota in 2006 and moved to Capella University, a for-profit university in Minnesota, in 2011. He has concentrated on the mantra \"simplify, standardize, automate\" since hearing the phrase from Jim Hall at the U of MN, when he realized that's what he had been doing for years. Learning about agile and DevOps made him an instant evangelist. He currently struggles with change management, production support, and not having enough time for photography or motorcycling."
diff --git a/exampleSite/data/speakers/2016/minneapolis/charity-majors.yml b/exampleSite/data/speakers/2016/minneapolis/charity-majors.yml
new file mode 100644
index 000000000..d6b7fbf9c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/charity-majors.yml
@@ -0,0 +1,3 @@
+name: "Charity Majors"
+twitter: "mipsytipsy"
+bio: "Cofounder and CTO of Honeycomb, a new startup focused on mining machine data. Previously running infrastructure at Parse, engineering manager at Facebook. Worked with the RocksDB team to build and deploy world’s first Mongo+Rocks in production. Likes single malt scotch."
diff --git a/exampleSite/data/speakers/2016/minneapolis/corwin-atkins.yml b/exampleSite/data/speakers/2016/minneapolis/corwin-atkins.yml
new file mode 100644
index 000000000..65a127e8c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/corwin-atkins.yml
@@ -0,0 +1,3 @@
+name: "Corwin Atkins"
+twitter: "CorwinAtkins"
+bio: "A Service Desk Team Lead at the University Of Minnesota, Corwin has been in IT since 2005. He is slowly getting over his resentment toward Disney regarding Star Wars, and eagerly awaits the day when his daughter can beat him in Magic, rendering him obsolete."
diff --git a/exampleSite/data/speakers/2016/minneapolis/dana-engebretson.yml b/exampleSite/data/speakers/2016/minneapolis/dana-engebretson.yml
new file mode 100644
index 000000000..a6a09df2a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/dana-engebretson.yml
@@ -0,0 +1,3 @@
+name: "Dana Engebretson"
+twitter: "bigdana"
+bio: "Dana Engebretson and Python are like synchronized swimmers in a sea of data. She is a data scientist building classification models for BI Worldwide, which somehow led to lots of devops-related fun too. Dana founded PyLadies Twin Cities, our local nest of Python women and allies. She enjoys mentoring and thinking about universal design."
diff --git a/exampleSite/data/speakers/2016/minneapolis/jamie-riedesel.yml b/exampleSite/data/speakers/2016/minneapolis/jamie-riedesel.yml
new file mode 100644
index 000000000..5d127193b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/jamie-riedesel.yml
@@ -0,0 +1,3 @@
+name: "Jamie Riedesel"
+twitter: "sysadm1138"
+bio: "Jamie Riedesel started out in Government IT for the City of St. Paul and has since moved into the private sector. Currently she’s working remotely for a San Francisco based startup. In the meantime, she’s earned the Chuck Yerkes award from LOPSA for being helpful online, and is trying to become more helpful in person."
diff --git a/exampleSite/data/speakers/2016/minneapolis/jasmine-russell.yml b/exampleSite/data/speakers/2016/minneapolis/jasmine-russell.yml
new file mode 100644
index 000000000..a2b74b672
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/jasmine-russell.yml
@@ -0,0 +1,3 @@
+name: "Jasmine Russell"
+twitter: "JasMRussell"
+bio: "Jasmine holds 8 years of experience within quantitative and qualitative market research and digital analytics across markets of: retail, consumer products, healthcare, service and technology industries. From her analytic focus, she brings a knowledge base of optimizing market strategy–guiding broad concepts into strategic business action. Jasmine additionally works within the Minneapolis community with groups to facilitate women empowerment, diversity development (i.e. P.O.C.’s), collaborative student learning, technology development, and community speaker concept development (i.e. event speaker curation). Founder of [theproceed.com](http://www.theproceed.com/)."
diff --git a/exampleSite/data/speakers/2016/minneapolis/jeff-smith.yml b/exampleSite/data/speakers/2016/minneapolis/jeff-smith.yml
new file mode 100644
index 000000000..1048f7351
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/jeff-smith.yml
@@ -0,0 +1,3 @@
+name: "Jeff Smith"
+twitter: "DarkAndNerdy"
+bio: "Jeff Smith has been in the technology field for over 15 years, oscillating between manager and individual contributor. He currently serves as the Manager of Site Reliability Engineering at GrubHub. Jeff enjoys discussing the psychological aspect of problems in organizations. Jeff is also one of the co-founders of the Chicago Nerd Social Club. He occasionally musters up the strength to write on his All Things Dork blog."
diff --git a/exampleSite/data/speakers/2016/minneapolis/john-kelly.yml b/exampleSite/data/speakers/2016/minneapolis/john-kelly.yml
new file mode 100644
index 000000000..76aa808f3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/john-kelly.yml
@@ -0,0 +1,3 @@
+name: "John Kelly"
+twitter: "jkelly3"
+bio: "John Kelly is a Director of Software Engineering at SPS Commerce. He spent the early part of his career as a professional LEGO model builder. John lives in South Minneapolis with his wife, two daughters, and enough LEGO bricks to swim in."
diff --git a/exampleSite/data/speakers/2016/minneapolis/matt-genelin.yml b/exampleSite/data/speakers/2016/minneapolis/matt-genelin.yml
new file mode 100644
index 000000000..45eaeb89e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/matt-genelin.yml
@@ -0,0 +1,3 @@
+name: "Matt Genelin"
+twitter: "magellanOnOps"
+bio: "Matt Genelin is a Senior DevOps Engineer @optum. Dad, Sys Admin, Improv. comedian, amateur radio op. Matt has been a System Administrator for big and small companies for 15 years."
diff --git a/exampleSite/data/speakers/2016/minneapolis/megan-carney.yml b/exampleSite/data/speakers/2016/minneapolis/megan-carney.yml
new file mode 100644
index 000000000..6e4f90d22
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/megan-carney.yml
@@ -0,0 +1,3 @@
+name: "Megan Carney"
+twitter: "PwnieFan"
+bio: "Megan Carney is an Infosecurity engineer at Yelp. Previous to working with Yelp, she worked as an analyst at a university and a retail company. She tries to keep her paranoia at healthy levels while protecting Yelp from the evils of the Internet."
diff --git a/exampleSite/data/speakers/2016/minneapolis/mike-bjerkness.yml b/exampleSite/data/speakers/2016/minneapolis/mike-bjerkness.yml
new file mode 100644
index 000000000..131d6c0a8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/mike-bjerkness.yml
@@ -0,0 +1,3 @@
+name: "Mike Bjerkness"
+twitter: "mikebjerkness"
+bio: "Mike Bjerkness is a Director of Software Engineering at SPS Commerce. Mike has worked in many facets of software development all the way from C++ coding radar systems, to building video games, to writing fancy Flex/Flash applications and attempting to wrangle MongoDB. Mike is a mostly lifelong Minnesota resident with stints in Boston (Raytheon) and Orlando (EA Sports)."
diff --git a/exampleSite/data/speakers/2016/minneapolis/nicole-forsgren.yml b/exampleSite/data/speakers/2016/minneapolis/nicole-forsgren.yml
new file mode 100644
index 000000000..ef4541eca
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/nicole-forsgren.yml
@@ -0,0 +1,3 @@
+name: "Nicole Forsgren"
+twitter: "nicolefv"
+bio: "Dr. Nicole Forsgren is an IT impacts expert who shows leaders and practitioners how to unlock the potential of technology change in their organizations. Best known for her work with tech professionals and as the lead investigator on the State of DevOps Reports, she is the Director of Organizational Performance and Analytics at Chef and an Academic Partner at Clemson University. In a previous life, she was a professor, sysadmin, and hardware performance analyst."
diff --git a/exampleSite/data/speakers/2016/minneapolis/sarah-goff-dupont.yml b/exampleSite/data/speakers/2016/minneapolis/sarah-goff-dupont.yml
new file mode 100644
index 000000000..d003e2f7a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/sarah-goff-dupont.yml
@@ -0,0 +1,3 @@
+name: "Sarah Goff-Dupont"
+twitter: "DevToolSuperFan"
+bio: "Sarah has been working in and around software teams for 14 years – as QA engineer, agile coach, and now a marketer. When not writing about all things agile and/or automated, she can be found reading contemporary fiction, smashing it out & keeping it real at CrossFit, or rolling around on the floor with her kids (possibly all at once)."
diff --git a/exampleSite/data/speakers/2016/minneapolis/tracey-treat.yml b/exampleSite/data/speakers/2016/minneapolis/tracey-treat.yml
new file mode 100644
index 000000000..ca4318596
--- /dev/null
+++ b/exampleSite/data/speakers/2016/minneapolis/tracey-treat.yml
@@ -0,0 +1,3 @@
+name: "Tracey Treat"
+twitter: "RPGprotagonist"
+bio: "Tracey is an incoming junior currently at Rosemount High School. She has been able to pursue her interest in Computer Science through mentoring in CoderDojo with Scratch, AppInventor, Web Development, and Finch Robots. Last year, she and her partner were Regional Winners for the Technovation Challenge with their app, AbroadNet, which helps bridge the gap between foreign exchange and local students. Because of these opportunities, Tracey has learned just as much from the younger students she mentored, as any strong teacher would. She is interested in pursuing a computer science career in the future."
diff --git a/exampleSite/data/speakers/2016/newyork/aaron-atwell.yml b/exampleSite/data/speakers/2016/newyork/aaron-atwell.yml
new file mode 100644
index 000000000..5f538eb04
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/aaron-atwell.yml
@@ -0,0 +1,14 @@
+name: "Aaron Atwell"
+twitter: "theAAexperience"
+bio: "Aaron is part of the team at VictorOps that is working to connect IT teams to
+a product that makes them more effective and helps make their 'on-call lives
+suck less' After spending 'many' years in the staffing industry helping put
+people to work, he's found a new adventure in helping IT teams be more
+effective by improving communication, increasing visibility of infrastructure
+issues, and helping teams get their product to their stakeholders, faster.
+He's also interested in the positive and negative effects technology has on IT
+professional's daily lives. When he's not working you'll find him on his
+mountain bike exploring Colorado's trails, hanging out with family, and
+volunteering to help and support people in need in the Boulder community. He's
+encouraging everyone to love more."
+pronouns: "he/him"
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/newyork/anthony-caiafa.yml b/exampleSite/data/speakers/2016/newyork/anthony-caiafa.yml
new file mode 100644
index 000000000..a9948d996
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/anthony-caiafa.yml
@@ -0,0 +1,11 @@
+name: "Anthony Caiafa"
+twitter: "anthonycaiafa"
+bio: "Anthony currently leads
+Production Engineering @ Bloomberg. Previously he started SRE @ Digitalocean
+and helped scale the company from the very beginning. He has an extensive
+background with startups and helping them grow from inception. Anthony has a
+passion for operations and loves helping as many people as possible in the
+field. He has interest in monitoring, automation, systems, big data,
+distributed systems and much more."
+website: "http://www.anthonycaiafa.com"
+pronouns: "he/him"
diff --git a/exampleSite/data/speakers/2016/newyork/bridget-kromhout.yml b/exampleSite/data/speakers/2016/newyork/bridget-kromhout.yml
new file mode 100644
index 000000000..f30d2421d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/bridget-kromhout.yml
@@ -0,0 +1,5 @@
+name: "Bridget Kromhout"
+twitter: "bridgetkromhout"
+bio: "Bridget Kromhout is a Principal Technologist for Cloud Foundry at Pivotal. Her CS degree emphasis was in theory, but she now deals with the concrete (if ‘cloud’ can be considered tangible). After years as an operations engineer (most recently at DramaFever), she traded in oncall for more travel. A frequent speaker at tech conferences, she helps organize tech meetups at home in Minneapolis, serves on the program committee for Velocity, and acts as a global core organizer for devopsdays. She podcasts at Arrested DevOps, occasionally blogs at bridgetkromhout.com, and is active in a Twitterverse near you."
+pronouns: "she/her"
+website: "http://bridgetkromhout.com/"
diff --git a/exampleSite/data/speakers/2016/newyork/dave-long.yml b/exampleSite/data/speakers/2016/newyork/dave-long.yml
new file mode 100644
index 000000000..f9d94cc80
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/dave-long.yml
@@ -0,0 +1,11 @@
+name: "Dave Long"
+twitter: "davejlong"
+bio: "Dave Long is a devops consultant at Cage Data. He has been working in the
+development world since the mid–2000’s with various companies including
+consultancies, startups and corporations. Throughout his time in the
+development work, Dave has always had an interest in automation to improve
+deployment and the general quality of the final product. Outside of the
+professional world, Dave works with his wife in Uganda, Africa to teach
+technology skills to children with the Kampala Children’s Centre."
+website: "https://cagedata.com/blog"
+pronouns: "he/him"
diff --git a/exampleSite/data/speakers/2016/newyork/david-blank-edelman.yml b/exampleSite/data/speakers/2016/newyork/david-blank-edelman.yml
new file mode 100644
index 000000000..2d445cd07
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/david-blank-edelman.yml
@@ -0,0 +1,12 @@
+name: "David Blank-Edelman"
+twitter: "otterbook"
+bio: "David is the Technical
+Evangelist at Apcera. He has spent close to thirty years in the systems
+administration/DevOps/SRE field in large multiplatform environments including
+Brandeis University, Cambridge Technology Group, MIT Media Laboratory and
+Northeastern University. He is the author of the O'Reilly Otter book
+(Automating System Administration with Perl) and is a frequent invited speaker
+at conferences in the field. David is honored to serve on the USENIX Board of
+Directors. He prefers to pronounce Evangelist with a hard 'g'."
+website: "http://www.apcera.com/dnb"
+pronouns: "he/him"
diff --git a/exampleSite/data/speakers/2016/newyork/eric-sigler.yml b/exampleSite/data/speakers/2016/newyork/eric-sigler.yml
new file mode 100644
index 000000000..664bb1ef4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/eric-sigler.yml
@@ -0,0 +1,3 @@
+name: "Eric Sigler"
+twitter: "esigler"
+bio: "Eric Sigler is an Engineering Manager at PagerDuty, and has formerly led Operations teams at Minted and Missouri S&T. He lives in San Francisco, and when he's not on an incident call he spends his time making cocktails using liquid nitrogen, and hiking around Northern California."
diff --git a/exampleSite/data/speakers/2016/newyork/frank-mitchell.yml b/exampleSite/data/speakers/2016/newyork/frank-mitchell.yml
new file mode 100644
index 000000000..c718db30a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/frank-mitchell.yml
@@ -0,0 +1,12 @@
+name: "Frank Mitchell"
+twitter: "onefrankguy"
+bio: "Frank Mitchell is a Senior Software Engineer at Rapid7. He’s been
+crisscrossing the DevOps Divide for the past ten years searching for that
+mythic place in the middle where code flows freely and conversations are super
+constructive. Along the way he’s helped build CAD engines, video game
+platforms, and open source security solutions. Frank believes shipping
+software is a skill, marketing isn’t an afterthought, and ice cream exists to
+be eaten."
+website: "https://www.frankmitchell.org/"
+pronouns: "he/him"
+
diff --git a/exampleSite/data/speakers/2016/newyork/jason-hand.yml b/exampleSite/data/speakers/2016/newyork/jason-hand.yml
new file mode 100644
index 000000000..606c616cb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/jason-hand.yml
@@ -0,0 +1,11 @@
+name: "Jason Hand"
+twitter: "jasonhand"
+bio: "DevOps Evangelist at VictorOps, organizer
+of DevOpsDays–Rockies, author of ChatOps for Dummies (Wiley), and cohost of
+the \"Community Pulse\" podcast about building community in tech. He has spent
+the last 18 months presenting and building content on a number of DevOps
+topics such as blameless postmortems, ChatOps, and modern incident
+management. A frequent speaker at DevOps-related events and conferences around
+the country, Jason enjoys talking to audiences large and small on a variety
+of technical and non-technical subjects"
+pronouns: "he/him"
diff --git a/exampleSite/data/speakers/2016/newyork/jason-yee.yml b/exampleSite/data/speakers/2016/newyork/jason-yee.yml
new file mode 100644
index 000000000..26e38d352
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/jason-yee.yml
@@ -0,0 +1,4 @@
+name: "Jason Yee"
+twitter: "gitbisect"
+bio: "Jason is a community builder, developer, traveller and chef. He currently works as a technical writer & evangelist at Datadog. When he's not working you can often find him on a plane trying to accumulate more miles or in a restaurant cooking."
+pronouns: "he/him"
diff --git a/exampleSite/data/speakers/2016/newyork/marcus-finley.yml b/exampleSite/data/speakers/2016/newyork/marcus-finley.yml
new file mode 100644
index 000000000..6525288c2
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/marcus-finley.yml
@@ -0,0 +1,17 @@
+name: "Marcus Finley"
+twitter: "marcusafinley"
+bio: "Marcus Finley is the CEO and Co-Founder of FIN Digital and full service
+application development firm in Washington DC. Marcus graduated from Florida
+State University where he majored in Mechanical Engineering and Public
+Administration. Marcus is a certified Scrum Master with expert knowledge of a
+number programming languages, user experience design and web/mobile
+application development. Marcus has managed over $3 million dollars of
+contracted technology development and strategy projects for with an average
+project budget of $200,000. In his professional roles he has provided
+technology strategies and user experiences to achieve client’s goals. He has
+help developed UX practices, lead a number of UX workshops with clients and
+guided companies with emerging needs of validating applications. He co-founded
+a Meetup called Color of Tech to bring together a diverse group of technology
+professionals to network and thrive."
+website: "http://www.fin-digital.com/"
+pronoun: "he/him"
diff --git a/exampleSite/data/speakers/2016/newyork/natacha-springer.yml b/exampleSite/data/speakers/2016/newyork/natacha-springer.yml
new file mode 100644
index 000000000..94331eaa6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/natacha-springer.yml
@@ -0,0 +1,4 @@
+name: "Natacha Springer"
+twitter: "devopsNatacha"
+bio: "Natacha is a happy Cloud Operations Momgineer at Kickstarter."
+pronoun: "she/her"
diff --git a/exampleSite/data/speakers/2016/newyork/nick-doiron.yml b/exampleSite/data/speakers/2016/newyork/nick-doiron.yml
new file mode 100644
index 000000000..84a5ee6f4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/nick-doiron.yml
@@ -0,0 +1,5 @@
+name: "Nick Doiron"
+twitter: "mapmeld"
+bio: "Traveling web developer and mapmaker"
+website: "https://github.com/mapmeld"
+pronouns: "he/him"
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/newyork/nivia-henry.yml b/exampleSite/data/speakers/2016/newyork/nivia-henry.yml
new file mode 100644
index 000000000..cfd257760
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/nivia-henry.yml
@@ -0,0 +1,9 @@
+name: "Nivia Henry"
+twitter: "Lanooba"
+bio: "A technologist with 15 years of experience executing strategy and
+delivering high quality products. Career has included product management;
+program/project execution; people leadership; agile coaching; and enterprise
+agile transformations. Also a proud participant and contributor to the
+technology community, including organizing meet-ups and conferences; speaking
+at local and regional conferences; and guest blogging."
+website: "http://linkedin.com/in/nivia"
diff --git a/exampleSite/data/speakers/2016/newyork/rakia-finley.yml b/exampleSite/data/speakers/2016/newyork/rakia-finley.yml
new file mode 100644
index 000000000..15d434843
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/rakia-finley.yml
@@ -0,0 +1,16 @@
+name: "Rakia Finley"
+twitter: "rakiamc"
+bio: "Rakia Finley is the Co-founder & Innovation Director if FIN. Digital.
+Her work includes consulting on the use of software systems to achieve
+corporate mission, information technology planning and the strategic use of
+technology. She specializes in mastering technology and web systems to
+increase development among organizations. Her strength is in planning for
+specific technology projects that involve complex information systems. With
+over 12 years of experience in the information technology industry, she has
+become an industry expert on organizational issues associated with program
+creation and growth. She is active in the technology-for-enhancement movement
+and is frequently invited to speak at conferences across the country,
+primarily focusing on application deployment strategy, start-up development
+and technology inclusion."
+website: "http://www.fin-digital.com/"
+pronouns: "she/her"
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/newyork/sharon-steed.yml b/exampleSite/data/speakers/2016/newyork/sharon-steed.yml
new file mode 100644
index 000000000..3a3423280
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/sharon-steed.yml
@@ -0,0 +1,14 @@
+name: "Sharon Steed"
+twitter: "sharonsteed"
+bio: "Sharon is the founder of Communilogue, an agency specializing in helping
+teams foster greater collaboration. A life-long stutterer, she uses her
+speech limitation to teach conference audiences as well as teams at companies
+about the value of vulnerability in communication. An internationally
+recognized public speaker, she's given keynotes, hosted workshops and spoken
+in house to companies. Sharon's talks inspire attendees to be more empathetic
+communicators, and they empower attendees to be more inclusive in their
+personal and professional lives. Originally from Chicago, she lives in
+Pittsburgh with her partner. You can learn more about her work at
+Communilogue.com."
+website: "http://www.communilogue.com"
+pronouns: "she/her"
diff --git a/exampleSite/data/speakers/2016/newyork/tim-jarrett.yml b/exampleSite/data/speakers/2016/newyork/tim-jarrett.yml
new file mode 100644
index 000000000..f9c8278b5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/tim-jarrett.yml
@@ -0,0 +1,10 @@
+name: "Tim Jarrett"
+twitter: "tojarrett"
+bio: "Tim Jarrett is Senior Director of Enterprise Security Strategy at
+Veracode. A Grammy-award winning product professional, he joined Veracode in
+2008 and has a Bacon number of 3. He has previously spoken at numerous events
+including the Birst Forward conference, the RSAM User Summit, and regional
+ISACA events, as well as on webcasts for Dark Reading, Black Hat, and the SANS
+Institute. He can be found on Twitter as @tojarrett"
+website: "https://www.veracode.com/blog"
+pronouns: "he/him"
diff --git a/exampleSite/data/speakers/2016/newyork/victoria-jeffrey.yml b/exampleSite/data/speakers/2016/newyork/victoria-jeffrey.yml
new file mode 100644
index 000000000..d1ac9194a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newyork/victoria-jeffrey.yml
@@ -0,0 +1,9 @@
+name: "Victoria Jeffrey"
+twitter: "vickkoala"
+bio: "Victoria is a software engineer @Chef. She's a wanderer turned preschool
+teacher turned coder. During her time at Chef, Victoria has developed on
+Automate (Workflow) and Compliance integrations, spending her days in her code
+cave battling whatever dragons come her way. When she's not hiding out in her
+code cave, you can find her hanging with her little boy admiring the lizards in
+the garden."
+pronouns: “she/her”
diff --git a/exampleSite/data/speakers/2016/newzealand/.yml b/exampleSite/data/speakers/2016/newzealand/.yml
new file mode 100644
index 000000000..7acd96dd1
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/.yml
@@ -0,0 +1,3 @@
+name: ""
+twitter: "Regardless of how fast you can release features into your production environments, unfortunately we caeterlikely that you will have to deal with a business impacting outage at some point. Having resilient mechanisms, and procedures in place means that 90% of these potential issues can be caught before they cause you true headaches, but in a true worst case scenario it's important to be able to quickly diagnose issues, and restore services."
+bio: ""
diff --git a/exampleSite/data/speakers/2016/newzealand/alex-corkin.yml b/exampleSite/data/speakers/2016/newzealand/alex-corkin.yml
new file mode 100644
index 000000000..7070c8ebb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/alex-corkin.yml
@@ -0,0 +1,3 @@
+name: "Alex Corkin"
+twitter: "4lexNZ"
+bio: "I'm Alex. I spent a portion of time in the Army. Then I left to do CompSci at Auckland University. I did an internship at Spark Ventures and now work for Healthlink. My background is in web applications with node and java. More and more I find myself drawn to a mixture of applications and infrastructure. I think Pilsner is superior to IPA and that Guinness is best served at room temperature. If I'm drinking a loaf of bread, that bread ought to be warm."
diff --git a/exampleSite/data/speakers/2016/newzealand/bridget-cowie.yml b/exampleSite/data/speakers/2016/newzealand/bridget-cowie.yml
new file mode 100644
index 000000000..9cde8d752
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/bridget-cowie.yml
@@ -0,0 +1,3 @@
+name: "Bridget Cowie"
+twitter: "bridgetkcowie"
+bio: "I'm the person you call when performance outages get really bad. I work with teams to identify and resolve issues with their production applications both in production environments and also in development & test. I'm happiest when we detect problems as early as possible and I hope that I can work myself out of a job! To sum it up - I love performance, technology & automation (and talking)."
diff --git a/exampleSite/data/speakers/2016/newzealand/damian-brady.yml b/exampleSite/data/speakers/2016/newzealand/damian-brady.yml
new file mode 100644
index 000000000..6b6233040
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/damian-brady.yml
@@ -0,0 +1,5 @@
+name: "Damian Brady"
+twitter: "damovisa"
+bio: "Damian is a Microsoft MVP in Visual Studio and Development Technologies and a Solution Architect for Octopus Deploy in Brisbane, Australia. He is a co-author of Professional Team Foundation Server 2013 from Wiley, and he regularly speaks at conferences, User Groups, and other events.
+
+Damian spends a lot of time training development teams on how to deliver their software better, be it through improving their agile process, code quality, or DevOps strategy. Most of the time youll find him working on Octopus Deploy or helping teams use it better."
diff --git a/exampleSite/data/speakers/2016/newzealand/jethro-carr.yml b/exampleSite/data/speakers/2016/newzealand/jethro-carr.yml
new file mode 100644
index 000000000..e580af9c3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/jethro-carr.yml
@@ -0,0 +1,3 @@
+name: "Jethro Carr"
+twitter: "jethrocarr"
+bio: "Part of the team running www.stuff.co.nz, Jethro likes long walks through Varnish configurations, has the patience of a Lambda instance and consumes coffee like a Java process consumes memory."
diff --git a/exampleSite/data/speakers/2016/newzealand/ken-mugrage.yml b/exampleSite/data/speakers/2016/newzealand/ken-mugrage.yml
new file mode 100644
index 000000000..f7b3c7171
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/ken-mugrage.yml
@@ -0,0 +1,3 @@
+name: "Ken Mugrage"
+twitter: "kmugrage"
+bio: "Ken Mugrage has 25 years of experience in the IT industry, spending the last 7 at ThoughtWorks. During his entire career, Ken has focused on using technology to increase business effectiveness, as opposed to using the latest cool thing. Ken has been focused on Continuous Delivery and DevOps for most of the past decade, working with organizations all over the world, ranging from startups to Fortune 50 companies. He now uses this experience to teach others how to get better at building, testing and deploying software."
diff --git a/exampleSite/data/speakers/2016/newzealand/lindsay-holmwood.yml b/exampleSite/data/speakers/2016/newzealand/lindsay-holmwood.yml
new file mode 100644
index 000000000..f95e3023a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/lindsay-holmwood.yml
@@ -0,0 +1,3 @@
+name: "Lindsay Holmwood"
+twitter: "auxesis"
+bio: "Lindsay Holmwood is a engineering manager living in the Australian Blue Mountains. Lindsay works at the Australian Government's Digital Transformation Office, building clearer, simpler, faster, more humane public services. A long-time contributor to the open source and DevOps communities, he authored cucumber-nagios, Visage, and Flapjack, and has run the Sydney DevOps meetup the past five years. Lindsay speaks internationally about both the cultural and technical side of DevOps, covering Just Culture, complexity, cognitive biases, and monitoring tools. He also won third place at the 1996 Sydney Royal Easter Show LEGO building competition."
diff --git a/exampleSite/data/speakers/2016/newzealand/martina-iglesias.yml b/exampleSite/data/speakers/2016/newzealand/martina-iglesias.yml
new file mode 100644
index 000000000..82857d99f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/martina-iglesias.yml
@@ -0,0 +1,3 @@
+name: "Martina Iglesias"
+twitter: ""
+bio: "Martina is a Lead Backend Engineer at Spotify in the team responsible for album, artist and chart pages. During university she worked as a researcher (Human Brain Project), which lead to a scientific publication. In her free time she enjoys music and dancing tango."
diff --git a/exampleSite/data/speakers/2016/newzealand/mrinal-mukherjee.yml b/exampleSite/data/speakers/2016/newzealand/mrinal-mukherjee.yml
new file mode 100644
index 000000000..7f8a42a73
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/mrinal-mukherjee.yml
@@ -0,0 +1,3 @@
+name: "Mrinal Mukherjee"
+twitter: "mukherjee_mk"
+bio: "With over 12 years of consulting experience in various technical domains, Mrinal is currently working with 'Assurity Consulting' as part of its DevOps practice. He is currently partnering with clients to help them implement CI/CD practices, Infrastructure as Code and to enjoy software development in general!"
diff --git a/exampleSite/data/speakers/2016/newzealand/owen-evans.yml b/exampleSite/data/speakers/2016/newzealand/owen-evans.yml
new file mode 100644
index 000000000..270ecf86b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/owen-evans.yml
@@ -0,0 +1,3 @@
+name: "Owen Evans"
+twitter: "buildmaster"
+bio: "Owen is a developers' developer. Someone who hates being pigeon-holed while writing his own bio. He is currently helping out 8i by leading their platform development, which involves being all things to all people in the business. He likes to get his hands dirty with AWS and Containerisation as well as leading highly productive engineering teams. Before 8i Owen founded and ran a developer startup focusing on one of the first 'serverless' computing platforms, hoist.io. And previously, he helped grow Xero from a company of 20 to 500 when he left as their Chief Architect."
diff --git a/exampleSite/data/speakers/2016/newzealand/pavel-jelinek.yml b/exampleSite/data/speakers/2016/newzealand/pavel-jelinek.yml
new file mode 100644
index 000000000..20ed7257a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/pavel-jelinek.yml
@@ -0,0 +1,3 @@
+name: "Pavel Jelínek"
+twitter: "pajel"
+bio: "AWS DevOps Challenge Auckland 2016 winner. Deploying anything at any time in Docker on Kubernetes."
diff --git a/exampleSite/data/speakers/2016/newzealand/peter-sellars.yml b/exampleSite/data/speakers/2016/newzealand/peter-sellars.yml
new file mode 100644
index 000000000..a8ad3907b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/peter-sellars.yml
@@ -0,0 +1,3 @@
+name: "Peter Sellars"
+twitter: "petersellars"
+bio: "Pete likes to think of himself as a developer, husband, thinker, dad, challenger and footballer. His focus on Continuous Improvement has led him on a journey of discovery through support, development, automated testing and delivery pipeline teams. He has blogged and co-created a Personal Kanban board with Assurity Consulting, introduced teams and organisations to the Improvement Kata and believes strongly that people are an organisation's biggest asset. He shares all he knows with the community. Founder of the Auckland Continuous Delivery Meetup and currently organizer of the Auckland Docker Meetup as well as active in the DevOps community in Auckland - New Zealand. Currently Continuous Delivery Lead at ClearPoint NZ he aims to provide businesses improved customer satisfaction, increased agility and improved outcomes via value-creating delivery pipelines."
diff --git a/exampleSite/data/speakers/2016/newzealand/troy-cornwall.yml b/exampleSite/data/speakers/2016/newzealand/troy-cornwall.yml
new file mode 100644
index 000000000..db6a52edb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/newzealand/troy-cornwall.yml
@@ -0,0 +1,4 @@
+name: "Troy Cornwall"
+twitter: "DevTroy"
+bio: "Currently a Software Developer in the Health Industry.
+Fighting to help make the right technology choices, in a industry which is resistant to change. I started programming in High School. During my second year of Uni, I worked at a start up, Active Mobile Security, helping write a Automation Testing Framework to test an Android Security Platform. When funding fell thru for AMS, I moved to Spark Ventures, and built the CI/CD platform for Bigpipe, as well as internal tooling for Lightbox. Now at HealthLink reworking the way developers here work, using all the buzz word technologies, focusing on increasing the quality of our products, and the speed to market."
diff --git a/exampleSite/data/speakers/2016/ohio/aaron-aldrich.yml b/exampleSite/data/speakers/2016/ohio/aaron-aldrich.yml
new file mode 100644
index 000000000..a08c05315
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/aaron-aldrich.yml
@@ -0,0 +1,2 @@
+name: "Aaron Aldrich"
+bio: "DevOps evangelist and consultant with @CageData, I love people and the people aspect of DevOps. Father of Four, Husband, musician and board gamer, balancing being human and getting devops done."
diff --git a/exampleSite/data/speakers/2016/ohio/bill-condo.yml b/exampleSite/data/speakers/2016/ohio/bill-condo.yml
new file mode 100644
index 000000000..a809c723c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/bill-condo.yml
@@ -0,0 +1,2 @@
+name: "Bill Condo"
+bio: "Bill is a long time PHP developer, small business owner, and a local PHP meetup organizer living in Columbus, OH. He frequently covers devops, application architecture, and security via public speaking and mentoring."
diff --git a/exampleSite/data/speakers/2016/ohio/chris-mcfee.yml b/exampleSite/data/speakers/2016/ohio/chris-mcfee.yml
new file mode 100644
index 000000000..1965acaa0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/chris-mcfee.yml
@@ -0,0 +1,2 @@
+name: "Chris Mcfee"
+bio: "Currently maturing DevOps practices, including continuous integration, continuous delivery, infrastructure as code, and configuration management / automation. Experience designing and implementing highly available enterprise-ready systems and processes and infrastructure solutions; while providing engineering, deployment, administration, and support. Master's degree in Digital Sciences with a focus on Enterprise Architecture from Kent State University."
diff --git a/exampleSite/data/speakers/2016/ohio/clinton-wolfe.yml b/exampleSite/data/speakers/2016/ohio/clinton-wolfe.yml
new file mode 100644
index 000000000..be6b67656
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/clinton-wolfe.yml
@@ -0,0 +1,2 @@
+name: "Clinton Wolfe"
+bio: "Clinton Wolfe leads the DevOps Practice at OmniTI, which means he voluntarily chooses to go into heavily siloed, dysfunctional organizations and try to get them to talk to each other with as few stabbings as possible. He's especially interested in testable infrastructure, and the processes needed to support quality throughout the application lifecycle. He is also Oliver and Sylvia’s Daddy."
diff --git a/exampleSite/data/speakers/2016/ohio/eric-sigler.yml b/exampleSite/data/speakers/2016/ohio/eric-sigler.yml
new file mode 100644
index 000000000..041832206
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/eric-sigler.yml
@@ -0,0 +1,2 @@
+name: "Eric Sigler"
+bio: "Eric Sigler is the Head of DevOps for PagerDuty, evangelizing culture, automation, measurement, and sharing. Prior to his current role, he lead the Developer Tools team, implementing Continuous Deployment across the company’s infrastructure. During his 16 year career in infrastructure engineering, he’s been the Technical Operations Manager at Minted, improving holiday cheer through high availability, and Manager of Computing Systems at Missouri S&T, saving the world one student at a time."
diff --git a/exampleSite/data/speakers/2016/ohio/jarred-olson.yml b/exampleSite/data/speakers/2016/ohio/jarred-olson.yml
new file mode 100644
index 000000000..2647ebfa0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/jarred-olson.yml
@@ -0,0 +1,2 @@
+name: "Jarred Olson"
+bio: "Jarred has been developing software professionally for over 10 years. He is passionate about automated testing, continuous delivery, removing inefficiencies, and developing DRY clean code in Groovy, Java, Javascript, Scala, or whatever the best tool for the job is. Currently employed at ForgeX in Columbus OH where he slings code while keeping a light and fun team environment. Outside of coding Jarred enjoys spending time with his wife and 2 kids, woodworking, golf, and watching college football."
diff --git a/exampleSite/data/speakers/2016/ohio/jason-yee.yml b/exampleSite/data/speakers/2016/ohio/jason-yee.yml
new file mode 100644
index 000000000..5a5180ba6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/jason-yee.yml
@@ -0,0 +1,2 @@
+name: "Jason Yee"
+bio: "Jason is a community builder, developer, traveller and chef. He currently works as a technical writer & evangelist at Datadog. When he's not working you can often find him on a plane trying to accumulate more miles or in a restaurant cooking."
diff --git a/exampleSite/data/speakers/2016/ohio/jody-wolfborn.yml b/exampleSite/data/speakers/2016/ohio/jody-wolfborn.yml
new file mode 100644
index 000000000..a7bc44a20
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/jody-wolfborn.yml
@@ -0,0 +1,2 @@
+name: "Jody Wolfborn"
+bio: "Jody is a theatre major-turned-technologist with a passion for languages of all kinds and a soft-spot for animals of the canine variety. Since entering the tech realm, she's had many years of experience living with and attempting to overcome Impostor Syndrome; through observation, research, and experimentation, she's collected resources to help combat this psychological self-sabotage."
diff --git a/exampleSite/data/speakers/2016/ohio/john-rzeszotarski.yml b/exampleSite/data/speakers/2016/ohio/john-rzeszotarski.yml
new file mode 100644
index 000000000..f8d2527f5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/john-rzeszotarski.yml
@@ -0,0 +1,2 @@
+name: "John Rzeszotarski"
+bio: "Changing the view on change!"
diff --git a/exampleSite/data/speakers/2016/ohio/ken-mugrage.yml b/exampleSite/data/speakers/2016/ohio/ken-mugrage.yml
new file mode 100644
index 000000000..d88af2a57
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/ken-mugrage.yml
@@ -0,0 +1,2 @@
+name: "Ken Mugrage"
+bio: "Ken Mugrage started his own web development company in 1994. Since then he’s held almost every position in a software development company, from developer to system administrator, sales engineer to development manager. This varied experience enables Ken to look at issues with a holistic view. Ken is currently a Technology Evangelist at ThoughtWorks, responsible for teaching others about DevOps and Continuous Delivery."
diff --git a/exampleSite/data/speakers/2016/ohio/leon-adato.yml b/exampleSite/data/speakers/2016/ohio/leon-adato.yml
new file mode 100644
index 000000000..36178f9eb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/leon-adato.yml
@@ -0,0 +1,2 @@
+name: "Leon Adato"
+bio: "Leon Adato is a Head Geek and technical evangelist at SolarWinds®, and is a Cisco® Certified Network Associate (CCNA), MCSE and SolarWinds Certified Professional. His experience spans financial, healthcare, food and beverage, and other industries. Before he was a SolarWinds Head Geek, Adato was a SolarWinds user for over a decade. His expertise in IT began in 1989 and has led him through roles in classroom training, desktop support, server support, and software distribution."
diff --git a/exampleSite/data/speakers/2016/ohio/leon-fayer.yml b/exampleSite/data/speakers/2016/ohio/leon-fayer.yml
new file mode 100644
index 000000000..d6bbe82f8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/leon-fayer.yml
@@ -0,0 +1,2 @@
+name: "Leon Fayer"
+bio: "Leon's two decades of expertise were concentrated on architecting and operating complex, web-based systems to withstand crushing traffic (often unexpectedly). Over the years, he's had a somewhat unique opportunity to design and build systems that run some of the most visited websites in the world. While his core expertise is in application development, he works his way around the whole technology stack from system architecture to databases design and optimization to front/back-end programming."
diff --git a/exampleSite/data/speakers/2016/ohio/matt-williams.yml b/exampleSite/data/speakers/2016/ohio/matt-williams.yml
new file mode 100644
index 000000000..34dfe91a0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/matt-williams.yml
@@ -0,0 +1,2 @@
+name: "Matt Williams"
+bio: "Matt Williams always wanted to be a Renaissance Person. Maybe one day he will be. In the mean time, he reads, cooks, weaves, hacks, and spends time with his daughter in Columbus, OH. You can find his technical musings at matthewkwilliams.com."
diff --git a/exampleSite/data/speakers/2016/ohio/nathen-harvey.yml b/exampleSite/data/speakers/2016/ohio/nathen-harvey.yml
new file mode 100644
index 000000000..008d4c4a1
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/nathen-harvey.yml
@@ -0,0 +1,2 @@
+name: "Nathen Harvey"
+bio: "Nathen Harvey, VP of Community Development at Chef, helps the community whip up an awesome ecosystem built around the Chef platform. Nathen also spends much of his time helping people learn about the practices, processes, and technologies that support DevOps, continuous delivery, and high velocity organizations. Nathen is a co-host of the Food Fight Show, a podcast about Chef and DevOps. He is also an occasional farmer who loves eggs and #hugops."
diff --git a/exampleSite/data/speakers/2016/ohio/paul-bauer.yml b/exampleSite/data/speakers/2016/ohio/paul-bauer.yml
new file mode 100644
index 000000000..c8c5531f4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/paul-bauer.yml
@@ -0,0 +1,2 @@
+name: "Paul Bauer"
+bio: "Platform Team engineer at Udacity, collects rare UUIDs"
diff --git a/exampleSite/data/speakers/2016/ohio/pete-gordon.yml b/exampleSite/data/speakers/2016/ohio/pete-gordon.yml
new file mode 100644
index 000000000..5f5835189
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/pete-gordon.yml
@@ -0,0 +1,2 @@
+name: "Pete Gordon"
+bio: "Columbus Software Guy and Buckeye, who never has and never will live anywhere but Columbus. Working the beautiful intersection of Statistics (ML, AI, R, Data Science) and Software (JavaScript, NodeJS, HTML/CSS, SVG, WebGL) at the Columbus Collaboratory. The Internet changes everything!"
diff --git a/exampleSite/data/speakers/2016/ohio/peter-walsh.yml b/exampleSite/data/speakers/2016/ohio/peter-walsh.yml
new file mode 100644
index 000000000..a7d2100c5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/ohio/peter-walsh.yml
@@ -0,0 +1,2 @@
+name: "Peter Walsh"
+bio: "Peter Walsh is a Director with Jackpine Technologies, a developer of software excellence solutions, including the CONS3RT cloud orchestrator. A graduate of Boston University, Peter has over 20 years of experience in the private & public sector in product design & development, from embedded systems through enterprise software. Peter is a speaker and trainer in Agile Development and DevOps; he has presented at DevOps Days, Red Hat Summit, DISA Mission Partner Conference, and others."
diff --git a/exampleSite/data/speakers/2016/oslo/anders-sveen.yml b/exampleSite/data/speakers/2016/oslo/anders-sveen.yml
new file mode 100644
index 000000000..a2cb1399e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/anders-sveen.yml
@@ -0,0 +1,3 @@
+name: "Anders Sveen"
+twitter: "anderssv"
+bio: "Anders has been working as an developer, architect, team-lead and automation nut for the last 12 years. He's a big proponent off most things agile and think it's time IT started enabling organisations to change. Not limiting the organisation.
Anders is a tech guy and programmer first. The last 4-years he has been trying to automate anything that is needed to deploy applications reliably. Learning (a little too much) Bash and Python along the way.
[LinkedIn](http://linkedin.com/in/anderssv)"
diff --git a/exampleSite/data/speakers/2016/oslo/anton-babenko.yml b/exampleSite/data/speakers/2016/oslo/anton-babenko.yml
new file mode 100644
index 000000000..5e15639df
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/anton-babenko.yml
@@ -0,0 +1,3 @@
+name: "Anton Babenko"
+twitter: "antonbabenko"
+bio: "Anton is DevOps engineer at Your.MD, start-up developing personal medical assistant applications and chat-bots. He is fully certified in all 5 AWS certifications and has been working as web-developer, team lead and CTO during last 10 years. He has been constantly involved in automation (from testing to marketing) and exploring ways to do it properly and as risk-free as possible. He has strong interest and experience in DevOps toolset and AWS.
[LinkedIn](http://linkedin.com/in/antonbabenko)"
diff --git a/exampleSite/data/speakers/2016/oslo/daniela-soares-cruzes.yml b/exampleSite/data/speakers/2016/oslo/daniela-soares-cruzes.yml
new file mode 100644
index 000000000..a95832bc5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/daniela-soares-cruzes.yml
@@ -0,0 +1,2 @@
+name: "Daniela Soares Cruzes"
+bio: "Dr. Daniela S. Cruzes is a researcher scientist at SINTEF. Previously, she was adjunct associate professor at the Norwegian University of Science and Technology (NTNU). She worked as a researcher fellow at the University of Maryland and Fraunhofer Center for Experimental Software Engineering-Maryland. Dr. Daniela Cruzes is the project manager of the SoS-Agile (Science of Security for Agile software Development) project funded by the Research Council of Norway. Her interests are agile software development, software security, global software engineering, empirical research methods, theory development and synthesis of software engineering studies."
diff --git a/exampleSite/data/speakers/2016/oslo/hans-kristian-flaatten.yml b/exampleSite/data/speakers/2016/oslo/hans-kristian-flaatten.yml
new file mode 100644
index 000000000..22fe25c7e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/hans-kristian-flaatten.yml
@@ -0,0 +1,2 @@
+name: "Hans Kristian Flaatten"
+bio: "Hans Kristian Flaatten is an Open Source and Open Data evangelist. He is an acting member of the Node.js Foundation where he manage the test and release infrastructure for official Node.js versions, as well as the official Docker Image for Node.js.
He is a Senior Systems Developer / DevOps at the Norwegian Trekking Association (Norway's biggest outdoor activities organisation) where he have lead the transition to a microservice oriented architecture on immutable infrastructure and Docker Containers. He have also spear headed DNT's initiative on Open Data through UT.no and Nasjonal Turbase."
diff --git a/exampleSite/data/speakers/2016/oslo/jason-diller.yml b/exampleSite/data/speakers/2016/oslo/jason-diller.yml
new file mode 100644
index 000000000..4f7fda6ae
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/jason-diller.yml
@@ -0,0 +1,3 @@
+name: "Jason Diller"
+twitter: "jdiller"
+bio: "Jason has been working professionally in technology since the 90s. He has written code for numerous platforms from DOS to Windows to Linux to the Web. In recent years he's devoted his time to management and has a serious obsession with making his teams, people, and processes better. (A quest that will never be completed.) Currently he does so at PagerDuty.
[LinkedIn](http://linkedin.com/in/jasonadiller)"
diff --git a/exampleSite/data/speakers/2016/oslo/jody-wolfborn.yml b/exampleSite/data/speakers/2016/oslo/jody-wolfborn.yml
new file mode 100644
index 000000000..0be2e7794
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/jody-wolfborn.yml
@@ -0,0 +1,3 @@
+name: "Jody Wolfborn"
+twitter: "joderita"
+bio: "Jody is a theatre major-turned-technologist with a passion for languages of all kinds and a soft-spot for animals of the canine variety. Since entering the tech realm, she’s had many years of experience living with and attempting to overcome Impostor Syndrome; through observation, research, and experimentation, she’s collected resources to help combat this psychological self-sabotage."
diff --git a/exampleSite/data/speakers/2016/oslo/jon-arild-torresdal.yml b/exampleSite/data/speakers/2016/oslo/jon-arild-torresdal.yml
new file mode 100644
index 000000000..93154feb2
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/jon-arild-torresdal.yml
@@ -0,0 +1,3 @@
+name: "Jon Arild Tørresdal"
+twitter: "torresdal"
+bio: "Jon Arild Tørresdal is a speaker, advisor and consultant working for Miles in Bergen, Norway. In the last decade he has worked with development and operations using Lean practices for a number of companies to fully automate their deployment and infrastructure processes. As a result of his work he created the open source project ConDep (condep.io) in 2011 to specifically enable and simplify infrastructure automation and continuous delivery on the Windows platform.
[LinkedIn](http://linkedin.com/in/jonarild)"
\ No newline at end of file
diff --git a/exampleSite/data/speakers/2016/oslo/kjetil-jorgensen-dahl.yml b/exampleSite/data/speakers/2016/oslo/kjetil-jorgensen-dahl.yml
new file mode 100644
index 000000000..0d40fef59
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/kjetil-jorgensen-dahl.yml
@@ -0,0 +1,3 @@
+name: "Kjetil Jørgensen-Dahl"
+twitter: "akafred"
+bio: "Kjetil Jørgensen-Dahl is a developer and consultant at [Kodemaker](http://kodemaker.no/kjetil). From time to time he dabbles in process and ops-related activities, usually because he is not to keen on rework and repetition (communication + automation FTW!).
If you ask for his two cents, you usually get a dollars worth ...
[LinkedIn](http://linkedin.com/in/kjetiljd)."
diff --git a/exampleSite/data/speakers/2016/oslo/kris-buytaert.yml b/exampleSite/data/speakers/2016/oslo/kris-buytaert.yml
new file mode 100644
index 000000000..93e31e1c6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/kris-buytaert.yml
@@ -0,0 +1,6 @@
+name: "Kris Buytaert"
+twitter: ""
+bio: "Kris Buytaert is a long time Linux and Open Source Consultant. He's one of instigators of the devops movement, currently working for Inuits.
+He is frequently speaking at, or organizing different international conferences and has written about the same subjects in different Books, Papers and Articles.
+He spends most of his time working on bridging the gap between developers and operations with a strong focus on High Availability, Scalability, Virtualisation and Large Infrastructure Management projects hence trying to build infrastructures that can survive the 10th floor test, better known today as the cloud while actively promoting the devops idea !
+His blog titled \"Everything is a Freaking DNS Problem\" can be found at [http://www.krisbuytaert.be/blog/](http://www.krisbuytaert.be/blog/)"
diff --git a/exampleSite/data/speakers/2016/oslo/magnus-reftel.yml b/exampleSite/data/speakers/2016/oslo/magnus-reftel.yml
new file mode 100644
index 000000000..cd2b1ce64
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/magnus-reftel.yml
@@ -0,0 +1,3 @@
+name: "Magnus Reftel"
+twitter: "magnus_reftel"
+bio: "Currently at the Norwegian Tax Office in a DevOpsy role, previously at Spotify and ST-Ericsson. Coder since the '90s. Habitual automator. Cucumber fan.
[LinkedIn](https://no.linkedin.com/in/magnusreftel)"
diff --git a/exampleSite/data/speakers/2016/oslo/mandi-walls.yml b/exampleSite/data/speakers/2016/oslo/mandi-walls.yml
new file mode 100644
index 000000000..667efa88d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/mandi-walls.yml
@@ -0,0 +1,3 @@
+name: "Mandi Walls"
+twitter: "lnxchk"
+bio: "Mandi Walls is the Technical Community Manager for Chef in EMEA, based in London. Mandi has been with Chef for several years, working with customers worldwide on their automation and DevOps journeys.
[LinkedIn](https://uk.linkedin.com/in/mandiwalls)"
diff --git a/exampleSite/data/speakers/2016/oslo/mari-grini.yml b/exampleSite/data/speakers/2016/oslo/mari-grini.yml
new file mode 100644
index 000000000..7bb1f2976
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/mari-grini.yml
@@ -0,0 +1,3 @@
+name: "Mari Grini"
+twitter: "MariGrini"
+bio: "Mari is currently managing security in Telenor Digital, a development house within Telenor. She has worked many years in IT security and has among other the experience from managing IT security in a major Norwegian bank. She has education from NTNU and have a Master of Management at BI.
[LinkedIn](https://no.linkedin.com/in/marigrini)"
diff --git a/exampleSite/data/speakers/2016/oslo/mark-burgess.yml b/exampleSite/data/speakers/2016/oslo/mark-burgess.yml
new file mode 100644
index 000000000..a003280de
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/mark-burgess.yml
@@ -0,0 +1,3 @@
+name: "Mark Burgess"
+twitter: ""
+bio: "Mark Burgess is a theoretician and practitioner in the area of information systems, whose work has focused largely on distributed information infrastructure. He is known particularly for his work on Configuration Management and Promise Theory. He was the principal Founder of CFEngine, and is emeritus professor of Network and System Administration from Oslo University College. He is the author of numerous books, articles, and papers on topics from physics, Network and System Administration, to fiction. He also writes a blog on issues of science and IT industry concerns."
diff --git a/exampleSite/data/speakers/2016/oslo/marta-paciorkowska.yml b/exampleSite/data/speakers/2016/oslo/marta-paciorkowska.yml
new file mode 100644
index 000000000..450a0bad6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/marta-paciorkowska.yml
@@ -0,0 +1,3 @@
+name: "Marta Paciorkowska"
+twitter: "a_meba"
+bio: "An activist/project manager turned programming enthusiast. Marta currently hold the position of DevOps Heroine at Acrolinx, where she is responsible for developer support, redesigning build infrastructure and introducing DevOps ideas. She actively support initiatives that make the tech community more inclusive. A very occasional Rails Girls coach. She ♥ Chef, alleycats and pizza.
[LinkedIn](http://linkedin.com/in/paciorkowska)"
diff --git a/exampleSite/data/speakers/2016/oslo/martin-b-smith.yml b/exampleSite/data/speakers/2016/oslo/martin-b-smith.yml
new file mode 100644
index 000000000..404d34519
--- /dev/null
+++ b/exampleSite/data/speakers/2016/oslo/martin-b-smith.yml
@@ -0,0 +1,3 @@
+name: "Martin B. Smith"
+twitter: "martinb3"
+bio: "It's one thing to say you want to make the world a better place, but as an engineer I feel I have an opportunity to put those words into action. With over 15 years of experience in infrastructure automation, software development, and systems administration for large scale public cloud providers and top public universities, my mission is to solve for real-world business problems with technical solutions that scale.
For me, it's important to share the lessons I've learned with local technical communities, particularly by mentoring minority college students in STEM fields. I strongly believe in open source and actively contribute to automation projects like Chef. When I’m not writing a technical talk or reviewing pull requests, I enjoy traveling the world, sharing my skills with other like-minded professionals who want to make the world more awesome."
diff --git a/exampleSite/data/speakers/2016/philadelphia/andrey-utis.yml b/exampleSite/data/speakers/2016/philadelphia/andrey-utis.yml
new file mode 100644
index 000000000..cdb2664ba
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/andrey-utis.yml
@@ -0,0 +1,3 @@
+name: "Andrey Utis"
+twitter: ""
+bio: "Andrey has a Masters in Computer Science from University of Maryland, College Park, where he primarily studied algorithms and computational complexity. In the industry, he spent several years consulting, working on a wide range of projects: implementing distributed systems, performance tuning Java applications, and optimizing large databases. Andrey has been working for CapitalOne for the last few years, initially leading customer security and fraud development teams. Currently, he is leading the Account Opening project, as well as related CI/CD and DevOps efforts."
diff --git a/exampleSite/data/speakers/2016/philadelphia/berenice-venegas-cotero.yml b/exampleSite/data/speakers/2016/philadelphia/berenice-venegas-cotero.yml
new file mode 100644
index 000000000..ce93f68ff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/berenice-venegas-cotero.yml
@@ -0,0 +1,3 @@
+name: "Berenice Venegas Cotero"
+twitter: ""
+bio: "A physicist that once fell to the stars of Astrophysics.\n\nHowever, being experimentalist and theoretician at heart, her love eventually fell for molecular Biophysics,\nresearching the cooperative but elusive behavior of lipids\ndesigned nanoliposomes for targeted drug delivery.\n\nHer first close encounter with a computer\nwas a PRIME 750, exclusively used\nto scare mother, who run batch jobs\nfilling her terminal screen with infinite error messages and warnings.\n\nAs a good physicist,\nonly UNIX style computing was acceptable.\nUnfortunately learned some Windows\nwell into the new millennium\nwhich then regretted quite a bit.\n\n\nResearch brought dynamic and Monte Carlo simulations,\nexperimental data required analysis automation\nso cloud computing offered attractive adventures\nBig data IoT pipelines dockerization Oh My!\n\nDevOps has become her fascinating playground.\nFeeling infinite compute power at the fingertips,\nshe automates infrastructure up from the ground\nnever having a particular server relationship\n\nBesides obvious interest of maxing out cloud resources\nshe likes unplanned travels and being outdoors\ngymnastics, including mind ones\nand collecting fine peppers for cooking.\n\nIn free time she likes rescuing any pet\nespecially ones being a 'poor thing'."
diff --git a/exampleSite/data/speakers/2016/philadelphia/bridget-kromhout.yml b/exampleSite/data/speakers/2016/philadelphia/bridget-kromhout.yml
new file mode 100644
index 000000000..de1378824
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/bridget-kromhout.yml
@@ -0,0 +1,3 @@
+name: "Bridget Kromhout"
+twitter: "bridgetkromhout"
+bio: "Bridget Kromhout is a Principal Technologist for Cloud Foundry at Pivotal. Her CS degree emphasis was in theory, but she now deals with the concrete (if ‘cloud’ can be considered tangible). After years as an operations engineer (most recently at DramaFever), she traded in oncall for more travel. A frequent speaker at tech conferences, she helps organize tech meetups at home in Minneapolis, serves on the program committee for Velocity, and acts as a global core organizer for devopsdays. She podcasts at Arrested DevOps, occasionally blogs at bridgetkromhout.com, and is active in a Twitterverse near you."
diff --git a/exampleSite/data/speakers/2016/philadelphia/catherine-enck.yml b/exampleSite/data/speakers/2016/philadelphia/catherine-enck.yml
new file mode 100644
index 000000000..761428b7e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/catherine-enck.yml
@@ -0,0 +1,3 @@
+name: "Catherine Enck"
+twitter: "mrsmodernamazon"
+bio: "Catherine Enck is Director of Operations for Hire an Esquire, an agile company disrupting the legal staffing scene by leveraging technology. Catherine has hands-on experience in all aspects of operations in multiple industries including tech, finance, and legal. The birth of her daughter a year ago has her more motivated than ever to advocate for powerful women in the workplace and better working options for mothers. When she's not actively preventing her toddler from accidental self-harm, she's spending the other 20% of her free-time blogging about strong women, exploring South Philly, and enjoying irreverent humor."
diff --git a/exampleSite/data/speakers/2016/philadelphia/dave-long.yml b/exampleSite/data/speakers/2016/philadelphia/dave-long.yml
new file mode 100644
index 000000000..c9a8701c8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/dave-long.yml
@@ -0,0 +1,3 @@
+name: "Dave Long"
+twitter: "davejlong"
+bio: "Dave Long is the Director of Development at Cage Data, a tech consultancy servicing the New England region. He's been writing applications in Ruby, JavaScript and Elixir for the past 8 years. Working in smaller consultancies, Dave has, often times, had to manage his own application infrastructure. In this, Dave has brought ideas and concepts from programming into his systems administration, such as managing infrastructure code like any application with tests and code analysis."
diff --git a/exampleSite/data/speakers/2016/philadelphia/eric-sigler.yml b/exampleSite/data/speakers/2016/philadelphia/eric-sigler.yml
new file mode 100644
index 000000000..a3118a370
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/eric-sigler.yml
@@ -0,0 +1,3 @@
+name: "Eric Sigler"
+twitter: ""
+bio: "Eric Sigler is the Head of DevOps for PagerDuty, evangelizing culture, automation, measurement, and sharing. Prior to his current role, he lead the Developer Tools team, implementing Continuous Deployment across the company’s infrastructure. During his 16 year career in infrastructure engineering, he’s been the Technical Operations Manager at Minted, improving holiday cheer through high availability, and Manager of Computing Systems at Missouri S&T, saving the world one student at a time."
diff --git a/exampleSite/data/speakers/2016/philadelphia/jon-mosco.yml b/exampleSite/data/speakers/2016/philadelphia/jon-mosco.yml
new file mode 100644
index 000000000..7211d5b90
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/jon-mosco.yml
@@ -0,0 +1,3 @@
+name: "Jon Mosco"
+twitter: "jpmosco"
+bio: "Systems Engineer, Release Engineer, Unix fanatic, Converter of tabs to spaces"
diff --git a/exampleSite/data/speakers/2016/philadelphia/kaitlin-picco.yml b/exampleSite/data/speakers/2016/philadelphia/kaitlin-picco.yml
new file mode 100644
index 000000000..8ef1a2c0f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/kaitlin-picco.yml
@@ -0,0 +1,3 @@
+name: "Kaitlin Picco"
+twitter: "PhillyKait"
+bio: "Kait Picco is General Counsel and Director of Human Resources for Tonic Design Co., a Philly-based digital design and development agency focused on emerging technologies. Prior to joining Tonic, Kait worked as an attorney in several large law firms and helped her clients navigate the world of transactional employment law and litigation. Kait's other notable achievements include never laying down her motorcycle; barely beating a 10-year old in the Broad Street Run; hatching a Lapras; and winning a Best Mom Ever coffee mug six years running."
diff --git a/exampleSite/data/speakers/2016/philadelphia/ken-mugrage.yml b/exampleSite/data/speakers/2016/philadelphia/ken-mugrage.yml
new file mode 100644
index 000000000..4991a6439
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/ken-mugrage.yml
@@ -0,0 +1,3 @@
+name: "Ken Mugrage"
+twitter: "kmugrage"
+bio: "Ken Mugrage has 25 years of experience in the IT industry, spending the last 7 at ThoughtWorks. During his entire career, Ken has focused on using technology to increase business effectiveness, as opposed to using the ‘latest cool thing’. Ken has been focused on Continuous Delivery and DevOps for most of the past decade, working with organizations all over the world, ranging from startups to Fortune 50 companies. He now uses this experience to teach others how to get better at building, testing and deploying software."
diff --git a/exampleSite/data/speakers/2016/philadelphia/leon-fayer.yml b/exampleSite/data/speakers/2016/philadelphia/leon-fayer.yml
new file mode 100644
index 000000000..2e6cb498f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/leon-fayer.yml
@@ -0,0 +1,3 @@
+name: "Leon Fayer"
+twitter: "papa_fire"
+bio: "Leon's two decades of expertise were concentrated on architecting and operating complex, web-based systems to withstand crushing traffic (often unexpectedly). Over the years, he's had a somewhat unique opportunity to design and build systems that run some of the most visited websites in the world. While his core expertise is in application development, he works his way around the whole technology stack from system architecture to databases design and optimization to front/back-end programming. He's considered a professional naysayer by peers and has the opinion that nothing really works until it works for at least a million people."
diff --git a/exampleSite/data/speakers/2016/philadelphia/mauricio-linhares.yml b/exampleSite/data/speakers/2016/philadelphia/mauricio-linhares.yml
new file mode 100644
index 000000000..87166f102
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/mauricio-linhares.yml
@@ -0,0 +1,3 @@
+name: "Maurício Linhares"
+twitter: "mauriciojr"
+bio: "Maurício Linhares is a technical lead at DigitalOcean working at the Edge team making sure all traffic routed into DO's API and cloud servers reach it's destination. He's been working on cloud environments and infrastructure automation on AWS and private clouds, making sure systems are doing their job. Passionate about functional programming, stateless infrastructure and DevOps to produce distributed systems that are scalable and maintainable in the long run."
diff --git a/exampleSite/data/speakers/2016/philadelphia/oguz-pastirmaci.yml b/exampleSite/data/speakers/2016/philadelphia/oguz-pastirmaci.yml
new file mode 100644
index 000000000..0ee60571a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/oguz-pastirmaci.yml
@@ -0,0 +1,3 @@
+name: "Oguz Pastirmaci"
+twitter: "OguzPastirmaci"
+bio: "Oguz worked as a system administrator for 6 years before joining Microsoft as an Infrastructure Technical Evangelist in 2012, focusing on virtualization and private cloud. Starting with 2015, his focus is now DevOps and Open Source."
diff --git a/exampleSite/data/speakers/2016/philadelphia/rick-pufky.yml b/exampleSite/data/speakers/2016/philadelphia/rick-pufky.yml
new file mode 100644
index 000000000..6ed9333c0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/rick-pufky.yml
@@ -0,0 +1,3 @@
+name: "Rick Pufky"
+twitter: ""
+bio: "Rick Pufky is a member of the DevOps Practice at OmniTI, diving into customer teams to help with difficult problems. He is well versed in several automation systems, helping customers to become familiar with them and use them in day-to-day activities."
diff --git a/exampleSite/data/speakers/2016/philadelphia/ross-kukulinski.yml b/exampleSite/data/speakers/2016/philadelphia/ross-kukulinski.yml
new file mode 100644
index 000000000..4dd3e0dcb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/ross-kukulinski.yml
@@ -0,0 +1,3 @@
+name: "Ross Kukulinski"
+twitter: "rosskukulinski"
+bio: "Ross Kukulinski works at NodeSource as a Technical Product Manager and is a member of the NodeJS Evangelism Working Group. His technical expertise is in architecting, developing, and deploying scalable, containerized, real-time cloud applications. When he’s not fostering enterprise adoption of NodeJS, Ross can be found running Node in production using container tools including Docker, CoreOS and Kubernetes.\n\nRoss is a frequent speaker at technology conferences and events including QCon, CoreOS Fest, ContainerCamp, NodeSummit, KrankyGeek WebRTC, and Philly Tech Week. Ross has also published an O’Reilly Video Tutorial Series called Introduction to CoreOS: Learn to Deploy, Monitor, and Scale Containerized Applications"
diff --git a/exampleSite/data/speakers/2016/philadelphia/shilpa-jindal.yml b/exampleSite/data/speakers/2016/philadelphia/shilpa-jindal.yml
new file mode 100644
index 000000000..b2dd90308
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/shilpa-jindal.yml
@@ -0,0 +1,3 @@
+name: "Shilpa Jindal"
+twitter: ""
+bio: "I am Technology Lead in Capital One, currently leading Billpay feature in Retail Bank."
diff --git a/exampleSite/data/speakers/2016/philadelphia/tim-gross.yml b/exampleSite/data/speakers/2016/philadelphia/tim-gross.yml
new file mode 100644
index 000000000..6fcb1d8de
--- /dev/null
+++ b/exampleSite/data/speakers/2016/philadelphia/tim-gross.yml
@@ -0,0 +1,3 @@
+name: "Tim Gross"
+twitter: "0x74696d"
+bio: "Tim Gross is a product manager for Joyent, providers of the Triton Elastic Container Service. Tim previously ran Ops at DramaFever, where he and his scrappy team ran Docker in production to serve a few million fans their daily dose of dramas, documentaries, and gross-out horror movies.\n\nIn a previous life, Tim was an architect (buildings, not software). He took the leap into programming and Operations after he discovered he could automate away almost everything boring in his life."
diff --git a/exampleSite/data/speakers/2016/portland/aaron-jensen.yml b/exampleSite/data/speakers/2016/portland/aaron-jensen.yml
new file mode 100644
index 000000000..845973cf9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/aaron-jensen.yml
@@ -0,0 +1,3 @@
+name: "Aaron Jensen"
+twitter: "pshdo"
+bio: "Aaron Jensen is a Software Architect for WebMD Health Services, where he automates software builds, deployments, configuration, and installation. He is the creator and maintainer of Carbon, an open-source PowerShell module for automating the installation and configuration of Windows computers, applications, websites, and services. It has been downloaded over 12,000 times and is the 13th most popular non-Microsoft module on the PowerShell Gallery."
diff --git a/exampleSite/data/speakers/2016/portland/adrien-thebo.yml b/exampleSite/data/speakers/2016/portland/adrien-thebo.yml
new file mode 100644
index 000000000..bb5178d28
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/adrien-thebo.yml
@@ -0,0 +1,3 @@
+name: "Adrien Thebo"
+twitter: "nullfinch"
+bio: "Adrien is a software engineer at Puppet. He started in IT Ops in 2005 and started writing code to automate everything, inadvertently becoming one of the earliest devops hipsters (he did devops before it was cool). Adrien joined Puppet in 2011, first on the Operations team where he helped cause frequent outages, and then transferred to the Engineering team in 2013 to where he helped break the build. The original author of r10k and other client tools for Puppet, these days Adrien works on the security development team yelling at openssl documentation and refining ways to protect systems and infrastructure."
diff --git a/exampleSite/data/speakers/2016/portland/ben-burry.yml b/exampleSite/data/speakers/2016/portland/ben-burry.yml
new file mode 100644
index 000000000..1adf848b0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/ben-burry.yml
@@ -0,0 +1,3 @@
+name: "Ben Burry"
+twitter: ""
+bio: "Ben Burry is a senior infrastructure engineer at Etsy, working both remotely (and not remotely!) on the Devtools team."
diff --git a/exampleSite/data/speakers/2016/portland/ben-hughes.yml b/exampleSite/data/speakers/2016/portland/ben-hughes.yml
new file mode 100644
index 000000000..ba0b35307
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/ben-hughes.yml
@@ -0,0 +1,3 @@
+name: "Ben Hughes"
+twitter: "benjammingh"
+bio: "Ben is a security engineer at Etsy where he protects the yarn from evil doers. He's previously been an operations engineer (or sysadmin to those who've been in the industry more than 10 years) at Puppet Labs working on automation software, a network engineer so knows how to battle through Cisco's product catalogue. He learnt about systems security by the generosity of other people's insecure systems in the 90s."
diff --git a/exampleSite/data/speakers/2016/portland/caskey-dickson.yml b/exampleSite/data/speakers/2016/portland/caskey-dickson.yml
new file mode 100644
index 000000000..8a271e9d0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/caskey-dickson.yml
@@ -0,0 +1,3 @@
+name: "Caskey Dickson"
+twitter: "caskey"
+bio: "Caskey L. Dickson is a Site Reliability Engineer at Microsoft where he is part of the leadership team reinventing operations at Azure. Before that he was at Google where he worked as an SRE/SWE writing and maintaining monitoring services that operate at \"Google scale\" as well as a few business intelligence pipelines and maybe a script or two. He has worked in online services since 1995 when he turned up his first web server and has been online ever since. Before working at Google, he was a senior developer at Symantec, wrote software for various Internet startups such as CitySearch and CarsDirect, ran a consulting company, and even taught undergraduate and graduate computer science at Loyola Marymount University. He has a B.S. in Computer Science, a Masters in Systems Engineering, and an M.B.A from Loyola Marymount."
diff --git a/exampleSite/data/speakers/2016/portland/chris-barker.yml b/exampleSite/data/speakers/2016/portland/chris-barker.yml
new file mode 100644
index 000000000..35fcfb509
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/chris-barker.yml
@@ -0,0 +1,3 @@
+name: "Chris Barker"
+twitter: "mrzarquon"
+bio: "Turning in his pager for an airline miles membership, Chris Barker now helps fellow system administrators refine and automate their infrastructure. In his past life as a systems administrator, he has administered Linux, Windows, and OS X systems in infrastructure ranging from small businesses to Fortune 500 companies. He was drawn to Puppet due to his automation-driven creativity. When not traveling for Puppet, he resides in Portland, OR automating parts of his house and deconstructing cocktails."
diff --git a/exampleSite/data/speakers/2016/portland/dan-young.yml b/exampleSite/data/speakers/2016/portland/dan-young.yml
new file mode 100644
index 000000000..790cd34da
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/dan-young.yml
@@ -0,0 +1,3 @@
+name: "Dan Young"
+twitter: "idleyoungman"
+bio: "Dan Young is a Senior Operations Engineer in the Site Engineering group at New Relic, Inc working on build infrastructure, Docker, and the hundred other things all ops folks do.\n\n He is a carbon-based biped who enjoys making things work, sharing the knowledge with others, and sweaters."
diff --git a/exampleSite/data/speakers/2016/portland/david-blank-edelman.yml b/exampleSite/data/speakers/2016/portland/david-blank-edelman.yml
new file mode 100644
index 000000000..e8f725738
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/david-blank-edelman.yml
@@ -0,0 +1,3 @@
+name: "David Blank Edelman"
+twitter: "otterbook"
+bio: "David is the Technical Evangelist at Apcera. He has spent close to thirty years in the systems administration/DevOps/SRE field in large multiplatform environments including Brandeis University, Cambridge Technology Group, MIT Media Laboratory and Northeastern University. He is the author of the O'Reilly Otter book (Automating System Administration with Perl) and is a frequent invited speaker at conferences in the field. David is honored to serve on the USENIX Board of Directors. He prefers to pronounce Evangelist with a hard 'g'."
diff --git a/exampleSite/data/speakers/2016/portland/e-dunham.yml b/exampleSite/data/speakers/2016/portland/e-dunham.yml
new file mode 100644
index 000000000..2e6c7beef
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/e-dunham.yml
@@ -0,0 +1,3 @@
+name: "E Dunham"
+twitter: "qedunham"
+bio: "E. Dunham is the DevOps engineer for Mozilla research, which in practice means shepherding servers for the Rust language and Servo browser engine web presence, continuous integration, and release infrastructure. The OSL alum's hobbies include carpentry, gardening, and filing \"please license your code\" issues on GitHub."
diff --git a/exampleSite/data/speakers/2016/portland/eric-passmore.yml b/exampleSite/data/speakers/2016/portland/eric-passmore.yml
new file mode 100644
index 000000000..a3da6f38d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/eric-passmore.yml
@@ -0,0 +1,3 @@
+name: "Eric Passmore"
+twitter: "ericpassmore"
+bio: "Eric Passmore is an online media and technology executive working at Microsoft. He has previously held executive roles at AOL and CBS Interactive. During his 20-year career he has served as head of platforms and infrastructure, content management, application development, and online media. Eric has developed real-time systems to power online social activities and demand-based systems to create customized and relevant experiences. He is a co-inventor of a patented system that creates personalized experiences from large volumes of online content. Eric is passionate about creating resilient services. He is a frequent speaker on topics of large-scale cloud services and improved operational practices."
diff --git a/exampleSite/data/speakers/2016/portland/jennifer-davis.yml b/exampleSite/data/speakers/2016/portland/jennifer-davis.yml
new file mode 100644
index 000000000..78ec9289c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/jennifer-davis.yml
@@ -0,0 +1,3 @@
+name: "Jennifer Davis"
+twitter: "sigje"
+bio: "Jennifer is the co-author of Effective DevOps. She is a co-organizer of devopsdays Silicon Valley, and the founder of Coffeeops. In her role at Chef, Jennifer develops software to simplify building and managing infrastructure. She has spoken at a number of industry conferences about devops, tech culture, monitoring, and automation. When she’s not working, she enjoys hiking Bay Area trails, learning to make things and quality time with her dog, George."
diff --git a/exampleSite/data/speakers/2016/portland/jj-asghar.yml b/exampleSite/data/speakers/2016/portland/jj-asghar.yml
new file mode 100644
index 000000000..95da896dd
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/jj-asghar.yml
@@ -0,0 +1,3 @@
+name: "Jj Asghar"
+twitter: "jjasghar"
+bio: "JJ is a Sr. Partner Engineer at Chef, he was also the PTL for the Openstack-Chef project. He lives in Austin, Texas and has been part of the OpenStack community since Diablo's release.\n\n He enjoys a good strong stout, hoppy IPA, and some Dwarf Fortress. He's a member of the Church of Emacs, and usually chooses Ubuntu over CentOS.\n\n He's a father and husband, if he's not trying to automate his job away he's trying to convince his daughters to \"let the bot's do the work for them.\""
diff --git a/exampleSite/data/speakers/2016/portland/josh-berkus.yml b/exampleSite/data/speakers/2016/portland/josh-berkus.yml
new file mode 100644
index 000000000..cc4329df1
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/josh-berkus.yml
@@ -0,0 +1,3 @@
+name: "Josh Berkus"
+twitter: "fuzzychef"
+bio: "Josh Berkus is Community Lead for Project Atomic, but is better known for his 18 years of contributions to PostgreSQL. Josh works with Docker, Kubernetes, Atomic, and Etcd. He lives in Portland, where he does Linux containers, gardening and pottery."
diff --git a/exampleSite/data/speakers/2016/portland/julia-wester.yml b/exampleSite/data/speakers/2016/portland/julia-wester.yml
new file mode 100644
index 000000000..10e983863
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/julia-wester.yml
@@ -0,0 +1,3 @@
+name: "Julia Wester"
+twitter: "everydaykanban"
+bio: "Julia brings 15 years of experience working in and managing teams at Turner Broadcasting and F5 Networks. Julia is passionate about teaching others how to tame the chaos of the everyday at work by embracing transparency and continuous improvement and talking about how management doesn’t have to be a dirty word. Julia joined LeanKit as an Improvement Coach in 2015. She blogs at everydaykanban.com and tweets at @everydaykanban."
diff --git a/exampleSite/data/speakers/2016/portland/kelsey-hightower.yml b/exampleSite/data/speakers/2016/portland/kelsey-hightower.yml
new file mode 100644
index 000000000..f7f304ac0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/kelsey-hightower.yml
@@ -0,0 +1,3 @@
+name: "Kelsey Hightower"
+twitter: "kelseyhightower"
+bio: "Kelsey Hightower has worn every hat possible throughout his career in tech, and enjoys leadership roles focused on making things happen and shipping software. Kelsey is a strong open source advocate focused on building simple tools that make people smile. When he is not slinging Go code, you can catch him giving technical workshops covering everything from programming to system administration, and his favorite Linux distro (CoreOS)."
diff --git a/exampleSite/data/speakers/2016/portland/ken-mugrage.yml b/exampleSite/data/speakers/2016/portland/ken-mugrage.yml
new file mode 100644
index 000000000..262e6eebc
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/ken-mugrage.yml
@@ -0,0 +1,3 @@
+name: "Ken Mugrage"
+twitter: "kmugrage"
+bio: "Ken Mugrage started his own web development company in 1994. Since then he’s held almost every position in a software development company, from developer to system administrator, sales engineer to development manager. This varied experience enables Ken to look at issues with a holistic view.\n\n Ken is currently a Technology Evangelist at ThoughtWorks, responsible for teaching others about DevOps and Continuous Delivery."
diff --git a/exampleSite/data/speakers/2016/portland/matthew-barker.yml b/exampleSite/data/speakers/2016/portland/matthew-barker.yml
new file mode 100644
index 000000000..4f4da90bb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/matthew-barker.yml
@@ -0,0 +1,3 @@
+name: "Matthew Barker"
+twitter: "matthewabq"
+bio: "As a experienced Solutions Architect, I assist companies in automating quality into their devops tool chain. My broad-based experience in open source software and rapid application development combined with my background in software security enables me to provide insightful, technical guidance to companies desiring to produce secure applications of high quality and with minimal risk."
diff --git a/exampleSite/data/speakers/2016/portland/nell-shamrell-harrington.yml b/exampleSite/data/speakers/2016/portland/nell-shamrell-harrington.yml
new file mode 100644
index 000000000..8ac574f82
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/nell-shamrell-harrington.yml
@@ -0,0 +1,3 @@
+name: "Nell Shamrell Harrington"
+twitter: "nellshamrell"
+bio: "Nell Shamrell-Harrington is a Software Development Engineer at Chef, focusing on the Supermarket open source product. She also sits on the advisory board for the University of Washington Certificates in Ruby Programming and DevOps. She specializes in Chef, Ruby, Rails, Regular Expressions, and Test Driven Development and has traveled the world speaking on these topics. Prior to entering the world of software development, she studied and worked in the field of theatre. The world of theatre prepared her well for the dynamic world of creating software applications. In both, she strives to create a cohesive and extraordinary experience. In her free time she enjoys practicing the martial art Naginata."
diff --git a/exampleSite/data/speakers/2016/portland/terrence-ryan.yml b/exampleSite/data/speakers/2016/portland/terrence-ryan.yml
new file mode 100644
index 000000000..8befdaa44
--- /dev/null
+++ b/exampleSite/data/speakers/2016/portland/terrence-ryan.yml
@@ -0,0 +1,3 @@
+name: "Terrence Ryan"
+twitter: "tpryan"
+bio: "Terry Ryan is a Developer Advocate for the Google Cloud Platform team. He has 15 years of experience working with the web - both front end and back. Before working for technology shops like Google and Adobe he worked in roles that combined development with system administration at the Wharton School of Business.\n\n He also wrote Driving Technical Change for Pragmatic Bookshelf, a book that arms technology professionals with the tools to convince reluctant co-workers to adopt new tools and technology."
diff --git a/exampleSite/data/speakers/2016/raleigh/aaron-suggs.yml b/exampleSite/data/speakers/2016/raleigh/aaron-suggs.yml
new file mode 100644
index 000000000..8bba34e88
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/aaron-suggs.yml
@@ -0,0 +1,3 @@
+name: "Aaron Suggs"
+twitter: "ktheory"
+bio: "Aaron Suggs is the Operations Engineering Manager at Kickstarter, where he backs too many video game projects. He enjoys writing code that makes developers happier."
diff --git a/exampleSite/data/speakers/2016/raleigh/brian-oconnell.yml b/exampleSite/data/speakers/2016/raleigh/brian-oconnell.yml
new file mode 100644
index 000000000..e9b743982
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/brian-oconnell.yml
@@ -0,0 +1,3 @@
+name: "Brian O'Connell"
+twitter: "boc_tothefuture"
+bio: "Brian O’Connell is a Senior Technical Staff Member at IBM focusing on DevOps, continuously available cloud technologies and software defined environments. Brian leads the team responsible for the transition of high profile web sites such as The Masters, Wimbledon, Roland Garros (French Open), US Open Tennis, and the Australian Open to a hybrid cloud. Brian has more than 300 patents, is an IBM Master Inventor, a member of the IBM Academy of Technology and a Franz Edelman laureate."
diff --git a/exampleSite/data/speakers/2016/raleigh/chris-collins.yml b/exampleSite/data/speakers/2016/raleigh/chris-collins.yml
new file mode 100644
index 000000000..7c5fe2bff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/chris-collins.yml
@@ -0,0 +1,3 @@
+name: "Chris Collins"
+twitter: "ChrisInDurham"
+bio: "Chris Collins is a senior automation engineer and the web architecture lead at Duke University's Office of Information Technology. He's a container and automation evangelist, leads adoption of containers within the university, and loves to talk about them with anyone who will listen, much to the annoyance of the co-workers who sit closest to him."
diff --git a/exampleSite/data/speakers/2016/raleigh/clinton-wolfe.yml b/exampleSite/data/speakers/2016/raleigh/clinton-wolfe.yml
new file mode 100644
index 000000000..eb9cc61e0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/clinton-wolfe.yml
@@ -0,0 +1,3 @@
+name: "Clinton Wolfe"
+twitter: "clintoncwolfe"
+bio: "Clinton Wolfe leads the DevOps Practice at OmniTI, which means he voluntarily chooses to go into heavily siloed, dysfunctional organizations and try to get them to talk to each other with as few stabbings as possible. He's especially interested in testable infrastructure, and the processes needed to support quality throughout the application lifecycle. He is also Oliver and Sylvia’s Daddy."
diff --git a/exampleSite/data/speakers/2016/raleigh/dylan-schowengerdt.yml b/exampleSite/data/speakers/2016/raleigh/dylan-schowengerdt.yml
new file mode 100644
index 000000000..28f3df661
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/dylan-schowengerdt.yml
@@ -0,0 +1,7 @@
+name: "Dylan Schowengerdt"
+twitter: "DevOpsDylan"
+bio: "Dylan wants to live in a world where common sense is a little more common, noise pollution is self-regulated and all dogs get along at the dog park.
+
+As an Operations Professional with almost 10 years of experience, he’s worked for global corporations, tech start-ups and everything in-between keeping business units organized, documented and fun.
+
+When he’s not creating unique customer solutions or designing reports that don’t bore the executive team to death, you can find him trying new recipes in the kitchen, painting in his studio and spending as much time as possible in the Great Outdoors."
diff --git a/exampleSite/data/speakers/2016/raleigh/eric-sigler.yml b/exampleSite/data/speakers/2016/raleigh/eric-sigler.yml
new file mode 100644
index 000000000..664bb1ef4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/eric-sigler.yml
@@ -0,0 +1,3 @@
+name: "Eric Sigler"
+twitter: "esigler"
+bio: "Eric Sigler is an Engineering Manager at PagerDuty, and has formerly led Operations teams at Minted and Missouri S&T. He lives in San Francisco, and when he's not on an incident call he spends his time making cocktails using liquid nitrogen, and hiking around Northern California."
diff --git a/exampleSite/data/speakers/2016/raleigh/fraser-pollock.yml b/exampleSite/data/speakers/2016/raleigh/fraser-pollock.yml
new file mode 100644
index 000000000..5233718d0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/fraser-pollock.yml
@@ -0,0 +1,2 @@
+name: "Fraser Pollock"
+bio: "I’ve been through several DevOps transformation with huge successes and catastrophic failures. I’ve seen the good and the bad of DevOps and am ready to share it at the speed of a lightning talk!"
diff --git a/exampleSite/data/speakers/2016/raleigh/gabe-ortiz.yml b/exampleSite/data/speakers/2016/raleigh/gabe-ortiz.yml
new file mode 100644
index 000000000..bb224c71d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/gabe-ortiz.yml
@@ -0,0 +1,3 @@
+name: "Gabe Ortiz"
+twitter: "signalnine"
+bio: "Gabe Ortiz has been replacing himself with a series of very small shell scripts for over 15 years, though these days it's mostly Python. He is currently sole infrastructure engineer at Agari Data, where he's responsible for Tom Sawyering his coworkers into writing infrastructure code."
diff --git a/exampleSite/data/speakers/2016/raleigh/jen-krieger.yml b/exampleSite/data/speakers/2016/raleigh/jen-krieger.yml
new file mode 100644
index 000000000..02ef5389d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/jen-krieger.yml
@@ -0,0 +1,3 @@
+name: "Jen Krieger"
+twitter: "mrry550"
+bio: "Jen Krieger is Chief Agile Architect at Red Hat. Most of her 20+ year career has been in software development representing many roles throughout the waterfall and agile lifecycles. At Red Hat, she lead a department-wide DevOps movement focusing on CI/CD best practices. Most recently, she worked with the Project Atomic & OpenShift teams. Now Jen is guiding teams across the company into agility in a way that respects and supports Red Hat's commitment to Open Source."
diff --git a/exampleSite/data/speakers/2016/raleigh/josh-atwell.yml b/exampleSite/data/speakers/2016/raleigh/josh-atwell.yml
new file mode 100644
index 000000000..db391caa5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/josh-atwell.yml
@@ -0,0 +1,3 @@
+name: "Josh Atwell"
+twitter: "josh_atwell"
+bio: "Josh Atwell is a Developer Advocate for NetApp SolidFire, focused on building a developer community and enabling customers and partner success. Over the last 10+ years he has worked very hard to allow little pieces of code to do his work for him through various automation tools. Josh is a contributing author to the popular Mastering vSphere series and the Devops for VMware Administrators book. He is a serial community builder and loves getting people together to talk technology or tell stories of pain and success. Never known for lacking an opinion he blogs at vtesseract.com and tweets at @josh_atwell."
diff --git a/exampleSite/data/speakers/2016/raleigh/leon-fayer.yml b/exampleSite/data/speakers/2016/raleigh/leon-fayer.yml
new file mode 100644
index 000000000..c21b57088
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/leon-fayer.yml
@@ -0,0 +1,3 @@
+name: "Leon Fayer"
+twitter: "papa_fire"
+bio: "Leon's two decades of expertise were concentrated on architecting and operating complex, web-based systems to withstand crushing traffic (often unexpectedly). Over the years, he's had a somewhat unique opportunity to design and build systems that run some of the most visited websites in the world. While his core expertise is in application development, he works his way around the whole technology stack from system architecture to databases design and optimization to front/back-end programming. He's considered a professional naysayer by peers and has the opinion that nothing really works until it works for at least a million people. In production."
diff --git a/exampleSite/data/speakers/2016/raleigh/maggie-gourlay.yml b/exampleSite/data/speakers/2016/raleigh/maggie-gourlay.yml
new file mode 100644
index 000000000..809ccaaeb
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/maggie-gourlay.yml
@@ -0,0 +1,3 @@
+name: "Maggie Gourlay"
+twitter: "okterok"
+bio: "I've been doing software quality assurance since the early 2000's and also have a degree in theoretical mathematics. I currently work ensuring quality for a DevOps application which brings me back to the days I was on call as a systems administrator in the late 90's. In my free time, I love to travel and learn new things (currently I'm learning R and Scala)."
diff --git a/exampleSite/data/speakers/2016/raleigh/michael-dehaan.yml b/exampleSite/data/speakers/2016/raleigh/michael-dehaan.yml
new file mode 100644
index 000000000..fed4ca940
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/michael-dehaan.yml
@@ -0,0 +1,3 @@
+name: "Michael DeHaan"
+twitter: "laserllama"
+bio: "Previously invented Ansible, Cobbler, and co-creator of some other things you might have used."
diff --git a/exampleSite/data/speakers/2016/raleigh/peter-lamar.yml b/exampleSite/data/speakers/2016/raleigh/peter-lamar.yml
new file mode 100644
index 000000000..78ab96854
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/peter-lamar.yml
@@ -0,0 +1,3 @@
+name: "Peter Lamar"
+twitter: "ptlamar"
+bio: "Peter has spent many years as both a Software Engineer and Product Manager at various organizations including Electronic Arts, Google and Cisco. Peter Lamar is a course director at Techtown training and thrives on challenging problems and building awesome teams."
diff --git a/exampleSite/data/speakers/2016/raleigh/rebecca-fernandez.yml b/exampleSite/data/speakers/2016/raleigh/rebecca-fernandez.yml
new file mode 100644
index 000000000..d39639904
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/rebecca-fernandez.yml
@@ -0,0 +1,3 @@
+name: "Rebecca Fernandez"
+twitter: "ruhbehka"
+bio: "Rebecca Fernandez is a Principal Employment Branding + Communication Specialist at Red Hat. She is a writer and a communications coach with a passion for cultivating and sustaining great company cultures. Rebecca is the program manager, maintainer, and evangelist for the Open Decision Framework, a collection of Red Hat's best practices for open, collaborative, and inclusive decision making that has been featured in Forbes, ZDNet, Business Insider, and opensource.com. She has contributed to opensource.com, was an editor for Red Hat CEO Jim Whitehurst’s book The Open Organization, and is an Open Organization Ambassador."
diff --git a/exampleSite/data/speakers/2016/raleigh/ryan-cook.yml b/exampleSite/data/speakers/2016/raleigh/ryan-cook.yml
new file mode 100644
index 000000000..d73b0c45c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/ryan-cook.yml
@@ -0,0 +1,3 @@
+name: "Ryan Cook"
+twitter: "cooktheryan"
+bio: "I'm all about making the process of IT easier and less scary. I have been part of a few teams with the goal to help safely speed up IT Infrastructure delivery and the release process from development to production. I love automation and finding out ways to do things faster and easier."
diff --git a/exampleSite/data/speakers/2016/raleigh/suzie-prince.yml b/exampleSite/data/speakers/2016/raleigh/suzie-prince.yml
new file mode 100644
index 000000000..53578bfda
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/suzie-prince.yml
@@ -0,0 +1,3 @@
+name: "Suzie Prince"
+twitter: "pm_suzie"
+bio: "I am Suzie Prince. I am the product manager for a software-as-a-service continuous integration and continuous delivery tool for software engineering teams. My team practices continuous integration and continuous delivery everyday to deliver quality software to our users. I like pushing buttons to release software, feature toggles and pager duty. I also like burritos, beer and hiking."
diff --git a/exampleSite/data/speakers/2016/raleigh/worth-becker.yml b/exampleSite/data/speakers/2016/raleigh/worth-becker.yml
new file mode 100644
index 000000000..9f9a76288
--- /dev/null
+++ b/exampleSite/data/speakers/2016/raleigh/worth-becker.yml
@@ -0,0 +1,3 @@
+name: "Worth Becker"
+twitter: "Func_E"
+bio: "As a consultant, I get exposed to lots of different company culture's. Some are awesome and some are getting it all wrong. I want to share that with you! I'm the co-founder of Neuralux; a software and devops consulting shop trying to do things (pretty much) right."
diff --git a/exampleSite/data/speakers/2016/singapore/adrian-cole.yml b/exampleSite/data/speakers/2016/singapore/adrian-cole.yml
new file mode 100644
index 000000000..5fc8eadfe
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/adrian-cole.yml
@@ -0,0 +1,3 @@
+name: "Adrian Cole"
+twitter: "adrianfcole"
+bio: "Adrian is an active member of cloud interoperability circles. He is the founder of a few popular open source projects, notably Apache jclouds and Netflix feign. Recently, he’s focused on distributed tracing, particularly in the OpenZipkin project. Adrian works at Pivotal in the Spring Cloud OSS team."
diff --git a/exampleSite/data/speakers/2016/singapore/angad-singh.yml b/exampleSite/data/speakers/2016/singapore/angad-singh.yml
new file mode 100644
index 000000000..c8e37bbc9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/angad-singh.yml
@@ -0,0 +1,3 @@
+name: "Angad Singh"
+twitter: "angadsg"
+bio: "Angad is a Data Scientist at Twitter Singapore. He recently led the DevOps team at Viki. He is passionate about large data infrastructures as well as distributed systems. Talked at previous DevOpsDays 2015 Singapore about ELK."
diff --git a/exampleSite/data/speakers/2016/singapore/benjamin-henshall.yml b/exampleSite/data/speakers/2016/singapore/benjamin-henshall.yml
new file mode 100644
index 000000000..a1bace014
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/benjamin-henshall.yml
@@ -0,0 +1,4 @@
+name: "Benjamin Henshall"
+twitter: "bhenshal"
+bio: "Benjamin Henshall is the Director of solutions for Red Hat’s developer tooling and developer platforms for the Asia Pacific region. His primary responsibility is to help clients, partners and the eco-system within Asia adopt the Red Hat toolsets and services in digital transformative opportunities.
+Benjamin comes with over 8 and half years experience within Red Hat and prior working at Oracle within the Fusion Middleware business unit and BEA Systems preceding his time at Oracle. His particular interests is to help organisations ‘out innovate’ the competition through ‘compressed innovation cycles’ using software engineering principles and cultural change known as DevOps and aligning IT architectures and operations to meet the demands of the next generation business model(s). Ben also has a passion for helping organisations understand how to harness the innovation from open source software and participate in their respective communities."
diff --git a/exampleSite/data/speakers/2016/singapore/brett-gray.yml b/exampleSite/data/speakers/2016/singapore/brett-gray.yml
new file mode 100644
index 000000000..75e7b69de
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/brett-gray.yml
@@ -0,0 +1,3 @@
+name: "Brett Gray"
+twitter: ""
+bio: "Greater than 20 years of experience in IT and electronics industry in various sectors, such a private, public and military. Brett has been using Puppet since 2011 and has been a Puppet Labs employee since 2013. Currently Brett is the Principal Solutions and Services Engineer for Puppet in APAC. Brett is the lead consultant in APAC for Puppet and undertakes many complex DevOps engagements. Brett has a Master of Systems Engineering, Bachelor of Computing and GradDip of Brewing."
diff --git a/exampleSite/data/speakers/2016/singapore/clemens-perz.yml b/exampleSite/data/speakers/2016/singapore/clemens-perz.yml
new file mode 100644
index 000000000..537772b60
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/clemens-perz.yml
@@ -0,0 +1,3 @@
+name: "Clemens Perz"
+twitter: ""
+bio: "I have been working as a freelance lead developer/architect/deployment wizzard since 1990 - and I today own the Next Workstation that I started learning Unix on :) Currently I work for a singaporean data center provider automating the deployment and management of an Open Stack infrastructure."
diff --git a/exampleSite/data/speakers/2016/singapore/clemri-steyn.yml b/exampleSite/data/speakers/2016/singapore/clemri-steyn.yml
new file mode 100644
index 000000000..1f92c9f11
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/clemri-steyn.yml
@@ -0,0 +1,3 @@
+name: "Clemri Steyn"
+twitter: ""
+bio: "I am the Group Product Manager on the Microsoft DevOps Marketing team. I have more than 16 years experience in the Developer Tools, ALM and DevOps market. Prior to this role, I managed Product Management teams at Compuware for the DevPartner Studio, DriverStudio, DevPartner for Java, OptimalTrace and Uniface product lines. i have spoken extensively at numerous conferences across the globe"
diff --git a/exampleSite/data/speakers/2016/singapore/ion-mudreac.yml b/exampleSite/data/speakers/2016/singapore/ion-mudreac.yml
new file mode 100644
index 000000000..cbbeefc3f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/ion-mudreac.yml
@@ -0,0 +1,5 @@
+name: "Ion Mudreac"
+twitter: "mudrii"
+bio: "Ion is DevOps Lead in Standard Chartered Bank, Head of Development in EDM. He has 20+ years IT experience with 10+ years experience in Banking. He previously worked in Japan as a Project Manager for Daiwa Securities and Merrill Lynch and eventually moved to Merrill Lynch Singapore to lead Asia Pac Wealth Management support team. Prior joining SCB, he was with Commerzbank and held various team lead roles for eFX Connectivity global team, eFX and FX Option Global support team and Murex Cash/Murex Currency Asia Pacific team.
+
+He is a practitioner of agile and lean development, Scrum, XP and Kanban, with experience in DevOps Continuous Delivery and Continuous Integration."
diff --git a/exampleSite/data/speakers/2016/singapore/jason-man.yml b/exampleSite/data/speakers/2016/singapore/jason-man.yml
new file mode 100644
index 000000000..c8afc201a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/jason-man.yml
@@ -0,0 +1,3 @@
+name: "Jason Man"
+twitter: "mrjasonman"
+bio: "Jason Man is an experienced Continuous Delivery and DevOps consultant at Forest Technologies. Forest has been helping companies worldwide transform their ability to deliver value to their customers through the adoption of DevOps and Automation for over 12 years. We’ve worked across a variety of sectors including retail, telecoms, financial, online gambling and online travel, from the biggest enterprises to small start-ups. This gives us a unique insight into what it takes for companies to successfully adopt a collaborative culture, and the underpinning processes and tools to increase the speed and quality that software and software-related services can be delivered to customers. Jason’s previous experience covers most aspects of the SDLC working as a Developer, Build and Release Engineering as well as architecting and implementing DevOps practices for many organisations around the world."
diff --git a/exampleSite/data/speakers/2016/singapore/ken-mugrage.yml b/exampleSite/data/speakers/2016/singapore/ken-mugrage.yml
new file mode 100644
index 000000000..51e29dfff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/ken-mugrage.yml
@@ -0,0 +1,3 @@
+name: "Ken Mugrage"
+twitter: "kmugrage"
+bio: "Ken Mugrage is a technology evangelist for ThoughtWorks, focused on providing education on DevOps and continuous delivery. He began his IT career in the early 1990s as a system administrator for Seattle’s first Internet service provider. Ken went on to form his own web development company in 1994, creating some of the first data-driven websites anywhere. During the next twenty years he held almost every position in a software development organization—from developer to director of a global engineering team. Using his experience Ken has consulted with top companies on applying the right technical solutions to business problems."
diff --git a/exampleSite/data/speakers/2016/singapore/mike-place.yml b/exampleSite/data/speakers/2016/singapore/mike-place.yml
new file mode 100644
index 000000000..dffb30add
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/mike-place.yml
@@ -0,0 +1,3 @@
+name: "Mike Place"
+twitter: "cachedout"
+bio: "I am the principle maintainer of SaltStack -- one of the world's leading open-source automation platforms. I've keynoted and spoken at dozens of conferences. I'm currently residing in Tokyo so this is a perfect chance for me to attend more conferences in Asia. :]"
diff --git a/exampleSite/data/speakers/2016/singapore/mitchell-hashimoto.yml b/exampleSite/data/speakers/2016/singapore/mitchell-hashimoto.yml
new file mode 100644
index 000000000..3c0d1a7a0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/mitchell-hashimoto.yml
@@ -0,0 +1,3 @@
+name: "Mitchell Hashimoto"
+twitter: "mitchellh"
+bio: "Mitchell Hashimoto is best known as the creator of Vagrant, Packer, Terraform and Consul. Mitchell is the founder of HashiCorp, a company that builds powerful and elegant DevOps tools. He is also an O’Reilly author. He is one of the top GitHub users by followers, activity, and contributions. “Automation obsessed,” Mitchell solves problems with as much computer automation as possible."
diff --git a/exampleSite/data/speakers/2016/singapore/nicole-forsgren.yml b/exampleSite/data/speakers/2016/singapore/nicole-forsgren.yml
new file mode 100644
index 000000000..4457c7aff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/nicole-forsgren.yml
@@ -0,0 +1,3 @@
+name: "Nicole Forsgren"
+twitter: "nicolefv"
+bio: "I am an IT impacts expert who shows leaders and tech professionals how to unlock the potential of technology change. Best known for my work with tech professionals and as the lead investigator on the Puppet Labs State of DevOps study, I am a consultant, expert, and researcher in DevOps, IT adoption and impacts, and knowledge management. I am the Director of Organizational Performance and Analytics at Chef. You can read more about it here, and about what Gartner says about my move from academia here. I am also an Academic Partner at Clemson University. In a previous life, I was a professor, sysadmin, and hardware performance analyst. I hold a PhD in Management Information Systems and a Masters in Accounting. I have been awarded public and private research grants (funders include NASA and the NSF), and my work has been featured in various media outlets, including the Wall Street Journal, Forbes, ComputerWorld, and InfoWeek. I have been named a Top 100 Leader and renowned expert in DevOps, and a Top 20 Most Influential Women in DevOps by TechBeacon."
diff --git a/exampleSite/data/speakers/2016/singapore/rizky-ariestiyansyah.yml b/exampleSite/data/speakers/2016/singapore/rizky-ariestiyansyah.yml
new file mode 100644
index 000000000..ac2894d74
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/rizky-ariestiyansyah.yml
@@ -0,0 +1,3 @@
+name: "Rizky Ariestiyansyah"
+twitter: "ariestiyansyah"
+bio: "Full-time researcher, part-time tech speaker, I've been working from small to big scale of DevOps system starting from StartUp to Minister in Indonesia. Mozilla Tech Speaker and CTO at IndonesiaX.co.id."
diff --git a/exampleSite/data/speakers/2016/singapore/seth-vargo.yml b/exampleSite/data/speakers/2016/singapore/seth-vargo.yml
new file mode 100644
index 000000000..adf35ecc6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/seth-vargo.yml
@@ -0,0 +1,3 @@
+name: "Seth Vargo"
+twitter: "sethvargo"
+bio: "Seth Vargo is the Director of Evangelism at HashiCorp. Previously, Seth worked at Chef (Opscode), CustomInk, and a few Pittsburgh-based startups. He the author of Learning Chef and is passionate about reducing inequality in technology. When he is not writing, working on open source, or speaking at conferences, Seth enjoys spending time with his friends and advising non-profits. He loves all things bacon."
diff --git a/exampleSite/data/speakers/2016/singapore/stefan-streichsbier.yml b/exampleSite/data/speakers/2016/singapore/stefan-streichsbier.yml
new file mode 100644
index 000000000..fdf587b51
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/stefan-streichsbier.yml
@@ -0,0 +1,4 @@
+name: "Stefan Streichsbier"
+twitter: "s_streichsbier"
+bio: "Stefan has been focusing on information security since 2003. He is passionate about analysing complex applications through architecture, design and source code reviews and improving their security posture. As the CTO of Vantage Point he is working on revolutionary approaches to integrate security into the agile and DevOps with the goal to sustainably eradicate vulnerabilities from applications and empower dev teams.
+Stefan has founded the local DevSecOps Singapore Meetup group that is enjoying an active and ever growing community."
diff --git a/exampleSite/data/speakers/2016/singapore/will-thames.yml b/exampleSite/data/speakers/2016/singapore/will-thames.yml
new file mode 100644
index 000000000..bb2acdc34
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/will-thames.yml
@@ -0,0 +1,3 @@
+name: "Will Thames"
+twitter: "willthames"
+bio: "Ultrarunner and software deliverer. I like running, beer, devops, continuous delivery."
diff --git a/exampleSite/data/speakers/2016/singapore/yagnik-khanna.yml b/exampleSite/data/speakers/2016/singapore/yagnik-khanna.yml
new file mode 100644
index 000000000..d6ed09206
--- /dev/null
+++ b/exampleSite/data/speakers/2016/singapore/yagnik-khanna.yml
@@ -0,0 +1,3 @@
+name: "Yagnik Khanna"
+twitter: ""
+bio: "I'm currently an Architect of Cloud and Infrastructure at Snapdeal and previously an engineer at Shopify"
diff --git a/exampleSite/data/speakers/2016/sydney/bridget-kromhout.yml b/exampleSite/data/speakers/2016/sydney/bridget-kromhout.yml
new file mode 100644
index 000000000..de1378824
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/bridget-kromhout.yml
@@ -0,0 +1,3 @@
+name: "Bridget Kromhout"
+twitter: "bridgetkromhout"
+bio: "Bridget Kromhout is a Principal Technologist for Cloud Foundry at Pivotal. Her CS degree emphasis was in theory, but she now deals with the concrete (if ‘cloud’ can be considered tangible). After years as an operations engineer (most recently at DramaFever), she traded in oncall for more travel. A frequent speaker at tech conferences, she helps organize tech meetups at home in Minneapolis, serves on the program committee for Velocity, and acts as a global core organizer for devopsdays. She podcasts at Arrested DevOps, occasionally blogs at bridgetkromhout.com, and is active in a Twitterverse near you."
diff --git a/exampleSite/data/speakers/2016/sydney/donny-nadolny.yml b/exampleSite/data/speakers/2016/sydney/donny-nadolny.yml
new file mode 100644
index 000000000..404bc4ebc
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/donny-nadolny.yml
@@ -0,0 +1,3 @@
+name: "Donny Nadolny"
+twitter: "DonnyNadolny"
+bio: "Donny Nadolny is a developer at PagerDuty, working on improving incident response. He is one of the co-organizers of Failure Friday, and is always interested in talking about distributed systems."
diff --git a/exampleSite/data/speakers/2016/sydney/hannah-browne.yml b/exampleSite/data/speakers/2016/sydney/hannah-browne.yml
new file mode 100644
index 000000000..301e5b731
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/hannah-browne.yml
@@ -0,0 +1,7 @@
+name: "Hannah Browne"
+twitter: "HannahBrowne"
+bio: "
Hannah Browne is an opinionated deal maker and General Manager of software delivery and devops firm, Cevo. A non-technical technologist strongly focused on the people component of teams and organisations, because frankly, the technology problems are the usually the easier challenges to resolve.
+
+
She cut her teeth with The British Consul-General, before leading Friday Media and Lambda Software through periods of strong growth and service evolution. Prior to starting Cevo in Victoria, Hannah worked with ThoughtWorks delivering great software with clients like IOOF, MYOB, Coles, World Vision, Slater & Gordon and Australia Post.
+
+
Now her mandate is to build Cevo into Australia’s premier provider of software delivery, devops and automation capability by forging a team of great technologists, who solve interesting problems with awesome clients.
Lindsay Holmwood is a engineering manager living in the Australian Blue Mountains. Lindsay works at the Australian Government’s Digital Transformation Agency, building clearer, simpler, faster public services . A long-time contributor to the open source and DevOps communities, he authored cucumber-nagios, Visage, and Flapjack, and has run the Sydney DevOps meetup the past six years.
+
Lindsay speaks internationally about both the cultural and technical side of DevOps, covering Just Culture, complexity, cognitive biases, and monitoring tools. He also won third place at the 1996 Sydney Royal Easter Show LEGO building competition.
"
diff --git a/exampleSite/data/speakers/2016/sydney/mujtaba-hussain.yml b/exampleSite/data/speakers/2016/sydney/mujtaba-hussain.yml
new file mode 100644
index 000000000..5f1c071aa
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/mujtaba-hussain.yml
@@ -0,0 +1,3 @@
+name: "Mujtaba Hussain"
+twitter: "khalidaapps"
+bio: "Infrastructure Engineer at Fillr (https://www.fillr.com)"
diff --git a/exampleSite/data/speakers/2016/sydney/nigel-kersten.yml b/exampleSite/data/speakers/2016/sydney/nigel-kersten.yml
new file mode 100644
index 000000000..3195ec071
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/nigel-kersten.yml
@@ -0,0 +1,3 @@
+name: "Nigel Kersten"
+twitter: "nigelkersten"
+bio: "Nigel came to Puppet from Google HQ in Mountain View, where he was responsible for the design and implementation of one of the largest Puppet deployments in the world. At Puppet, Nigel was responsible for development of the initial versions of Puppet Enterprise, and has since served in a variety of roles, including head of product, CTO and CIO. He has been deeply involved in Puppet's DevOps initiatives, and regularly speaks around the world about adoption of DevOps in the enterprise and IT organizational transformation."
diff --git a/exampleSite/data/speakers/2016/sydney/patrick-robinson.yml b/exampleSite/data/speakers/2016/sydney/patrick-robinson.yml
new file mode 100644
index 000000000..3aabc0aef
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/patrick-robinson.yml
@@ -0,0 +1,5 @@
+name: "Patrick Robinson"
+twitter: "drnemski"
+bio: "I have worked as a systems/devops engineer for 5 years mostly on large distributed platforms. I am easily bored with repetitive work and find myself constantly trying to automate myself out of a job, but alas have not yet succeeded.
+I currently work at Envato, an e-commerce company specialising in creative digital media.
+My current technical interests are container orchestration and learning Golang and Elixir."
diff --git a/exampleSite/data/speakers/2016/sydney/peter-hall.yml b/exampleSite/data/speakers/2016/sydney/peter-hall.yml
new file mode 100644
index 000000000..2f85a9d70
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/peter-hall.yml
@@ -0,0 +1,3 @@
+name: "Peter Hall"
+twitter: "peterkh"
+bio: "Operations Delivery Lead at REA Group"
diff --git a/exampleSite/data/speakers/2016/sydney/steve-mactaggart.yml b/exampleSite/data/speakers/2016/sydney/steve-mactaggart.yml
new file mode 100644
index 000000000..2f38ffb19
--- /dev/null
+++ b/exampleSite/data/speakers/2016/sydney/steve-mactaggart.yml
@@ -0,0 +1,4 @@
+name: "Steve Mactaggart"
+twitter: "stevemac"
+bio: "
Steve Mactaggart is an Application Delivery Evangineer at Cevo, his focus is on helping businesses deliver the best solution for their customers in a way that fits both their timelines and their customer needs. A passionate technologist, he takes great pleasure in keeping abreast of current trends in technology always looking for opportunities to improve current practice with some innovative thinking.
+
Using Lean and Agile principals, Steve is constantly working with teams to help them realise the goal of delivering value in discrete units, measuring the results and then learning and adapting in rapid succession.
"
diff --git a/exampleSite/data/speakers/2017/moscow/alexleyn.yml b/exampleSite/data/speakers/2017/moscow/alexleyn.yml
new file mode 100644
index 000000000..9b3e62e7f
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/alexleyn.yml
@@ -0,0 +1,10 @@
+name: "Alexander Leyn"
+twitter: ""
+bio: "Александр Лэйн
+Родился 09.06.1987
+Имею высшее образование по специальности Автоматизированные системы обработки информации и управления.
+В ИТ работаю с 2003 года.
+Общение с компами началось с 286-го в возрасте 4-х лет.
+Имею стаж системного администратора около 6-ти лет.
+Последние 2 года работаю руководителем: 1,5 года руководителем дежурных админов в QIWI и полгода руководителем отдела эксплуатации в DocDoc.
+Люблю все автоматизировать. Предпочитаю погрузиться в автоматизацию на несколько дней, чем выполнять монотонную похожую работу)."
diff --git a/exampleSite/data/speakers/2017/moscow/anton-ivanov.yml b/exampleSite/data/speakers/2017/moscow/anton-ivanov.yml
new file mode 100644
index 000000000..9915b2d9e
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/anton-ivanov.yml
@@ -0,0 +1,3 @@
+name: "Anton Ivanov"
+twitter: "IvanovAnton"
+bio: "Тим лид команды SRE (site reliability engineering) в HeadHunter.
SRE (Site reliability engineering) team lead at HeadHunter."
diff --git a/exampleSite/data/speakers/2017/moscow/anton-weiss.yml b/exampleSite/data/speakers/2017/moscow/anton-weiss.yml
new file mode 100644
index 000000000..43e65a970
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/anton-weiss.yml
@@ -0,0 +1,3 @@
+name: "Anton Weiss"
+twitter: ""
+bio: "Антон (Энт) Вайс - совладелец технологического консалтинга Отомато. Обладатель более чем 15-тилетнего опыта в области высоких технологий. Эксперт по техническому преподаванию. Инициатор и со-автор первого в Израиле курса девопс-сертификации. Участник ряда международных конференций, опытный докладчик.
Anton (Ant) Weiss is the founder, principal consultant and CEO at Otomato – the effective software delivery company. Anton has been building and delivering software for the last fifteen years both at large enterprise companies (AT&T, BMC) and startups. A big fan of technical training and knowledge sharing, Anton was one of the initiators and instructors of the first DevOps certification course in Israel. Anton is a seasoned engineer, but he also holds a BA in Sociology and an MBA, which makes him very keen on exploring the social aspects of collaborative software development. He is a frequent speaker at technology events and a rock star – Ant loves the stage and makes sure his audience stays both entertained and enriched. Firm believer in continuous improvement and organisational transparency."
diff --git a/exampleSite/data/speakers/2017/moscow/katerina-troshina.yml b/exampleSite/data/speakers/2017/moscow/katerina-troshina.yml
new file mode 100644
index 000000000..4dd0bf550
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/katerina-troshina.yml
@@ -0,0 +1,10 @@
+name: "Ekaterina Troshina"
+twitter: ""
+bio: "В настоящее время является ведущим специалистом по анализу кода компании Solar Security.
+В 2005 году с отличием закончила факультете ВМК МГУ и потупила в аспирантуру, где продолжила, начатые еще в студенческие годы работы по анализу программ как в высокоуровневом, так и в низкоуровневом представлении. В 2009 году защитила диссертацию на соискание ученой степени кандидата физико -математических наук на факультете ВМК МГУ.
+Трошина К.Н. занимается анализом кода в том числе и по требованиям ИБ уже более 15 лет. Помимо этого выполняет работы, связанные с внедрением различных успешных мировых практик по разработке защищенного программного обеспечения в крупные компании. Имеет большой опыт разработки различных регламентов реагирования на инциденты, а также различных программ повышения качества работы программистов: от обучения до мотивации.
+
Currently she is a lead expert in code analysis with Solar Security.
+In 2005 she obtained specialist degree from the Faculty of Computational Mathematics and Cybernetics, Lomonosov Moscow State University.
+In 2009 she received Ph.D. from Lomonosov Moscow State University. The thesis topic was high-level and low-level program analysis.
+She has been performing the code analysis for over 15 years. She is engaged in deployment of the industry’s best practices of secure software development to the major companies. Katerina gas deep in-field experience in development of incident response regulations as well as various motivation and awareness programs for developers.
+"
diff --git a/exampleSite/data/speakers/2017/moscow/konstantin-nazarov.yml b/exampleSite/data/speakers/2017/moscow/konstantin-nazarov.yml
new file mode 100644
index 000000000..1e9f7a8f3
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/konstantin-nazarov.yml
@@ -0,0 +1,3 @@
+name: "Konstantin Nazarov"
+twitter: "racktear"
+bio: "Константин Назаров - инфраструктурный инженер в команде Tarantool. В прошлом - системный программист и любитель Common Lisp. Минималист и приверженец итеративного подхода ко всему.
Konstantin Nazarov is an infrastructure engineer in Tarantool team. In the past was a system programmer and a fan of Common Lisp. Minimalist and adept of iterative approach to everything."
diff --git a/exampleSite/data/speakers/2017/moscow/leon-fayer.yml b/exampleSite/data/speakers/2017/moscow/leon-fayer.yml
new file mode 100644
index 000000000..55cb7b293
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/leon-fayer.yml
@@ -0,0 +1,3 @@
+name: "Leon Fayer"
+twitter: "papa_fire"
+bio: "Два десятилетия опыта Леона были сконцентрированы на проектировании и эксплуатации сложных веб-систем, которые смогли бы устоять про многократном росте трафика (часто, неожиданно для всех). На протяжении многих лет у него была уникальная возможность проектировать и строить системы, которые поддерживают некоторые из самых посещаемых сайтов в мире, таких как National Geographic, WhiteHouse.gov, и т.д. Он считается профессиональным циником среди коллег и абсолютно уверен что на самом деле ничего не может считаться работающим пока не работает, как минимум, для миллиона пользователей.
Leon's two decades of expertise were concentrated on architecting and operating complex, web-based systems to withstand crushing traffic (often unexpectedly). Over the years, he's had a somewhat unique opportunity to design and build systems that run some of the most visited websites in the world. While his core expertise is in application development, he works his way around the whole technology stack from system architecture to databases design and optimization to front/back-end programming. He's considered a professional naysayer by peers and has the opinion that nothing really works until it works for at least a million people. In his current role as Vice President of OmniTI Leon advises companies about critical aspects of project strategies and and concentrates on educating others by writing and speaking about industry trends and best practices, sharing his experience as related to designing and operating architectures at scale."
diff --git a/exampleSite/data/speakers/2017/moscow/michael-huttermann.yml b/exampleSite/data/speakers/2017/moscow/michael-huttermann.yml
new file mode 100644
index 000000000..6f5b88ea0
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/michael-huttermann.yml
@@ -0,0 +1,3 @@
+name: "Michael Hüttermann"
+twitter: ""
+bio: "Background on my person: Michael Hüttermann (Java Champion, SCJA, SCJP, SCJD, SCWCD) is freelance developer, architect, coach, author and tutor for Java/JEE, ALM/SCM and agile software development. He speaks at international conferences, was responsible stage producer of the tooling track of Agile 2009, is driver of the Java User Group Cologne, java.net JUGs Community Leader, member of Agile Alliance, member of the JetBrains Academy, committer to FEST as well as Java contributor. His work-life-balance also consists of writing books and articles. Further information:http://huettermann.net."
diff --git a/exampleSite/data/speakers/2017/moscow/sergei-egorov.yml b/exampleSite/data/speakers/2017/moscow/sergei-egorov.yml
new file mode 100644
index 000000000..559ae9bc8
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/sergei-egorov.yml
@@ -0,0 +1,3 @@
+name: "Sergei Egorov"
+twitter: "bsideup"
+bio: "DevOps-на-все-руки (и голову) в компании ZeroTurnaround. Является со-ведущим русскоговорящего DevOps подкаста \"Two Devs One Ops\". Ранее работал в геймдеве, где высоконагруженные системы - это не вам не хухры-мухры!
DevOps-man at ZeroTurnaround. Co-creator of a DevOps podcast (in Russian) named \"Two Devs One Ops\". Used to be a game developer, where \"highload\" - isn't a buzzword!"
diff --git a/exampleSite/data/speakers/2017/moscow/yartsev.yml b/exampleSite/data/speakers/2017/moscow/yartsev.yml
new file mode 100644
index 000000000..af94146bd
--- /dev/null
+++ b/exampleSite/data/speakers/2017/moscow/yartsev.yml
@@ -0,0 +1,3 @@
+name: "Vladimir Yartsev"
+twitter: ""
+bio: "Владимир Ярцев - технический директор в компании Cloud Castle и создатель dockhero.io. В прошлом - системный программист и сисадмин. В настоящем - Ruby-on-Rails-разработчик и адепт Heroku. Верит в The Twelve Factors.
Vladimir Yartsev is a technical director at Cloud Castle and creator of dockhero.io. A system programmer and sysadmin in the past, a Ruby-on-Rails developer and Heroku adept in the present. Strongly believes into The Twelve Factors."
diff --git a/exampleSite/static/events/2015-amsterdam/logo.png b/exampleSite/static/events/2015-amsterdam/logo.png
new file mode 100644
index 000000000..d780631c1
Binary files /dev/null and b/exampleSite/static/events/2015-amsterdam/logo.png differ
diff --git a/exampleSite/static/events/2015-austin/logo.png b/exampleSite/static/events/2015-austin/logo.png
new file mode 100644
index 000000000..9d7cc739b
Binary files /dev/null and b/exampleSite/static/events/2015-austin/logo.png differ
diff --git a/exampleSite/static/events/2015-bangalore/logo.png b/exampleSite/static/events/2015-bangalore/logo.png
new file mode 100644
index 000000000..6be2d505a
Binary files /dev/null and b/exampleSite/static/events/2015-bangalore/logo.png differ
diff --git a/exampleSite/static/events/2015-berlin/logo.png b/exampleSite/static/events/2015-berlin/logo.png
new file mode 100644
index 000000000..fa888b6d6
Binary files /dev/null and b/exampleSite/static/events/2015-berlin/logo.png differ
diff --git a/exampleSite/static/events/2015-boston/boston.jpg b/exampleSite/static/events/2015-boston/boston.jpg
new file mode 100644
index 000000000..edd2d1653
Binary files /dev/null and b/exampleSite/static/events/2015-boston/boston.jpg differ
diff --git a/exampleSite/static/events/2015-derby/conduct/index.html b/exampleSite/static/events/2015-derby/conduct/index.html
new file mode 100644
index 000000000..671e6d282
--- /dev/null
+++ b/exampleSite/static/events/2015-derby/conduct/index.html
@@ -0,0 +1,203 @@
+
+
+
+
+
+
+
+
+
+
+Derby 2015
+ - Conduct
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
All attendees, speakers, sponsors and volunteers at our conference are required to agree with the following code of conduct. Organisers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensuring a safe environment for everybody. A strong community benefits everyone. To that end, please consider as a goal that you should always try to benefit the community by encouraging participation, open-mindedness, learning, and safety in every interaction. Behaviour outside of our community guidelines is unacceptable and should and will not be tolerated by anyone.
+
+
tl;dr: Don’t be a Jerk
+
+
+
The Quick Version
+
+
Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, age, sexual orientation, disability, physical appearance, body size, race, or religion (or lack thereof). We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organisers.
+
+
The Less Quick Version
+
+
Harassment includes offensive verbal comments related to gender, age, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
+
+
Participants asked to stop any harassing behavior are expected to comply immediately.
+
+
Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualised images, activities, or other material. Booth staff (including volunteers) should not use sexualised clothing/uniforms/costumes, or otherwise create a sexualised environment.
+
+
If a participant engages in harassing behavior, the conference organisers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. Conference staff can be identified as they'll be wearing branded t-shirts.
+
+
Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+
We expect participants to follow these rules at conference and workshop venues and conference-related social events.
Saturday 7th February to Sunday 8th of February 2015 POSTPONED - further info to follow
+
+
+
This conference, which is now happening frequently around the globe, is THE conference for bridging the gap between developers and operations.
+
+
DevOpsDays is a grassroots event for folks in the field connecting, sharing war stories, advice, ideas, and tools relating to DevOps.
+
+
It is organized by people who care about DevOps.
+
+
About Derby
+
+
Derby a bustling and vibrant city located in the East Midlands area of the UK, it has a renound reputatiuon for transport and aero manufacturing with Rolls-Royce and Toyota having manfacturing bases there. Situated near East Midlands airport with fantastic rail and road transport links to London, it makes a great location for both international delegates and UK based devops entusiasts.
+
+
Register
+
+
Unfortunately tickets are not yet available, so please register your interest and we'll let you know the latest news about the event including sponsorship, the shedule and when and how to get tickets.
We are currently shouting out for speakers. If you are doing something new and interesting in the DevOps space we want to hear from you! If you have something great to talk about, then we're happy to help you polish and practice your presentation.
+
+
Also, if you know someone who would be a great speaker or somebody you would like to see, let us know! This is a community driven event, so we want your input.
+
+
Patrick Debois, who started DevOps Days and is also helping co-ordinate events around the world, recently said in an interview that "the content of the show needs to continuously evolve and be new. We don’t want content that is already available online. We want new content and controversial ideas for our audience." Let's make that happen!
Get a notification whether your proposal was accepted
+
+
+
+
Proposal Checklist
+
+
+
Title
+
Speaker name (optionally, company/position)
+
Abstract
+
Talk type (Ignite (5 min) or regular (30 min))
+
Twitter handle (or public means of contact)
+
Email (won’t be published, unless specified by you)
+
Bio (max 200 words, we reserve the right to shorten it for publishing/layout reasons)
+
+
+
+
Besides the suggest a speaker/topic we also have the traditional ways to propose a session:
+
+
+
A proposal for a talk/panel during the conference part : these are 30 minute slots that will have all people's full attention as everybody will be in that one room.
+
An Ignite talk that will be presented during the Ignite sessions: these are 5 minutes slots with slides changing every 15 seconds (20 slides total) also presented to all attendees in one room
+
Openspace session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during the openspace opening. Check the openspace format for more information
+
+
+
+
+
+
Speaker selection
+
+
+
The selection is done by the complete organization team over a discussion.
+We take into account comments/remarks at the bottom of each proposal.
+Once selection is complete, we will notify both selected and non selected speakers.
+Optionally we will tell people they are a runner up or ask them to propose the same subject as an Ignite talk.
+
+
Suggest a speaker, topic
+
+
+
Come on, don't be shy. We know you've always wanted a person to give their own view on a specific subject.
+Now's your chance and we might make it happen.
Please register your interest and we'll let you know the latest news about the event including sponsorship, the shedule and when and how to get tickets.
We greatly value sponsors for this open event. If you are interested in sponsoring drop us an email.
+
+
+
+
+
+
+
+
+
Packages
Silver (1500 £)
Gold (3000 £)
+
+
+
+
+
+
Logo on website
+
Logo on all email communications
+
Ability to demo product (5min max) during Openspace Demo Session
+
2 free sponsor tickets
+
+
Opportunity to do a one minute pitch to the full audience
+
Additional 2 passes (4 in total)
+
Sponsor presence and Booth Space (simple table, no full blown commercial booth:) at event
+
+
+
+
+
+
DevOpsDays is a self-organizing conference for DevOps practitioners that depends on your sponsorships to happen. However, because of the nature of the event, we do not have vendor booths or book product pitches.
+
+
Gold sponsors do get a table they can hang out at and put materials on for interested people to come visit during breaks, and of course all attendees are welcome to propose any subject they want during the openspaces, but this is not 'that kind of conference' and heavy marketing will probably work against you when trying to make a good impression on the attendees. The best thing to do is send engineers to interact with the experts at DevOpsDays on their own terms.
Abstract:
+One of the main tenets of the Devops movement is empathy. One might even say it is the "essence" of Devops.
+
+
Throughout history, great philosophers, writers, and thinkers have passed along important thoughts and ideologies about our relationships, our passions, our purpose, and our place in this world. Time and time again, they return to the idea of empathy in one form or another.
+
+
Henry David Thoreau wrote "Could a greater miracle take place than for us to look through each other's eye for an instant?" Heinz Kohut, an American clinical psychologist, was the first to consider empathy as a form of internal scientific inquiry. "Our task must be to free ourselves from this prison by widening our circle of compassion to embrace all living creatures and the whole of nature in its beauty." wrote Albert Einstein. Even the Golden Rule of "One should treat others as one would like others to treat oneself." is a message passed down through scripture. You know - "Do unto others"
+
+
Philosophy, like the DevOps movement, forces us to ask questions of ourselves and our place in the bigger picture. How do we interact & communicate with others? What does it take to be a contributing member of a team and how can you be a better teammate?
+
+
We will use this as a platform to explore additional parallels of basic philosophy and the ideals that are a part of that and how they can be woven into the fabric of Devops. Call it a different approach at explaining the Devops message and movement.
+
+
Additionally, we'll touch on the fact that (like in philosophy), "leaders" and "teachers" will surface to "Show you the way" (of Devops). Some have the best of intentions, others may just be looking out for themselves or trying to make money on the movement. (i.e. DevOps Institute?)
+
+
Where do casual observers of Devops "best practices" fall in to this? Compare that to those who follow the Devops methodology by the book and rarely deviate. Is one better than the other?
+
+
By placing the ideals of Devops in to a different context, perhaps we can spark other interesting thoughts and dialogues that may help others to seek what Devops may mean to them and how they can apply it to their own situations within an organization.
ChatOps is a topic that has really started to gain traction within the last year. As teams begin to adopt the practice of inserting tools right within their conversations, more and more questions are being raised. Many of those questions are simply "how do I get started?"
+
+
In many cases, teams are distributed across the country or broader and adopting the practice of ChatOps is easy and the benefits are clear. Conversely, for those teams who all work together, it's tougher to find obvious motivation to adopt the practice.
+
+
We'll address methods of bringing non-distributed teams in to the modern age of ChatOps by highlighting the primary benefits of the practice with a focus on what is important even when your entire team works under one roof.
This talk will cover many of the high-level features of Consul as they relate to monitoring. While this talk may seem deeply technical on the surface, it is aimed at a very large audience. I will not discuss setup or installation of Consul, but I will demonstrate the Consul Web UI and command line. There will be some commands/code on slides, but there will be no live demos.
+
+
One of the goals of this talk is to demonstrate the Consul is more than a monitoring solution - it is a runtime for the modern datacenter. Consul allows infrastructure to adapt to the changing needs of any environment.
+
+
Descripton
+
+
Consul is an open source tool for service discovery, monitoring, and infrastructure configuration. There are two sides to monitoring -- exposing problems with alerts and acting upon those alerts to automatically resolve them when possible or notify an operator.
+
+
For exposing problems, Consul works much like other monitoring solutions. Users can define any script for Consul to intelligently check and report the health status of a node in a cluster. In this way, Consul is compatible with Nagios and Sensu style checks, but the problem with monitoring systems like Nagios or Sensu is that they are knowledge silos. They are designed to ingest health information and expose them to human operators. Consul supports health monitoring using Nagios-style plugins, but it is designed to expose that information in a way that is both machine and human actionable.
+
+
With Consul custom watches and service discovery integration, infrastructure can automatically react and adjust around failures. If a web node is reporting an unhealthy state, Consul can automatically remove the node from the load balancer. If a disk space health check is low, Consul can automatically run logrotate and delete everything in /tmp. If CPU load is high, Consul can trigger a script to add more nodes to the cluster. In this way, Consul pushes the existing paradigms of monitoring, making it much more than a notification system.
The software industry is rapidly moving to a Software-as-a-Service (SaaS) model. Compared to traditionally licensed software, SaaS greatly shortens release cycles, significantly shrinks support costs, and allows publishers to reach the global market. As part of this agile evolution, more and more developers are choosing to create their SaaS products in the public cloud. This talk will introduce the experienced web developer to building a highly-scalable, self-healing SaaS application on Amazon Web Services. Some of the things you'll take back to work: The business reasons for building a SaaS product over an installed product, the scalability and security challenges introduced by serving thousands of customers from a single instance of an application, and the different tenancy models and the tradeoffs of each.
Cheffing Etsy: Do too many cooks really spoil the soup?
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
It's an oft-quoted adage that too many cooks spoil the soup. But is this always true? At Etsy, we have roughly 40 Ops and Developers making upwards of 20 or 30 Chef changes per day.
+
+
In this talk, I'll look at the tools, techniques and workflows we leverage to enable tens of people spread across teams, timezones and even countries to work together to continuously deliver Chef changes with nearly the same frequency we ship code. Although the specific tooling discussed in this talk is designed to work with Chef, many of the techniques and practices I'll talk about are applicable to many other engineering disciplines - the importance of communication and visibility in a Continuously Delivered world, the importance of testing and metrics, and optimising your workflows to remove friction and enable agility while also satisfying the requirements of your stakeholders.
+
+
This talk will break down roughly as follows:
+
+
+
A quick summary of Chef at Etsy - what we use it for, a quick guide to our workflow, and how we think about Chef changes internally
+
Tooling & Workflows - the tools and practices we use to deliver our Chef changes, and how we monitor and test our changes.
+
The roadbumps we've encountered along the way as we've scaled and evolved our usage of Chef and what we've done to solve those problems
+
What next? We're not perfect, and we never stop iterating and improving our workflows. What are the pain points we're experiencing currently, and how are we looking to solve them?
How do you choose the technology to run your business? The prevailing advice du jour is something like: "use the best tool for the job." This is obviously right, but it is also devoid of meaning in an unfortunate way that lets people define the words "best" and "job" as myopically as they like.
+
+
This talk aims to give shape to these nebulous terms. Your job is to keep your company in business. The best tools tend to be the ones that solve the widest array of problems while requiring the least amount of operational overhead. If innovation happens when preparation meets opportunity, I submit that opportunity rarely appears in the form of an unforeseen data loss bug.
+
+
Choose boring technology. If you can get past this, you can be exciting in ways you can't imagine.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/Code like a Beginner with the Insight of a Pro/index.html b/exampleSite/static/events/2015-minneapolis/proposals/Code like a Beginner with the Insight of a Pro/index.html
new file mode 100644
index 000000000..1db6716ea
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/Code like a Beginner with the Insight of a Pro/index.html
@@ -0,0 +1,370 @@
+
+
+
+
+
+Code like a Beginner with the Insight of a Pro
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Too often, the most experienced people on your team, the ones who have so much to teach, are also the hardest to understand. Documentation frequently falls out of date, intimidated rookies become the norm, and perl golf jokes get thrown around (and actually implemented).
+
+
For this reason, its really important to establish a natural method of knowledge transfer. Too many people have work that cant be completed or improved upon by others due to siloed strategies and implementations. Collaborative work using things like wiki's, git repositories, code reviews, partner programming (even in reactive situations), allows you to get things done right, improve processes, and move forward in all areas of work. This gives you the best bang for your buck and keeps things progressing.
+
+
Documentation becomes universally understood. Information spreads naturally through the organization. Decisions get made quicker and concensus is established early. Walking through these strategies allows us to find ways where everyone of every level can contribute, and even those experts, really hone their skills and consider things they originally didnt think about. Everyone improves and everyone becomes an expert.
Abstract:
+It's your birthday, and the day before your vacation starts. You arrive at the office, prep your workstation, get a drink, and start the day. Almost immediately, you start to receive indicators that multiple core systems are beginning to have critical failures as the slow trickle of alerts increases to multiple alarms sounding. By now the systems are entirely inaccessible due to system load, and you watch the count of outgoing alerts plummet. It's 10:52 am; it's your aircraft.
+
+
These are the PagerDuty (Unintended) War Stories.
+
+
In this talk we'll discuss the failures, the successes, and the outcomes of unexpected incidents at PagerDuty. This includes the technical details of the outage, and how an internal incident commander was used to coordinate the recovery work across multiple teams cohesively.
DevOps is often heralded as the solution to all the problems within IT - planning, slow delivery, large team, etc. All solved via automation. Yet, DevOps is not a technology problem at core, but rather a business problem. Once the dust settles and the new tools are implemented, the more challenging problems begin. Implementation of a DevOps type practice requires change and adaptation of the practices within the framework of the existing culture, and these challenges are often overlooked or poorly addressed.
+This talk discusses many of these challenges as observed in small and large companies alike, how to plan and execute successfully. This includes technologies and techniques including:
+
+
+
The Hows and Why of ChatOps
+
Avoiding the Great is the Enemy of Good concerns.
+
Decoupling complex infrastructures with DevOps tools
The most critical component of building out successful a DevOps culture is creating a successful merger of sustainable technology and process. ChatOps practices help teams accelerate delivery by bringing in technology operations inline with conversations already happening today. This in turn helps turns operations into simple events than can be chained together to make teams even more powerful and flexible than ever before! This talk discusses the practical implementations of ChatOps and how it can be used to grow teams of all types and sizes.
Devops has come a long way in the 5+ years since its inception. From simply breaking down silos and automating/measuring all the things, we’ve grown and started talking recently about complexity and inclusivity, burnout and empathy. We started trying to make people's professional lives better in the fields of development and operations; this expanded in two dimensions: both including more teams (QA! Databases! Even security!) and outside of the office, encouraging people to think about burnout and work-life balance.
+
+
What’s missing from this picture? Or rather, what’s next for devops? I’d like to propose that, as the lines between the “online” world and the “real” world blur and fade away to nothing, we expand our view of devops to cover this whole new world. Let’s expand our empathy beyond just the tech industry, following the examples of B Corporations who work towards social and environmental good. And let’s talk about how we can make the world better, more empathetic, and safer for everyone, online and off.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/DevOps as understood by a young IBM developer/index.html b/exampleSite/static/events/2015-minneapolis/proposals/DevOps as understood by a young IBM developer/index.html
new file mode 100644
index 000000000..942f0c9da
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/DevOps as understood by a young IBM developer/index.html
@@ -0,0 +1,379 @@
+
+
+
+
+
+DevOps as understood by a young IBM developer
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Most of us have heard about what DevOps is, and what are its merits and challenges. Many of us practice it everyday. In this conference and its past editions, we have heard what the early adopters did to catch the DevOps boat.
+I wish to present a Developer's view on what it means to be a part of DevOps. What it means to be part of a steady, mature Agile process, and what happens when one is suddenly thrown into the fast paced, fail-fast, DevOps roller coaster.
+My short talk will focus on the following aspects.
+
+
1) Various change catalysts in the tech industry. viz. environment, competition, process need, leader's vision, curiosity.
+2) What I was doing couple of years back, and my current work-day. What changed, and what helped me get here?
+3) Some of my biggest challenges, how I dealt with uncertainties, found my own path, and adapted to the changes to be a leader when I transitioned from Agile to DevOps.
+
+
4) What developers need to know when they embark on DevOps transformation?
+
+
I would like the attendees to take this away from my presentation:
+
+
1) Understand what challenges development teams face during the transition to DevOps.
+2) What developers need to know when they embark on DevOps transformation.
Two core tenets of DevOps are culture and sharing. While devOps is
+proliferating through the tech industry there are still daily instances of
+exclusion, cruelty, and indifference. As an engineer, a husband, and a
+father I am in a constant struggle of trying to being inclusive without
+being intrusive.
+
+
An understanding of the robustness that diversity provides only complicates
+this matter further. Sometimes we have to work with people we don't prefer
+and sometimes we have to perform tasks we'd rather avoid. This should not
+prevent us from respecting each other, working together, and enjoying it
+too.
+
+
Please join me as we explore:
+
+
-The perceived threat of diversity
+-The actual strength diversity provides
+-Why diversity is good for business
+-Ways to increase diversity in your organization
Investors - like VCs and strategy planners inside companies - are starting to hear about DevOps and are curious how they might profit from it. This talk is a DevOpsDays version of what those investors want to know, explaing how they view emerging markets like DevOps and evaluate investment into the markets. It contains a "case" for evaluating investments in DevOps, covering the viablity of DevOps from their perspective and possible ways that "DevOps" could effect the models and valuations that investors are performing. The question being answered is: "should I invest in DevOps? Does that even make sense?"
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/DevOps in IBM Power System Testing/index.html b/exampleSite/static/events/2015-minneapolis/proposals/DevOps in IBM Power System Testing/index.html
new file mode 100644
index 000000000..624eba07d
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/DevOps in IBM Power System Testing/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+DevOps in IBM Power System Testing
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
In this presentation we are going to talk about how DevOps with Jenkins and Urban Code Deploy is used in verifying IBM Power Systems. Is it just the hardware we are testing? No. FSP, PHYP and HMC (Hardware Management Console) are being the major component and they all together makes IBM Power Server a whole product. So how are we going to test different components? How do they work together in achieving extended iterative development process beyond Continuous Integration and achieve Continuous Release, Continuous Delivery and Continuous Testing?
+
+
Is DevOps everything? Will it be sufficient to verify the IBM Power Systems? Obviously Not. There are different test teams. We will see how the quality products are delivered from DevOps to all other test teams.
+
+
We will also see how each team automated their component testing and how do they screen for defects in their respective subsystems using DevOps? And how effective was it? Was it worth moving to DevOps? What was the outcome? Did it improve the product quality ? Did it improve the feedback time to development?
+
+
How did the overall system test cycle improve? Did it improve really? What are the future plans? Let's wait and see.
In this ignite, a set of tweets from @petechesbot will be selected and presented. Pete Chesbot is the ultimate DevOps bot, distilling down the thought leadership of Pete Cheslock into much more consumable, and often more coherent, ideas. The presenter will explain the truth behind these constructed tweets, and we will all learn some deep insight into the "DevOps in the Machine".
Monitoring isn't just for ops people and application developers. Front-end developers need just as much visibility into their work as anyone else.
+
+
When thinking about the things we monitor with our configuration-managed monitoring pipelines, we rarely include the front-end development team or consider their needs from the outset. As the statistics that browser APIs can collect have become more robust, it is becoming easier to standardize the collection of WebPerf stats.
+
+
Inspired by the UK GDS team's event-store project, the team at Critical Mass created a Go program that can collects Navigation Timing API data, Javascript Error Reports, and CSP Reports. The application became the focus of one of our monitoring recipes, and has since become standard on any node serving web pages to end-users. Our front-end developers have developed drop-in javascript functions to interact with this service and thus made WebPerf monitoring relatively turnkey.
+
+
In this ignite, I'd like to talk about the conversations and brainstorming that lead to this initiative, about some of the mechanics of collecting the data, and how it has changed the way front-end developers relate to the production applications and monitoring dashboards used by the team. I plan to focus on the cultural aspects of the experience, but will also be able to share the architecture and code.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/Enabling DevOps Through End to End Performance Monitoring/index.html b/exampleSite/static/events/2015-minneapolis/proposals/Enabling DevOps Through End to End Performance Monitoring/index.html
new file mode 100644
index 000000000..e748760b0
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/Enabling DevOps Through End to End Performance Monitoring/index.html
@@ -0,0 +1,379 @@
+
+
+
+
+
+Enabling DevOps Through End to End Performance Monitoring
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Enabling DevOps Through End to End Performance Monitoring
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
A typical HTTP request lifecycle could be divided on three stages:
+
+
+
front end devices (browser, API, or mobile)
+
middle mile transport (CDN)
+
backend servers and services in a data center (or cloudified data center)
+
+
+
+
A request can span dozens of diverse systems and platforms, and with that, many monitoring tools controlled by diverse teams in development, operations, performance and QA. These teams cannot collaborate efficiently as they lack unified data, leaving each team with different limited understanding of what is really happening.With the full lifecycle of the request not well understood and teams operating in silos,its no wonder the end result is unnecessary finger pointing during troubleshooting efforts such as performance incidents.
+
+
For a DevOps team to be successful, they must see the big picture and know the answers to key questions such as:. Where to spend your resources to improve application performance?How to do root cause analysis for performance issues along the entire path?What metrics to use? Identify, in real time, what is and isn't working through the request flow? What your CDN is contributing to this picture? What out-of-your-control performance issues from systems such as mobile carriers or corporate gateways impact your site?
+
+
This talk will look at the tools available to monitor each stage of the request, and then examine how to unify this data into a single real time global view of the request lifecycle. During the presentation you will learn how unified monitoring of the request flow enables DevOps teams to see the big picture and collaborate using an unified set of metrics over a global dashboard.
Fear & Failure is a soft talk (with no technical content), discussing imposter syndrome, fear of failure, and how to combat them; I follow this up with a discussion on ways to cope with inevitable failure and benefit from it. This talk was inspired by one I saw at the Madison Ruby conference last year, "What Stuttering Taught Me About Marketing", which triggered a lot of self-reflection about why I let my fears hold me back personally and professionally.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/Good Bad and Ugly of devOps/index.html b/exampleSite/static/events/2015-minneapolis/proposals/Good Bad and Ugly of devOps/index.html
new file mode 100644
index 000000000..302f8daaa
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/Good Bad and Ugly of devOps/index.html
@@ -0,0 +1,365 @@
+
+
+
+
+
+Good, Bad and Ugly of devOps - A case study of cloud delivery pipeline
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Good, Bad and Ugly of devOps - A case study of cloud delivery pipeline
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+Continuous delivery in the cloud requires infrastructure that enables everyone to deliver "good" code any time. In order to build a delivery pipeline infrastructure which can throw bad code you need to build right cloud deployment tools and change management process. Essentially, there are three main stages of a pipeline - image baking stage, acceptance stage and production stage. Code should move through these stages with a trusted infrastructure which can validate for quality, resiliency and security. This talk will showcase real case study of successful cloud deployment pipeline developed by IBM Cloud data services team. I will also talk about some radical ideas of Runbook automation, monitoring and log analytics.
I'm a developer. I barely know what Nagios is, let alone how to set it up or configure new alerts. But I do know a lot about the application I'm working on, and I know how to code. By building a framework for easily adding new monitoring rules, the operations team at Swiftype has opened up application-level monitoring for the whole development team. I'll talk about the tools we wrote and explain how they allow developers to easily add new monitoring checks that probe our application (including web services, queues, and database) and alert the team by email, chat, or phone.
+
+
I'll show how to use the monitoring framework we wrote, but I'll also use this collaboration as a jumping off point to discuss how I think developers and operations can work together to build software faster and keep it reliable, based on our experiences at Swiftype.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/Home is the New Dev/index.html b/exampleSite/static/events/2015-minneapolis/proposals/Home is the New Dev/index.html
new file mode 100644
index 000000000..916e9178b
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/Home is the New Dev/index.html
@@ -0,0 +1,370 @@
+
+
+
+
+
+Home is the New Dev
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Running a homelab is a great way to keep your skills fresh and direct your career trajectory. It's easy to get bogged down by all of the work that you already have in your day job, but using the things you learn on the job and applying it in the form of a fun hobby extends your skillset and keeps you flexible when approaching problems in the real working world.
+
+
In your day job, it can be difficult to get new technologies implemented as there can be perceived risks such as lack of knowledge across your team, new tech not necessarily being fully proven, or just a general unwillingness to change. This does not have to be where the conversation around new technology ends. With effective projects in your home that model some of the ways that you wish your work environment was structured, you get to fully run through your implementation strategy across multiple arenas.
+
+
You become your own dev, ops, QA, and architecture team. You call the shots and get to see what the pain points will be for each and every one of these organizations. Additionally, you expand your skillset to more than just the niche areas you cover normally in your day to day work. Gaining this insight is invaluble and allows you to explore well outside of the normal bounds you would encounter typically in your day job. You make mistakes at home, take responsibility for them without fear or judgement and correct your path. You iterate, learn, develop and gain insight into how to approach problems all without needing any approval. Plus you get to have a little bit of fun doing it.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/How to Hire a Good DevOps Engineer/index.html b/exampleSite/static/events/2015-minneapolis/proposals/How to Hire a Good DevOps Engineer/index.html
new file mode 100644
index 000000000..8ba3c040f
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/How to Hire a Good DevOps Engineer/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+How to Hire a Good DevOps Engineer
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
There's a good and a bad side to any role in any industry and devOps is no different. Hiring to help ensure quality and optimize workflows is not anything new but the discipline has changed a lot over the years. We'll cover the history, evolution, and some experiences of this profession that will not only help find homes for wayward DevOps Engineers but empower them to have the desired effect too.
DevOps can optimize any process that results in an artifact by applying lessons learned from manufacturing and agile software development. Unfortunately not many people firmly understand how either industry works, never mind both of them. Come learn how using a cookie company as a model for devOps provides an example that anyone can grasp.
+
+
When dealing with a new concept it's often convenient to have a base case example to fall back to for reference. In this presentation you'll learn how to teach devOps with cookies by working as a group to apply devOps models like CALMS, ICE, and the Three Ways to our cookie company as that base case reference. Not only are cookies and the baking process a good instructional aid for explaining devOps methodologies and concepts, but the snacks encourage the collaboration needed to work through difficult conversations and problems as well.
+
+
-Why We Use Cookies and Not Gravel
+
+
-Applying Different DevOps Models
+
+
-How to Use Simple Descriptive Statistics
+
+
-How to Use Simple Predictive Statistics
+
+
-How to Manage what Drives Business Prioritization
+
+
-Optimizing Hand Offs and Transitions
+
+
-Defining a Thin Line Between a POC and a MVP
+
+
By the end of the presentation you should be able to form an actionable devOps game plan with a clear next step.
+
+
Attendees will need:
+
+
An network capable device, preferably a phone or a tablet
+
+
A problematic process or concept they're looking to establish or improve with the help of devOps
The promise of technology, and of automation particularly, is that they can free people to do the things that people excel at by assuming the rote, repetitive tasks that are better suited to machines. That promise has largely gone unfulfilled, as the demands and structure of the modern workplace have instead compelled people to behave more like machines than like people: consider the assembly-line worker, the sysadmin on call, the siloed teams accepting input from and providing output to one another. Too often, technological work diminishes the humanity of those who do the work. One of the most exciting aspects of the DevOps movement is its power to affirm that humanity.
+
+
This talk will focus on the potential of DevOps principles and practices to create environments where technology enriches not only organizations, but also the lives of their people.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/If you want to have an impact/index.html b/exampleSite/static/events/2015-minneapolis/proposals/If you want to have an impact/index.html
new file mode 100644
index 000000000..e32d60c60
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/If you want to have an impact/index.html
@@ -0,0 +1,368 @@
+
+
+
+
+
+If you want to have an impact
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract: DevOps is just one part of a bucket of "trends" you hear about in every keynote, the riders of the digital apocalypse. You've heard these talks: Software is eating the world! Cloud! Millennials! Mobile! DevOps! Change or die! You must buy our products! These trends are cast out as imperatives with little analysis of what they mean and if they're real. This talk looks at those keynote cliches and answers the question, "do I really need to do anything about them?"
I hate computers. How many times have you heard those words? Or said them yourself. Systems crash and go boom all the time. The easiest thing to do is to blame the person touching the keyboard when it happens. Especially when that person touching the keyboard is you. But how do we build safer systems? How do we build humane systems, systems that actually engage and even delight the user? Sidney Dekker says "Safety improvements come from organizations monitoring the gap between procedures and practice". How can you build a system for safety if the way the system is designed isn't actually how it's used. Of course it doesn't work, you were doing it wrong. We have to stop shoving users into systems with procedures that aren't based on reality.
+
+
In this talk I address these questions through my experience building tools for developers. Every tool works in an ideal world and on my machine. But the hard part is building tools that "work" even when they don't. Understanding the gap between procedure and practice can be a real challenge, and if you don't approach that problem with a big dose of empathy you won't have much luck closing that gap.
"Once upon a time": powerful words that begin many oral narratives and indicate that the story to be told will be imbued with magic and myth. Organizational folklore can be a very powerful force for instilling or perpetuating behavior, systems, and culture within an organization.
+
+
Too often, fear and negativity are the driving forces in the folklore behind many organizational traditions. A positive narrative that embraces the customs and traditions of a healthy, balanced feedback loop can help jumpstart your DevOps journey. This talk will help you frame your narrative alongside metrics and use folklore as a catalyst for positive change.
It's information overload these days -- how can a technology professional manage to keep up with everything that is new and exciting in the world of DevOps? What are the best methods for absorbing content and developing skills? Just how useful are podcasts, anyway?
+
+
In this talk (inspired by an episode of my [Podcast Name] podcast) I will share strategies for consuming information about techniques, concepts, and stories about DevOps. I will include practical methods for acquiring information, managing intake of blogs, articles, and studies, and absorbing and synthesizing this information in an applicable way.
As organizations move towards implementing DevOps related concepts one of the building blocks is typically a Continuous Integration and Continuous Delivery pipeline. Traditional processes revolve around simple functional tests with Boolean pass/fail and do not encompass non-functional elements. This can result in more rollbacks as code is deployed that may be functionally sound but unstable or non-performant.
+
+
In this talk we will show you how to automatically capture and report on key performance and scalability metrics (such as # of SQL Queries, time spent in components, # of resources on a page) through every stage of your deployment pipeline.
+
+
Tracking these metrics across all stages and comparing them between builds will help ensure higher quality releases and ensure something like a database killing bug does not make it all the way into production!
+
+
Less time spent rolling back suboptimal releases means more time spent delivering new features and happier customers.
Dive into the theories behind a system of profound knowledge, how one can build positive interactions, develop and understand flow and see the very foundations of what we call devops. I would talk about how to think through reliability, systems and human interactions and show how wrapping all of this together gives people the power to probe, sense, act and respond and managers & employees the tools they need to build a system of profound knowledge. This knowledge can then be codified, iterated and experimented with and the process of human management can be closely aligned with systems management to make both flexible and aware of each others requirements and easily communicated.
I love sports and my Dad loves programming. Our compromise is learning statistics with computers. In this presentation I will share what I learned about statistics working with all sorts of sports data.
Rolling Your Own vs SaaS: Tradeoffs & Considerations
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Description
+
+
At Bloom Health, we're operating in a highly regulated environment (including HIPAA & PII) while at the same time running our infrastructure in public cloud. This leads to a number of considerations and tradeoffs when choosing the various parts of our stack. I'll detail the considerations we've undertaken, the compromises and winding paths towards workable solutions, and the specific technologies we've found work better for us as in-house solutions versus those where we've found SaaS to be the optimal (or at least acceptable) choice.
Saved or Sabotaged? Seven Deadly Wastes in Your DevOps Practice
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Every software development organization on the planet has a software supply chain that is consuming a massive volume of open source and third-party components at extremely high velocity. To provide a much clearer perspective to this volume and velocity, we can see that a global population more than 11 million developers consumed over 20 billion components in 2014.
+
+
Those in DevOps who have pursued improved visibility, supplier choices, and control mechanisms across their software supply chains have boosted developer productivity by 15%, crumbled mountains of technical debt, and shifted millions of dollars from sustaining operations to accelerating innovation.
+
+
Yet the vast majority of organizations developing software are blind to their free-for-all consumption volume, patterns, and velocity. Their software supply chain practices are silently sabotaging efforts to accelerate development, improve efficiency and maintain quality.
+
+
In May, I authored the 2015 State of the Software Supply Chain Report. It is a quantitative analysis of more than 160,000 software development organizations consuming billions of open source and third-party software components from over 15,000 suppliers. Your organization is most likely among those I analyzed.
+
+
While the average organization in the study consumed 240,000 open source and third party software components in 2014, the study revealed evidence of seven deadly wastes in their operations: (1) inefficient software sourcing practices, (2) building in outdated software components, (3) using redundant software components, (4) bypassing quality control mechanisms, (5) extending build times, (6) limiting traceability, and (7) electively sourcing software with known security vulnerabilities or risky license types that result in unplanned rework.
+
+
These practices have resulted in:
+
+
An average of 27 versions of software components consumed, meaning development teams are electively building in outdated parts and creating mountains of technical debt
+
+
An average of 15,337 components consumed included known security flaws, impacting the integrity of operations
+
+
Over 30 days of build time wasted annually as a result of poor sourcing practices
+
+
But this discussion is not intended to simply shed light on bad practices, it is about learning. Attendees will gain new visibility as to what’s happening in their own software supply chains, how to avoid the seven deadly wastes, and how leading organizations like eBay, ServiceNow, Blackboard, Aetna, the US Air Force, Federal Reserve and Department of Homeland Security are applying proven supply chain principles from other industries toward improving their DevOps practices.
It's time to bring golden images to the new age of automation. Using new tools, it is possible to automatically create golden images on top of configuration management best practices. Not only is this possible for a single platform, but for multiple platforms (AWS, VMware, OpenStack, etc.) all at the same time. Unlock new potential, increase organizational agility, and improve system stability.
+
+
Abstract
+
+
Golden images have been thrown to wayside in the past few years in favor of using configuration management tools on top of clean OS installations. Historically, golden images have been tedious to maintain, slow to create, and represented archaic operations practices.
+
+
But golden images also offer a variety of benefits. Instead of waiting 10 to 30 minutes for configuration management to complete on a new server, you can have a new server up and running in seconds. You can comprehensively test golden images before deploying them to production and confidently know that production will have stable configurations. Instead of manually building development environments, you can give developers golden image virtual machines, getting their development environments up and running in seconds. The list goes on.
+
+
It is time to bring golden images to the new age of automation. Using new tools, it is possible to automatically create golden images built on top of configuration management best practices. And not only is this possible for a single platform, but for multiple platforms (AWS, VMware, OpenStack, etc.) all at the same time. Generate development images for VMware identical to production images that run in AWS. And do it all quickly, automatically, and using pre-existing configuration management scripts.
+It's time to shed the social stigma against golden images, because these are completely different, adopt modern operations best practices, embrace DevOps culture, improve agility of your operations organization, and are really, really cool.
Simplifying Cloud Template Management Using Packer
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
While installing OpenStack or CloudStack is a fairly simple prospect, the promise of cloud efficiency comes from a viable template
+management process. Creating the first template, or attempting to migrate existing VMs into that new cloud can be quite problematic. In this session we'll learn how Packer plugins can be used to both create that initial set of templates, and to clone existing VMs into the cloud. When cloning existing VMs, a process will be presented where users aren't impacted when migrating existing functionality to a cloud.
This session would focus on how testing changes in an agile DevOps world.Discussion points would include:
+
+
What is the best combination of white box, grey box, and black box testing?
+ Should there be separate test teams and what testing should they own?
+ Is there still a concept of System Test in an Agile DevOps world?
+If so, how does it change? When and how should Accessibility, Usability, and Performance testing be done?
+ How does customer usage (A/B testing or Beta testing) fit into the Agile DevOps world?
+
+
I would provide the following to start the discussion:
+ Generally accepted definitions of white box, grey box, and black box testing
+ Working models of agile testing in a DevOps world (a couple of views that can be discussed)
+ Breakdown of what is typically done during System Test so we can discuss what is still needed
+ Breakdown of the other type of testing (Accessibility, Usability, Performance, and so on) so we can discuss when and how this should be done
Although not officially coined until 2009, DevOps ideals have been explicitly discussed since at least 2006. Recently, however, the term "DevOps" has gained increasing popularity across a variety of fields and industries. DevOps is not a development methodology or technology; DevOps is an ideology. It is a way to facilitate organizational prosperity and growth while increasing each individual employee's happiness along the way. As DevOps has gained in prominence, a gap has been created between the original definition of DevOps and this new "enterprise-ready" buzzword. I present to you the 10 Myths of DevOps!
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/The Five Love Languages of DevOps/index.html b/exampleSite/static/events/2015-minneapolis/proposals/The Five Love Languages of DevOps/index.html
new file mode 100644
index 000000000..2106a2b00
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/The Five Love Languages of DevOps/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+The Five Love Languages of DevOps
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The title of this session is inspired by the self-help book The Five Love Languages by Gary Chapman, but the similarities end there. When we are working to bring about cultural change in our organization, it's essential for us to understand that not everyone speaks the same "language" of DevOps as we do. The CFO has different drivers and communication style than your friend in the QA department, who is still different than the DBA in that remote office. In this talk, I will work to help provide techniques and strategies for identifying the drivers of your peers and decision-makers. We will talk about beliefs, perceptions, and communication styles, all with the express intent of helping YOU drive home the value of the DevOps philosophies and work-practices to make your organization succeed!
+
+
Content will include a discussion of the DiSC model, as well as discerning drivers for different individuals to adjust the conversation.
+
+
The DiSC model provides a common language that people can use to better understand themselves and to adapt their behaviors with others. The four areas of DiSC are Dominance, Influence, Steadiness, and Conscientiousness.
+
+
Approximately 25% of the talk will be background on DiSC and methods for identifying the communication styles of others. 25% will be based upon identifying drivers of example roles in an organization (finance, product, tech ops, etc), and the remaining will be focused on use cases and strategies for applying this skill towards organizational change.
we talk about DevOps as a process of dissolving organizational silos. We also focus a lot on automation. Both of these activities require a lot of time and energy. Are they absolutely necessary prerequisites? Can we do DevOps across silos, or even across company boundaries? What is the 'Hello, World' of DevOps? Is it possible to do anything useful without significant investment in organizational redesign and system retooling?
+
+
This talk will tackle this question in simple, concrete terms by presenting a DevOps transformation case study from 2004. This case study involves a highly dysfunctional relationship between a SaaS provider and its outsourced hosting vendor. It describes the simple transformation that repaired that relationship, and allowed the client to dramatically increase the quality of their service as well as their satisfaction with their vendor.
+
+
The talk will conclude by describing precisely what it was about the repair process that led to success. It will illustrate the difference between healthy and dysfunctional inter-organizational relationships. It will explore ways that any IT organization, regardless of its structure, can begin to reap the benefits of DevOps.
We spent a lot of time over the last decade talking about teams, stories, and WIP. We laid the groundwork for a big change in the way software is developed. Now is the time to change the conversation – from process to technology. We agree that we must dramatically shorten the feedback loop from idea to outcome – but how?
+
+
It’s time to focus on the tools and techniques that make it possible for small teams to deploy small changes to large systems very rapidly and very safely. Consider architecture: we are learning how to break monolithic systems into micro services – small, independently deployable components. Look at packaging: we now have standard containers that move freely across environments. Examine reliability: contract tests have proven effective at isolating the impact of component changes.
+
+
In the end the important question is: How long does it take you to deploy a single line a code, learn something useful, and act on the information?
DevOps is growing in popularity and even usage in "the real world." It seems like we're slowly getting past unicorns only and seeing many "horses" do DevOps. Soon we'll see the mainstream market - the "donkeys" - start to pick it up and bend DevOps to its will. This talk will go over "the state of the union" of DevOps and provide some guidance for how to prepare for the donkey apocalypse.
They Don't Call it Continuous Integration for Nothing!
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
This talk will dig deep into the process of continuous integration (CI) and the key processes that make up the overall CI process. We will discuss the relationships and process flows between change management, configuration management, and release/build management and how the CI process, when coupled with a solid performance engineering discipline across the product lifecycle, can result in a better user experience for your web & mobile application. We will speak about the entire lifecycle, the "conveyor belt" of the application lifecycle, with concentration on the "Big 3" processes that support the overall CI strategy.
+We will include a real-world example of how SOASTA uses Jenkins and other open source solutions for its "conveyor belt" and how this process enables SOASTA to complete over 100 product releases in 2014 and still maintain its customer SLA's for its Saas product offerings.
With learning and empathy being critical tenets of a healthy DevOps environment, you need to be vulnerable. Being vulnerable allows you to show that you are not perfect, and the rest of your team will feel safe to share successes and failures more freely. This attitude needs to flow to your whole life.
Why orchestration tools should understand your app
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Configuration management tools have made it possible to manage complex distributed applications. Their power can be further enhanced with a model of the application architecture. Benefits of a model based tool include ease of use, increased safety, consistency of what is managed, rich functionality, and many more we will discuss during this session. We will walk you through how we manage a large-scale, distributed system in AWS using a single, model-based tool.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2015-minneapolis/proposals/Why you should care about DevOps in the public sector/index.html b/exampleSite/static/events/2015-minneapolis/proposals/Why you should care about DevOps in the public sector/index.html
new file mode 100644
index 000000000..a49f7aff9
--- /dev/null
+++ b/exampleSite/static/events/2015-minneapolis/proposals/Why you should care about DevOps in the public sector/index.html
@@ -0,0 +1,381 @@
+
+
+
+
+
+Why you should care about DevOps in the public sector
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Why you should care about DevOps in the public sector
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
The IT community in the public sector has a sizeable, but frequently forgotten influence on peoples lives. Have you tried to renew a license plate online recently? How about navigated https://www.healthcare.gov/ to get health insurance? Used online learning tools for a public educational institution? Have any of these experiences been pleasant, or what you would expect from a well run modern website? These websites are your tax dollars at work.
+Are there reasons why we maybe aren't seeing the cultural ideas of DevOps reaching public sector IT shops as quickly?
+
+
Public sector organizations differ greatly from private sector organizations with regards to structure, motivations and funding. Other factors such as government mandates for the existence of these organizations, tenured employees and reliance on antiquated domain specific applications can exacerbate the issues caused by these differences.
+
+
In the past year or so, we've seen how the discussions around DevOps in enterprise organizations have opened up discussion of many of these cultural ideas to more traditional corporate settings. For DevOps ideas to gain influence the thousands of public sector IT workers, we need to recognize that they too have a separate subset of problems and challenges and start a conversation about how to tackle these issues. This talk will seek to begin that conversation, explain some of the cultural differences between the public and private sectors, explain some of the challenges the public sector faces when trying to break down silos and explain why and how we should evangelize to public sector employees.
Biz team wants revenue. Devs want key method call times. Ops want response times and throughput.
+
+
We ALL want metrics, but instrumenting, viewing and monitoring these metrics normally involves a stack of tools, tons of coordination and worries about overhead.
+
+
Until now.
+
+
Let's spend 5 minutes and explore StatsD, an open-sourced network daemon that listens, collects and aggregates statistics for backend services. We'll take a quick look at what StatsD can collect, what a typical StatsD stack looks like - and a little bit about how teams can leverage StatsD to instrument (all the things).
+
+
Walk away with a great head start on a technology you've heard a lot about - but haven't had the chance to explore.
As a developer, for years I wrote code in a graphical IDE on Windows or a Mac. I have written hundreds of thousands of lines likely to only click a button to compile, build, deploy locally or even push to repositories. Coming from the development side of the house I regularly feel like a fraud when working with the system. I have had this feeling before, since I didn't study computer science in school. I will cover techniques I used to ramp up quickly on system commands and string together my favorite commands to understand a system quickly. Even experienced system admins will likely get an interesting tidbit or 2.
Building an End to End Windows or Linux Application Deployment Pipeline
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
We would like to share our journey towards an OS Agnostic fully automated application deployment pipeline. Our proposal would take our audience through our trial and error, how we chose our tools, how we geared those tools, and were we are headed in the future. As a sample, we would cover things like; Arriving at the conclusion that most DevOps groups focus on a handful of programming languages specific to a single OS. In contrast, CareerBuilder has applications built on both Rails and .NET. Therefore we needed a solution that satisfies both sets of requirements. We also learned that not many examples exist for Windows based deployment pipelines leveraging .Net. Most examples are geared towards Linux and a language like Rails or Node.JS. Even with all available information, it is not easy to create a serviceable solution that supports all language and OS requirements within a single gitflow framework.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2016-atlanta/proposals/Developing and Operating an Enterprise Application as a 12Factor App using Docker and Amazon Web Services/index.html b/exampleSite/static/events/2016-atlanta/proposals/Developing and Operating an Enterprise Application as a 12Factor App using Docker and Amazon Web Services/index.html
new file mode 100644
index 000000000..604c34421
--- /dev/null
+++ b/exampleSite/static/events/2016-atlanta/proposals/Developing and Operating an Enterprise Application as a 12Factor App using Docker and Amazon Web Services/index.html
@@ -0,0 +1,400 @@
+
+
+
+
+
+Developing and Operating an Enterprise Application as a 12Factor App using Docker and Amazon Web Services
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Developing and Operating an Enterprise Application as a 12Factor App using Docker and Amazon Web Services
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
An application that follows the principles of the 12 Factor results in highly scalable, portable, disposable and manageable deployment. However, making a large scale enterprise or business application into a 12 Factor App is a non-trivial exercise. The technical aspects outlined below are keys to developing and operating a large scale enterprise application as a 12 Factor App:
+
+
· Componentization:
+
+
o How Spring Boot and microservices architecture could play a big role in breaking a larger monolithic application into finer grained components
+
+
o How these finer grained components could be developed, tested and versioned independently
+
+
o How Spring Cloud and Netflix libraries could be leveraged to build the plumbing around these microservices components that can provide the binding features such as service look ups, load balancing, graceful failure handling and dynamic routing of requests across these components
+
+
o What role unit testing and JUnit frameworks could play to ensure that the developed code is well tested before it reaches the version control system
+
+
· Containerization:
+
+
o How Docker could be leveraged to build, deliver and deploy the component images with consistent naming and versioning schemes.
+
+
o How containerization could help encapsulate the technology stack and application configuration nuances
+
+
o How containerization could help us optimize our applications for cross-platform deployments (cloud or on-premise)
+
+
· Continuous Integration:
+
+
o How a Continuous Integration and Continuous Delivery platform can be built for thoroughly testing microservices components
+
+
o Frequency and scheduling of different phases of testing and verification (functional, performance, upgradability and user acceptance) before code can be promoted to staging and production environments
+
+
o How CI/CD platform can help developers find the defects in minutes after development
+
+
· Cloud Runtime:
+
+
o How Amazon Cloud Formation and EC2 Container Service (ECS) can be leveraged to run, scale and manage microservice components on EC2
+
+
o How to enable frequent, independent and zero-downtime upgrades of the deployed components
+
+
o How to keep the application source-code completely agnostic of the underlying cloud platform such as AWS
+
+
My presentation/talk would primarily focus on these four topics and will discuss how an organization can manage getting the developers and deployment engineers work in unison to create a consistent environment for development, testing and production.
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2016-atlanta/proposals/Dont hit it with a pretty stick LeanUX Methods for Agile Teams/index.html b/exampleSite/static/events/2016-atlanta/proposals/Dont hit it with a pretty stick LeanUX Methods for Agile Teams/index.html
new file mode 100644
index 000000000..4a0b9c61e
--- /dev/null
+++ b/exampleSite/static/events/2016-atlanta/proposals/Dont hit it with a pretty stick LeanUX Methods for Agile Teams/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+Don’t hit it with a pretty stick: LeanUX Methods for Agile Teams
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Don’t hit it with a pretty stick: LeanUX Methods for Agile Teams
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
UX is seen as a bottleneck and/or creates lots of rework for Agile teams. I’ll discuss how you can incorporate LeanUX principles within your Agile teams to enable collaboration and continuous learning about your product.
+
+
I’ll discuss sharing the design process with the entire team, covering the basics of customer research, interviewing, and how to create lean personas for hypothesis validation.
Code reviews, stand up, retros, and performance reviews — all acknowledge the importance of communication and feedback and they are good starts. But they don’t tell you how to give negative feedback or ensure that you, as a teammate or manager, hear the small things before they become big things.
+
+
Let’s talk about feedback and examine frameworks for how to ask for and frame feedback effectively. Not all situations call for the same type of feedback and some are more sensitive than others. We will look at Non-violent communication, techniques from family and marriage therapy, as well as more traditional frameworks for feedback.
From 0 to Hero: CareerBuilder DevOps Deployment Pipeline
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
We would like to share our journey towards an OS Agnostic fully automated application deployment pipeline. Our proposal would take our audience through our trial and error, how we chose our tools, how we geared those tools, and were we are headed in the future. As a sample, we would cover things like; Arriving at the conclusion that most DevOps groups focus on a handful of programming languages specific to a single OS. In contrast, CareerBuilder has applications built on both Rails and .NET. Therefore we needed a solution that satisfies both sets of requirements. We also learned that not many examples exist for Windows based deployment pipelines leveraging .Net. Most examples are geared towards Linux and a language like Rails or Node.JS. Even with all available information, it is not easy to create a serviceable solution that supports all language and OS requirements within a single gitflow framework.
Conway’s Law expresses Melvin Conway’s observation that we are doomed to design systems that mirror the shapes of our organizations. Forward-thinking companies like Amazon and Netflix use Conway’s Law to their advantage. They structure their organizations to reflect the kinds of systems they want to create by matching microservices architectures with so-called “2-pizza” micro-teams.
+
+
Conway also, though, observed that designing a system is just the beginning; it also needs continual redesign. He stressed the importance of organizational flexibility to effective design. How can we achieve this flexibility without descending into re-org madness?
+
+
This talk will explore the relationship between organizations and systems. It will delve more deeply into Conway’s original article, and introduce ‘Conway’s Corollary’. By connecting Conway’s work to ideas from service design and Promise Theory, it will present an approach that treats the design and operations of systems and organizations as continuous and inseparable.
In today's world, a company must be a "Learning Organization" in order to be successful and innovative. Learning from both failure and success, in order to implement small incremental improvements is critical. But until you implement and apply new information, you haven't truly "learned” anything and you certainly haven’t improved.
+
+
According to the 2015 Monitoring Survey, most companies leverage metrics from monitoring and logging purely for performance analytics and trending. If high availability and reliability are important, they also leverage metrics to alert on fault and anomaly detection. Despite these “best practices”, the metrics are primarily only used as context to keep things “running” or return them back to "normal" if there’s a problem. Rarely is that data used as a method to identify areas of improvement once services have been restored.
+When an outage occurs to your system, you will absolutely repair and restore services as best you know how, but are you paying attention to the data from the recovery efforts? What were operators seeing during diagnosis and remediation? What were their actions? What was going on with everyone, including conversations? A step-by-step replay of exactly what took place during that outage.
+
+
This “old-view” perspective on the purpose of monitoring, logging, and alerting leaves the full value of metrics unrealized. It fails to address what’s important to the overall business objective and it lacks any hope of seeking out innovation or disruption of the status quo.
+
+
This talk will illustrate how to identify if your company is making the best use of metrics and ways to not only learn from failure, but to become a "Learning Company".
+
+
+
+
+
+
+
+
+
diff --git a/exampleSite/static/events/2016-atlanta/proposals/The test automation journey a labor of love and where are we now/index.html b/exampleSite/static/events/2016-atlanta/proposals/The test automation journey a labor of love and where are we now/index.html
new file mode 100644
index 000000000..aa2e17af2
--- /dev/null
+++ b/exampleSite/static/events/2016-atlanta/proposals/The test automation journey a labor of love and where are we now/index.html
@@ -0,0 +1,365 @@
+
+
+
+
+
+The test automation journey; a labor of love and where are we now?
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The test automation journey; a labor of love and where are we now?
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Test automation has long existed at Autotrader. In 2001, QA was using WinRunner. Along the way we've used, LoadRunner, JUnit and HTTPUnit, Selenium, WatiN, QTP, RFT, and A3, Today the foundation of test automation at Autotrader is TestNG, Selenium-WebDriver (Java client), Selenium Grid, BrowserStack, Jenkins, JIRA, and Xenon, an in house test results management tool.
+The presentation will include a brief history of test automation at Autotrader.com from 2001 through 2016, the current state of test automation, our future direction and how test automation plays into the vision of continuous delivery going forward.
+
+
Speaker:
+Lee Blackburn, Chue Her, & Adrian Kosciak
Many teams and organisations say that they are pacticing Devops successfully, yet when we look there are big differences in organizational structure, team composition and culture. Broadly speaking, we can identify to main "styles" of Devops at present: "single-team Devops" and "two-team DevOps". We'll describe the two styles, benefits and disadvantages of both, and discuss how you can figure out which might be a better fit for your team and organization.
Over the past few years, there seems to have been an increase in suicides in our sector of the IT industry. With complexity and responsibility ever increasing in the creation and support of digital services industries, we have seen a correlated increase in stress levels. We have come to know this as a term we call “Burnout.” Burnout was coined by German-American psychologist Herbert Freudenberger in 1974. The Japanese have a word for burnout that leads to death -- "karoshi." When suicide is involved they call it "karojisatsu." In this presentation, we are going to break down what we know about Burnout. We will look at some survey data and try to suggest some ways to achieve healthier outcomes for ourselves and our colleagues.
Why DevOps toolchain fails? we are going to showcase devops implementation with speed and correctness which helps in understanding that in agile CI/CD was designed before DevOps revolution happened to the world. we are going to add a fourth question to daily scrum to make it "Agile for DevOps". This best practice has brought down the devops toolchain Ops quality gate failures down by 75%! for fortune 500 companies.
+So want to describe this journey of experience with devops implementations and the complexity involvement for DevOps.
+
+
Speaker:
+
+
Uchit is an IT industry veteran, Cloud technologist at heart and a hands-on Automation/DevOps Consultant at Opex Software. Through his speaking, writing and analysis, he helps businesses take advantage of the emerging technologies. Uchit loves to play Chess and Age of Empires that helps to clearly see the impact of ideas, research & automation empowering economies of IT.
+
+
Uchit works with large IT organizations to automate traditional datacenters flow, explores new-age tools and technologies, defines solutions and best practices for small and large enterprises. He worked at world-class product and service companies like SAP and Infosys, during which time he analyzed various cloud platforms, Big Data, Infrastructure Automation, Containers, DevOps and Continuous Delivery.
+
+
He has also published various books on Amazon cloud platform and Enterprise Service Bus named Mule ESB cookbook, AWS Development Essentials, Mastering AWS development, DynamoDB Applied Design Patterns and still counting.
Rapid innovation, changing business landscapes, and new IT demands force businesses to make changes quickly. The DevOps approach is a way to increase business agility through collaboration, communication, and integration across different teams in the IT organization.
+
+
In this presentation, you’ll learn about:
+
+
+
The acceleration of Application Delivery for the Business with DevOps
+
The transformation of IT to a DevOps, Microservices, and Container based Cloud Architecture
+including the use of a PaaS along with Docker, Google’s Kubernetes and Jenkins.
+
How DevOps practices can operate in a Platform-as-a-Service (PaaS)-enabled environment.
+
PaaS and DevOps, used together, can reduce software delivery cycle times, drive automation, and increase efficiency.
+
How other organizations are using DevOps and how to replicate their success
+
+
+
+
Speaker:
+
+
Chris Van Tuin, Chief Technologist for the Western US at Red Hat, has over 20 years of experience in IT and Software. Since joining Red Hat in 2005, Chris has been architecting solutions for strategic customers and partners with a focus on emerging technologies including IaaS, PaaS, and DevOps. He started his career at Intel in IT and Managed Hosting followed by leadership role˝s in services and sales engineering at Loudcloud and Linux startups. Chris holds a Bachelors of Electrical Engineering from Georgia Institute of Technology.
A modern approach to designing and verifying your infrastructure code policy with Chef, InSpec, and Docker
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
I’ll discuss a modern approach to design and verify Chef infrastructure code and policy using Chef’s new resource declaration style, InSpec, and containers. Chef’s fundamental building blocks are resources, not recipes, so why not create, consume, and verify those? This modern approach allows you to rapidly and effectively verify your glorious and perfect infrastructure code.
+
+
Speaker:
+
+
Kevin Dickerson is a former sandwich artisan from Oakland, California. He’s written software for billions of years, and currently travels nationally for many many of Chef's fine customers with the Customer Success organization.
Continuous verification, provided by our beloved dev ops teams, is one of the cornerstones of modern development practices. However, many operationally oriented teams struggle with "eating their own dog food", and those strict practices falter in favour of agility and responsiveness to the product's needs.
+
+
Revision control, unit and functional testing, and staging-production workflows can be just as important to apply to operational systems as to the product itself. As a dev ops team that has been rapidly growing in number of consumers, automation scale, and breadth of technology, we would never have survived without investing in the application of our own CM practices to the services we provide.
+
+
At Electronic Arts, we have employed a number of automation technologies in the past few years. From in-house CI engines, to various enterprise solutions, and finally to Jenkins, the unique features and architecture of each stack necessitated a similarly unique approach to managing its configuration.
+
+
In this talk, we aim to share these experiences in automation configuration, and the practices therein. We will discuss the pros and cons of various approaches, lessons we learned, and future plans we aspire to.
+
+
Speaker:
+
+
Sean Sutherland comes from a future where poor dev ops practices has led to the grim downfall of humanity. Sean has traveled to this time with the hopes of securing a brighter, more stable future for us all.
Being an introvert and at a conference, not as hellish as you think it is
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
I'd like to give some advice on how to deal with conferences as an introvert.
+Over the last couple years I've grown and learned to engage with the tech community in ways that an introvert would find challenging. This talk will hopefully help the audience avoid some of the landmines that I have stepped on.
+
+
I want to help out my fellow introverts to realize that it's OK to be an introvert at big conferences. We can enjoy them too.
In this talk, I will show how any organization can build a two pizza teams like how Amazon is doing it. I will show Microservices, Containers and DevOps as the perfect trifecta for two pizza teams and then talk about the key ingredients to building successful two pizza team. The ingredients include repeatable and portable pipeline automation, continuous insights, choice of tools and platform. At the end of the talk, any organization (whether it is a startup or an enterprise) will understand what Jeff Bezos meant when he proposed Two Pizza Team as the recipe for innovation at Amazon. With some help, they may be able to implement it in their organization.
+
+
Speaker:
+
+
Krish Subramanian is SVP of Products and Strategy at CloudMunch overseeing Products, Go To Market Strategy and Business Execution. Prior to joining CloudMunch, Krish was Director for OpenShift Strategy at Red Hat. In the past, he used to be an industry analyst focussed on Cloud Services. He is a strong advocate of Enterprise Digital transformation using Modern Enterprise Model
Uninterrupted online gameplay is critical to the success of popular gaming franchises such as Call of Duty. Call of Duty and other titles rely on Demonware for backend services such as matchmaking, event logging, leader boards and many many others. Ensuring that all the services are available and have predictable low latency response time is essential for creating a great gaming experience from day zero. This is especially challenging given that the backend services see a very rapid traffic increase from tens to millions of concurrent users within days.
+
+
DW performs capacity planning at multiple stages of the service lifecycle, from design to deployment. It is done to ensure that services and data centers are provisioned sufficiently for launch, yet have a financially sound hardware footprint.
+
+
The presentation will cover the capacity planning process, as well as tools and methods used at Demonware.
+
+
The first part of the talk will focus on capacity planning at various phases of the lifetime of a service, and on the importance of load testing and benchmarking.
+
+
The second part will cover key metrics gathering, processing and transformation of data into information suitable for decision making. A special focus will be given to doing capacity planning for large MySQL deployments, and web services.
+
+
The third part will be dedicated to discussing Demonware’s capacity planning BI. BI aggregates processed metric data with metadata on data centers and services and allows answering high level capacity related questions.
+
+
Speaker:
+
+
Dmytro Dyachuk
+
+
Dmytro Dyachuk has been a capacity planning engineer at Demonware, a subsidiary of Activision-Blizzard, for more than four years. He took part in launching Call of Duty, Guitar Hero and Spyro titles.
+
+
Max Eisenbraun
+
+
Max Eisenbraun joined Demonware last year and also took part in launching Call of Duty, Guitar Hero and Spyro titles
Collective action is a wonderful thing. Meetups and open source projects are two examples of people getting together to have a conversation about the things they care about, with the aim to do something positive for themselves and their community. How can this collective action happen inside your organization? At Hootsuite, the answer is Guilds.
+
+
Guilds are a self-organizing group of people with common interests. It is a natural forum for social interactions that build relationships that, in turn, promote cooperation, cohesion, and productivity.
+
+
Guilds provide a horizontal communication layer across our Product Engineering teams. Our engineers, testers, and other staff use them to set their own missions, to establish technical roadmaps, to take on joint tasks for their grassroots initiatives, and to promote education through experiential learning. This collective action benefits their members, their craft, and our organization.
Consul for QA - integration testing a monitoring tool by simulating distributed systems.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Consul has been winning devops mindshare and establishing itself in production deployments. I will explore a less conventional use of this popular service discovery tool for a specific QA use case and discuss problems and successes of this approach.
+
+
We decide to build a means of extracting system architecture information from the performance monitoring data we collect in order to generate a structural overview of the components of a distributed system.
+
+
And we need to test it end to end. Build and deploy a wide variety of live distributed systems, capture enough data to infer the structure of the application, compare the inferred structure to the actual designed structure.
+
+
Use a service discovery tool to wire canned apps together using test fixture data, making test system configuration fast and repeatable.
+
+
Enter Consul:
+
+
… hard work and thinking ...
+
+
Speaker:
+
+
Reformed mainframe hacker who loves all things web with a penchant for breaking stuff.
CI is a well-known and popular methodology, which is supposed to help software projects to stabilize their source code and make the entire development more predictable and surprise-free. Even though all this sounds very good in theory, the practice is different. in many companies I’ve been consulting with, the situation is very similar - continuous integration is causing troubles if being aggressively enforced. There is a very logical reason for that, which I will discuss at the session and will suggest a vendor-neutral solution.
+
+
Speaker:
+
+
Yegor is a CTO and co-founder of Teamed.io, a software development company with a unique approach to management of distributed teams; a regular blogger at www.yegor256.com; a proud holder of PMP and OCMEA certifications; a hands-on Java developer and a lead architect of a few popular open source projects, including jcabi.com, takes.org, rultor.com and qulice.com. Yegor lives in Palo Alto, CA and Kyiv, Ukraine.
Mobify has access to and a great interest in copious quantities of end-user data regarding shopping behaviour and global network performance (see: DevOps Days '15 talk RE CDN performance). We're scaling up to do be able to churn more data and analyze it in new and interesting ways, all with a path of least resistance to keep things simple and easy for our data science teams to jump and use the tools. This talk will be a quick recap of the stack choices we've used at every stage of the pipeline, and take a look at how path dependency and "MVP" dev practices shape our final solutions.
+
+
Speaker:
+
+
Kyle Young @ksgyoung is Mobify's System Engineer, where he has spent the last three years championing DevOps, and building the backend systems and infrastructure that keep things humming. He is also Quidditch Captain.
DevOps Meets Containers: Application Centricity and Continuous Insights
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
DevOps is the most abused term in the industry today with lots of end user confusion driven by purists focus on culture and vendor marketing of their tools. Most of the discussion around DevOps centers on infrastructure automation or application lifecycle automation or about the underlying deployment infrastructure/platform. While these tools are critical to deriving DevOps benefits, there is still confusion about how exactly DevOps is helping organizations. In this talk, we will propose an approach to effective DevOps by focussing on the continuous feedback loop as a critical factor in enabling better and faster software delivery.
+
+
As we move into a world of Microservices and containers, traditional DevOps approach becomes more fragmented. An application centric approach to delivery pipelines offers reliable and repeatable automation, leading to real business value. The standard unit of infrastructure automation may have changed from VMs to containers, taking an application centric approach to operations, monitoring and security ensures complete control while allowing rapid innovation. In this talk, we will talk about the value of taking an application centric approach to DevOps automation.
+
+
The key element in DevOps is the feedback loop but most of the discussions include feedback as an after thought by putting the focus on culture and tools. In this talk, we will argue that feedback through continuous insights is critical component of DevOps and show how it helps deliver better quality software faster.
+
+
Speaker:
+
+
Krish Subramanian is SVP of Products and Strategy at CloudMunch overseeing Products, Go To Market Strategy and Business Execution. Prior to joining CloudMunch, Krish was Director for OpenShift Strategy at Red Hat. In the past, he used to be an industry analyst focussed on Cloud Services. He is a strong advocate of Enterprise Digital transformation using Modern Enterprise Model
Your boss has asked you to do DevOps? No surprise as the term DevOps has become a trendy word. DevOps however is more than just Devs and Ops working together. It is not something you can buy with your credit card. The efficiencies the process provides on behalf of a supported organization can yield increased productivity between IT Professionals, Developers and Business Decision Makers.
+
+
Yes… But where I'm supposed to start ??? What will be my learning path ? How I can involve people ?
+
+
Come to this sessions to share together our success stories and help you start your strategy.
+You can also come and share about your success or not experiences.
+This session will be interactive and will require your creativity to be successful.
+
+
Speaker:
+
+
Julien Stroheker is a Technical Evangelist at Microsoft.
Remember the times when one server was enough? And a guy named “sysadmin” was babysitting it along with his other duties of installing MS Office for everybody?
+
+
For better or for worse, those times are long gone. Today, companies manage tens of thousands of servers and perform thousands of production changes per day.
+
+
In this talk we will look at the resources, techniques and tools needed for managing DevOps at Scale and we will discuss the challenges that companies encounter when they hit it.
+
+
Speaker:
+
+
Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate of JFrog, the home of Artifactory - the Universal Artifact Repository, and Bintray - the Universal Distribution Hub.
+
+
For a living he hangs out with the JFrog tech leaders, writes some code around Artifactory and Bintray, and then speaks and blogs about all that. He does it repeatedly for the last dozen of years and enjoys every moment of it.
Docker Container Lifecycles – Problem or Opportunity?
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production?
+We will demonstrate how to implement a promotion model for docker images, and then show how to distribute them to any kind of consumer, being it a customer or a data center.
+
+
Speaker:
+
+
Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate of JFrog, the home of Artifactory - the Universal Artifact Repository, and Bintray - the Universal Distribution Hub.
+
+
For a living he hangs out with the JFrog tech leaders, writes some code around Artifactory and Bintray, and then speaks and blogs about all that. He does it repeatedly for the last dozen of years and enjoys every moment of it.
Docker Provides Convenience with Hidden Complexity - How Can We Cope?
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Using a container as the new unit of deployment greatly simplifies things on the surface. You no longer have your application and all the components in it. You don’t need to worry about the runtime environment. Or the operating system? It is all there. You just have the containers. But hold on. Think again. Things are a lot easier to manage - but you still have all those parts. You still have an operating system. And a runtime environment like e.g. a Java VM. And your application. It consists of a bunch of third party, open source libraries for the web frontend. Oh.. yeah and persistence is handled by that ORM library. And then there is this command line tool we have in the container to manage a few tasks. Learn how you can apply supply chain principles to get a better understanding of your container and all its parts. Improve the workflows around them, optimize the parts and manage it all efficiently. And take advantage of a number of emerging tools to keep it manageable.
+
+
Outline:
+
+
Introduction to hidden complexity of components inside containers with examples
+
+
+
E.g. JAR files and JS libraries in application
+
Libraries in application server
+
Services running on operating system of container
+
+
+
+
Introduction to supply chain management principles
+
+
+
Reduce parts
+
Reduce suppliers
+
Higher quality parts
+
+
+
+
Apply supply chain principles to container management and creation
+
+
+
Create your own containers
+
Understand what is in them - including security and license details
+
Reduce complexity
+
Manage them in your own registry
+
+
+
+
Review helpful tools
+
+
+
Docker Trusted Registry as SaaS
+
Sonatype Nexus Repository Manager as on site registry
+
TwistLock for security analysis
+
+
+
+
Speaker:
+
+
Manfred Moser got involved with agile methodologies, CI servers and the intersection of Ops and Dev, before everybody was talking about it. He has a passion for tools that help other developers. He is a trainer for Apache Maven and the Nexus Repository Manager and author of multiple books. He is a committer with a number of open source projects. As community advocate for Sonatype, he helps developers with their component usage reaching out from Victoria, BC.
Deploying and running web services using Docker has great benefits. It isolates the application, allows closer parity between production and development and easier deployment of generated Docker images. The best practises around building and deploying with Docker, however, are still emerging.
+
+
In this talk I’d like to explore one way of building and deploying a Python web application in a Docker image with the following goals:
+
+
+
Keeping the Docker image small.
+
Leave the build tools out of the production image.
+
Reduce the build time by avoiding unnecessary dependency installation.
+Our approach uses a “build” and a “deploy” image in combination with the Docker tool chain. Let’s see what you think 😄.
+
+
+
+
Speaker:
+
+
Sebastian has discovered his love for Python early on and found ways to use it successfully in various industries. Over the last few years, he's been mainly building things for the web using the Django framework. He's also enthusiastic about Docker and improving life, one container at a time.
Since we all love Docker, won’t it be fun to use it for other purposes that require a standard and simple way to setup things? In this session we’ll share our experience of using Docker for technical pre- and post-sales, trainings and PoCs, using the Docker Machine, Docker Compose, Docker Swarm, and Google Kubernetes.
+
+
Speaker:
+
+
Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate of JFrog, the home of Artifactory - the Universal Artifact Repository, and Bintray - the Universal Distribution Hub.
+
+
For a living he hangs out with the JFrog tech leaders, writes some code around Artifactory and Bintray, and then speaks and blogs about all that. He does it repeatedly for the last dozen of years and enjoys every moment of it.
I'll present the idea that operational empathy is essential to the software engineering practice. With examples from five years of helping to build and operate a large IaaS product, I'll show how empathy influences choices from logging libraries to high-level design for observability and debuggability.
+Touching on the role of code review, professional development, and the
+existential inevitability of production failures, we'll see how this approach acts as a #hugops force multiplier, improves operations, and creates positive feedback into engineering.
It took Bench Accounting a long time to go from simple manually provisioned Java monolith app to a fully automated microservices environment with Scala and Node.js apps deployed in AWS.
+
+
In this session I want to share our experience using Ansible to leverage your existing AWS infrastructure and build repeatable environments using AMIs, CloudFormation and Elastic Beanstalk.
+
+
In the beginning I’m going to describe how we created playbooks for our backing services and also used Ansible for creating AWS AMIs.
+
+
Then I’ll talk more about repeatable environments and show how one can use Ansible playbooks, AMIs and CloudFormation together.
+
+
Finally, I’ll present the way of automating AWS CLI with Ansible for services that are not covered by Ansible standard modules, using Elastic Beanstalk as an example.
+
+
Speaker:
+
+
Yaroslav Tkachenko is a Director of Engineering, Platform at Bench Accounting. For more about Yaroslav see sap1ens.com and linkedin.com/in/sap1ens
Gender in organizations: From fixing the women to liberating the men
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Male-dominated organizations and industries have struggled with integrating women into their ranks. Professor Berdahl presents the different frameworks that have been used for thinking about this problem, from training women to act more like men to examining how work continues to be the site of masculinity contests. Berdahl discusses the underlying assumptions, implied remedies, and ultimate effectiveness of these different frameworks.
I'd like to put a selection of people to talk about ways they use different
+plugins and tools for the different text editors out there.
+
+
Mainly covering:
+- How to set up snippets for Atom, Sublime Text, NeoVim, Emacs
+- How to set up ways to run rubocop inside Atom, Sublime Text, NeoVim, Emacs
+- Ways to run rspec inside Atom, Sublime Text, NeoVim, Emacs
+- General plugins and 'neat' things you can do in Atom, Sublime Text, NeoVim, Emacs
+
+
I want, this talk, NOT to be a religious war, I want this talk to be informative and get
+people away from using Notepad, or Notepad++ or even Word.
+
+
In a statement, "I realize there are strong opinions here, but I want you to be informed not which is 'better.'"
Improve the impact of DevOps–driven application delivery with machine data insights
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
The deployment of microservices and containers is accelerating DevOps driven application releases. With shorter release times and increased complexity, it is important to have the full visibility into all elements of the application delivery lifecycle. Join my talk to understand how mining machine data can help DevOps teams improve the velocity, quality and business impact of DevOps-driven application delivery
+
+
Speaker:
+
+
Stela Udovicic is a Senior Product Marketing Manager at Splunk. At Splunk, Stela is working within IT Markets group, focusing on DevOps. She enjoys traveling, reading and swimming,
You know the story. You wrote some code, diligently wrote your unit and integration tests, babysat the deploy, performed a smoke test, and your new feature is shipped and looking good. Five minutes later though and the metrics in some unrelated part of the system have all tanked, everyone's getting paged, and it looks like it was your deploy that did it. You sheepishly roll back to make the system stable again. What happened? You did everything you were supposed to.
+
+
Reliability is paramount. Downtime creates irate customers and lost business opportunity. In this talk, we'll discuss how to improve the overall resilience of your systems, and prevent situations like the above, by testing in production. We will review four different tools and processes implemented at PagerDuty that test various dimensions of its production systems:
+Failure Friday: Intentionally injecting failure into production systems
+Watchdog: Constantly validating the functional specification
+Canary Deploys: Verifying forward progress is made during deploys
+End to End Provider Testing: Ensuring availability of our third party telephony providers
+For each of these, we will discuss their origin story, their tooling and functionality, pitfalls to watch out for, learnings we've gathered, and how they've measurably improved reliability.
+
+
Speaker:
+
+
Kenneth Rose is a Principal Software Engineer at PagerDuty in Toronto. Ken has worked on everything from the C# compiler at Microsoft, to 3D graphics tools at Autodesk, to most recently writing highly available event processing systems at PagerDuty.
Infrastructure as Code is the new black for the operation team
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
In a world of DevOps, with your time to deployment having to be faster, you need to be more efficient and flexible on your environment and don't want to lose a few days to spin a bunch of Virtual Machines or Database just for testing or deploying a new feature.
+
+
It doesn't matter if you're using your own environment or a public cloud provider's, you need to be sure that your configuration and architecture are the same everywhere for every deployment in every environment. And this is where Infrastructure as Code (IaC) will help you to spin, multiple environments with the same configuration overtime in only a few minutes.
+
+
We will share during this session how I experienced the changes in my role, from a classic operations guy to a full fan of automatization.
+
+
Speaker:
+
+
Julien Stroheker is a Technical Evangelist at Microsoft.
How confident are you that your infrastructure is in the state that you think it's in? How do you detect when unexpected changes are made to your infrastructure? In this talk, I'll teach how you can use Terraform to detect infrastructure inconsistencies in AWS and how you can use this technique to stay sane when managing multiple data centres.
+
+
Speaker:
+
+
Payam Moghaddam is an Infrastructure Engineer at ACL for their global SaaS platform where he both manages and implements ACL's platform on AWS. Payam started off as an application developer where he consulted enterprises in both architecting and implementing their web applications with modern web frameworks. He has since shifted focus away from application development towards infrastructure development, where he now focuses on coding the infrastructure and automating everything.
It's all Code! Using GitHub, Terraform and CircleCI to build a Dev Pipeline
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
There's more code than ever being used to manage development pipelines. Infrastructure-as-code, configuration management scripts, application source...where should it all live? Get that code off of your local machine and into version control where it belongs! This talk will showcase a simple dev pipeline using Terraform and Circle CI with code, scripts and configuration all stored in GitHub. We'll walk through the progression of a commit, from git push to spinning up infrastructure with Terraform to testing with Circle CI.
Do you know if your infrastructure have the good specifications to run your application ? Or do you have a need for testing your service with a large burst load just before your big launch ?
+In this session, we will talk about how you can automatically include load tests in your development stream from code to production and the best practices in term of how integrate your favorite tools in your workflow using Visual Studio.
+
+
Speaker:
+
+
Julien Stroheker is a Technical Evangelist at Microsoft.
A client wanted to enable their teams to take ownership of AWS projects in a manner that removed the client's CloudOps Team as a direct blocker. However, CloudOps still needed to maintain permission oversight over the AWS projects. Our team was brought in to develop a solution to monitor and store permission changes in AWS and if necessary escalate repeated bad requests to the CloudOps team.
+
+
We designed and developed a new solution to manage and govern IAM credentials across various organizations. The design was created to be scalable to multiple accounts in a repeatable fashion using Cloud Formation.
+
+
Lambda was used for data and permission processing. DynamoDB tables was used to store allowed/denied information. SNS was utilized to message resources of failed attempts.
+
+
Speaker:
+
+
Michael Towbin is a Senior DevOps Engineer at Slalom Consulting
+
+
Jeremy Dyche is a Senior DevOps Engineer at Slalom Consulting
Lets verify your OpenStack cloud's level of Security!
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Using Compliance, and in turn Inspec, on an OpenStack cloud. I'll explain and show the OpenStack security guide, and where you can find it and how we have used Inspec to code the whole thing.
+
+
This will be a technical discussion about the OpenStack security guide, a walk through and then a demo of using Inspec to automate the manual steps. I plan on demoing Compliance also as another layer of reporting too.
As our organization grows, we have to grow our deployment tools with it. I will discuss improvements we've made including removing shared SSH keys, pull vs push deployments, using build artifacts, and doing atomic deploys. We've got a fully continuous deployment process, getting our deploy times and our build times under 15 minutes each. I'll also present running the CI tests in Docker containers so that we will be testing the code in the exact same environment as production.
+
+
Speaker:
+
+
Jan Ulrich is the DevOps team manager and developer at Salesforce Pardot, where he's been working on automating internal processes. Previously Jan was co-founder of Optemo Technologies building e-commerce solutions for large retailers.
The key question that every developer goes through when they do a release is whether their release will break the web. This talk will go through what are some of the best practice in making sure developers are comfortable in doing releases in a continuous integration/delivery environment and doing these releases frequently. I will go through the iterations of our deployment flow and what were the lessons we learned from them.
+
+
Speaker:
+
+
Shih Oon Liong is a Senior Operations Developer at Hootsuite, with nearly a decade of experience in operations and development for the web in both London, UK and Vancouver, Canada. Despite being part of a company with 200+ engineers, Shih Oon is primarily responsible for managing both infrastructure and build pipeline that handles a significant amount of traffic (15 million requests a month) across 3 major applications.
Single Page Applications (SPA) have been one of the major new architectural shifts for websites. While this has enabled impressive site look and feel, and reduced the number of bytes delivered to the end users, it has introduced new challenges resulting on many sites degrading performance or not “working” on mobile after migrating to SPA. Come to this talk and learn how to get a top performing SPA.
+
+
When implementing SPA it is critical to understand that techniques that worked well in traditional sites might no longer deliver acceptable site performance. Single Page Applications pose inherent obstacles to fast load times and good user experience:
+
+
+
The Overhead of Frameworks: SPA frameworks use JavaScript to modify and control the DOM in a developer friendly environment; however, this comes with a cost. Experts in the field have identified problems such as memory leaks, overloaded libraries, and large framework files. This can especially be devastating on lower end mobile devices.
+
API Caching: Many SPA sites encounter decreased caching and offload at both clients and CDN. Both do not work well with default configurations and JSON communications only add to the difficulties.
+
Expensive Load: We often see websites first view taking 6-10 seconds to load on desktops. Often this is due to an install/bootstrap process for the framework on each user visits. In lower end mobile devices, the framework’s JavaScript overhead can make the site practically unusable.
+
Latency Sensibility: As SPAs consist mostly of API based communications, they are extremely sensitive to latency . This is particularly troubling in mobile connections where latency could be between 100 ms and 3.5s All the old HTML tricks of rending and flushing are not applicable anymore.
+
Performance Monitoring and Testing Challenges: Classic monitoring and testing tools cannot accurately track the transactions and end user experience. For example, because Navigation events happen after the onload event, the popular onLoad metric ceases to be useful. Metrics such as Page Load Time and Time to Start Render are not well defined making it hard to identify the real user Time To Interact. All this lack of visibility into the application makes tuning difficult
+
+
+
+
In this talk we will discuss each of these challenges and how they can be solved. We will explore the latest industry best practices for the fastest SPA sites, such as:
+
+
+
Lazy load strategies as they apply to SPA
+
JavaScript packaging best practices
+
Latest Monitoring tools and techniques for SPA
+
Over download mitigation
+
CDN configuration optimizations
+
Server rendering to reduce client processing
+
+
+
+
While your Single Page Application may deliver many benefits, it should not come at the cost of performance. By learning new techniques to optimize the application and new tools to track performance, SPAs should deliver equal if not faster performance than any classic server side rendering frameworks.
+
+
Speakers:
+
+
Boris Livshutz - Senior Enterprise Architect, Advanced Solutions and Services, Akamai Technologies
+
+
Boris has spent over two decades making enterprise applications run faster. Boris is an Enterprise Architect at Akamai, working on improving the performance of some of the world's largest websites. Previously he ran the Center of Excellence at AppDynamics where he developed best practices for using performance monitoring tools to improve the speed and reliability of large sites and helped them scale in the cloud. In his earlier years, he worked at startups and then at Oracle, building database and data warehousing products for enterprise customers.
+
+
If doable, Boris will have it done
+
+
Manuel Alvarez - Enterprise Architect, Advanced Solutions and Services, Akamai Technologies
+
+
Manuel’s career focus on both designing complex technical solutions over a variety of technologies and driving business objectives by implementing solutions aligned with the organization goals with proven ROI, as implementing advanced caching techniques to reduce platform costs. He has worked in large projects with Financial Institutions, High Tech Companies, and Telecommunication Services across multiple geographies.
At Hootsuite we have created a new microservice framework called Skyline based on REST HTTP services written primarily in Scala, auto discovering and routing using Nginx and Consul, and running in Docker containers on Mesos.
+
+
We are moving away from services using non-standard means of communication (ZeroMQ) and have seen this new framework to be far easier to understand, require fewer moving parts and network hops, and be far more tolerant to instability in the network or system.
+
+
This talk will cover our experience with using Consul and Nginx to create an easy to use, scalable, and HA service discovery and routing system.
+
+
Speaker:
+
+
Bill has spent his 15+ year career working almost exclusively for startups. He was one of the early employees at Hootsuite and has spent the last 6 years writing PHP and Scala and tackling the many Distributed Systems problems that are come with scaling from a hundred thousand users to tens of millions.
Platforms: either you have one or you’re building one. Over the years I’ve observed six high-level characteristics common to production environments which are operationally mature:
+
+
Routing and load balancing.
+Backing services broker.
+Infrastructure orchestration.
+Health management, monitoring, and recovery.
+Immutable artifact repository.
+Log aggregation.
+
+
This talk will explain in detail the six capabilities in an operationally mature production environment. It will serve as a rubric for anyone building their own production platform composed of unstructured components; or choosing an integrated, structured platform from the many options available.
+
+
Sometimes the automation and speed available to operationally mature organizations can seem like magic to those at the beginning of their devops and automation journeys. That’s why I will also demonstrate these capabilities in an interactive, live exposition.
+
+
Critical capabilities including infrastructure and application lifecycle management, deployment, auto-provisioning backing services, and failure recovery will shown. You’ll see what life is like for teams who have the operational maturity of a Minimum Viable Platform.
Working in Internet infrastructure, web app security, and design taught Casey to be a paranoid, UX-oriented, problem solving Internet plumber; his earliest contributions to Perl live to this day on your Mac. Casey’s speaking and writing ranges from open source communities and culture to technical architecture and automation tips and tricks. Casey West wears the mantle of Principal Technologist focused on Pivotal’s Cloud Foundry Platform and lives in Pittsburgh raising three sarcastic children.
Orchestrating and automating AWS Spot Fleets in a distributed crawler for profit and fun!
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
At STAT Search Analytics, we unlock insights in complex data to give brands a competitive advantage in search. Several enterprise brands such as Expedia, Ebay, Pinterest etc. track millions of search terms with us everyday. We crawl these search terms on Google, Yahoo and Bing using our distributed system and report valuable SEO metrics to our clients. This helps our clients stay ahead of the competition and win the search game.
+
+
An important and expensive component of the distributed system is the Parser. It parses the HTML on the Search Engine Result Page to inform our clients of their website ranking. The parsers are susceptible to changes in the HTML making their speed and performance vary frequently. In our production system, parsers are setup as standard EC2 instances, with multiple workers running on each instance. The EC2 instances are kept ON for the entire day so that the parsers are ready to process jobs whenever required.
+
+
I will describe our distributed crawler at a high level. Then, we will discuss how we are moving to AWS Spot Fleets to reduce costs and improve the efficiency of our parsers. There are several challenges that I will talk about – Bidding on Spot Instances, setting up of Spot Fleets and deployment of code, networking and communication of instances with other parts of the distributed system, automation, fault tolerance and orchestration of the entire process. The system is fairly platform agnostic and can be swapped with other cloud computing services like Google, Azure etc.
+
+
This talk will be useful to developers and teams that are building a large scale and efficient distributed system and/or are building Big Data Analytics platforms, financial modelling and analysis systems, image and media encoders and web crawlers.
+
+
Speaker:
+
+
Anish Kumar is the Director of Technology at STAT Search Analytics. He has been working on large-scale distributed systems and analytics web applications for the past 6 years at STAT, where he is leading and growing an amazing team of developers. In a previous career, he was conducting Machine Learning research on Natural Language Processing and speaking at research conferences in Europe and Australia. Anish enjoys long distance running, history, museums, travel and food and loves having an engaging conversation on any of those.
Ownership –the key to DevOps, above even tech skills
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
To some people DevOps is a simple as embedding people with operations skills into your development team to make turn-around time on infrastructure needs that much shorter. To other it’s taking someone already on your team and training them up to become the DevOps expert. It could be either of those things in part but neither of them are really the instrumental path to success in implementing and living the life of a DevOps organization.
+
+
The success of DevOps in an organization is entirely predicated on the concept of disallowing the phrase ‘that’s not my job’ and encouraging the embracing of the concept of total ownership. Each and every member of your team needs to able and willing to see things that need to get done and figure out how to get them done. Does this mean that you have a QA coding in binary simply because it needs to be done?
+No, but it does mean that your QA can learn some things and facilitate others to ensure that tasks that need to get done are done.
+
+
Do you need an Ops person to spin up a new server? Has a server crashed and no one is dealing with it? Is there a new technology that needs review and assessment? None of these things require that you wait for an Ops person. They simply require that someone take ownership of the problem.
+
+
This talk will demonstrate through talk and stories what ownership in a successful DevOps environment looks like and why it breeds success.
+
+
Speaker:
+
+
Mike Hrycyk - has been trapped in the world of quality since he first did user acceptance testing 17 years ago. He has survived all of the different levels and a wide spectrum of technologies and environments to become the quality dynamo that he is today. Mike believes in creating a culture of quality throughout software production and tries hard to create teams that hold this ideal and advocate it to the rest of their workmates. Mike is currently the Director of Quality for PQA Testing, but has previously worked in social media management, parking, manufacturing, web photo retail, music delivery kiosks and at a railroad. Intermittently, he blogs about quality at www.qaisdoes.com.
At Mobify, we’ve been running Docker in Production for about a year now. When we decided to make the switch, we evaluated several SaaS solution that would allow us to run Docker services and ended up choosing Amazon Beanstalk.
+
+
After 12 months and countless moments of swearing, it is time to share some of the annoyances that came with Beanstalk running Docker.
+
+
These are the problems we’ll be looking at:
+
+
+
Worker WTF: running a worker on Beanstalk is plain weird.
+
Getting centralized logging to work.
+
Integrating New Relic server monitoring (for EC2 intances).
+
Some insane and some not so insane scripts that we wrote.
+
Try EC2 Container Service (ECS)…if you have a high pain threshold
+
+
+
+
Speaker:
+
+
Sebastian has discovered his love for Python early on and found ways to use it successfully in various industries. Over the last few years, he's been mainly building things for the web using the Django framework. He's also enthusiastic about Docker and improving life, one container at a time.
Running on hotness, deploying with Docker and Convox
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
The need for small teams to deploy and manage applications on a massive scale has fuelled the development of open source deployment tools such as Docker and Convox. This has removed the dependencies on specialized teams or system admins to deploy, manage and provision applications. At Zillow / Retsly, we share this vision of empowering our developers to deploy, manage and scale their own code at will.
+
+
In this talk I will go through:
+- Retsly’s use case and how we got to the scaling problem.
+- Why we chose to use open source software such as Docker and Convox.
+- A demo on deploying a microservice stack to AWS using Convox.
+- The good, the hard and the lessons learned.
+
+
This talk is useful to the developers and teams:
+- Who’s deployment demands are outgrowing their time and capabilities.
+- Who want to learn about the risks of deploying production grade application with new open-source software.
+- Who want to see a live deployment of applications using Convox and compare that to their own flows.
+
+
Open source software such as Docker and Convox is quickly becoming the foundation of deployment pipelines. By simplifying a once complicated and gruesome processes, it has enabled small teams to easily deploy and manage applications on a scale once thought impossible.
+
+
Speaker:
+
+
At Zillow / Retsly, Rongxin has helped set up deployment pipelines that enable their applications to scale with an ever increasing developer base. He has deep experiences that span from designing beautiful user-interfaces to deploying battle-tested containers. When he is not developing or deploying, he spends his days listening to old school funk and grooming flowers.
A follow up to 2014's DevOps days regarding Mobify's DevOps culture. We've since grown from a 50 person team to an international crew several times that size with offices across the world, and the way DevOps fits in our culture has changed. What does "DevOps" mean to a startup vs a medium sized technology company.
+
+
Speaker:
+
+
Kyle Young @ksgyoung is Mobify's System Engineer, where he has spent the last three years championing DevOps, and building the backend systems and infrastructure that keep things humming. He is also Quidditch Captain.
Continuous delivery can be a simple practice when you are a small development team with a low scale web application. However, as teams scale up in size, commit and test volumes increase, and production architecture becomes more complex, continuous delivery becomes harder to achieve. Tools that once handled the load begin to fail, individual steps in the delivery process that were once fast turn into bottlenecks, and cultural practices and processes break down.
+
+
This talk will describe how Shopify faced these scaling challenges as the team and its application infrastructure grew. A year ago, it could take hours for a developer to go from commit to fully deployment application. In response, the team re-architected its entire delivery pipeline to hand these scaling challenges. We cover how moving to a container-based build and creating the open source Shipit deployment tool allowed the team to regain its continuous delivery cadence.
+
+
Today, every developer on a team of hundreds can deliver a change from commit to production in ten minutes. Each deploy includes execution of over 45,000 tests in a massively parallel build farm, and deploying the application to hundreds of servers in multiple data centres. Thirty or more production releases now run in a typical workday, and developer happiness has increased. We will cover the steps taken to get here, the technology choices made, and the stumbling blocks faced along the way.
+
+
Speaker:
+
+
John works on the Shopify Production Engineering team, with a specific focus on creating developer tooling to accelerate application delivery. John is a frequent speaker at technical conferences in both Europe and North America, serves on conference program committees, is a JavaOne Rock Star, and frequently writes blogs and articles on technical topics. His current interests are in tools and practices for Continuous Delivery, and in highly scalable cloud architectures. Before joining Shopify, John led a team building cloud-based developer tooling for IBM Bluemix, and was a prominent leader within the Eclipse open source community.
So You Want to Choose a new CI Tool... without being a dictator!
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
As part of ThoughtWorks, we have seen many projects where DevOps is a separate team and structure or not present at all. In my recent work, we had the chance to explore integrating DevOps in a delivery team from the start of a project, starting with choosing a CI tool. In order to help ensure the right tool was being selected, we crafted a decision process that helped us to both evaluate a growing number of options in the CI/CD space as well as examine the constraints and concerns our particular team face. This talk covers the process we followed for evaluating CI/CD tools, how we made a flexible decision, and some pitfalls on the process.
+
+
Speaker:
+
+
Elise McCallum is a Senior Consultant and Applications Developer at ThoughtWorks, with a focus in DevOps and integrating DevOps as part of agile delivery teams.
Many have ended up in their career, whether it is by choice or by circumstances, in which they
+become sole developer who becomes the goto guy for anything about infrastructure. They become the
+linchpin in the development team and fighting the fires on the servers. This is especially true in start ups or
+agency work where resources are limited and the pace is fast. This talk will suggest some guidelines such
+developer can follow to survive and grow in such an environment.
+
+
Speaker:
+
+
Shih Oon Liong is a Senior Operations Developer at Hootsuite, with nearly a decade xperience in operations and development for the web in both London, UK and Vancouver, Canada. Despite being part of a company with 200+ engineers, Shih Oon is primarily responsible for managing both infrastructure and build pipeline that handles a significant amount of traffic (15 million requests a month) across 3 major applications.
System testing a microservice architecture is challenging. As we move away from monolithic architectures, system testing becomes more important but also more complicated.
+
+
In the video game industry, if a game doesn’t work properly immediately after launch, it will heavily impact game success. We have found system testing to be an important tool for pre launch testing of game services and operational tools, to guarantee quality of these services at launch.
+
+
We want to share with you best practices for system testing: when to write system tests, what to test and what not to, and common pitfalls to avoid. Using python’s pytest tool and docker-py for setting up services and their dependencies has made it easier than ever to write complex but maintainable system tests and we’ll share with you how we’ve made use of them.
+
+
Developers (senior and junior) and ops folks can walk away from this talk with practical tips they can use to apply system testing to their software.
+
+
Speaker:
+
+
Christie Wilson
+
+
Christie Wilson is the team lead of the Test Tools team at Demoware, which provides high quality tools and best practices for testing AAA video games. Christie founded and runs the Vancouver BC chapter of PyLadies. She loves lolcats and quality.
+
+
Michael Tom-Wing
+
+
Michael is a software engineer at Demonware, where he masquerades as a video game title developer but really works on DevOps problems. Recently his focus has been on improving software release and deployment management, but also dockerizing everything in sight. He loves Python and all things Japanese, and has been known to have an “automate first, save time later” attitude.
Jenkins is ubiquitous and powerful, but very quickly becomes unruly with a lot of wasted resources. It ultimately becomes a highly operationally dependent snowflake that is hard to manage. Chances are a lot of DevOps attendees use Jenkins for CI/CD with a love/hate relationship. There is a better way; releasing Jenkins as a service in itself just like other software. We’ll talk about how we Dockerized our Jenkins setup (masters & slaves) as immutable containers, get them to share compute resources on Mesos, and create per-team instances to give your engineering teams autonomy. All the while centrally managing and deploying the Jenkins cluster with roll-backs, HA, and easy to manage dependencies.
+
+
Speaker:
+
+
Mark Eijsermans is a Senior Software Engineer on the Platform team at Hootsuite.
The Blameless Cloud: Bringing Actionable Retrospectives to Salesforce
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
As organizations experiment with greater concurrency and integration between their departments and move toward a continuous delivery of customer-value, failure is assured. Asking "how can failure be avoided?" isn't as useful or relevant as focusing on
+
+
+
"How does our organization react when failure occurs?" and
+
"How do we create a sustainable, actionable process for describing, exploring, and remedying failure?"
+
+
+
+
This is the question that presented itself to Salesforce’s Service Reliability Engineering team. Their SREs had received training in incident response and management, but were still struggling with how to incorporate that feedback into the organization at large, to improve outcomes. Feedback loops weren’t always closed, leaving many opportunities for improvement lost.
+
+
This is the story of my months-long journey with J.Paul Reed and my team to identify the specifics of what made reliability retrospectives difficult to have, why actionable takeaways were often lacking, and how the feedback loops within the company’s operations organization weren’t serving Salesforce’s needs.
+
+
We then ran a series of experiments together, putting the SRE team on a road to improving their ability to respond, react, remediate, and re-incorporate learnings from failure into the organization.
+
+
The Takeaways?
+
+
+
The importance of the retrospective process in building resilient, humane, operable systems.
+
The common hurdles to holding actionable operations retrospectives and the experiments we ran to overcome those hurdles at Salesforce, hopefully providing possible solutions for attendees.
+
+
+
+
Speakers:
+
+
Kevina Finn-Braun
+
+
Kevina Finn-Braun’s focus throughout her 18 years in the Internet Industry has been Operational Excellence and Risk Management. She is currently Director of Site Reliability Service Management at Salesforce where she leads the team focused on operational process improvements in the areas of incident, problem and change management. In her previous role as Director of Business Continuity at Yahoo! she led the team focused on risk management and service continuity best practices.
+
+
J. Paul Reed
+
+
J. Paul Reed, aka The Sober Build Engineer, has over a decade of experience in the trenches as a build/release and tools engineer, working with such organizations as VMware, Mozilla, Postbox, and Symantec.
+In 2012, he founded Release Engineering Approaches, a consultancy incorporating a host of tools and techniques to help organizations “Simply Ship. Every time.” He’s worked across a number of industries, from financial services to cloud-based infrastructure, with teams from 2 to 12,000 on everything from tooling, operational analysis and improvement, team culture transformation, and business value optimization.
The Cognitive Neuroscience of Empathy: You’re a DevOps Natural
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
There is a understanding in the DevOps community that human empathy is a fundamental component of what is required as collaborators and in understanding our customers (for examples see http://blog.ingineering.it/post/72964480807/empathy-the-essence-of-devops, http://www.opsbs.com/2014/03/empathy-in-oss-its-important/, http://chadfowler.com/blog/2014/01/19/empathy/, http://blog.lusis.org/blog/2014/10/19/software-empathy/). Scientific discoveries have explored just how innate empathy is to the human condition. With the discovery of mirror neurons (Rizzolatti, et. al), we’ve learned we don't merely observe the actions of others, we activate the same neural circuits to allow us to imagine their goals and motivations. We were born to partner with others instead of "throwing it over the wall". Combining that knowledge of being able to feel what others are feeling, with the recognition that others have a mind (mentalizing), as well as a desire to help those we consider in our “in-group” (prosocial concern), creates a powerful effect when it comes to working with others on a common goal. Come and learn what role your neurobiology has in our ability to empathize with teammates and why it is at the core of effective cross-functional teams.
+
+
Speaker:
+
+
Dave Mangot is the Director of Operations for Librato and Papertrail and an accomplished systems engineer with over 20 years of experience. He has held positions in various organizations from small startups like Terracotta to multinational corporations like Cable & Wireless and Salesforce, and from systems administrator, to architect. He has led transformations of multiple companies both in operational maturity and in a deeper adherence to DevOps thinking. He enjoys time spent as a mentor, a speaker, and a student of so many talented members of the community. Dave has a degree in Cognitive Science and lives with his wife and three children in San Francisco.
This talk will use the seminal twelve-factor app essay as a guide to discuss the do’s and dont’s of building and running containers. Each factor gives us an opportunity to consider avoidable anti-patterns if you’re using containers to deploy and manage repeatable, reliable, and portable services.
+
+
Containers rose in popularity on an oft used metaphor: lightweight virtual machines. We have a robust understanding of the benefits of virtualized hardware as a method of efficient resource utilization. The idea of even more efficient resource utilization makes sense. Unfortunately it’s a problematic metaphor.
+
+
Containers represent a constrained set of capabilities compared to virtual machines in order to make fine-grained guarantees about resource constraints and process isolation. This is a good thing. There is overlap in ideal capabilities between VMs and containers but it isn’t complete. Newcomers to the container ecosystem begin with a “lightweight VM” understanding and fall victim to specific anti-patterns.
+
+
After this talk you’ll understand common pitfalls in containerization and how you can avoid them. This discussion is useful for developers who wish to gain greater understanding of the environment their applications are deployed to, as well as operators interested in the benefits of containers for their architecture.
+
+
Speaker:
+
+
Working in Internet infrastructure, web app security, and design taught Casey to be a paranoid, UX-oriented, problem solving Internet plumber; his earliest contributions to Perl live to this day on your Mac. Casey’s speaking and writing ranges from open source communities and culture to technical architecture and automation tips and tricks. Casey West wears the mantle of Principal Technologist focused on Pivotal’s Cloud Foundry Platform and lives in Pittsburgh raising three sarcastic children.
Up and Running with ELK (Or: the 5 minute ELK install)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Without being too buzz-word laden, a talk to go over get ELK up and running in AWS in a way that would also apply to on-prem, Azure and other cloud vendors. The key difference will be Beats, Mesos and Marathon, which should allow for some fancy screens and hopefully get people ready for container scheduling on many nodes.
+
+
Speaker:
+
+
Seasoned technical systems operator currently deploying servers, workflows and processes to Amazon Web Services by leveraging years of multi-platform web, database and programming experience. In my spare time I dabble in fashion photography, wrestle dogs and pretend to jog.
Utilizing DevOps for effective IoT and User Telemetry correlation-based Data Analytics
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Two areas that have gained immense traction in the technology space recently are Internet of Things (IoT) and user telemetry analytics. IoT focuses on deploying and linking physical sensors together to collect and exchange information, while user telemetry focuses on collecting behavioral data and provides insight on application usage patterns.
+
+
In this presentation, we will provide our vision and framework on how to leverage Internet of Things and telemetry data together to deliver the most business value to the end user. Data from Internet of Things sensors provides insights on environment and physical information experienced by the user, yet it is telemetry and behavior data that allows for user feedback and validation. As a result, a framework that correlates data from both sources allows for the user to be front and center in any Internet of Things scenario, thus delivering key business value by improving the user experience.
+
+
As both IoT and user telemetry processes collect large amounts of data, we will focus the talk on two important areas, dev-ops (using Git, Jenkins and Docker) and data science, which come hand-in-hand in supporting data-driven scenarios. Having both the necessary development and operations support for both software and hardware, along with effective and efficient data science tools, is critical to realize this vision of correlating both IoT and telemetry data for the end user.
+
+
Speaker:
+
+
Hubert
+
+
Hubert is a Data Scientist at Boeing Canada – AeroInfo working in the area of aviation prognostics. He has 6 years of professional experience in statistics, data science, and machine learning, having worked at Microsoft, Statistics Canada, Canadian Department of National Defense, and University of Ottawa. Areas that he is passionate about include airplane predictive maintenance, cyber-security, Internet of Things, behavioral (telemetry) analytics.
+
+
Manpreet
+
+
Manpreet is a Senior Full-Stack Software Developer at Boeing Canada – AeroInfo working in the Advanced Analytics Group. He has more than 9 years of professional experience in full stack software development using a variety of technologies. Before joining Boeing Canada – AeroInfo, he has also worked at Best Buy Canada, HSBC Canada, InComm Canada, Dominion Marine Media and Edifecs.
+
+
Alex
+
+
Alex is a DevOps Engineer / Senior Linux Systems Administrator at Boeing Canada – AeroInfo working in the DevOps / IT Group. He has more than 9 years of professional experience in Systems Administration using a variety of technologies. Before joining Boeing Canada – AeroInfo, he has also worked at Qtrade Financial Group, hyperWALLET Systems, and La Jornada.
What do the recent CVEs tell us about Container Security compliance?
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Abstract:
+
+
Just this year alone there have been a big number of CVEs that impacted more than half of the web properties out there and there has been a lot of talk about how safe containers are after they achieve a running state and how they compare in levels of security to Virtual Machines.
+
+
Little has been said though about how container based packaging and deployments will improve or degrade the ability to keep us safe.
+Management of dependencies will stop being a headache only for Security and Ops teams reaching also the ones on the very edge writing code and choosing what libraries to use.
+This talk will be focused at three main areas in regards to Container Security.
+the life cycle of a container as it relates to updates and fixes
+Continuous Security and DevOps
+Tips when creating a Security Pipeline
+At the end of the talk I expect attendees to be aware of the process and mindset changes that are necessary if you adopt containers as a packaging and deployment model.
+
+
Speaker:
+
+
As an OpenShift product manager, Diogenes Guedes Rettori leads the direction for Red Hat's middleware-services strategy. Prior to joining the OpenShift team, Diogenes focused primarily on educating customers on updates and new offerings for Red Hat JBoss Middleware. Diogenes has a strong engineering background having work at companies such as Ericsson and IBM. He is fluent in Portuguese, English and Spanish.
The Sharethrough platform has grown both in size and complexity as we expand to support more customers. How can we refresh our infrastructure and continue to serve millions of ad requests without interruption? DevOps has been coined a movement, a culture change, to something money can't buy. What does it mean to an AdTech company? Being the first DevOps, I have the chance to shape this uncharted area. In this presentation, I like to share lessons we learned from consolidating multiple AWS accounts and the unexpected side effects. Unknowingly using social psychology to nudge our engineers to deploy more, as a result completed the last mile of our CD pipeline. Tools we use to treat our "Infrastructure as Code" and refresh it when there are changes without fear. Increase security and reduce code complexity by using identity and access management tools. These projects all contributes to the meaning of DevOps at Sharethrough
+
+
Speaker:
+
+
Mason Leung is a Software Engineer at Sharethrough
Amazon’s user, role and policy management provides a lot of finegrained control of permissions for their individual services. In general, this is a great thing to ensure that humans and robots only have access to things that they should have access to…and that they can’t accidentally break production.
+
+
Unfortunately, the management console makes managing IAMs slightly more complicated than I think it should be: arbitrary limitations on groups per user, complex policy definitions in the form of JSON and the use of ARNs everywhere.
+
+
At Mobify, we decided to change the way we deal with this and provide a different way that integrates better with our existing workflows. We decided to manage IAMs in a github repo with some tooling that allows us to create new policies and users as well as update old ones.
+
+
Speaker:
+
+
Sebastian has discovered his love for Python early on and found ways to use it successfully in various industries. Over the last few years, he's been mainly building things for the web using the Django framework. He's also enthusiastic about Docker and improving life, one container at a time.
+
+ 
+
+
+
+
+ 
+
+ 
+ Photo:Perlbach
+
+ 
+
+
+
+
+
+
+
+
+Auditório do Prédio C (subsolo), próximo a entrada do prédio C.
+
+Para mais informações sobre o local, veja nesse link
+
+
diff --git a/exampleSite/content/events/2016-portoalegre/patrocinio.md b/exampleSite/content/events/2016-portoalegre/patrocinio.md
new file mode 100644
index 000000000..a2cd3ce23
--- /dev/null
+++ b/exampleSite/content/events/2016-portoalegre/patrocinio.md
@@ -0,0 +1,58 @@
++++
+date = "2016-05-09T10:06:26-03:00"
+title = "patrocínio"
+type = "event"
+aliases = ["/events/2016-portoalegre/sponsor"]
+
+
++++
+
+Se você está interessado em nos patrocinar, entre em contato pelo email [{{< email_organizers >}}].
+
+Material de patrocinadores:
+
+
+
+Para a proposta executiva completa, acesse esse link
+
+
+
+## Booth Space
+
+Gold and Platinum sponsors receive booth space at the event. This is the perfect spot for your engineers to meet other tech geeks. Your booth space will have a booth table (185 cm x 80 cm) and two chairs. You can set up your table as you like, be it to display signage, products, materials, or swag giveaways. We encourage sponsors to send engineers to interact with attendees during session breaks.
+
+Large displays and oversized marketing material are not allowed in the exhibitor space. Please check with the organizers if your items fall under the restricted category. You may ship your booth materials to the venue prior to the event day.
+
+
+
+
+# SPONSORSHIP PACKAGES
+
+Our sponsorship packages are structured around how you can help be part of the conference.
+
+
+
+### When can we pick our booth spot?
+
+Booths are not selectable. Our team will assign your table. Assignments will be made two weeks before the conference date.
+
+You can enter the venue Saturday morning at 7:30 am to set up your table.
+
+### How many scanners (and which type) do we get?
+
+None. The booth is a place to talk to people during breaks and this conference is not a typical conference or convention.
+
+We have seen that sponsors benefit the most when they bring engineers to the conference and interact with the attendees during the sessions. You are responsible to collect any information you want in person if you want to do giveaways.
+
+### Can we bring a 1m roll-up as our back wall?
+
+Whatever you bring must fit behind or on your table (185 x 80 cm).
+
+### Will we have any chairs at our booth?
+
+Each booth comes with 2 chairs.
+
+### Will there be a company sign at our booth? When do you need the graphics?
+
+You must bring your own signage and all signage must either fit on or behind the table.
+
+### Do we get any sponsored talks?
+
+No, but you are welcome to submit a proposal for consideration through our CfP form.
+
+### How many talk tracks do you have?
+
+It's a single-track program. You find more details on the program on {{< event_link page="program" text="our program page" >}}.
+
+### Do we get electricity connection for out booth?
+
+Yes, you will get a power strip (Plug Type G).
+
+### Will wifi connection be good enough for showing demos?
+
+We do not provide Wifi. Wifi has to be booked as extra on the venue.
+
+### Do we get an advertising in the program? When do you need the graphics?
+
+We will be using the logos that are sent by you.
+
+### Do we get a dedicated email blast?
+
+No, even better: we will give you a Twitter shout out.
+
+### Who should I send?
+
+Not marketing folks. Send your techie geeks that can interact with attendees during the sessions and the breaks.
+
+### How do I pay the sponsorship package?
+
+Invoices will be handled by our conference partner. You will receive an invoice including GST, if applicable.
+
+For this, we need the official business address, full name of your contact and GST number.
+
+### How do we register our sponsor tickets?
+
+Once payment is complete, we will send you an email requesting registration details of the attendees that will use the tickets associated with your sponsorship level.
+
+### How many people do you expect?
+
+We are planning for 150 attendees.
+
+### What kind of attendees will come to the conference?
+
+We are focusing on people who are architecting and building distributed applications or doing migration projects, especially those away from monolithic software. This will typically include Architects, Lead Developers, and IT-Operations.
+
+### Do you have media partners who will cover the conference?
+
+No; however, if you have an idea to support the event in the media, please let us know!
+
+### Can we ship stuff ahead?
+
+Yes. Please send us an email so we can work out the details.
+
+### Can we lock things at the venue during the event?
+
+Yes. There is a shared room where you can stash stuff. Access is organized by the venue itself.
+
+### My question is not covered here. What can I do?
+
+If you have any questions not answered above, please do not hesitate to send us an email at organizers-singapore-2016@devopsdays.org
+.
diff --git a/exampleSite/content/events/2016-singapore/the_sponsor_area.jpg b/exampleSite/content/events/2016-singapore/the_sponsor_area.jpg
new file mode 100755
index 000000000..83c0c6ed9
Binary files /dev/null and b/exampleSite/content/events/2016-singapore/the_sponsor_area.jpg differ
diff --git a/exampleSite/content/events/2016-singapore/the_venue.jpg b/exampleSite/content/events/2016-singapore/the_venue.jpg
new file mode 100755
index 000000000..202cd5c31
Binary files /dev/null and b/exampleSite/content/events/2016-singapore/the_venue.jpg differ
diff --git a/exampleSite/content/events/2016-singapore/welcome.md b/exampleSite/content/events/2016-singapore/welcome.md
new file mode 100644
index 000000000..38b29e318
--- /dev/null
+++ b/exampleSite/content/events/2016-singapore/welcome.md
@@ -0,0 +1,91 @@
++++
+City = "Singapore"
+Year ="2016"
+date = "2016-03-06T21:15:25-06:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-singapore"]
+
+
++++
+
+
+ 
+
+
+
+
+
+ 
+
+
+### A house divided against itself cannot stand.
+
+**_Change is in session!_**
+DevOpsDays DC was held **June 8 and 9, 2016** at the {{< event_link page="location"
+text="US Patent and Trademark Office" >}} in Alexandria, Virginia.
+
+## Review The Video
+
+
+
+Courtesy of our Platinum and Venue Sponsor, the [US Patent and Trademark
+Office](http://www.uspto.gov/). Archived video is available via
+[Livestream.com](http://livestream.com/uspto/Devops2016).
+
+## Why Attend?
+
+Whether you're in government, academia, or the private sector, _DevOpsDays is
+for you._
+
+Whether you're in operations, development, QA, security, or any other
+department, _DevOpsDays is for you._
+
+Whether you want to learn about DevOps, share your experiences, or just talk
+shop with DevOps practitioners, _DevOpsDays is for you._
+
+DevOpsDays are a mix of keynote sessions and [open
+spaces](http://en.wikipedia.org/wiki/Open_Space_Technology).
+
+## About Washington, DC
+
+If all you know of Washington, DC is what you see on C-SPAN or _House of Cards_,
+you're missing out. While its importance as the Nation's Capital and center of
+government is undisputed, the "DMV" (District, Maryland, and Virginia) is also
+home to innovative startups, leading universities, and world-class arts and
+culture.
+
+If you're local, you already know the diversity of our DevOps community. If
+you're coming in from elsewhere, prepare to mix with DevOps leaders from every
+segment of our vibrant local scene. And, of course, take some time to check out
+everything else the Nation's Capital has to offer, from the many free
+Smithsonian museums to great food and drink!
+
+For those coming from out of town, there are flights from just about everywhere
+to our three local airports, and there are several hotels nearby. More details
+are on the {{< event_link page="location" text="location page" >}}.
+
diff --git a/exampleSite/content/events/2017-amsterdam/conduct.md b/exampleSite/content/events/2017-amsterdam/conduct.md
new file mode 100644
index 000000000..61e283a95
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/conduct.md
@@ -0,0 +1,36 @@
++++
+date = "2016-08-10T20:18:13+02:00"
+title = "conduct"
+type = "event"
+
++++
+
+## ANTI-HARASSMENT POLICY
+
+DevOpsDays is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to adhere to the code of conduct at all conference venues and conference-related social events.
+
+## CODE OF CONDUCT
+
+I. I am an attendee at devopsdays, learning from and sharing with other devopsdays attendees in an effort to better myself and my industry. I co-create the experience with fellow attendees. I am prepared to give my energy, presence and sensitivity to creating the best possible experience for myself and others.
+
+II. I am coming to devopsdays to interact with people. I understand that imagery and language which is suggestive or derogatory will offend and make people uncomfortable. I also understand that people may have boundaries and sensibilities different from my own. I will accept without question when informed that something is offensive or unacceptable in the context of the devopsdays event.
+
+III. I will never intentionally harass or offend another attendee regardless of gender, sexual orientation, disability, appearance, size, race or religion and will not abide another attendee being harassed or offended. If I am aware that anyone is uncomfortable or unsafe, I will notify those giving offense and the devopsdays event organizers.
+
+IV. If I am offended or harassed, I will inform people around me who make me feel safe and the event organizers. If I feel safe, at my discretion, I will inform those giving offense of the specific actions with the hope that the other party is well-intentioned and ignorant, but I am under no obligation to do so.
+
+V. I understand that people are different and I attempt to be forgiving of others actions at the level of their sincere intent, but my priority is protecting my safety and the safety of others. I will act without hesitation or reservation until there are no question of the safety of all parties.
+
+VI. I trust the devopsdays organizers and attendees will co-create the best possible experience for everyone involved, as I will. I believe devopsdays is about empowering people and I will not forget I am empowered to create a safe and nurturing environment. If I or any other attendee violates this aspect of the event, I expect the conference organizers to protect the attendees by direct action, including expelling those in violation and contacting the proper authorities.
diff --git a/exampleSite/content/events/2017-amsterdam/contact.md b/exampleSite/content/events/2017-amsterdam/contact.md
new file mode 100644
index 000000000..945f1e372
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/contact.md
@@ -0,0 +1,16 @@
++++
+date = "2016-08-10T20:18:13+02:00"
+title = "contact"
+type = "event"
+tags = ["amsterdam","amsterdam-2017"]
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/exampleSite/content/events/2017-amsterdam/location.md b/exampleSite/content/events/2017-amsterdam/location.md
new file mode 100644
index 000000000..e28c25e14
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/location.md
@@ -0,0 +1,47 @@
++++
+City = "Amsterdam"
+Year = "2016"
+date = "2016-03-06T21:17:00-06:00"
+heading = "devopsdays Amsterdam - Event Location"
+title = "Event Location"
+type = "event"
+tags = ["amsterdam","amsterdam-2016"]
++++
+
+### Conference Location
+
+The conference is located at [Pakhuis de Zwijger](http://www.dezwijger.nl/ "Website of Pakhuis de Zwijger")
+
+Piet Heinkade 179
+1019 HC Amsterdam
+The Netherlands
+
+{{< event_map >}}
+
+## Getting there and accommodation
+
+### Transportation
+
+Amsterdam has a fantastic public transportation system.
+- Buses [48](http://maps.gvb.nl/en/lijnen/48), [246](http://maps.gvb.nl/en/lijnen/246) and [759](http://maps.gvb.nl/en/lijnen/759) stop right in front of the conference.
+- Tram [26](http://maps.gvb.nl/en/lijnen/26), departing from Amsterdam Centraal Station (main train station in the city).
+
+More information can be obtained by using the [GVB](http://en.gvb.nl/) or [9292](http://9292.nl/en) websites. Both have excellent apps in the iOS ([GVB](https://itunes.apple.com/nl/app/gvb/id370393784) & [9292](https://itunes.apple.com/nl/app/9292/id556557690)) and Google Play ([GVB](https://play.google.com/store/apps/details?id=nl.moopmobility.gvb&hl=en)) & [9292](https://play.google.com/store/apps/details?id=nl.negentwee&hl=en)) store. Other apps (like Google Maps) have great integration as well.
+
+##### A note to out of towners in in regards to obtaining a reloadable card for public transportation.
+
+You can purchase an "OV chipkaart" at Amsterdam Centraal and most large metro stations (including Schiphol). Note that the unattended machines do not handle non-EU issued (e.g. Chip+Signature) cards well. Some U.S. Credit Unions now offer Chip+Pin technology on their *debit* card (note: not *credit* card). If your card doesn't work or want to use Euros (other than coins), there is a customer service center located on the "IJ side" of Amsterdam Centraal where you can purchase a chipkaart in person at the [Service Office](https://www.nsinternational.nl/en/tickets-services/opening-hours-ticket-and-service-shops "Link to NS International Service Office"). If you're arriving via Schiphol - a similar service is offered in the main train hall
+
+#### Alternative methods of transportation
+- [Uber](https://www.uber.com/)
+- [Rent A Bike](http://www.iamsterdam.com/en/visiting/plan-your-trip/getting-around/rental/bike-hire)
+- And if you want must -- [Taxis](http://www.iamsterdam.com/en/visiting/plan-your-trip/getting-around/taxis)
+
+
+### Accommodations
+Amsterdam has amazing hotels and incredible amount of Airbnbs spread out all over the city that allows you to experience life as an Amsterdammer (Beware of the dark red bike paths!). Besides Airbnbs, here is a list of hotels that are near to the [Pakhuis de Zwijger](http://www.dezwijger.nl/ "Website of Pakhuis de Zwijger").
+
+* [Mövenpick Hotel Amsterdam City Centre](http://www.movenpick.com/en/europe/netherlands/amsterdam/hotel-amsterdam/overview/)
+* [DoubleTree by Hilton Hotel Amsterdam Centraal Station](http://doubletree3.hilton.com/en/hotels/netherlands/doubletree-by-hilton-amsterdam-centraal-station-AMSCSDI/index.html)
+* [Hotel NH Barbizon Place](http://www.nh-hotels.nl/hotel/nh-collection-amsterdam-barbizon-palace)
+* [Inntel Hotels Amsterdam Centre](http://www.inntelhotelsamsterdamcentre.nl/)
diff --git a/exampleSite/content/events/2017-amsterdam/program.md b/exampleSite/content/events/2017-amsterdam/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-amsterdam/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+
diff --git a/exampleSite/content/events/2017-charlotte/program.md b/exampleSite/content/events/2017-charlotte/program.md
new file mode 100644
index 000000000..f7ef83e16
--- /dev/null
+++ b/exampleSite/content/events/2017-charlotte/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "program"
+type = "event"
+
++++
+
+
+Charity Majors is the cofounder and CTO of Honeycomb, a new startup focused on mining machine data. Previously, Charity ran infrastructure at Parse and was an engineering manager at Facebook. She also worked with the RocksDB team to build and deploy the world’s first Mongo + Rocks in production. Charity likes single malt scotch.
+
+
+
+
+
+___[Marion Oliver McCaw Hall](https://www.mccawhall.com/plan-your-event/event-spaces/nesholm-family-lecture-hall) at Seattle Center is the region’s premier performance venue.___
+
+McCaw Hall opened in June 2003 as a $127 million renovation of the Seattle Opera House, made possible by a partnership between the Hall’s two world-class resident performing arts tenants, Pacific Northwest Ballet and Seattle Opera, along with Seattle Center and the Seattle Center Foundation. This partnership secured $55 million in public funds and over $72 million in private philanthropic gifts to make the Hall a reality. The Hall is owned by the City of Seattle and operated by Seattle Center, in accordance with a unique 25-year Operating Agreement with its resident tenants, which provides them with on-going oversight and shared responsibility for its operations and budget.
+
+
+
+McCaw Hall encompasses the state-of-the-art 2,900-seat Susan Brotman Auditorium, the 380-seat Nesholm Family Lecture Hall, Prelude Café, elegant lobbies fronted by a luminous five-story serpentine glass wall, two beautiful donor/special function rooms, and a 17,800-square-foot public plaza (the Kreielsheimer Promenade) that serves as an entry into McCaw Hall and the Seattle Center campus. Designed by local architectural firm LMN, the Hall’s design emphasizes elegance balanced with flexibility and functionality. Its open, airy lobbies strive to minimize the separation between exterior and interior, inviting the community to view and join the anticipation of audiences prior to a performance. As well, the Hall incorporates a number of environmentally sustainable design features which minimize its use of resources, waste generation and carbon footprint.
+
+
+
+Each year the Ballet and Opera present approximately 150 performances in McCaw Hall. In addition, the Hall hosts two productions of the Seattle Men’s Chorus annually, as well as a wide range of popular music concerts, lectures, corporate meetings, receptions, weddings, festival performances, community, and non-profit events.
+
+
+
+
diff --git a/exampleSite/content/events/2017-seattle/program.md b/exampleSite/content/events/2017-seattle/program.md
new file mode 100644
index 000000000..22d161fea
--- /dev/null
+++ b/exampleSite/content/events/2017-seattle/program.md
@@ -0,0 +1,348 @@
++++
+date = "2016-03-06T21:28:07-06:00"
+title = "DevOpsDays Seattle 2017 Program"
+type = "event"
+
++++
+
+
+
+We're very excited to bring DevOpsDays back to Seattle in 2017. This year the event will be held at
+{{< event_link page="location" text="McCaw Hall" >}} in the Seattle Center. This theater style venue
+will be great for both speakers and attendees.
+
+
+
+
+
+
+
+
+
+
+
+
+
+Open Space Mechanics
+
+Since the meeting is supposed to be self-organizing, the conveners put their energy not in running the meeting but creating a setting that gets everyone’s creative energy flowing.
+
+Opening:
+
). This gives conveners an idea of how busy their session is going to be. It gives participants an image of how the break-out session is going.
+
+People may shuffle sessions around, or merge sessions as they are deciding where to go. Have a wiki where people can record outcomes of sessions, or provide paper forms for note-taking during sessions (recording who attended, a summary of the session and outcomes/questions for further work) that you can collect into a ‘book of proceedings’.
+
+The facilitators’ role in this bit of the conference is to answer questions, and make sure everyone has the materials they need to run their break-out session. They do not (in principle) intervene in the sessions - the participants are supposed to self-organize.
+
+Closing:
+Have everyone back in the circle. A simple and effective way to close is to have the participants pass a ‘talking stick’ around, and let them (briefly, e.g. in a sentence or a word) say what they feel about the day.
+
+Bumblebees and butterflies:
+Bumblebees internalize the law of two feet quickly, and constantly flit from meeting to meeting, pollinating, cross-fertilizing, and adding richness and variety.
+
+Butterflies may never get into any meeting. They are focal points of quiet and beauty. If you watch them, every once in a while you'll see them engage in conversation. Those conversations often are significant.
+
+(from Pono consultants)
diff --git a/exampleSite/content/page/organizing.md b/exampleSite/content/page/organizing.md
new file mode 100644
index 000000000..09ce5c5ea
--- /dev/null
+++ b/exampleSite/content/page/organizing.md
@@ -0,0 +1,522 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2015-11-22T01:21:47-06:00"
+title = "Devopsdays - Organizing Guide"
+aliases = ["/pages/organizing/"]
++++
+
+---
+
+## Introduction
+Congratulations! The fact that you have reached this page means you at least have an interest in spreading the devops love to the world. Back in 2009 when we organized the first event, we were probably as excited as you are now. But we were also bit scared and full of questions: how does this work? how do we get sponsors? what is the first thing we have to do?
+
+Years later, we can offer some advice from our experiences. Even though every event is a bit unique in its own way, we've come to a more or less standard approach for organizing these events. With this document we want to support you and make you feel at ease in organizing one yourself. Don't worry; we'll be there along the way!
+
+We recommend that at least one person on your team attend another devopsdays first, and then get in touch with the [core organizers](/contact) to tell us about where you'd like to organize your own!
+
+---
+
+## Assembling a team
+
+In the devops spirit of collaboration, find people in your region that want to help you run the next awesome event.
+
+- Talk to people at your local devops or related community meetups.
+- Tweet that you'd be interested in running one in your region. (Use the #devopsdays hashtag.)
+- [Email the global core organizers](mailto:info@devopsdays.org) and we'll try to connect you to other people in your region
+
+You're going to need people from different organizations on your local organizing team, so you have a broader base of support and involvement from the community.
+
+---
+
+## Website, Email, and Slack
+
+When you have your initial team, [email the global core organizers](mailto:info@devopsdays.org) and we'll schedule a kickoff meeting with you. After chatting, we'll set up the @devopsdays.org mail aliases for your team. This will let you have a standard email for organizer contact and proposals. We'll also invite you to the Slack team so you can meet other organizers and share ideas. (Slack has an XMPP gateway if you'd prefer that.)
+
+We prefer the city name for the actual email and site. Wider regional terms are less preferable since someone in a nearby city may want to have a devopsdays in a following year. Fun nicknames require too much dereferencing of pointers and so are best kept for slogans and t-shirt designs.
+
+One thing you'll want to do as soon as possible is get your event listed on the website by submitting a pull request to https://github.com/devopsdays/devopsdays-web. The most up-to-date instructions can always be found on that repo's [README](https://github.com/devopsdays/devopsdays-web/blob/master/README.md).
+
+It's fine if you just list the organizers, the city, and say "coming soon". You don't have to have the date & venue set or open registration & the CFP right away.
+
+The [devopsdays code of conduct](/conduct) is based on the one from the [Geek Feminism Wiki](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) as well additions by Andrew Clay Shafer for [devopsdaysPGH 2014](/events/2014-pittsburgh/conduct/). You will need to have a code of conduct before your initial pull request will be merged.
+
+---
+
+## Rules
+
+Every devopsdays event is different, but there are a few rules to keep in mind if you'd like your event to be listed on devopsdays.org:
+
+- Inclusiveness and respect for differences are core devops values, and we invite you to help us make each devopsdays event a place that is welcoming and respectful to all participants. Your event will need to have a code of conduct.
+- These are community events, so your event must have an open call for proposals and accept registrations from the general public. Internal devops events focused on a specific organization or curated events with all speakers privately selected are wonderful and we encourage them, but they won't be listed as "devopsdays" events on this site.
+- These events are not for individual or corporate profit. If you have money left over, you can use it for your next event, to help other devopsdays events directly or via sending participants, or for [charity](/devops-gives-back/). The global core team does not have any ability to accept your money, but neither should it be making its way into anyone's pockets.
+- Sponsors are much appreciated for their financial assistance, and they are welcome to participate in devopsdays events. They are never given attendee contact info by a devopsdays event's organizers, nor are they allowed to purchase speaking slots for talks or ignites at a devopsdays.
+
+---
+
+## Handling Money
+
+Part of organizing the event is handling of the local event's money. This will be needed for:
+
+- Invoicing sponsors and accepting their payments.
+- Accepting money from and (as needed) sending official invoices to people that register
+- Paying suppliers like the venue, catering, T-shirts, etc.
+
+You cannot announce a date until you know you have a way to handle money. Realizing too late that you cannot process money has led to rescheduled or canceled events in the past.
+
+The way many events have handled this is to find a local company that is willing to handle these logistics. In some countries, a local company is the only way to handle taxes. Some events register a local not-for-profit entity; there is no such central entity.
+
+Depending on the size of the event, you might want to give them a Silver or Gold sponsorship in return. Make sure they understand they will need to generate invoices and accept/make payments with a fast turn-around.
+
+If a local company is not an option, we've worked with a few companies in the past that are willing to help you for a fee:
+
+- US Based: Laura from Conference Ops
+- EU Based: Bernd from Netways
+
+If you would like to use this method, contact us to get more details.
+
+To make invoicing smooth, it helps to use that company's paypal account for registration (on eventbrite or equivalent) and to use paypal (or equivalent) buttons generated by them for sponsor packages.
+
+---
+
+## Selecting a date
+
+Now that you have assembled your team, the next step is choosing a date. We usually take the following into consideration to find a good date:
+
+- Avoid overlapping dates with other devopsdays, especially nearby. We want to spread the events out; think of it as loadbalancing. All devopsdays events with their dates scheduled will be shown on the front page of [devopsdays.org](/).
+- Avoid overlap in dates with other important local events: with other events happening at the same time, your attendance rate might be affected negatively
+- 'Piggyback' after/before other events: it's a great way to get started, and as people might have traveled already, they can be potentially be interested in a pre or post event conference
+- Take a look at the [devops conferences site](http://devopsconferences.org/) so as to avoid accidentally scheduling during a time it may be more challenging to get the speakers and sponsors you want.
+- You cannot announce a date until you have two things: an agreement with a venue, and a way to handle money.
+- Look at a few two-day choices you can accept. When talking to a venue, you might find that they can accommodate you better during some parts of the week than others. Sometimes they may be fully booked a given week, but available the next.
+- Consider that if you schedule one or more day on a weekend, you are likely to see a significant drop-off of attendance on the weekend day(s). DevOps is part of people's work life, and the weekends are typically used for refreshing energy with family. We recommend choosing weekdays.
+
+---
+
+## Budgeting
+
+Your budget is going to be refined and adjusted as you determine how many attendees you think you'll get and how much you're going to commit to spending up-front. You're not going to know all these numbers immediately, but it's valuable to start thinking about them as you're choosing a venue.
+
+Categories to consider:
+
+Income:
+
+- Sponsors (could be up to 75% of your income, depending on sponsorship levels)
+- Registrations (make sure to set this such that you're covering per-attendee costs)
+
+Expenses:
+
+- Venue for talks & open space discussions
+- Internet for attendees
+- Livestream/recording of talks
+- Catering for breakfast/coffee breaks/lunches (some venues require the use of their caterer)
+- Evening event
+- T-shirts/other swag
+- Badges/lanyards
+- Signage
+- Speakers dinner
+- Speaker gifts (small token)
+- Insurance/taxes
+- Payment for accounting services
+
+---
+
+## Selecting a venue
+
+When you have some idea of when you want to run and how much you want to spend, you can start talking to potential venues.
+
+Venue space considerations:
+
+- A (big) room where everybody can sit comfortably and listen to the talks. This of course depends on the number of attendees you expect. Events have ranged from 70 to 700 people. Assess the numbers usually attending your best-attended local meetups; you might get 2-3x that.
+- A number of break-out rooms for the afternoon sessions:
+ - it's nice to be able to put the chairs in a circle for better discussions
+ - you can be creative by splitting the big room in smaller rooms but in practice, separate rooms are less noisy
+ - we usually go for a few smaller (10-20) and few bigger (20-40) rooms
+ - it's helpful if the rooms are close to one another, making it easier to move between open space rooms.
+ - you can use the big room for open space too
+- Room to hang out: not everybody attends sessions, and some are more interested in the hallway track. If there is some room for the food or a quiet room that's a plus.
+- Sponsor space: Gold sponsors (at a minimum) get a table to have a presence. Make sure they have a nice spot at the event (typically close to the food or hangout space).
+
+Aside from having enough space, there are other things to consider:
+
+- Is the venue easily reachable by public transit and/or does it have sufficient parking, depending on the transit options in your local area?
+- Are there (affordable) hotel accommodations nearby? (Running the event in a hotel makes it easy for out-of-town guests.)
+- Does the venue allow for catering by other parties, or what are the options for food?
+- Does the venue have enough wifi/internet capacity, or can more be added? Attendees will likely expect it.
+- Can the video be streamed with enough capacity (if livestreaming is an option)?
+
+A final big space differentiator is the pricing: as the price of devopsdays is typically relatively low, we look for affordable venue space:
+
+- looking for (free) innovation centers or educational venues (universities...)
+- finding local companies that can act as a host with their facilities
+- finding a host sponsor that is willing to pay for a venue for you
+
+Don't overcommit on the number of people coming and don't do a pre-payment for the venue until you must. The same goes for food: it's always easier to add a few extra plates as opposed to having too much food ordered.
+
+If you have some legal entity created for the event, have the details at hand (legal name, contact details, business number etc.). Some venues may require this information to put in a hold for your chosen date(s).
+
+---
+
+## Designing a local event's devopsdays logo
+
+The devopsdays logo with the gears in the brain has become recognizable for the overall devopsdays brand. For each individual devopsdays event you can take elements from the devopsdays brand logo. This is optional, but recommended. The goal should be to design something that denotes your city specifically.
+
+Note different existing logos:
+
+- [Seattle 2016 - Needle using the gears with a backdrop of mountains](https://www.devopsdays.org/events/2016-seattle/logo.png)
+- [Chicago 2016 - A local take on the gears in the brain](https://www.devopsdays.org/events/2016-chicago/logo.png)
+- [Cape Town 2016 - The characteristic Table Mountain skyline, using the gears](https://www.devopsdays.org/events/2016-capetown/logo.png)
+
+A simple exercise to do with your organizers would be to ask for one word descriptions of your city and then review and vote on the list.
+
+---
+
+## Announce your event
+
+Once you have a time and place, you can announce your event to the world! It's great if you've had a chance to open your CFP and registration, though those aren't essential to announce your dates.
+
+### Website
+
+Update your data file for your event to add your start & end dates; this adds your event to the map on the front page!
+
+### Twitter
+
+Tweet with the hashtag #devopsdays and if desired, set up an event-specific Twitter account such as @devopsdaysmsp. If you PR your event Twitter handle onto your site, your tweets will be included in the Twitter feed on devopsdays.org.
+
+---
+
+## Distributing the work
+
+On your local organizing team, it's best to discuss the following tasks. Of course this is not set in stone, but it helps for people to focus on different areas.
+
+- Person/Pair handling talk proposals
+- Person/Pair handling ignite proposals
+- Person/Pair handling website updates
+- Person/Pair handling sponsors
+- Person/Pair handling registration, invoicing, questions
+- Person/Pair handling venue, catering, local things, hotel
+- Person/Pair handling t-shirts
+- Person/Pair handling evening event logistics
+
+---
+
+## Call for proposals
+
+When you're ready to open your call for proposals, you'll want to include the date it opens, the date it closes, and the date by which people will be informed of your decisions. People will usually need at least 4-6 weeks to arrange for travel or time off, and you'll want your call to be open for at least a month, and you'll want at least 2 weeks to consider proposals and fill in any gaps. This means that you should open your CFP as soon as possible, and close it at least 6-8 weeks before your event.
+
+Set an official theme if one beyond "devops" is desired. Within the context of this theme (but other proposals can work too):
+
+- **no speaker spots can be bought by sponsors: not ever - period.**
+- encourage new content: if the content has already been presented/published online we will consider it but it's less attractive. We want to stimulate the creation of new content as much as we can, as part of the goal is to record and spread the ideas from these sessions
+- a good balance between local and out-of-town speakers. building the local community is just as important as bringing in new ideas from the wider community.
+- favor new speakers: devopsdays is a supportive environment to encourage new voices in our space
+- encourage bold subjects: we don't want to hear the same things over and over, do we? This avoids us becoming an echo-chamber of ideas
+- shy away from specific technology/product talks: always try to elevate it to the conceptual part
+balance between technical and cultural content: for specific tools talk, there are open spaces not the main conference talks
+
+Events usually have 4 30-min talks per day + ignite talks. Open space sessions are scheduled during the conference, not ahead of time.
+
+For people to respond to the call for proposals we create a specific address (proposals-yourlocation-year@devopsdays.org). You can also use a third-party CFP tool.
+
+Keep in mind that under-represented people in tech are much less likely to respond to your CFP. If you would like to encourage diverse viewpoints from voices other than those you hear the most often, you will need to reach out into those communities and encourage participation.
+
+Talk selection doesn't have to be finished when you announce a schedule; it's ok to leave to space until the end. Still, we found that a finished schedule helps for attendees to make the case for them to attend. Remember that announcing only a few speakers can lead to unwarranted assumptions about your demographics.
+
+Don't be surprised if proposals don't flow in quickly at first. People usually wait a bit before sending them in and need some extra calls. It's good to have a backup plan and contact individual speakers as well. You're not required to create your schedule solely from responses to your CFP. You should also provide speaker support according to your budget; at a minimum, all speakers should receive a free event ticket.
+
+It works best if you dedicate a person/pair to respond to proposals/speakers and handle communication. This is best for both ignite and conference talks. While your local team is going to select your event's talks, the core organizers may weigh in to help you make a more balanced schedule having less overlap with other devopsdays.
+
+---
+
+## Sponsorship packages
+
+Overall [guidelines for sponsorship](http://www.devopsdays.org/sponsor/) are available. Sponsor packages are decided upon by the local organizing team for a city. The global core team does not offer sponsor packages, so any sponsors will work directly with the devopsdays event(s) they'd like to sponsor. You can use the examples in the template to help you make your decisions. Here are some typical offerings:
+
+- Host (cost of venue): if a company sponsors the venue/food they will be acknowledged as a Host sponsor. Their logo will be directly visible on the main event page. They also have the opportunity to do a pre/post event meetup that will get promoted. And of course they get the same benefits as Gold and Silver sponsors
+- Gold (around 5000 Euro/USD): 6 included tickets + a 'promo' spot during talk intermissions + the ability to have a simple table/sponsor presence at the venue.
+- Silver (around 3000 Euro/USD): 4 included tickets, sometimes half a table depending on the local event's choices, sometimes just a single shared swag table.
+- Bronze (around 1000 Euro/USD): 2 included tickets, sometimes can leave stickers/flyers/etc in public spaces
+- Community Sponsor: get logo on the site and acknowledgement on social media. Used for media outlets and other conferences that are interested in cross-promotion with you. Sometimes they'll provide giveaways; usually you will not ask them to provide cash.
+
+We want to avoid the traditional high-priced model for sponsors. We believe that the more companies that sponsor, the better: it amplifies the ideas and shows that many companies subscribe to the devops idea.
+
+We believe the pricing is low compared to the value sponsors get compared to what other conferences are charging. Also, you may want to refrain from deviations from the standard package. Exceptions take extra CPU cycles. Best to be avoided.
+
+Other offerings might be:
+
+- A lanyard sponsor
+- An evening event sponsor
+- A lunch or breaks sponsor
+
+As a reminder:
+
+- we do NOT offer speaker slots in return for sponsorship, and we want to maintain a standard policy on the pricing inside a given event.
+- we do NOT ever sell contact details of attendees. You can share demographics in aggregate to give sponsors a feel for what kind of crowd will attend.
+
+---
+
+## Finding/Handling Sponsors
+
+Sponsors pay the bills. You rely on them. So what can you do to find them and keep them satisfied?
+
+- post on Twitter and other social media
+- find local meetups/companies that can help you
+- if you're looking for a contact of a specific company that sponsored before, ping the devopsdays core organizers to see if they can help.
+- talk to the other organizers on Slack - many of them work at sponsors!
+- write a blog on the website to promote your event.
+
+Sponsors will usually ask you the following; best to have this information ready.
+
+- Projected number of attendees
+- Industries/Companies represented (share only in aggregate)
+- What they get with what level of sponsorship (refer them to your sponsor page)
+- If they can buy a speaker spot (NO, but they can submit a talk, ignite or open space topic)
+- If you provide a badge-scanning mechanism (no)
+- If they will have electricity & network at the venue
+- If they can get a monitor (let them bring their own or rent one themselves)
+- Where to ship their stuff and pick it up (don't take responsibility and let them handle that directly with venue)
+- What size of table they have? Find out from the venue and say it has to fit behind the one table
+- Where their table will be located (produce a map and let them choose in the order they signed up)
+
+From experience, we found that it helps to have a single local organizer act as the contact with the sponsors to track prospects, payment, and giving them discount codes.
+
+When they sponsor they need to supply:
+
+- a logo for the website
+- a URL to link it to
+- an email address of a contact you can reach
+- a Twitter handle for you to thank (optionally)
+- the invoice details (including VAT in Europe)
+
+In return you'll :
+
+- put the logo online
+- link it on the website
+- send the official invoice (as applicable)
+- once payment has been received, provide the registration discount code
+
+On the registration page, have them select the special sponsor ticket with their discount. Many of the sponsor contacts are traveling from event to event, you'll have to follow up with them a bit so they sign up their crew in time for your badge printing. Make sure you make the invoices "due on receipt" or provide Paypal links so sponsors don't wait months to pay you.
+
+
+---
+
+## Tickets and pricing
+
+We want to ensure that anyone who's interested in attending a devopsdays is able to, and that price is not a barrier. So, you'll want to keep your prices relatively low compared to many industry conferences.
+
+### Free registration
+
+Experience has taught us that 'free' events come with a cost:
+
+- about 30-40% of the people 'grabbing' a free ticket don't show up in the end
+- this makes it harder to plan logistically: how many people will actually show up?
+- people who could have attended are left out because the event appears 'full'
+
+### Minimal Cost
+
+Asking a minimal fee (covering about food cost for two days - about 100USD or 100 Euro) gives us the best of both worlds:
+
+- The numbers are more accurate that way and more people feel happy about it.
+- The financial risk for venue/catering cost is spread
+
+The downside is that this will require 'official' invoices:
+
+- It requires time to create the invoices (although it's pretty much automated if you use [http://eventbrite.com](http://eventbrite.com))
+- It might cost some accounting time because of the administration
+- Specifically in the EU region:
+ - if a EU company organizes an event in another country, it will have to request a Tax-ID in that other country. The costs of doing that would take a significant portion of the event money.
+ - charges for the event needs to be in the currency of the country where the event will take place
+
+Bottom line: if you want to charge a fee (which gives you better financial protection), make sure you have considered that in your handling of the money.
+
+To encourage people to register early it's advised to offer discounted **early-bird** registration.
+
+Because getting time away from work may already be a barrier for under-represented people in tech, offering free tickets to those individuals may make it more possible for them to secure workplace buy-in on their participation. If your budget has room, this is a good place to spend some of the extra money. Be sure you comply with all local laws that may apply in regards to demographic information and the uses thereof.
+
+---
+
+## Setting up registration
+
+Once pricing has been decided you're ready to set up registration. We've had good experiences with [Eventbrite](http://www.eventbrite.com) integrated with [PayPal](http://paypal.com) payments. The paypal account for payment needs to be linked directly to the company that does the invoicing.
+(Note: if using Eventbrite, use Paypal, not "Eventbrite payment processing", or you'll have to wait for Eventbrite to disperse funds after your event.)
+
+The core organizers will not run registration for you, but we can suggest things that will be useful to you in your registration process.
+
+Specifically on eventbrite we usually:
+
+- ask for employer name (optional) if people want it printed on their badge
+- ask for Twitter handle (optional) to help attendees connect with one another
+- ask for T-shirt sizes (make sure you offer more than S-M-L-XL "unisex")
+- (in Europe) ask if they require an invoice; if yes ask more details like VAT number if needed
+- ask if they are interested in attending the evening event on the first night (optionally)
+- disable the facebook integration
+- don't allow people to see who is coming
+- set up hidden ticket types for sponsors, organizers, speakers, etc
+- create access codes for hidden ticket types
+
+*Attendee email or direct-contact information should never be visible on the website or given out to vendors.* We value privacy and anti-spam a lot!
+
+---
+
+## Setting your program
+
+We recommend a two day single-track program with the following structure:
+
+- talks in the morning: this follows the traditional format of a speaker or panel
+- There is usually an introduction of about 15 minutes at the beginning of the conference from the organizers
+- We find that talks of about 30 minutes have the right balance for content.
+- You'll want to let the Gold sponsors speak for a minute between the 30-minute talks as that gives presenters time to set up their laptops
+- allow for rest and discussion breaks
+- You may break for lunch before the Ignite talks if that works best for your schedule.
+- You'll have a set of several ignite talks: 5 minute talks with 20 slides that auto-advance (More detail on Ignite format)
+- openspaces in the afternoon: a self-organizing part where everybody gets to propose a session (More detail on OpenSpace Format)
+
+We provide a sample schedule in the event template.
+
+You can usually draw on different sources to get speakers:
+
+- the call for proposals
+- ask on Twitter for people to retweet your CFP announcement
+- reach out to local meetups and organizations
+- contact desired speakers directly
+
+A few words of advice:
+
+- No sponsor should be able to buy their way into the program. The schedule should be decided by your local organizers.
+- Usually you will receive more tools talks vs cultural talks. We believe it's important to keep the balance right.
+- Tool talks should be at the conceptual level, not at the individual day-to-day level
+- We prefer new speakers to come on board
+- We prefer new content that was not presented yet (or was already recorded)
+- Avoid inviting only prominent out-of-town speakers; we need to make sure that local content/ideas get picked up and spread to the community
+
+---
+
+## T-shirts and other swag
+
+Printing shirts is entirely optional. Some events choose to donate to charity instead, while others go with a different kind of swag. If you decide to do shirts, bear in mind that at registration time, attendees can help you know what their body shapes and sizes mean for their preferences. Ask! Do not just guess, or you will find you've inadvertently made some attendees feel excluded.
+
+While some shirt styles only go to 2XL, there will be attendees who (given the option) will choose 3XL, 4XL, or 5XL. Women will sometimes be happier with a fitted shirt (which is not the same as a "girl" shirt - those are typically a "junior" size). Avoid making your extended sizes and your fitted shirts significantly different from the "S-2XL unisex" shirt in color or design.
+
+Keep in mind that you want your design to be appealing on a wide range of humans, not just those who happen to have smaller torsos without many curves. If you want soft, comfortable shirts that can fit many people, consider something like a tri-blend instead of a 100% cotton shirt.
+
+If you're ordering shirts a few weeks before your event, consider padding the counts by up to 30% of each size/style. Having a few extra shirts is way better than anyone going home sad.
+
+You may also want to order stickers or other items. Give yourself plenty of lead time.
+
+---
+
+## A word on hotels
+
+There will almost certainly be a few speakers and sponsors who will travel to your event and will appreciate having a discounted rate at the most conveniently located affordable hotel you can manage.
+
+If you're holding your event in a hotel, they will likely give you a "courtesy" room block that guarantees a discounted rate for your attendees.
+
+If you're not using the hotel's meeting rooms and catering, they may want you to guarantee at least 80% or so of the room nights you block off for your group will be used. This isn't as risky as it sounds if you want to start with a very small block (5 rooms or so, for the night before day one and the night between day one and day two - don't expect people to stay overnight the evening of day two). Usually the hotel will also let you add more rooms to the block as it fills.
+
+If you make your group rate code available on your website, keep on eye on who registers with it (the hotel should be able to provide this info), and ensure that you have enough space for all the out-of-town people you expect. You may have to remind some people to register, as the group rate usually expires a month or so before an event.
+
+---
+
+## Venue logistics
+
+You will want a local organizer acting as the primary contact person with the venue. You will need to arrange things like the chair layout, table arrangement, audio-visual needs, etc. The catering deadline (by which time you'll need to provide numbers) is usually a couple weeks or so before your event.
+
+Make sure you ask the venue how soon sponsors can start shipping items there, get the correct address/routing info, and ask what fees they might incur. Find out exact times you'll have access to your space, and find out whether you'll have secure overnight storage (because both you and definitely the sponsors will need that).
+
+Your venue may require some form of insurance. See what they require, and look into something like TULIP event insurance depending on what's available for your local area.
+
+You will want some members of your local organizing team to be tasked with...
+
+- finalizing venue details
+- running the registration check-in desk
+- preparing and posting signs
+- printing and assembling badges
+- etc.
+
+---
+
+## Evening event
+
+Most devopsdays host a social gathering the evening after the first day of the two-day event. This is a great place for attendees to get to know one another better. There's some sort of food and drink, but usually a full dinner is not provided. Having fun activities to participate in (bowling, trivia, other games, etc) is recommended. While alcohol is enjoyable, it should not be the only activity, and it's important to remember the needs of attendees who aren't choosing to drink alcohol. It's also not required for your event to pay for any alcohol; if it's not free, it is more socially acceptable to refrain from choosing it.
+
+Often the evening event will be at a different location than the venue for the talks. It's a good idea to make it within walking distance or provide transportation if possible. Running it at the same venue can lead to higher attendance, especially if you provide some content such as the Ignite talks.
+
+Offering a family-inclusive evening event will allow more people to participate; unlike at a destination conference, many local devopsdays events occur within commuting distance. While people who work outside the home typically have a daycare arrangement in place, it probably does not extend into the evening.
+
+---
+
+## Running registration
+
+You are going to want a place where people can check in and get their badges when they arrive. They may also pick up T-shirts there. If you use Eventbrite, there is an app which makes check-in much easier than using paper, but it may not be necessary to do more than just give the badges out (as you can see which ones are left at the end.) Sort the badges ahead of time alphabetical by last, then first name. If you separate out the sponsor ones, keep in mind that some people might not realize if they fell into the "sponsor" tickets or a "regular attendee" ticket according to how their company registered them.
+
+Sort shirts by style and size, and then let attendees just tell you which size they wanted. If you built in enough margin of error, this won't cause any problems and will be the most efficient way to deal with it, rather than looking up what they ordered.
+
+You may want to staff the registration desk at all times if you want to be able to help attendees with their questions. As the conference organizers may want to attend talks, it's wise to call in favors from friends and family who aren't interested in the subject matter of the talks and won't mind missing them all. Make sure any such staff have a way of getting ahold of the organizer on duty for any questions they can't answer on their own.
+
+---
+
+## Video - recording and streaming
+
+Whether or not you're able to livestream, it's important to record all the talks. This is invaluable for your speakers, and it's great for the community. Your audiovisual company should be able to provide a camera or cameras and record the feed off the board into a computer. If you have no budget for recording talks, a smartphone is better than nothing.
+
+If you're going to livestream, rehearse ahead of time, and then assign at least one person to run it during the event.
+
+- For past events we have used [livestream](https://new.livestream.com/live-video-tools#mobile-broadcasting). The software can be installed on Windows or OS X.
+- You may need [producer software](https://new.livestream.com/producer/software).
+- You can create a free account at livestream to experiment. Create it as **new.livestream.com** and NOT at livestream.com.
+- We have mainly used it on a Mac; there, it will read any video device supported and record it both on your local computer + stream.
+- Find out if you can hook up your camera equipment directly to a computer and have the software detect it.
+
+---
+
+## Running the event itself
+
+- Prepare and share a team playbook of exactly what is scripted to happen when.
+ - Assign one or more MCs to kick off and orchestrate the event
+ - Assign people to introduce specific speakers
+- Consider assigning "on duty" shifts so one person isn't the SPOF for all last-minute decision-making in crisis mode
+
+---
+
+## Running Ignites
+
+Running Ignites can be a challenge: people tend to submit them last minute, or they didn't understand the format too well. Here are few tips on making this process run more smoothly:
+
+- Require the Ignite presenters to send the slides ahead of time
+- Inform the Ignite presenters that there are no presenter notes during their talks
+- Animations (gifs or slide transitions) and videos may not work due to the conversion process
+- PDF is the easiest format to collect all presentations
+ - An option is to use a Dropbox shared directory
+- You can run either :
+ - `impressive -a 15` [http://impressive.sourceforge.net/](http://impressive.sourceforge.net/)
+ - Adobe Acrobat Reader in [auto-advance mode](http://malektips.com/adobe_reader_7_0019.html); ask presenters to add empty slide to the end as Reader doesn't exit after last slide
+- Don't let them run on their own laptops
+- Use a dedicated laptop (avoid any popups etc...)
+- Mention again on the day itself.
+ - "Just so you know, your slides will auto advance every 15 seconds; you can't advance them yourself"
+ - Remind the presenters again that there are no presenter notes
+- Have Ignite presenters queue next to the stage and either:
+ -start the slidedeck for them.
+ - or even build all slides in Slidedeck and build in a bio slide as a interludium and have that autoadvance as well
+
+[Ignite format page](/ignite-talks-format/)
+
+---
+
+## Running Open Space
+
+There is a wealth of detail on the [Open Space format page](/open-space-format/). Consider both a physical schedule grid and an easily-updated shared spreadsheet you can link from your event page. Also consider posting the open space choices for a specific room outside that room.
+
+---
+
+## Website updates
+
+- The core organizers want the devopsdays website to be a central reference for all content produced during your event.
+ - Embed links to each of your speakers' slides on your program page. (Ask them to post slides on slideshare, speakerdeck, etc.)
+ - Upload the videos to youtube or your video site of choice, then embed them on your program page.
+- Surveying your attendees and blogging about the results is optional, but strongly recommended.
+
+---
+
+If you have further questions, chat with the other organizers on Slack, and have fun! It's going to be great!
diff --git a/exampleSite/content/page/privacy.md b/exampleSite/content/page/privacy.md
new file mode 100644
index 000000000..8e8d29b95
--- /dev/null
+++ b/exampleSite/content/page/privacy.md
@@ -0,0 +1,10 @@
++++
+Categories = []
+Description = ""
+Tags = []
+date = "2016-08-19T18:40:18-05:00"
+title = "Privacy Policy"
+
++++
+
+{{< privacy_policy >}}
diff --git a/exampleSite/content/page/speaking.md b/exampleSite/content/page/speaking.md
new file mode 100644
index 000000000..d409f9104
--- /dev/null
+++ b/exampleSite/content/page/speaking.md
@@ -0,0 +1,11 @@
++++
+date = "2015-11-29T00:00:00-06:00"
+title = "speaking at devopsdays"
+type = "cfp"
+
++++
+
+The call for participation for a devopsdays event helps each city's local organizers find speakers for their event. Follow the talk proposal submission process for a given city if you'd like to submit an idea to their CFP!
+
+These are the cities which currently have an open call for participation.
+
diff --git a/exampleSite/content/page/sponsor.md b/exampleSite/content/page/sponsor.md
new file mode 100644
index 000000000..cca6dd120
--- /dev/null
+++ b/exampleSite/content/page/sponsor.md
@@ -0,0 +1,57 @@
++++
+Categories = []
+Description = ""
+Tags = []
+Date = "2016-05-03T13:04:25-05:00"
+Title = "Sponsor devopsdays"
+
++++
+
+Devopsdays is a community-organized not-for-profit conference series for practitioners. It began in Ghent, Belgium with one conference in 2009, and has grown to more than 30 events planned worldwide for 2016.
+
+Sponsoring devopsdays conferences gives your organization an opportunity to speak with practitioners, managers, and executives from companies of all sizes and industries. Whether your goals include recruiting new talent, opening new markets, or connecting with your existing customers, this event will be the place to have those conversations with experts and leaders in tech innovation.
+
+
+**Code of Conduct**
+
+All devopsdays events have a code of conduct and require sponsors to follow it. This applies to giveaways, items and images at your table, behavior of your staff, etc. See the specific city's site for the details of their code of conduct.
+
+
+**How to sponsor**
+
+All devopsdays events are independently organized. No multi-city sponsorships are available; when you decide which cities to sponsor, you need to contact each city's organizing team individually.
+
+Events set their own rates and can tell you about their expected attendance in terms of numbers and communities represented. Sometimes they will offer additional special sponsorships for more visibility, such as lanyard, evening event, etc. They typically are charging exactly what they need to run the event; nobody's making any money off these events, so discounts are generally not available.
+
+The vast majority of events do not have a legal tax-deductible status. Most sponsors fund this sponsorship either out of their marketing budget or recruiting budget, depending on their goals for sponsorship. Because these events are organized by volunteers who usually have no legal entity, contracts are generally not used. However, most events employ some form of professional accounting, so you usually have the option of paypal/credit card or invoice followed by check or bank transfer.
+
+
+**Staffing & participation onsite**
+
+Most sponsorship packages include a number of conference tickets for you to send employees. If you're sponsoring at a level which comes with a table presence, you'll need to line up people to staff it. Since traffic at the table is minimal during the single track of talks in the morning, they can attend the talks and then take turns staffing the table versus attending participatory breakout sessions in the afternoon.
+
+Most devopsdays conferences also include an evening networking event, which is a great place for informal continued conversations.
+
+If your goal is recruiting, consider sending engineering managers. If you are a vendor, send your sales engineers as well as your technical product marketing, and even some engineers.
+
+All attendees including sponsors are welcome to propose any subject they would like to discuss in a group, during the afternoon proposals of breakout discussions known as "open space". Sponsors are encouraged to actively participate and engage with the other attendees as peers.
+
+Demos at your table are one good way to show off your org. It's usually possible to bring or rent monitors, though be sure to check with a given event about the exact mechanism at their venue.
+
+You don't need to ship your own booth or tables; devopsdays will provide table and chairs corresponding to your sponsorship level. You'll likely want to ship a table cloth, banner/background, giveaways, etc.
+
+
+**Speaking & Attendee contact info**
+
+Devopsdays does not sell conference speaking slots; sponsors' employees are welcome to submit talk proposals in the same call for proposals as anyone else. The talks are videorecorded and freely available online after the fact, and occasionally livestreamed, which is a great takeaway for the speakers and their orgs. Most events have an opportunity for sponsors to make a short elevator pitch for their services (generally in the order of a minute or two); this makes it to the livestream but usually not into the edited recordings.
+
+Devopsdays does not ever distribute attendee contact information. Do not expect badge scanning of any sort. Most events don't even collect information about job title. _Sometimes_ company affiliation is on the badges, and sometimes it's not.
+
+If you want to collect leads, you'll have to talk directly with individuals and request their contact info. Vendors also often raffle off prizes ranging from large Lego sets to tablets and other desirable items, collecting contact info in the process.
+
+
+**When will a devopsdays conference happen in some specific place?**
+
+New cities start a devopsdays event each year, and some cities run regularly. When planning out your sponsorship budget for the year, it's a good idea to assume that at least one or two must-sponsor devopsdays will crop up after you've already starting reaching out and sponsoring the early announcers.
+
+If one hasn't happened near you, and you wish it would, you can always look into [running your own event](/pages/organizing)!
diff --git a/exampleSite/data/events/2017-charlotte.yml b/exampleSite/data/events/2017-charlotte.yml
index 89a792b53..113481491 100644
--- a/exampleSite/data/events/2017-charlotte.yml
+++ b/exampleSite/data/events/2017-charlotte.yml
@@ -1,7 +1,6 @@
name: "2017-charlotte" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Charlotte" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
@@ -21,10 +20,11 @@ location: "Mint Museum Uptown" # Defaults to city, but you can make it the venue
nav_elements: # List of pages you want to show up in the navigation of your page.
- name: welcome
# - name: program
-# - name: propose
-# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
-# - name: location
-# - name: registration
+ - name: propose
+ url: https://www.papercall.io/dod-clt
+ - name: location
+ - name: agenda
+ - name: registration
- name: sponsor
- name: contact
- name: conduct
@@ -53,10 +53,34 @@ proposal_email: "proposals-charlotte-2017@devopsdays.org" # Put your proposal em
sponsors:
- id: sumologic
level: gold
- - id: thoughtworks-products
- level: gold
+ - id: gocd
+ level: gold
+ - id: opsgenie
+ level: gold
+ - id: pivotal
+ level: gold
+ - id: ns1
+ level: gold
- id: split-software
level: silver
+ - id: netapp
+ level: silver
+ - id: honeycomb
+ level: silver
+ - id: actifio
+ level: silver
+ - id: techtowntraining
+ level: silver
+ - id: victorops
+ level: silver
+ - id: deis
+ level: bronze
+ - id: sonatype
+ level: bronze
+ - id: versionone
+ level: bronze
+ - id: spoken
+ level: bronze
- id: city-of-charlotte
level: community
diff --git a/exampleSite/data/events/2017-chicago.yml b/exampleSite/data/events/2017-chicago.yml
index 4373b4efb..852948f25 100644
--- a/exampleSite/data/events/2017-chicago.yml
+++ b/exampleSite/data/events/2017-chicago.yml
@@ -1,7 +1,6 @@
name: "2017-chicago" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Chicago" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
diff --git a/exampleSite/data/events/2017-dallas.yml b/exampleSite/data/events/2017-dallas.yml
new file mode 100644
index 000000000..3321cd8f8
--- /dev/null
+++ b/exampleSite/data/events/2017-dallas.yml
@@ -0,0 +1,85 @@
+name: "2017-dallas" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Dallas" # The displayed city name of the event. Capitalize it.
+friendly: "2017-dallas" # Four digit year and the city name in lower-case. Don't forget the dash!
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted YYYY-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Dallas / Ft. Worth" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Mike Rosado"
+ twitter: "MikeRosTX"
+ - name: "Michael Hedgpeth"
+ twitter: "michaelhedgpeth"
+ employer: "NCR"
+ - name: "Annie Hedgpeth"
+ twitter: "anniehedgie"
+ employer: "10th Magnitude"
+ - name: "Ben Johnson"
+ twitter: "benjohnson77"
+ employer: "Particle41"
+ - name: "Mark Saum"
+ twitter: "msaum"
+ employer: "Fidelis Consulting"
+ - name: "Jack Teoh"
+ twitter: "jaxteoh"
+ employer: "Alkami Technology"
+ - name: "Gokul Sridharan"
+ twitter: "ConsultGokul_CA"
+ employer: "CA Technologies"
+organizer_email: "organizers-dallas-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-dallas-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: platinum
+ label: Platinum
+ max: 4
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-denver.yml b/exampleSite/data/events/2017-denver.yml
new file mode 100644
index 000000000..78e5a89f4
--- /dev/null
+++ b/exampleSite/data/events/2017-denver.yml
@@ -0,0 +1,50 @@
+name: "2017-denver" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: 2017 # The year of the event. Make sure it is in quotes.
+city: "Denver" # The city name of the event. Capitalize it.
+friendly: "2017-denver" # Four digit year and the city name in lower-case. Don't forget the dash!
+status: "current" # Options are "past" or "current".
+startdate: 2017-04-10 # The start date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+enddate: 2017-04-11 # The end date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+cfp_date_start: 2017-01-13
+cfp_date_end: 2017-02-17
+cfp_date_announce: 2017-03-01
+coordinates: "39.739236, -104.990251" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Denver" # The name of your location
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+ - name: sponsor
+ - name: propose
+ - name: contact
+ - name: conduct
+ - name: location
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Tavis Aitken"
+ - name: "Jason Hand"
+ - name: "Beau Christensen"
+ - name: "Joe Thompson"
+ - name: "Hannah Klemme"
+ - name: "Nick Huanca"
+ - name: "Ryan Koch"
+
+
+organizer_email: "organizers-denver-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-denver-2017@devopsdays.org" # Put your proposal email address here
+sponsors: # List all of your sponsors here along with what level of sponsorship they have.
+ - id: victorops
+ level: social
+
+sponsor_levels: # In this section, list the level of sponsorships and the label to use.
+ - id: social
+ label: Social
+ max: 1
+ - id: lanyard
+ label: Lanyard
+ - id: gold
+ label: Gold
+ - id: silver
+ label: Silver
+ - id: bronze
+ lable: Bronze
diff --git a/exampleSite/data/events/2017-detroit.yml b/exampleSite/data/events/2017-detroit.yml
new file mode 100644
index 000000000..bde2874f0
--- /dev/null
+++ b/exampleSite/data/events/2017-detroit.yml
@@ -0,0 +1,67 @@
+name: "2017-detroit" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Detroit" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+status: "current"
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: 2017-09-27
+enddate: 2017-09-28
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "42.331034, -83.046382" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "A. Alfred Taubman Center for Design Education, College for Creative Studies" # The name of your location
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+ - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: Ben Chess
+ employer: Yelp
+ - name: "Jamie Begin"
+ employer: RightBrain Networks
+ - name: "Brian Nuszkowski"
+ employer: Uber
+ - name: "Joe Arnet"
+ employer: Barracuda Networks
+ - name: "Trevor Smith"
+ - name: "Allison Green"
+organizer_email: "organizers-detroit-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-detroit-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 0
+ - id: silver
+ label: Silver
+ max: 0
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-hartford.yml b/exampleSite/data/events/2017-hartford.yml
new file mode 100644
index 000000000..1f60842cd
--- /dev/null
+++ b/exampleSite/data/events/2017-hartford.yml
@@ -0,0 +1,75 @@
+name: "2017-hartford" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Hartford" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2016-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.763711, -72.685093" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Hartford" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Dave Long"
+ twitter: davejlong
+ employer: "Cage Data, Inc."
+ - name: "Aaron Aldrich"
+ twitter: crayzeigh
+ employer: "Cage Data, Inc."
+ - name: "Scott Russel"
+ twitter: sergeography
+ employer: "Core Informatics"
+ - name: "Jose Andrade"
+ twitter: jandrade
+ employer: "Yale University"
+ - name: Eric Loveland
+ twitter: elovelan
+ - name: Serena Ness
+organizer_email: "organizers-hartford-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "organizers-hartford-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-indianapolis.yml b/exampleSite/data/events/2017-indianapolis.yml
new file mode 100644
index 000000000..d03c03c42
--- /dev/null
+++ b/exampleSite/data/events/2017-indianapolis.yml
@@ -0,0 +1,67 @@
+name: "2017-indianapolis" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Indianapolis" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate:
+enddate:
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Indianapolis" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Byron Schaller"
+ twitter: "byronschaller"
+ - name: "Shane Weinbrecht"
+ twitter: "shizrah"
+ - name: "Rob Nelson"
+ - name: "Andrew Poland"
+ - name: "Greg Swallow"
+organizer_email: "organizers-indianapolis-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-indianapolis-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-london.yml b/exampleSite/data/events/2017-london.yml
new file mode 100644
index 000000000..0ea7213e8
--- /dev/null
+++ b/exampleSite/data/events/2017-london.yml
@@ -0,0 +1,72 @@
+name: "2017-london" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "London" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+#startdate: 2017-04-18
+#enddate: 2017-04-19
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "51.507351, -0.127758" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "London" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "bob walker"
+ twitter: "rjw1"
+ - name: "Dean Wilson"
+ twitter: "unixdaemon"
+ - name: "Paula Kennedy"
+ twitter: "PaulaLKennedy"
+ - name: "Dawn Foster"
+ twitter: "geekygirldawn"
+ - name: "Markos Rendell"
+ twitter: "markosrendell"
+ - name: "Barry Chandler"
+ twitter: "bdc101"
+ - name: "Hannah Foxwell"
+ twitter: "HannahFoxwell"
+organizer_email: "organizers-london-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-london-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-minneapolis.yml b/exampleSite/data/events/2017-minneapolis.yml
index 1fd5a2987..2c4bcea5e 100644
--- a/exampleSite/data/events/2017-minneapolis.yml
+++ b/exampleSite/data/events/2017-minneapolis.yml
@@ -1,14 +1,13 @@
name: "2017-minneapolis"
year: "2017"
city: "Minneapolis"
-status: "current"
startdate: 2017-07-25
enddate: 2017-07-26
-cfp_date_start:
-cfp_date_end:
-cfp_date_announce:
+cfp_date_start: 2016-12-22
+cfp_date_end: 2017-04-09
+cfp_date_announce: 2017-05-07
coordinates: "44.972610,-93.272960"
location: "Minneapolis"
@@ -17,9 +16,9 @@ nav_elements:
- name: welcome
# - name: program
# - name: speakers
-# - name: propose
-# - name: location
-# - name: registration
+ - name: propose
+ - name: location
+ - name: registration
- name: sponsor
- name: contact
- name: conduct
@@ -48,6 +47,14 @@ proposal_email: "proposals-minneapolis-2017@devopsdays.org"
sponsors:
- id: arresteddevops
level: community
+ - id: pivotal
+ level: platinum
+ - id: deis
+ level: silver
+ - id: hackthegap
+ level: community
+ - id: saucelabs
+ level: silver
sponsors_accepted : "yes"
diff --git a/exampleSite/data/events/2017-moscow.yml b/exampleSite/data/events/2017-moscow.yml
index 150804871..667cfc7d0 100644
--- a/exampleSite/data/events/2017-moscow.yml
+++ b/exampleSite/data/events/2017-moscow.yml
@@ -4,12 +4,12 @@ city: "Moscow" # The displayed city name of the event. Capitalize it.
status: "current" # Options are "past" or "current". Use "current" for upcoming.
# All dates are in unquoted 2016-MM-DD, like this: variable: 2016-01-05
-startdate: 2017-02-11 # The start date of your event. Leave blank if you don't have a venue reserved yet.
-enddate: 2017-02-11 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+startdate: 2017-03-11 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2017-03-11 # The end date of your event. Leave blank if you don't have a venue reserved yet.
# Leave CFP dates blank if you don't know yet, or set all three at once.
-cfp_date_start: # start accepting talk proposals.
-cfp_date_end: # close your call for proposals.
-cfp_date_announce: # inform proposers of status
+cfp_date_start: 2016-12-01 # start accepting talk proposals.
+cfp_date_end: 2017-02-17 # close your call for proposals.
+cfp_date_announce: 2017-02-17 # inform proposers of status
# Location
#
@@ -31,21 +31,43 @@ nav_elements: # List of pages you want to show up in the navigation of your page
# These are the same people you have on the mailing list and Slack channel.
team_members: # Name is the only required field for team members.
+ - name: "Alexander Titov"
- name: "Boris Zlobin"
- name: "Michael Krivilev"
- name: "Vitaly Mosin"
+ - name: "Vladimir Turovtsev"
- name: "Vladislav Zavisnov"
- - name: "Alexander Titov"
organizer_email: "organizers-moscow-2017@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-moscow-2016@devopsdays.org" # Put your proposal email address here
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
+# media
+ - id: Express42
+ level: media
+ - id: Logrocon
+ level: media
+ - id: superjob
+ level: media
+ - id: avito
+ level: media
- id: samplesponsorname
level: gold
- id: arresteddevops
- level: community
+ level: media
+ - id: pcweek
+ level: media
+ - id: logo_vox
+ level: media
+ - id: unicraft
+ level: media
+ - id: oktell
+ level: media
+ - id: globalcio
+ level: media
+ - id: hh
+ level: hrsponsor
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
@@ -54,13 +76,18 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
# sponsorship for a specific level, it is best to remove the level.
sponsor_levels:
+ - id: platinum
+ label: Platinum
- id: gold
label: Gold
max: 10
- id: silver
label: Silver
max: 0 # This is the same as omitting the max limit.
- - id: bronze
- label: Bronze
+ - id: hrsponsor
+ label: HR
+ - id: media
+ label: Media
- id: community
label: Community
+
diff --git a/exampleSite/data/events/2017-ohio.yml b/exampleSite/data/events/2017-ohio.yml
new file mode 100644
index 000000000..ef03cd8f0
--- /dev/null
+++ b/exampleSite/data/events/2017-ohio.yml
@@ -0,0 +1,33 @@
+name: "2017-ohio" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: 2017 # The year of the event. Make sure it is in quotes.
+city: "Ohio" # The city name of the event. Capitalize it.
+friendly: "2017-ohio" # Four digit year and the city name in lower-case. Don't forget the dash!
+status: "past" # Options are "past" or "current".
+startdate: "" # The start date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+enddate: "" # The end date of your event, in YYYY-MM-DD format. Leave blank if you don't have a date yet.
+cfp_date_start: ""
+cfp_date_end: ""
+cfp_date_announce: ""
+coordinates: "40.038877, -82.874830" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "" # The name of your location
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+ - name: contact
+ - name: conduct
+ - name: sponsor
+team: ["Ben Blanquera", "Bill Schwanitz", "David Laulusa", "Kyle Jenkins", "John Lusk", "Mark Goodmanson", "Michael Ducy", "Michael Swartzbaugh", "Rob Kinyon", "Warner Moore"]
+organizer_email: "organizers-ohio-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "organizers-ohio-2017@devopsdays.org" # Put your proposal email address here
+sponsors: # List all of your sponsors here along with what level of sponsorship they have.
+ - id: test
+ level: gold
+
+sponsor_levels: # In this section, list the level of sponsorships and the label to use.
+ - id: gold
+ label: Gold
+ - id: silver
+ label: Silver
+ - id: bronze
+ label: Bronze
+ - id: support
+ label: Community and Supporting
diff --git a/exampleSite/data/events/2017-paris.yml b/exampleSite/data/events/2017-paris.yml
index e54609c8f..8b037a48a 100644
--- a/exampleSite/data/events/2017-paris.yml
+++ b/exampleSite/data/events/2017-paris.yml
@@ -1,7 +1,6 @@
name: "2017-paris" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Paris" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
diff --git a/exampleSite/data/events/2017-portland.yml b/exampleSite/data/events/2017-portland.yml
index 93af87a83..d121640f4 100644
--- a/exampleSite/data/events/2017-portland.yml
+++ b/exampleSite/data/events/2017-portland.yml
@@ -2,7 +2,6 @@ name: "2017-portland" # The name of the event. Four digit year with the city nam
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Portland" # The displayed city name of the event. Capitalize it.
friendly: "2017-portland"
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
diff --git a/exampleSite/data/events/2017-saint-louis.yml b/exampleSite/data/events/2017-saint-louis.yml
new file mode 100644
index 000000000..62b8109ab
--- /dev/null
+++ b/exampleSite/data/events/2017-saint-louis.yml
@@ -0,0 +1,70 @@
+name: "2017-saint-louis" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Saint Louis" # The displayed city name of the event. Capitalize it.
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: "DevOpsDays is coming to Saint Louis in 2017! It'll be a great opportunity to share knowledge, socialize, and have fun with other memnbers of our great technical community." # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # 2017-03-31 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # 2017-04-01 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # 2016-12-01 # start accepting talk proposals.
+cfp_date_end: # 2017-02-01 # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "38.7084, -90.4390" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Saint Louis" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: https://trello.com/b/qtP2nsVm/presentations # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+# - name: policies
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Sabree Blackmon"
+ twitter: "heavypackets"
+ - name: "Phil Cryer"
+ twitter: "fak3r"
+ - name: "Jim Hopkins"
+ - name: "Jess Jackson"
+ twitter: "jess_d_jackson"
+ - name: "Sayam Masood"
+ twitter: "mixpix3ls"
+ - name: "Matthew Perry"
+ twitter: "mlperry81"
+
+organizer_email: "organizers-saint-louis-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-saint-louis-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors: {}
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-salt-lake-city.yml b/exampleSite/data/events/2017-salt-lake-city.yml
index 15e066d7b..3e7bc03f1 100644
--- a/exampleSite/data/events/2017-salt-lake-city.yml
+++ b/exampleSite/data/events/2017-salt-lake-city.yml
@@ -1,16 +1,15 @@
name: "2017-salt-lake-city" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Salt Lake City" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: "DevOpsDays returns to the Silicon Slopes!"# A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
startdate: 2017-05-16 # The start date of your event. Leave blank if you don't have a venue reserved yet.
enddate: 2017-05-17 # The end date of your event. Leave blank if you don't have a venue reserved yet.
# Leave CFP dates blank if you don't know yet, or set all three at once.
-cfp_date_start: # start accepting talk proposals.
-cfp_date_end: # close your call for proposals.
-cfp_date_announce: # inform proposers of status
+cfp_date_start: 2016-12-14 # start accepting talk proposals.
+cfp_date_end: 2017-02-15 # close your call for proposals.
+cfp_date_announce: 2017-03-01 # inform proposers of status
# Location
#
@@ -21,13 +20,16 @@ location: "Noah's Event Venue" # Defaults to city, but you can make it the venue
nav_elements: # List of pages you want to show up in the navigation of your page.
- name: welcome
# - name: program
-# - name: propose
-# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
-# - name: location
-# - name: registration
+ - name: propose
+ url: https://www.papercall.io/slc-dev-ops-days
+ - name: location
+ - name: registration
+ url: http://slcdevopsdays.org/tc-events/slc-devops-days-2917/
- name: sponsor
+ url: http://slcdevopsdays.org/our-sponsors/
- name: contact
- name: conduct
+ url: http://slcdevopsdays.org/code-of-conduct/
# These are the same people you have on the mailing list and Slack channel.
team_members: # Name is the only required field for team members.
@@ -52,6 +54,9 @@ team_members: # Name is the only required field for team members.
employer: "HealthEquity"
twitter: "alexinslc"
- name: "Lindley White"
+ - name: "Brett Palmer"
+ - name: "Johnny Martinez"
+ - name: "Claron Twitchel"
organizer_email: "organizers-saltlakecity-2017@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-saltlakecity-2017@devopsdays.org" # Put your proposal email address here
@@ -59,6 +64,10 @@ proposal_email: "proposals-saltlakecity-2017@devopsdays.org" # Put your proposal
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
+ - id: morpheus_data
+ level: greencircle
+ - id: deis
+ level: blackdiamond
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
# In this section, list the level of sponsorships and the label to use.
@@ -68,6 +77,8 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
sponsor_levels:
- id: eveningsocial
label: Evening Social
+ - id: doubleblackdiamond
+ label: Double Black Diamond
- id: blackdiamond
label: Black Diamond
- id: bluesquare
diff --git a/exampleSite/data/events/2017-sao-paulo.yml b/exampleSite/data/events/2017-sao-paulo.yml
new file mode 100644
index 000000000..b4eee1b28
--- /dev/null
+++ b/exampleSite/data/events/2017-sao-paulo.yml
@@ -0,0 +1,75 @@
+name: "2017-sao-paulo" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "São Paulo" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "-23.551261, -46.634345" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "São Paulo" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: bem vindo
+ url: ../bemvindo
+# - name: programacao
+# - name: chamada
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: local
+# - name: inscricao
+ - name: patrocinio
+ - name: contato
+ - name: conduta
+
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Diógenes Rettori"
+ twitter: "rettori"
+ - name: "Fernando Ike"
+ - name: "Luciano Ramalho"
+ - name: "Luis Albinati Jr"
+ - name: "Melina Deraldo"
+ twitter: "melderaldo"
+ - name: "Rafael Gomes"
+ twitter: "gomex"
+ - name: "Thiago Araki"
+ - name: "Ana Paula Maia"
+ - name: "Frederico Moreira"
+# employer: "Acme Anvil Co."
+organizer_email: "organizers-sao-paulo-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-sao-paulo-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: samplesponsorname
+ level: gold
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-seattle.yml b/exampleSite/data/events/2017-seattle.yml
index 3c3da2e98..22876c8c6 100644
--- a/exampleSite/data/events/2017-seattle.yml
+++ b/exampleSite/data/events/2017-seattle.yml
@@ -1,7 +1,6 @@
name: "2017-seattle" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Seattle" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: "DevOpsDays is returning to Seattle in 2017" # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
@@ -14,7 +13,7 @@ cfp_date_announce: 2017-02-07 # inform proposers of status
# Location
#
-coordinates: "47.606209, -122.332071" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+coordinates: "47.623948, -122.350088" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
location: "Seattle" # Defaults to city, but you can make it the venue name.
#
@@ -46,8 +45,20 @@ proposal_email: "proposals-seattle-2017@devopsdays.org" # Put your proposal emai
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
- - id: thoughtworks-products
+ - id: gocd
level: gold
+ - id: sumologic
+ level: gold
+ - id: deis
+ level: gold
+ - id: slalom
+ level: gold
+ - id: pivotal
+ level: gold
+ - id: opsgenie
+ level: gold
+ - id: spoken
+ level: bronze
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
diff --git a/exampleSite/data/events/2017-stockholm.yml b/exampleSite/data/events/2017-stockholm.yml
new file mode 100644
index 000000000..e8e79b94e
--- /dev/null
+++ b/exampleSite/data/events/2017-stockholm.yml
@@ -0,0 +1,66 @@
+name: "2017-stockholm" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Stockholm" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "59.329323, 18.068581" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Stockholm" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Andrey Devyatkin"
+ - name: "Björn Sundling"
+ - name: "Cecilia Wirén"
+ - name: "Fredrik Nilsson"
+ - name: "Lowe Schmidt"
+ - name: "Niklas Åkerlund"
+organizer_email: "organizers-stockholm-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-stockholm-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+ - id: praqma
+ level: silver
+ - id: arresteddevops
+ level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-tokyo.yml b/exampleSite/data/events/2017-tokyo.yml
new file mode 100644
index 000000000..d0b26fac4
--- /dev/null
+++ b/exampleSite/data/events/2017-tokyo.yml
@@ -0,0 +1,68 @@
+name: "2017-tokyo" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Tokyo" # The displayed city name of the event. Capitalize it.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "35.689488, 139.691706" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Tokyo" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Ippei Suzuki"
+ employer: "Creationline"
+ - name: "Alex Papadimoulis"
+ employer: "Inedo"
+ twitter: "apapadimoulis"
+ - name: "Yasunobu Kawaguchi"
+ employer: "Rakuten"
+
+organizer_email: "organizers-tokyo-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-tokyo-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+# - id: samplesponsorname
+# level: gold
+# - id: arresteddevops
+# level: community
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+# - id: gold
+# label: Gold
+# max: 10
+# - id: silver
+# label: Silver
+# max: 0 # This is the same as omitting the max limit.
+# - id: bronze
+# label: Bronze
+# - id: community
+# label: Community
diff --git a/exampleSite/data/events/2017-toronto.yml b/exampleSite/data/events/2017-toronto.yml
index 7d27622a2..293ff9918 100644
--- a/exampleSite/data/events/2017-toronto.yml
+++ b/exampleSite/data/events/2017-toronto.yml
@@ -1,30 +1,29 @@
name: "2017-toronto" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Toronto" # The displayed city name of the event. Capitalize it.
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
-startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
-enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+startdate: 2017-05-25 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2017-05-26 # The end date of your event. Leave blank if you don't have a venue reserved yet.
# Leave CFP dates blank if you don't know yet, or set all three at once.
-cfp_date_start: # start accepting talk proposals.
-cfp_date_end: # close your call for proposals.
-cfp_date_announce: # inform proposers of status
+cfp_date_start: 2016-12-21 # start accepting talk proposals.
+cfp_date_end: 2017-01-31 # close your call for proposals.
+cfp_date_announce: 2017-02-28 # inform proposers of status
# Location
#
-coordinates: "43.6532,-79.3831" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
-location: "Toronto" # The name of your location
+coordinates: "43.644489,-79.388044" # The corrodinates of your venue. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Glenn Gould Studio" # The name of your location
#
nav_elements: # List of pages you want to show up in the navigation of your page.
- name: welcome
# - name: program
-# - name: propose
+ - name: propose
# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
-# - name: location
-# - name: registration
+ - name: location
+ - name: register
- name: sponsor
- name: contact
- name: conduct
@@ -50,6 +49,8 @@ proposal_email: "proposals-toronto-2017@devopsdays.org" # Put your proposal emai
# List all of your sponsors here along with what level of sponsorship they have.
# Check data/sponsors/ to use sponsors already added by others.
sponsors:
+ - id: nocompany #HACK - add a sponsor at a non-existent level to force levels to show.
+ level: community
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
@@ -60,11 +61,15 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
sponsor_levels:
- id: gold
label: Gold
- max: 10
+ max: 14
+ - id: happyhour
+ label: Happy Hour
+ max: 1
+ - id: lunch
+ label: Lunch
+ max: 2
- id: silver
label: Silver
max: 0 # This is the same as omitting the max limit.
- id: bronze
label: Bronze
- - id: community
- label: Community
diff --git a/exampleSite/data/events/2017-vancouver.yml b/exampleSite/data/events/2017-vancouver.yml
new file mode 100644
index 000000000..9bd2a6762
--- /dev/null
+++ b/exampleSite/data/events/2017-vancouver.yml
@@ -0,0 +1,67 @@
+name: "2017-vancouver" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Vancouver" # The displayed city name of the event. Capitalize it.
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: 2017-03-31 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2017-04-01 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: 2016-12-01 # start accepting talk proposals.
+cfp_date_end: 2017-02-01 # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "49.282729, -123.120738" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Vancouver" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+ - name: program
+ - name: propose
+ url: "https://docs.google.com/forms/d/e/1FAIpQLSddTit30OVfFcbrRNXyIIqPRwX-USUbQWMzNpM9meBEi1DB7g/viewform"
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+ - name: location
+ - name: registration
+ url: "https://www.eventbrite.ca/e/devops-days-vancouver-2017-mar-31st-apr-1st-tickets-29634403298"
+ - name: sponsor
+ - name: contact
+ - name: conduct
+ - name: policies
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Kelly Shkuratoff"
+ - name: "Michael Collins"
+ - name: "Ronald Bow"
+ - name: "Vincent Janelle"
+ twitter: "randomfrequency"
+ - name: "Saem Ghani"
+ - name: "Chris Demwell"
+organizer_email: "organizers-vancouver-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-vancouver-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors: {}
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: gold
+ label: Gold
+ max: 10
+ - id: silver
+ label: Silver
+ max: 0 # This is the same as omitting the max limit.
+ - id: bronze
+ label: Bronze
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-washington-dc.yml b/exampleSite/data/events/2017-washington-dc.yml
new file mode 100644
index 000000000..ce2e85672
--- /dev/null
+++ b/exampleSite/data/events/2017-washington-dc.yml
@@ -0,0 +1,80 @@
+name: "2017-washington-dc" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2017" # The year of the event. Make sure it is in quotes.
+city: "Washington, DC" # The displayed city name of the event. Capitalize it.
+status: "current" # Options are "past" or "current". Use "current" for upcoming.
+description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
+
+# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
+startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+cfp_date_start: # start accepting talk proposals.
+cfp_date_end: # close your call for proposals.
+cfp_date_announce: # inform proposers of status
+
+# Location
+#
+coordinates: "41.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Washington, DC" # Defaults to city, but you can make it the venue name.
+#
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ - name: welcome
+# - name: program
+# - name: propose
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+# - name: location
+# - name: registration
+ - name: sponsor
+ - name: contact
+ - name: conduct
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members: # Name is the only required field for team members.
+ - name: "Nathen Harvey"
+ twitter: "nathenharvey"
+ employer: "Chef"
+ - name: "Alan Kraft"
+ employer: "United States Patent and Trademark Office (USPTO)"
+ - name: "Michael Barbine"
+ twitter: "BigNerdLoLz"
+ employer: "Barbine Worldwide"
+ - name: "Mike DelNegro"
+ twitter: "radiocats"
+ employer: "Deltek"
+ - name: "Greg Elin"
+ twitter: "gregelin"
+ employer: "GovReady"
+ - name: "Jeff Gallimore"
+ twitter: "jgallimore"
+ employer: "Excella Consulting"
+ - name: "James Martin"
+ twitter: "grepless"
+ employer: "3M"
+ - name: "Ramez Mourad"
+ twitter: "ramezjm"
+ employer: "Cvent"
+organizer_email: "organizers-washington-dc-2017@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-washington-dc-2017@devopsdays.org" # Put your proposal email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimitted sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+ - id: platinum
+ label: Platinum
+ - id: gold
+ label: Gold
+ - id: silver
+ label: Silver
+ - id: media
+ label: Media
+ - id: community
+ label: Community
diff --git a/exampleSite/data/events/2017-zurich.yml b/exampleSite/data/events/2017-zurich.yml
index 5a1a06f6d..a5170be78 100644
--- a/exampleSite/data/events/2017-zurich.yml
+++ b/exampleSite/data/events/2017-zurich.yml
@@ -2,14 +2,13 @@ name: "2017-zurich" # The name of the event. Four digit year with the city name
year: "2017" # The year of the event. Make sure it is in quotes.
city: "Zürich" # The city name of the event. Capitalize it.
friendly: "2017-zurich" # Four digit year and the city name in lower-case. Don't forget the dash!
-status: "current" # Options are "past" or "current". Use "current" for upcoming.
# All dates are in unquoted 2017-MM-DD, like this: variable: 2016-01-05
startdate: 2017-05-03
enddate: 2017-05-04
# Leave CFP dates blank if you don't know yet, or set all three at once.
cfp_date_start: 2016-11-01 # start accepting talk proposals.
-cfp_date_end: 2017-03-01 # close your call for proposals.
+cfp_date_end: 2017-02-01 # close your call for proposals.
cfp_date_announce: 2017-04-01 # inform proposers of status
# Location
@@ -51,6 +50,7 @@ team_members: # Name is the only required field for team members.
- name: "Tobias Brunner"
twitter: "tobruzh"
employer: "VSHN AG"
+ - name: "Vittorio Boccone"
organizer_email: "organizers-zuerich-2017@devopsdays.org" # Put your organizer email address here
proposal_email: "proposals-zuerich-2017@devopsdays.org" # Put your proposal email address here
@@ -60,7 +60,7 @@ proposal_email: "proposals-zuerich-2017@devopsdays.org" # Put your proposal emai
sponsors:
- id: swisscom
level: gold
- - id: glenfis
+ - id: pontine
level: gold
- id: redhat
level: gold
@@ -68,8 +68,14 @@ sponsors:
level: gold
- id: chef
level: gold
+ - id: gocd
+ level: gold
- id: vshn
level: bronze
+ - id: dectris
+ level: bronze
+ - id: atos
+ level: gold
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
sponsor_levels: # In this section, list the level of sponsorships and the label to use.
diff --git a/exampleSite/data/speakers/2016/amsterdam/adam-jacob.yml b/exampleSite/data/speakers/2016/amsterdam/adam-jacob.yml
new file mode 100644
index 000000000..3fa307a28
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/adam-jacob.yml
@@ -0,0 +1,3 @@
+name: "Adam Jacob"
+twitter: "adamhjk"
+bio: "Adam Jacob is the creator of Chef and co-founder of Chef, Inc. in 2008 and currently serves as its Chief Technology Officer. Prior to Chef, Inc. Adam founded HJK Solutions, an automated infrastructure consultancy. During two years at HJK, Adam built new infrastructures for 15 different startups. Including Adam's time at HJK, Adam has 13 years of experience as a systems administrator, systems architect, and tools developer."
diff --git a/exampleSite/data/speakers/2016/amsterdam/andrew-farley.yml b/exampleSite/data/speakers/2016/amsterdam/andrew-farley.yml
new file mode 100644
index 000000000..949b2a65d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/andrew-farley.yml
@@ -0,0 +1,3 @@
+name: "Andrew Farley"
+twitter: ""
+bio: "Farley is a Senior DevOps Engineer and consultant for OlinData. He has experience with high-scalability systems both in bare metal and in the cloud for the last 12 years and on AWS for over 6 years now. He's founded a handful of startups and been doing consulting for a wide range of companies in Silicon Valley and around the world. He is passionate about high-scalability and redundant, systems, automation, agile and continuous deployment, documentation, diagramming and open-source software. He has no associations with Amazon other than being a passionate user of their platform and holding an AWS Associate Certification. Farley's interests don’t end at managing servers, he's authored and launched over 30 mobile applications, numerous games, he’s launched or been an early employee at a dozen startups, and has years of experience designing and consuming APIs using various languages. And for fun he plays with microelectronics and designs & flies racing quad-copters in his free time."
diff --git a/exampleSite/data/speakers/2016/amsterdam/arnold-van-wijnbergen.yml b/exampleSite/data/speakers/2016/amsterdam/arnold-van-wijnbergen.yml
new file mode 100644
index 000000000..000defaee
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/arnold-van-wijnbergen.yml
@@ -0,0 +1,3 @@
+name: "Arnold van Wijnbergen"
+twitter: "bsmconsultant"
+bio: "Arnold van Wijnbergen is an independent advisor, coach and consultant from Devoteam. He specializes in Monitoring and Automation topics to improve quality and efficiency of operational control of IT4IT business. To achieve this he combines Lean principles with DevOps culture, because he strongly believes in the power of culture and self-steering teams. His broad experience in Monitoring and Automation tooling implementations ranges from midsize till enterprise scale, formed mainly in the banking, insurance, governance, retail, telco and service provider branches. At ING he is management consultant within the ING Automate monitoring stream, which is responsible for advising, training and coaching DevOps teams with improving their monitoring capabilities."
diff --git a/exampleSite/data/speakers/2016/amsterdam/avishai-ish-shalom.yml b/exampleSite/data/speakers/2016/amsterdam/avishai-ish-shalom.yml
new file mode 100644
index 000000000..8637c1699
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/avishai-ish-shalom.yml
@@ -0,0 +1,3 @@
+name: "Avishai Ish-Shalom"
+twitter: "nukemberg"
+bio: "Avishai Ish-Shalom is a veteran Ops and a survivor of many production skirmishes. Currently an independent consultant, Avishai helps companies deal with web era operations and scale. In his spare time Avishai is spreading weird ideas and conspiracy theories such as DevOps."
diff --git a/exampleSite/data/speakers/2016/amsterdam/bas-meijer.yml b/exampleSite/data/speakers/2016/amsterdam/bas-meijer.yml
new file mode 100644
index 000000000..a57b1024e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/bas-meijer.yml
@@ -0,0 +1,3 @@
+name: "Bas Meijer"
+twitter: "bbaassssiiee"
+bio: "Bas is a systems engineer and software developer and wasted decades on latenight hacking. He is currently helping out 2 enterprises with continuous delivery and devops."
diff --git a/exampleSite/data/speakers/2016/amsterdam/bernd-erk.yml b/exampleSite/data/speakers/2016/amsterdam/bernd-erk.yml
new file mode 100644
index 000000000..88a6e8cb9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/bernd-erk.yml
@@ -0,0 +1,3 @@
+name: "Bernd Erk"
+twitter: "gethash"
+bio: "Bernd Erk is co-founder and community manager of the Icinga Project. In his day job he is CEO at NETWAYS, a German open source service company. As contributor to Linux Magazine and Admin Magazine, Bernd regularly publishes articles and presents on open source topics ranging from monitoring, configuration management to various open source datacenter solutions. He tries to spread the DevOps spirit wherever and whenever possible."
diff --git a/exampleSite/data/speakers/2016/amsterdam/christoph-andreas-torlinsky.yml b/exampleSite/data/speakers/2016/amsterdam/christoph-andreas-torlinsky.yml
new file mode 100644
index 000000000..f2560e71c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/christoph-andreas-torlinsky.yml
@@ -0,0 +1,3 @@
+name: "Christoph Andreas Torlinsky"
+twitter: "nuagenetworks"
+bio: "Hello, i work for a Startup called Nuage Networks in EMEA and we are actively trying to change how Software interacts with the Network. Check us out, I've been working for a number of companies prior to Nuage in the Networking and Linux and Operating Space."
diff --git a/exampleSite/data/speakers/2016/amsterdam/daniel-van-gils.yml b/exampleSite/data/speakers/2016/amsterdam/daniel-van-gils.yml
new file mode 100644
index 000000000..5f8db3e3e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/daniel-van-gils.yml
@@ -0,0 +1,3 @@
+name: "Daniël van Gils"
+twitter: "foldingbeauty"
+bio: "Daniël van Gils is a polyglot developer advocate at Cloud 66. He helps other polyglot developers craft ruby (on rails) web applications and container based microservice architectures with ♥, to deploy on any server or public cloud. He’s been involved in the web development, creative technologies, and gaming industries. An accomplished creative technologist, Daniel has vast and varied experience in application development, agile workflows, lecturing and building container technologies at scale. In his spare time he experiments with strawberries in his backyard, likes to surf and practices improvisation theater."
diff --git a/exampleSite/data/speakers/2016/amsterdam/dave-van-herpen.yml b/exampleSite/data/speakers/2016/amsterdam/dave-van-herpen.yml
new file mode 100644
index 000000000..f65b25b60
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/dave-van-herpen.yml
@@ -0,0 +1,3 @@
+name: "Dave van Herpen"
+twitter: "daveherpen"
+bio: "Dave van Herpen is management coach (Enterprise Agility & DevOps) at Sogeti Netherlands. In his role as practitioner, coach, trainer and change agent, Dave has been supporting his customers to organize for end-to-end agility for the past 15 years."
diff --git a/exampleSite/data/speakers/2016/amsterdam/desmond-delissen.yml b/exampleSite/data/speakers/2016/amsterdam/desmond-delissen.yml
new file mode 100644
index 000000000..895522e46
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/desmond-delissen.yml
@@ -0,0 +1,3 @@
+name: "Desmond Delissen"
+twitter: ""
+bio: "Desmond started his career at a big consultancy company. Via this company he got the change to join a mobile app project in the beginning of 2012. Desmond enjoined this so much that he decided to start working for IceMobile and become a expert in testing mobile apps and their backend systems."
diff --git a/exampleSite/data/speakers/2016/amsterdam/erica-baker.yml b/exampleSite/data/speakers/2016/amsterdam/erica-baker.yml
new file mode 100644
index 000000000..b48f228b0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/erica-baker.yml
@@ -0,0 +1,3 @@
+name: "Erica Baker"
+twitter: "EricaJoy"
+bio: "Erica is a Senior Engineer at Slack Technologies and advocate for diversity and inclusion in tech, and expanding access to tech education. Erica's career in tech began fourteen years ago doing domain administration for the University of Alaska Statewide System, before becoming a Googler in 2006. Erica's role grew and shifted within Google, growing from Support Technician to Site Reliability Engineer. She joined Slack in 2015, where she focuses on Build and Release Engineering. Erica is on the Advisory Boards for Atipica and Hack the Hood, and is a Tech Mentor for Black Girls Code. Erica is currently based in Oakland, California."
diff --git a/exampleSite/data/speakers/2016/amsterdam/gopal-ramachandran.yml b/exampleSite/data/speakers/2016/amsterdam/gopal-ramachandran.yml
new file mode 100644
index 000000000..fb7375d5e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/gopal-ramachandran.yml
@@ -0,0 +1,3 @@
+name: "Gopal Ramachandran"
+twitter: "goposky"
+bio: "Gopal is an experienced engineer/consultant who is passionate about Devops. The last few years he has been busy creating CD pipelines, implementing configuration management, and automating stuff at few large companies in the Netherlands. Prior to that he has been a hosting engineer, and also a Java developer."
diff --git a/exampleSite/data/speakers/2016/amsterdam/guy-podjarny.yml b/exampleSite/data/speakers/2016/amsterdam/guy-podjarny.yml
new file mode 100644
index 000000000..56b74c57c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/guy-podjarny.yml
@@ -0,0 +1,3 @@
+name: "Guy Podjarny"
+twitter: "guypod"
+bio: "Guy Podjarny is a cofounder at Snyk.io focusing on securing open source code. Guy was previously CTO at Akamai and founder of Blaze.io, and worked on the first web app firewall & security static code analyzer. Guy is a frequent conference speaker, the author of 'Responsive & Fast', 'High Performance Images' and the upcoming 'Securing Third Party Code' (via O’Reilly), and the creator of Mobitest."
diff --git a/exampleSite/data/speakers/2016/amsterdam/hannah-foxwell.yml b/exampleSite/data/speakers/2016/amsterdam/hannah-foxwell.yml
new file mode 100644
index 000000000..a17bd78df
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/hannah-foxwell.yml
@@ -0,0 +1,3 @@
+name: "Hannah Foxwell"
+twitter: "hannahfoxwell"
+bio: "While culture and sharing are at the heart of DevOps, Infrastructure Automation is the technical backbone. That’s one of the reasons why Hannah co-founded Pendrica, a consultancy specialising in Platform Automation with Chef and Microsoft. Hannah’s background and experience in managing large scale software programmes naturally lead to a keen interest in Agile, Continuous Delivery and the DevOps movement as a way of building collaborative, highly-performing teams. As a coach and mentor she continues this work today, helping teams improve how they work together in the fast-moving world of automation. Outside of work you can generally find Hannah in her local pub enjoying a craft beer while planning her next adventure."
diff --git a/exampleSite/data/speakers/2016/amsterdam/harm-weites.yml b/exampleSite/data/speakers/2016/amsterdam/harm-weites.yml
new file mode 100644
index 000000000..418b8b86b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/harm-weites.yml
@@ -0,0 +1,3 @@
+name: "Harm Weites"
+twitter: "wehkamp"
+bio: "Harm is committed to engineering the Wehkamp e-commerce platform, making sure it scales and performs to meet customer and business demands. He is passionate about automation and is part of Wehkamp’s SRE team."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jan-de-vries.yml b/exampleSite/data/speakers/2016/amsterdam/jan-de-vries.yml
new file mode 100644
index 000000000..b8e004892
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jan-de-vries.yml
@@ -0,0 +1,3 @@
+name: "Jan de Vries"
+twitter: ""
+bio: "Jan de Vries is a senior business IT consultant and a trusted advisor in the fields of requirements engineering, business information management, application management and DevOps. He is a BiSL, ASL, ITIL, ISM and FSM trainer and convenor of the Enterprise DevOps working group that unites members of the ASL BiSL Foundation and the Agile Consortium. He founded Blue Ocean Recon to do research that focuses on Blue Oceans and Lean Startups."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jan-kaan.yml b/exampleSite/data/speakers/2016/amsterdam/jan-kaan.yml
new file mode 100644
index 000000000..b79e82ea5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jan-kaan.yml
@@ -0,0 +1,3 @@
+name: "Jan Kaan"
+twitter: "jankaan81"
+bio: "Jan Kaan runs the Expert Partner Program for Atlassian within the Benelux & Nordics. With a background in Intercultural Awareness and 15 years of experience within the IT space he has fulfilled various roles from Recruitment to Sales in primarily large international organizations."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jason-yee.yml b/exampleSite/data/speakers/2016/amsterdam/jason-yee.yml
new file mode 100644
index 000000000..4ecbdd537
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jason-yee.yml
@@ -0,0 +1,3 @@
+name: "Jason Yee"
+twitter: "gitbisect"
+bio: "Jason is a community builder, developer, traveller and chef. He's passionate about connecting people and ideas to build a better world."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jim-leitch.yml b/exampleSite/data/speakers/2016/amsterdam/jim-leitch.yml
new file mode 100644
index 000000000..5b2c250a9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jim-leitch.yml
@@ -0,0 +1,3 @@
+name: "Jim Leitch"
+twitter: ""
+bio: "Jim is a family man, guitarist and dog lover. Having lived in the Netherlands for the last 22 years he knows where the best stroopwafels are."
diff --git a/exampleSite/data/speakers/2016/amsterdam/jody-wolfborn.yml b/exampleSite/data/speakers/2016/amsterdam/jody-wolfborn.yml
new file mode 100644
index 000000000..0be2e7794
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/jody-wolfborn.yml
@@ -0,0 +1,3 @@
+name: "Jody Wolfborn"
+twitter: "joderita"
+bio: "Jody is a theatre major-turned-technologist with a passion for languages of all kinds and a soft-spot for animals of the canine variety. Since entering the tech realm, she’s had many years of experience living with and attempting to overcome Impostor Syndrome; through observation, research, and experimentation, she’s collected resources to help combat this psychological self-sabotage."
diff --git a/exampleSite/data/speakers/2016/amsterdam/karleen-wijsman.yml b/exampleSite/data/speakers/2016/amsterdam/karleen-wijsman.yml
new file mode 100644
index 000000000..c1ddda3c3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/karleen-wijsman.yml
@@ -0,0 +1,3 @@
+name: "Karleen Wijsman"
+twitter: ""
+bio: "Karleen Wijsman is an all-round IT Specialist and has many years of experience in providing training and workshops in the field of personal development and organisational change. Her NLP Practitioner and NLP Master background give her a solid foundation to motivate, engage and energize people and organizations"
diff --git a/exampleSite/data/speakers/2016/amsterdam/ken-mugrage.yml b/exampleSite/data/speakers/2016/amsterdam/ken-mugrage.yml
new file mode 100644
index 000000000..4991a6439
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/ken-mugrage.yml
@@ -0,0 +1,3 @@
+name: "Ken Mugrage"
+twitter: "kmugrage"
+bio: "Ken Mugrage has 25 years of experience in the IT industry, spending the last 7 at ThoughtWorks. During his entire career, Ken has focused on using technology to increase business effectiveness, as opposed to using the ‘latest cool thing’. Ken has been focused on Continuous Delivery and DevOps for most of the past decade, working with organizations all over the world, ranging from startups to Fortune 50 companies. He now uses this experience to teach others how to get better at building, testing and deploying software."
diff --git a/exampleSite/data/speakers/2016/amsterdam/marco-ceppi.yml b/exampleSite/data/speakers/2016/amsterdam/marco-ceppi.yml
new file mode 100644
index 000000000..d28909f08
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/marco-ceppi.yml
@@ -0,0 +1,3 @@
+name: "Marco Ceppi"
+twitter: "marcoceppi"
+bio: "Marco Ceppi is a devops engineer working for Canonical - the company behind Ubuntu. When not behind a computer, he often enjoys sailing, restoring cars, and voiding warranties."
diff --git a/exampleSite/data/speakers/2016/amsterdam/mark-van-holsteijn.yml b/exampleSite/data/speakers/2016/amsterdam/mark-van-holsteijn.yml
new file mode 100644
index 000000000..7a4d3a7e8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/mark-van-holsteijn.yml
@@ -0,0 +1,3 @@
+name: "Mark van Holsteijn"
+twitter: ""
+bio: "Mark van Holsteijn is Principal Consultant at Xebia specialized in cloud software architectures with open-source technologies."
diff --git a/exampleSite/data/speakers/2016/amsterdam/melanie-rieback.yml b/exampleSite/data/speakers/2016/amsterdam/melanie-rieback.yml
new file mode 100644
index 000000000..32c9e7f29
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/melanie-rieback.yml
@@ -0,0 +1,3 @@
+name: "Melanie Rieback"
+twitter: ""
+bio: "Melanie Rieback is the CEO/Co-founder of Radically Open Security. She is also a former Asst. Prof. of Computer Science at the Vrije Universiteit Amsterdam who performed RFID security research (RFID Virus and RFID Guardian), that got worldwide press coverage, and won several awards (VU Mediakomeet, ISOC Award finalist, NWO I/O award, IEEE Percom Best Paper, USENIX Lisa Best Paper). Melanie also worked as a Sr. Engineering Manager on XenClient at Citrix, where she led the Citrix Vancouver office. She was also a Sr. Managing Consultant in the Cyber Crime Expertise and Response Team (CCERT) at ING Bank, where she set up the CCERT Analysis Lab and was the lead technical project manager of the ING Core Threat Intelligence Systems. For fun, she founded the Dutch Girl Geek Dinner in 2008. Melanie was also named 2010 ICT Professional of the Year (Finalist) by WomeninIT, and one of the “400 most successful women in the Netherlands” by Viva Magazine (Viva400) in 2010."
diff --git a/exampleSite/data/speakers/2016/amsterdam/michael-ducy.yml b/exampleSite/data/speakers/2016/amsterdam/michael-ducy.yml
new file mode 100644
index 000000000..d27997ef9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/michael-ducy.yml
@@ -0,0 +1,3 @@
+name: "Michael Ducy"
+twitter: "mfdii"
+bio: "Michael Ducy currently works as a Manager for Solutions Architects at Chef focusing on helping companies understand Chef, DevOps, and IT transformation. Previously, Michael focused on designing and implementing automation solutions for customer’s Cloud, IT Automation, and Continuous Delivery needs. Michael has also worked in a variety of roles in his career including Cloud Architecture, Systems Engineering , Performance Engineering, and IT Instructor. Michael holds a Masters in Computer Science from the University of Chicago and an MBA from The Ohio State University."
diff --git a/exampleSite/data/speakers/2016/amsterdam/michael-friedrich.yml b/exampleSite/data/speakers/2016/amsterdam/michael-friedrich.yml
new file mode 100644
index 000000000..617d9d894
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/michael-friedrich.yml
@@ -0,0 +1,3 @@
+name: "Michael Friedrich"
+twitter: ""
+bio: "Michael has been an Icinga core developer for more than 7 years. He is currently leading the Icinga 2 development together with Gunnar. In addition to the exciting core architecture work he likes to play with Vagrant. Docker and Dashing. You’ll also find him active over at monitoring-portal.org, most recently as administrator too. In his spare time Michael loves to build LEGO models and enjoys Nuremberg with his Austrian dialect."
diff --git a/exampleSite/data/speakers/2016/amsterdam/nati-cohen.yml b/exampleSite/data/speakers/2016/amsterdam/nati-cohen.yml
new file mode 100644
index 000000000..33e2b752f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/nati-cohen.yml
@@ -0,0 +1,3 @@
+name: "Nati Cohen"
+twitter: "nocoot"
+bio: "Nati Cohen is a Production Engineer at SimilarWeb, fighting manual labor with code and vengeance. Previous experience includes: operations consulting, software development, *nix administration and security research in the Intelligence corps as well as in multiple startup companies."
diff --git a/exampleSite/data/speakers/2016/amsterdam/pavel-chunyayev.yml b/exampleSite/data/speakers/2016/amsterdam/pavel-chunyayev.yml
new file mode 100644
index 000000000..e6948c9b6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/pavel-chunyayev.yml
@@ -0,0 +1,3 @@
+name: "Pavel Chunyayev"
+twitter: "PavelChunyayev"
+bio: "Pavel Chunyayev is a Continuous Delivery Architect at Levi9 IT Services. With 12 years of experience he moved a year and a half ago to Amsterdam to continue working with Levi9’s customers to help them create or optimize the way they deliver their applications to production. Pavel is a regular speaker at local meetups promoting ideas of continuous delivery, programmable infrastructure and automated testing."
diff --git a/exampleSite/data/speakers/2016/amsterdam/philipp-krenn.yml b/exampleSite/data/speakers/2016/amsterdam/philipp-krenn.yml
new file mode 100644
index 000000000..39b219189
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/philipp-krenn.yml
@@ -0,0 +1,3 @@
+name: "Philipp Krenn"
+twitter: "xeraa"
+bio: "Philipp is a Developer Advocate at Elastic, spreading the love and knowledge of full-text search, analytics, and real-time data. He is a frequent speaker at conferences and meetups about all things search & analytics, databases, cloud computing, and devops. Philipp lives in Vienna where he enjoys experimenting with software, organizing meetups, and sports."
diff --git a/exampleSite/data/speakers/2016/amsterdam/remi-bergsma.yml b/exampleSite/data/speakers/2016/amsterdam/remi-bergsma.yml
new file mode 100644
index 000000000..0aebf2be3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/remi-bergsma.yml
@@ -0,0 +1,3 @@
+name: "Remi Bergsma"
+twitter: "remibergsma"
+bio: "Remi Bergsma is an engineer with a pasion for automation. He works for Schuberg Philis, a Mission Critical outsourcing company in NL. Since about 2,5 years Remi works in the Mission Critical Cloud Team at Schuberg Philis. In this role he and his colleagues make sure their Mission Critical Cloud simply works. That is truly DevOps: from ordering, racking and automatically configuring hardware all the way to developing new features and fixing bugs in the Java and Python code. Remi is an Apache CloudStack committer/PMC member and was Release Manager for CloudStack 4.6, 4.7 and 4.8. Nowadays Remi is one of the committers in the Cosmic Cloud project. He did several talks and workshops on conferences and enjoys teaching others new stuff."
diff --git a/exampleSite/data/speakers/2016/amsterdam/robert-den-broeder.yml b/exampleSite/data/speakers/2016/amsterdam/robert-den-broeder.yml
new file mode 100644
index 000000000..358a6060f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/robert-den-broeder.yml
@@ -0,0 +1,3 @@
+name: "Robert den Broeder"
+twitter: ""
+bio: "Robert den Broeder is owner of Trigono BV and is a certified trainer / coach in IT Service Management and Organizational Behavior Management (OBM). Organizational Behavior Management (OBM) is a management approach that demonstrably increases team performance and motivation. Robert supports organizations with implementing and improving service management processes, with special attention for behavioral change, using OBM techniques and principles."
diff --git a/exampleSite/data/speakers/2016/amsterdam/simon-fisher.yml b/exampleSite/data/speakers/2016/amsterdam/simon-fisher.yml
new file mode 100644
index 000000000..32ae36622
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/simon-fisher.yml
@@ -0,0 +1,3 @@
+name: "Simon Fisher"
+twitter: "simfish85"
+bio: "Simon is a Solutions Architect at Chef, he has spent the past few years helping customers solve their Continuous Delivery problems with a variety of products and methods. In his spare time he also develops and maintains DAFNE Online, a site for people with Type 1 Diabetes in the UK. He also enjoys watching rugby, attempting to learn the piano, and learning how to be a new dad."
diff --git a/exampleSite/data/speakers/2016/amsterdam/stefan-stolzle.yml b/exampleSite/data/speakers/2016/amsterdam/stefan-stolzle.yml
new file mode 100644
index 000000000..82fa553f9
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/stefan-stolzle.yml
@@ -0,0 +1,3 @@
+name: "Stefan Stolzle"
+twitter: ""
+bio: "Stefan has been a software developer, teacher and consultant for over 10 years, he believes \"code is beautiful\" and achieving it through collaboration. On the https://services.github.com team at GitHub his focus lies in helping companies to implement and migrate Git and GitHub, and to learn about the https://guides.github.com/introduction/flow/ to write beautiful software."
diff --git a/exampleSite/data/speakers/2016/amsterdam/takahiko-ito.yml b/exampleSite/data/speakers/2016/amsterdam/takahiko-ito.yml
new file mode 100644
index 000000000..5e203ec54
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/takahiko-ito.yml
@@ -0,0 +1,3 @@
+name: "Takahiko Ito"
+twitter: "takahi_i_en"
+bio: "Takahiko Ito received his Ph.D. in Engineering at the Nara Institute of Science and Technology, specializing in graph mining. He worked at FAST's (now Microsoft) R&D group as an Asian language NLP expert before joining Recruit Technologies as an R&D engineer."
diff --git a/exampleSite/data/speakers/2016/amsterdam/tiziano-perrucci.yml b/exampleSite/data/speakers/2016/amsterdam/tiziano-perrucci.yml
new file mode 100644
index 000000000..a02e2c397
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/tiziano-perrucci.yml
@@ -0,0 +1,3 @@
+name: "Tiziano Perrucci"
+twitter: "tizianoperrucci"
+bio: I'm an independent Italian software engineer working in the software industry for more than a decade. My expertise lies in backend and system integration, never the less I've a strong background (and passion) in automation and devops. I'm a co-founder of the StarterSquad community where I take part in several teams. We earn our living working for several startups around the world. I'm a collaborative problem solver with strong analytical skills and committed to a continuous improvement process."
diff --git a/exampleSite/data/speakers/2016/amsterdam/victoria-jeffrey.yml b/exampleSite/data/speakers/2016/amsterdam/victoria-jeffrey.yml
new file mode 100644
index 000000000..64e953bb8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/victoria-jeffrey.yml
@@ -0,0 +1,3 @@
+name: "Victoria Jeffrey"
+twitter: ""
+bio: "As a software engineer at Chef, Victoria has developed on Delivery and Compliance, spending her days in her code cave battling whatever dragons come her way. Prior to joining Chef, she was an assistant teacher at her son’s school, where she spent her days getting dirty in gardens and playing games. When she’s not hiding out in her code cave, you can find her hanging with family, admiring the baby lizards in the backyard, and wishing she had a koala pet."
diff --git a/exampleSite/data/speakers/2016/amsterdam/warner-moore.yml b/exampleSite/data/speakers/2016/amsterdam/warner-moore.yml
new file mode 100644
index 000000000..b970a8f49
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/warner-moore.yml
@@ -0,0 +1,3 @@
+name: "Warner Moore"
+twitter: "warnermoore"
+bio: "Warner Moore is a technology and information security leader who is passionate about innovation and entrepreneurship having worked with tech-focused businesses nearly his entire career. When not scaling platforms and teams at CoverMyMeds, he contributes back to the community by organizing Ohio LinuxFest and DevOpsDays Ohio. Additionally, he is co-founder of the LOPSA Columbus chapter and chairs the Leadership Committee."
diff --git a/exampleSite/data/speakers/2016/amsterdam/will-button.yml b/exampleSite/data/speakers/2016/amsterdam/will-button.yml
new file mode 100644
index 000000000..8270f97c4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/amsterdam/will-button.yml
@@ -0,0 +1,3 @@
+name: "Will Button"
+twitter: "wfbutton"
+bio: "Will Button is a DevOps advocate for Trax Technologies, working to integrate DevOps methods and ideology into development and operations teams. When not at work, he can be found sharing his knowledge through lessons at http://egghead.io and http://www.pluralsight.com as well as his blog and public speaking engagements."
diff --git a/exampleSite/data/speakers/2016/berlin/alexander-schwartz.yml b/exampleSite/data/speakers/2016/berlin/alexander-schwartz.yml
new file mode 100644
index 000000000..87a5baaa6
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/alexander-schwartz.yml
@@ -0,0 +1,3 @@
+name: "Alexander Schwartz"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/anthony-stanton.yml b/exampleSite/data/speakers/2016/berlin/anthony-stanton.yml
new file mode 100644
index 000000000..8a6599cea
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/anthony-stanton.yml
@@ -0,0 +1,3 @@
+name: "Anthony Stanton"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/anup-bishnoi.yml b/exampleSite/data/speakers/2016/berlin/anup-bishnoi.yml
new file mode 100644
index 000000000..f75cc863b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/anup-bishnoi.yml
@@ -0,0 +1,3 @@
+name: "Anup Bishnoy"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/avishai-ish-shalom.yml b/exampleSite/data/speakers/2016/berlin/avishai-ish-shalom.yml
new file mode 100644
index 000000000..8927be7ea
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/avishai-ish-shalom.yml
@@ -0,0 +1,3 @@
+name: "Avishai Ish-Shalom"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/blerim-sheqa.yml b/exampleSite/data/speakers/2016/berlin/blerim-sheqa.yml
new file mode 100644
index 000000000..dc8f5b13c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/blerim-sheqa.yml
@@ -0,0 +1,3 @@
+name: "Blerim Sheqa"
+twitter: ""
+bio: "My name is Blerim Sheqa and I work as Senior Systems Engineer at NETWAYS. In the Managed Services department I am responsible for an infrastructure that hosts multiple customer setups. In the last couple of years I spent my time on creating a fully monitored environment by using Open Source tools like Icinga2, Puppet, Graphite and Logstash. Starting from now I will support the Icinga Team in the matter of implementation of interfaces and managing technical partnerships."
diff --git a/exampleSite/data/speakers/2016/berlin/david-schmitt.yml b/exampleSite/data/speakers/2016/berlin/david-schmitt.yml
new file mode 100644
index 000000000..89dd0df44
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/david-schmitt.yml
@@ -0,0 +1,3 @@
+name: "David Schmitt"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/eric-maxwell.yml b/exampleSite/data/speakers/2016/berlin/eric-maxwell.yml
new file mode 100644
index 000000000..b6cebaf5f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/eric-maxwell.yml
@@ -0,0 +1,3 @@
+name: "Eric Maxwell"
+twitter: ""
+bio: "Eric Maxwell is a Success Engineer at Chef Software and is focused on making companies more awesome by helping them 'do the DevOps' and enabling them to ship at velocity. In past lives, Eric was a back-end C# engineer, a big-data engineer playing in the Hadoop ecosystem, and a professional social engineer working in the InfoSec world."
diff --git a/exampleSite/data/speakers/2016/berlin/francois-le-droff.yml b/exampleSite/data/speakers/2016/berlin/francois-le-droff.yml
new file mode 100644
index 000000000..c9b36983c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/francois-le-droff.yml
@@ -0,0 +1,3 @@
+name: "François Le Droff"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/gerald-schmidt.yml b/exampleSite/data/speakers/2016/berlin/gerald-schmidt.yml
new file mode 100644
index 000000000..762e2ff67
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/gerald-schmidt.yml
@@ -0,0 +1,3 @@
+name: "Gerald Schmidt"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/hannah-foxwell.yml b/exampleSite/data/speakers/2016/berlin/hannah-foxwell.yml
new file mode 100644
index 000000000..621b5f0f8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/hannah-foxwell.yml
@@ -0,0 +1,3 @@
+name: "Hannah Foxwell"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/james-shubin.yml b/exampleSite/data/speakers/2016/berlin/james-shubin.yml
new file mode 100644
index 000000000..b2eca69b3
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/james-shubin.yml
@@ -0,0 +1,3 @@
+name: "James Shubin"
+twitter: "purpleidea"
+bio: "James is a DevOps/Config mgmt. hacker and physiologist from Montreal, Canada. He often goes by @purpleidea on the internet, and writes 'The Technical Blog of James'. He currently works for Red Hat doing research and prototyping within systems engineering. He started a Next Generation Config Management prototype called mgmt. He studied Physiology at university and sometimes likes to talk about cardiology."
diff --git a/exampleSite/data/speakers/2016/berlin/johannes-nicolai.yml b/exampleSite/data/speakers/2016/berlin/johannes-nicolai.yml
new file mode 100644
index 000000000..b70cb1a50
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/johannes-nicolai.yml
@@ -0,0 +1,3 @@
+name: "Johannes Nicolai"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/konrad-hosemann.yml b/exampleSite/data/speakers/2016/berlin/konrad-hosemann.yml
new file mode 100644
index 000000000..a1e9375d5
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/konrad-hosemann.yml
@@ -0,0 +1,3 @@
+name: "Konrad Hosemann"
+twitter: ""
+bio: "I’m a software engineer leading ImmobilienScout24's cloud team. We are paving the way for all our services into the public cloud. The team consists of operation managers, system engineers and software developers."
diff --git a/exampleSite/data/speakers/2016/berlin/kris-buytaert.yml b/exampleSite/data/speakers/2016/berlin/kris-buytaert.yml
new file mode 100644
index 000000000..40731b2b1
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/kris-buytaert.yml
@@ -0,0 +1,3 @@
+name: "Kris Buytaert"
+twitter: "KrisBuytaert"
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/martin-thalmann.yml b/exampleSite/data/speakers/2016/berlin/martin-thalmann.yml
new file mode 100644
index 000000000..2579d0f2a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/martin-thalmann.yml
@@ -0,0 +1,3 @@
+name: "Martin Thalmann"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/michael-huettermann.yml b/exampleSite/data/speakers/2016/berlin/michael-huettermann.yml
new file mode 100644
index 000000000..5fd866731
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/michael-huettermann.yml
@@ -0,0 +1,3 @@
+name: "Michael Hüttermann"
+twitter: ""
+bio: "Author of 'Agile ALM' and 'DevOps for Developers'"
diff --git a/exampleSite/data/speakers/2016/berlin/michal-bryxi.yml b/exampleSite/data/speakers/2016/berlin/michal-bryxi.yml
new file mode 100644
index 000000000..15ef7a46b
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/michal-bryxi.yml
@@ -0,0 +1,3 @@
+name: "Michal Bryxi"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/nathen-harvey.yml b/exampleSite/data/speakers/2016/berlin/nathen-harvey.yml
new file mode 100644
index 000000000..96c0b9a64
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/nathen-harvey.yml
@@ -0,0 +1,3 @@
+name: "Nathen Harvey"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/peter-varhol.yml b/exampleSite/data/speakers/2016/berlin/peter-varhol.yml
new file mode 100644
index 000000000..fcbe43482
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/peter-varhol.yml
@@ -0,0 +1,3 @@
+name: "Peter Varhol"
+twitter: ""
+bio: "Peter Varhol is a well-known writer and speaker on software and technology topics, having authored dozens of articles and spoken at a number of industry conferences and webcasts. He has advanced degrees in computer science, applied mathematics, and psychology, and is currently a community evangelist at Dynatrace, an international software testing and application monitoring company. His past roles include technology journalist, software product manager, software developer, and university professor."
diff --git a/exampleSite/data/speakers/2016/berlin/rodrigo-campos.yml b/exampleSite/data/speakers/2016/berlin/rodrigo-campos.yml
new file mode 100644
index 000000000..9f786da87
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/rodrigo-campos.yml
@@ -0,0 +1,3 @@
+name: "Rodrigo Campos"
+twitter: ""
+bio: "I work as a Production Engineering manager at Facebook in London"
diff --git a/exampleSite/data/speakers/2016/berlin/romain-pelisse.yml b/exampleSite/data/speakers/2016/berlin/romain-pelisse.yml
new file mode 100644
index 000000000..49b849915
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/romain-pelisse.yml
@@ -0,0 +1,3 @@
+name: "Romain Pelisse"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/berlin/tp-honey.yml b/exampleSite/data/speakers/2016/berlin/tp-honey.yml
new file mode 100644
index 000000000..bc2be4b9e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/berlin/tp-honey.yml
@@ -0,0 +1,3 @@
+name: "TP Honey"
+twitter: ""
+bio: ""
diff --git a/exampleSite/data/speakers/2016/boise/-kelsey-hightower.yml b/exampleSite/data/speakers/2016/boise/-kelsey-hightower.yml
new file mode 100644
index 000000000..8a194d4c2
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/-kelsey-hightower.yml
@@ -0,0 +1,12 @@
+---
+ name: Kelsey Hightower
+ twitter: kelseyhightower
+ bio: |
+ Kelsey has worn every hat possible throughout his career in tech and
+ enjoys leadership roles focused on making things happen and shipping
+ software.
+
+ Kelsey is a strong open source advocate focused on building simple tools
+ that make people smile. When he is not slinging Go code you can catch
+ him giving technical workshops covering everything from Programming,
+ System Administration and Kubernetes.
diff --git a/exampleSite/data/speakers/2016/boise/-vm-brasseur.yml b/exampleSite/data/speakers/2016/boise/-vm-brasseur.yml
new file mode 100644
index 000000000..8d7b7c130
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/-vm-brasseur.yml
@@ -0,0 +1,12 @@
+---
+ name: VM Brasseur
+ twitter: vmbrasseur
+ bio: |
+ VM Brasseur (aka Vicky) is a manager of technical people, projects,
+ processes, products, and p^Hbusinesses. In her nearly 20 years in the
+ tech industry, Vicky has been an analyst, programmer, product manager,
+ software engineering manager, technical business consultant, and
+ director of software engineering. Currently, she is a senior
+ engineering manager at Hewlett Packard Enterprise, serving a team of
+ developers 100% dedicated to upstream open source development on
+ OpenStack. Vicky [occasionally blogs](http://anonymoushash.vmbrasseur.com/).
diff --git a/exampleSite/data/speakers/2016/boise/alan-kraft.yml b/exampleSite/data/speakers/2016/boise/alan-kraft.yml
new file mode 100644
index 000000000..e2931ac6d
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/alan-kraft.yml
@@ -0,0 +1,9 @@
+---
+ name: "Alan Kraft"
+ twitter: ""
+ bio: |
+ After an early career in UNIX and Linux system administration, Alan now
+ works on hybrid cloud computing, Linux Containers, and DevOps at USPTO.
+ His current interests include infrastructure as code, systems thinking
+ & learning organizations, and the application of concepts from safety
+ science and complexity theory to DevOps.
diff --git a/exampleSite/data/speakers/2016/boise/baruch-sadogursky.yml b/exampleSite/data/speakers/2016/boise/baruch-sadogursky.yml
new file mode 100644
index 000000000..97e13fbff
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/baruch-sadogursky.yml
@@ -0,0 +1,15 @@
+---
+ name: "Baruch Sadogursky"
+ twitter: "jbaruch"
+ bio: |
+ Baruch Sadogursky (a.k.a JBaruch) is the Developer Advocate of JFrog,
+ the creators of Artifactory Binary Repository, the home of Bintray, and
+ JavaOne 2011 Duke Choice Awards winner.
+
+ For a living he hangs out with the JFrog tech leaders, writes some code
+ around Artifactory and Bintray, and then speaks and blogs about all
+ that. He does it repeatedly for the last 10 years and enjoys every
+ moment of it.
+
+ Baruch is [@jbaruch](https://twitter.com/jbaruch) on twitter and mostly
+ blogs on http://blog.bintray.com and http://blogs.jfrog.org.
diff --git a/exampleSite/data/speakers/2016/boise/ben-rockwood.yml b/exampleSite/data/speakers/2016/boise/ben-rockwood.yml
new file mode 100644
index 000000000..3665dce20
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/ben-rockwood.yml
@@ -0,0 +1,12 @@
+---
+ name: "Ben Rockwood"
+ twitter: "benr"
+ bio: |
+ Ben Rockwood is the Director of IT & Operations at Chef. He has been a
+ UNIX System Administrator for over 20 years and an Operations
+ Management junkie for the last 8. Between 2006 and 2014 he was the
+ Director of Operations at Joyent, one of the first IaaS Cloud
+ providers. He recently moved to Seattle with his super-hot wife and
+ their 5 children.
+
+ Ben blogs at http://cuddletech.com/.
diff --git a/exampleSite/data/speakers/2016/boise/caskey-dickson.yml b/exampleSite/data/speakers/2016/boise/caskey-dickson.yml
new file mode 100644
index 000000000..daa80415e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/caskey-dickson.yml
@@ -0,0 +1,16 @@
+---
+ name: "Caskey Dickson"
+ twitter: "caskey"
+ bio: |
+ Caskey L. Dickson is a Site Reliability Engineer at Microsoft where he
+ is part of the leadership team reinventing operations at Azure. Before
+ that he was at Google where he worked as an SRE/SWE writing and
+ maintaining monitoring services that operate at “Google scale” as well
+ as a few business intelligence pipelines and maybe a script or two. He
+ has worked in online services since 1995 when he turned up his first
+ web server and has been online ever since. Before working at Google, he
+ was a senior developer at Symantec, wrote software for various Internet
+ tartups such as CitySearch and CarsDirect, ran a consulting company,
+ and even taught undergraduate and graduate computer science at Loyola
+ Marymount University. He has a B.S. in Computer Science, a Masters in
+ Systems Engineering, and an M.B.A from Loyola Marymount.
diff --git a/exampleSite/data/speakers/2016/boise/corey-quinn.yml b/exampleSite/data/speakers/2016/boise/corey-quinn.yml
new file mode 100644
index 000000000..543f9ef32
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/corey-quinn.yml
@@ -0,0 +1,13 @@
+---
+ name: Corey Quinn
+ twitter: QuinnyPig
+ bio: |
+ Principal at The Quinn Advisory Group, Corey has a history as an
+ engineering manager, public speaker, and advocate for business
+ resilience through processes that aren't actively ridiculous. He
+ specializes in helping FinTech companies leverage cloud technologies
+ while managing and mitigating risk.
+
+ Outside of his professional work, Corey is known for overdressing,
+ telling entertaining stories, and carrying a cigarette case full of
+ drink umbrellas.
diff --git a/exampleSite/data/speakers/2016/boise/dan-isla.yml b/exampleSite/data/speakers/2016/boise/dan-isla.yml
new file mode 100644
index 000000000..c9da15713
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/dan-isla.yml
@@ -0,0 +1,13 @@
+---
+ name: "Dan Isla"
+ twitter: "danisla"
+ bio: |
+ Dan Isla is a Data Scientist in the Office of Chief Technology and
+ Innovation at NASA's Jet Propulsion Laboratory. For the past 7 years,
+ Isla has worked on the teams that build, launch and operate robotic
+ spacecraft throughout the solar system. Legacy is everywhere in
+ Aerospace and after seeing the scale of the data problems and
+ challenges that face our missions, Isla has now dedicated his time to
+ infusing the latest big data tools, cloud computing solutions, and
+ container platforms to revolutionize how we operate interplanetary
+ spacecraft.
diff --git a/exampleSite/data/speakers/2016/boise/darryl-bowler.yml b/exampleSite/data/speakers/2016/boise/darryl-bowler.yml
new file mode 100644
index 000000000..665483b5e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/darryl-bowler.yml
@@ -0,0 +1,11 @@
+---
+ name: "Darryl Bowler"
+ twitter: "darrylbowler"
+ bio: |
+ Darryl is a manager within Accenture DevOps practice and his working
+ roles include project management, product development, engagement
+ management and architecture. In the last six years, Darryl’s primary
+ focus has been delivering client value through agile methodologies and
+ DevOps. Currently, he is responsible for establishing a DevOps
+ capability within a digital transformation program for a major mobile
+ communications provider.
diff --git a/exampleSite/data/speakers/2016/boise/dave-hahn.yml b/exampleSite/data/speakers/2016/boise/dave-hahn.yml
new file mode 100644
index 000000000..16b91d6a0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/dave-hahn.yml
@@ -0,0 +1,7 @@
+---
+ name: "Dave Hahn"
+ twitter: "relix42"
+ bio: |
+ Dave Hahn is a Sr SRE on the Critical Operations & Reliability
+ Engineering team at Netflix. The CORE team is on the fore front of
+ availability for Netflix streaming service. Dave is very serious.
diff --git a/exampleSite/data/speakers/2016/boise/dave-harrison.yml b/exampleSite/data/speakers/2016/boise/dave-harrison.yml
new file mode 100644
index 000000000..0e3735b43
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/dave-harrison.yml
@@ -0,0 +1,15 @@
+---
+ name: Dave Harrison
+ twitter: ""
+ bio: |
+ Dave is an Application Development Manager at Microsoft where he
+ utilizes his expertise and technical background to help solve dev team
+ maturity bottlenecks and help clients deliver better software, faster
+ to add more business value.
+
+ At heart he's a developer and loves solving problems creatively. Coming
+ from the relational database/data warehousing ranks, he's been writing
+ applications for about 20 years now with strong experience in a broad
+ variety of tools within the Microsoft stack. He's crazy about ALM/SDLC
+ and DevOps concepts and frequently gives presentations and chalktalks
+ on implementing Agile in the real world.
diff --git a/exampleSite/data/speakers/2016/boise/gareth-greenaway.yml b/exampleSite/data/speakers/2016/boise/gareth-greenaway.yml
new file mode 100644
index 000000000..68ab391c4
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/gareth-greenaway.yml
@@ -0,0 +1,5 @@
+---
+ name: "Gareth Greenaway"
+ twitter: "garethgreenaway"
+ bio: |
+ Lead DevOps Engineer at Croscon & Core contributor to Salt Stack.
diff --git a/exampleSite/data/speakers/2016/boise/gerie-owen.yml b/exampleSite/data/speakers/2016/boise/gerie-owen.yml
new file mode 100644
index 000000000..fc424e22c
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/gerie-owen.yml
@@ -0,0 +1,15 @@
+---
+ name: "Gerie Owen"
+ twitter: "GerieOwen"
+ bio: |
+ Gerie Owen is a test architect at Eversource Energy, Certified
+ ScrumMaster, conference presenter, and author on testing/test
+ management topics. She is developing a test center of excellence and
+ consults on test processes and tools. Gerie manages large, complex
+ projects involving multiple applications; coordinates test teams across
+ multiple time zones; and delivers high-quality projects on time and
+ within budget. She enjoys mentoring new QA leads and brings a cohesive
+ team approach to testing. Learn more about Gerie on her
+ [website](http://gerieowen.com/), her
+ [Software Testing in the Trenches](http://testinggirl.wordpress.com/)
+ blog, and on Twitter [@GerieOwen](https://twitter.com/gerieowen).
diff --git a/exampleSite/data/speakers/2016/boise/jason-hand.yml b/exampleSite/data/speakers/2016/boise/jason-hand.yml
new file mode 100644
index 000000000..907b2e016
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jason-hand.yml
@@ -0,0 +1,12 @@
+---
+ name: "Jason Hand"
+ twitter: "jasonhand"
+ bio: |
+ DevOps Evangelist at VictorOps, organizer of DevOpsDays - Rockies,
+ author of "ChatOps for Dummies", and host of a number of DevOps related
+ events in the Denver/Boulder area. Jason has spent the last 8 months
+ presenting and building content on a number of DevOps topics such as
+ Blameless Post-mortems, ChatOps, and the value of context within
+ incident management. A frequent speaker at DevOps events around the
+ country, Jason enjoys talking to audiences large and small on a variety
+ of technical and non-technical subjects.
diff --git a/exampleSite/data/speakers/2016/boise/jean-bennett.yml b/exampleSite/data/speakers/2016/boise/jean-bennett.yml
new file mode 100644
index 000000000..22f08ed35
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jean-bennett.yml
@@ -0,0 +1,4 @@
+---
+ name: "Jean Bennett"
+ twitter: "JeanBennett01"
+ bio: ""
diff --git a/exampleSite/data/speakers/2016/boise/jeff-anderson.yml b/exampleSite/data/speakers/2016/boise/jeff-anderson.yml
new file mode 100644
index 000000000..7f8ffe2d8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jeff-anderson.yml
@@ -0,0 +1,7 @@
+---
+ name: "Jeff Anderson"
+ twitter: "programm3rq"
+ bio: |
+ Jeff Anderson is a Developer Support Engineer at Docker. He has a
+ background in Linux system operations, configuration management, and
+ automation.
diff --git a/exampleSite/data/speakers/2016/boise/jonah-horowitz.yml b/exampleSite/data/speakers/2016/boise/jonah-horowitz.yml
new file mode 100644
index 000000000..c08757de8
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/jonah-horowitz.yml
@@ -0,0 +1,8 @@
+---
+ name: "Jonah Horowitz"
+ twitter: "jonahhorowitz"
+ bio: |
+ Jonah Horowitz is a Senior Site Reliability Architect at Netflix with
+ over 20 years of experience keeping servers and sites online. He
+ started with a home-built BBS and has worked at both large and small
+ tech companies including Walmart.com, Looksmart, and Quantcast.
diff --git a/exampleSite/data/speakers/2016/boise/leonid-igolnik.yml b/exampleSite/data/speakers/2016/boise/leonid-igolnik.yml
new file mode 100644
index 000000000..5b4dd9842
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/leonid-igolnik.yml
@@ -0,0 +1,19 @@
+---
+ name: "Leonid Igolnik"
+ twitter: "ligolnik"
+ bio: |
+ Leonid is technologist blending product development, product management
+ and product operations at scale. In his current role as a Vice
+ President of Engineering with CA Technologies he is responsible for
+ product development of SaaS applications for the Enterprise Security
+ space. He has spend his entire professional career building on-line
+ applications starting his career at one of the earliest internet
+ service providers in Israel. Leonid first started building large scale
+ applications in Java in 2002 while working for the 2nd largest domain
+ registrar at the time at Tucows/OpenSRS where he led the platform team.
+ Subsequently to that he held several technology leadership roles with
+ companies in Canada and US. Most recently Leonid has been responsible
+ for engineering teams at Taleo (acquired by Oracle) building
+ applications that help millions of people find jobs that have
+ propelled the company to a position of one of the 4 largest SaaS
+ companies in the world.
diff --git a/exampleSite/data/speakers/2016/boise/mary-younce.yml b/exampleSite/data/speakers/2016/boise/mary-younce.yml
new file mode 100644
index 000000000..b9eff73aa
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/mary-younce.yml
@@ -0,0 +1,9 @@
+---
+ name: Mary Younce
+ bio: |
+ As information technology risk and compliance professional, Mary has
+ had the good fortune to lead teams of talented technologists on
+ devising solutions that reduce risk and meet company goals. She’s
+ contributed over 20 years in IT operations and security roles. Mary
+ encourages technical and professional resiliency to balance
+ requirements and safeguards.
diff --git a/exampleSite/data/speakers/2016/boise/matthew-barker.yml b/exampleSite/data/speakers/2016/boise/matthew-barker.yml
new file mode 100644
index 000000000..48d60a00f
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/matthew-barker.yml
@@ -0,0 +1,10 @@
+---
+ name: "Matthew Barker"
+ twitter: "matthewabq"
+ bio: |
+ As a experienced Solutions Architect and Sales Engineer, Matthew helps
+ companies efficiently secure their applications. His broad-based
+ experience in open source software and rapid application development
+ combined with background in software security enables him to provide
+ insightful, technical guidance to companies desiring to produce secure
+ applications of high quality and with minimal license risk.
diff --git a/exampleSite/data/speakers/2016/boise/peter-varhol.yml b/exampleSite/data/speakers/2016/boise/peter-varhol.yml
new file mode 100644
index 000000000..029c10f24
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/peter-varhol.yml
@@ -0,0 +1,15 @@
+---
+ name: "Peter Varhol"
+ twitter: "pvarhol"
+ bio: |
+ Peter Varhol is principal technology evangelist at Technology Strategy
+ Research and a consulting QA lead for a leading digital design firm. An
+ accomplished and frequent speaker at technology conferences and user
+ groups, Peter’s topics cover software development to testing and
+ application lifecycle. As a technology journalist and thought leader,
+ he has authored hundreds of articles, white papers, and blog posts on
+ software development, testing, and related topics. His past roles
+ include technology journalist, software product manager, software
+ developer, and university professor. Learn more about Peter on his
+ [Cutting Edge Computing blog](https://pvarhol.wordpress.com/) and on
+ Twitter [@pvarhol](https://twitter.com/pvarhol).
diff --git a/exampleSite/data/speakers/2016/boise/seth-falcon.yml b/exampleSite/data/speakers/2016/boise/seth-falcon.yml
new file mode 100644
index 000000000..86ab6c539
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boise/seth-falcon.yml
@@ -0,0 +1,12 @@
+---
+ name: "Seth Falcon"
+ twitter: "sfalcon"
+ bio: |
+ A product focused engineering leader who builds teams that consistently
+ deliver valuable, high quality software at velocity.
+
+ Seth believes the essential elements for a high performing team are
+ trust, commitment to learning and experimentation, mechanisms for
+ measuring outcomes, and clear communication. He's helped teams increase
+ their effectiveness as an individual contributor, an engineering
+ manager, and as a leader of managers.
diff --git a/exampleSite/data/speakers/2016/boston/andreas-grabner.yml b/exampleSite/data/speakers/2016/boston/andreas-grabner.yml
new file mode 100644
index 000000000..957614464
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/andreas-grabner.yml
@@ -0,0 +1,12 @@
+bio: "Andreas Grabner is a performance enthusiast who has been working in this field\
+ \ for the last fifteen+ years. He was a developer, tester, architect and product\
+ \ evangelist for several testing and diagnostics companies such as Segue, Borland,\
+ \ Compuware and Dynatrace. In these days Andreas helps organizations finding the\
+ \ performance, scalability and architectural problems in their applications. He\
+ \ is taking his knowledge to teach others on how to spot and avoid these problems.\
+ \ He is doing that by speaking at different meetups, user groups and international\
+ \ conferences such as Star, STPCon, Agile Testing Days, Swiss Testing Day, Java\
+ \ South Africa, JavaOne, \u2026 "
+name: Andreas Grabner
+twitter: grabnerandi
+website: http://blog.dynatrace.com
diff --git a/exampleSite/data/speakers/2016/boston/andy-rosequist.yml b/exampleSite/data/speakers/2016/boston/andy-rosequist.yml
new file mode 100644
index 000000000..fe145571a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/andy-rosequist.yml
@@ -0,0 +1,5 @@
+bio: Andy is the Director of IT Operations at Zipcar. He's very passionate about collaboration
+ and transparency, as well as beards.
+name: Andy Rosequist
+twitter: blond_baron
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/anjuan-simmons.yml b/exampleSite/data/speakers/2016/boston/anjuan-simmons.yml
new file mode 100644
index 000000000..86548766a
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/anjuan-simmons.yml
@@ -0,0 +1,20 @@
+bio: "Anjuan Simmons is a technologist with a successful track record of delivering\
+ \ technology solutions from the user interface to the database. He is currently\
+ \ a software project manager and Certified Scrum Master at a leading construction\
+ \ software manufacturer, and he has previously worked as an executive for Accenture,\
+ \ Deloitte, and Infosys, all multi-billion dollar technology services companies\
+ \ with hundreds of clients around the world. \r\n\r\nAnjuan is also an energetic\
+ \ and informative speaker who often presents at conferences, seminars, schools,\
+ \ and community events. He is a sought after thought leader on Agile software development,\
+ \ design, diversity, and leadership. Drawing from his work experience as well as\
+ \ his educational background, Anjuan delivers presentations that focus on facts\
+ \ and provide simple explanations of complex ideas. \r\n\r\nAnjuan has an undergraduate\
+ \ degree in electrical engineering from the University of Texas at Austin and an\
+ \ MBA from Texas A&M University (where he was the first person voted by his fellow\
+ \ MBA students to serve as Student Speaker during their graduation ceremony). He\
+ \ lives in Houston with his beautiful wife and three amazing kids. Anjuan's hobbies\
+ \ include reading, writing, travel, and exercise. His has vowed to never again speak\
+ \ the name of his favorite member of One Direction aloud."
+name: Anjuan Simmons
+twitter: anjuan
+website: http://www.AnjuanSimmons.com
diff --git a/exampleSite/data/speakers/2016/boston/barak-chamo.yml b/exampleSite/data/speakers/2016/boston/barak-chamo.yml
new file mode 100644
index 000000000..45fa67c4e
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/barak-chamo.yml
@@ -0,0 +1,8 @@
+bio: "Barak is a passionate software developer, entrepreneur and digital artist. He's\
+ \ been working with and building startups in Tel-Aviv, London and New-York for the\
+ \ past 6 years.\r\n\r\nAn avid web developer and creative coder, he enjoys exploring\
+ \ the connection between art and technology in audio, visual and physical form and\
+ \ creates new and exciting digital experiences."
+name: Barak Chamo
+twitter: barakchamo
+website: http://github.com/barakchamo
diff --git a/exampleSite/data/speakers/2016/boston/corey-quinn.yml b/exampleSite/data/speakers/2016/boston/corey-quinn.yml
new file mode 100644
index 000000000..b9cf57619
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/corey-quinn.yml
@@ -0,0 +1,14 @@
+bio: "Corey has a long and storied history as a consultant -- long, in that every\
+ \ year he did it felt like three years, and storied, in that he's got a few. Prior\
+ \ to his current role as Director of DevOps at FutureAdvisor, he spent most of the\
+ \ past few years at a Bay Area consulting firm, where he served as a systems architect,\
+ \ ad-hoc recruiter, advocate for driving transformational change throughout organizations,\
+ \ and (due to a misunderstanding around what a \"standup meeting\" really was) an\
+ \ improvisational comic. One of the early developers behind Saltstack, Corey also\
+ \ has a rich history of contributing to various open source projects.\r\n\r\nCorey's\
+ \ hobbies include motorcycles, building custom keyboards, and drinking whiskey--\
+ \ it's a shame that they all don't work well together. He lives in San Francisco\
+ \ with his wife and two rodents of unusual size masquerading as dogs."
+name: Corey Quinn
+twitter: QuinnyPig
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/david-blank-edelman.yml b/exampleSite/data/speakers/2016/boston/david-blank-edelman.yml
new file mode 100644
index 000000000..b5fec2dd0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/david-blank-edelman.yml
@@ -0,0 +1,10 @@
+bio: David is the Technical Evangelist at Apcera. He has spent close to thirty years
+ in the systems administration/DevOps/SRE field in large multiplatform environments
+ including Brandeis University, Cambridge Technology Group, MIT Media Laboratory
+ and Northeastern University. He is the author of the O'Reilly Otter book (Automating
+ System Administration with Perl) and is a frequent invited speaker at conferences
+ in the field. David is honored to serve on the USENIX Board of Directors. He prefers
+ to pronounce Evangelist with a hard 'g'.
+name: David Blank-Edelman
+twitter: otterbook
+website: ''
diff --git a/exampleSite/data/speakers/2016/boston/david-fredricks.yml b/exampleSite/data/speakers/2016/boston/david-fredricks.yml
new file mode 100644
index 000000000..d0f1e7fa0
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/david-fredricks.yml
@@ -0,0 +1,10 @@
+bio: 'David provides consultative services to organizations on how to
+ successfully grow technical teams. His services help leaders understand current
+ candidate markets and offer realistic solutions for solving critical hiring
+ challenges. David helps clients by creating SMART personalized plans and
+ delivery models to successfully on board the right engineers. If you are
+ struggling to identify, attract and hire technical folks. Give him a call to
+ set up a meeting and discuss your situation.'
+name: David Fredricks
+twitter: 'dfreddy76'
+website: https://www.linkedin.com/pulse/devops-needs-great-managers-david-fredricks?trk=mp-author-card
diff --git a/exampleSite/data/speakers/2016/boston/elliot-murphy.yml b/exampleSite/data/speakers/2016/boston/elliot-murphy.yml
new file mode 100644
index 000000000..5bf1dfac7
--- /dev/null
+++ b/exampleSite/data/speakers/2016/boston/elliot-murphy.yml
@@ -0,0 +1,10 @@
+name: "Eliot Murphy"
+twitter: "sstatik"
+bio: "Elliot is the CEO of Kindly Ops, a DevOps and security firm focused on\
+ \ reducing the cost of healthcare innovation. Over the last year he has assisted\
+ \ organizations with operation, scaling, and 3rd party risk assessment of mission\
+ \ critical systems that conduct medical research, perform real time malware\
+ \ defense, process prescription refills, deliver therapy, and store psychiatric\
+ \ records.
+ Home
+ 
+ Contact
+ 
+ Events
+ 
+ Presentations
+ 
+ Blog
+ 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+