Skip to content

Commit

Permalink
Merge branch 'master' of github.com:devopsdays/devopsdays-web
Browse files Browse the repository at this point in the history
Former-commit-id: 82daf99
  • Loading branch information
mattstratton committed Apr 13, 2016
2 parents 322fc03 + 3edafae commit 7974e14
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,6 @@ This is by no means complete, but a couple things to know:
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.
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.yml`. 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/2015chicagochef.yml`. (Note: there is an experimental feature for an "override" of the sponsor data; more on this feature as it is developed)
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)
6. Put the images for your sponsors in the `/static/img/sponsors` directory. They need to be PNG files and named exactly after the name of the sponsor in your event file (and the corresponding sponsor data file), i.e., `/static/img/sponsors/chef.png`.
7. You will also want to add your event's logo to the following directory (creating the directory if necessary) `/static/img/events/yyyy-city/logo.png`. The file MUST be called `logo.png`.

0 comments on commit 7974e14

Please sign in to comment.