diff --git a/content/events/2016-capetown/conduct.md b/content/events/2016-capetown/conduct.md
new file mode 100644
index 00000000000..6e48add21a1
--- /dev/null
+++ b/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/content/events/2016-capetown/contact.md b/content/events/2016-capetown/contact.md
new file mode 100644
index 00000000000..bfa6e7c2e8d
--- /dev/null
+++ b/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/content/events/2016-capetown/location.md b/content/events/2016-capetown/location.md
new file mode 100644
index 00000000000..f9ef52eea18
--- /dev/null
+++ b/content/events/2016-capetown/location.md
@@ -0,0 +1,10 @@
++++
+date = "2016-05-07T09:47:20-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/content/events/2016-capetown/program.md b/content/events/2016-capetown/program.md
new file mode 100644
index 00000000000..e0dbcccc3f4
--- /dev/null
+++ b/content/events/2016-capetown/program.md
@@ -0,0 +1,122 @@
++++
+date = "2016-05-07T09:47:20-05:00"
+title = "program"
+type = "event"
+
++++
+
+
+
+
+
+
+
+The Schedule
+
+
+
+
Day 1
+
+
+
08:00-09:00
Registration, Breakfast, and Sponsor Booths Open
+
09:00-9:15
Opening Welcome
+
09:15-09:45
+
+
+
09:45-09:55
+ Sponsors
+
+
09:55-10:25
+
+
+
+
10:25-10:40
+ Break
+
+
+
10:40-11:10
+
+
+
+
11:10-11:20
+ Sponsors
+
+
+
11:20-11:50
+
+
+
+
11:50-13:00
Lunch (catered)
+
+
13:00-13:30
Ignites
+
+
+
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
+
+
19: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
+
+
+
09:45-09:55
+ Sponsors
+
+
09:55-10:25
+
+
+
+
10:25-10:40
+ Break
+
+
+
10:40-11:10
+
+
+
+
11:10-11:20
+ Sponsors
+
+
+
11:20-11:50
+
+
+
+
11:50-13:00
Lunch (catered)
+
+
13:00-13:30
Ignites
+
+
+
+
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
+
+
+
+
+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/content/events/2016-capetown/registration.md b/content/events/2016-capetown/registration.md
new file mode 100644
index 00000000000..e97f3b776be
--- /dev/null
+++ b/content/events/2016-capetown/registration.md
@@ -0,0 +1,13 @@
++++
+date = "2016-05-07T09:47:20-05:00"
+title = "registration"
+type = "event"
+
+
++++
+
+
+
+Embed registration iframe/link/etc.
+
+
diff --git a/content/events/2016-capetown/sponsor.md b/content/events/2016-capetown/sponsor.md
new file mode 100644
index 00000000000..756ae770f74
--- /dev/null
+++ b/content/events/2016-capetown/sponsor.md
@@ -0,0 +1,49 @@
++++
+date = "2016-05-07T09:47:20-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/content/events/2016-capetown/welcome.md b/content/events/2016-capetown/welcome.md
new file mode 100644
index 00000000000..5ef5c7d9248
--- /dev/null
+++ b/content/events/2016-capetown/welcome.md
@@ -0,0 +1,52 @@
++++
+date = "2016-05-07T09:47:20-05:00"
+title = "welcome"
+type = "event"
+aliases = ["/events/2016-capetown"]
+
++++
+
+## {{< event_start >}} - {{< event_end >}}
+
+DevOps Days is coming to {{< event_location >}}!
+
+
+
+
+
+ | 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 cptdevops >}}
+ |
+
+
diff --git a/data/events/2016-capetown.yml b/data/events/2016-capetown.yml
new file mode 100644
index 00000000000..18a7964a4cd
--- /dev/null
+++ b/data/events/2016-capetown.yml
@@ -0,0 +1,62 @@
+name: "2016-capetown" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2016" # The year of the event. Make sure it is in quotes.
+city: "Cape Town" # The city name of the event. Capitalize it.
+friendly: "2016-capetown" # 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 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.882219, -87.640530" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html
+location: "Cape Town" # 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: "Adrian Moisey"
+- name: "William Stewart"
+- name: "Cobus Bernard"
+- name: "Graeme Glass"
+- name: "Tom Bamford"
+- name: "Julia Quickfall"
+# - name: "Firstname Lastname"
+# twitter: "yourtwitterhandle"
+# employer: "Acme Anvil Co."
+organizer_email: "organizers-capetown-2016@devopsdays.org" # Put your organizer email address here
+proposal_email: "proposals-capetown-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:
+ - id: samplesponsorname
+ level: gold
+# - id: arresteddevops
+# level: community
+
+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: community
+ label: Community