Add twitter handles to upcoming events & template.

data/events/2017-amsterdam.yml

@@ -1,6 +1,7 @@
 name: "2017-amsterdam" # 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: "Amsterdam" # The city name of the event. Capitalize it.
+event_twitter: "devopsams"
 friendly: "2017-amsterdam" # Four digit year and the city name in lower-case. Don't forget the dash!
 
 # All dates are in unquoted 2017-MM-DD, like this:   variable: 2016-01-05

data/events/2017-atlanta.yml

@@ -1,6 +1,7 @@
 name: "2017-atlanta" # 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: "Atlanta" # The displayed city name of the event. Capitalize it.
+event_twitter: "devopsdaysATL"
 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

data/events/2017-austin.yml

@@ -1,6 +1,7 @@
 name: "2017-austin" # 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: "Austin" # The displayed city name of the event. Capitalize it.
+event_twitter: "DoDAustin"
 
 # All dates are in unquoted 2017-MM-DD, like this:   variable: 2016-01-05
 startdate:  2017-05-04

data/events/2017-baltimore.yml

@@ -1,6 +1,7 @@
 name: "2017-baltimore"
 year: "2017"
 city: "Baltimore"
+event_twitter: "devopsdaysbmore"
 friendly: "2017-baltimore"
 
 startdate:  2017-03-07

data/events/2017-beijing.yml

@@ -1,6 +1,7 @@
 name: "2017-beijing" # 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: "Beijing" # The displayed city name of the event. Capitalize it.
+event_twitter: "DevOpsDays_CN"
 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

data/events/2017-cape-town.yml

@@ -1,6 +1,7 @@
 name: "2017-cape-town" # 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: "Cape Town" # The displayed city name of the event. Capitalize it.
+event_twitter: "devopsdayscpt"
 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
 

data/events/2017-charlotte.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdays_clt"
 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

data/events/2017-chicago.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysChi"
 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

data/events/2017-dallas.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysdfw"
 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

data/events/2017-denver.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysrox"
 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.

data/events/2017-detroit.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysdet"
 description: # A short blurb of text to describe your event, defaults to common DevOpsDays description
 status: "current"
 

data/events/2017-hartford.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdayshfd"
 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

data/events/2017-indianapolis.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "DevOpsDaysINDY"
 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

data/events/2017-minneapolis.yml

@@ -1,6 +1,7 @@
 name: "2017-minneapolis"
 year: "2017"
 city: "Minneapolis"
+event_twitter: "devopsdaysmsp"
 
 startdate: 2017-07-25
 enddate: 2017-07-26

data/events/2017-moscow.yml

@@ -1,6 +1,7 @@
 name: "2017-moscow" # 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: "Moscow" # The displayed city name of the event. Capitalize it.
+event_twitter: "DevOpsDaysMSK"
 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

data/events/2017-ohio.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "DevOpsDaysOhio"
 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.

data/events/2017-paris.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysparis"
 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

data/events/2017-portland.yml

@@ -1,6 +1,7 @@
 name: "2017-portland" # 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: "Portland" # The displayed city name of the event. Capitalize it.
+event_twitter: "devopsdayspdx"
 friendly: "2017-portland"
 
 # All dates are in unquoted 2017-MM-DD, like this:   variable: 2016-01-05

data/events/2017-salt-lake-city.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysslc"
 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

data/events/2017-sao-paulo.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdayssp"
 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

data/events/2017-seattle.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdayssea"
 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

data/events/2017-stockholm.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdayssthlm"
 description: "DevOpsdays are finally coming to Stockholm!"
 
 # All dates are in unquoted 2017-MM-DD, like this:   variable: 2016-01-05

data/events/2017-toronto.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "DevOpsDaysTO"
 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

data/events/2017-vancouver.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysyvr"
 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
 

data/events/2017-washington-dc.yml

@@ -1,6 +1,7 @@
 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.
+event_twitter: "devopsdaysdc"
 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
 

data/events/2017-zurich.yml

@@ -1,6 +1,7 @@
 name: "2017-zurich" # 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: "Zürich" # The city name of the event. Capitalize it.
+event_twitter: "devopszh"
 friendly: "2017-zurich" # Four digit year and the city name in lower-case. Don't forget the dash!
 
 # All dates are in unquoted 2017-MM-DD, like this:   variable: 2016-01-05

utilities/examples/yyyy-city.yml

@@ -1,6 +1,7 @@
 name: "yyyy-city" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
 year: "YYYY" # The year of the event. Make sure it is in quotes.
 city: "City" # The displayed city name of the event. Capitalize it.
+event_twitter: "devopsdayscityabbr" # The twitter handle for your event, which is often devopsdays and then an abbreviation for the city
 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