diff --git a/README.md b/README.md index 1a1de59ce19..ed2ba4e10ea 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ Here are the steps to follow to get going as an DevOpsDays content contributor ( This is by no means complete, but a couple things to know: 1. Create a data file for your event in `data/events`, for example, `data/events/2015-chicago.yml`. It must be the same name as the directory you will create for your event. It should follow the format of `yyyy-city.yml`. It is highly recommended to just duplicate one from another event. A sample version can be found [here](https://github.com/devopsdays/devopsdays-web/blob/master/yyyy-city.yml) -2. You can either copy the files from the `/content/events/sample-event` directory into a directory named `/content/events/YYYY-city`, or do it manually as listed below. +2. You can either copy the files from the `/content/events/sample-event` directory into a directory named `/content/events/YYYY-city`, or do it manually as listed below. If you copy from the sample site, please remove `draft = true` from the frontmatter of the pages (or they won't be built) 3. Generate the pages for your event, in the following manner for each page. `hugo new events/2016-kiel/welcome.md --kind=event` 4. The `welcome.md` file needs to have a field added to its frontmatter for the alias, i.e., `aliases = ["/events/2015-chicago"]` 5. Sponsors each need a file in the data directory, as such: `data/sponsors/chef-2016.yml`. Please make sure to use the year for the sponsor (just so that the old events don't end up with newer sponsor logos, etc - but don't make one just for your city). If there is an existing sponsor and you can use it, you do not need to create the data file (or the image). If your information is different, please create a new file, such as `data/sponsors/chicagochef-2016.yml`. (Note: there is an experimental feature for an "override" of the sponsor data; more on this feature as it is developed) diff --git a/content/events/2016-chicago/conduct.md b/content/events/2016-chicago/conduct.md index 1ca9cae1018..18901b089c6 100644 --- a/content/events/2016-chicago/conduct.md +++ b/content/events/2016-chicago/conduct.md @@ -5,7 +5,7 @@ type = "event" +++ -##ANTI-HARASSMENT POLICY +## 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. @@ -21,7 +21,7 @@ Conference staff can be identified by distinct staff badges. Conference staff wi We expect participants to adhere to the code of conduct at all conference venues and conference-related social events. -##CODE OF CONDUCT +## 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. diff --git a/content/events/2016-raleigh/conduct.md b/content/events/2016-raleigh/conduct.md index 61051a15148..18901b089c6 100644 --- a/content/events/2016-raleigh/conduct.md +++ b/content/events/2016-raleigh/conduct.md @@ -1,14 +1,11 @@ +++ -City = "" -Year = "" date = "2016-03-06T21:17:08-06:00" title = "conduct" type = "event" -draft = true +++ -##ANTI-HARASSMENT POLICY +## 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. @@ -24,7 +21,7 @@ Conference staff can be identified by distinct staff badges. Conference staff wi We expect participants to adhere to the code of conduct at all conference venues and conference-related social events. -##CODE OF CONDUCT +## 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. diff --git a/content/events/2016-raleigh/contact.md b/content/events/2016-raleigh/contact.md index bf6f01a6ea4..280e81d2599 100644 --- a/content/events/2016-raleigh/contact.md +++ b/content/events/2016-raleigh/contact.md @@ -1,11 +1,7 @@ +++ -City = "Raleigh" -Year = "2016" date = "2016-03-06T21:16:08-06:00" title = "contact" type = "event" -draft = false - +++ diff --git a/content/events/2016-raleigh/location.md b/content/events/2016-raleigh/location.md index 0c6b0849c5e..5378d135c17 100644 --- a/content/events/2016-raleigh/location.md +++ b/content/events/2016-raleigh/location.md @@ -1,10 +1,7 @@ +++ -City = "" -Year = "" date = "2016-03-06T21:17:00-06:00" title = "location" type = "event" -draft = true +++