This is the repo for managing devopsdays.org.
If you discover an issue with the theme, please open an issue in the devopsdays-theme repo.
The technical details and guidelines for contributing to this repository are outlined in CONTRIBUTING.md. If you intend to contribute (and we sure hope you do!), please take a moment to review that document.
Instructions and utilities are available for managing sponsors, events, speakers, and more. Full documentation on the currently released theme is always found in themes/devopsdays-theme/REFERENCE.md.
Generally speaking, you should avoid storing any files other than logos or small images inside the repo itself (out of consideration for your fellow devopsdays organizers who have to pull down this repo). Please follow these guidelines:
- Do not upload presentations, artifacts from your event, etc. Either link to the preso on Speakerdeck/Slideshare from the presenter, or even better, create a Speakerdeck account for your event and put the presos there.
- Small, web images are fine (logos, etc). If you have high-resolution versions of your logo to share with others, please do not host them on the devopsdays-web repo.
- It is acceptable to add in a single PDF for your sponsor prospectus if you desire (in
static/events/YYYY-city), but please keep this file under 3 MB. It is better to host it on Google Drive or something similar, and then link to it from your site. - OPTIONAL - you can host your PDF's for prospectus, etc, in the repo at devopsdays/devopsdays-assets and then link to them from there. Files in that repo are presented under their relative URL at https://assets.devopsdays.org. For example, the file located at
static/events/2016/chicago/devopsdays-chicago-2016-prospectus.pdfin thedevopsdays/devopsdays-assetsrepo will be presented athttps://assets.devopsdays.org/events/2016/chicago/devopsdays-chicago-2016-prospectus.pdf
If there is a feature in the theme that you would like to see, please submit an issue to this repository and prepend the title with [ENHANCEMENT]. If you discover an issue with the theme, submit an issue and prepend the title with [BUG].
If you would like to help prioritize enhancements, please upvote the original issue by adding a reaction.
See CONTRIBUTING.md for details on our workflow, dev setup, and how to release new versions of the theme.