├── .gitignore
├── .ruby-version
├── .travis.yml
├── Gemfile
├── Gemfile.lock
├── README.md
├── _config.yml
├── _data
    └── authors.yml
├── _drafts
    └── blog
    │   └── 2015-03-25-recap-q1-demo-night-by-julia-gitis.md
├── _includes
    ├── add-edit.html
    ├── application.html
    ├── breadcrumbs.html
    ├── comments.html
    ├── footer.html
    ├── header.html
    ├── ndoch_head.html
    ├── open-graph.html
    ├── page-author.html
    ├── page-meta.html
    ├── share-this.html
    ├── stories.html
    └── updates.html
├── _layouts
    ├── blog.html
    ├── default.html
    ├── job.html
    └── projects.html
├── _posts
    ├── blog
    │   ├── 2014-09-05-LocalFreeWeb.md
    │   ├── 2014-10-22-how-our-campaign-data-visualization-app-can-help-you-this-election.md
    │   ├── 2014-10-22-speaker-mattarana-on-accessibility.md
    │   ├── 2015-01-07-sf-brigade-hosts-citycampsf.md
    │   ├── 2015-01-18-code-for-san-francisco-gets-sponsored.md
    │   ├── 2015-03-25-recap-q1-demo-night-by-julia-gitis.md
    │   ├── 2015-04-09-celebrating-ethan-lang.md
    │   ├── 2015-04-29-april-12-2015-campaign-finance-summit.md
    │   ├── 2015-06-01-SF-Bay-Area-Happiness-Survey.md
    │   ├── 2016-03-24-code-across.md
    │   ├── 2016-04-09-created-meet-sf-brigade-members.md
    │   ├── 2016-04-26-sf-brigade-s-data-science-working-group.md
    │   ├── 2016-08-15-vr-data-visualization-a-new-way-to-address-community-issues.md
    │   ├── IMG_4949.JPG
    │   ├── MattArana.jpg
    │   ├── Screen Shot 2014-09-11 at 4.44.39 PM.png
    │   ├── TopTenA11yIssues.jpg
    │   ├── image00.jpg
    │   └── image01.jpg
    ├── images
    │   └── TopTenA11yIssues.jpg
    ├── jobs
    │   ├── 2015-08-17-executive-team.md
    │   ├── 2015-08-17-finance-team.md
    │   ├── 2015-08-17-hack-night-team.md
    │   ├── 2015-08-17-new-member-support-team.md
    │   ├── 2015-08-17-project-launch-team.md
    │   ├── 2015-08-17-website-and-tools-team.md
    │   ├── 2016-08-30-events-team.md
    │   └── 2016-09-04-infrastructure-team.md
    └── projects
    │   ├── 7746
    │       └── 2015-04-29-code-for-san-francisco-shared-resources.md
    │   ├── 32595
    │       └── 2014-07-26-sf-open-referral.md
    │   ├── 32597
    │       └── 2015-01-24-code-for-san-francisco-website.md
    │   └── 32601
    │       └── 2015-06-03-sf-cycleready.md
├── about
    ├── index.html
    └── privacy_policy.html
├── api
    ├── authors.json
    └── tags.json
├── blog
    ├── feed.xml
    └── index.html
├── codeacross
    └── index.html
├── css
    ├── bootstrap.min.css
    ├── font-awesome.min.css
    └── sfbrigade.css
├── events
    └── index.html
├── favicon.ico
├── fonts
    ├── FontAwesome.otf
    ├── fontawesome-webfont.eot
    ├── fontawesome-webfont.svg
    ├── fontawesome-webfont.ttf
    ├── fontawesome-webfont.woff
    ├── glyphicons-halflings-regular.eot
    ├── glyphicons-halflings-regular.svg
    ├── glyphicons-halflings-regular.ttf
    └── glyphicons-halflings-regular.woff
├── getstarted
    └── index.html
├── hackforchange
    ├── 2015recap
    │   └── index.html
    ├── index.html
    ├── judges
    │   └── index.html
    ├── participate
    │   └── index.html
    ├── partners
    │   └── index.html
    ├── project-guidelines
    │   └── index.html
    ├── projectreqs
    │   └── index.html
    ├── projects
    │   └── index.html
    ├── resources
    │   ├── NDoCH_Logo-02-02_WhiteBackground.png
    │   ├── NDoCH_onepager.pdf
    │   ├── NDoCH_webflyer_WhiteBackground.png
    │   └── index.html
    ├── schedule
    │   └── index.html
    └── sponsors
    │   └── index.html
├── happiness
    ├── happyform.js
    ├── index.html
    └── thankyou.html
├── images
    ├── 9thHoward.png
    ├── Jesse.jpg
    ├── NDoCH_banner-02_WhiteBackground.png
    ├── NDoCH_banner-2.png
    ├── NDoCH_webflyer_WhiteBackground.png
    ├── ayoriselassie.jpeg
    ├── blog
    │   ├── EthanAbroad.jpg
    │   ├── EthanProfessional.jpg
    │   ├── LocalFreeWebText.jpg
    │   ├── MattArana.jpg
    │   └── TopTenA11yIssues.jpg
    ├── cfsf.png
    ├── danparham.jpg
    ├── goldengate-top.jpg
    ├── headshot 2.15.16.jpg
    ├── petershanley.jpg
    ├── projects
    │   └── ohana-screen.png
    ├── sponsors
    │   ├── CfA_logo.jpg
    │   ├── Imagineh2o.png
    │   ├── MSFTlogo.png
    │   ├── code-for-america.jpg
    │   └── galvanize.png
    └── uploads
    │   ├── IMG_1846.jpg
    │   ├── IMG_2066.jpg
    │   ├── IMG_2084.jpg
    │   ├── Screen Shot 2015-01-14 at 11.33.05 AM.png
    │   ├── Screen Shot 2015-01-14 at 9.39.41 AM.png
    │   ├── first.png
    │   └── gyver.png
├── index.html
├── jobs
    ├── faq
    │   └── index.md
    └── index.html
├── js
    ├── bootstrap.min.js
    ├── jquery-2.1.1.min.js
    ├── jquery.validate.min.js
    ├── moment.min.js
    ├── mustache.js
    ├── projectData.js
    ├── projects.js
    ├── resources.js
    └── sponsors.js
├── people
    └── index.html
├── projects.csv
├── projects
    ├── details.html
    └── index.html
├── scripts
    ├── audit.js
    ├── setup
    └── test
├── sfperspectives
    └── index.html
└── signup
    └── index.html


/.gitignore:
--------------------------------------------------------------------------------
1 | .DS_Store
2 | _site/
3 | CNAME
4 | .c9
5 | node_modules
6 | 


--------------------------------------------------------------------------------
/.ruby-version:
--------------------------------------------------------------------------------
1 | 2.4.2
2 | 


--------------------------------------------------------------------------------
/.travis.yml:
--------------------------------------------------------------------------------
 1 | sudo: false
 2 | language: ruby
 3 | env:
 4 |   - PATH=$HOME/bin:$PATH
 5 | install:
 6 |   # install newer phantomjs, see https://github.com/travis-ci/travis-ci/issues/3225 for discussion
 7 |   - mkdir $HOME/bin
 8 |   - curl https://s3.amazonaws.com/travis-phantomjs/phantomjs-2.0.0-ubuntu-12.04.tar.bz2 | tar Oxjv phantomjs > $HOME/bin/phantomjs
 9 |   - chmod +x $HOME/bin/phantomjs
10 |   - scripts/setup
11 | before_script:
12 |   - phantomjs --version
13 |   - bundle exec jekyll serve --detach
14 | script:
15 |   - scripts/test
16 | 


--------------------------------------------------------------------------------
/Gemfile:
--------------------------------------------------------------------------------
1 | source 'https://rubygems.org'
2 | ruby "2.4.2"
3 | 
4 | gem 'github-pages'
5 | 


--------------------------------------------------------------------------------
/Gemfile.lock:
--------------------------------------------------------------------------------
  1 | GEM
  2 |   remote: https://rubygems.org/
  3 |   specs:
  4 |     activesupport (4.2.9)
  5 |       i18n (~> 0.7)
  6 |       minitest (~> 5.1)
  7 |       thread_safe (~> 0.3, >= 0.3.4)
  8 |       tzinfo (~> 1.1)
  9 |     addressable (2.5.2)
 10 |       public_suffix (>= 2.0.2, < 4.0)
 11 |     coffee-script (2.4.1)
 12 |       coffee-script-source
 13 |       execjs
 14 |     coffee-script-source (1.11.1)
 15 |     colorator (1.1.0)
 16 |     concurrent-ruby (1.0.5)
 17 |     ethon (0.11.0)
 18 |       ffi (>= 1.3.0)
 19 |     execjs (2.7.0)
 20 |     faraday (0.13.1)
 21 |       multipart-post (>= 1.2, < 3)
 22 |     ffi (1.9.18)
 23 |     forwardable-extended (2.6.0)
 24 |     gemoji (3.0.0)
 25 |     github-pages (167)
 26 |       activesupport (= 4.2.9)
 27 |       github-pages-health-check (= 1.3.5)
 28 |       jekyll (= 3.6.2)
 29 |       jekyll-avatar (= 0.5.0)
 30 |       jekyll-coffeescript (= 1.0.2)
 31 |       jekyll-default-layout (= 0.1.4)
 32 |       jekyll-feed (= 0.9.2)
 33 |       jekyll-gist (= 1.4.1)
 34 |       jekyll-github-metadata (= 2.9.3)
 35 |       jekyll-mentions (= 1.2.0)
 36 |       jekyll-optional-front-matter (= 0.2.0)
 37 |       jekyll-paginate (= 1.1.0)
 38 |       jekyll-readme-index (= 0.1.0)
 39 |       jekyll-redirect-from (= 0.12.1)
 40 |       jekyll-relative-links (= 0.5.1)
 41 |       jekyll-sass-converter (= 1.5.0)
 42 |       jekyll-seo-tag (= 2.3.0)
 43 |       jekyll-sitemap (= 1.1.1)
 44 |       jekyll-swiss (= 0.4.0)
 45 |       jekyll-theme-architect (= 0.1.0)
 46 |       jekyll-theme-cayman (= 0.1.0)
 47 |       jekyll-theme-dinky (= 0.1.0)
 48 |       jekyll-theme-hacker (= 0.1.0)
 49 |       jekyll-theme-leap-day (= 0.1.0)
 50 |       jekyll-theme-merlot (= 0.1.0)
 51 |       jekyll-theme-midnight (= 0.1.0)
 52 |       jekyll-theme-minimal (= 0.1.0)
 53 |       jekyll-theme-modernist (= 0.1.0)
 54 |       jekyll-theme-primer (= 0.5.2)
 55 |       jekyll-theme-slate (= 0.1.0)
 56 |       jekyll-theme-tactile (= 0.1.0)
 57 |       jekyll-theme-time-machine (= 0.1.0)
 58 |       jekyll-titles-from-headings (= 0.4.0)
 59 |       jemoji (= 0.8.1)
 60 |       kramdown (= 1.14.0)
 61 |       liquid (= 4.0.0)
 62 |       listen (= 3.0.6)
 63 |       mercenary (~> 0.3)
 64 |       minima (= 2.1.1)
 65 |       rouge (= 2.2.1)
 66 |       terminal-table (~> 1.4)
 67 |     github-pages-health-check (1.3.5)
 68 |       addressable (~> 2.3)
 69 |       net-dns (~> 0.8)
 70 |       octokit (~> 4.0)
 71 |       public_suffix (~> 2.0)
 72 |       typhoeus (~> 0.7)
 73 |     html-pipeline (2.7.1)
 74 |       activesupport (>= 2)
 75 |       nokogiri (>= 1.4)
 76 |     i18n (0.9.1)
 77 |       concurrent-ruby (~> 1.0)
 78 |     jekyll (3.6.2)
 79 |       addressable (~> 2.4)
 80 |       colorator (~> 1.0)
 81 |       jekyll-sass-converter (~> 1.0)
 82 |       jekyll-watch (~> 1.1)
 83 |       kramdown (~> 1.14)
 84 |       liquid (~> 4.0)
 85 |       mercenary (~> 0.3.3)
 86 |       pathutil (~> 0.9)
 87 |       rouge (>= 1.7, < 3)
 88 |       safe_yaml (~> 1.0)
 89 |     jekyll-avatar (0.5.0)
 90 |       jekyll (~> 3.0)
 91 |     jekyll-coffeescript (1.0.2)
 92 |       coffee-script (~> 2.2)
 93 |       coffee-script-source (~> 1.11.1)
 94 |     jekyll-default-layout (0.1.4)
 95 |       jekyll (~> 3.0)
 96 |     jekyll-feed (0.9.2)
 97 |       jekyll (~> 3.3)
 98 |     jekyll-gist (1.4.1)
 99 |       octokit (~> 4.2)
