_config.yml

# Welcome to Jekyll!
#
# This config file is meant for settings that affect your whole blog, values
# which you are expected to set up once and rarely edit after that. If you find
# yourself editing this file very often, consider using Jekyll's data files
# feature for the data you need to update frequently.
#
# For technical reasons, this file is *NOT* reloaded automatically when you use
# 'bundle exec jekyll serve'. If you change this file, please restart the server process.

# Site settings
# These are used to personalize your new site. If you look in the HTML files,
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
# You can create any custom variable you would like, and they will be accessible
# in the templates via {{ site.myvariable }}.
title: Open Charlotte
email: info@opencharlotte.org
description: >- # this means to ignore newlines until "baseurl:"
  Open Charlotte
baseurl: '' # the subpath of your site, e.g. /blog
url: 'https://www.opencharlotte.org'
analytics_id: '137246896-1'

social:
  facebook_url: https://facebook.com/opencltbrigade
  twitter_url: https://twitter.com/opencltbrigade
  medium_url: https://medium.com/opencltbrigade
  github_url: https://github.com/opencltbrigade

include: ['_pages', '_redirects']

# Build settings
markdown: kramdown

plugins:
  - jekyll-redirect-from
  - jekyll-sitemap

meetup:
  collection_name: events
  urlname: 'Open-Charlotte-Brigade'

pagination:
  permalink: '/page/:num/'
  sort_reverse: true
  sort_field: 'date'
  enabled: true
  per_page: 5
  limit: 0

navigation_top_left:
  - title: 'Brigade'
    url: /brigade/
  - title: 'Events'
    url: /events/
  - title: 'Projects'
    url: /projects/
    new_window: true
  - title: 'Code of Conduct'
    url: /code-of-conduct/
  - title: 'Blog'
    url: '/blog/'
    new_window: true
  - title: 'About Us'
    url: /about/

navigation_top_right:

featured_event:
  headline: 'Join us at our next Community Night'
  date: 'August 14th, 2019 - 7:00pm to 9:00pm'
  description: 'You’re invited to help us re-image government and community services. Join our community of civic hackers, as we come together to help address problems that matter and make Charlotte more awesome.'
  href: 'https://www.meetup.com/Open-Charlotte-Brigade/events/hvprpqyzlbsb/'
  background_image: '/img/event-bg.jpeg'

leadership_team_members:
  executive:
    - name: 'Jill Bjers'
      title: 'Executive Director'
      photo: '/img/about/leadership/jill.jpg'
      email: 'jill@opencharlotte.org'
      linkedin: 'jillzey'
    - name: 'Andrew Natoli'
      title: 'Co-Director'
      photo: '/img/about/leadership/andrew.jpg'
      email: 'andrew@opencharlotte.org'
      linkedin: 'andrewnatoli'
    - name: 'Jim Van Fleet'
      title: 'Senior Advisor'
      photo: '/img/about/leadership/jim.jpg'
      email: 'jim@opencharlotte.org'
      linkedin: 'jimvanfleet'
  marketing:
    - name: 'Kazi Smith'
      title: 'Marketing Team'
      photo: '/img/about/leadership/kazi.jpg'
      email: 'kazi@opencharlotte.org'
      linkedin: 'kazi-smith-a6196049'
    - name: 'Dawn Peterson'
      title: 'Marketing Team'
      photo: '/img/about/leadership/dawn.jpg'
      linkedin: 'dawn-peterson-9a882862'
  technology:
    - name: 'Ryan Edge'
      title: 'Technology Team'
      photo: '/img/about/leadership/ryan.jpg'
      email: 'ryan@opencharlotte.org'
      linkedin: 'ryan-edge'

exclude:
  - Gemfile
  - Gemfile.lock
  - node_modules
  - vendor/bundle/
  - vendor/cache/
  - vendor/gems/
  - vendor/ruby/
  - webpack.config.js
  - package.json
  - package-lock.json