100 |     jekyll-github-metadata (2.9.3)
101 |       jekyll (~> 3.1)
102 |       octokit (~> 4.0, != 4.4.0)
103 |     jekyll-mentions (1.2.0)
104 |       activesupport (~> 4.0)
105 |       html-pipeline (~> 2.3)
106 |       jekyll (~> 3.0)
107 |     jekyll-optional-front-matter (0.2.0)
108 |       jekyll (~> 3.0)
109 |     jekyll-paginate (1.1.0)
110 |     jekyll-readme-index (0.1.0)
111 |       jekyll (~> 3.0)
112 |     jekyll-redirect-from (0.12.1)
113 |       jekyll (~> 3.3)
114 |     jekyll-relative-links (0.5.1)
115 |       jekyll (~> 3.3)
116 |     jekyll-sass-converter (1.5.0)
117 |       sass (~> 3.4)
118 |     jekyll-seo-tag (2.3.0)
119 |       jekyll (~> 3.3)
120 |     jekyll-sitemap (1.1.1)
121 |       jekyll (~> 3.3)
122 |     jekyll-swiss (0.4.0)
123 |     jekyll-theme-architect (0.1.0)
124 |       jekyll (~> 3.5)
125 |       jekyll-seo-tag (~> 2.0)
126 |     jekyll-theme-cayman (0.1.0)
127 |       jekyll (~> 3.5)
128 |       jekyll-seo-tag (~> 2.0)
129 |     jekyll-theme-dinky (0.1.0)
130 |       jekyll (~> 3.5)
131 |       jekyll-seo-tag (~> 2.0)
132 |     jekyll-theme-hacker (0.1.0)
133 |       jekyll (~> 3.5)
134 |       jekyll-seo-tag (~> 2.0)
135 |     jekyll-theme-leap-day (0.1.0)
136 |       jekyll (~> 3.5)
137 |       jekyll-seo-tag (~> 2.0)
138 |     jekyll-theme-merlot (0.1.0)
139 |       jekyll (~> 3.5)
140 |       jekyll-seo-tag (~> 2.0)
141 |     jekyll-theme-midnight (0.1.0)
142 |       jekyll (~> 3.5)
143 |       jekyll-seo-tag (~> 2.0)
144 |     jekyll-theme-minimal (0.1.0)
145 |       jekyll (~> 3.5)
146 |       jekyll-seo-tag (~> 2.0)
147 |     jekyll-theme-modernist (0.1.0)
148 |       jekyll (~> 3.5)
149 |       jekyll-seo-tag (~> 2.0)
150 |     jekyll-theme-primer (0.5.2)
151 |       jekyll (~> 3.5)
152 |       jekyll-github-metadata (~> 2.9)
153 |       jekyll-seo-tag (~> 2.2)
154 |     jekyll-theme-slate (0.1.0)
155 |       jekyll (~> 3.5)
156 |       jekyll-seo-tag (~> 2.0)
157 |     jekyll-theme-tactile (0.1.0)
158 |       jekyll (~> 3.5)
159 |       jekyll-seo-tag (~> 2.0)
160 |     jekyll-theme-time-machine (0.1.0)
161 |       jekyll (~> 3.5)
162 |       jekyll-seo-tag (~> 2.0)
163 |     jekyll-titles-from-headings (0.4.0)
164 |       jekyll (~> 3.3)
165 |     jekyll-watch (1.5.0)
166 |       listen (~> 3.0, < 3.1)
167 |     jemoji (0.8.1)
168 |       activesupport (~> 4.0, >= 4.2.9)
169 |       gemoji (~> 3.0)
170 |       html-pipeline (~> 2.2)
171 |       jekyll (>= 3.0)
172 |     kramdown (1.14.0)
173 |     liquid (4.0.0)
174 |     listen (3.0.6)
175 |       rb-fsevent (>= 0.9.3)
176 |       rb-inotify (>= 0.9.7)
177 |     mercenary (0.3.6)
178 |     mini_portile2 (2.3.0)
179 |     minima (2.1.1)
180 |       jekyll (~> 3.3)
181 |     minitest (5.10.3)
182 |     multipart-post (2.0.0)
183 |     net-dns (0.8.0)
184 |     nokogiri (1.8.1)
185 |       mini_portile2 (~> 2.3.0)
186 |     octokit (4.7.0)
187 |       sawyer (~> 0.8.0, >= 0.5.3)
188 |     pathutil (0.16.0)
189 |       forwardable-extended (~> 2.6)
190 |     public_suffix (2.0.5)
191 |     rb-fsevent (0.10.2)
192 |     rb-inotify (0.9.10)
193 |       ffi (>= 0.5.0, < 2)
194 |     rouge (2.2.1)
195 |     safe_yaml (1.0.4)
196 |     sass (3.5.3)
197 |       sass-listen (~> 4.0.0)
198 |     sass-listen (4.0.0)
199 |       rb-fsevent (~> 0.9, >= 0.9.4)
200 |       rb-inotify (~> 0.9, >= 0.9.7)
201 |     sawyer (0.8.1)
202 |       addressable (>= 2.3.5, < 2.6)
203 |       faraday (~> 0.8, < 1.0)
204 |     terminal-table (1.8.0)
205 |       unicode-display_width (~> 1.1, >= 1.1.1)
206 |     thread_safe (0.3.6)
207 |     typhoeus (0.8.0)
208 |       ethon (>= 0.8.0)
209 |     tzinfo (1.2.4)
210 |       thread_safe (~> 0.1)
211 |     unicode-display_width (1.3.0)
212 | 
213 | PLATFORMS
214 |   ruby
215 | 
216 | DEPENDENCIES
217 |   github-pages
218 | 
219 | RUBY VERSION
220 |    ruby 2.4.2p198
221 | 
222 | BUNDLED WITH
223 |    1.15.4
224 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
  1 | # CodeForSanFrancisco.org [![Build Status](https://travis-ci.org/sfbrigade/sfbrigade.github.io.svg?branch=master)](https://travis-ci.org/sfbrigade/sfbrigade.github.io)
  2 | 
  3 | **Note: This repo is deprecated, the brigade has since moved to an installation of Brigadehub. If you're noticing an issue with something on the current site, please contact the leadership team at Code for San Francisco for further support.***
  4 | 
  5 | The website for the Code for San Francisco Brigade
  6 | 
  7 | ### Goals
  8 | 1. Explain what Code for San Francisco is and the type of work we do.
  9 | 2. To celebrate our events, projects, and discussions!
 10 | 4. Encourage current and new members to participate with clear ways to get involved.
 11 | 5. To have this site be easily reused by other Brigades just starting out.
 12 | 
 13 | ## Blogging Instructions
 14 | If you are tasked with writing posts for the site blog, follow these instructions:
 15 | 
 16 | What you'll need:
 17 | - a github account with access to the sfbrigade github organization.
 18 | (ask somebody at san francisco brigade for this)
 19 | 
 20 | To create a new post:
 21 | - go to http://prose.io/#sfbrigade/sfbrigade.github.io/tree/master/_posts/blog
 22 | - if the page asks you to "authorize with github", click the authorize button
 23 | note: ensure you are signed in with your github account
 24 | - create a new blog post by clicking the "new file" button
 25 | there are various controls for formatting text, links and creating images
 26 | 
 27 | To add an image:
 28 | - click on the add image button.
 29 | - click "selecting one".
 30 | - pick a file on your local computer.
 31 | - in the "image url" field, ensure to change the url from something like
 32 | "_posts/blog/yourimagename.jpg"
 33 | to
 34 | "images/blog/yourimagename.jpg"
 35 | this is changing the path of the image to be images/blog/ rather then _posts/blog.
 36 | !this is important, as the image will not work if this is not done!
 37 | - add in alt text for the image. alt text is important for user's that browse by websites using text readers.
 38 | 
 39 | ## Adding a Notification
 40 | 
 41 | To add a new notification:
 42 | 
 43 | 0. Open up [_includes/header.html](https://github.com/sfbrigade/sfbrigade.github.io/blob/master/_includes/header.html)
 44 | 0. Click the `Edit` button
 45 | 0. Search for `Notification`
 46 | 0. Copy/paste the example and modify the title and description
 47 | 0. Preview your changes
 48 | 0. If satisfied, commit your changes with a small description of them. This
 49 |    will create a pull request (basically a change request) and someone will
 50 |    review your changes. If it is time sensitive, please reach out to someone on
 51 |    the website and tools team directly (see
 52 |    http://codeforsanfrancisco.org/about/) to have them review
 53 | 0. Later you should remove the notification by deleting it using the same
 54 |    process as above
 55 | 
 56 | ### Tech
 57 | 
 58 | Built using [Jekyll](http://jekyllrb.com/), [Bootstrap](http://getbootstrap.com/), and the [CfAPI](https://github.com/codeforamerica/cfapi).
 59 | 
 60 | ## Contributing
 61 | 
 62 | ### <a name="issues"></a>Submitting an Issue
 63 | 
 64 | We use [GitHub Issues](https://github.com/sfbrigade/sfbrigade.github.io/issues) to track bugs and features. We've included several of our open GitHub Issues right on our homepage using the [Civic Tech Issue Finder](http://www.codeforamerica.org/geeks/civicissues).
 65 | 
 66 | ### Running the Site Locally on Your Computer
 67 | 
 68 | To run the site locally on your own computer (most helpful for previewing your own changes), you will need Jekyll installed ([click here for Jekyll installation instructions](http://jekyllrb.com/docs/installation/).)
 69 | 
 70 | Fork and clone the repository, then install dependencies (requires **ruby** and **bundler**).
 71 | 
 72 | ```` sh
 73 | cd sfbrigade.github.io/
 74 | ./scripts/setup
 75 | ````
 76 | 
 77 | Finally, run the following command in the root directory of the repo:
 78 | 
 79 |     $ bundle exec jekyll serve
 80 | 
 81 | or
 82 | 
 83 |     $ bundle exec jekyll serve --watch
 84 | 
 85 | The latter will cause Jekyll to watch for file changes and automatically
 86 | regenerate the HTML (though you will still need to refresh the browser).
 87 | If the `--watch` flag does not work, try the following instead:
 88 | 
 89 |     $ bundle exec jekyll serve --force_polling
 90 | 
 91 | (See [here](https://github.com/guard/listen/wiki/Troubleshooting) for
 92 | background information on why `--watch` might not be working.)
 93 | 
 94 | 
 95 | Your computer should now be serving your local copy of the site at:
 96 | 
 97 | * [http://0.0.0.0:4000](http://0.0.0.0:4000)
 98 | 
 99 | If the above URL does not work (e.g. when using Chrome), try:
100 | 
101 | * [http://127.0.0.1:4000](http://127.0.0.1:4000)
102 | 
103 | (See [this issue](https://github.com/jekyll/jekyll/issues/3048) for more
104 | information.)
105 | 
106 | ### Accessibility
107 | 
108 | An accessible website/app is our number one priority. We value all
109 | contributions that put user accessibility as the top consideration when
110 | creating or modifying user interface elements. See
111 | http://www.w3.org/WAI/intro/wcag and for information/examples about accessible
112 | forms/controls see http://webaim.org/techniques/forms/controls.
113 | 
114 | ### Sharing Your Changes Using Jekit
115 | 
116 | You can use the nifty [Jekit](https://jekit.codeforamerica.org/) app to preview changes you make to this site.
117 | 
118 | To do this, fork this repo, and commit your changes on a branch to your fork. You can then preview what your changes look like by navigating to:
119 | 
120 | https://jekit.codeforamerica.org/USERNAME/sfbrigade.github.io/BRANCHNAME/
121 | 
122 | For a basic example of its usage, if GitHub user **@lolname** has made changes to the projects page on their fork (on the `master` branch), they can preview their changes using Jekit by going to:
123 | 
124 | https://jekit.codeforamerica.org/lolname/sfbrigade.github.io/master/projects
125 | 
126 | ### Submitting a Pull Request
127 | 
128 | 1. Fork the project.
129 | 2. Create a topic branch.
130 | 3. Implement your feature or bug fix.
131 | 4. Commit and push your changes.
132 | 5. Submit a pull request.
133 | 


--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
 1 | permalink: /:categories/:title/
 2 | markdown: kramdown
 3 | url: "http://old.codeforsanfrancisco.org"
 4 | defaultbranch: master
 5 | 
 6 | name: Code for San Francisco
 7 | description: A volunteer civic technology group.
 8 | 
 9 | owner:
10 |   twitter: sfbrigade
11 | 
12 | plugins:
13 |   - jekyll-redirect-from
14 | 
15 | prose:
16 |   media: 'images/uploads'
17 |   rooturl: '_posts'
18 |   siteurl: http://old.codeforsanfrancisco.org
19 |   relativeLinks: 'http://prose.github.io/starter/links.jsonp'
20 |   ignore:
21 |     - index.md
22 |     - _config.yml
23 |     - /_layouts
24 |     - /_includes
25 |     - /js
26 |   metadata:
27 |     _posts/blog:
28 |       - name: "layout"
29 |         field:
30 |           element: "hidden"
31 |           value: "blog"
32 |       - name: "title"
33 |         field:
34 |           element: "text"
35 |           label: "Title"
36 |       - name: "tags"
37 |         field:
38 |           element: "multiselect"
39 |           label: "Add Tags"
40 |           options: "http://old.codeforsanfrancisco.org/api/tags.json?callback=tagsCallback"
41 |           alterable: true
42 |           placeholder: "Choose Tags"
43 |       - name: "author"
44 |         field:
45 |           element: "select"
46 |           label: "Author"
47 |           options: "http://old.codeforsanfrancisco.org/api/authors.json?callback=authorsCallback"
48 |     _posts/projects:
49 |       - name: "layout"
50 |         field:
51 |           element: "hidden"
52 |           value: "projects"
53 |       - name: "category"
54 |         field:
55 |           element: "hidden"
56 |           value: "projects"
57 |       - name: "title"
58 |         field:
59 |           element: "text"
60 |           label: "Title"
61 |       - name: "lead"
62 |         field:
63 |           element: "text"
64 |           label: "Short description"
65 |           help: "This text shows up directly under the name of the project and should be a one sentence description."
66 |       - name: "contact"
67 |         field:
68 |           element: "text"
69 |           label: "Contact email"
70 |           help: "This is used as the contact email where form submissions will get sent"
71 |     _posts/updates:
72 |       - name: category
73 |         field:
74 |           element: "hidden"
75 |           value: "updates"
76 |       - name: title
77 |         field:
78 |           element: "text"
79 |           label: "Title"
80 | 
81 | exclude: ["lib", "config.rb", ".sass-cache", "Capfile", "config", "log", "Rakefile", "Rakefile.rb", "tmp", "*.sublime-project", "*.sublime-workspace", "Gemfile", "Gemfile.lock", "README.md", "LICENSE", "node_modules", "Gruntfile.js", "package.json", "vendor", "scripts", ".travis.yml"]
82 | 


--------------------------------------------------------------------------------
/_data/authors.yml:
--------------------------------------------------------------------------------
 1 | jason_lally:
 2 |   name: Jason Lally
 3 |   bio: "Open Data Program Manager for the City and County of San Francisco"
 4 |   gravatar: b0d79f25e915d34f7f06907322ad8060
 5 | 
 6 | joseph_tanigawa:
 7 |   name: Joseph Tanigawa
 8 |   bio: "Joseph leads the LocalFreeWeb project team"
 9 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
10 | 
11 | jesse_biroscak:
12 |   name: Jesse Biroscak
13 |   bio: "Brigade Captain"
14 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
15 | 
16 | jay_rooney:
17 |   name: Jay Rooney
18 |   bio: ""
19 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
20 | 
21 | laura_paajanen:
22 |   name: Laura Paajanen
23 |   bio: ""
24 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
25 | 
26 | lawrence_grodeska:
27 |   name: Lawrence Grodeska
28 |   bio: ""
29 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
30 | 
31 | allen_meyer:
32 |   name: Allen Meyer
33 |   bio: ""
34 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
35 | 
36 | peter_thompson:
37 |   name: Peter Thompson
38 |   bio: ""
39 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
40 | 
41 | julio_feliciano:
42 |   name: Julio Feliciano
43 |   bio: ""
44 |   gravatar: 7a6e46ed3a94c711d31f8ee4e343e958
45 | 
46 | andrew_hyder:
47 |   name: Andrew Hyder
48 |   bio: ""
49 |   gravatar: ""
50 | 
51 | desmond_liang:
52 |   name: Desmond Liang
53 |   bio: ""
54 |   gravatar: ""
55 | 
56 | maddie_suda:
57 |   name: Maddie Suda
58 |   bio: "Brigade Co-Captain"
59 |   gravatar: ""
60 | 
61 | lamar_jordan:
62 |   name: Lamar Jordan
63 |   bio: ""
64 |   gravatar: ""
65 | 
66 | laura_childs:
67 |   name: Laura Childs
68 |   bio: ""
69 |   gravatar: ""
70 | 
71 | asha_john_allen:
72 |   name: Asha John and Allen Meyer
73 |   bio: ""
74 |   gravatar: ""
75 | 
76 | vedrana_trbusic:
77 |   name: Vedrana Trbusic
78 |   bio: "Executive Coordinator at Code for SF"
79 |   gravatar: ""
80 | 
81 | kasia_rachuta:
82 |   name: Kasia Rachuta
83 |   bio: "Data Analyst Intern with background in theoretical physics, passionate about technology and impact"
84 |   gravatar: ""
85 | 


--------------------------------------------------------------------------------
/_drafts/blog/2015-03-25-recap-q1-demo-night-by-julia-gitis.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: false
 4 | title: ""
 5 | author: andrew_hyder
 6 | ---
 7 | 
 8 | ## 
 9 | On Wed Mar 18, we hosted our first demo night at the brigade! It was awesome to see what kind of projects our members are working on.
10 | 
11 | Trent Robbins presented GetSocrata. He is bilding an api wrapper to get data from Socrata ("the world leader in cloud solutions for open data and data-driven governments").
12 | 
13 | Yariv Rabinovitch presented the Bicycle Newbie Initiative. They are deploying a project for connecting experienced and newbie bicyclists during commutes. How great is that?
14 | 
15 | Sheffield Hale represented the Open Health Data Team, which is working on mapping ads for unhealthy products like tobacco and soda, like how many ads are within walking distance of schools.
16 | ![IMG_4949.JPG](/_posts/blog/IMG_4949.JPG)
17 | 
18 | Patrick Stern presented Parksafe. His team is looking to provide parking confidence for drivers in SF. They are building an app that informs users on rules surrounding potential ticketing situations.
19 | 
20 | Mike Hernandez presented SF in Progress. They are bringing more awareness and advocacy to citizens. For example, his team gives citizens a chance to show up at public hearings and get their voices heard.
21 | 
22 | Jeremy Lucas presented Project Blip- promoting online safety, security, and privacy.
23 | 
24 | Jason Lally represented SF Social Services Open Referral Database. They are mapping social services so that folks can more easily find them. Isn't that great?
25 | 
26 | Greg Arenius presented BallotAPI- make it really easy to find out what's on your ballot.
27 | 
28 | Peter Hall presented Campaign Finance Visualization- different ways to look at data around campaign finance. Their team uses data to check that people are following the law. 
29 | 
30 | Finally, Jason Lally went over the Code for San Francisco website (yes, the one you're looking at now). How can we create a website that meets the needs of the communities we serve?
31 | 
32 | Then on Wed Mar 25, 3 teams that didn't get a chance to present last week presented their work. Chris Jerdonek presented on SF Election Data. Scott presented on [World University and School](http://worlduniversityandschool.org/), which is free high quality online wiki education. David Biel presented [SFHomeless.net](http://sfhomeless.net), a valuable resource in wiki format.
33 | 
34 | Come to our hack nights to meet these teams, support their work, and learn more.


--------------------------------------------------------------------------------
/_includes/add-edit.html:
--------------------------------------------------------------------------------
 1 | <div class="add-edit">
 2 | 	{% if include.edit != false %}
 3 |   <a href="{% if page.path %}https://github.com/login/oauth/authorize?client_id=c602a8bd54b1e774f864&scope=repo&redirect_uri=http://prose.io/#{{site.github.repository_nwo}}/edit/{{site.defaultbranch}}/{{ page.path }}{% else %}https://github.com/login/oauth/authorize?client_id=c602a8bd54b1e774f864&scope=repo&redirect_uri=http://prose.io/#{{site.github.repository_nwo}}{% endif %}" target="_blank" class="btn btn-default"><i class="fa fa-pencil-square-o"></i> Edit this page in Prose.io</a>
 4 |   {% endif %}
 5 | 
 6 |   {% if include.add != false %}
 7 |   <!-- Add post -->
 8 |   <a href="https://github.com/login/oauth/authorize?client_id=c602a8bd54b1e774f864&scope=repo&redirect_uri=http://prose.io/#{{site.github.repository_nwo}}/new/{{site.defaultbranch}}/_posts/{{include.posttype}}" target="_blank" class="btn btn-default"><i class="fa fa-plus"></i> Add a post with Prose.io</a>
 9 |   {% endif %}
10 | </div>


--------------------------------------------------------------------------------
/_includes/application.html:
--------------------------------------------------------------------------------
1 | <iframe src="https://docs.google.com/a/codeforsanfrancisco.org/forms/d/e/1FAIpQLSfHoFmjPWHbqOmEPP0degJAx3zqsJNZoumHEblrlyL-byhk6g/viewform?embedded=true" width="100%" height="1600" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>
2 | 


--------------------------------------------------------------------------------
/_includes/breadcrumbs.html:
--------------------------------------------------------------------------------
 1 | {% if page.categories and page.categories != empty %}
 2 |   <nav class="breadcrumbs">
 3 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
 4 |       <a href="{{ site.url }}" itemprop="url">
 5 |         <span itemprop="title">Home</span>
 6 |       </a> › 
 7 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
 8 |       <a href="{{ site.url }}/{{ page.categories | first }}/" itemprop="url">
 9 |         <span itemprop="title">{{ page.categories | first | replace: '-',' ' | capitalize }}</span>
10 |       </a>
11 |     </span>
12 |   </nav><!-- /.breadcrumbs -->
13 | {% endif %}


--------------------------------------------------------------------------------
/_includes/comments.html:
--------------------------------------------------------------------------------
 1 | <hr />
 2 | <div id="disqus_thread"></div>
 3 | <script type="text/javascript">
 4 | 	/* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
 5 | 	var disqus_shortname = '{{ site.disqus-shortname }}';
 6 | 
 7 | 	/* * * DON'T EDIT BELOW THIS LINE * * */
 8 | 	(function() {
 9 | 		var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
10 | 		dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
11 | 		(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
12 | 	})();
13 | </script>
14 | <noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>


--------------------------------------------------------------------------------
/_includes/footer.html:
--------------------------------------------------------------------------------
 1 |  	<!-- FOOTER -->
 2 |   <div class="footer">
 3 |     <p>
 4 |       <a href="http://twitter.com/SFbrigade" rel="me">
 5 |         <i aria-hidden="true" class="fa fa-twitter-square fa-2x"></i>
 6 |         <span class="sr-only">Twitter</span>
 7 |       </a>
 8 |       <a href="http://github.com/sfbrigade" rel="me">
 9 |         <i aria-hidden="true" class="fa fa-github-square fa-2x"></i>
10 |         <span class="sr-only">Github</span>
11 |       </a>
12 |       <span class="pull-right">© Code for San Francisco 2014 | <a href="/about/privacy_policy.html">Privacy Policy</a></span>
13 |     </p>
14 |   </div>
15 | </div><!-- /.container -->
16 | <!-- Bootstrap core JavaScript
17 | ================================================== -->
18 | <!-- Placed at the end of the document so the pages load faster -->
19 | <script src="/js/jquery-2.1.1.min.js"></script>
20 | <!-- Latest compiled and minified JavaScript -->
21 | 
22 | <script type="text/javascript">
23 |   $(function() {
24 |     var checkInLinks = [
25 |       "http://c4sf.me/checkin"
26 |     ];
27 |     var today = new Date().getDay();
28 |     if(today === 3){
29 |       var checkInLink = checkInLinks[Math.floor(Math.random()*checkInLinks.length)];
30 |       $('a.check-in').attr('href', checkInLink);
31 |       $('.check-in-banner').show();
32 |     }
33 |   });
34 | </script>
35 | <script src="/js/bootstrap.min.js"></script>
36 | <script src="/js/moment.min.js"></script>
37 | <script src="/js/mustache.js"></script>
38 | <script>
39 |   (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
40 |       (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
41 |     m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
42 |   })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
43 | 
44 |   ga('create', 'UA-70064412-1', 'auto');
45 |   ga('send', 'pageview');
46 | </script>
47 | {% for script in page.scripts %}
48 |   <script src="{{ site.baseurl }}/js/{{script}}"></script>
49 | {% endfor %}
50 | 


--------------------------------------------------------------------------------
/_includes/ndoch_head.html:
--------------------------------------------------------------------------------
1 | <div class="row">
2 |   <div class="col-md-12 banner-fold">
3 |     <center>
4 |       <img alt="National Day of Civic Hacking banner" src="{{site.baseurl}}/images/NDoCH_webflyer_WhiteBackground.png" width="600px" style="margin-top: 40px;">
5 |     </center>
6 |   </div>
7 | </div>
8 | 


--------------------------------------------------------------------------------
/_includes/open-graph.html:
--------------------------------------------------------------------------------
 1 | 	<!-- Twitter Cards -->
 2 | 	<meta name="twitter:title" content="{% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}">
 3 | 	{% if page.excerpt %}<meta name="twitter:description" content="{{ page.excerpt | strip_html }}">{% endif %}
 4 | 	{% if site.owner.twitter %}<meta name="twitter:site" content="@{{ site.owner.twitter }}">{% endif %}
 5 | 	{% if author.twitter %}<meta name="twitter:creator" content="@{{ author.twitter }}">{% endif %}
 6 | 	{% if page.image.feature %}
 7 | 	<meta name="twitter:card" content="summary_large_image">
 8 | 	<meta name="twitter:image" content="{{ site.url }}/images/{{ page.image.feature }}">
 9 | 	{% else %}
10 | 	<meta name="twitter:card" content="summary">
11 | 	<meta name="twitter:image" content="{% if page.image.thumb %}{{ site.url }}/images/{{ page.image.thumb }}{% else %}{{ site.url }}/images/{{ site.logo }}{% endif %}">
12 | 	{% endif %}
13 | 	<!-- Open Graph -->
14 | 	<meta property="og:locale" content="{{ site.locale }}">
15 | 	<meta property="og:type" content="article">
16 | 	<meta property="og:title" content="{% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}">
17 | 	{% if page.excerpt %}<meta property="og:description" content="{{ page.excerpt | strip_html }}">{% endif %}
18 | 	<meta property="og:url" content="{{ page.url | replace:'index.html','' | prepend: site.url }}">
19 | 	<meta property="og:site_name" content="{{ site.title }}">


--------------------------------------------------------------------------------
/_includes/page-author.html:
--------------------------------------------------------------------------------
 1 | {% if page.author %}
 2 |   {% assign author = site.data.authors[page.author] %}{% else %}{% assign author = site.owner %}
 3 | {% endif %}
 4 | 
 5 | <div class="author-image pull-left">
 6 | 	<img src="http://gravatar.com/avatar/{{author.gravatar}}" alt="{{ author.name }}">
 7 | </div><!-- ./author-image -->
 8 | <div class="author-content clearfix">
 9 | 	<h3 class="author-name" >Written by {% if author.web %}<a href="{{ author.web }}" itemprop="author">{{ author.name }}</a>{% else %}<span itemprop="author">{{ author.name }}</span>{% endif %}</h3>
10 | 	<p class="author-bio">{{ author.bio }}</p>
11 | </div><!-- ./author-content -->


--------------------------------------------------------------------------------
/_includes/page-meta.html:
--------------------------------------------------------------------------------
1 | {% if page.date %}
2 | <div class="page-meta">
3 | 	<p>Updated {% if page.modified %}<time datetime="{{ page.modified | date: "%Y-%m-%dT%H:%M:%SZ" }}" itemprop="dateModified">{{ page.modified | date: "%B %d, %Y" }}</time>{% else %}<time datetime="{{ page.date | date: "%Y-%m-%dT%H:%M:%SZ" }}" itemprop="datePublished">{{ page.date | date: "%B %d, %Y" }}</time></p>{% endif %}
4 | </div><!-- /.page-meta -->
5 | {% endif %}


--------------------------------------------------------------------------------
/_includes/share-this.html:
--------------------------------------------------------------------------------
1 | <div class="inline-btn">
2 | 	<a class="btn-social twitter" href="https://twitter.com/intent/tweet?text={{ page.title | escape | replace:' ','%20' }}&amp;url={{ page.url | replace:'index.html','' | prepend: site.url }}&amp;via={{ site.owner.twitter }}" target="_blank"><i class="fa fa-twitter" aria-hidden="true"></i> Share on Twitter</a>
3 | 	<a class="btn-social facebook" href="https://www.facebook.com/sharer/sharer.php?u={{ page.url | replace:'index.html','' | prepend: site.url }}" target="_blank"><i class="fa fa-facebook" aria-hidden="true"></i> Share on Facebook</a>
4 | 	<a class="btn-social google-plus"  href="https://plus.google.com/share?url={{ page.url | replace:'index.html','' | prepend: site.url }}" target="_blank"><i class="fa fa-google-plus" aria-hidden="true"></i> Share on Google+</a>
5 | </div><!-- /.share-this -->


--------------------------------------------------------------------------------
/_includes/stories.html:
--------------------------------------------------------------------------------
 1 | <!-- Stories List Section -->
 2 | <section id="stories" class="bg-light-gray">
 3 |     <div class="row">
 4 |       <div class="col-lg-8">
 5 |         {% for post in site.posts %} 
 6 |         {% if post.layout == "blog" %}
 7 |         <div class="story-item">
 8 |           <div class="story-caption clearfix">
 9 |             <time datetime="{{ post.date | date: " %Y-%m-%d " }}" itemprop="datePublished">
10 |               {{ post.date | date: "%B %d, %Y" }}
11 |             </time>
12 |             <h2><a href="{{site.baseurl}}{{post.url}}">{{post.title}}</a> <small>By {{site.data.authors[post.author].name}}</small></h2>
13 |             <p class="text-muted">{{ post.excerpt | remove: '<p>' | remove: '</p>' }} <a href="{{site.baseurl}}{{post.url}}" alt="Click to read more of this blog post">Read more... </a></p>
14 |           </div>
15 |         </div>
16 |         {% endif %} 
17 |         {% endfor %}
18 |       </div>
19 |     </div>
20 | </section>
21 | 


--------------------------------------------------------------------------------
/_includes/updates.html:
--------------------------------------------------------------------------------
 1 | {% assign id_array = page.path | split:"/" %}
 2 | {% assign updates_count = 0 %}
 3 | <h2>Updates</h2>
 4 | {% for post in site.categories.updates %} 
 5 | {% assign path_array = post.path | split:"/" %}
 6 | {% if id_array[2] == path_array[2] and updates_count < 3%}
 7 | {% assign updates_count = updates_count | plus:1 %}
 8 | <div class="panel panel-default">
 9 |   <div class="panel-heading">
10 |     <h3 class="panel-title">{{post.title}} <small>{{ post.date | date: "%-d %B %Y" }}</small> <a href="{% if post.path %}https://github.com/login/oauth/authorize?client_id=c602a8bd54b1e774f864&scope=repo&redirect_uri=http://prose.io/#{{site.github.repository_nwo}}/edit/{{site.defaultbranch}}/{{ post.path }}{% else %}https://github.com/login/oauth/authorize?client_id=c602a8bd54b1e774f864&scope=repo&redirect_uri=http://prose.io/#{{site.github.repository_nwo}}{% endif %}" target="_blank" class="pull-right"><i class="fa fa-pencil-square-o"></i></a></h3>
11 |   </div>
12 |   <div class="panel-body">
13 |     {{post.content | markdownify}}
14 |   </div>
15 | </div>
16 | {% endif %}
17 | {% endfor %}
18 | {% if updates_count  == 0 %}
19 | <div>
20 | 	There are currently no updates listed for this project. Add the first one by clicking the + icon.
21 | </div>
22 | {% endif %}
23 | <a href="https://github.com/login/oauth/authorize?client_id=c602a8bd54b1e774f864&scope=repo&redirect_uri=http://prose.io/#{{site.github.repository_nwo}}/new/{{site.defaultbranch}}/_posts/updates/{{id_array[2]}}/{{ site.time | date: '%Y-%m-%d' }}-{{page.title | slugify }}-update-{{updates_count | plus:1}}.md" class="btn btn-default" style="width: 100%"><i class="fa fa-plus-square"></i> Add new update</a>


--------------------------------------------------------------------------------
/_layouts/blog.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | ---
 4 | 
 5 | <div id="main" role="main" class="blog-post">
 6 |   <div class="row">
 7 |     <div class="col-md-8">
 8 |       <article class="wrap" itemscope itemtype="http://schema.org/Article">
 9 |         {% if page.image.feature %}
10 |         <div class="page-feature">
11 |           <div class="page-image">
12 |             <img src="{{ site.url }}/images/{{ page.image.feature }}" class="page-feature-image" alt="{{ page.title }}" itemprop="image"> {% if page.image.credit %}{% include image-credit.html %}{% endif %}
13 |           </div>
14 |           <!-- /.page-image -->
15 |         </div>
16 |         <!-- /.page-feature -->
17 |         {% endif %}
18 |         <!-- include breadcrumbs.html -->
19 |         <div class="inner-wrap">
20 |           <nav class="toc"></nav>
21 |           <!-- /.toc -->
22 |           <div id="content" class="page-content" itemprop="articleBody">
23 |             {{ content }}
24 |             <hr />
25 |             <div class="page-footer">
26 |               {% if page.categories %}{% include page-author.html %}{% endif %} {% if page.share != false %}{% include share-this.html %}{% endif %}
27 | 
28 |               {% include page-meta.html %}
29 | 
30 |               {% include add-edit.html posttype="blog"%}
31 |             </div>
32 |             <!-- /.footer -->
33 |             <aside>
34 |               {% if page.comments == true %}{% include comments.html %}{% endif %}
35 |             </aside>
36 |           </div>
37 |           <!-- /.content -->
38 |         </div>
39 |         <!-- /.inner-wrap -->
40 |       </article>
41 |       <!-- ./wrap -->
42 |     </div>
43 |     <div class="col-md-4">
44 |       <!-- Stories List Section -->
45 |       <aside class="panel panel-default">
46 |         <header class="panel-heading">
47 |           <h1>Other Stories</h1>
48 |         </header>
49 |         <ul class="list-unstyled panel-body">
50 |           {% for post in site.categories.blog limit: 15 %}
51 |           {% if post.categories contains "blog" and post.path != page.path %}
52 |           <li>
53 |             <h4>
54 |               <small class="pull-right">
55 |                 {{ post.date | date: "%-d %B %Y" }}
56 |               </small>
57 |               <a href="{{ site.baseurl }}{{ post.url }}">
58 |                 {{ post.title }}
59 |               </a>
60 |             </h4>
61 |           </li>
62 |           {% endif %}
63 |           {% endfor %}
64 |         </ul>
65 |       </aside>
66 |     </div>
67 |   </div>
68 | </div>
69 | <!-- /#main -->
70 | 


--------------------------------------------------------------------------------
/_layouts/default.html:
--------------------------------------------------------------------------------
1 | {% include header.html %}
2 |   {{ content }}
3 | {% include footer.html %}
4 | </body>
5 | </html>


--------------------------------------------------------------------------------
/_layouts/job.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | ---
 4 | 
 5 | <div id="main" role="main" class="job">
 6 |   <div class="row">
 7 |     <div class="col-md-7">
 8 |       <article class="wrap" itemscope itemtype="http://schema.org/Article">
 9 |         {% if page.image.feature %}
10 |         <div class="page-feature">
11 |           <div class="page-image">
12 |             <img src="{{ site.url }}/images/{{ page.image.feature }}" class="page-feature-image" alt="{{ page.title }}" itemprop="image"> {% if page.image.credit %}{% include image-credit.html %}{% endif %}
13 |           </div>
14 |           <!-- /.page-image -->
15 |         </div>
16 |         <!-- /.page-feature -->
17 |         {% endif %}
18 |         <!-- include breadcrumbs.html -->
19 |         <div class="inner-wrap">
20 |           <nav class="toc"></nav>
21 |           <!-- /.toc -->
22 |           <a href="{{site.baseurl}}/jobs">Return to jobs overview and application</a>
23 |           <div id="content" class="page-content" itemprop="articleBody">
24 |             <h2>Background</h2>
25 |               <p>
26 |                 Code for San Francisco is a collection of creative volunteers
27 |                 working to improve the lives of San Franciscans. We continue to
28 |                 advocate for open public data, we continue to build useful civic
29 |                 apps like Adopt-a-Drain and We Vote, and we continue to
30 |                 work on civic infrastructure like Lighten.
31 |               </p>
32 |               <p><b>But <u>we want to do more</u> and to do it better.</b> To that end, we are building our leadership team.
33 |             {{ content }}
34 |             <hr />
35 |             <div class="page-footer">
36 |               <p>Please submit your application or nomination by October 1st by 11:59 PM. If you have questions about this new team and the process you can find out more on our <a href="{{site.baseurl}}/jobs/faq">FAQ page</a>.</p>
37 |               <p>We are committed to building an inclusive, diverse organization.  Everyone is encouraged to apply.</p>
38 |             </div>
39 |             <!-- /.footer -->
40 |           </div>
41 |           <!-- /.content -->
42 |         </div>
43 |         <!-- /.inner-wrap -->
44 |       </article>
45 |       <!-- ./wrap -->
46 |     </div>
47 |     <div class="col-md-5">
48 |       {% include application.html %}
49 |     </div>
50 |   </div>
51 | </div>
52 | <!-- /#main -->
53 | 


--------------------------------------------------------------------------------
/_layouts/projects.html:
--------------------------------------------------------------------------------
  1 | {% include header.html %}
  2 | <div class="row main-row">
  3 |   <div class="col-md-7">
  4 |     {{ content }} {% include add-edit.html add=false %}
  5 |   </div>
  6 |   <div class="col-md-4">
  7 |     <div class="list-group">
  8 |       <h2 class="first needs">Needs</h2>
  9 |       <button type="button" class="btn btn-success btn-block" data-toggle="modal" data-target="#exampleModal">I want to Help!</button>
 10 |     </div>
 11 | <h2 class="code">Details</h2> {% include updates.html %}
 12 |   </div>
 13 | </div>
 14 | {% include footer.html%}
 15 | 
 16 | <div class="modal fade" id="exampleModal" tabindex="-1" role="dialog" aria-labelledby="exampleModalLabel" aria-hidden="true">
 17 |   <div class="modal-dialog">
 18 |     <form method="post" action="//formspree.io/{{page.contact}}">
 19 |       <div class="modal-content">
 20 |         <div class="modal-header">
 21 |           <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">&times;</span>
 22 |           </button>
 23 |           <h4 class="modal-title" id="exampleModalLabel">Send a message</h4>
 24 |         </div>
 25 |         <div class="modal-body">
 26 |           <div class="form-group">
 27 |             <label for="name" class="control-label">Name:</label>
 28 |             <input type="text" class="form-control" id="name" name="name">
 29 |           </div>
 30 |           <div class="form-group">
 31 |             <label for="reply-email" class="control-label">Email:</label>
 32 |             <input type="text" class="form-control" id="reply-email" name="_replyto">
 33 |           </div>
 34 |           <div class="form-group">
 35 |             <label for="message-text" class="control-label">Message:</label>
 36 |             <textarea class="form-control" id="message-text" name="message"></textarea>
 37 |           </div>
 38 |           <div class="form-group">
 39 |             I'm interested in helping with...
 40 |             <br>
 41 |             <div class="checkbox">
 42 |               <label class="checkbox">
 43 |                 <input type="checkbox" id="inlineCheckbox1" value="Community Outreach" name="helpwith"> Community Outreach
 44 |               </label>
 45 |             </div>
 46 |             <div class="checkbox">
 47 |               <label class="checkbox">
 48 |                 <input type="checkbox" id="inlineCheckbox2" value="Data Research" name="helpwith"> Data Research
 49 |               </label>
 50 |             </div>
 51 |             <div class="checkbox">
 52 |               <label class="checkbox">
 53 |                 <input type="checkbox" id="inlineCheckbox3" value="Graphic Design" name="helpwith"> Graphic Design
 54 |               </label>
 55 |             </div>
 56 |             <div class="checkbox">
 57 |               <label class="checkbox">
 58 |                 <input type="checkbox" id="inlineCheckbox4" value="Marketing" name="helpwith"> Marketing
 59 |               </label>
 60 |             </div>
 61 |             <div class="checkbox">
 62 |               <label class="checkbox">
 63 |                 <input type="checkbox" id="inlineCheckbox5" value="Product Management" name="helpwith"> Product Management
 64 |               </label>
 65 |             </div>
 66 |             <div class="checkbox">
 67 |               <label class="checkbox">
 68 |                 <input type="checkbox" id="inlineCheckbox6" value="Project Management" name="helpwith"> Project Management
 69 |               </label>
 70 |             </div>
 71 |             <div class="checkbox">
 72 |               <label class="checkbox">
 73 |                 <input type="checkbox" id="inlineCheckbox7" value="Software Development" name="helpwith"> Software Development
 74 |               </label>
 75 |             </div>
 76 |             <div class="checkbox">
 77 |               <label class="checkbox">
 78 |                 <input type="checkbox" id="inlineCheckbox8" value="Subject Matter Advisor" name="helpwith"> Subject Matter Advisor
 79 |               </label>
 80 |             </div>
 81 |             <div class="checkbox">
 82 |               <label class="checkbox">
 83 |                 <input type="checkbox" id="inlineCheckbox9" value="User Research / Testing" name="helpwith"> User Research / Testing
 84 |               </label>
 85 |             </div>
 86 |             <div class="checkbox">
 87 |               <label class="checkbox">
 88 |                 <input type="checkbox" id="inlineCheckbox10" value="UX Design" name="helpwith"> UX Design
 89 |               </label>
 90 |             </div>
 91 |             <div class="checkbox">
 92 |               <label class="checkbox">
 93 |                 <input type="checkbox" id="inlineCheckbox11" value="Other" name="helpwith"> Other
 94 |               </label>
 95 |             </div>
 96 |           </div>
 97 |           <input type="hidden" name="_cc" value="jason.lally@gmail.com">
 98 |           <input type="hidden" name="_subject" value="Someone is interested in {{page.title}}" />
 99 |           <input type="text" name="_gotcha" style="display:none" />
100 |         </div>
101 |         <div class="modal-footer">
102 |           <button type="button" class="btn btn-danger" data-dismiss="modal">Close</button>
103 |           <button type="submit" class="btn btn-primary">Send message</button>
104 |         </div>
105 |     </form>
106 |     </div>
107 |   </div>
108 | </div>
109 | 
110 | <script id="needsList" type="x-tmpl-mustache">
111 |   {% raw %}
112 |   {{#needs}}
113 |     <a href="{{html_url}}" class="list-group-item">{{title}}</a>
114 |   {{/needs}}
115 |   {% endraw %}
116 | </script>
117 | <script id="repoPanels" type="x-tmpl-mustache">
118 |   {% raw %}
119 |   {{#repos}}
120 |     <div class="panel panel-default">
121 |       <div class="panel-heading">
122 |         <a href="{{link_url}}"><h3 class="panel-title">{{name}}</h3></a>
123 |       </div>
124 |       <div class="panel-body">
125 |         <p>{{description}}</p>
126 |       </div>
127 |       <div class="list-group">
128 |         <a href="{{code_url}}" class="list-group-item">Code</a>
129 |         {{#github_details}}
130 |           <a href="{{code_url}}/issues" class="list-group-item">Issues<span class="badge">{{open_issues}}</span></a>
131 |           <a href="{{code_url}}/contributors" class="list-group-item">Contributors<span class="badge">{{contributors.length}}</span></a>
132 |         {{/github_details}}
133 |       </div>
134 |     </div>
135 |   {{/repos}}
136 |   {% endraw %}
137 | </script>
138 | <script>
139 | {% assign id_array = page.path | split: "/" %}
140 | 
141 | var cfapi_project = 'http://codeforamerica.org/api/projects/{{id_array[2]}}';
142 | var projects = [];
143 | var issues = [];
144 | var repos = [];
145 | var needs = [];
146 | 
147 | $.getJSON(cfapi_project, showProjectDetails);
148 | 
149 | function showProjectDetails(response) {
150 |   // Fill up the projects list
151 |   var template = $('#repoPanels').html();
152 |   var repoPanels = Mustache.render(template, {
153 |     repos: response
154 |   });
155 |   $("h2.code").after(repoPanels);
156 | }
157 | </script>
158 | </body>
159 | 
160 | </html>
161 | 


--------------------------------------------------------------------------------
/_posts/blog/2014-09-05-LocalFreeWeb.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: LocalFreeWeb
 5 | categories: blog
 6 | author: joseph_tanigawa
 7 | lead: Bringing the Web to those who can’t find it
 8 | ---
 9 | 
10 | 
11 | 
12 | If you couldn’t access the internet right now, how would you figure out where to go to get online? Maybe you would go to the library, but what if it’s closed? What if there's a long wait? Where would you go then?
13 | 
14 | Many organizations and institutions offer access to free, internet-enabled computers, but there is no way for someone to find these locations without being online already. In short, you need the internet to find the internet.
15 | 
16 | On August 15, Code for San Francisco, a Code for America brigade, launched <a href="http://LocalFreeWeb.org">LocalFreeWeb</a> to bring access to free, internet-enabled computers (not just Wi-Fi) to anyone who can send a text message. This effort to bring the benefits of the Web to low-income, mono-lingual, and other disadvantaged people is designed not only to give access to the Web, but also to generate interest among folks who might not know why they would use the internet in the first place. 
17 | 
18 | 
19 | 
20 | LocalFreeWeb was born out of a PARISOMA hackathon challenge to “help City organizations and corporations get involved the Sharing Economy”. Hackathon teammates Jesse Biroscak, Rachel Stanley, and others concluded that the most valuable thing organizations and corporations could do would be to bring access to the internet to all City residents - sharing their access to the knowledge on the web. They interviewed people in a rough part of the mid-Market / SOMA neighborhood to come up with the reasons why someone who does not use the internet might ever come online. The team tested the viability of the service by posting flyers in English and Spanish at nearbybus stops, presenting the benefits of the web (results of the user research), and proposing that people text a cell phone number (Jesse’s) for more information. The enthusiastic response confirmed the demand and the hackathon team soon brought the project to the Code for San Francisco brigade team to build a first version.
21 | 
22 | ### How it works (summary)
23 | Every bus stop in San Francisco has a bus stop identification number. When someone at a bus stop sends a text message to a specific phone number (as prompted by a flyer on the bus stop), including the bus stop identification number, they will receive a text message response with the locations of the 3 closest free, internet-enabled computers, as well as the current day's hours of avaliablilty of those locations. The message response also prompts them to ask for “Free Internet” when they arrive at the location. Locations are not only sourced from an established database of community centers and libraries, but also from the crowd - anyone can add their knowledge of a free, internet-enabled computer. 
24 | ![Photo of LocalFreeWeb text message](/images/blog/LocalFreeWebText.jpg)
25 | 
26 | ### How it works (technical details)
27 | 
28 | LocalFreeWeb was built with CartoDB and Twilio. CartoDB stores a database of the locations providing free internet, along with all the relevant data about the location, such as address, phone number, hours, and geolocation (coordinates), as well as another database of all the bus stops in SF with their Stop ID and corresponding geolocation. Twilio handles the sending and receiving of text messages. 
29 | 
30 | To make these technologies work together, we created an app with Flask (a Python framework for web applications). When Twilio receives a text message from a user, the Flask app parses out the Stop ID from the message body and requests the geolocation of the Stop ID from CartoDB. With the received geolocation, the app makes another request to CartoDB asking for the three closest locations of free, internet-enabled computers to the bus stop's geolocation. Then it formats the metadata for the three closest locations into a readable text message and sends it back to the user.
31 | 
32 | We use the Google Spreadsheet API to record the date, time, and Stop ID of each valid request made to the app.
33 | 
34 | If you’re curious, here’s the <a href="https://github.com/sfbrigade/localfreeweb-sms-api">application backend code</a> and <a href="https://github.com/sfbrigade/localfreeweb.org/tree/gh-pages">frontend website code</a>.
35 | 
36 | ### Technical Challenges
37 | 
38 | We discovered that the bus stop data (Stop ID) provided by the SFMTA was not stored in the database provided to the public. Not only is the database updated every three months, but Stop IDs are truncated by removing the leading digit for reasons unclear. For example, if the Stop ID at a bus stop is 13003, in SFMTA's database it will be stored as 3003. We realized this problem when we started testing the service - most of the stops weren’t in the database! Thankfully, we figured this out and made the necessary changes to the data.
39 | 
40 | ## Next steps!
41 | 
42 | Now that we’ve built and tested this first version, we will be spreading the word to relevant City organizations and building relationships with Clear Channel Media, the company controlling the advertising space on bus shelters. Recently Allen and Joseph, Storytellers from the Brigade, enthusiastically set off with a stack of flyers and a roll of tape. They found willing recipients at the SF Library Main Branch, which will be distributing flyers to all of the City’s libraries. They also met with public housing offices and community centers to distribute the flyers to low income citizens. We currently have fliers avaliable in English, Spanish & Mandarin. We hope to soon have our fliers translated into Tagalog as well.
43 | 
44 | ### Plans include:
45 | - Distributing more flyers
46 | - Printing stickers
47 | - Creating partnerships with digital literacy organizations
48 | - Finalizing a partnership with Clear Channel Media
49 | - More outreach to relevant community organizations
50 | - Converting the text messaging app into at least Spanish, Mandarin & Tagalog
51 | - Partnering with MTA to have signs permanently placed at Wave Shelters explaining how to use our service 
52 | - Acquiring funding for a shortcode ie; 311 for finding 'Free Internet' locations
53 | 
54 | 
55 | ### How you can help
56 | 
57 | 1. Go to <a href="http://LocalFreeWeb.org">LocalFreeWeb.org</a> and let us know how/if it works!
58 | 2. Use the form on the website to add more locations
59 | 3. Print out <a href="https://drive.google.com/file/d/0B3Rg0E6TFEMCZGRGS1BtbzZxWjg/edit?usp=sharing">fliers</a> and post them near bus stops in your neighborhood
60 | 4. Check out the code and make suggestions
61 | 5. Use the open source code to build a version for your city (and tell us about it!)
62 | 
63 | If you’re in San Francisco and interested in helping build LocalFreeWeb, we’d love to see you at <a href="http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/">Code for San Francisco civic hack nights</a>. 
64 | 
65 | ### We need people with all types of skills:
66 | - Writing
67 | - Marketing
68 | - Business Development
69 | - Research
70 | - Code (Python, JavaScript, HTML, CSS)
71 | - User Experience and User Interface Designers
72 | 


--------------------------------------------------------------------------------
/_posts/blog/2014-10-22-how-our-campaign-data-visualization-app-can-help-you-this-election.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: How our Campaign Data Visualization App Can Help YOU This Election
 5 | categories: blog
 6 | author: jay_rooney
 7 | tags: 
 8 |   - Data Visualization
 9 | ---
10 | 
11 | On November 4th, San Franciscans head to the polls to vote for, amongst other things, a tax on carbonated beverages (aka “Soda”). Did you know that pro-soda tax individuals and committees have raised $224,971 to pass the ordinance, while the soda industry has raised $7,700,000 to defeat it?
12 | 
13 | To visualize that: [VISUALIZATION IMAGE]
14 | 
15 | We got that data in a matter of seconds from the San Francisco Brigade’s Campaign Data Visualization App. You can, too.
16 | 
17 | Let’s face it - whether you’re a journalist covering the election, or just a voter trying to make an informed choice, the best thing to do is “follow the money.” However, San Francisco’s campaign finance data is, to put it simply, a hot mess. If you want to decipher the data, you need to either have:
18 | a lot of expertise
19 | a lot of time
20 | Neither of which most voters - and even journalists - have, unless they’re able to devote unfathomable amounts of hours towards poring over datasets. If you’re a journalist on a deadline, or a voter trying to go about your life, this just isn’t feasible.
21 | 
22 | Which is where the Data Visualization App comes in. See what’s really going on behind the scenes, who’s giving how much money to whom, and help shine a much-needed light on the often murky and labyrinthine world of campaign finance.
23 | 
24 | At the very least, make an informed decision before you cast your ballot!
25 | 
26 | Some other interesting findings:
27 | 
28 | [Coming Soon]
29 | 
30 | Find out all this, and more, before the election with the San Francisco Brigade’s Campaign Data Visualization App. Access it here: http://election-sf.herokuapp.com/


--------------------------------------------------------------------------------
/_posts/blog/2014-10-22-speaker-mattarana-on-accessibility.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: "Speaker: Matt Arana on Accessibility"
 5 | categories: blog
 6 | author: laura_paajanen
 7 | excerpt: "The SF Brigade was fortunate to get an introduction to accessibility from Matt Arana from SSB BART Group, which has been helping organizations be more accessible since 1997. Matt’s introduction to accessibility came when he was working for a tobacco company. He had an opportunity to work for SSB BART instead, but wasn’t sure if it was a good career move. Since family and faith are important to Matt, he discussed it with his aunt before they went to services."
 8 | tags: 
 9 |   - Accessibility
10 |   - Speaker
11 | ---
12 | 
13 | The SF Brigade was fortunate to get an introduction to accessibility from [Matt Arana](https://www.ssbbartgroup.com/blog/2011/10/15/employee-spotlight-matt-arana/) from [SSB BART Group](https://www.ssbbartgroup.com/), which has been helping organizations be more accessible since 1997. Matt’s introduction to accessibility came when he was working for a tobacco company. He had an opportunity to work for SSB BART instead, but wasn’t sure if it was a good career move. Since family and faith are important to Matt, he discussed it with his aunt before they went to services. The sermon they attended was about Bartimaeus, who was blind and given sight by Jesus. It became clear to Matt that working in accessibility was his opportunity to contribute something positive to the world.
14 | 
15 | Matt explained that accessibility (sometimes abbreviated as A11y) is very broad: it’s not just considering mobile, but making everything digital accessible for people with vision, cognitive, and mobility-related limitations. That means websites, web applications, PDF, video, chat, email notifications, mobile, ebooks – “anything with a 1 and a 0.” Accessibility means making sure your audience can do what they need to do on a web site. It is also the law. Section 508 states that government procured electronic and information technologies must meet certain standards.
16 | 
17 | ![Matt Arana](/images/blog/MattArana.jpg)
18 | _Matt Arana visits the SF Brigade to introduce accessibility issues and tools._
19 | 
20 | Accessibility is important because 19% of the population has some kind of disability – that’s 57 million Americans. Disabilities can be visual impairments like low vision or blindness, auditory impairments such as deafness or hearing loss, speech impairments, mobility issues, cognitive or learning disabilities, and age-related limitations.
21 | 
22 | There are many kinds of assistive technologies: screen readers, refreshable braille displays, screen magnifiers, onscreen of other special keyboards, TDD/TYY and video relay devices, text-to-speech software, and word prediction software. Many organizations don’t know how to build their websites and apps to accessibility standards, or have the resources to do so. Matt shared the top ten things that he sees affect the accessibility of sites and apps.
23 | 
24 | Top Ten Things that affect sites and applications
25 | * Missing or incorrect names
26 | * Navigation doesn’t follow visual design
27 | * Skipping over visible items or speaking invisible items
28 | * Not grouping visually related elements
29 | * Element type (link, button, etc.) is missing or incorrect
30 | * The state of buttons is not described
31 | * Headings are missing or used inconsistently
32 | * Missing “hints” that provide context
33 | * Missing closed captions or caption controls
34 | * Low contrast
35 | 
36 | ![TopTen](/images/blog/TopTenA11yIssues.jpg)
37 | _Matt’s list of ten common issues that affect accessibility on websites and applications_
38 | 
39 | We looked at some pages using a popular screen reader, [JAWS](http://www.freedomscientific.com/Products/Blindness/Jaws) - and saw firsthand why it’s helpful to have an option to skip to the main content rather than reading through every link at the top of a page. JAWS also highlights what is being read on the screen with a box outline, so help people with reduced vision find their spot. JAWS can be expensive, but Apple products often come with accessibility features built in, which is making more devices usable for more people. It’s a big deal to have good access on mobile devices.
40 | 
41 | There are still many challenges with coding for accessibility - for example, some CMS systems get in the way of modifications for accessibility, and it’s hard to get security and privacy right with screen readers. However, there are standards for web accessibility: the [Web Content Accessibility Guidelines (WCAG)](http://www.w3.org/WAI/intro/wcag) published by the [World Wide Web Consortium (W3C)](http://www.w3.org/) is the basis for most web accessiblity standards. The WCAG outlines three levels of conformance:
42 | A - must do items to be accessible, such as alt text, form fields, and keyboard access
43 | AA - general requirement/ strongly recommended - for example, providing focus
44 | AAA - nice to haves that aren’t as common, such as more restrictive color contrast rules
45 | 
46 | SSB BART looks at both standards like the WCAG and functional requirements. They have users with disabilities test sites to see if they can do what they’re trying to - that’s at least as important as following standards.
47 | 
48 | Thanks, for the intro to A11y, Matt!


--------------------------------------------------------------------------------
/_posts/blog/2015-01-07-sf-brigade-hosts-citycampsf.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: SF Brigade Hosts CityCampSF
 5 | categories: blog
 6 | author: lawrence_grodeska
 7 | lead: "Join us this Saturday, January 10"
 8 | excerpt: "What happens when you gather local officials, city staff, entrepreneurs, designers, developers, journalists and citizens in a room for one day, and ask for their best ideas to improve their communities? You get CityCamp - a lot of excitement, a little chaos, plenty of solutions, and a whole lot of action."
 9 | ---
10 | 
11 | **[Register now!](https://www.eventbrite.com/e/citycampsf-2015-tickets-13722252627)**
12 | 
13 | What happens when you gather local officials, city staff, entrepreneurs, designers, developers, journalists and citizens in a room for one day, and ask for their best ideas to improve their communities? You get CityCamp - a lot of excitement, a little chaos, plenty of solutions, and a whole lot of action.
14 | 
15 | [CityCamp](http://citycamp.com/sf/) is a national movement that brings people together to build stronger communities where they live. Core to the CityCamp model is the belief that local governments and community organizations have the most direct influence to make cities more open and “user friendly.” CityCamp provides a space for that to happen through locally organized “unconferences.” At an unconference, the agenda is created by attendees and reflects the interests and expertise of those in the room.
16 | 
17 | The first CityCamp was held in Chicago in January 2010, inspired by other unconferences like Transparency Camp and Gov 2.0 Camp. Each CityCamp has four main goals:
18 | 
19 | 1. Bring together local government officials, municipal employees, experts, programmers, designers, citizens and journalists to share perspectives and insights about the cities where they live
20 | 2. Create or maintain patterns for local government transparency and effective local governance using the Web as a platform
21 | 3. Foster communities of practice and advocacy on the role of information and open data in cities
22 | 4. Create outcomes that participants will act upon after the event is over
23 | 
24 | To celebrate 5 years of community building for better cities, CityCamp is being re-booted and re-energized in 2015. **On January 10th, four cities – Chattanooga, Oakland, Sacramento and San Francisco** – will host concurrent CityCamps in city halls, public libraries, and local civic hacking organizations.
25 | 
26 | CivicMakers is honored to produce CityCampSF 2015 as part of our mission to co-create a living democracy on planet earth. We’ll be at Code for America HQ, a beautiful office space in the SoMA neighborhod of San Francisco. close to Civic Center BART. A host of local officials will start the day by answering questions about the “State of SF.”
27 | 
28 | Confirmed speakers include:
29 | 
30 | - Supervisor Mark Farrell, City and County of San Francisco
31 | - Jay Nath, Chief Innovation Officer, SF Mayor’s Office of Civic Innovation
32 | - Joy Bonaguro, Chief Data Office, SF Mayor’s Office
33 | - Francis Zamora & Kristin Hogan, SF Dept. of Emergency Management
34 | - Dan Parham, Founder, Neighborland
35 | - Joaquín Torres, Deputy Director, OEWD
36 | 
37 | And, of course, the bulk of the day will be reserved for an unconference organized by attendees, along with plenty of food and drink for breakfast, lunch, snacks and a CityCampSF closing party.
38 | 
39 | If you’re in the Bay Area, I hope you can join us at CityCampSF on Saturday, January 10th, for a day of community engagement and action for a better San Francisco! Or attend one of the other 2015 CityCamps in Chattanooga, Oakland or Sacramento to join the conversation on building communities for better cities.
40 | 
41 | A very special thank you to our gracious sponsor Microsoft for supporting CityCampSF. Check out how Microsoft is supporting the civic tech sector in the Bay Area at http://www.microsoftbayarea.com/.
42 | civictech democracy san francisco citycamp


--------------------------------------------------------------------------------
/_posts/blog/2015-01-18-code-for-san-francisco-gets-sponsored.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: "Code for San Francisco gets sponsored!"
 5 | categories: blog
 6 | author: jesse_biroscak
 7 | tags: 
 8 |   - Sponsorship
 9 |   - Microsoft
10 |   - State of the Brigade
11 | ---
12 | 
13 | I joined Code for San Francisco in October of 2013 and immediately found myself surrounded by a group of people dedicated to improving the lives of fellow City residents. At the time we didn't have money or tangible resources, but we did have passion and a deep motivation to change our city.
14 | 
15 | Our enthusiasm was contagious and it spurred buzz within the community, which, along with a dedicated core team and a series of successful events, brought even more passionate and motivated people to our cause ... and the attention from potential sponsors.
16 | 
17 | As Captain of Code for San Francisco, it is my pleasure to announce [Microsoft](http://www.microsoftbayarea.com/) as the Brigade's first sponsor.
18 | 
19 | I want to say off the bat that Microsoft (represented by [Scott Mauvais](http://www.microsoftbayarea.com/author/scottmauvais/) and [Kenny Spade](http://www.microsoftbayarea.com/author/kspade/)) has consistently shown up for hack nights and not only contributed resources, but also innovative ideas and code to our efforts. While we welcome this type of enthusiastic participation from everyone interested in our work, not just sponsors, it is especially rewarding to have a sponsor take such an active interest in the local civic hacking community.
20 | 
21 | We recently hosted the Director and CTO of Microsoft's [Disaster Response Team](http://www.microsoft.com/about/corporatecitizenship/en-us/serving-communities/disaster-and-humanitarian-response/) [Tony Surma](https://twitter.com/tonysurma) for a discussion about how to make our apps consume less battery power and data - great for any situation, not just disasters.  [On February 4th](http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/events/219643560/), we will host the authors of [The Responsive City](http://datasmart.ash.harvard.edu/responsivecity) (Stephen Goldsmith and Susan Crawford) for a Q&A discussion on their book (check one out from the CfSF library), thanks to the introduction and coordination from Microsoft. 
22 | 
23 | 2015 is going to be an exciting year for us - we will be able to host larger events and offer more resources our participants as a result of the Microsoft sponsorship. Our community has already benefitted greatly from these contributions and we look forward to a continued and productive relationship with Microsoft in 2015.


--------------------------------------------------------------------------------
/_posts/blog/2015-03-25-recap-q1-demo-night-by-julia-gitis.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: false
 4 | title: "Recap: Q1 Demo Night! By Julia Gitis"
 5 | author: jason_lally
 6 | ---
 7 | 
 8 | ## 
 9 | On Wed Mar 18, we hosted our first demo night at the brigade! It was awesome to see what kind of projects our members are working on.
10 | 
11 | Trent Robbins presented GetSocrata. He is bilding an api wrapper to get data from Socrata ("the world leader in cloud solutions for open data and data-driven governments").
12 | 
13 | Yariv Rabinovitch presented the Bicycle Newbie Initiative. They are deploying a project for connecting experienced and newbie bicyclists during commutes. How great is that?
14 | 
15 | Sheffield Hale represented the Open Health Data Team, which is working on mapping ads for unhealthy products like tobacco and soda, like how many ads are within walking distance of schools.
16 | 
17 | Patrick Stern presented Parksafe. His team is looking to provide parking confidence for drivers in SF. They are building an app that informs users on rules surrounding potential ticketing situations.
18 | 
19 | Mike Hernandez presented SF in Progress. They are bringing more awareness and advocacy to citizens. For example, his team gives citizens a chance to show up at public hearings and get their voices heard.
20 | 
21 | Jeremy Lucas presented Project Blip- promoting online safety, security, and privacy.
22 | 
23 | Jason Lally represented SF Social Services Open Referral Database. They are mapping social services so that folks can more easily find them. Isn't that great?
24 | 
25 | Greg Arenius presented BallotAPI- make it really easy to find out what's on your ballot.
26 | 
27 | Peter Hall presented Campaign Finance Visualization- different ways to look at data around campaign finance. Their team uses data to check that people are following the law. 
28 | 
29 | Finally, Jason Lally went over the Code for San Francisco website (yes, the one you're looking at now). How can we create a website that meets the needs of the communities we serve?
30 | 
31 | Then on Wed Mar 25, 3 teams that didn't get a chance to present last week presented their work. Chris Jerdonek presented on SF Election Data. Scott presented on [World University and School](http://worlduniversityandschool.org/), which is free high quality online wiki education. David Biel presented [SFHomeless.net](http://sfhomeless.net), a valuable resource in wiki format.
32 | 
33 | Come to our hack nights to meet these teams, support their work, and learn more.


--------------------------------------------------------------------------------
/_posts/blog/2015-04-09-celebrating-ethan-lang.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: "Celebrating the Life of Our Friend, Ethan Lang"
 5 | author: laura_childs
 6 | ---
 7 | 
 8 | Two months ago, Code for San Francisco lost a friend. Ethan Lang was a passionate civic hacker who had moved to San Francisco in October to live with his brother. He quickly found his place in the Bay Area, joining the LocalFreeWeb initiative and starting a job at City Hall. Ethan passed away in the night of January 30, after a short illness.
 9 | 
10 | ![Photo of Ethan](/images/blog/EthanProfessional.jpg)
11 | 
12 | Ethan's life ended but he will forever live on in the memories of those who met him. Everything Ethan did came from love and compassion. He was a life coach to some, a role model to many, a son and brother to others, and most importantly, a friend to all.
13 | 
14 | Throughout his life, Ethan was involved in community activities, from participating in musicals and being captain of the swim team in high school, to guiding incoming freshmen as an orientation student advisor in college, to volunteering at Code for San Francisco every Wednesday night. 
15 | 
16 | A background in political science and public relations led Ethan halfway around the world to Istanbul, Turkey where he worked for a political consultancy company, APCO Worldwide. In San Francisco, Ethan found his passion for politics and innovation converge. He was immediately attracted to Code for America's San Francisco Brigade. His lack of coding knowledge did not stop him from pursuing opportunities in civic tech. With undying motivation to bridge the digital divide with LocalFreeWeb, Ethan organized weekend flyering parties around the city, motivating even his laziest friends to dedicate a couple of hours to a good cause.In January, he began a new job at California Public Utilities Commission. 
17 | 
18 | Ethan fell ill with a fever that lasted several days in late January. He was feeling much better after receiving antibiotics. On the night before he passed, he made dinner with his brother and they shared jokes and smiles. 
19 | 
20 | Ethan loved to bring people together through music. His friends, family and loved ones will never forget his footloose spirit and ability to always get them on a dance floor. In Turkey, he was known to dance at a traditional turkish bar with locals in a bar mitzvah-type circle. In 2011, while celebrating at the Boston Marathon, he never stopped jiving to the street music, despite warning from policemen. "Dancin' ain't illegal," he'd say. He inspired people around him to enjoy life to the fullest and not take anything too seriously. His dance moves could cure anyone during the saddest of times – and they still do.
21 | 
22 | [Video of Ethan's dancing](https://vimeo.com/120393051)
23 | 
24 | Ethan lived with intention. He sought to connect with every individual with whom he crossed paths. He explored the world with wide eyes and a full heart, soaking up new cultures and going on new adventures without rest. His warm affability made him friends in all corners of the world. From Turkey to Australia, by way of Boston, Minnetonka, and San Francisco, Ethan's contributions to the world are countless. His contagious laughter, enduring altruism and sweet dance moves will be sorely missed.
25 | 
26 | Please join us on [Saturday April 18 at Ocean Beach](https://www.facebook.com/events/930243943673109/) for a bonfire and potluck honoring Ethan's time with us. Whether you spoke to him once or knew him for years, he touched every single person he met. Let's all come together and honor his memory in true Ethan fashion -- with good food, big smiles, a bonfire, and lots of dancing. 
27 | 
28 | ![Photo of Ethan](/images/blog/EthanAbroad.jpg)


--------------------------------------------------------------------------------
/_posts/blog/2015-04-29-april-12-2015-campaign-finance-summit.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: "April 12, 2015: Campaign Finance Summit"
 5 | author: asha_john_allen
 6 | ---
 7 | 
 8 | Our Campaign Finance Summit featured a speaker series followed by a visual data exploration hackathon. Below we have outlined the motivating issues for Open Campaign Finance Data along with updates on resources that can further keep us informed. The issues are followed up by a summary and video of each speaker's contribution to the discussion.
 9 | 
10 | ## Is writing a check free speech?
11 | 
12 | Few topics raise as much concern as money in politics. We all want to believe that candidates will get elected based on their values and merit but there is an overwhelming sense that our democracy is for sale. Who is behind this money is often nearly impossible to uncover. How much money are we talking about? OpenSecrets.org reports nearly $700,000,00 was raised by super PACSin 2014.
13 | https://www.opensecrets.org/outsidespending/summ.php
14 | 
15 | #### Shouldn’t we know who is writing the checks for whom? The answer is far more complicated.
16 | 
17 | On Sunday April 12, 2015, the San Francisco Code for America Brigade brought together a range of people, organizations and news members to try and uncover who is paying for whom in politics. Campaign finances have been one of the Brigade’s key projects for the last six months and the Brigade took it to the next level. Asha John’s team has been working on Campaign Data Visualization since last summer. The team released an App for the November 2014 elections visualizing the money raised and spent on San Francisco District Supervisor elections and Ballot Measures elections.
18 | 
19 | Participants were given a crash course on how legal decisions have created the current system of campaign finance, the challenges in accessing campaign finance data, and some of the work being done to make campaign finances more transparent. The event was sponsored by SAP.
20 | 
21 | 
22 | ## Super PACS
23 | 
24 | The first presentation was by Jesse Mainardi, Deputy Executive Director, SF Ethics Commission. Jesse lead us through a brief history of campaign finances and the legal decisions that given rise to SuperPACS:
25 | http://en.wikipedia.org/wiki/Buckley_v._Valeo
26 | http://en.wikipedia.org/wiki/Citizens_United_v._FEC
27 | 
28 | [**Video of Jesse's talk**](https://www.youtube.com/watch?v=Y6Sg24MQ-aE)
29 | [**Jesse's Slides**](https://docs.google.com/presentation/d/1Q4jqA4XrRBPIaw_lCW3lBJJy7MRLp93OVSChNoa1vPc/edit?usp=sharing)
30 | 
31 | 
32 | ## Dark Money. It’s as creepy as it sounds.
33 | 
34 | Jay Costa, Executive Director, Counter PAC, walked us through how wealthy individuals and corporations use non-profit 501(c)(4)s to hide their vast contributions. Due to laws which allow donations to remain anonymous to these non-profits, funds are shuffled around in a kind of shell game effectively hiding who is financing political advertising.
35 | 
36 | [**Video of Jay's talk**](https://www.youtube.com/watch?v=I5SXO4ZMakE)
37 | 
38 | 
39 | ## Phil
40 | Phillip Ung, Director of Public Affairs at California Forward, gave us a historical overview of how Cal-Access was created after the Online Disclosure Act of 1996. Originally created as a publisher and repository for endless government campaign finance forms, Cal-Access is a roadblock in the age of open data. The data is also only available for state races, local jurisdiction data is mostly only available in local government offices.
41 | 
42 | [**Video of Phillip's talk**](https://www.youtube.com/watch?v=1Z7GFfDOg1E)
43 | 
44 | ## Oliver
45 | Oliver Luby, District 1 Policy Manager, City of Oakland, opened with a 2010 FPPC paper Big Money Talks: “Just 15 wealthy special interests have spent more than $1 billion in the past 10 years to influence California voters and public officials.” This spending is done through independent expenditures, and Oliver has a keen sense of the weak spots in independent expenditure reports and disclosures. Luby pointed to the campaign data loop-hole of data being filled out only in paper forms.
46 | 
47 | [**Video of Oliver's talk**](https://www.youtube.com/watch?v=ue_JO5rES0c)
48 | 
49 | ## Journalist Panel
50 | As to be expected, the press panel had a lively discussion. In attendance were: Aaron Williams, News Applications Developer, Center for Investigative Reporting; Michael Stoll, Editor, San Francisco Public Press; John Osborn, Digital Communication Manager, EdSource.
51 | Michael pointed to the importance of journalists having access to campaign data tools to tell the story behind the data. “A story isn’t worth doing unless you bring new information to it.” The data is the starting point to set the public policy debate. Technology can be an expensive challenge for a non profit news organization and the journalist discussed partnerships with each other and technologists as one way of bringing information to the public. CIR and LA Times created the California Data Coalition to pool resources on data and compete on stories. The SF Public Press is collaborating with the Internet Archive. John Osborn reminded us to “Thank the city clerk who gives you access to data.” They are the unsung heros in the depths of city hall.
52 | 
53 | [**Video of Journalist Panel**](https://www.youtube.com/watch?v=9fz1WD-BvaY)
54 | 
55 | ## Miriam
56 | Miriam Marks, Data Director at MapLight. “The challenges with using state data are the challenges of using Cal-Access.” Miriam illustrated how MapLight has found its way through the labyrinth that Cal-Access places between users and campaign finance data. Despite this, MapLight is able to build comprehensive, data-rich stories which track the influence of money in politics.
57 | 
58 | [**Video of Miriam's talk**](https://www.youtube.com/watch?v=yz7oJWLbzUY)
59 | [**Miriam's Slides**](https://docs.google.com/presentation/d/1n3MTLB2FJKCPfeHauY0Gsl5r9AonMMoVHPB_Ggotjl4/edit?usp=sharing)
60 | 
61 | The challenge to our democracy by the influence of seemingly unlimited amounts of campaign contributions through super PACS is being met with alarm and increasing scrutiny. The California Campaign Finance Summit demonstrated how a partnership with technologists, designers, concerned citizens and journalists can shine some light into the dark recesses of campaign finances.
62 | 
63 | 


--------------------------------------------------------------------------------
/_posts/blog/2015-06-01-SF-Bay-Area-Happiness-Survey.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | published: true
 4 | title: "Text if you’re happy or not says tech volunteer group"
 5 | author: seunghee_eu_julio_feliciano
 6 | 
 7 | ---
 8 | FOR IMMEDIATE RELEASE
 9 | 
10 | ##TEXT IF YOU’RE HAPPY OR NOT SAYS TECH VOLUNTEER GROUP
11 | Civic Hackers Help Communities by Developing Technology for Good
12 | 
13 | San Francisco, June 1, 2015 - Code for San Francisco volunteer hackers today launch the Happiness Survey to better understand the Bay Area state of mind. Any resident can take the two-minute survey now through June 3 to add their voice to National Day of Civic Hacking, a weekend dedicated to social and civic change using technology.
14 | 
15 | The survey is at codeforSanFrancisco.org/happiness or by texting “happiness” to (650)249-9400. Results will be made available on June 9, 2015 at codeforSanFrancisco.org, and at Code for San Francisco’s weekly Hack Night presentation on June 10, 2015.
16 | 
17 | The third annual National Day of Civic Hacking, from June 5 to 7, 2015, will draw thousands of people from across the U.S. to build new solutions for communities and government. Passionate neighbors, urbanists, civic hackers, developers, designers, government staff, and community organizers will unite around building tools for their common cause. Last year, civic hackers developed an app to alert Boston commuters about transit delays, and an app to share information about adoptable pets in Palo Alto.
18 | 
19 | “How you feel about where you are right now is important. This single, small text message, grouped with many others has the potential to change the conversation around neighborhoods, housing, and transportation,” says Jesse Biroscak, Brigade Captain for Code for San Francisco, “Join your neighbors and tell us how you’re feeling!”
20 | 
21 | National Day of Civic Hacking is organized by Code for America with coordination from NASA and SecondMuse, and additional support from the White House Office of Science and Technology Policy and other Federal, state, and local agencies.
22 | 
23 | Anyone with ideas can participate in local events, which include hackathons, unconferences, meetups, block parties and more throughout the weekend, and sometimes beyond. More information is at CodeForSanFrancisco.org/hackforchange/
24 | 


--------------------------------------------------------------------------------
/_posts/blog/2016-04-09-created-meet-sf-brigade-members.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | tags: 
 4 |   - members
 5 | author: vedrana_trbusic
 6 | published: true
 7 | title: Meet SF Brigade Members
 8 | ---
 9 | 
10 | 
11 | ## Meet April Steed, a passionate UX designer and Lighten Project Lead
12 | 
13 | We’re kicking off our #MeetSFBrigadeMembers series with April Steed – a UX designer, passionate civic hacker, and Project Lead for Lighten. Read on to find out how she got involved with Code for SF, what drives her and how Lighten is making access to social services more user friendly! 
14 | 
15 | **Tell me a little bit about yourself, what is your professional background and your interests?**
16 | 
17 | My professional background is in UX design, I've been working as a freelancer for the last year and a half. I started out in illustration and graphic design, and gradually ended up on the UX path. I still love illustration, I'll be starting a new body of work over the course of this year.
18 |  
19 | **What are you passionate about?**
20 | 
21 | I'm passionate about making people's lives better, especially those who have historically been underserved, ignored, and oppressed. It's why I became a UX designer. I believe the key to sustainable positive change lies in ethical design. In the words of Gloria Steinem, I'm determined to leave this world a better place than when I found it.
22 | 
23 | <img alt="April Steed head shot" src="{{site.baseurl}}/images/headshot%202.15.16.jpg" width="250" height="250" />
24 | 
25 | **How did you get involved with Code for San Francisco and how long have you been a part of the SF Brigade?**
26 | 
27 | I literally just showed up one night about two years ago and never left! I had just finished a UX bootcamp and was eager to find something to work on. I never thought I would end up leading a project.
28 |  
29 | **What do you like best about being a member?**
30 | 
31 | I like how passionate and supportive people are at CfA, it feels like a community. I get to talk to people I never would have otherwise met, and I love seeing what other people are doing in the civic space.
32 |  
33 | **Tell me about Lighten, what is the project hoping to achieve?**
34 | 
35 | The goal of Lighten (previously Open Referral) is to improve social services delivery by making information about those services easy to access, and by making sure that information is accurate and useful. We believe the way to make this happen is by developing a universal open source set of standards so this information can be automatically exchanged between agencies whenever a change is made.
36 |  
37 | **How long have you been working on this project? How many people are in the team?**
38 | 
39 | I've been working on this project for two years now. I came on as a UX researcher, and gradually took on more and more of an active role until I was leading the project, which I've been doing for about a year and a half. There's about 8 people on the team, although it varies depending on the tasks at hand. It sounds like a long time, but because we are attempting systemic long-term change in uncharted territory, we've still got a long way to go.
40 |  
41 | **What is the next big thing for this project?**
42 | 
43 | Funding!  Once we get a functional prototype off the ground we will be looking for financial support to turn it into a real product.
44 |  
45 | **What might (someone) be surprised to know about you?**
46 | 
47 | I'm a total comics geek! Despite it's problematic recent history I've been a fan of comics for a long time. The industry is having a bit of a renaissance right now. There are tons of great new stories coming out that star women and people of color, written by women and people of color, that are anything but your typical superhero storyline.
48 |  
49 | **What do you do when you aren’t volunteering?**
50 | 
51 | Getting out into nature as much as I can by camping, hiking, or kayaking. Working on my own personal creative projects or my illustration work, or relaxing with a stack of comic books!
52 | 
53 | 


--------------------------------------------------------------------------------
/_posts/blog/2016-04-26-sf-brigade-s-data-science-working-group.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | tags: 
 4 |   - Data Science
 5 | author: kasia_rachuta
 6 | published: true
 7 | title: "SF Brigade's Data Science Working Group"
 8 | ---
 9 | # SF Brigade's Data Science Working Group
10 | 
11 | The past couple of months have been an exciting time for the Data Science
12 | Group Working Group (DWSG). The group, which started in January, brings together
13 | both professional data scientists and data enthusiasts hoping to improve their skills
14 | whilst making an impact. DSWG uses the wealth of open source data made available
15 | by SF Open Data and others to work on both its own projects as well as to support
16 | other civic hackers at Code for San Francisco. By providing data science expertise
17 | they’ve become a central resource to the broader SF Brigade.
18 | 
19 | ![data science working group hard at work]({{site.baseurl}}/images/uploads/IMG_1846.jpg)
20 | 
21 | One project that the DSWG is currently working on is SF Open Data’s 311 case
22 | dataset to understand what agencies tend to respond first, which neighborhoods
23 | are served first and what their most common problems are. Another example is
24 | ImpactGov, a project aiming to measure the impact of government- funded
25 | activities in the Bay Area. The goal of the SF Environment Benchmark project is
26 | to visualize building energy consumption and greenhouse gas emissions in order
27 | to encourage building owners and managers to make changes.  Sounds interesting?
28 | If you want to join our projects, have a problem that big data can help you
29 | solve, or want to use or develop your data skills and make a difference, come
30 | see us! We meet every Wednesday during Civic Hack Night.
31 | 
32 | Stay tuned to learn more about our findings!
33 | 


--------------------------------------------------------------------------------
/_posts/blog/2016-08-15-vr-data-visualization-a-new-way-to-address-community-issues.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: blog
 3 | author: allen_meyer
 4 | published: true
 5 | title: 'VR Data Visualization: A New Way to Address Community Issues'
 6 | tags: ''
 7 | ---
 8 | 
 9 | A San Francisco Brigade team has been partnering with SFHIP for almost a year now on a data visualization project that looks at alcohol licenses in San Francisco, specifically those establishments that sell alcohol to be sold off premise. Before any mapping or visualization could happened, SFHIP reached out to community advocates to find out first hand how the easy access to alcohol was impacting their communities. SFHIP lead community focus discussions in three SF neighborhoods, Bayview, Tenderloin and the Mission. SF Brigade members participated in these community listening sessions and helped SFHIP distill the findings using user centered design principles.
10 | 
11 | Brigade member David Rust-Smith created the following map which shows the density of establishments selling alcohol to be consumed offsite in the Mission, Bay, and Tenderloin neighborhoods: http://davidrs.github.io/sfhip-map/. 
12 | 
13 | While the community research took several months, the map was completed in just a couple of hack nights thanks to a tightly scoped set of features, a simple design, and awesome open source tools. The [dataset](https://github.com/davidrs/sfhip-map/blob/master/data/abc_map_2016.csv) is very small: ten columns and two hundred rows, so a backend database or API was unnecessary. All the data could just be loaded as a [csv file](https://github.com/davidrs/sfhip-map/blob/master/data/abc_map_2016.csv) and parsed with [D3.js](https://github.com/d3/d3/wiki/CSV). Not having a database meant fancy hosting wasn’t necessary—free and scalable hosting with GitHub pages made things nice and simple. It also meant all code could be written by one frontend developer in JavaScript. For the map [Leaflet.js](http://leafletjs.com/), the go-to open source mapping library, was used. Leaflet has lots of great examples out there, which made writing the [choropleth](http://leafletjs.com/examples/choropleth.html) (fancy map term for coloured areas) just a couple of minutes of work.
14 | 
15 | David then teamed up with Nick Breen and decided to take the data and see how it would look in VR. The difference from a 2-d map and VR visualization is dramatic as one watches a city within the city rise up to sell alcohol. One can see how concentrated the establishments are in the Bayview, Tenderloin and Mission neighborhoods: [Click here to watch the video](https://www.youtube.com/embed/videoseries?list=PLXYeZ3VwLuLsYzMd9unp7_Ig_GJsjh3J8). 
16 | 
17 | 
18 | These clips are YouTube’s 360 videos, so only a smartphone is needed to experience them, making it accessible to many more people than full VR kits. If you would like to learn more about the process behind how the map was made, or turn your own CSV into a 360 video, then checkout the [GitHub repo](https://github.com/davidrs/vr-dataviz).
19 | 
20 | Team Members: Steven Meloan, [Allen Meyer](http://allenmeyerdesign.com/), Peter Thompson, Seung-hee Eu, David Rust-Smith, Nick Breen
21 | 


--------------------------------------------------------------------------------
/_posts/blog/IMG_4949.JPG:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/_posts/blog/IMG_4949.JPG


--------------------------------------------------------------------------------
/_posts/blog/MattArana.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/_posts/blog/MattArana.jpg


--------------------------------------------------------------------------------
/_posts/blog/Screen Shot 2014-09-11 at 4.44.39 PM.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/_posts/blog/Screen Shot 2014-09-11 at 4.44.39 PM.png


--------------------------------------------------------------------------------
/_posts/blog/TopTenA11yIssues.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/_posts/blog/TopTenA11yIssues.jpg


--------------------------------------------------------------------------------
/_posts/blog/image00.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/_posts/blog/image00.jpg


--------------------------------------------------------------------------------
/_posts/blog/image01.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/_posts/blog/image01.jpg


--------------------------------------------------------------------------------
/_posts/images/TopTenA11yIssues.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/_posts/images/TopTenA11yIssues.jpg


--------------------------------------------------------------------------------
/_posts/jobs/2015-08-17-executive-team.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | layout: job
  3 | categories: jobs
  4 | ---
  5 | Apply to support the Executive Team as it works to support the rest of Code for
  6 | San Francisco’s Core Teams and help us grow into a more effective, impactful,
  7 | and inclusive organization. We are looking for an additional Captain, an
  8 | Executive Coordinator to support the Captains, and a PR Coordinator to build
  9 | our brand distribution network.
 10 | 
 11 | Read the descriptions for each position:
 12 | 
 13 | - [Co-Captain](#co-captain-description)
 14 | - [Executive Coordinator](#executive-coordinator-description)
 15 | - [PR Coordinator](#pr-coordinator-description)
 16 | 
 17 | ## Co-Captain Description
 18 | Along with our esteemed captain, Maddie Suda, your role will be to internalize
 19 | the vision for Code for San Francisco and maintain an overall understanding of
 20 | all of the brigade’s moving parts. We have purposefully created these new Core
 21 | Teams in service of better brigade outputs and to avoid siloed actions. During
 22 | October - January (at least), you will support all Core Teams, coordinate
 23 | communication as appropriate, and remove blockers as needed. When the brigade
 24 | stops moving forward, you must inspire and work with others to break that
 25 | stagnation.
 26 | 
 27 | Functionally, you will work with the Executive Coordinator to handle any and
 28 | all tasks that others cannot fulfil, no matter what they are, in order to
 29 | sustain and advance Code for San Francisco’s efforts. You will likely be the
 30 | first to arrive and the last to leave, you will direct people with questions to
 31 | the appropriate Core Team, and you will provide counsel and advice to folks who
 32 | simply need to connect with someone at Code for SF.
 33 | 
 34 | Other duties include:
 35 | 
 36 | - Build and maintain a respectful and productive relationship with municipal partner and local government.
 37 | - Be ultimately responsible for all activities involving Code for San Francisco
 38 | - Commit to making your Brigade look like the community the Brigade is in.
 39 | - Commit to upholding Code for America Code of Conduct and Brigade Code of Conduct / Values
 40 | 
 41 | ### Relevant Skills
 42 | - CEO, Executive Director, or Project, product, or program management background
 43 | - Understanding of a Holacracy
 44 | - Experience managing teams
 45 | - Experience running meetings, developing agendas, and giving presentations
 46 | - Quick, calm, and collected thinking
 47 | - Patience
 48 | - Coordination skills
 49 | 
 50 | ### Commitment
 51 | - There is a 1-year minimum commitment for this position
 52 | - If accepted, you must work to find a replacement should you leave or step down
 53 | - Attend semimonthly virtual Core Team coordination meeting
 54 | - Attend monthly meeting for Onboarding Team members (coordinated among your team)
 55 | - Attend hack nights and Brigade events that generate new members, such as hackathons
 56 | - Available for 20+ hours of communication per month outside of Hack Nights on Core Team and external coordinating efforts
 57 | 
 58 | ### Metrics
 59 | The Captain will track the following:
 60 | 
 61 | - Active members, teams, and partners growth rate
 62 | - Overall number and usage of launched projects
 63 | - Core Team member happiness
 64 | - Forecasted Brigade account balance
 65 | - Effectiveness of the website as a tool to service the brigade
 66 | - Other metrics to be determined
 67 | 
 68 | ## Executive Coordinator Description
 69 | Are you the most organized person you know? Are things in your home sorted
 70 | alphabetically or by color? Do you take pleasure in helping others to achieve
 71 | their goals? As Code for San Francisco’s Executive Coordinator, you will see
 72 | everything the Captains see... and more in order to:
 73 | 
 74 | - Help Captains to execute on action items
 75 | - Ensure record keeping and scheduling at meetings
 76 | - Ensure there is always a project owner, due date, and follow up… for everything
 77 | - Ensure every i is dotted and every t crossed
 78 | - Help Captains to keep track of the progress of Core Team reporting
 79 | - Coordinate among Core Teams as a supplement to the Captains’ efforts
 80 | 
 81 | Understand that your role is one of the most critical in the organization, even
 82 | if it may not always be recognized as such. The Executive Coordinator makes
 83 | things happen. During meetings, which you will help to keep on schedule, you
 84 | will guide the Core Team from ideas to concrete, assigned tasks with deadlines.
 85 | During Hack Night, you may that may mean facilitating a portion of the
 86 | evening's activities, protecting team members from distractions (especially our
 87 | busy Captains), working on the future of the Brigade, project management of
 88 | everything that's not hack night projects, or whatever else needs to be done.
 89 | 
 90 | ### Relevant Skills
 91 | - Experience as an Executive Assistant
 92 | - Selflessness and Patience
 93 | - Experience running meetings, developing agendas, and giving presentations
 94 | - Quick, calm, and collected thinking
 95 | - Coordination skills
 96 | 
 97 | ### Commitment
 98 | - There is a 3-month trial period for this position, with ideal candidates looking to stay for at least 6 months
 99 | - If accepted, you must work to find a replacement should you leave or step down
100 | - Attend semimonthly virtual Core Team coordination meeting
101 | - Available for 2-4 hours per week outside of Hack Nights
102 | 
103 | ### Metrics
104 | The Executive Coordinator will help the Captains to track and improve their metrics, which include:
105 | 
106 | - Active members, teams, and partners growth rate
107 | - Overall number and usage of launched projects
108 | - Core Team member happiness
109 | - Forecasted Brigade account balance
110 | - Effectiveness of the website as a tool to service the brigade
111 | - Other metrics to be determined
112 | 
113 | ## PR Coordinator Description
114 | Are you amazing at networking or have an already large network of media
115 | contacts? Do people constantly imply you have a flair for social media? Do you
116 | write in a clear, concise manner? As Code for San Francisco’s PR Coordinator,
117 | you will:
118 | 
119 | - Help project teams to come up with proper marketing strategies for launch
120 | - Help the brigade to take advantage of potential media-engagement opportunities
121 | - Develop and coordinate the PR / media strategy for the brigade with the Executive Team
122 | - Help the various teams to properly publicize their events
123 | - Coordinate Code for San Francisco’s social media presence
124 | 
125 | Public relations (PR) is about managing reputation. You will help Code for San
126 | Francisco realize the public-facing part of its vision by encouraging
127 | understanding and support for the organization externally, likely through
128 | publicizing of projects, opinions, and events.
129 | 
130 | Functionally, you will use all forms of media and communication to build,
131 | maintain and manage our reputation. You or the appropriate Core Team Lead will
132 | communicate key messages, often using third party endorsements, to defined
133 | target audiences in order to establish and maintain goodwill and understanding
134 | between Code for San Francisco and its public. You will monitor publicity and
135 | conduct research to find out the concerns and expectations of our stakeholders
136 | and report and explain the findings to leads of the Core Teams.
137 | 
138 | ### Relevant Skills
139 | - Experience in Public Relations
140 | - Knack for understanding media cycles
141 | - Fantastic understanding of long-term brand narratives
142 | - Quick, calm, and collected thinking
143 | - Understanding of how to tell the same story in multiple ways
144 | 
145 | ### Commitment
146 | - There is a 3-month trial period for this position, with ideal candidates looking to stay for at least 6 months
147 | - If accepted, you must work to find and train a replacement should you leave or step down
148 | - Attend virtual semimonthly Core Team coordination meeting
149 | - Attend hack nights and Brigade events that generate new members, such as hackathons
150 | - Available for 2-4 hours per week outside of Hack Nights
151 | 
152 | ### Metrics
153 | The PR Coordinator will track the following:
154 | 
155 | - Social media followers and engagement
156 | - Number of inbound community partners and potential sponsors approaching Code for SF
157 | - Number of public speaking opportunities for all Core Teams
158 | - Amount of mainstream media coverage
159 | - Effectiveness of the website as a tool to service the brigade
160 | - Other metrics to be determined
161 | 


--------------------------------------------------------------------------------
/_posts/jobs/2015-08-17-finance-team.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: job
 3 | categories: jobs
 4 | ---
 5 | Apply to help us manage our finances and help us grow into a more stable,
 6 | responsible, and transparent organization. We are looking for a lead to help us
 7 | understand and manage our financial needs, as well as folks to support the
 8 | lead or specialize in specific roles.
 9 | 
10 | ## The Pitch
11 | Do you take charge of dividing up the check at a restaurant? Are you constantly
12 | reviewing your favorite personal finance app? Are you great with sourcing
13 | funding for your pet projects? As the Finance Lead or part of a team of Lead
14 | Supporters, you will ensure that Code for San Francisco has enough money to
15 | support its needs and will work with Code for San Francisco members and
16 | partners to:
17 | - Lead all aspects of financial management at Code for San Francisco
18 | - Approve and coordinate reimbursements
19 | - Facilitate budget preparation and enforcement
20 | - Manage fundraising process and documentation
21 | - Coordinate grant writing assistance with partners
22 | 
23 | ## Finance Team Responsibilities
24 | - Coordination
25 | - Build out and coordinate the Finance Team
26 | - Collaborate with Captains, New Member, Project and Infrastructure Teams to build and get metrics for fundraising
27 | - Strategically plan budget for hack nights, events and partnerships along with the relevant teams
28 | - Communicate funding, budget, and recruiting efforts to the Brigade
29 | - Coordinate with Code for America team to get expenses pre-approved
30 | 
31 | ## Process
32 | - Define and improve process to manage filing of reimbursements
33 | - Open and Manage a Brigade Bank Account
34 | - Facilitate budget preparation and enforcement
35 | - Manage fundraising process and documentation
36 | - Coordinate grant writing assistance with partners
37 | - Help the Brigade stay aligned with Code for San Francisco’s goals and budget
38 | 
39 | ## Relevant Skills
40 | - Accounting skills
41 | - Project or program management background
42 | - Experience with creating budgets, managing finances, fundraising, etc.
43 | - Adaptability
44 | - Patience
45 | - Seriously amazing communication skills
46 | 
47 | ## Commitment
48 | - Attend semiweekly virtual Core Team coordination meeting
49 | - Attend monthly meeting for Finance Team members (coordinated among your team)
50 | - Attend weekly hack nights on Wednesdays
51 | - Available for 5-10 hours of communication per month outside of Hack Nights on member engagement
52 | 
53 | ## Metrics
54 | - The Finance Team will track the following:
55 | - Brigade Budget and Expenses
56 | - Bank Account
57 | - Fundraising
58 | - General Accounting and Bookkeeping
59 | - Other metrics as appropriate
60 | 


--------------------------------------------------------------------------------
/_posts/jobs/2015-08-17-hack-night-team.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: job
 3 | categories: jobs
 4 | ---
 5 | Apply to manage our weekly hack night - our core offering to the civic tech community. Your efforts will help Code for San Francisco grow into a more effective, impactful, and inclusive organization. We are looking for two leads to run Hack Night, as well as folks to support those leads or specialize in specific roles.
 6 | 
 7 | ##The Pitch
 8 | Are you a logistical mastermind? Can you organize a calendar of events better than the Mayor’s Scheduler? Can you get information from 7 different teams with time to spare before your deadline? As one of two Hack Night Leads or part of a team of Lead Supporters, you will manage our most important product - Hack Night, and will work with Code for San Francisco members and partners to:
 9 | 
10 | - Ensure Hack Night logistics are finalized well in advance of Hack Night
11 | - Balance the frequency of Hack Night events with sufficient Hack Night hacking
12 | - Communicate Code for San Francisco’s calendar of events to encourage regular attendance
13 | - Create a safe, inclusive, and participatory environment for members and partners
14 | - Help the Onboarding and Project Launch teams coordinate efforts to increase member retention
15 | 
16 | ##Hack Night Team Responsibilities
17 | - Build out and coordinate the Hack Night Team
18 | - Manage & delegate hack night tasks each week
19 | - Emceeing
20 | - Intro slide deck
21 | - Guest Speakers
22 | - Greet /Check-in members
23 | - Responsible for food- ordering, making sure there’s enough, food planning, coordinating with the Finance Team to manage the food budget. Opportunity to engage with local small businesses!
24 | - Organize hack night special events
25 | - Quarterly Demo night
26 | - Socials- approximately once per quarter
27 | 
28 | ##Coordinate with key folks internally
29 | - Onboarding team
30 | - Make sure someone is leading onboarding each night during hack night
31 | - Help coordinate sign-in/check-in process
32 | - Help connect newbies to projects
33 | - Project team- help newbies plug into existing projects and highlight any projects during hack night
34 | - Serve as a liaison between the onboarding team and the project team so that new people can plug into existing projects
35 | - Make sure the projects are being highlighted during hack night so that the community can understand how they can get involved and next steps.
36 | - Showcase project successes and challenges during hack night!
37 | - Manage guest speaker requests that come from external partners and brigade community
38 | - Create a process flow to manage pitches and speakers at hack night
39 | - Communicate hack night milestones for marketing, outreach, funding, and recruiting efforts
40 | - Relevant Skills:
41 |   - Program or event management background
42 |   - Experience revising a process or workflow
43 |   - Adaptability
44 |   - Patience
45 |   - Seriously amazing communication skills
46 | - Commitment:
47 |   - Attend weekly core team meetings (5:45-6:30pm) and hack nights 6:30-9pm
48 |   - Attend in-person monthly Core Team coordination meeting
49 |   - Available for 5-10 hours of communication per month outside of Hack Nights
50 | - Metrics (tracked by the Hack Night Team):
51 |   - Hack night attendance - new and returning
52 |   - Hack night speakers and events
53 |   - Active members and partners
54 |   - Other metrics as appropriate
55 | 


--------------------------------------------------------------------------------
/_posts/jobs/2015-08-17-new-member-support-team.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: job
 3 | categories: jobs
 4 | ---
 5 | 
 6 | Apply to support new members and partners as they join Code for San Francisco
 7 | and help us grow into a more effective, impactful, and inclusive organization.
 8 | We are looking for members to help support new member and partner onboarding,
 9 | as well as folks to support the lead or specialize in specific roles.
10 | 
11 | ## The Pitch
12 | 
13 | Do you greet people with a smile… every time? Do other people tell you how
14 | considerate you are? Can you form a personal connection with someone in
15 | 3 seconds or spend an hour helping someone to feel comfortable? Are you amazing
16 | at following up with people? As one of two New Member Support Leads or a team
17 | of Lead Supporters, you will be the front line for both new members and
18 | partners and will work with Code for San Francisco members and partners, both
19 | new and old, to:
20 | 
21 | - Help them understand what Code for San Francisco is and does
22 | - Introduce them to our self-starter, people-centered, organization
23 | - Help them build relationships with the right people or projects
24 | - Understand their reasons for coming and make their dreams come true
25 | - Instill a culture of people-centered design
26 | - Actively improve the member experience to minimize attrition.
27 | - Create a sense of commitment, pride and belonging
28 | 
29 | ## Team Responsibilities
30 | - Process
31 |     - Define and improve our onboarding process
32 |     - Review and develop methodology and tools for new member engagement
33 |     - Monitor members progress through the onboarding processes
34 |     - Develop method for an ongoing and effective feedback from member
35 | - Coordination
36 |     - Build out and coordinate the New Member Support Team
37 |     - Collaborate with Captains, Project Launch Team, and Website Team to assist in the engagement of members
38 |     - Communicate onboarding milestones and context for marketing, outreach, funding, and recruiting efforts
39 | - Support
40 |     - Help new members connect with project teams.
41 |     - Ensure new members are familiar with Code of Conduct and foster a feeling of belonging.
42 |     - Help new members understand the values and goals of Code for San Francisco and Code for America.
43 |     - Work with the Project Launch Team in support of the matching process to help volunteers and teams connect at each stage of their projects.
44 | 
45 | ## Relevant Skills
46 | - Strong relationship building skills
47 | - Adaptability
48 | - Patience
49 | - Seriously amazing communication skills
50 | 
51 | ## Commitment
52 | - Attend virtual semiweekly Core Team coordination meeting
53 | - Attend monthly meeting for Onboarding Team members (coordinated among your team)
54 | - Attend hack nights and Brigade events that generate new members, such as hackathons
55 | - Available for 5-10 hours of communication per month outside of Hack Nights on member engagement
56 | 
57 | ## Metrics
58 | 
59 | The Team will track the following:
60 | 
61 | - New members and partners
62 | - Active members and partners
63 | - Other metrics as appropriate
64 | 


--------------------------------------------------------------------------------
/_posts/jobs/2015-08-17-project-launch-team.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: job
 3 | categories: jobs
 4 | ---
 5 | Apply to support the launch of projects at Code for San Francisco and help us grow into a more effective, impactful, and inclusive organization. We are looking for two leads to help support project launches, as well as folks to support those leads or specialize in specific roles.
 6 | 
 7 | ##The Pitch
 8 | 
 9 | Do you love keeping things on track, removing obstacles to completion, and patiently helping people think through tough issues? Can you inspire someone to test their product (on a weekend) in the real world? As one of two Project Launch Leads or part of a team of Lead Supporters, you will have a centerpiece position in our growing organization and will work with Code for San Francisco projects, both new and old, to:
10 | 
11 | - Help them define their roadmap and launch date
12 | - Understand and address their talent and resource gaps
13 | - Remember that they should always focus on the people using their product
14 | - Personally connect to their end users
15 | 
16 | ##Project Launch Team Responsibilities:
17 | - Coordination
18 |     - Build out and coordinate the Project Launch Team
19 |     - Collaborate with Captains, Onboarding Team, and Website Team to assist in the incubation, growth, and launch of projects
20 |     - Strategically plan project launches, project needs, and overall life cycle/phase of projects, including project sunsets
21 |     - Communicate project milestones and context for marketing, outreach, funding, and recruiting efforts
22 | - Process
23 |     - Define and improve our program management process
24 |     - Help develop project development process, to help volunteers understand how to launch new projects and incubate new ones.
25 |     - Review and develop project methodology and tools
26 |     - Evaluate feasibility of new project ideas (i.e. timing, thematic fit into Code for San Francisco’s core project requirements, values, etc.) and encourage development as appropriate
27 | - Support
28 |     - Help project leaders move their products from idea to launch and from launch to growth.
29 |     - Help project leads stay aligned with Code for San Francisco’s goals
30 |     - Help projects recruit for each stage of their lifecycle
31 |     - Work with the Onboarding Team in support of the matching process to help volunteers and teams connect at each stage of their projects
32 |     - Engage and educate project leads on project methodologies and tools
33 | 
34 | ##Relevant Skills
35 | - Project, product, or program management background
36 | - Experience revising a process or workflow
37 | - Adaptability
38 | - Patience
39 | - Seriously amazing communication skills
40 | 
41 | ##Commitment
42 | - Attend in-person monthly Core Team coordination meeting
43 | - Attend monthly meeting for Project Launch Team members (coordinated among your team)
44 | - Attend hack nights and Brigade events that generate projects, such as hackathons
45 | - Available for 5-10 hours of communication per month outside of Hack Nights on projects
46 | 
47 | ##Metrics
48 | The Project Launch Team will track the following:
49 | 
50 | - Stages of all projects (inactive, active, launched) and progress through those stages
51 | - Project launch timelines
52 | - Project human and technical resource needs
53 | - Possible redeployments of projects from other cities
54 | - Other metrics as appropriate
55 | 


--------------------------------------------------------------------------------
/_posts/jobs/2015-08-17-website-and-tools-team.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: job
 3 | categories: jobs
 4 | ---
 5 | 
 6 | Code for San Francisco needs a team to help build tools that help us grow into a more effective, impactful, and inclusive organization. We are looking for two leads to help improve the web presence and Brigade toolkit, as well as folks to support those leads or specialize in specific roles.
 7 | 
 8 | ##The Pitch
 9 | 
10 | Are you committed to code? Do you play nice with others in the open source sandbox? Do you believe in documentation? If you are the kind of person that gets excited about enabling others to do more and better work, then this is the job for you. In this role, your code will multiply the impact of Code for San Francisco. At the core, you'll help build the website into a resource that can be used not just in the communication of what we do, but in the management of the organization and projects. You will also roll out new tools that meet the needs of our diverse users as well as strengthen some of the ones we already use. In this role you should:
11 | 
12 | - Code with empathy, you must listen and understand the problems and bring technical solutions to them
13 | - Be a lifelong learner
14 | - Use github and use it well
15 | - Be interested in sharing your skills with others
16 | - Up to the challenge of applying agile practices to a 100% volunteer organization
17 | - Have worked with APIs and integrations
18 | 
19 | ##Team Responsibilities
20 | - Process
21 |     - Implement stronger standards and best practices for issue and code management on core Brigade technology projects
22 |     - Create process for clear roadmapping among the many needs of the brigade
23 |     - Work with onboarding team and projects team to identify clear pathways for people to help the website and tools team
24 |     - Implement feedback loops from brigade members to help improve tools
25 | - Coordination
26 |     - Coordinate with onboarding and projects team primarily to bring tools to solving some of the core organizational challenges
27 |     - Communicate website and tools milestones and context for marketing, outreach, funding, and recruiting efforts
28 |     - Use tools to communicate the direction and velocity of development as appropriate
29 | - Support
30 |     - Help develop tools that actually meet the needs of the organization and its members
31 |     - Advise the project and onboarding teams on technical matters related to the other projects
32 |     - Help onboarding and projects team develop standard practices for brigade projects
33 | 
34 | ##Relevant Skills
35 | - Ability to code and use a mix of languages and toolkits effectively
36 | - Fluent in javascript and related frameworks
37 | - Good code management practices
38 | - Previous open source dev
39 | - Adaptability
40 | - Patience
41 | - Seriously amazing communication skills
42 | 
43 | ##Commitment
44 | - Attend in-person monthly Core Team coordination meeting
45 | - Attend monthly meeting for website and tools team checkin
46 | - Attend hack nights and Brigade events, recruit skilled developers as needed to the website team
47 | - Available for 5-10 hours of communication per month outside of Hack Nights on member engagement
48 | 
49 | ##Metrics
50 | 
51 | The Team will track the following:
52 | 
53 | - Number of commits on core brigade tools
54 | - Number of resolved pull requests on core brigade tools
55 | - Number of logged issues on core tool repos
56 | - Happiness and satisfaction with tools by users
57 | - Other metrics as appropriate
58 | 


--------------------------------------------------------------------------------
/_posts/jobs/2016-08-30-events-team.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: job
 3 | categories: jobs
 4 | ---
 5 | 
 6 | Apply to manage our events - one of our core offerings to the civic tech
 7 | community. Your efforts will help Code for San Francisco grow into a more
 8 | effective, impactful, and inclusive organization. We are looking for the lead
 9 | to coordinate and run our events, as well as folks to support those leads or
10 | specialize in specific roles.
11 | 
12 | ## The Pitch
13 | 
14 | Are you a logistical mastermind?  Can you organize a calendar of events better
15 | than the Mayor's Scheduler? Can you get information from 7 different teams with
16 | time to spare before your deadline? Do you want to plan events attended which
17 | benefit the community and city of San Francisco? As the Events Lead or part of
18 | a team of Lead Supporters, you will plan our two major events and lead the
19 | coordination of our weekly Hack Nights.
20 | 
21 | ## Relevant Skills
22 | 
23 | - Program or event management background
24 | - Experience revising a process or workflow
25 | - Adaptability
26 | - Patience
27 | - Seriously amazing communication skills
28 | 
29 | ## Commitment
30 | 
31 | - Attend semimonthly virtual core team meetings
32 | - Attend 3x Hack Nights per month
33 | - Available for 5-10 hours of communication per month outside of Hack Nights
34 | 
35 | ## Major Responsibilities
36 | 
37 | ### Lead the planning and coordination of our two key annual events CodeAcross (March) and National Day of Civic Hacking (June)
38 | 
39 | - Plan event programming which includes keynote speakers, workshops, and project hacking
40 | - Secure venue and catering for both events, with support from the rest of the Core Team
41 | - Work closely with the Finance Lead to secure event sponsors and stay within budget
42 | - Work closely with the Partnerships lead to outreach community partners and speakers
43 | 
44 | ### Manage the weekly Civic Hack Night MeetUp's
45 | 
46 | - Create a safe, inclusive, and participatory environment for members and partners
47 | - Balance the frequency of Hack Night events with sufficient Hack Night hacking
48 | - Help the Onboarding and Project Launch teams coordinate efforts to increase member retention
49 | - Ensure Hack Night logistics are finalized well in advance of Hack Night, with support from the rest of the Core Team
50 | 
51 | ### Hack Night Logistics
52 | 
53 | - Build out and coordinate the Hack Night Team
54 | - Manage & delegate hack night tasks each week
55 | 	- Emceeing
56 | 	- Preparing the intro slide deck
57 | 	- Securing Guest Speakers
58 | 	- New member orientation facilitation
59 | - Greet / Check-in members
60 | - Responsible for food-ordering, making sure there's enough, food planning,
61 | 	coordinating with the Finance Team to manage the food budget. Opportunity to
62 | 	engage with local small businesses!
63 | - Organize hack night special events, Demo Nights, and Socials
64 | 
65 | ### Coordinate with key folks internally
66 | 
67 | - Onboarding team
68 | - Make sure someone is leading onboarding each night during hack night
69 | - Help coordinate sign-in/check-in process
70 | - Help connect newbies to projects
71 | - Project team- help newbies plug into existing projects and highlight any
72 | 	projects during hack night
73 | - Serve as a liaison between the onboarding team and the project team so that
74 | 	new people can plug into existing projects
75 | - Make sure the projects are being highlighted during hack night so that the
76 | 	community can understand how they can get involved and next steps.
77 | - Showcase project successes and challenges during hack night!
78 | - Manage guest speaker requests that come from external partners and brigade
79 | 	community
80 | - Create a process flow to manage pitches and speakers at hack night
81 | - Communicate hack night milestones for marketing, outreach, funding, and
82 | 	recruiting efforts
83 | 


--------------------------------------------------------------------------------
/_posts/jobs/2016-09-04-infrastructure-team.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: job
 3 | categories: jobs
 4 | ---
 5 | 
 6 | Code for San Francisco needs a team to help build tools that help us grow into
 7 | a more effective, impactful, and inclusive organization. We are looking for
 8 | a lead to help improve the web presence and Brigade toolkit, as well as folks
 9 | to support the lead or specialize in specific roles.
10 | 
11 | ## The Pitch
12 | 
13 | Are you committed to code? Do you play nice with others in the open source
14 | sandbox? Do you believe in documentation? If you are the kind of person that
15 | gets excited about enabling others to do more and better work, then this is the
16 | job for you. In this role, your code will multiply the impact of Code for San
17 | Francisco. At the core, you'll help coordinate with the
18 | [brigadehub](https://github.com/sfbrigade/brigadehub) team to turn the website
19 | into a resource that can be used not just in the communication of what we do,
20 | but in the management of the organization and projects. You will also roll out
21 | new tools that meet the needs of our diverse users as well as strengthen some
22 | of the ones we already use. In this role you should:
23 | 
24 | - Code with empathy, you must listen and understand the problems and bring technical solutions to them
25 | - Be a lifelong learner
26 | - Use github and use it well
27 | - Be interested in sharing your skills with others
28 | - Up to the challenge of applying agile practices to a 100% volunteer organization
29 | - Have worked with APIs and integrations
30 | 
31 | ## Team Responsibilities
32 | - Process
33 |     - Implement stronger standards and best practices for issue and code management on core Brigade technology projects
34 |     - Create process for clear roadmapping among the many needs of the brigade
35 |     - Work with onboarding team and projects team to identify clear pathways for people to help the infrastructure team
36 |     - Implement feedback loops from brigade members to help improve tools
37 | - Coordination
38 |     - Coordinate with onboarding and projects team primarily to bring tools to solving some of the core organizational challenges
39 |     - Communicate infrastructure milestones and context for marketing, outreach, funding, and recruiting efforts
40 |     - Use tools to communicate the direction and velocity of development as appropriate
41 | - Support
42 |     - Help develop tools that actually meet the needs of the organization and its members
43 |     - Advise the project and onboarding teams on technical matters related to the other projects
44 |     - Help onboarding and projects team develop standard practices for brigade projects
45 | 
46 | ## Relevant Skills
47 | - Ability to code and use a mix of languages and toolkits effectively
48 | - Fluent in javascript and related frameworks
49 | - Good code management practices
50 | - Previous open source dev
51 | - Adaptability
52 | - Patience
53 | - Seriously amazing communication skills
54 | 
55 | ## Commitment
56 | - Attend virtual semimonthly Core Team coordination meeting
57 | - Attend hack nights and Brigade events, recruit skilled developers as needed to the team
58 | - Available for 5-10 hours of communication per month outside of Hack Nights on member engagement
59 | 
60 | ##Metrics
61 | 
62 | The Team will track the following:
63 | 
64 | - Number of commits on core brigade tools
65 | - Number of resolved pull requests on core brigade tools
66 | - Number of logged issues on core tool repos
67 | - Happiness and satisfaction with tools by users
68 | - Other metrics as appropriate
69 | 


--------------------------------------------------------------------------------
/_posts/projects/32595/2014-07-26-sf-open-referral.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | category: projects
 3 | layout: projects
 4 | title: SF Open Referral
 5 | code_url: "https://github.com/sfbrigade/sf-openreferral"
 6 | lead: "Improve social service delivery through shared, open resource data."
 7 | project: "open-referral"
 8 | published: true
 9 | contact: "jason.lally@gmail.com"
10 | ---
11 | 
12 | ##The Problem
13 | Agencies and organizations create and maintain many different community resource directories. Each organization applies similar resources and effort against a shared issue, but there is no shared knowledge. Although they share similar goals and challenges, these efforts work in isolation of each other.
14 | 
15 | 1. Individuals seeking help are left to navigate confusing lists of resources that may or may not lead them to what they need. 
16 | 2. Social workers and other intermediaries must master multiple lists of competing information, making it hard to connect their clients to the relevant help. 
17 | 3. Community development initiatives are left paying for new research to understand the state of their community resources.
18 | 
19 | ###Data - Many Locations and Formats 
20 | 
21 | **Where does the data live?**
22 | 
23 | - internal contract management systems
24 | - printed resource guides
25 | - administration databases
26 | - internal PDFs
27 | - the minds of single employees
28 | 
29 | ##Opportunity - Data should be free!
30 | 
31 | We see an opportunity to free this data so it can be:
32 | 
33 | - published in a standardized format
34 | - easily accessible 
35 | - easy to update
36 | - a precedent for modern referral systems
37 | 
38 | And ultimately: **Deliver consistent, high quality social services to those in need!**
39 | 
40 | ##Additional Resources
41 | 
42 | - Getting started guide
43 | - Mid-market pilot description


--------------------------------------------------------------------------------
/_posts/projects/32597/2015-01-24-code-for-san-francisco-website.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | category: projects
 3 | layout: projects
 4 | published: true
 5 | title: Code for San Francisco Website
 6 | lead: "The online presence for the San Francisco Brigade, Code for San Francisco"
 7 | link: 'http://www.codeforsanfransico.org'
 8 | code_url: 'https://github.com/sfbrigade/sfbrigade.github.io'
 9 | ---
10 | 
11 | ## Our Digital Front Door
12 | 
13 | The Code for San Francisco website (the thing you're looking at now) is a project that anyone can help with. It's a statically-compiled website, meaning it doesn't use a database or complex server....etc, etc.
14 | 
15 | 


--------------------------------------------------------------------------------
/_posts/projects/32601/2015-06-03-sf-cycleready.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | category: projects
 3 | layout: projects
 4 | published: true
 5 | title: SF CycleReady
 6 | lead: "Community-powered bike navigation: match riders to the routes that suit them best"
 7 | contact: "hello@sbzoto.com"
 8 | redirect_from:
 9 | - /projects/test/
10 | ---
11 | 
12 | 
13 | CycleReady is a web and mobile app that offers community-powered bike navigation, helps keep riders informed, and encourages hesitant cyclists to bike in San Francisco.
14 | 
15 | **[Visit cycleready.com for details about our project.](http://www.cycleready.com "SF CycleReady")**
16 | 
17 | ## National Day of Civic Hacking
18 | 
19 | We're looking developers (GIS), data geeks, designers (visual).
20 | 


--------------------------------------------------------------------------------
/_posts/projects/7746/2015-04-29-code-for-san-francisco-shared-resources.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | category: projects
 3 | layout: projects
 4 | published: true
 5 | title: Code for San Francisco Shared Resources
 6 | ---
 7 | 
 8 | ## Below are links to our main folders:
 9 | 
10 | Testing
11 | 
12 | [Welcome to Hack Night & SF Brigade](https://drive.google.com/folderview?id=0B3EtJjXG7BqAMzRtN3BPcHpNMkE&usp=sharing)
13 | 
14 | [Presentations](https://drive.google.com/folderview?id=0B3EtJjXG7BqATlFMR1JBdDRFMHc&usp=sharing)
15 | 
16 | [Hack Days & Events](https://drive.google.com/folderview?id=0B3EtJjXG7BqAM1VVT1NJeHRKODA&usp=sharing)
17 | 
18 | [Brigade Projects](https://drive.google.com/folderview?id=0B3EtJjXG7BqAamFTc0dFdW5iQXM&usp=sharing)


--------------------------------------------------------------------------------
/about/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: Code for San Francisco | About
 4 | ---
 5 | <div class="row" id="maincontent" tabindex="-1">
 6 | 
 7 |   <div id="about">
 8 |     <h1>About Code for San Francisco</h1>
 9 |     <p>Code for San Francisco is a group of people, first and foremost. We also call ourselves technologists, planners, designers, doers, thinkers, and activists. <a href="http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/">Each week</a>, we
10 |       actively work together to improve the City and County of San Francisco, often <a href="https://github.com/sfbrigade">using technology</a> to support our efforts. By connecting people, organizations, resources, tools, and networks to build for San
11 |       Francisco, we will all thrive.</p>
12 | 
13 |     <h2>Brigade</h2>
14 |     <p>Code for San Francisco is a local chapter of the Code for America Brigade, an international network of people committed to using their voices and hands, in collaboration with local governments, to make their cities better.</p>
15 | 
16 |     <h2>Code of Conduct</h2>
17 |     <p>Code for San Francisco holds it’s leadership and participants to a Code of Conduct, which applies to our meetups, events, and digital forums. Read our <a href="https://docs.google.com/document/d/1ZV_iy2CeDlTu13Af9-_5NyOC8SVP9mpxIBn0g1e_S-Q/edit">Code of Conduct</a>.</p>
18 | 
19 |     <h2>Our Vision</h2>
20 |     <p>Code for San Francisco is a safe space for experimentation, learning and
21 |       practicing skills, taking chances, and asking questions, all to affect and
22 |       encourage positive change. Whenever possible, we proactively reach out to
23 |       those who are left out, excluded,
24 |       ignored, or discriminated against. Those people, in our opinion, represent
25 |       our most desirable source for experiences, knowledge, and thoughts. We fail
26 |       without their involvement.
27 |       <!-- Read Code for San Francisco’s 
28 |       <a href="https://docs.google.com/a/codeforamerica.org/document/d/1WcCAWQTfCUhZLqb-AArYDWVWW1E3V96UKDeoIr_3j5s/">2014 strategic plan</a>.</p> -->
29 | 
30 |     <h2>Leadership Team</h2>
31 |     <p>
32 |       Code for San Francisco is organized by a volunteer group of leaders.
33 |       Reach us at <a
34 |          href="mailto:hello@codeforsanfrancisco.org">hello@codeforsanfrancisco.org</a>,
35 |        or <a href="http://c4sf.me/slack">join us on Slack</a>
36 |     </p>
37 |     <h3>Executive Team</h3>
38 |     <ul>
39 |       <li>Maddie Suda, <b>Captain</b> (@maddie on Slack)</li>
40 |       <li>Vedrana Trbusic, <b>Public Relations</b> (@vedrana on Slack)</li>
41 |     </ul>
42 |     <h3>Member Support</h3>
43 |     <ul>
44 |       <li>Jason Lally (@jasonlally on Slack)</li>
45 |       <li>Sandra Stark (@sandrastark on Slack)</li>
46 |     </ul>
47 |     <h3>Project Launch</h3>
48 |     <ul>
49 |       <li>Larry Bafundo (@larry on Slack)</li>
50 |       <li>Jacob Sills (@jsills on Slack)</li>
51 |       <li>Kevin Lam (@smokymcbear on Slack)</li>
52 |     </ul>
53 |     <h3>Infrastructure</h3>
54 |     <ul>
55 |       <li>Jesse Szwedko (@jszwedko on Slack)</li>
56 |       <li>Trent Oswald (on hiatus) (@therebelrobot on Slack)</li>
57 |     </ul>
58 |     <h3>Finance / Partnerships</h3>
59 |     <ul>
60 |       <li>Pamela Mardo (@pamela on Slack)</li>
61 |       <li>Mike Bridge (@bridgeology on Slack)</li>
62 |     </ul>
63 | 
64 |     <h2>Our Partners</h2>
65 |     <p>Code for San Francisco partners with San Francisco government and Bay Area non-profits to make our city work better. Here’s who we work with:</p>
66 |     <ul>
67 |       <li><a href="http://innovatesf.com/">SF Mayor's Office of Civic Innovation</a></li>
68 |       <li><a href="http://datasf.org/">DataSF</a></li>
69 |     </ul>
70 |     <p>Interested in partnering with Code for San Francisco? Contact Jesse or Maddie for more information.</p>
71 |   </div>
72 | 
73 | </div>
74 | 


--------------------------------------------------------------------------------
/about/privacy_policy.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: Code for San Francisco | Privacy Policy
 4 | ---
 5 | 
 6 | <div class="row" id="maincontent" tabindex="-1">
 7 |   <div id="about">
 8 |     <h1>Privacy Policy</h1>
 9 |       <p>
10 |         We use <a href='https://www.google.com/analytics/'>Google
11 |           Analytics</a>, a web analysis service provided by Google to track and
12 |         analyze usage patterns on www.codeforsanfrancisco.org. This information
13 |         is collected in an anonymous fashion by installing a cookie (small
14 |         file) on your computer and sent directly to Google. We do not share
15 |         this data with any other organizations.
16 |       </p>
17 | 
18 |       <p>
19 |         <a href='http://www.google.com/intl/en/policies/privacy/'>Google's
20 |           privacy policy</a> has more information about how they store and use
21 |         this data.
22 |       </p>
23 | 
24 |       <p>
25 |         <a href='https://tools.google.com/dlpage/gaoptout/'>Google's opt out
26 |           page</a> has links to a browser addon you can install to opt out of
27 |         being tracked.
28 |       </p>
29 | 
30 |       <p>
31 |         If we decide to change our privacy policy, we will post those changes on this page.
32 |       </p>
33 | 
34 |       <p>
35 |         Last updated on 2016-02-20.
36 |       </p>
37 | </div>
38 | 


--------------------------------------------------------------------------------
/api/authors.json:
--------------------------------------------------------------------------------
 1 | ---
 2 | ---
 3 | authorsCallback([
 4 | {% for author in site.data.authors %}
 5 | 	{
 6 | 		"name": "{{ author[1].name }}",
 7 | 		"value": "{{ author[0] }}"
 8 | 	}{% if forloop.last != true %},{% endif %} 
 9 | {% endfor %}
10 | ]);
11 | 


--------------------------------------------------------------------------------
/api/tags.json:
--------------------------------------------------------------------------------
 1 | ---
 2 | ---
 3 | tagsCallback([
 4 | {% for tag in site.tags %}
 5 | 	{
 6 | 	"name": "{{ tag[0] }}",
 7 | 	"value": "{{ tag[0] }}"
 8 | 	}{% if forloop.last != true %},{% endif %} 
 9 | {% endfor %}
10 | ]);
11 | 


--------------------------------------------------------------------------------
/blog/feed.xml:
--------------------------------------------------------------------------------
 1 | ---
 2 | ---
 3 | <?xml version="1.0" encoding="UTF-8"?>
 4 | <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
 5 | 	<channel>
 6 | 		<title>{{ site.name | xml_escape }}</title>
 7 | 		<description>{% if site.description %}{{ site.description | xml_escape }}{% endif %}</description>		
 8 | 		<link>{{ site.url }}</link>
 9 | 		<atom:link href="{{ site.url }}/feed.xml" rel="self" type="application/rss+xml" />
10 | 		{% for post in site.posts limit:10 %}
11 | 			<item>
12 | 				<title>{{ post.title | xml_escape }}</title>
13 | 				{% if post.author.name %}
14 | 					<dc:creator>{{ post.author.name | xml_escape }}</dc:creator>
15 | 				{% endif %}        
16 | 				{% if post.excerpt %}
17 | 					<description>{{ post.excerpt | xml_escape }}</description>
18 | 				{% else %}
19 | 					<description>{{ post.content | xml_escape }}</description>
20 | 				{% endif %}
21 | 				<pubDate>{{ post.date | date: "%a, %d %b %Y %H:%M:%S %z" }}</pubDate>
22 | 				<link>{{ site.url }}{{ post.url }}</link>
23 | 				<guid isPermaLink="true">{{ site.url }}{{ post.url }}</guid>
24 | 			</item>
25 | 		{% endfor %}
26 | 	</channel>
27 | </rss>


--------------------------------------------------------------------------------
/blog/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | title: 'Our Stories'
4 | lead: "SF Brigade's recent developments"
5 | ---
6 | 
7 | {% include stories.html %}
8 | {% include add-edit.html posttype="blog" edit=false %}
9 | 


--------------------------------------------------------------------------------
/codeacross/index.html:
--------------------------------------------------------------------------------
 1 | <html lang="en-US">
 2 | <head>
 3 |   <meta http-equiv="refresh" content="0;url=http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/events/228463980/">
 4 |   <title>Redirect to CodeAcross event</title>
 5 | </head>
 6 | <body>
 7 |   Redirecting to <a href="http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/events/228463980/">CodeAcross Event page</a>...
 8 | </body>
 9 | </html>
10 | 


--------------------------------------------------------------------------------
/events/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: Events
 4 | lead: Happenings You Might Want to Check Out
 5 | ---
 6 | <div class="row">
 7 |   <div id="events" style="margin-top:20px">
 8 |     <div class="col-md-8 sidebar">
 9 |       <iframe src="https://calendar.google.com/calendar/embed?mode=AGENDA&amp;height=600&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=codeforsanfrancisco.org_jubgpv4ptibltblat4oi239a68%40group.calendar.google.com&amp;color=%23853104&amp;src=1fcu54gntj5vhrkoj7kmk8gddj8s2g5t%40import.calendar.google.com&amp;color=%2328754E&amp;ctz=America%2FLos_Angeles" style="border-width:0" width="600" height="600" frameborder="0" scrolling="no"></iframe>
10 |       <h2>Weekly Hack Nights<h2>
11 | 
12 |       <h4>Logistics</h4>
13 |       <p>Wednesday, 6:00 - 10 pm<br/>
14 |        155 9th Street<br/>
15 |        Code for America, SF Office</p>
16 | 
17 |       <h4>Come As You Are</h4>
18 |       <p>Technical skills are appreciated but never required to be an effective Civic Hacker; you only need willingness to improve your local community, often through technology.</p>
19 | 
20 |       <p>
21 |         <a href="http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night" class="btn btn-xs btn-success btn-strong-alone">Please RSVP</a>
22 |       </p>
23 |       <p>
24 |       <a href="http://c4sf.me/drive">Slides from previous weeks</a>
25 |       </p>
26 |     </div>
27 | 
28 |     <div class="col-md-4">
29 |       <h1>Featured</h1>
30 |       <div>
31 |         <h2>SF’s National Day of Civic Hacking</h2>
32 |         <h4>Every June</h4>
33 | 
34 |         <p>The National Day of Civic Hacking is an international event for people to focus on improving their community. Thousands of people from around the world tackle civically-oriented projects around open data, disaster relief, mapping, safety and justice, economic development, and other topics. Urbanists, civic hackers, developers, designers, marketers, students, government staff, and passionate residents join together to collaborate on new solutions for our city.</p>
35 |         <p>Code for San Francisco organizes our local National Day of Civic Hacking. Check out 2015’s projects and website. Stay tuned for more information soon with 2016’s event.</p>
36 |         <p>
37 |         <a href="http://codeforsanfrancisco.org/hackforchange/">SF’s National Day of Civic Hacking 2015</a>
38 |         </p>
39 |       </div>
40 |     </div>
41 |   </div>
42 | </div>
43 | 


--------------------------------------------------------------------------------
/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/favicon.ico


--------------------------------------------------------------------------------
/fonts/FontAwesome.otf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/fonts/FontAwesome.otf


--------------------------------------------------------------------------------
/fonts/fontawesome-webfont.eot:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/fonts/fontawesome-webfont.eot


--------------------------------------------------------------------------------
/fonts/fontawesome-webfont.ttf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/fonts/fontawesome-webfont.ttf


--------------------------------------------------------------------------------
/fonts/fontawesome-webfont.woff:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/fonts/fontawesome-webfont.woff


--------------------------------------------------------------------------------
/fonts/glyphicons-halflings-regular.eot:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/fonts/glyphicons-halflings-regular.eot


--------------------------------------------------------------------------------
/fonts/glyphicons-halflings-regular.ttf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/fonts/glyphicons-halflings-regular.ttf


--------------------------------------------------------------------------------
/fonts/glyphicons-halflings-regular.woff:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/fonts/glyphicons-halflings-regular.woff


--------------------------------------------------------------------------------
/getstarted/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: New to Code for San Francisco?
 4 | ---
 5 | <div class="row" id="maincontent" tabindex="-1">
 6 | 	<div class="col-md-12">
 7 |   <div id="about">
 8 |     <h2>First time at a civic tech hack night? Here's some ways to get started.</h2>
 9 |     <ul class="list-group">
10 |         <li class="list-group-item">Check out our <a href="http://codeforsanfrancisco.org/projects/">current projects</a>. Introduce yourself to the team and ask how you can help.</li>
11 |         <li class="list-group-item">Start a discussion about <a href="https://github.com/sfbrigade/project-ideas/issues">a new project idea</a>. Its good to talk about it first to see if anything similar has been built already.</li>
12 |         <li class="list-group-item">Help us research the quality of San Francisco's Open Data on the national <a href="http://us-city.census.okfn.org/">open data census</a>. Help us keep the lead. We have close connections with City Hall to keep the quality of our data top ranking.</li>
13 |         <li class="list-group-item">Help us give some User Experience advice for important online city services for San Francisco at <a href="http://citizenonboard.com/">http://citizenonboard.com/</a>. We have connections to the City departments that can use your advice to improve these services.</li>
14 |         <li class="list-group-item">Code for San Francisco anytime by helping use with our open GitHub Issues. <iframe id="widget" src="http://codeforamerica.org/geeks/civicissues/widget?organization_name=Code-for-San-Francisco&number=3" width="100%" height="500" frameBorder="0"></iframe> </li>
15 |     </ul>
16 |   </div>
17 | </div>
18 | 


--------------------------------------------------------------------------------
/hackforchange/2015recap/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: National Day of Civic Hacking - 2015 Recap
 4 | lead: What Happened
 5 | is_ndoch: true
 6 | ---
 7 | 
 8 | <div class="row article-content">
 9 |   <div class="col-md-12">
10 |     <h1>What Happened?</h1>
11 |     <div class="col-md-12" style="margin:0px; padding:0px">
12 |       <iframe width="100%" height="400" src="http://s280.photobucket.com/user/Code4SF/embed/story"></iframe>
13 |     </div>
14 |     <p>&nbsp;</p>
15 |     <h2>Key Metrics</h2>
16 |     <ul>
17 |       <li>300+ attendees</li>
18 |       <li>20+ projects developed by 150+ hackers</li>
19 |       <li>18,409 Twitter Impressions in 3 days</li>
20 |       <li>48+ hours</li>
21 |       <li>20+ projects developed</li>
22 |       <li>2 professional videos</li>
23 |       <li>1 great hackathon</li>
24 | 
25 |     </ul>
26 |     <hr>
27 | 
28 |     <h2>Project Winners</h2>
29 |     <div class="col-md-12">
30 |       <div class="col-md-3">
31 |       <h4>&mdash; Grand Prize &mdash;</h4><h4>Made with Open Data</h4>
32 |       <a href="http://challengepost.com/software/made-with-open-data">Official Submission</a><br/>
33 |       <a href="https://www.madewithopendata.org">Project Site</a><br/>
34 |       <p>&nbsp;</p>
35 | 
36 |       </div>
37 |       <div class="col-md-3">
38 |         <h4>&mdash; Second Place &mdash;</h4><h4>Housing Market Model</h4>
39 |         <a href="http://challengepost.com/software/housing-market-model">Official Submission</a><br/>
40 |         <a href="https://docs.google.com/file/d/0B6FpfcltJScFaFdrS3FMRWlXanc/edit">Project Site</a><br/>
41 |       </div>
42 |       <div class="col-md-3">
43 | 
44 |         <h4>&mdash; Third Place &mdash;</h4><h4>SF In Progress</h4>
45 |         <a href="http://challengepost.com/software/sf-openreferral">Official Submission</a><br/>
46 |         <a href="http://sf-in-progress.surge.sh/">Project Site</a><br/>
47 |       </div>
48 |     </div>
49 |     <div class="col-md-12">
50 | 
51 |     <div class="col-md-3">
52 | 
53 |       <h4>&mdash; Fourth Place &mdash;</h4><h4>Personas Project</h4>
54 |       <a href="http://challengepost.com/software/the-personas-project-yeal">Official Submission</a><br/>
55 |       <p>&nbsp;</p>
56 |     </div>
57 |     <div class="col-md-3">
58 | 
59 |       <h4>&mdash; Fifth Place &mdash;</h4><h4>WhatIfWe.org</h4>
60 |       <a href="http://challengepost.com/software/whatifwe-org">Official Submission</a><br/>
61 |       <a href="http://whatifwe.org">Project Site</a><br/>
62 |     </div>
63 |   </div>
64 |     <hr/>
65 | 
66 |     <h2>Civic Hacking in Action</h2>
67 |       <div class="col-md-6">
68 |         <div class="video-container">
69 |           <iframe width="640" height="360" src="https://www.youtube.com/embed/W9p5aninvAs?rel=0" frameborder="0" allowfullscreen></iframe>
70 |         </div>
71 |         </div>
72 |         <div class="col-md-6">
73 | 
74 |         <div class="video-container">
75 |           <iframe width="640" height="360" src="https://www.youtube.com/embed/BS_-qLVd_I0?rel=0" frameborder="0" allowfullscreen></iframe>
76 |         </div>
77 |         </div>
78 |         </div>
79 |       <p>&nbsp;</p>
80 | 


--------------------------------------------------------------------------------
/hackforchange/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: About
 4 | is_ndoch: true
 5 | ---
 6 | 
 7 | <div class="row article-content">
 8 |   <div class="col-md-12">
 9 |     <h1>About</h1>
10 |     <hr>
11 |   </div>
12 | 
13 |   <div class="col-md-4 sidebar">
14 |   <h2>Schedule</h2>
15 |     <ul>
16 |       <li><strong>Friday Night, 6/5:</strong> Opening Party</li>
17 |       <li><strong>Saturday, 6/6:</strong> Work Day</li>
18 |       <li><strong>Sunday, 6/7:</strong> Work, Presentations and Closing Reception </li>
19 |     </ul>
20 |     <h2>Location</h2>
21 |     <ul>
22 |       <li id="bulletLoc"><strong>Galvanize  </strong><br>44 Tehama St, San Francisco, CA 94105</li>
23 |     </ul>
24 | 
25 |     <a href="https://www.eventbrite.com/e/national-day-of-civic-hacking-sf-2015-tickets-16547714660?ref=estw" title="Register for National Day of Civic Hacking SF"><button class="btn btn-block btn-md btn-danger"><span style="color:white; font-size: 18px">Get Tickets</span></button></a>
26 | 
27 |     <h2>The Details</h2>
28 |     <ul>
29 |       <li><b>What:</b> 3-day hackathon focused on improving SF</li>
30 |       <li><b>Who:</b> 300+ Passionate People</li>
31 |       <li><b>Why:</b> Meet people. Work on projects. Enjoy food. Make a difference.</li>
32 |      <li><b>Info:</b> Read our <a href="http://codeforsanfrancisco.org/hackforchange/participate/">Participate page</a>.</li>
33 |     </ul>
34 |   </div>
35 | 
36 |   <div class="col-md-8" style="margin-top: 20px;">
37 |     <div id="about">
38 |       <p>The <a href="http://hackforchange.org/">National Day of Civic Hacking</a> is an international event for people to focus on improving their community. Thousands of people from around the world will tackle civically-oriented projects around open data, disaster relief, mapping, safety and justice, economic development, and other topics.</p>
39 |       <p>
40 |       <b>Here in San Francisco,</b> we will be doing a 3-day hackathon organized by Code for San Francisco and SF State. Urbanists, civic hackers, developers, designers, marketers, students, government staff, and passionate residents will join together to collaborate on new solutions for our city.</p>
41 | 
42 |       <p><b>We invite you to join us:</b> <a href="http://codeforsanfrancisco.org/hackforchange/participate/">participate</a> in the weekend, <a href="http://codeforsanfrancisco.org/hackforchange/project-guidelines/">pitch a new project</a>, lead an existing challenge, <a href="http://codeforsanfrancisco.org/hackforchange/sponsors/">sponsor the event</a>, or <a href="http://codeforsanfrancisco.org/hackforchange/partners/">partner with us</a>.</p>
43 | 
44 |       <h2>Shared Prosperity Agenda + National Day of Civic Hacking</h2>
45 |       <p>In January 2015, Mayor Lee announced the <a href="http://sfmayor.org/index.aspx?page=1028">Shared Prosperity Agenda</a> – offering specific activities that the City will undertake for its citizens in the areas of housing, education, transportation,women’s empowerment, and anti-poverty. The National Day of Civic Hacking is a chance for residents to prototype and test out their own solutions in these same issue areas, offering complementary projects to those being envisioned by the government.</p>
46 | 
47 |       <h2>Join Us</h2>
48 |       <ul>
49 |         <li><b>Participants:</b> <a href="https://www.eventbrite.com/e/national-day-of-civic-hacking-sf-2015-tickets-16547714660?ref=estw">Get tickets to join us</a>. Tickets ($10) include the entertainment, workshops, food, and fun for the entire weekend.
50 |           If you have financial constraints, please contact us at hello@codeforsanfrancisco.org.</li>
51 |         <li><b>Project/Challenges:</b> Read the <a href="http://codeforsanfrancisco.org/hackforchange/project-guidelines/">Project and Challenge Guidelines</a>. </li>
52 |         <li><b>Sponsors:</b> <a href="/hackforchange/sponsors/">Read more about our sponsorship opportunities</a>.</li>
53 |         <li><b>Partners:</b> <a href="/hackforchange/partners/">Read more about our partnership opportunities</a>.</li>
54 |       </ul>
55 | 
56 |       <h2>Propose a Challenge or Project</h2>
57 |       <p> Please see our <a href="http://codeforsanfrancisco.org/hackforchange/project-guidelines/">Project and Challenge Guidelines</a> page to learn more. Registration for projects and challenges will open on May 1, 2015. </p>
58 | 
59 |       <h2>Sponsors</h2>
60 |       <p>Thank you to our sponsors:</p>
61 |       <div itemscope="" itemtype="http://schema.org/Organization" class="sponsor-details col-md-12">
62 | 
63 |         <div class="row">
64 |           <div class="col-md-3">
65 |             <img src="{{site.baseurl}}/images/sponsors/MSFTlogo.png" alt="Microsoft" itemprop="logo" class="img-responsive">
66 |           </div>
67 | 
68 |           <div class="col-md-3">
69 |             <img src="{{site.baseurl}}/images/sponsors/Imagineh2o.png" alt="Microsoft" itemprop="logo" class="img-responsive">
70 |           </div>
71 | 
72 |           <div class="col-md-3">
73 |             <img src="{{site.baseurl}}/images/sponsors/galvanize.png" alt="Microsoft" itemprop="logo" class="img-responsive">
74 |           </div>
75 | 
76 |           <div class="col-md-3">
77 |             <img src="{{site.baseurl}}/images/sponsors/CfA_logo.jpg" alt="Microsoft" itemprop="logo" class="img-responsive">
78 |           </div>
79 |         </div>
80 | 
81 |       </div>
82 |       </div>
83 |     </div>
84 |   </div>
85 | </div>
86 | 


--------------------------------------------------------------------------------
/hackforchange/judges/index.html:
--------------------------------------------------------------------------------
  1 | ---
  2 | layout: default
  3 | title: Judges
  4 | is_ndoch: true
  5 | ---
  6 | <div class="row article-content">
  7 |   <div class="col-md-12">
  8 |     <h1>Competition Information</h1>
  9 |     <hr>
 10 |   </div>
 11 | 
 12 |   <div class="col-md-8" style="margin-top: 20px;">
 13 |     <h2>Judges</h2>
 14 | <h3>Andrew Hyder</h3>
 15 | <p>Andrew Hyder is a civic hacker who enjoys making apps and maps. He is the developer relations engineer at Code for America where he travels the world helping volunteers build useful technology for their cities. As a 2013 CfA Fellow in Kansas City he advised on open data legislation, helped organized a volunteer Brigade, and developed BizFriend.ly to help small business owners adopt new technology. A trained urban planner he has built school yards, bicycle paths, and neighborhood parks around the Bay Area.</p>
 16 | 
 17 | <hr>    
 18 |     
 19 |     <h3>Ayori Selassie</h3>
 20 |   <img alt="Ayori Selassie profile" src="{{site.baseurl}}/images/ayoriselassie.jpeg" class="img-circle pull-left" style="margin-right: 20px; width: 200px;">
 21 |     <p>Ayori is an Oakland, CA native, a mother, entrepreneur and tech professional. She is a self taught software developer since age 11 and first founder at age 16 and has worked in tech sector for the last 16 years. Currently she is a Senior Solution
 22 |       Engineer at Salesforce where she&rsquo;s also held roles in Product Management, Business Analysis, and Technical Engineering. Prior to salesforce.com Ayori held engineering roles at large global outfits such as ABB Inc and Schneider Electric. She's
 23 |       lead several initiatives at Salesforce to support women and underrepresented groups of color including serving as President of Boldforce, an employee resource group she founded to support, mentor, retain and recruit employees of African and African
 24 |       American descent. </p>
 25 |       
 26 |       <p>Ayori&rsquo;s list of social contributions include organizing the first ever Hackathon on Black Male Achievement (Startup Weekend Oakland Black Male Achievement), founding Pitch Mixer Entrepreneur Forum (a pre-incubator for entrepreneurs
 27 |       in undeveloped regions), founding and serving as the President of Boldforce, an affinity group at Salesforce supporting people of African descent, serving on the Communities Board at the Anita Borg Institute, mentoring Emerging Leaders in the Middle
 28 |       East and Africa for TechWomen (U.S. Department of State initiative started by Secretary of State Hilary R. Clinton), mentoring young African American males for The Hidden Genius Project (which provides black boys with knowledge, skills and support
 29 |       to create technical jobs in the 21st century), Producing/Designing Sid&rsquo;s Day of Discovery (science education android based tablet video game for pre-schoolers) for the Jim Henson Company featuring Sid the Science Kid and helping a long list
 30 |       of Fortune 500 enterprise businesses maintain their competitive differentiation by adopting cloud strategies.</p>
 31 | 
 32 | <hr>
 33 | 
 34 |     <h3>Dan Parham</h3>
 35 |     <img alt="Dan Parham profile" src="{{site.baseurl}}/images/danparham.jpg" class="img-circle pull-left" style="margin-right: 20px; width: 200px;">
 36 |     <p>Dan Parham co-founded Neighborland with Candy Chang and Tee Parham. Neighborland is a platform that helps residents and community leaders take action on their most important issues. 150 organizations have engaged with 500,000 neighbors to collaboratively
 37 |       shape the development of their communities. Dan is the lead designer, product manager, and runs operations for the team. </p>
 38 | 
 39 |     <p>Before founding Neighborland, Dan was a Director of User Experience at Yahoo, working for the Marketplaces and Advertising Platform teams. Previously, Dan was the Associate Creative Director for Aol&rsquo;s entertainment division. Dan received a BFA
 40 |       from the University of North Carolina.</p>
 41 | 
 42 |     <p>Dan&rsquo;s work has been recognized by the Venice Biennale of Architecture, American Institute of Graphic Arts, and Cooper Hewitt National Design Museum.</p>
 43 | 
 44 |     <p>Dan has spoken about civic engagement and technology at the Smart Cities World Congress in Barcelona, San Francisco Placemaking Summit at the American Institute of Architects, Adaptive Metropolis Conference at UC Berkeley, and SPUR San Jose. </p>
 45 |     
 46 | <hr>
 47 | 
 48 |     <h3>Dave Selinger</h3>
 49 |     <p>Dave Selinger is CEO and Founder of RichRelevance, focussed on personalizing the consumer digital experience. He has been with the company for 7 years. He is the founder of mytwofrontteeth.org and now sits on the board of non-profit 'The Family Giving Tree'. </p>
 50 | 
 51 |     <hr>
 52 |     
 53 |     <h3>Peter Shanley</h3>
 54 |     <img alt="Peter Shanley profile" src="{{site.baseurl}}/images/petershanley.jpg" class="img-circle pull-left" style="margin-right: 20px; width: 200px;">
 55 |     <p>Peter Shanley is the Neo Evangelist and a Principal in the SF office. Peter's passion for business strategy and customer development powers his charter to share Neo&rsquo;s values with the world. From connecting with teams across the Enterprise and
 56 |       Startup landscape to exposing the Neo Way to best-in-class practitioners across the globe, Peter's role bridges business development, marketing and recruiting. Prior to joining Neo, Peter worked across the Fortune 500 and Startup world to bring
 57 |       new ventures to market. He was a product manager at HP Labs/Snapfish and the program director of the Yahoo! Brickhouse product incubator. Between those roles he was VP of Customer Development at Betable where he led the strategic pivot that resulted
 58 |       in an $18.5M Series A investment.</p>
 59 |       
 60 |       <p>Peter is passionate about social justice and impact, applying modern methods and practices to the big problems of our time. He organizes Civic Love and TEDxMarketStreet in San Francisco, advises Code for America
 61 |       and a diverse set of non-profit, philanthropic and government leaders, and champions an impact vertical for Neo's consulting practice. </p>
 62 |       
 63 |       <hr>
 64 | 
 65 |     <h2>Submission Guidelines</h2><ul>
 66 |      <li>Deadline: Sunday June 7th, 2:30 pm</li>
 67 |      <li>Submit on ChallengePost</li></ul>
 68 |     
 69 |     <hr>
 70 | 
 71 |     <h2>Schedule</h2>
 72 | 
 73 |     <ul>
 74 |     
 75 |      <li>2:30 - Submit projects on challenge post</li>
 76 |      <li>3:00-3:10 - Introduce judges</li>
 77 |      <li>3:10-4:30 - Teams present</li>
 78 |      <li>4:30-4:45 - Judges deliberate</li>
 79 |      <li>4:45-5:00 - Award Ceremony</li>
 80 |      <li>5:00-6:00 - Closing Reception</li></ul>
 81 | 
 82 | <hr>
 83 | 
 84 |     <h2>Judging Criteria</h2>
 85 | 
 86 |     <ul>
 87 |       <li><strong>Impact:</strong> How much impact (quality and quantity) could the solution have? Could this solution solve a big or small problem?</li>
 88 |       <li><strong>Product/Market Fit:</strong> How well does the solution fit the needs of the problem they chose to tackle? How user-friendly is the solution?</li>
 89 |       <li><strong>Creativity:</strong> Are there similar solutions available today? Is the solution innovative?</li>
 90 |       <li><strong>Sustainability:</strong> How and Do they have a plan for next steps? How prepared are they to continue their work beyond the event?</li>
 91 |       <li><strong>Presentation:</strong> How well did the team communicate the problem and solution? How well did they respond to the questions from judges?</li>
 92 |     </ul>
 93 | 
 94 | <h2>Minimum Project Goals</h2>
 95 |       <ul>
 96 |         <li> Identify users</li>
 97 |         <li> Show supporting data</li>
 98 |         <li> Complete a competitive assessment</li>
 99 |         <li> Have either a minimum viable product AND/OR concrete conceptual plan</li>
100 |         <li> List your next steps</li>
101 |         <li> Show potential civic and social partners</li>
102 |       </ul>
103 |       
104 | <hr>
105 | 
106 |     <h2>Prizes</h2>
107 |     <h3>1st Place</h3> 
108 |     4 Full-time memberships to Galvanize for 2 months and Free SF National Day of Civic Hacking T-Shirts</p>
109 |     <h3>2nd Place</h3> 
110 |     4 25-Hour Hub Membership to Impact Hub for the whole team and Free SF National Day of Civic Hacking T-Shirts
111 |     <h3>3rd Place</h3> 
112 |     Complimentary tickets to the Exploratorium and Free SF National Day of Civic Hacking T-Shirts</p>
113 |     <h3>4th Place</h3> 
114 |     5 copies of "Coined: The Rich Life of Money and How Its History Has Shaped Us" by Kabir Seghal and Free SF National Day of Civic Hacking T-Shirts</p>
115 |     <h3>5th Place</h3> 
116 |     5 copies of "Haline" by Sundeep Ahuja and Free SF National Day of Civic Hacking T-Shirts</p>
117 |     <h3>Popular Vote</h3> 
118 |     Free SF National Day of Civic Hacking T-Shirts</p>
119 |   </div>
120 | </div>
121 | 


--------------------------------------------------------------------------------
/hackforchange/participate/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: National Day of Civic Hacking
 4 | lead: Learn more about how you can participate
 5 | is_ndoch: true
 6 | ---
 7 | 
 8 | <div class="row article-content">
 9 | 
10 |   <div class="col-md-12">
11 |     <h1>Participate</h1>
12 |     <hr>
13 |     <h2>How can I participate?</h2>
14 |     <h3>Join Us</h3>
15 |     <p>Interested in joining SF's National Day of Civic Hacking (NDoCH)? Awesome. This non-traditional weekend hackathon is a chance for you to join thousands of passionate citizens from around the globe for the National Day of Civic Hacking. Tackle challenges and projects with a range of peers: urbanists, civic hackers, developers, designers, government staff, and more. The topics of the hackathon will include open data, disaster relief, mapping, safety and justice, economic development, and more. We need people with all sorts of ideas, insights and experiences.</p>
16 |     <a href="https://www.eventbrite.com/e/national-day-of-civic-hacking-sf-2015-tickets-16547714660?ref=estw" title="Get Tickets"><button class="btn btn-block btn-md btn-danger"><span style="color:white; font-size: 18px">Get Tickets</span></button></a>
17 | 
18 |     <h3>Pitch and lead project</h3>
19 |     <p>Got a great idea? Or even some code already that you want help on? Great! Take a look at the project guidelines, register for NDoCH SF, and submit your project. Requirements: prep time to develop the idea and action plan for your project, recruiting a team during the Friday night opening party, attending Saturday and Sunday to work on the project, and presenting with your team on Sunday night. You do not need technical expertise to propose a project, but it is good to work with someone who had some technical skills while at the event.</p>
20 |     <a href="https://docs.google.com/forms/d/1fpo5cOb0NJXeD-uUQcLJj31s8uB8xJHajtzoneGTKKA/viewform" title="Submit a project proposal for National Day of Civic Hacking SF"><button class="btn btn-md btn-warning"><span style="color:white">Register Your Project</span></button></a>
21 |     <a href="{{site.baseurl}}/hackforchange/project-guidelines" title="NDoCH SF Project Guidelines"><button class="btn btn-hack btn-md">Check out Project Guidelines</button></a>
22 | 
23 |     <h3>Lead a National Challenge</h3>
24 |     <p>Do you want to be the point person for a challenge? Challenges are projects that have been set up and released by Code for America for this year's National Day of Civic Hacking. This could be taking a project from another city and adapting it to San Francisco, or turning a data set into a visualization, or plenty of other things. Requirements: some prep time to look up the needs of the project (up to 5 hours), recruiting a team during the Fri event, attending Sat/Sun to work on the challenge. You do not need technical expertise to lead a challenge.</p>
25 |     <a href="https://docs.google.com/forms/d/1Gd7HPOVBQORvBLFy-M1xK7RY8CbiDpwRMTGbYbLmiG8/viewform" title="Lead a Challenge"><button class="btn btn-md btn-warning"><span style="color:white">Lead a Challenge</span></button></a>
26 |     <a href="http://hackforchange.org/challenges/" title="Challenges"><button class="btn btn-hack btn-md">National Challenges</button></a>
27 | 
28 | 
29 |     <h3>Work on an existing project or challenge</h3>
30 |     <p>Attend NDoCH SF for the weekend. Bring yourself, your computer and join a project or challenge to tackle over the weekend. There will also be fun activities, food, and workshops throughout the weekend. You can register and check back here as we add projects and challenges.</p>
31 |     <a href="https://www.eventbrite.com/e/national-day-of-civic-hacking-sf-2015-tickets-16547714660?ref=estw" title="Register for National Day of Civic Hacking SF"><button class="btn btn-hack btn-md">Register for NDoCH SF</button></a>
32 |     <h3>Volunteer for the weekend</h3>
33 |     <p>Don't want to hack, but want to contribute to making the weekend successful? We're looking for volunteers to help make NDoCH successful. You can sign up to be a volunteer below. We'll get in touch shortly.</p>
34 |     <a href="https://docs.google.com/forms/d/1klrkDp-152SoX-uZ0C7aL6ID4cZ6YoNm3xgls2Pt7N0/viewform" title="Volunteer for National Day of Civic Hacking SF"><button class="btn btn-hack btn-md">Volunteer for NDoCH SF</button></a>
35 |     <h3>Not sure yet? Register and make your mind up later.</h3>
36 |     <p>Maybe you're just curious? Just want to check this thing out without committing too much? You can still register and show up that weekend. If you plan on floating or checking things out, or want to join a team later, we'll get you all that important information between now and the event.</p>
37 |     <a href="https://www.eventbrite.com/e/national-day-of-civic-hacking-sf-2015-tickets-16547714660?ref=estw" title="Register for National Day of Civic Hacking SF"><button class="btn btn-hack btn-md">Register for NDoCH SF</button></a>
38 |     <hr>
39 |     <h2>Timeline</h2>
40 |     <ul class="timeline">
41 |     <li>
42 |       <div class="timeline-badge"></div>
43 |       <div class="timeline-panel">
44 |         <div class="timeline-heading">
45 |           <h4 class="timeline-title">Friday Night (6:30 - 9 pm)</h4>
46 |         </div>
47 |         <div class="timeline-body">
48 |           <p><strong>Opening Party:</strong> Welcome and Announcements. Participants join Projects and Challenges. Guest Speakers. Music. Food. Drinks. Fun.</p>
49 |         </div>
50 |       </div>
51 |     </li>
52 |     <li class="timeline-inverted">
53 |       <div class="timeline-badge"></div>
54 |       <div class="timeline-panel">
55 |         <div class="timeline-heading">
56 |           <h4 class="timeline-title">Saturday (10 - 6 pm)</h4>
57 |         </div>
58 |         <div class="timeline-body">
59 |           <p><strong>Work and Fun Day:</strong> Projects and Challenge work starts. Fun activities. Experts on hand to consult as needed. Food. Drinks. </p>
60 |         </div>
61 |       </div>
62 |     </li>
63 |     <li>
64 |       <div class="timeline-badge"></div>
65 |       <div class="timeline-panel">
66 |         <div class="timeline-heading">
67 |           <h4 class="timeline-title">Sunday (10 - 6 pm)</h4>
68 |         </div>
69 |         <div class="timeline-body">
70 |           <p><strong>Work Continues</strong>: Teams continue to work on projects and challenges.</p>
71 |           <p><strong>Closing Reception:</strong> Teams present their work to judges. Prizes awarded. A closing reception with drinks and food. Thank you's.</p>
72 |         </div>
73 |       </div>
74 |     </li>
75 |   </ul>
76 |   <hr>
77 |     <h2>FAQs</h2>
78 |     <p><b>How do I sign up to attend SF's NDoCH?</b> Register to attend <a href="https://www.eventbrite.com/e/national-day-of-civic-hacking-sf-2015-tickets-16547714660?ref=estw">SF's National Day of Civic Hacking</a> here. Tickets ($10) include all food, entertainment, workshops, and activities for the whole weekend.</p>
79 | 
80 |     <p><b>What if I cannot attend one of the days of the event?</b>Missing Friday Night: The challenges and projects will be listed ahead of time on our website (stay tuned.) If you cannot attend Friday night, then check out the projects/challenges. Once you have decided on one project/challenge, contact the lead to let them know you want to help on the days you can attend.  Missing Sat/Sun: Come to the Friday Night Party, join a project and let the project/challenge lead know that you cannot attend one of the following days. Then come when you can!</p>
81 |   <p>
82 |   <b>What if I just want to attend the event to observe the projects and network?</b> There will be a variety of workshops and activities throughout the day, however we strongly encourage each participant to join a project team to experience the passion and collaboration of the event.</p>
83 | 
84 |   <p>
85 |   <b>Where can I propose a project?</b> Read the <a href="http://codeforsanfrancisco.org/hackforchange/projectreqs/">Project Requirements</a> and fill out form (on the Project Req's page) to have your project at NDoCH.</p>
86 | 
87 |   <p>
88 |   <b>Do I have to bring my printed ticket to the event?</b> No. You can bring the tickets digitally on your phone (save paper), or just an ID.</p>
89 | 
90 |   <p>
91 |   <b>How can I get more information about Code for San Francisco and other events?</b> Join our <a href="http://codeforsanfrancisco.org/signup/">weekly e-newsletter</a>.</p>
92 | 
93 |   </p>
94 |   </div>
95 | </div>
96 | 


--------------------------------------------------------------------------------
/hackforchange/resources/NDoCH_Logo-02-02_WhiteBackground.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/hackforchange/resources/NDoCH_Logo-02-02_WhiteBackground.png


--------------------------------------------------------------------------------
/hackforchange/resources/NDoCH_onepager.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/hackforchange/resources/NDoCH_onepager.pdf


--------------------------------------------------------------------------------
/hackforchange/resources/NDoCH_webflyer_WhiteBackground.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/hackforchange/resources/NDoCH_webflyer_WhiteBackground.png


--------------------------------------------------------------------------------
/hackforchange/resources/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: National Day of Civic Hacking
 4 | is_ndoch: true
 5 | 
 6 | ---
 7 | <div class="row article-content">
 8 |   <div class="col-md-12">
 9 |     <h1>Resources to Download</h1>
10 |     <hr>
11 | 
12 |     <div class="col-md-4">
13 |       <h2>One Page Flyer</h2>
14 |       <form method="get" action="NDoCH_onepager.pdf">
15 |         <button type="submit" i class="fa fa-file-pdf-o"> Download!</i></button>
16 |       </form>
17 |     </div>
18 | 
19 |     <div class="col-md-4">
20 |       <h2>Web Flyer</h2>
21 |       <form method="get" action="NDoCH_webflyer_WhiteBackground.png">
22 |         <button type="submit" <i class="fa fa-file-image-o"> Download!</i></button>
23 |       </form>
24 |     </div>
25 | 
26 |     <div class="col-md-4">
27 |       <h2>Logo</h2>
28 |       <form method="get" action="NDoCH_Logo-02-02_WhiteBackground.png">
29 |         <button type="submit" <i class="fa fa-file-image-o"> Download!</i></button>
30 |       </form>
31 |     </div>
32 | 
33 |     <div class="col-md-12">
34 |       <hr>
35 |       <h2>Use the following information to help promote the event</h2>
36 |       <p>Calling all passionate people who want to improve San Francisco. <a href="http://codeforsanfrancisco.org/hackforchange/">Attend SF’s National Day of Civic Hacking</a>, June 5 - 7 at <a href= "http://www.galvanize.com/campuses/san-francisco-soma/">Galvanize</a> (downtown SF)! As part of a <a href="http://hackforchange.org/">global event with thousands of people tackling local issues</a>, this nontraditional hackathon will focus on developing civic and socially-oriented projects for the San Francisco Bay Area. All skills, interests, and people are welcome. Just be ready to collaborative and make a difference.</p>
37 | 
38 |       <p>We invite you to join us: <a href="http://codeforsanfrancisco.org/hackforchange/participate/">get tickets to attend</a>, <a href="http://codeforsanfrancisco.org/hackforchange/project-guidelines/">pitch a project</a>, lead a <a href="http://hackforchange.org/challenges/">national challenge</a>, <a href="http://codeforsanfrancisco.org/hackforchange/sponsors/">sponsor the event</a>,<a href="http://codeforsanfrancisco.org/hackforchange/partners/"> or partner with us</a>.</p>
39 | 
40 |       <p><strong>Facebook:</strong> Want to help improve SF? Have an idea for how? Attend SF’s <a hef="http://codeforsanfrancisco.org/hackforchange/">National Day of Civic Hacking</a> (June 5-7). A nontraditional hackathon to tackle challenges, pitch a new projects, and meet other civically-oriented residents. #hackforchangeSF #civictech</p>
41 | 
42 |       <p><strong>Twitter</strong>: Join SF's <a href="http://codeforsanfrancisco.org/hackforchange/">National Day of Civic Hacking</a> with @SFbrigade. Hack to improve SF! June 5-7 at @galvanize. #hackforchangeSF #civictech</p>
43 | 
44 |     </div>
45 |   </div>
46 | </div>


--------------------------------------------------------------------------------
/hackforchange/schedule/index.html:
--------------------------------------------------------------------------------
  1 | ---
  2 | layout: default
  3 | title: About
  4 | is_ndoch: true
  5 | ---
  6 | <h1>Schedule</h1>
  7 | <p>Join us for this amazing program. <a href="https://www.eventbrite.com/e/national-day-of-civic-hacking-sf-2015-tickets-16547714660?ref=estw">Get your tickets ($10) here.</a> We will also be offering childcare on Saturday and Sunday.</p>
  8 | <hr>
  9 | 
 10 | 
 11 | <h3>Friday 6/5 - Opening Party (6 - 10 pm)</h3>
 12 |     <ul class="timeline">
 13 |     <li>
 14 |       <div class="timeline-badge"></div>
 15 |       <div class="timeline-panel">
 16 |         <div class="timeline-heading">
 17 |           <h4 class="timeline-title">Speakers</h4>
 18 |         </div>
 19 |         <div class="timeline-body">
 20 |           <p><ul>
 21 |       <li><strong>Joy Bonaguro</strong> - Chief Data Officer, City and County of San Francisco</li>
 22 |       <li><strong>Sameer Verma</strong> - Information Systems, San Francisco State University</li>
 23 |       <li><strong>Scott Wiener</strong> - San Francisco Board of Supervisors </li>
 24 |       <li><strong>Scott Mauvais</strong> - Director of Technology and Civic Innovation, Microsoft </li>
 25 |       <li><strong>Weston McBride</strong> - Director of Product, WaterSmart </li>
 26 |       <li><strong>Jesse Biroscak</strong> - Co-Captain, Code for San Francisco </li>
 27 |     </ul>
 28 |           </p>
 29 |         </div>
 30 |       </div>
 31 |     </li>
 32 |     <li class="timeline-inverted">
 33 |       <div class="timeline-badge"></div>
 34 |       <div class="timeline-panel">
 35 |         <div class="timeline-heading">
 36 |           <h4 class="timeline-title">Find A Project</h4>
 37 |         </div>
 38 |         <div class="timeline-body">
 39 |           <p>Learn more about <a href="http://codeforsanfrancisco.org/hackforchange/projects/">participating projects</a> and sign up for the one that you want to tackle over the weekend!</p>
 40 |         </div>
 41 |       </div>
 42 |     </li>
 43 |     <li>
 44 |       <div class="timeline-badge"></div>
 45 |       <div class="timeline-panel">
 46 |         <div class="timeline-heading">
 47 |           <h4 class="timeline-title">Performers</h4>
 48 |         </div>
 49 |         <div class="timeline-body">
 50 |           <p><ul>
 51 |       <li><strong>Jamie DeWolf</strong> - Host of the Night</li>
 52 |       <li><strong>Antique Naked Soul</strong> - Beat-Box Musical Group</li>
 53 |       <li><strong>Caitlin Gill</strong> - Stand-Up Comedian</li>
 54 |       <li><strong>Natalie Rhae</strong> - Contortionist </li>
 55 |       <li><strong>Syzygy</strong> - Beat-Boxer / M.C. </li>
 56 |       <li><strong>Gabriel Cortez</strong> - Youth Speaks Poet </li>
 57 |       <li><strong>Natasha Huey</strong> - Youth Speaks Poet </li>
 58 |       <li><strong>Xzist</strong> - Breakdancer </li>
 59 |       <li><strong>Thadra Sherdian Cortez</strong> - Slam Poetry Champion </li>
 60 |       <li><strong>Subverse</strong> - Rapper </li>
 61 |     </ul>
 62 |           </p>
 63 |         </div>
 64 |       </div>
 65 |     </li>
 66 |   </ul>
 67 |   <hr>
 68 | 
 69 | <h3>Saturday 6/6 - Work Day (9 am - 9 pm)</h3>
 70 |     <ul class="timeline">
 71 |     <li>
 72 |       <div class="timeline-badge primary"></div>
 73 |       <div class="timeline-panel">
 74 |         <div class="timeline-heading">
 75 |           <h4 class="timeline-title">Tackle Projects</h4>
 76 |         </div>
 77 |         <div class="timeline-body">
 78 |           <p>Work on your projects throughout the day.</p>
 79 |         </div>
 80 |       </div>
 81 |     </li>
 82 |     <li class="timeline-inverted">
 83 |       <div class="timeline-badge primary"></div>
 84 |       <div class="timeline-panel">
 85 |         <div class="timeline-heading">
 86 |           <h4 class="timeline-title">Awesome Activities</h4>
 87 |         </div>
 88 |         <div class="timeline-body">
 89 |           <p>Take a break from working with these cool activities:
 90 |           <ul>
 91 |       <li><strong><a href="http://comeoutandplaysf.org/">Come Out and Play</a></strong> - Join interactive physical games hosted by this awesome group.</li>
 92 |       <li><strong>Interactive Science</strong> - Explore phenomena through hands-on science activities with David Mangiante.</li>
 93 |       </ul></p>
 94 |         </div>
 95 |       </div>
 96 |   
 97 |     </li>
 98 |   </ul>
 99 |   <hr>
100 | 
101 |   <h3>Sunday 6/7 - Work Finishes, Projects Judged, and Closing Reception (9 am - 6 pm)</h3>
102 |     <ul class="timeline">
103 |     <li>
104 |       <div class="timeline-badge danger"></div>
105 |       <div class="timeline-panel">
106 |         <div class="timeline-heading">
107 |           <h4 class="timeline-title">Finishing Projects </h4>
108 |         </div>
109 |         <div class="timeline-body">
110 |           <p>Teams will work on final details for their projects and submit them online at 2:30 pm. </p>
111 |         </div>
112 |       </div>
113 |     </li>
114 |     <li class="timeline-inverted">
115 |       <div class="timeline-badge danger"></div>
116 |       <div class="timeline-panel">
117 |         <div class="timeline-heading">
118 |           <h4 class="timeline-title">Judging Projects</h4>
119 |         </div>
120 |         <div class="timeline-body">
121 |           <p>All projects will be evaluated by a stellar panel of judges, from 3 - 5 pm. </p>
122 |         </div>
123 |       </div>
124 |     </li>
125 |     <li>
126 |       <div class="timeline-badge danger"></div>
127 |       <div class="timeline-panel">
128 |         <div class="timeline-heading">
129 |           <h4 class="timeline-title">Closing Reception</h4>
130 |         </div>
131 |         <div class="timeline-body">
132 |           <p>Conclude the weekend with a closing celebration of the projects and the work done over the weekend!</p>
133 |         </div>
134 |       </div>
135 |     </li>
136 |   </ul>
137 |   <hr>
138 | 


--------------------------------------------------------------------------------
/happiness/happyform.js:
--------------------------------------------------------------------------------
 1 | $(document).ready(function() {
 2 |     var request;    
 3 |     
 4 |     $("#happyForm").submit(function(event) {
 5 |         // Abort any pending request
 6 |         if (request) {
 7 |             request.abort();
 8 |         }
 9 |         // setup some local variables
10 |         var $form = $(this);
11 | 
12 |         // Let's select and cache all the fields
13 |         var $inputs = $form.find("input, select, button, textarea");
14 | 
15 |         // Serialize the data in the form
16 |         var serializedData = $form.serialize();
17 | 
18 |         // Let's disable the inputs for the duration of the Ajax request.
19 |         // Note: we disable elements AFTER the form data has been serialized.
20 |         // Disabled form elements will not be serialized.
21 |         $inputs.prop("disabled", true);
22 | 
23 |         // Fire off the request
24 |         request = $.ajax({
25 |             url: "https://script.google.com/macros/s/AKfycbzamyed1-s4H_SANrL83v12Fo5yl61AOgU-47J_P201gEe824vS/exec",
26 |             type: "post",
27 |             data: serializedData
28 |         });
29 | 
30 |         // Callback handler that will be called on success
31 |         request.done(function (response, textStatus, jqXHR){
32 |             // Log a message to the console
33 |             console.log("Hooray, it worked!");
34 |         });
35 | 
36 |         // Callback handler that will be called on failure
37 |         request.fail(function (jqXHR, textStatus, errorThrown){
38 |             // Log the error to the console
39 |             console.error(
40 |                 "The following error occurred: "+
41 |                 textStatus, errorThrown
42 |             );
43 |         });
44 | 
45 |         // Callback handler that will be called regardless
46 |         // if the request failed or succeeded
47 |         request.always(function () {
48 |             // Reenable the inputs
49 |             $inputs.prop("disabled", false);
50 |             document.location = "./thankyou.html"; // Other page in same directory
51 |         });
52 | 
53 |         // Prevent default posting of form
54 |         event.preventDefault();
55 |         });
56 | });
57 | 
58 | //function createRecord() {
59 | 
60 |     //var happiness = $("input[name=happiness]:checked").val();
61 |     //var zipcode = $("input[name=zip]").val();
62 |     
63 |     //var gender = $("input[name=gender]").val();
64 |     //var commute = $("input[name=commute]:checked").val();
65 |     //if (typeof commute === "undefined") {
66 |     //    commmute = "did not disclose";
67 |     //}
68 |     //var housing = $("input[name=housing]:checked").val();
69 |     //if (typeof housing === "undefined") {
70 |     //    housing = "did not disclose";
71 |     //}    
72 |     //var age = $("input[name=age]:checked").val();
73 |     //if (typeof age === "undefined") {
74 |     //    age = "did not disclose";
75 |     //}    
76 |     //alert(happiness);
77 |     //alert(zipcode);
78 |     //alert(housing);
79 |     //var item = {"record":[
80 |     //    {"happiness":happiness, "zipcode":zipcode, "gender":gender, "commute":commute, "housing":housing, "age":age}
81 |     //]};
82 |     //df.apis.db.createRecords({"table_name":"happiness", "body":item}, function (response) {
83 |         
84 |     //});
85 | //}
86 | 


--------------------------------------------------------------------------------
/happiness/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: SF Bay Area Happiness Survey
 4 | ---
 5 | <div class="row article-content" id="maincontent2" >
 6 | 
 7 |   <div class="row">
 8 |     <div class="col-xs-2"></div>
 9 |   <div class="col-xs-8">
10 |     <p>June 1, 2015 - Code for San Francisco volunteer hackers today launch the Happiness Survey to better
11 |       understand the Bay Area state of mind. Any resident can take the two-minute survey now
12 |       through June 3 to add their voice to National Day of Civic Hacking, a weekend dedicated
13 |       to social and civic change using technology. </p>
14 |     <form id="happyForm" role="form">
15 |       <div class="form-group">
16 | 
17 |         <div class="row">
18 |         <fieldset>
19 |           <legend>Taking all things together, how happy would you say you are? <br>
20 |         1 (very unhappy) to 5 (extremely happy)(required):<br></legend>
21 | 
22 |         <div class="col-md-2"><input type="radio" id="hap1" name="happiness" value="1"/> <label for="hap1" required > 1 (very unhappy) </label></div>
23 |         <div class="col-md-2"><input type="radio" id="hap2" name="happiness" value="2"/> <label for="hap2" > 2</label></div>
24 |         <div class="col-md-2"><input type="radio" id="hap3" name="happiness" value="3"/> <label for="hap3" > 3</label></div>
25 |         <div class="col-md-2"><input type="radio" id="hap4" name="happiness" value="4"/> <label for="hap4" > 4</label></div>
26 |         <div class="col-md-2"><input type="radio" id="hap5" name="happiness" value="5"/> <label for="hap5" >5 (extremely happy)</label></div>
27 |       <div class="col-md-2"></div></fieldset>
28 |     </div>
29 |         <br>
30 |         <div class="form-group">
31 |           <label for="zip">Enter Home ZIP Code (required):</label>
32 |         <input type="number" name="zipcode" id="zip" maxlength="5" placeholder="94***" pattern="^94\d{3}$" class="form-control" required /><br>
33 | </div>
34 |         <h2>Optional (for statistical purposes only)</h2>
35 |         <div class="form-group">
36 |         <label for="gender">Gender:</label>
37 |         <input type="text" name="gender" id="gender" class="form-control" />
38 |       </div>
39 |   <fieldset>
40 |     <legend>How long was your commute today?</legend>
41 |         <div class="radio"><label for="commute1" ><input type="radio" id="commute1" name="commute" value="I don't have a commute"/>I don't have a commute</label></div>
42 |         <div class="radio"><label for="commute2" ><input type="radio" id="commute2" name="commute" value="Less than 15 minutes"/>Less than 15 minutes</label></div>
43 |         <div class="radio"><label for="commute3" ><input type="radio" id="commute3" name="commute" value="15-30 minutes"/>  15-30 minutes</label></div>
44 |         <div class="radio"><label for="commute4" ><input type="radio" id="commute4" name="commute" value="30-60 minutes"/>  30-60 minutes</label></div>
45 |         <div class="radio"><label for="commute5" ><input type="radio" id="commute5" name="commute" value="1-2 hours"/>  1-2 hours</label></div>
46 |         <div class="radio"><label for="commute6" ><input type="radio" id="commute6" name="commute" value="More than 2 hours"/>  More than 2 hours</label></div>
47 | </fieldset>
48 |         <fieldset>
49 |           <legend>Housing:</legend>
50 |         <div class="radio">
51 |         <label for="housing1" ><input type="radio" id="housing1" name="housing" value="own"/>own</label>
52 |         </div>
53 |         <div class="radio">
54 |         <label for="housing2"><input type="radio" id="housing2" name="housing" value="rent"/>rent</label>
55 |         </div>
56 |         </fieldset>
57 |         <fieldset>
58 |           <legend>Age:</legend>
59 |         <div class="radio">
60 |         <label for="age1"><input type="radio" id="age1" name="age" value="16-29"/>16-29</label>
61 |         </div>
62 |         <div class="radio">
63 |         <label for="age2"><input type="radio" id="age2" name="age" value="30-59"/>30-59</label>
64 |         </div>
65 |         <div class="radio">
66 |         <label for="age3"><input type="radio" id="age3" name="age" value="60+"/>60+</label>
67 |       </div>
68 |         </fieldset>
69 |         </br>
70 |         <button class="submit btn btn-primary" type="submit" value="Send">Submit</button>
71 |       </div>
72 |     </form>
73 |     </div>
74 |     <div class="col-xs-2"></div>
75 |   </div>
76 | 
77 | </div>
78 | <!--<script src='lib/shred.bundle.js' type='text/javascript'></script>-->
79 | <!--<script src='lib/swagger.js' type='text/javascript'></script>-->
80 | <!--<script src='lib/sdk-init.js' type='text/javascript'></script>-->
81 | <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
82 | <!--<script src="http://netdna.bootstrapcdn.com/twitter-bootstrap/2.3.1/js/bootstrap.min.js"></script>-->
83 | <script src=happyform.js></script>
84 | 


--------------------------------------------------------------------------------
/happiness/thankyou.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: SF Bay Area Happiness Survey
 4 | ---
 5 | <div class="row article-content" id="maincontent2" >
 6 |   <div class="row">
 7 |     <div class="col-xs-2"></div>
 8 |   <div class="col-xs-8">
 9 |     <h2>Thank you</h2>
10 |     <p>Results will be made available after National Day of Civic Hacking - San Francisco on June 9, 2015 on this site and presented at Code for San Francisco's <a href="http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/">weekly hack night</a> on June 10, 2015.
11 |   </div>
12 | </div>
13 | </div>
14 | 


--------------------------------------------------------------------------------
/images/9thHoward.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/9thHoward.png


--------------------------------------------------------------------------------
/images/Jesse.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/Jesse.jpg


--------------------------------------------------------------------------------
/images/NDoCH_banner-02_WhiteBackground.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/NDoCH_banner-02_WhiteBackground.png


--------------------------------------------------------------------------------
/images/NDoCH_banner-2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/NDoCH_banner-2.png


--------------------------------------------------------------------------------
/images/NDoCH_webflyer_WhiteBackground.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/NDoCH_webflyer_WhiteBackground.png


--------------------------------------------------------------------------------
/images/ayoriselassie.jpeg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/ayoriselassie.jpeg


--------------------------------------------------------------------------------
/images/blog/EthanAbroad.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/blog/EthanAbroad.jpg


--------------------------------------------------------------------------------
/images/blog/EthanProfessional.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/blog/EthanProfessional.jpg


--------------------------------------------------------------------------------
/images/blog/LocalFreeWebText.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/blog/LocalFreeWebText.jpg


--------------------------------------------------------------------------------
/images/blog/MattArana.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/blog/MattArana.jpg


--------------------------------------------------------------------------------
/images/blog/TopTenA11yIssues.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/blog/TopTenA11yIssues.jpg


--------------------------------------------------------------------------------
/images/cfsf.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/cfsf.png


--------------------------------------------------------------------------------
/images/danparham.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/danparham.jpg


--------------------------------------------------------------------------------
/images/goldengate-top.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/goldengate-top.jpg


--------------------------------------------------------------------------------
/images/headshot 2.15.16.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/headshot 2.15.16.jpg


--------------------------------------------------------------------------------
/images/petershanley.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/petershanley.jpg


--------------------------------------------------------------------------------
/images/projects/ohana-screen.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/projects/ohana-screen.png


--------------------------------------------------------------------------------
/images/sponsors/CfA_logo.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/sponsors/CfA_logo.jpg


--------------------------------------------------------------------------------
/images/sponsors/Imagineh2o.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/sponsors/Imagineh2o.png


--------------------------------------------------------------------------------
/images/sponsors/MSFTlogo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/sponsors/MSFTlogo.png


--------------------------------------------------------------------------------
/images/sponsors/code-for-america.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/sponsors/code-for-america.jpg


--------------------------------------------------------------------------------
/images/sponsors/galvanize.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/sponsors/galvanize.png


--------------------------------------------------------------------------------
/images/uploads/IMG_1846.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/uploads/IMG_1846.jpg


--------------------------------------------------------------------------------
/images/uploads/IMG_2066.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/uploads/IMG_2066.jpg


--------------------------------------------------------------------------------
/images/uploads/IMG_2084.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/uploads/IMG_2084.jpg


--------------------------------------------------------------------------------
/images/uploads/Screen Shot 2015-01-14 at 11.33.05 AM.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/uploads/Screen Shot 2015-01-14 at 11.33.05 AM.png


--------------------------------------------------------------------------------
/images/uploads/Screen Shot 2015-01-14 at 9.39.41 AM.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/uploads/Screen Shot 2015-01-14 at 9.39.41 AM.png


--------------------------------------------------------------------------------
/images/uploads/first.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/uploads/first.png


--------------------------------------------------------------------------------
/images/uploads/gyver.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/images/uploads/gyver.png


--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: Code for San Francisco | A Code for America Brigade
 4 | is_front: true
 5 | ---
 6 | <div class="row">
 7 |   <div class="col-md-7">
 8 |     <h1>Want To Help San Francisco?</br>
 9 |       <small>Good, we could use your help.</small>
10 |     </h1>
11 |     <p class="lead">We are a <a href="http://codeforamerica.org/brigade">Code for America Brigade</a>, which means we're volunteers that contribute our talents toward improving the way our local governments and community organizations use the web. The Brigade is about action and you're here because you are someone who takes action.
12 |     </p>
13 |     <p>We do a lot of things together, but our main activity is our <a href="http://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/">Hack Night</a>, which is held every Wednesday night from 6:30 to 9PM. The Hack Night is for those who want to:</p>
14 |     <ul>
15 |       <li>get work done on civic projects</li>
16 |       <li>start a new project, or find one to join (all backgrounds welcome!)</li>
17 |       <li>bounce ideas and get help from tech and gov experts</li>
18 |       <li>learn about open data, smart cities, and open government</li>
19 |     </ul>
20 | 
21 |     <hr/>
22 | 
23 |     <p>For more, watch the inspirational TED talk given by Jennifer Pahlka, the founder of Code for America.</a>
24 |     </p>
25 |     <div class="video-container">
26 |       <!--a href="http://www.ted.com/talks/jennifer_pahlka_coding_a_better_government?language=en" class="skiplink">Play Video of Jennifer Pahlka's Ted Talk</a-->
27 |       <iframe src="https://embed-ssl.ted.com/talks/lang/en/jennifer_pahlka_coding_a_better_government.html" width="560" height="315" frameborder="0" title="Video of Jennifer Pahlka's Ted Talk" scrolling="no" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe>
28 |       <!--iframe width="560" height="316" src="//www.youtube.com/embed/n4EhJ898r-k" frameborder="0" allowfullscreen></iframe-->
29 |       <!--a11y:changing to ted talk subtitles are in sync and accurate-->
30 |     </div>
31 |     <hr/>
32 | 
33 |     <h2>Sponsors</h2>
34 |     <p>These fine organizations help us keep the Brigade running</p>
35 |     <div class="row">
36 |       <!--
37 |       Set the icons to col-xs-* to prevent them from expanding to fill the
38 |       entire width of the screen on small screens.
39 |       -->
40 |       <div itemscope="" itemtype="http://schema.org/Organization" class="sponsor-details col-xs-3">
41 |         <a href="http://microsoftbayarea.com" itemprop="url">
42 |           <img src="{{site.baseurl}}/images/sponsors/MSFTlogo.png" alt="Microsoft" itemprop="logo" class="img-responsive">
43 |           <span itemprop="name">Microsoft</span>
44 |         </a>
45 |       </div>
46 |       <div itemscope="" itemtype="http://schema.org/Organization" class="sponsor-details col-xs-3">
47 |         <a href="http://codeforamerica.org" itemprop="url">
48 |           <img src="{{site.baseurl}}/images/sponsors/code-for-america.jpg" alt="Code for America" itemprop="logo" class="img-responsive">
49 |           <span itemprop="name">Code for America</span>
50 |         </a>
51 |       </div>
52 |     </div>
53 | 
54 |   </div>
55 | 
56 |   <div class="col-md-5" style="text-align:center;">
57 |     <h2>Code for SF Right Now!</h2>
58 |     <p>Open GitHub Issues on our projects that need your help.</p>
59 |     <iframe id="widget" src="http://codeforamerica.org/geeks/civicissues/widget?organization_name=Code-for-San-Francisco&number=5" width="100%" height="1100" frameBorder="0"></iframe>
60 | 
61 |     <!--
62 |     Issue #19: Add twitter widget.
63 | 
64 |       https://github.com/sfbrigade/sfbrigade.github.io/issues/19
65 | 
66 |     The settings for this widget are located and managed by the SFbrigate
67 |     Twitter account under Settings > Widgets.
68 |     -->
69 |     <a class="twitter-timeline" href="https://twitter.com/SFbrigade" data-widget-id="583457760647315457">Tweets by @SFbrigade</a>
70 |     <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
71 |   </div>
72 | 
73 | </div>
74 | 


--------------------------------------------------------------------------------
/jobs/faq/index.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: Jobs FAQ
 4 | lead: Got Questions? We've got answers
 5 | ---
 6 | [Return to the jobs overview]({{site.baseurl}}/jobs)
 7 | 
 8 | ##Q. Where are you located?
 9 | San Francisco, California.
10 | We meet weekly for Civic Hack Nights at Code for America Headquarters at 155 - 9th Street  (between Mission and Howard), San Francisco, California.
11 | 
12 | ##Q. Why are you called a “brigade”?
13 | We picked up the term from old fire brigades, volunteers who did important work for their towns, who organized themselves, and who took pride in and earned respect for their contribution to civic life.
14 | 
15 | ##Q. Does Code for San Francisco have paid staff?
16 | No. We’re 100% run by our volunteers for now.
17 | 
18 | ##Q. How is Code for San Francisco organized?
19 | We have historically had a Core Team running the brigade. We’re creating better defined, more accountable teams focused on brigade outputs (e.g. launching projects or running hack night) rather than siloed individual roles, all in support of the organization. While a little awkward to say, these teams are designed to push towards a specific output, which requires consistent cross-team communication. As Teams produce results, they will adapt, both in name and structure, to fit evolving organizational needs.
20 | 
21 | Members of most teams will initially be asked to serve for four months with a default option to renew every four months afterwards – we know volunteers have busy lives and we’re making it as easy as possible for new people to step up and in, yet still commit to consistent involvement.
22 | 
23 | Teams will operate semi-independently with day-to-day decisions being taken at the individual Team level and larger strategic decisions being coordinated with the Executive Team to help the organization move in a more-or-less unified way. Teams will be fully empowered to act how they see fit to reduce the need for bureaucracy, especially among a group of volunteers.
24 | 
25 | Most of our volunteers outside of the Core Teams work on a project teams. Teams talk to people with a civic problem, work with those people to design solutions, build and test the solutions, and then promote their use. Project teams nearly always need a diverse group of skills, including developers, designers, marketers, project managers, and, most importantly, someone to engage the people using whatever the team is building.
26 | 
27 | Some of our teams organize around a service or event instead of building software. For example, one team organizes San Franciscans to test civic software for usability and performance. Another set of folks have run our public events like the CityCamp Oakland unconference.
28 | 
29 | ##Q. What is Code for San Francisco’s relationship with Code for America?
30 | Code for America (CfA) supports us through their Brigades program, including regional support staff, a planning process, and some events for brigade organizers. CfA works to get us non-profit discounts on or free use of technology and offers their time to process reimbursements, manage our finances, and run helpful webinar trainings. We are looking to house some of these things internally to help the brigade run more smoothly.
31 | 
32 | ##Q. What is Code for San Francisco’s relationship with other brigades?
33 | We share open source apps with each other, most often through github.
34 | We share ideas on our instant messaging tool (Slack), on the brigade e-mailing list, and use #cfabrigades in social media.
35 | We’re starting to cooperate within California in quarterly meetings, the first in October 2014 with Sacramento, San Jose, San Francisco, and Oakland attending.
36 | 
37 | ##Q. What is Code for San Francisco’s relationship with the City of San Francisco?
38 | Code for San Francisco and the City are friendly and independent. We would like to do more with the City, but it’s tough for them to engage a group of volunteers. The relationship is evolving and we’re getting to know how best to work together over time. City staff and elected officials often come to our Hack Nights and other events.
39 | 
40 | ##Q. How do I apply for one of these roles?
41 | Review the jobs available on this site, then use the application form embedded on each job posting.
42 | If you’d like to lead one of our functional teams, [check out our /jobs page](http://www.codeforsanfrancisco.org/jobs) for role descriptions. We are asking new leaders to commit to meeting weekly on their own teams and monthly as a full group of leads. Meetings may take place outside of the normal hack night schedule.
43 | 
44 | ##Q. How long do people serve in a leadership role?
45 | Initially we’re asking people to serve for four months to test out the role for themselves, and we hope most people will want to renew for the next quarter.
46 | 


--------------------------------------------------------------------------------
/jobs/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: Jobs
 4 | lead: Join the core team and help shape the Brigade
 5 | ---
 6 | <div id="jobs" class="row" style="margin-top:20px">
 7 | <div class="col-md-7">
 8 |   <h2>Help build a stronger organization</h2>
 9 |   <p>
10 |     Code for San Francisco is a collection of creative volunteers
11 |     working to improve the lives of San Franciscans. We continue to
12 |     advocate for open public data, we continue to build useful civic
13 |     apps like Adopt-a-Drain and We Vote, and we continue to
14 |     work on civic infrastructure like Lighten.
15 |   </p>
16 |   <p><b>But <u>we want to do more</u> and to do it better.</b> To that end, we are building our leadership team.</p>
17 |   <p>The positions on the teams below are unpaid volunteer positions, but the work is rewarding and a lot of fun. Get in on building an entirely new model of civic engagement and action. You can apply into a team and indicate interest in either leading or supporting the team. Each team will have one leader ultimately responsible for delivering on the vision, but will likely be supported by several others in that work. While the teams support core, important functions of the Brigade, all core team members will work collaboratively together across teams as well. Read more about the teams below and apply using the form to the right.</p>
18 |   <ul>
19 |     <li><a href="{{site.baseurl}}/jobs/executive-team">Executive Team</a></li>
20 |     <li><a href="{{site.baseurl}}/jobs/events-team">Events Team</a></li>
21 |     <li><a href="{{site.baseurl}}/jobs/new-member-support-team">New Member Support Team</a></li>
22 |     <li><a href="{{site.baseurl}}/jobs/infrastructure-team">Infrastructure Team</a></li>
23 |     <li><a href="{{site.baseurl}}/jobs/finance-team">Finance Team</a></li>
24 |   </ul>
25 |   <hr>
26 |   <h2>Safe, inclusive and diverse</h2>
27 |   <p>We keep our events safe for all and our members <a href="https://docs.google.com/document/d/1ZV_iy2CeDlTu13Af9-_5NyOC8SVP9mpxIBn0g1e_S-Q/edit">follow a code of conduct.</a></p>
28 |   <p>We strive for inclusiveness and diversity and these new roles are very much open to all. <a href="mailto:hello@codeforsanfrancisco.org">If you need assistance in completing an application, please email hello@codeforsanfrancisco.org.</a></p>
29 |   <h2>Got Questions?</h2>
30 |   <a href="{{site.baseurl}}/jobs/faq">Read our FAQ to answer all your burning questions</a>
31 | </div>
32 | 
33 | <div class="col-md-5">
34 |   {% include application.html %}
35 | </div>
36 | </div>
37 | 


--------------------------------------------------------------------------------
/js/projectData.js:
--------------------------------------------------------------------------------
 1 | ---
 2 | ---
 3 | var projectData =
 4 | {
 5 | {% assign posts = site.posts | sort: title | reversed %}
 6 | {% for post in posts %}
 7 | {% if post.layout == 'projects' %}
 8 | {% assign id_array = post.path | split:"/" %}
 9 |   	"{{id_array[2]}}": {
10 |   		"url" : "{{site.baseurl}}{{post.url}}"
11 |   	} {% unless forloop.last %},{% endunless%}
12 | {% endif %}
13 | {% endfor %}
14 | };
15 | 


--------------------------------------------------------------------------------
/js/projects.js:
--------------------------------------------------------------------------------
 1 | ---
 2 | ---
 3 | function slugify(text) {
 4 |   text = text.replace(/[^-a-zA-Z0-9\s+]+/ig, '');
 5 |   text = text.replace(/\s+/gi, "-");
 6 |   return text;
 7 | }
 8 | 
 9 | var cfapi_url = 'http://codeforamerica.org/api/organizations/Code-for-San-Francisco/projects';
10 | 
11 | // Go get projects! Then show them off.
12 | $.getJSON(cfapi_url, showProjects);
13 | 
14 | function showProjects(response){
15 |   projects = response.objects;
16 |   var featuredIndex = []; 
17 |   // loop through our project data
18 |   $.each(projects, function(i, project) {
19 |     //if (project['tags'].indexOf("featured") > -1) {
20 |     //  featuredIndex.push(i);
21 |     //}
22 |     // check to see if this project has a corresponding Jekyll page
23 |     if (projectData[project['id']]) {
24 |       project['cfsf_url'] = projectData[project['id']]['url'];
25 |     }
26 |     // add some variables to support adding a new Jekyll project post
27 |     project['repository_nwo'] = {% if site.github.repository_nwo %}"{{site.github.repository_nwo}}"{% else %}" "{% endif %};
28 |     project['default_branch'] = "{{site.defaultbranch}}";
29 |     project['file_name'] = moment().format('YYYY-MM-DD-') + slugify(project['name']).toLowerCase() + ".md";
30 |     // to display text like 'x days ago' we use moment.js's awesome fromNow function
31 |     // http://momentjs.com/docs/#/displaying/fromnow/
32 |     project['last_updated_formatted'] = moment(project['last_updated']).fromNow();
33 | 
34 |   });
35 | 
36 |   var template = $('#projects').html();
37 | 
38 |   var featuredDiv = document.createElement('div');
39 |   featuredDiv.id = 'featured';
40 |   $("#hack-night-projects").append(featuredDiv);
41 |   $("#hack-night-projects").append(Mustache.render(template, { projects: projects }));
42 |   // Follow next page links
43 |   if (response.pages.next) {
44 |     $.getJSON(response.pages.next, showProjects);
45 |   }
46 | //
47 | }
48 | 


--------------------------------------------------------------------------------
/js/resources.js:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/sfbrigade/sfbrigade.github.io.2017-11-05/a21cfde652d86fe1e622f6d39a9fd48a736702fe/js/resources.js


--------------------------------------------------------------------------------
/js/sponsors.js:
--------------------------------------------------------------------------------
 1 | $(function() { 
 2 |   $("#form-sponsor-us").validate({
 3 |     rules: {
 4 |       _replyto: {
 5 |         required: true,
 6 |         email: true
 7 |       },
 8 |       message: {
 9 |         required: true
10 |       },
11 |       name: {
12 |         required: true
13 |       }
14 |     },
15 |     submitHandler: function(form) {
16 |       var data = $(form).serialize();
17 |       $.ajax({
18 |         url: "//formspree.io/hello@codeforsanfrancisco.org",
19 |         method: "POST",
20 |         data: data,
21 |         dataType: "json"
22 |       })
23 |       .done(function() {
24 |         $('.form-content').hide();
25 |         $('.form-sponsor-us-success').show();
26 |         $('.form-submit').hide();
27 |       });
28 |     }
29 |   });
30 | });


--------------------------------------------------------------------------------
/people/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: 'People <small id="people-count" style="color: #fff;"></small>'
 4 | scripts: [people.js]
 5 | lead: The people that make our projects possible
 6 | ---
 7 | <div class="row main-row">
 8 |   <div class="col-md-12">
 9 |   <table id='hack-night-people' class='table people'>
10 |     <thead>
11 |       <tr>
12 |         <th>Name</th>
13 |         <th>Location</th>
14 |         <th>Civic projects</th>
15 |         <th>Contributions</th>
16 |       </tr>
17 |     </thead>
18 |     <tbody>
19 |     </tbody>
20 |   </table>
21 | </div>
22 | </div>
23 |   <script id="people" type="text/html">
24 |   {% raw %}
25 |   {{#people}}
26 |     <tr>
27 |       <td>
28 |         <a href='{{html_url}}'>
29 |           <img class='img-thumbnail' src='{{avatar_url}}' alt='{{login}}' />
30 |           {{name}}
31 |         </a>
32 |       </td>
33 |       <td>{{location}}</td>
34 |       <td><a href='projects.html#/?search={{login}}'>{{projects}}</a></td>
35 |       <td><a href='https://github.com/{{login}}?tab=activity'>{{contributions}}</a></td>
36 |     </tr>
37 |     {{/people}}
38 |     {% endraw %}
39 |   </script>


--------------------------------------------------------------------------------
/projects.csv:
--------------------------------------------------------------------------------
1 | ---
2 | ---
3 | {% assign projects = site.categories.projects | sort: title | reversed %}
4 | name,description,link_url,code_url,status,tags{% for project in projects %}
5 | {{ project.title}},{{project.excerpt}},{{project.link}},{{project.code_url}},"",""{% endfor %}
6 | 


--------------------------------------------------------------------------------
/projects/details.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: 'Projects'
 4 | excerpt: Open source civic technology projects from the local open gov community.
 5 | ---
 6 | <div class="row main-row">
 7 | {% for post in site.categories.projects %}
 8 |   <div class="col-md-4">
 9 |       <div class="panel panel-default">
10 |         <div class="panel-heading">
11 |           <h3 class="panel-title"><a href="{{post.url}}">{{post.title}}</a></h3>
12 |         </div>
13 |         <div class="panel-body">
14 |           {{ post.excerpt}}
15 |         </div>
16 |       </div>
17 |   </div>
18 | {% endfor %}
19 | </div>
20 | <!-- End page content-->
21 | 


--------------------------------------------------------------------------------
/projects/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: 'Our Projects'
 4 | scripts: ['projectData.js','projects.js']
 5 | lead: 'The fine works of Code for San Francisco'
 6 | ---
 7 | 
 8 | <section>
 9 |   <div id="hack-night-projects">
10 |   </div>
11 | </section>
12 | 
13 | <!-- Define the template for data loaded from the CFAPI -->
14 | <script id="projects" type="x-tmpl-mustache">
15 | {%raw%}
16 | {{#projects}}
17 | 
18 |   <div class="row">
19 |     <div class="col-sm-12">
20 |       <h1>{{name}} {{^cfsf_url}}
21 |           <a href="https://github.com/login/oauth/authorize?client_id=c602a8bd54b1e774f864&scope=repo&redirect_uri=http://prose.io/#{{repository_nwo}}/new/{{default_branch}}/_posts/projects/{{id}}/{{file_name}}" class="btn btn-xs btn-success">Create detailed project page</a></strong><span style="display:none">{{id}}</span>
22 |           {{/cfsf_url}}</h1>
23 |       <p class="lead">{{description}}
24 |       {{#cfsf_url}}
25 |       <strong><a href="{{cfsf_url}}">Learn more...</a></strong>
26 |       {{/cfsf_url}}</p>
27 |       <div class="row">
28 |         <div class="col-md-5">
29 |           {{#link_url}}
30 |           <span class="glyphicon glyphicon-home"></span>
31 |           <a href="{{link_url}}">{{link_url}}</a>
32 |           <br />
33 |           {{/link_url}}
34 |           {{#code_url}}
35 |           <i class="fa fa-github-square"></i>
36 |           <a href="{{code_url}}">{{code_url}}</a>
37 |           <br />
38 |           {{/code_url}}
39 |           <strong>Last Updated: </strong>{{last_updated_formatted}}
40 |           <br />
41 |           {{#github_details.language}}
42 |           <strong>Language: </strong>{{github_details.language}}
43 |           {{/github_details.language}}
44 |           <br/>
45 |           <br/>
46 |         </div>
47 |         <div class="col-md-offset-1 col-md-6">
48 |           {{#github_details}}<strong>GitHub Contributors</strong>{{/github_details}}
49 |           <p class='contributors'>
50 |             {{#github_details.owner}}
51 |             <a href='{{html_url}}' class='contributor-owner'><img class='img-thumbnail' src='{{avatar_url}}' alt='Owner: {{login}}' title='Owner: {{login}}'/></a>
52 |             <span style='display: none;'>{{login}}</span>
53 |             {{/github_details.owner}}
54 |             {{#github_details.contributors}}
55 |             {{^owner}}
56 |             <a href='{{html_url}}'><img class='img-thumbnail' src='{{avatar_url}}' alt='{{login}}' title='{{login}}'/></a>
57 |             <span style='display: none;'>{{login}}</span>
58 |             {{/owner}}
59 |             {{/github_details.contributors}}
60 |           </p>
61 |         </div>
62 |       </div>
63 |     </div>
64 |   </div>
65 | {{/projects}}
66 | {%endraw%}
67 | </script>
68 | 
69 | <hr/>
70 | 
71 | Powered by the <a href="https://github.com/codeforamerica/cfapi">CfAPI</a>. Edit <a href="https://docs.google.com/a/codeforamerica.org/spreadsheet/ccc?key=0ArHmv-6U1drqdDVGZzdiMVlkMnRJLXp2cm1ZTUhMOFE&usp=drive_web#gid=0">this spreadsheet</a> to change which projects are included.
72 | 


--------------------------------------------------------------------------------
/scripts/audit.js:
--------------------------------------------------------------------------------
 1 | // Copyright 2013 Google Inc.
 2 | //
 3 | // Licensed under the Apache License, Version 2.0 (the "License");
 4 | // you may not use this file except in compliance with the License.
 5 | // You may obtain a copy of the License at
 6 | //
 7 | //      http://www.apache.org/licenses/LICENSE-2.0
 8 | //
 9 | // Unless required by applicable law or agreed to in writing, software
10 | // distributed under the License is distributed on an "AS IS" BASIS,
11 | // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 | // See the License for the specific language governing permissions and
13 | // limitations under the License.
14 | //
15 | // Copied from accessibility-developer-tools so that we can customize exceptions
16 | 
17 | var page = require('webpage').create(),
18 |     system = require('system'),
19 |     url;
20 | 
21 | // disabling so we can get the document root from iframes (http -> https)
22 | page.settings.webSecurityEnabled = false;
23 | 
24 | if (system.args.length !== 2) {
25 |   console.log('Usage: phantomjs audit.js URL');
26 |   phantom.exit();
27 | } else {
28 |   url = system.args[1];
29 |   page.open(url, function (status) {
30 |     if (status !== 'success') {
31 |       console.log('Failed to load the page at ' +
32 |         url +
33 |         ". Status was: " +
34 |         status
35 |         );
36 |       phantom.exit();
37 |     } else {
38 |       page.injectJs('../node_modules/accessibility-developer-tools/dist/js/axs_testing.js');
39 |       var report = page.evaluate(function() {
40 |         var configuration = new axs.AuditConfiguration();
41 | 
42 |         // https://github.com/GoogleChrome/accessibility-developer-tools/issues/247
43 |         // in general this rule seems very finicky and intermittently gives false positives
44 |         configuration.ignoreSelectors('focusableElementNotVisibleAndNotAriaHidden', '*');
45 | 
46 |         var results = axs.Audit.run(configuration);
47 |         return axs.Audit.createReport(results);
48 |       });
49 |       console.log(report);
50 |       phantom.exit();
51 |     }
52 |   });
53 | }
54 | 


--------------------------------------------------------------------------------
/scripts/setup:
--------------------------------------------------------------------------------
 1 | #!/bin/bash
 2 | 
 3 | set -o errexit
 4 | 
 5 | if ! which ruby ; then
 6 |   echo "Please install ruby from https://www.ruby-lang.org/en/downloads/"
 7 | fi
 8 | 
 9 | if ! which bundle; then
10 |   echo "Please install the bundler ruby gem (e.g. gem install bundler)"
11 | fi
12 | 
13 | if ! which npm ; then
14 |   echo "Please install nodejs from https://nodejs.org/en/download/"
15 | fi
16 | 
17 | if ! which phantomjs ; then
18 |   echo "Please install phantomjs from http://phantomjs.org/download.html"
19 |   exit 1
20 | fi
21 | 
22 | npm install accessibility-developer-tools@2.10.0
23 | 
24 | bundle install
25 | 


--------------------------------------------------------------------------------
/scripts/test:
--------------------------------------------------------------------------------
 1 | #!/bin/bash
 2 | 
 3 | set -o errexit
 4 | 
 5 | echo "Running jekyll doctor"
 6 | bundle exec jekyll doctor
 7 | 
 8 | echo "Building"
 9 | bundle exec jekyll build
10 | 
11 | echo "Running accessibility checks"
12 | 
13 | status=0
14 | for file in $(find _site -name '*.html' | sed -e 's/_site//') ; do
15 |   echo "Checking $file"
16 |   if [[ "$(curl -s http://localhost:4000$file)" == *'<title>Redirecting...</title>'* ]] ; then
17 |     echo "Skipping $file because it is a redirect" # https://github.com/jekyll/jekyll-redirect-from/pull/100
18 |     continue
19 |   fi
20 |   output="$(phantomjs scripts/audit.js http://localhost:4000$file)"
21 |   echo "$output"
22 |   if [[ "$(echo "$output" | grep -E '(Failed to load|Warnings:)')" != '' ]] ; then
23 |     set +o errexit
24 |     let "status++"
25 |     set -o errexit
26 |   fi
27 | done
28 | 
29 | exit $status
30 | 


--------------------------------------------------------------------------------
/sfperspectives/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: San Francisco Perspectives
 4 | ---
 5 | 
 6 | <div class="row" id="maincontent" tabindex="-1">
 7 |     <div class="col-md-6">
 8 |     <h1> What is San Francisco Perspectives? </h1>
 9 |     <p> 
10 |      San Francisco Perspectives is a group of regular San Francisco locals who want to test out websites, mobile apps, and other tools created by Code for San Francisco volunteers to help improve our city. Examples can be found on the Code for San Francisco Projects Page.</p>
11 |     <p>Code for San Francisco is a growing community of "civic hackers" — technology developers, community developers, engaged citizens, and others who collaborate to develop tech-based solutions for civic needs.</p>
12 | 
13 |     <h1> How do I participate? </h1>
14 |     <p>We need people from all parts of San Francisco to test out these solutions and provide insights to make them better. No special experience is needed.</p>
15 |     <p>If you’re interested in joining San Francisco Perspectives, just fill out the form on this page. </p>
16 |     <p>After you submit the form, your information will be stored securely and will not be used for any purpose other than to contact you about participating in a San Francisco Perspectives session. You can opt out at any time.</p>
17 | <p>Your First Name, Last Name, and email address are required in order to contact you about participating.<p>
18 |     <h1>FAQ</h1>
19 | 
20 | <div><b>Q:</b> What would I do as a San Francisco Perspectives participant?</div>
21 | <div><b>A:</b> Code for America volunteers may contact you to help in one of the following ways:</div>
22 | <p>
23 | <ol>
24 |     <li>
25 |         Large Group Sessions - Come to a group “testing” session at the Code for San Francisco Headquarters (or a public library or other community space). There you will join other San Francisco Perspectives participants to test out a website or other tech solution created by Code for San Francisco volunteers. They will speak with you about your experience and gather feedback to improve the tool.
26 |     </li> 
27 |     <li>
28 |          Small Group Sessions - Come to Code for San Francisco Headquarters for a small informal discussion or brainstorming session with one of our project teams to share your perspectives on how to make their solution better.
29 |     </li>
30 |     <li>
31 |         Community Needs Assessment - Take part in a focus group discussion about what civic needs you, a San Francisco local, have. Code for San Francisco volunteers will get ideas of how technology solutions may be able to help.
32 |     </li>
33 | </ol>
34 | </p>
35 | 
36 | <div><b>Q:</b> What do San Francisco Perspectives Participants receive in return for sharing their experiences?</div>
37 | <div><b>A:</b> Each session is unique. Participants will be informed whether certain incentives are offered for their session. Examples of some things participants may receive as a result of participating:</div>
38 | <ul>
39 |     <li>
40 |         The great feeling of helping to improve their community
41 |     </li>
42 |     <li>
43 |         Dinner at Code for America Headquarters
44 |     </li>
45 |     <li>
46 |         Gift Card
47 |     </li>
48 |     <li>
49 |         Meeting other interesting SF locals 
50 |     </li>
51 | </ul>
52 |     <h3>Have questions? Contact us at: <a href="mailto:sfperspectives@codeforsanfrancisco.org" target="_top">sfperspectives@codeforsanfrancisco.org</a></h3>
53 |     </div>
54 |     <div class="col-md-6">
55 |     <iframe src="https://docs.google.com/forms/d/1a96bLVr5eHeq056cIzioTb5vHjbB_-zJcPR4nawdGbM/viewform?embedded=true" id="" width="600" height="1119" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>
56 |     </div>
57 | </div>
58 | 


--------------------------------------------------------------------------------
/signup/index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | title: Sign Up for Code for San Francisco
 4 | ---
 5 | <div class="row" id="maincontent" tabindex="-1">
 6 | 
 7 |   <!-- Begin MailChimp Signup Form -->
 8 |   <link href="//cdn-images.mailchimp.com/embedcode/classic-081711.css" rel="stylesheet" type="text/css">
 9 |   <style type="text/css">
10 | #mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; }
11 | /* Add your own MailChimp form style overrides in your site stylesheet or in this style block.
12 |    We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */
13 |   </style>
14 |   <div id="mc_embed_signup">
15 |     <form action="//codeforsanfrancisco.us10.list-manage.com/subscribe/post?u=13e30524fec23783d4f80e3b5&amp;id=9ea07180fe" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate>
16 |       <div id="mc_embed_signup_scroll">
17 |         <h2>Subscribe to our mailing list</h2>
18 |         <div class="indicates-required"><span class="asterisk">*</span> indicates required</div>
19 |         <div class="mc-field-group">
20 |           <label for="mce-EMAIL">Email Address  <span class="asterisk">*</span>
21 |           </label>
22 |           <input type="email" value="" name="EMAIL" class="required email" id="mce-EMAIL">
23 |         </div>
24 |         <div class="mc-field-group">
25 |           <label for="mce-FNAME">First Name </label>
26 |           <input type="text" value="" name="FNAME" class="" id="mce-FNAME">
27 |         </div>
28 |         <div class="mc-field-group">
29 |           <label for="mce-LNAME">Last Name </label>
30 |           <input type="text" value="" name="LNAME" class="" id="mce-LNAME">
31 |         </div>
32 |         <div id="mce-responses" class="clear">
33 |           <div class="response" id="mce-error-response" style="display:none"></div>
34 |           <div class="response" id="mce-success-response" style="display:none"></div>
35 |         </div>    <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->
36 |         <div aria-hidden="true" style="position: absolute; left: -5000px;"><input type="text" name="b_13e30524fec23783d4f80e3b5_9ea07180fe" tabindex="-1" value=""></div>
37 |         <div class="clear"><input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button"></div>
38 |       </div>
39 |       <h2>Past Issues</h2>
40 |       <style type="text/css">
41 | <!--
42 | .display_archive {font-family: arial,verdana; font-size: 12px;}
43 | .campaign {line-height: 125%; margin: 5px;}
44 | //-->
45 |       </style>
46 |       <script language="javascript" src="http://us10.campaign-archive1.com/generate-js/?u=13e30524fec23783d4f80e3b5&fid=5557&show=10" type="text/javascript"></script>
47 |     </form>
48 |   </div>
49 |   <script type='text/javascript' src='//s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js'></script><script type='text/javascript'>(function($) {window.fnames = new Array(); window.ftypes = new Array();fnames[0]='EMAIL';ftypes[0]='email';fnames[1]='FNAME';ftypes[1]='text';fnames[2]='LNAME';ftypes[2]='text';}(jQuery));var $mcj = jQuery.noConflict(true);</script>
50 |   <!--End mc_embed_signup-->
51 | 
52 | </div>
53 | 


--------------------------------------------------------------------------------