From 30fbd3133ceb5cd692100274b42d0d0bdfe54662 Mon Sep 17 00:00:00 2001 From: John Dunning Date: Thu, 11 Jan 2024 18:13:22 -0800 Subject: [PATCH] Add existing blog pages into src/content/blog/ Add blog/[slug].astro to render the markdown from a blog page. Add config.ts to content/blog. --- .../blog/2014-07-26-sf-open-referral.md | 42 +++ .../content/blog/2014-09-05-localfreeweb.md | 72 ++++ ...paign-data-visualization-app-can-help-y.md | 36 ++ ...-22-speaker-matt-arana-on-accessibility.md | 43 +++ .../2015-01-07-sf-brigade-hosts-citycampsf.md | 41 +++ ...01-18-announcing-c4sf-sponsor-microsoft.md | 22 ++ ...ating-the-life-of-our-friend-ethan-lang.md | 30 ++ ...9-april-12-2015-campaign-finance-summit.md | 68 ++++ ...re-happy-or-not-says-tech-volunteer-gro.md | 25 ++ .../blog/2016-03-24-codeacross-sf-2016.md | 71 ++++ .../2016-04-09-meet-sf-brigade-members.md | 50 +++ ...-sf-brigades-data-science-working-group.md | 40 +++ ...ualization-a-new-way-to-address-communi.md | 21 ++ ...6-11-17-announcing-c4sf-sponsor-segment.md | 26 ++ .../blog/2016-11-23-community-forum-week-1.md | 61 ++++ ...-02-09-project-investment-fund-launches.md | 39 +++ ...17-02-16-2016-sf-brigade-year-in-review.md | 72 ++++ ...7-searching-for-equity-in-a-sea-of-data.md | 45 +++ ...17-05-28-spring-2017-project-demo-night.md | 14 + ...t-timers-account-of-code-for-san-franci.md | 36 ++ ...y-of-civic-hacking-2017-how-we-learned-.md | 44 +++ ...5-designers-geeks-provoke-sf-crime-data.md | 24 ++ ...01-21-code-for-america-brigade-congress.md | 104 ++++++ .../content/blog/2018-02-05-site-relaunch.md | 90 +++++ .../2018-03-07-project-investment-fund.md | 90 +++++ .../blog/2018-04-11-open-data-day-recap.md | 68 ++++ .../2018-04-27-in-loving-memory-of-sanat.md | 75 +++++ .../content/blog/2018-04-30-sba-case-study.md | 308 ++++++++++++++++++ .../content/blog/2018-06-14-mapping-tools.md | 46 +++ .../astro/src/content/blog/2018-08-04-odsc.md | 43 +++ ...rogram-at-national-day-of-civic-hacking.md | 65 ++++ ...s-a-voter-guide-to-help-fight-fake-news.md | 73 +++++ ...n-inc-domestic-violence-referral-center.md | 36 ++ ...ata-day-2019-community-driven-hackathon.md | 50 +++ ...-san-franciscos-underserved-communities.md | 73 +++++ ...e-for-san-francisco-2019-year-in-review.md | 64 ++++ packages/astro/src/content/config.ts | 14 + packages/astro/src/pages/blog.astro | 13 +- packages/astro/src/pages/blog/[slug].astro | 25 ++ packages/astro/tsconfig.json | 1 + 40 files changed, 2159 insertions(+), 1 deletion(-) create mode 100644 packages/astro/src/content/blog/2014-07-26-sf-open-referral.md create mode 100644 packages/astro/src/content/blog/2014-09-05-localfreeweb.md create mode 100644 packages/astro/src/content/blog/2014-10-22-how-our-campaign-data-visualization-app-can-help-y.md create mode 100644 packages/astro/src/content/blog/2014-10-22-speaker-matt-arana-on-accessibility.md create mode 100644 packages/astro/src/content/blog/2015-01-07-sf-brigade-hosts-citycampsf.md create mode 100644 packages/astro/src/content/blog/2015-01-18-announcing-c4sf-sponsor-microsoft.md create mode 100644 packages/astro/src/content/blog/2015-04-09-celebrating-the-life-of-our-friend-ethan-lang.md create mode 100644 packages/astro/src/content/blog/2015-04-29-april-12-2015-campaign-finance-summit.md create mode 100644 packages/astro/src/content/blog/2015-06-01-text-if-youre-happy-or-not-says-tech-volunteer-gro.md create mode 100644 packages/astro/src/content/blog/2016-03-24-codeacross-sf-2016.md create mode 100644 packages/astro/src/content/blog/2016-04-09-meet-sf-brigade-members.md create mode 100644 packages/astro/src/content/blog/2016-04-26-sf-brigades-data-science-working-group.md create mode 100644 packages/astro/src/content/blog/2016-08-15-vr-data-visualization-a-new-way-to-address-communi.md create mode 100644 packages/astro/src/content/blog/2016-11-17-announcing-c4sf-sponsor-segment.md create mode 100644 packages/astro/src/content/blog/2016-11-23-community-forum-week-1.md create mode 100644 packages/astro/src/content/blog/2017-02-09-project-investment-fund-launches.md create mode 100644 packages/astro/src/content/blog/2017-02-16-2016-sf-brigade-year-in-review.md create mode 100644 packages/astro/src/content/blog/2017-03-17-searching-for-equity-in-a-sea-of-data.md create mode 100644 packages/astro/src/content/blog/2017-05-28-spring-2017-project-demo-night.md create mode 100644 packages/astro/src/content/blog/2017-07-31-noob-a-first-timers-account-of-code-for-san-franci.md create mode 100644 packages/astro/src/content/blog/2017-10-17-national-day-of-civic-hacking-2017-how-we-learned-.md create mode 100644 packages/astro/src/content/blog/2017-11-25-designers-geeks-provoke-sf-crime-data.md create mode 100644 packages/astro/src/content/blog/2018-01-21-code-for-america-brigade-congress.md create mode 100644 packages/astro/src/content/blog/2018-02-05-site-relaunch.md create mode 100644 packages/astro/src/content/blog/2018-03-07-project-investment-fund.md create mode 100644 packages/astro/src/content/blog/2018-04-11-open-data-day-recap.md create mode 100644 packages/astro/src/content/blog/2018-04-27-in-loving-memory-of-sanat.md create mode 100644 packages/astro/src/content/blog/2018-04-30-sba-case-study.md create mode 100644 packages/astro/src/content/blog/2018-06-14-mapping-tools.md create mode 100644 packages/astro/src/content/blog/2018-08-04-odsc.md create mode 100644 packages/astro/src/content/blog/2018-09-16-dev-mission-and-c4sf-launch-fellowship-program-at-national-day-of-civic-hacking.md create mode 100644 packages/astro/src/content/blog/2018-10-20-code-for-san-francisco-community-creates-a-voter-guide-to-help-fight-fake-news.md create mode 100644 packages/astro/src/content/blog/2019-04-17-w-o-m-a-n-inc-domestic-violence-referral-center.md create mode 100644 packages/astro/src/content/blog/2019-05-01-open-data-day-2019-community-driven-hackathon.md create mode 100644 packages/astro/src/content/blog/2019-06-22-introducing-civc-tech-to-san-franciscos-underserved-communities.md create mode 100644 packages/astro/src/content/blog/2020-02-06-code-for-san-francisco-2019-year-in-review.md create mode 100644 packages/astro/src/content/config.ts create mode 100644 packages/astro/src/pages/blog/[slug].astro diff --git a/packages/astro/src/content/blog/2014-07-26-sf-open-referral.md b/packages/astro/src/content/blog/2014-07-26-sf-open-referral.md new file mode 100644 index 0000000..5217fd2 --- /dev/null +++ b/packages/astro/src/content/blog/2014-07-26-sf-open-referral.md @@ -0,0 +1,42 @@ +--- +authors: +- jason_lally +date: '2014-07-26' +published: true +title: SF Open Referral +description: 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. SF Open Referral improves social service delivery through shared, open resource data. +--- + +## The Problem + +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. + +1. Individuals seeking help are left to navigate confusing lists of resources that may or may not lead them to what they need. +2. Social workers and other intermediaries must master multiple lists of competing information, making it hard to connect their clients to the relevant help. +3. Community development initiatives are left paying for new research to understand the state of their community resources. + +### Data - Many Locations and Formats + +**Where does the data live?** + +- internal contract management systems +- printed resource guides +- administration databases +- internal PDFs +- the minds of single employees + +## Opportunity - Data should be free! + +We see an opportunity to free this data so it can be: + +- published in a standardized format +- easily accessible +- easy to update +- a precedent for modern referral systems + +And ultimately: **Deliver consistent, high quality social services to those in need!** + +## Additional Resources + +- Getting started guide +- Mid-market pilot description diff --git a/packages/astro/src/content/blog/2014-09-05-localfreeweb.md b/packages/astro/src/content/blog/2014-09-05-localfreeweb.md new file mode 100644 index 0000000..4f5c991 --- /dev/null +++ b/packages/astro/src/content/blog/2014-09-05-localfreeweb.md @@ -0,0 +1,72 @@ +--- +authors: +- joseph_tanigawa +date: '2014-09-05' +published: true +image: "LocalFreeWebText.jpg" +image_alt: Photo of LocalFreeWeb text message +title: LocalFreeWeb +description: 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. LocalFreeWeb makes it so all you need is a cell phone. +--- + +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? + +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. + +On August 15, Code for San Francisco, a Code for America brigade, launched LocalFreeWeb 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. + + + +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. + +### How it works (summary) +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. + +{% include image.html name="LocalFreeWebText.jpg" alt="Photo of LocalFreeWeb text message" %} + +### How it works (technical details) + +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. + +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. + +We use the Google Spreadsheet API to record the date, time, and Stop ID of each valid request made to the app. + +If you’re curious, here’s the application backend code and frontend website code. + +### Technical Challenges + +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. + +## Next steps! + +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. + +### Plans include: +- Distributing more flyers +- Printing stickers +- Creating partnerships with digital literacy organizations +- Finalizing a partnership with Clear Channel Media +- More outreach to relevant community organizations +- Converting the text messaging app into at least Spanish, Mandarin & Tagalog +- Partnering with MTA to have signs permanently placed at Wave Shelters explaining how to use our service +- Acquiring funding for a shortcode ie; 311 for finding 'Free Internet' locations + + +### How you can help + +1. Go to LocalFreeWeb.org and let us know how/if it works! +2. Use the form on the website to add more locations +3. Print out fliers and post them near bus stops in your neighborhood +4. Check out the code and make suggestions +5. Use the open source code to build a version for your city (and tell us about it!) + +If you’re in San Francisco and interested in helping build LocalFreeWeb, we’d love to see you at Code for San Francisco civic hack nights. + +### We need people with all types of skills: +- Writing +- Marketing +- Business Development +- Research +- Code (Python, JavaScript, HTML, CSS) +- User Experience and User Interface Designers diff --git a/packages/astro/src/content/blog/2014-10-22-how-our-campaign-data-visualization-app-can-help-y.md b/packages/astro/src/content/blog/2014-10-22-how-our-campaign-data-visualization-app-can-help-y.md new file mode 100644 index 0000000..41f145d --- /dev/null +++ b/packages/astro/src/content/blog/2014-10-22-how-our-campaign-data-visualization-app-can-help-y.md @@ -0,0 +1,36 @@ +--- +published: true +title: How our Campaign Data Visualization App Can Help YOU This Election +description: 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? Check out our visualizations of campaign financing. +authors: +- jay_rooney +image: image.png +image_alt: Visualization +tags: + - Data Visualization +--- + +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? + +To visualize that: + +{% include image.html name="visualization.png" alt="Supervisor Farrell 2014 Campaign Contributions" %} + +We got that data in a matter of seconds from the San Francisco Brigade’s Campaign Data Visualization App. You can, too. + +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: + +* a lot of expertise +* a lot of time + +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. + +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. + +At the very least, make an informed decision before you cast your ballot! + +Some other interesting findings: + +[Coming Soon] + +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/](http://election-sf.herokuapp.com/). diff --git a/packages/astro/src/content/blog/2014-10-22-speaker-matt-arana-on-accessibility.md b/packages/astro/src/content/blog/2014-10-22-speaker-matt-arana-on-accessibility.md new file mode 100644 index 0000000..7fba968 --- /dev/null +++ b/packages/astro/src/content/blog/2014-10-22-speaker-matt-arana-on-accessibility.md @@ -0,0 +1,43 @@ +--- +authors: +- laura_paajanen +date: '2014-10-22' +published: true +title: 'Speaker: Matt Arana on Accessibility' +description: "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." +image: speaker.jpg +image_alt: Matt Arana +--- + +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. + +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. + +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. + +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. + +Top Ten Things that affect sites and applications +* Missing or incorrect names +* Navigation doesn’t follow visual design +* Skipping over visible items or speaking invisible items +* Not grouping visually related elements +* Element type (link, button, etc.) is missing or incorrect +* The state of buttons is not described +* Headings are missing or used inconsistently +* Missing “hints” that provide context +* Missing closed captions or caption controls +* Low contrast + +{% include image.html name="TopTenA11yIssues.jpg" alt="Top Ten A11y Issues" caption="Matt’s list of ten common issues that affect accessibility on websites and applications" %} + +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. + +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: +A - must do items to be accessible, such as alt text, form fields, and keyboard access +AA - general requirement/ strongly recommended - for example, providing focus +AAA - nice to haves that aren’t as common, such as more restrictive color contrast rules + +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. + +Thanks, for the intro to A11y, Matt! diff --git a/packages/astro/src/content/blog/2015-01-07-sf-brigade-hosts-citycampsf.md b/packages/astro/src/content/blog/2015-01-07-sf-brigade-hosts-citycampsf.md new file mode 100644 index 0000000..c113142 --- /dev/null +++ b/packages/astro/src/content/blog/2015-01-07-sf-brigade-hosts-citycampsf.md @@ -0,0 +1,41 @@ +--- +authors: +- lawrence_grodeska +date: '2015-01-07' +published: true +title: SF Brigade Hosts CityCampSF +description: "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." +--- + +**[Register now!](https://www.eventbrite.com/e/citycampsf-2015-tickets-13722252627)** + +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. + +[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. + +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: + +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 +2. Create or maintain patterns for local government transparency and effective local governance using the Web as a platform +3. Foster communities of practice and advocacy on the role of information and open data in cities +4. Create outcomes that participants will act upon after the event is over + +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. + +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.” + +Confirmed speakers include: + +- Supervisor Mark Farrell, City and County of San Francisco +- Jay Nath, Chief Innovation Officer, SF Mayor’s Office of Civic Innovation +- Joy Bonaguro, Chief Data Office, SF Mayor’s Office +- Francis Zamora & Kristin Hogan, SF Dept. of Emergency Management +- Dan Parham, Founder, Neighborland +- Joaquín Torres, Deputy Director, OEWD + +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. + +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. + +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/. +civictech democracy san francisco citycamp diff --git a/packages/astro/src/content/blog/2015-01-18-announcing-c4sf-sponsor-microsoft.md b/packages/astro/src/content/blog/2015-01-18-announcing-c4sf-sponsor-microsoft.md new file mode 100644 index 0000000..7925701 --- /dev/null +++ b/packages/astro/src/content/blog/2015-01-18-announcing-c4sf-sponsor-microsoft.md @@ -0,0 +1,22 @@ +--- +authors: +- jesse_biroscak +date: '2015-01-18' +published: true +title: 'Announcing C4SF sponsor: Microsoft' +image: microsoft.png +img_alt: Microsoft +description: As Captain of Code for San Francisco, it is my pleasure to announce [Microsoft](http://www.microsoftbayarea.com/) as the Brigade's first sponsor. +--- + +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. + +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. + +As Captain of Code for San Francisco, it is my pleasure to announce [Microsoft](http://www.microsoftbayarea.com/) as the Brigade's first sponsor. + +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. + +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. + +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. diff --git a/packages/astro/src/content/blog/2015-04-09-celebrating-the-life-of-our-friend-ethan-lang.md b/packages/astro/src/content/blog/2015-04-09-celebrating-the-life-of-our-friend-ethan-lang.md new file mode 100644 index 0000000..6b64cea --- /dev/null +++ b/packages/astro/src/content/blog/2015-04-09-celebrating-the-life-of-our-friend-ethan-lang.md @@ -0,0 +1,30 @@ +--- +authors: +- laura_childs +date: '2015-04-09' +published: true +title: Celebrating the Life of Our Friend, Ethan Lang +description: 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. +image: EthanProfessional.jpg +image_alt: Photo of Ethan +--- + +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. + +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. + +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. + +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. + +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. + +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. + +[Video of Ethan's dancing](https://vimeo.com/120393051) + +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. + +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. + +{% include image.html name="EthanAbroad.jpg" alt="Photo of Ethan" %} diff --git a/packages/astro/src/content/blog/2015-04-29-april-12-2015-campaign-finance-summit.md b/packages/astro/src/content/blog/2015-04-29-april-12-2015-campaign-finance-summit.md new file mode 100644 index 0000000..d36ae47 --- /dev/null +++ b/packages/astro/src/content/blog/2015-04-29-april-12-2015-campaign-finance-summit.md @@ -0,0 +1,68 @@ +--- +authors: +- asha_john +- allen_meyer +date: '2015-04-29' +published: true +title: 'April 12, 2015: Campaign Finance Summit' +description: 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. +image: panel.jpg +image_alt: Journalist panel on campaign finance +--- + +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. + +## Is writing a check free speech? + +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](https://www.opensecrets.org/outsidespending/summ.php). + +#### Shouldn’t we know who is writing the checks for whom? The answer is far more complicated. + +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. + +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. + + +## Super PACS + +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: + +* [Buckley v. Valeo](http://en.wikipedia.org/wiki/Buckley_v._Valeo) +* [Citizens United v. FEC](http://en.wikipedia.org/wiki/Citizens_United_v._FEC) + +{% include youtube.html id="Y6Sg24MQ-aE" caption="Video of Jesse's talk" %} + +[**Jesse's Slides**](https://docs.google.com/presentation/d/1Q4jqA4XrRBPIaw_lCW3lBJJy7MRLp93OVSChNoa1vPc/edit?usp=sharing) + + +## Dark Money. It’s as creepy as it sounds. + +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. + +{% include youtube.html id="I5SXO4ZMakE" caption="Video of Jay's talk" %} + +## Phil +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. + +{% include youtube.html id="1Z7GFfDOg1E" caption="Video of Phillip's talk" %} + +## Oliver +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. + +{% include youtube.html id="ue_JO5rES0c" caption="Video of Oliver's talk" %} + +## Journalist Panel +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. + +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. + +{% include youtube.html id="9fz1WD-BvaY" caption="Video of Journalist Panel" %} + +## Miriam +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. + +{% include youtube.html id="yz7oJWLbzUY" caption="Video of Miriam's talk" %} + +[**Miriam's Slides**](https://docs.google.com/presentation/d/1n3MTLB2FJKCPfeHauY0Gsl5r9AonMMoVHPB_Ggotjl4/edit?usp=sharing) + +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. diff --git a/packages/astro/src/content/blog/2015-06-01-text-if-youre-happy-or-not-says-tech-volunteer-gro.md b/packages/astro/src/content/blog/2015-06-01-text-if-youre-happy-or-not-says-tech-volunteer-gro.md new file mode 100644 index 0000000..cca760a --- /dev/null +++ b/packages/astro/src/content/blog/2015-06-01-text-if-youre-happy-or-not-says-tech-volunteer-gro.md @@ -0,0 +1,25 @@ +--- +authors: +- julio_feliciano +- seunghee_eu +date: '2015-06-01' +published: true +title: "Text if you\u2019re happy or not says tech volunteer group" +--- + +FOR IMMEDIATE RELEASE + +## TEXT IF YOU’RE HAPPY OR NOT SAYS TECH VOLUNTEER GROUP +Civic Hackers Help Communities by Developing Technology for Good + +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. + +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. + +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. + +“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!” + +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. + +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/ diff --git a/packages/astro/src/content/blog/2016-03-24-codeacross-sf-2016.md b/packages/astro/src/content/blog/2016-03-24-codeacross-sf-2016.md new file mode 100644 index 0000000..80ea2ef --- /dev/null +++ b/packages/astro/src/content/blog/2016-03-24-codeacross-sf-2016.md @@ -0,0 +1,71 @@ +--- +authors: +- vedrana_trbusic +date: '2016-03-24' +published: true +title: CodeAcross SF 2016 +image: first.png +image_alt: Opening presentation +description: On March 5 we organized the third annual CodeAcross in San Francisco. The event, which was hosted at Microsoft Reactor, was part of a nationwide effort around the world to bring together people who want to collaborate to make their cities better. And collaborate we did! Nearly 100 people joined us to work on projects that benefit the community and San Francisco. +--- + +## CodeAcross SF Brings together techies, nonprofits, and Bay Area residents to make San Francisco better + +On March 5 we organized the third annual CodeAcross in San Francisco. The event, which was hosted at Microsoft Reactor, was part of a nationwide effort around the world to bring together people who want to collaborate to make their cities better. And collaborate we did! Nearly 100 people joined us to work on projects that benefit the community and San Francisco. + +This year’s focus was on Open Data. Our goal was to bring together Bay Area residents and cater to different backgrounds, not only technologists. The participants could choose between three different tracks, and there was plenty to do for everybody. It was really inspiring to see so much passion for making a difference in one place! + + +Here is a brief overview of the participating projects. + +One of the biggest groups at CodeAcross was the Data Science Working Group, a group that was recently formed at Code for SF. They worked on three projects: data visualization of energy consumption and greenhouse gas emissions (SF Environment Benchmark project), mapping 311 data, and an interactive map of San Francisco parks. Sanat Moningi, who leads the SF Environment Benchmark project, shared some interesting findings that they discovered by using the City’s datasets. For example, did you know that residential buildings score well on energy efficiency but not hotels? Or that any facility that handles food is (somewhat expected) energy inefficient? Moningi is really excited about this because he’s seen other projects in New York and Philadelphia that used visualizations to convince the property managers to make better choices. “Nobody is willing to make changes but when they see what the building is doing and how they compare to others, they are more likely to do it,” said Moningi. There are some exciting potential uses for this project and the team will be meeting with the City to present their findings. Ultimately the Data Science Working Group is hoping to work together with building managers to see how they can help them become more energy efficient. +Check out the interview with the team below. + + + + +BrigadeHub was building an alpha of the new Code for SF website that will consolidate the efforts of maintaining a brigade website into a single location and allow non-developer brigade leadership members to update content as needed. With the help of a few more people that joined their team at CodeAcross, they were able to make a lot of progress and get closer to where they want to be. + +{% include image.html name="IMG_2066.jpg" alt="Brigadehub team" %} + +pdfhook is a new project that started at Civic Hack Night a few days before CodeAcross. Their goal is to build a Python web application for converting PDF forms into PDF-filling APIs. The idea for the project came from seeing that a lot of government agencies are still using paper forms, which can be time-consuming and inefficient. Check out their github for more info on the progress they’ve made so far and watch this video to learn about how the idea for the project came about. + + + + +CivicMakers, a knowledge-sharing platform for the civic innovation community, is a project that started at Code for San Francisco. Their mission is to accelerate the capacity of communities, organizations and institutions to rapidly deploy collaborative solutions by growing a network of people, resources and recipes for public good projects. At CodeAcross the team was able to make usability tweaks, fix their prototype and talk to project leads to get more info on how to develop their value proposition. [Check out their knowledge-sharing prototype and find out how it can help your project](https://app.civicmakers.com). + +While most projects originated at Code for SF hack nights, we were also very happy to see a couple of independent projects that liked our mission and decided to join us at CodeAcross. One such project was Gyver – a community based giving app that makes donating things to your neighbors easier while at the same time helping you decide who to donate to. The idea is simple – the more stuff you give to others, the higher you rank and the more likely you are to get an item from somebody. Jezmin and her team came to CodeAcross with the intention to build and test the Facebook sign-up feature and we were excited to see how much progress they were able to get done in just one day. We look forward to seeing this app launch! + +{% include image.html name="IMG_2084.jpg" alt="Gyver photo" %} +{% include image.html name="gyver.png" alt="Gyver team working" %} + +One of San Francisco’s darker sides is its growing homeless population. In the city where a lot of people have been priced out of the housing market, the daily reality of many who lost their homes is in stark contrast with the prosperous tech-mecca reputation that the city has. Darcel Jackson, who many of you have met at hack night, led an inspiring conversation on changing the face of homelessness and plans to start a dialogue between homeless communities and the people that can help. Darcel, who has experienced homelessness himself, knows first-hand what a difference having access to trusted resources can make for somebody who is in that situation. He has an idea for an app that will help the homeless find resources and collect data that can be useful to the homeless community. To turn his idea into reality he founded Sheltertech, a nonprofit with a mission to bring tech to low-income and no-income individuals. They are currently working on two projects: bringing wi-fi to homeless shelters and developing AskDarcel, an app that is meant for both the homeless as well as those who want to help them with services they might need. The team is already talking with the City of San Francisco about helping them distribute the app. This is a great example of how tech, community and local government can work together to build products that can make a real difference. + +Watch Sheltertech team talk about their goals in this video. + + + +As you can see a lot of teams came to CodeAcross to improve upon their existing projects but we are really excited about the fact that there are also four projects that actually got started at CodeAcross! Code for SF's new Research Group created an Open Impact Challenge that led to a new project team working to prevent violence against women. The group generated so much interest that by the end of the day they decided to split up and work on three different ideas: + +* Violet. An app that enables victims to communicate their experience anonymously so they will know that they are not alone. + +* You’ve got friends. The second idea focuses on people who will be there for the victims. The basic premise is to enable the enablers. They are working on an app that asks people if they have ever been a victim of violence. The app then reports to that person’s friends so they can learn how to be better supporters and pledge to listen and be there for the victim. + +* Walk together. The third group will focus on prevention and the fact that a lot women report feeling unsafe around BART stations. They will work on a solution that will give women the opportunity to walk together in groups to discourage predators. + +If you have experience working with victims of violence, the group would love to hear from you and get your input on their ideas. + + + + +Another project that was born at CodeAcross actually started as an unconference discussion. The group gathered together in a passionate debate about healthcare and decided to launch a project that will build tools to connect people with health care services. We’re excited about having this group at our future hack nights where they will continue working on this idea. If you are a subject expert in this field and want to get involved, let us know! + +Watch this video to find out more about their plans. + + + + +We’re really proud of the amazing progress that was made at this year’s CodeAcross SF and of all the awesome ideas and discussions. A special thank you goes to our sponsors who made this event possible: Microsoft, our main sponsor, for hosting the event and for their generous support; Braintree for sponsoring our yummy lunch; and Exygy for their donation that helped us organize the event. + +Stay tuned for more posts about what Code for SF teams are up to next week! Like what you read and want to get involved? Come join us at our weekly hack night and talk to team leads about joining their projects! diff --git a/packages/astro/src/content/blog/2016-04-09-meet-sf-brigade-members.md b/packages/astro/src/content/blog/2016-04-09-meet-sf-brigade-members.md new file mode 100644 index 0000000..6085aeb --- /dev/null +++ b/packages/astro/src/content/blog/2016-04-09-meet-sf-brigade-members.md @@ -0,0 +1,50 @@ +--- +authors: +- vedrana_trbusic +date: '2016-04-09' +published: true +title: Meet SF Brigade Members +description: "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!" +image: headshot.jpg +image_alt: April Steed head shot +--- + +## Meet April Steed, a passionate UX designer and Lighten Project Lead + +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! + +**Tell me a little bit about yourself, what is your professional background and your interests?** + +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. + +**What are you passionate about?** + +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. + +**How did you get involved with Code for San Francisco and how long have you been a part of the SF Brigade?** + +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. + +**What do you like best about being a member?** + +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. + +**Tell me about Lighten, what is the project hoping to achieve?** + +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. + +**How long have you been working on this project? How many people are in the team?** + +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. + +**What is the next big thing for this project?** + +Funding! Once we get a functional prototype off the ground we will be looking for financial support to turn it into a real product. + +**What might (someone) be surprised to know about you?** + +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. + +**What do you do when you aren’t volunteering?** + +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! diff --git a/packages/astro/src/content/blog/2016-04-26-sf-brigades-data-science-working-group.md b/packages/astro/src/content/blog/2016-04-26-sf-brigades-data-science-working-group.md new file mode 100644 index 0000000..8515f39 --- /dev/null +++ b/packages/astro/src/content/blog/2016-04-26-sf-brigades-data-science-working-group.md @@ -0,0 +1,40 @@ +--- +authors: +- kasia_rachuta +date: '2016-04-26' +published: true +title: SF Brigade's Data Science Working Group +image: IMG_1846.jpg +image_alt: data science working group hard at work +description: | + The past couple of months have been an exciting time for the Data Science + Group Working Group (DWSG). The group, which started in January, brings together + both professional data scientists and data enthusiasts hoping to improve their skills + whilst making an impact. DSWG uses the wealth of open source data made available + by SF Open Data and others to work on both its own projects as well as to support + other civic hackers at Code for San Francisco. By providing data science expertise + they’ve become a central resource to the broader SF Brigade. +--- + +# SF Brigade's Data Science Working Group + +The past couple of months have been an exciting time for the Data Science +Group Working Group (DWSG). The group, which started in January, brings together +both professional data scientists and data enthusiasts hoping to improve their skills +whilst making an impact. DSWG uses the wealth of open source data made available +by SF Open Data and others to work on both its own projects as well as to support +other civic hackers at Code for San Francisco. By providing data science expertise +they’ve become a central resource to the broader SF Brigade. + +One project that the DSWG is currently working on is SF Open Data’s 311 case +dataset to understand what agencies tend to respond first, which neighborhoods +are served first and what their most common problems are. Another example is +ImpactGov, a project aiming to measure the impact of government- funded +activities in the Bay Area. The goal of the SF Environment Benchmark project is +to visualize building energy consumption and greenhouse gas emissions in order +to encourage building owners and managers to make changes. Sounds interesting? +If you want to join our projects, have a problem that big data can help you +solve, or want to use or develop your data skills and make a difference, come +see us! We meet every Wednesday during Civic Hack Night. + +Stay tuned to learn more about our findings! diff --git a/packages/astro/src/content/blog/2016-08-15-vr-data-visualization-a-new-way-to-address-communi.md b/packages/astro/src/content/blog/2016-08-15-vr-data-visualization-a-new-way-to-address-communi.md new file mode 100644 index 0000000..5fd8064 --- /dev/null +++ b/packages/astro/src/content/blog/2016-08-15-vr-data-visualization-a-new-way-to-address-communi.md @@ -0,0 +1,21 @@ +--- +authors: +- allen_meyer +date: '2016-08-15' +published: true +title: "VR Data Visualization: A New Way to Address Community Issues" +description: 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. +--- + +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. + +Brigade member David Rust-Smith created [a map](http://davidrs.github.io/sfhip-map/) which shows the density of establishments selling alcohol to be consumed offsite in the Mission, Bay and Tenderloin neighborhoods. + +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. + +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). + + +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). + +Team Members: Steven Meloan, [Allen Meyer](http://allenmeyerdesign.com/), Peter Thompson, Seung-hee Eu, David Rust-Smith, Nick Breen diff --git a/packages/astro/src/content/blog/2016-11-17-announcing-c4sf-sponsor-segment.md b/packages/astro/src/content/blog/2016-11-17-announcing-c4sf-sponsor-segment.md new file mode 100644 index 0000000..817a487 --- /dev/null +++ b/packages/astro/src/content/blog/2016-11-17-announcing-c4sf-sponsor-segment.md @@ -0,0 +1,26 @@ +--- +authors: +- allen_meyer +date: '2016-11-17' +published: true +title: 'Announcing C4SF sponsor: Segment' +description: Code for San Francisco is happy to announce that Segment has contributed $5,047 to support our efforts. A huge, sincere thank you to Segment! +image: segment.png +image_alt: Segment Logo +redirect_from: +- /blog/post/Announcing-C4SF-sponsor-Segment + +--- + +### Code for San Francisco is happy to announce that Segment has contributed $5,047 to support our efforts. A huge, sincere thank you to Segment! + +[Segment](https://segment.com)’s generosity will make it possible to continue serving meals to everyone who volunteers at our weekly hack nights. Code for San Francisco is an all volunteer organization working to use technology to improve the city. Our hack nights run on donated time, donated talent, donated space, and donated meals. + +> Code for San Francisco really embodies some of the values Segment holds dear, Karma and Drive. We are grateful to have the opportunity to help with such an awesome cause and very excited to see what types of projects will come out of this endeavour. +> - Laylee Asgari, with Segment + +Code for San Francisco would like to give a special shoutout to the brigade’s veteran, [Oz Haven](https://github.com/therebelrobot), for his efforts in reaching out to Segment. A big thank you to Oz for continuing and maintaining Code for San Francisco’s drive to build socially impactful technology. + +Segment’s substantial support will cover about a fourth of our fundraising goal for 2016. Code for San Francisco looks forward to using this donation to fuel our volunteers efforts to build civic tech projects. Our brigade has several active projects and is welcoming new volunteers every week. + +Segment’s donation shows how far a well placed donation can go. If you or your company are looking for ways to contribute to Code for San Francisco, drop us a line at [fundraising@codeforsanfrancisco.org](mailto:fundraising@codeforsanfrancisco.org) diff --git a/packages/astro/src/content/blog/2016-11-23-community-forum-week-1.md b/packages/astro/src/content/blog/2016-11-23-community-forum-week-1.md new file mode 100644 index 0000000..ddca7c8 --- /dev/null +++ b/packages/astro/src/content/blog/2016-11-23-community-forum-week-1.md @@ -0,0 +1,61 @@ +--- +authors: +- oz_ozwald +date: '2016-11-23' +published: true +title: Community Forum - Week 1 +description: "We at Code for San Francisco have one goal: to positively impact our community by means of the skills at our disposal, which for many of us means leveraging various technologies to meet a community need. This goal can be often distilled into two words: *civic tech*. And here in the Bay Area we have at our disposal a seemingly endless supply of technologists: developers, designers, data scientists, product managers, and many many more. I think in our city, as a collective community dedicated to civic tech, we do not have a lack of engagement on the latter half of that phrase. The former half, however, the *civic* in *civic tech*, is the real tricky part to get right. If the past election has taught us nothing, it has taught us that civic engagement with our communities is not something that can be underestimated nor ignored." +image: wordcloud.png +image_alt: Wordcloud of community forum responses +--- + +We at Code for San Francisco have one goal: to positively impact our community by means of the skills at our disposal, which for many of us means leveraging various technologies to meet a community need. This goal can be often distilled into two words: *civic tech*. And here in the Bay Area we have at our disposal a seemingly endless supply of technologists: developers, designers, data scientists, product managers, and many many more. I think in our city, as a collective community dedicated to civic tech, we do not have a lack of engagement on the latter half of that phrase. The former half, however, the *civic* in *civic tech*, is the real tricky part to get right. If the past election has taught us nothing, it has taught us that civic engagement with our communities is not something that can be underestimated nor ignored. + +Toward that end, the leadership team at Code for San Francisco has decided to pilot a new section of our hack night: The Weekly Community Forum. Inspired by our sister brigade in Chicago, [Chi Hack Night](https://chihacknight.org/events/2016/11/15/post-election-community-feedback-session.html) and their [Community feedback session](https://docs.google.com/document/d/1LcB5wI43AM7sKwJ7FGJhTVJosH6egBcKKkioSgfoG4w/edit#) held last week, this guided brainstorming session, recurring every Wednesday, is designed to help our volunteers learn and target the specific civic needs of our unique community. One civic-centric question is asked every week, and answers are solicited from our attendees, written anonymously on post-it notes, and collected for review and discussion. It not only helps us as a leadership team to target the focused of our members, but it helps us all get out of it normal routine and into the #civictech mindset for the evening. + +We ran this for the first time last Wednesday with encouraging results. The question posed received a lot of diverse responses, and showed a lot how our members are feeling right now. We'll be changing these questions every week, each building on the last, to help inform our technology decisions. + +So without further ado, I give you this week's responses. + +#### This week's question + +**How are you feeling about your community and government right now?** + +##### Summary + +The general feeling that came out of these responses was a feeling if fear and uncertainty with our government and community on a national level. We also received a lot of positive responses about our state and local government. + +##### Raw Responses + +* The government is not working for the people at the federal level +* Government: fear and loathing, Community: hopeful, please +* SF is great +* Tenderloin is stinky +* This government does not represent the interests of the diverse community, only a reactionary subset of the people +* Inspired by my community and disappointed in my government +* Bad +* Disjointed. I feel that unlike prior movements the current one for change has little direction. There are many heads but no clear voice +* I feel disconnected from my community due to being so busy with work +* Devastated. Betrayed. Determined to fight. +* Locally, I am proud of our city and state government. But dismayed by the recent changes to our federal government and baffled by the choices of 60 million voters +* Scared for good people who are actually a net gain to the USA +* Scared +* White people are the worst +* I feel disenfranchised by my government as an academic and I feel disappointed in how unsafe my community is getting +* Meh +* Local level = {heart emoji} {star emoji} - Federal = {sad face emoji} {angry face emoji} +* Terrified, want to flee, etc. {sad face emoji} +* City government is slow +* Disappointed +* Wait and see +* Community good, no complaints, well run -- Government, terrified +* Feeling alright! +* Feel like more can be done to make it efficient to work for people +* Great!! We’re gonna have a real man in the White House +* Again - we’re gonna get our country back!! + +#### Where to go from here? + +This week we'll be discussing a new question based off the previous: **There is a lot of anger and resentment in our community and America today. How can we as a community of civic technologists direct it towards positive action?** Stay tuned for more updates as the forum progresses! + +{% include image.html name="cfa.jpg" alt="CFA HQ Wall Quotes" style="max-height: 400px" %} diff --git a/packages/astro/src/content/blog/2017-02-09-project-investment-fund-launches.md b/packages/astro/src/content/blog/2017-02-09-project-investment-fund-launches.md new file mode 100644 index 0000000..6d307be --- /dev/null +++ b/packages/astro/src/content/blog/2017-02-09-project-investment-fund-launches.md @@ -0,0 +1,39 @@ +--- +authors: +- mike_bridge +- jesse_szwedko +date: '2017-02-09' +published: true +title: Project Investment Fund Launches +description: Code for San Francisco is happy to announce we are launching a new partnership with Microsoft to support the work of our volunteers. Beginning today, projects organized through Code for San Francisco can apply to access up to $2,000 to spend on anything they need to build stronger solutions; e.g. web hosting, training, data processing, user testing, or more! We are excited to begin this new experiment and look forward to seeing where it leads. +image: logo.png +image_alt: Project investment fund banner +--- + +## Project Investment Fund Launches Today + +Code for San Francisco is happy to announce we are launching a new partnership with Microsoft to support the work of our volunteers. Beginning today, projects organized through Code for San Francisco can apply to access up to $2,000 to spend on anything they need to build stronger solutions; e.g. web hosting, training, data processing, user testing, or more! We are excited to begin this new experiment and look forward to seeing where it leads. + +The goal of the Project Investment Fund goal is to enable projects to reach their milestones,and to design projects beyond what can be built for free. Microsoft suggested this idea late in 2016 and Code for San Francisco is glad to be the first brigade to pilot this new funding program. + +If you think your project could benefit from financial support, please read on! + +## The details +Applications to this program will be accepted triannually. The first application window opens on February 8th and closes on March 8th. + +We are only taking online applications. We have created an [application template](https://docs.google.com/document/d/1HLT9ytbFtmnw6UAk2j0JI5vgmIY3_m2o88bsgcpnlbo/edit) to provide project teams with a clear idea of what to prepare before submitting an application. Applications can be submitted through the google form [available here.](https://docs.google.com/forms/d/e/1FAIpQLSd_TMVKYkSH4X0kssx-9_VnOkuUgH-wwdYwCoKLSTeCiOzx3w/viewform?c=0&w=1) + +**The review panel will complete their selections from the first round and notify projects on March 29th.** + +Projects interested in applying should review the [Program Overview](https://docs.google.com/document/d/1C2kpmXhWzd_4kauy3sZhCWKBtHHKfv4fTHICjgMIMjc/edit#heading=h.6qz9rr99awes) for more details on how applications will be evaluated and the process of participating in the Project Investment Fund. Feel free to [contact the core team](mail-to:coreteam@codeforsanfrancisco.org) with any questions or concerns on this new program; we welcome your input. + +We believe our volunteers will come up with creative and valuable ways to use this resource. Microsoft has long been a key sponsor of Code for San Francisco and the Project Investment Fund is possible entirely through their support. Thank you again, Microsoft! + +**Program timeline (for first round):** + +- **2017-02-08** Application window opens +- **2017-03-08** Application window closes +- **2017-03-29** Selections completed & projects notified +- **2017-04-01** Grant term begins +- **2017-06-01** Grant check-in +- **2017-08-01** Grant term ends; final check-in diff --git a/packages/astro/src/content/blog/2017-02-16-2016-sf-brigade-year-in-review.md b/packages/astro/src/content/blog/2017-02-16-2016-sf-brigade-year-in-review.md new file mode 100644 index 0000000..560a7ae --- /dev/null +++ b/packages/astro/src/content/blog/2017-02-16-2016-sf-brigade-year-in-review.md @@ -0,0 +1,72 @@ +--- +authors: +- mike_bridge +- allen_meyer +date: '2017-02-16' +published: true +title: 2016 SF Brigade Year in Review +description: '2016 was defined by broken politics. [Dumpster fire](http://www.americandialect.org/dumpster-fire-is-2016-american-dialect-society-word-of-the-year) was chosen as “best representing the public discourse and preoccupations of the past year.” While the world of politics looks completely dysfunctional, Code for San Francisco folks continue to meet in growing numbers, committed to the ideal that our politics and government can work better for people by leveraging technology.' +image: codeforsanfrancisco.org +image_alt: San Francisco with Code for San Francisco logo +--- + +2016 was defined by broken politics. [Dumpster fire](http://www.americandialect.org/dumpster-fire-is-2016-american-dialect-society-word-of-the-year) was chosen as “best representing the public discourse and preoccupations of the past year.” While the world of politics looks completely dysfunctional, Code for San Francisco folks continue to meet in growing numbers, committed to the ideal that our politics and government can work better for people by leveraging technology. + +San Francisco is uniquely positioned to demonstrate how much better government can serve the people when human centered design, open data, and technology are leveraged in smart ways. The [open source](https://opensource.org/history) movement began a Caltrain away in Palo Alto. There is no shortage of programmers, engineers, designers, and civic minded volunteers here. The city has been a leader on open data and continues to make significant progress on making [more data](https://datasf.org/) accessible. Our brigade believes open source tools make it possible to build such solutions for free. + +C4SF has created a safe place for a thriving community of of folks interested in improving civic life. On any given Wednesday, 50 to 70 people gather, with a core group helping to anchor projects and welcome and guide new attendees. San Francisco faces challenges on many fronts: homelessness, housing, crime, transportation, the environment, education, and civic engagement to name a few. The brigade has projects addressing many of these issues. The Brigade has also become an important place for recent boot camps grads and folks just moving to the Bay Area looking to network and meet others. So, what have we been up to? Read on! + +# Projects and/or Success Stories + +### Data Science Working Group +This is the team within C4SF that focuses on solving social good problems with data science which provides useful insights into real world problem. [The Data Science Working Group](http://datascience.codeforsanfrancisco.org/) Co-captains Sanat and Jude have led their teams on some solid wins: +* [SF Homelessness Analysis](http://datascience.codeforsanfrancisco.org/project/sf-homelessness-analysis/) examining what programs and services have the best outcomes in partnership with Community Technology Alliance. +* [OpenJustice](https://openjustice.doj.ca.gov/) project using inferential statistics to [answer prompts](http://datascience.codeforsanfrancisco.org/project/ca-doj-openjustice-hypothesis-testing-predictive-modeling/) on criminal and juvenile justice for the California Department of Justice. +* [SF Environment Benchmark](http://datascience.codeforsanfrancisco.org/project/sf-environment-benchmark/) dashboard enabling Department of the Environment to show building managers how their properties are doing on greenhouse emissions. +* [Friends of the Urban Forest](https://www.fuf.net/) built a [visualization tool](http://datascience.codeforsanfrancisco.org/project/friends-of-the-urban-forest-street-tree-viz/) of street tree data. Working on a tree planting recommendation system. +* [Anomaly Detection Tool for Hazardous Material Incidents](https://judec.shinyapps.io/shiny_anomaly_detection/) won the Bayes Hack competition. Currently being developed into a Universal Civic Anomaly Detector. + +### Adopt a Drain +The brainchild of Jesse Biroscak, Jean Walsh, and Jason Lally in late 2015, the [Adopt-a-Drain SF](https://adoptadrain.sfwater.org/) project came into its own in the fall of 2016 including: being adopted by the SF Public Utilities Commission as an official SF Water project; a number of volunteer events; and [some local press](http://hoodline.com/2016/11/the-great-leaf-catcher-puuurple-drainnnn-san-francisco-residents-adopt-drains-to-prevent-flooding). Originally a fork of Code for America's [Adopt-a-Hydrant](https://www.codeforamerica.org/products/adopt-a-hydrant/), Code for San Francisco brigade members made a number of adjustments and added a number of features to make the project a success. To date almost 1400 drains have been adopted in San Francisco! + +### Brigadehub +Masterminded by core team member, Oz Haven, this easy to deploy data portal and CMS for volunteer coding organizations could be become a model Brigade platform. [See it in action]( http://codeforsanfrancisco.org/). + +### Lighten +[Web-based tool](http://codeforsanfrancisco.org/projects/Lighten) for social service providers to store, update, and exchange social services information through a universal standard. We are solving the problem of quickly getting the right help to the right people, by making it easy to get the right information to the right people. + +### [SF Crime Data](http://codeforsanfrancisco.org/projects/SF-Crime-Data) +A radial search tool designed to facilitate SFPD responses to requests from colleges for information they need to comply with the Jeanne Clery Act. The project team recently presented at Apps4Change. + +### [SFS Book](http://codeforsanfrancisco.org/projects/SFS-Book) +Interactive guide of resources for survivors of sexual assault allowing [SFWAR](http://sfwar.org/about.html) volunteers to maintain a public and up-to-date directory. + +### [UX Research Group](http://codeforsanfrancisco.org/projects/User-Research-Working-Group) +Applies user-centered design, design thinking methods, and lots of post-it notes to improve C4SF projects and the Brigade experience. Developing a system for matching new volunteers with active projects based on skills, interests, & needs with the goal of incorporating this tool into Brigadehub. + +### WeVote +C4SF has been a welcoming and supportive space for We Vote USA to build their [social network for voters]( http://www.wevoteusa.org/) + +# 2016 Events +In addition to our weekly hack night, C4Sf hosts and supports several large events throughout the year. +* Demo Day: We held two dog and pony shows this year, it’s a great way to share with the community work in progress and the pressure of presenting helps teams refine their projects. [Video from our May event]( https://www.youtube.com/playlist?list=PLtMOjE6qfBWjnI_Vm80ZKoT4Ap5drMCfv) +* National Day of Civic Hacking: Weekend long event in June hosted by communities throughout the world. +* CodeAcross: Code for America nodes across the world host civic hacking events, timed to coincide with International Open Data Day + +# Partnerships +* UCSF Data Visualization: collaborated on a community research project that examined how alcohol impacts low income neighborhoods in San Francisco, resulting in a [data visualization](http://codeforsanfrancisco.org/blog/post/VR-Data-Visualization-A-New-Way-to-Address-Community-Issues) that will be used to help community advocates in neighborhood planning. +* Water & Justice Panel + +### And now, a word for our sponsors +[Microsoft](https://blogs.microsoft.com/bayarea/) has been a long standing supporting partner to C4SF. In addition we added several new sponsor in 2016 including Segment, DataBricks, SalesForce and Braintree. + +# What’s in store for 2017 + +### Project Investment Fund +This may be the biggest news for the Brigade this year. MicroSoft is sponsoring $10,000 in direct grants to cover expenses on approved projects. Projects are invited to submit proposals for funding, to learn more, [check out the blog post](http://codeforsanfrancisco.org/blog/post/Project-Investment-Fund-Launches) + +### Major Hacking Events for 2017 +* Open Data Day Saturday March 4 at Microsoft Reactor in SOMA. +* National Day of Civic Hacking + +The civic tech movement is entering a phase of transition, much of the early enthusiasm and idealism is still there, but also a lot of uncertainty of what happens next. Making government data open and available to citizens has never been more important. Code for America’s mission of people making government work for the people by the people is a powerful vision. How will the volunteers of the SF Brigade rise to this challenge? We need your help to develop our current projects and your contributions for ideas on what to build next. Join us at our next hack night, meet some awesome people, and get involved! diff --git a/packages/astro/src/content/blog/2017-03-17-searching-for-equity-in-a-sea-of-data.md b/packages/astro/src/content/blog/2017-03-17-searching-for-equity-in-a-sea-of-data.md new file mode 100644 index 0000000..878a6b8 --- /dev/null +++ b/packages/astro/src/content/blog/2017-03-17-searching-for-equity-in-a-sea-of-data.md @@ -0,0 +1,45 @@ +--- +authors: +- allen_meyer +date: '2017-03-17' +published: true +title: Searching for Equity in a Sea of Data +description: Open Data Day is an annual celebration of open data all over the world. This year, it was celebrated on Saturday, March 4. Code for San Francisco hosted its Open Data Day event at the [Microsoft Reactor](http://microsoftreactor.com/venue/sf-reactor/) and launched the day with an inspiring keynote by Carla Mays. [@CarlaMays](https://twitter.com/CarlaMays) is a veteran of the Civic tech movement and this was a bit of a homecoming for her having attended Open Data Day’s previous incarnation, Code Across in 2013. Carla discussed how open data could be used to create a more equitable and inclusive society. "We've really got to start to see the faces of this change, it's got to be more inclusive and we've got to work as a team." She also stressed that “We have to address biases that are baked into data sets.” The key to inclusiveness and equity is what Carla tagged #WithNot4Design. +image: carla.jpg +image_alt: Carla Mays +--- + +Open Data Day is an annual celebration of open data all over the world. This year, it was celebrated on Saturday, March 4. Code for San Francisco hosted its Open Data Day event at the [Microsoft Reactor](http://microsoftreactor.com/venue/sf-reactor/) and launched the day with an inspiring keynote by Carla Mays. [@CarlaMays](https://twitter.com/CarlaMays) is a veteran of the Civic tech movement and this was a bit of a homecoming for her having attended Open Data Day’s previous incarnation, Code Across in 2013. Carla discussed how open data could be used to create a more equitable and inclusive society. "We've really got to start to see the faces of this change, it's got to be more inclusive and we've got to work as a team." She also stressed that “We have to address biases that are baked into data sets.” The key to inclusiveness and equity is what Carla tagged #WithNot4Design. + +> "Communities must be included in the design and development process for technology to truly reflect their needs and priorities." + +### Public Administration for the 21st century +Carla Mays was followed by Damian Ortellado @daortellado from the California Department of Justice who described the work being done on [OpenJustice.doj.ca.gov](https://openjustice.doj.ca.gov/) Open Justice is an effort to bring transparency to criminal justice data. A example of this transparency effort are the data stories featured on the site. Damian stressed that: +> “It’s not just about sharing data, but giving it context and doing our due diligence to explain to the public what this data means.” + +Members from the Brigade’s Data Science Working Group have been working with Open Justice on juvenile justice data with prompts from CA DOJ on issues such as: Which counties/agencies arrest African American juveniles at a statistically significantly higher rate than that of other counties/agencies? For the same criminal offense, are particular ethnic juvenile groups more likely to be treated with harsher consequences by law enforcement? + +{% include image.html name="dswg.jpg" alt="Open Justice presentation" %} + +The Data Science Working Group is an example of how the civic tech volunteer movement is maturing. The Group is a dedicated team working on complex social issues in partnership with a government agency. The civic tech movement is the testing place for innovative ideas in government technology and also for training the next generation of what Carla dubbed “public administration for the 21st century”. + +### Microsoft: Committed to the Civic Tech Community +Microsoft has been a continued supporter and host for several Code for San Francisco events from Code Across to the National Day of Civic Hacking. "For years, Microsoft has partnered with Code for America brigades across the country to promote civic innovation for all,’ said Scott Mauvais, Director of Technology and Civic Engagement for Microsoft. ‘Events like Code Across and the National Day of Civic Hacking help bring innovative solutions directly to the people. We're honored to support these initiatives and to help Code for San Francisco inspire progress through ingenuity." + +### It Was a Busy Day +Data driven social justice is a great ideal, but what does that look like in practical terms for a volunteer lead organization like Code for San Francisco? Here’s a look at some of the projects worked on C4SF’s Open Data Day event. Some are new projects, others are ongoing Brigade projects. + +How might we lower San francisco rents? Good question. The five member team of Ryan, Jeremie, James, Jaoyi and Wendy decided to address the supply issue. After diving into [data.sfgov.org](https://data.sfgov.org/) they discovered that San Francisco has 166,068 off-street parking lot and parking garage spaces. Designer Tim McCormick has addressed affordable housing with modular, mobile housing that fits in parking spaces. The team decided to initially target single, transient professionals, but this concept could work for San Francisco’s large homeless population as well. + +**Open Justice:** Working with the California Department of Justice to create an interactive visualization of the juvenile arrest process: Inform the public of the process and show the data of where juveniles fall in the process and what might affect those outcomes. Does geography or race have an effect on juvenile justice outcomes? + +**Small Business Administration and underserved communities:** Working from prompts from the SBA the team examine loan data for trends to make recommendations on how to address neighborhoods that are underserved or are over-served by the SBA. The team looked at data from the SBA that looks at small business loan data from 1990 to current.The team used the event to begin their research into the data and outline next steps on this on going project. [project github](https://github.com/sfbrigade/datasci-sba) + +**Econozen: Consumer Activism?** Let’s make an app for that! The Econozen team is looking to quantify consumer behaviour to align beliefs with consumer behavior. They analyzed data from the SF ethics commission to that tracks who donates to what. + +**Planning Department: Housing pipeline:** Modeling data for the San Francisco Housing Action coalition addressing questions about the data set from the Planning Department. Data modeling and UI continues. + +**SF Department of Environment:** Building a dashboard for building managers to understand where there buildings are in relation to similar types in regards to greenhouse gas emissions and energy consumption. This is a dedicated project with the SF Department of Environment. + +### What’s Next? +Several of the projects that folks worked on at Open Data Day are on-going projects at our weekly, Wednesday night hack nights. Open Data Day was a continuation of the amazing volunteering collaboration between the civic tech community, government and the private sector that Code for San Francisco has fostered for several years. Check out some of our open projects and come lend a hand: [CodeForSanfrancisco.org/Projects](http://codeforsanfrancisco.org/projects) diff --git a/packages/astro/src/content/blog/2017-05-28-spring-2017-project-demo-night.md b/packages/astro/src/content/blog/2017-05-28-spring-2017-project-demo-night.md new file mode 100644 index 0000000..56daed8 --- /dev/null +++ b/packages/astro/src/content/blog/2017-05-28-spring-2017-project-demo-night.md @@ -0,0 +1,14 @@ +--- +authors: +- allen_meyer +date: '2017-05-28' +published: true +title: Spring 2017 Project Demo Night +description: There’s nothing like a Demo Night to help a team focus their presentation and take stock of where they are in their project. It is also a great opportunity to recruit for their project and show the rest of the Brigade the work they’ve been up to. Eleven teams presented their projects and the progress the teams are making is inspiring. The project teams are working on a wide range of issues facing San Francisco residents from helping the homeless to analyzing juvenile justice sentencing disparities. Check out the videos from the teams presentations and join us every Wednesday night hacking for San Francisco! +image: prep.jpg +image_alt: Teams huddling on demo night +--- + +There’s nothing like a Demo Night to help a team focus their presentation and take stock of where they are in their project. It is also a great opportunity to recruit for their project and show the rest of the Brigade the work they’ve been up to. Eleven teams presented their projects and the progress the teams are making is inspiring. The project teams are working on a wide range of issues facing San Francisco residents from helping the homeless to analyzing juvenile justice sentencing disparities. Check out the videos from the teams presentations and join us every Wednesday night hacking for San Francisco! + +{% include youtube_playlist.html id="PLtMOjE6qfBWj-MBoxuhfACOxGKS6IKLYm" %} diff --git a/packages/astro/src/content/blog/2017-07-31-noob-a-first-timers-account-of-code-for-san-franci.md b/packages/astro/src/content/blog/2017-07-31-noob-a-first-timers-account-of-code-for-san-franci.md new file mode 100644 index 0000000..cc2b12d --- /dev/null +++ b/packages/astro/src/content/blog/2017-07-31-noob-a-first-timers-account-of-code-for-san-franci.md @@ -0,0 +1,36 @@ +--- +authors: +- lauren_harriman +date: '2017-07-31' +published: true +title: 'NOOB: A First Timer''s Account of Code for San Francisco Civic Hack Night' +image: sign.jpg +image_alt: Entrance to Code for San Francisco Hack Night +description: My very first [Code for America Civic Hack Night](https://www.codeforamerica.org/blog/2013/07/24/brigade-101-how-to-hack-night/) began with pressing a buzzer to gain entry to the Code for America building in San Francisco's SoMa district. A very welcoming receptionist greeted me and noticed right away that I was new. He pointed me towards the red name tags for newbies (as opposed to the blue name tags for returning attendees). The color coding of newbies and repeat attendees, plus the use of name tags in the first place, made it so much easier to strike up conversations with people and quickly learn why each attendee decided to spend their Wednesday night volunteering. +--- + +## Color Hacking and Welcome + +My very first [Code for America Civic Hack Night](https://www.codeforamerica.org/blog/2013/07/24/brigade-101-how-to-hack-night/) began with pressing a buzzer to gain entry to the Code for America building in San Francisco's SoMa district. A very welcoming receptionist greeted me and noticed right away that I was new. He pointed me towards the red name tags for newbies (as opposed to the blue name tags for returning attendees). The color coding of newbies and repeat attendees, plus the use of name tags in the first place, made it so much easier to strike up conversations with people and quickly learn why each attendee decided to spend their Wednesday night volunteering. + +## Welcome Remarks & Project Pitches + +After the perfect amount of chitchat time, attendees were all encouraged to move into the Ben Franklin room where a presentation awaited us. We learned that [Code for America](https://www.codeforamerica.org/what), as a whole, is [politically neutral](https://www.codeforamerica.org/how/#principles) (my personal favorite Hack Night fact). Included in the presentation was space for people to pitch new project ideas. Ambassadors from four teams pitched their projects by essentially just telling us the name of the project and what the team was currently working on. The four projects pitched were: [CA Dept. of Justice OpenJustice Project](http://codeforsanfrancisco.org/projects/California-OpenJustice), [We Vote](http://codeforsanfrancisco.org/projects/We-Vote), [SF Fire Risk Project](http://codeforsanfrancisco.org/projects/SF-Fire-Risk-Project), [SF Crime Data](http://codeforsanfrancisco.org/projects/SF-Crime-Data), and [Hack for Cities](http://codeforsanfrancisco.org/projects/Hack-for-Cities). The ambassadors asked for data scientists, data visualization developers, and other specific skillsets. + +## N00b Orientation + +Next came the presentation just for n00bs (newbies)! The new hacker orientation included everyone introducing themselves by stating their names, their background, their favorite snack, and their skills they hoped to contribute (in most cases, a list of their tech stack skills). The presenter did an awesome job of encouraging newbies to take on anything they found interesting, and he mentioned the [code of conduct](https://docs.google.com/document/d/1ZV_iy2CeDlTu13Af9-_5NyOC8SVP9mpxIBn0g1e_S-Q) that results in a safe space and incredibly supportive community for all. I was especially impressed by how excited the presenter was with my skillset (especially considering I mostly pitched myself as someone who could write, as an attorney, and as someone with basic HTML and Python skills). I happened to find the [Data Science Working Group](http://datascience.codeforsanfrancisco.org/) interesting, specifically the [CA DoJ: OpenJustice Hypothesis Testing & Predictive Modeling](http://datascience.codeforsanfrancisco.org/project/ca-doj-openjustice-hypothesis-testing-predictive-modeling/) project. The presenter then personally escorted me, along with a few other newbies who were interested in the project, over to the group's ambassador. + +## Hacking Away + +To be honest, I did not write a single line of code during my first Code for America Civic Hack Night. The [Data Science Working Group](http://datascience.codeforsanfrancisco.org/our-mission/) was interested in the prospect of someone writing a [blog](http://codeforsanfrancisco.org/blog) post, and I readily accepted the assignment. One of the members of the team suggested that I write a post on what it's like to be a newcomer, so I ran with that. More importantly, I recognized that I could be especially useful in helping fellow newbies identify [projects](http://datascience.codeforsanfrancisco.org/current-projects/) that would showcase their unique talents. + +## Important Takeaways + +Code for SF recognizes that it takes [more than developers](http://datascience.codeforsanfrancisco.org/become-a-brigade-partner/) for a project to succeed. One of the stated goals of [the Data Science Working Group at Code for San Francisco](https://github.com/sfbrigade/data-science-wg) is to set up each project such that every single person currently working on a project could leave the project and new people could easily come in and pick up where the previous team members left off. Code for SF is actively seeking people who are interested in working on fundraising, project management, and marketing. Most importantly, if you want to try your hand at a new skill, Code for SF is the perfect environment to get your feet wet! + +## Call to Action + +Are you a tech project manager? Are you a designer? Are you a recent coding bootcamp grad? Are you a recent business school grad? Do you have any desire to try your hand at one of the many things I mentioned in this blog post? Even if you would just like to learn more about Code for SF, we would love to have you join us. We are actively seeking partners, both financial and the kind that can introduce us to people who might have interesting projects for us to work on. Join us on [Meetup](https://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/), and stop by Civic Hack Night at Code for America in San Francisco's SoMa district on Wednesday nights from 6-10pm. + +Thanks to Lauren Harriman for this first person account: [@lmmharriman](https://twitter.com/lmmharriman) diff --git a/packages/astro/src/content/blog/2017-10-17-national-day-of-civic-hacking-2017-how-we-learned-.md b/packages/astro/src/content/blog/2017-10-17-national-day-of-civic-hacking-2017-how-we-learned-.md new file mode 100644 index 0000000..6d0a1e8 --- /dev/null +++ b/packages/astro/src/content/blog/2017-10-17-national-day-of-civic-hacking-2017-how-we-learned-.md @@ -0,0 +1,44 @@ +--- +authors: +- allen_meyer +- celia_moreno +date: '2017-10-17' +published: true +title: 'National Day of Civic Hacking 2017: How We Learned to Deal with Disasters' +description: Live long enough in California and you might experience an earthquake, wildfire, catastrophic flood from winter rains, extreme drought, and those are just the natural events. C4SF decided to do something a little different this year for NDoCH. Rather than a two or three day event, we decided to do a one-day deeper exploration of resilience and disaster preparedness in our neighborhoods. +image: team.jpg +image_alt: Run Your Resilientville Team Photo +--- + +Live long enough in California and you might experience an earthquake, wildfire, catastrophic flood from winter rains, extreme drought, and those are just the natural events. C4SF decided to do something a little different this year for NDoCH. Rather than a two or three day event, we decided to do a one-day deeper exploration of resilience and disaster preparedness in our neighborhoods. + +To create something that is truly relevant to the communities we hope to engage, we decided to immerse ourselves in human centered design principles. We asked [Megan Goering](https://www.linkedin.com/in/megangoering/) to give us a deep dive in human centered design. Megan is an Google veteran and now works as a international consultant, +>“My work scales the tools, methods, and creative practices of the tech world in San Francisco / Silicon Valley to those empowering their communities to address humanity's most pressing problems.” + +Perfect. With Megan’s insight, we hoped to be able to better understand how we might address the real world needs of neighborhood emergency responders. It wouldn’t be a human centered design session if we didn’t come up with a “how might we” statement. Ours is: “How might we empower people in times of stress through a shared asset map.” + +With the aim of inspiring our resiliency project, Code for San Francisco brought practitioners from the [Neighborhood Empowerment Network](http://empowersf.org/) and the [Department of Emergency Management's SF72](http://sf72.org) to show attendees how preparedness works in SF today. Megan had equipped attendees with human centered design tools to help prototype civic tech solutions around resiliency. Now it was time to get serious. + +## Not your usual hackathon + +Daniel Homsey, Director of the Neighborhood Empowerment Network, enthusiastically guided attendees off their feet and into working mode. He began the tabletop exercise abruptly and with little notice, to imagine San Francisco had just been hit by a 7.1 magnitude earthquake to simulate an actual disaster. He gave instructions on creating and utilizing the HUB Incident Command System (ICS) which was practiced by completing the exercise, “Run Your Resilientville.” + +During the exercise, participants split into three groups. One person in each group was designated the leader, who then assigned other members a ‘logistics’ or ‘operations’ role. The tabletop map was an aerial view of Ocean Avenue in the Ocean View/Merced Heights/Ingleside district of San Francisco. + +Participants were first asked to identify the community’s vulnerable populations and how they would be impacted by a large magnitude earthquake. Facilitated by the leader, the group addressed three categories: central shelter, shelter in place, and mass feeding. The ‘operations’ team identified needs in terms of supplies, food/water, power, and medical supplies for the designated number of people per category. The ‘logistics’ team located where and addressed how these things could be attained. Throughout the exercise, the group recognized gaps within each category. + +{% include image.html name="meagan.jpg" alt="table top mapping team" %} + +Once the table top exercise was complete, each individual group debriefed their maps. The leaders of the incident command system presented their performance gaps and potential for improvement. The consensus was that everyone could benefit from being more prepared and having a system in place for times of stress. + +Now it was time for our challenge from Daniel: sustainably empower people in times of stress with a shared asset map. The concept is an asset map that shows where community leaders can find resources in case of emergency, and to map those assets before the emergency strikes. Assets such as generators, medical supplies and grocery store managers that will distribute refrigerated food rather than have it go bad if power is down. The final part of the day was spent with attendees split into three groups to consider how to collect, exchange and visualize data related to asset mapping. + +The outcome of the day was a deeper understanding of how to apply human centered design skills to a real world challenge. The Brigade is continuing the work in our Resiliency Mapping project with a core group meeting every Wednesday night at Hack Night. Join us, we could use your help. + +In addition to joining us at hack night to contribute skills to a more resilient SF, here are some things you should do today to increase personal, family and community resiliency: + +* Register for AlertSF by texting your zipcode to 888-777; you’ll receive public safety alerts +* Review your emergency kit supplies and visit [SF72.org](http://sf72.org) to find out what you’re missing + * Make a commitment to purchase/make each of those missing items +* Have a conversation with your friends and family about your disaster plan; pick a place to meet and an out-of-state point of contact to check in with if something should happen +* [Sign up to host a Neighborfest block party](http://empowersf.org/neighborfest) through the Neighborhood Empowerment Network diff --git a/packages/astro/src/content/blog/2017-11-25-designers-geeks-provoke-sf-crime-data.md b/packages/astro/src/content/blog/2017-11-25-designers-geeks-provoke-sf-crime-data.md new file mode 100644 index 0000000..edf1451 --- /dev/null +++ b/packages/astro/src/content/blog/2017-11-25-designers-geeks-provoke-sf-crime-data.md @@ -0,0 +1,24 @@ +--- +authors: +- mike_bridge +date: '2017-11-25' +published: true +title: Designers & Geeks Provoke SF Crime Data +image: screenshot.jpg +image_alt: SF Crime Data Screenshot +description: 'Code for San Francisco first collaboration with Designers & Geeks leads off Provoke, a new event series.' +--- + +On October 12th we met at DesignMap’s offices with 75 others to witness the culmination of a partnership between Code for San Francisco and Designers & Geeks to rethink the user experience of SF Crime Data as part of Provoke, a new event series from [Designers & Geeks](https://designersandgeeks.com/) focused on the redesign of city projects. + +The vision of [sfcrimedata.org](http://sfcrimedata.org/) is to satisfy crime reporting needs for SFPD, and other interested parties including watchdog groups, universities, and civic hackers, while ensuring an easily maintainable product. + +There is a clear need for skilled designers and product managers among our brigade’s projects. By showcasing how one designer working with a project can make an impactful contribution in a short period, we hope Provoke will help designers better understand our vision for open source civic tech projects. The concept for the Provoke events grew out of talks with Joe Robinson, the organizer of Designers + Geeks, about how best to foster collaboration between San Francisco’s design community and Code for San Francisco’s civic hackers. + +The event kicked off with pizza and conversation, as all good tech meetups do, but at 7:30 we moved into the main event of the evening, a presentation by designer Joey Golaw, who worked with the SF Crime Data team to redesign the user experience of [sfcrimedata.org](http://sfcrimedata.org/). He spent the first half of the presentation making a compelling case about why designers should get involved in civic technology projects by highlighting the current lack of expertise in this area and the impact that is possible by redesigning the government to be more user friendly. + +Joey moved on to discuss how he approached rethinking the experience of [sfcrimedata.org](http://sfcrimedata.org/) by applying human centered design principles. He started the process by surveying the existing landscape of smilar tools, as well as reading interviews of crime statisticians to get a better feel for the end-users of this application. He moved through two iterations of possibilities for the UI. The first broke out the UI based on the two groups of users, crime statisticians and the general public, which were viewed as having different needs to meet by visiting the site. It was later realized that they could reunify the UI to serve both user groups and create a cleaner experience. + +Paul Hennings, the project lead for SF Crime Data, then offered a few thoughts about the redesign and talked about next steps for the project. He plans to take the designs proposed by Joey and break them down into actionable issues for brigade volunteers to hack on in the coming weeks. + +Want to be part of the [sfcrimedata.org](http://sfcrimedata.org/) team? Stop by an upcoming hack night. diff --git a/packages/astro/src/content/blog/2018-01-21-code-for-america-brigade-congress.md b/packages/astro/src/content/blog/2018-01-21-code-for-america-brigade-congress.md new file mode 100644 index 0000000..16a8e9d --- /dev/null +++ b/packages/astro/src/content/blog/2018-01-21-code-for-america-brigade-congress.md @@ -0,0 +1,104 @@ +--- +authors: +- jude_calvillo +- kenny_durrell +- vincent_la +date: '2018-01-21' +published: true +title: Code for America Brigade Congress +image: congress.jpg +image_alt: Brigade Congress Attendees +description: The report back from Code for San Franicisco's Brigade contingent to the 2017 Code for America Brigade Congress. +--- + +Each member of the SF Brigade contingent (Ryan, Vincent, Jude and I) had a distinct itinerary and a few different modes +of transit en route to the Brigade Congress this October but we finally convened at the opening ceremonies, aptly held +in a server bay near downtown Philadelphia. + +We quickly realized that we were in the company of kindred citizens and government officials. What started as a hum of +conversation between friends new and old quickly became a roar. Everyone was so excited to find fellow impassioned +technologists and designers that the hosts of the event were hard-pressed to get us to quiet down for a welcome speech. + +Amongst the 200-300 attendees were people from every corner of the U.S. and from every level of government. We had +in-depth conversations with brigade members from Maine to Hawaii as well as with heads of service design, county data +scientists and countless other civil servants. If not for Ryan and my presentation scheduled first thing the next +morning, I think I might very well still be at the event. It was an incredible way to start the Congress and a portent +of the enthusiastic and productive weekend to come. + +The next day, after breakfast, a few icebreakers and inspiring remarks from the founder of Code for America and the +Congress organizing committee, came the lightning talks. These highlighted successful projects from a few of the +Brigade, including excellent work on promoting diversity in brigades from fellow Bay Area contingent OpenOakland as well +as a talk by Ryan and I about the [SF Fire Risk prediction model](https://github.com/sfbrigade/datasci-firerisk) that we +and a number of contributors had worked on over the past year. + +{% include image.html name="fire-risk.jpg" alt="Fire Risk Project Presentation" %} + +Then came the unconference voting. I’d never been to an unconference before, but to summarize for the uninitiated: there +is no set agenda. + +{% include image.html name="unconference.jpg" alt="Unconference Voting" %} + +Participants typically submit session ideas ahead of time, although some people had bursts of inspiration and added +theirs to the fray that morning. Every session proposer goes up on stage and gives a quick pitch on the content of their +session to the entire conference. The proposals are then printed on separate pieces of paper, with a short description, +and taped to a wall. Then the attendees clamor to vote for those they’d like to attend by adding stickers to the paper +proposals. After the quick voting process, the session with the most votes get reviewed by the conference committee and +if there are any overlapping ideas, these sessions are combined and run by co-leaders. Needless to say, it feels very +democratic and participatory! + +There were 8 sessions over the course of the two days, and Jude and Vincent, of our Code for SF Brigade, were +immediately thrust into leading a session on data science principles and best practices as learned from their work with +the Data Science Working Group. This unconference session was really awesome. The room was packed; there was a ton of +interest in data science out there. We took this opportunity to share what has worked for Code for SF and learn from +other brigades what worked for them. It was really awesome to see all the energy and passion for data science out there. +A few key highlights from that session: + +* Even a “Data Science” Working Group is not strictly data science. With successful projects, The majority of the work + is establishing strong partnerships with civic agencies and making sure you’re working towards solving real problems. + Furthermore, there’s a ton of work to write good documentation, build solid infrastructure, and establish ETL + processes. Fancy “modeling” is only 10% of the battle. +* A key question that came up was “how do we establish those partnerships with government”. At SF, sometimes we take it + for granted that we live in an area where data science is such a hot button issue. For example, we asked everyone who + lived in a city with a “Chief Data Officer” to raise their hands, and the majority of the room could not. This even + further exemplified that it’s important for us to engage with our civic partners and make sure we can communicate the + value of data science to solve real world problems +* The Data Science Hippocratic Oath: one extremely intriguing idea that came out was forming some kind of data science + “hippocratic oath”. Just as doctors need to take this oath to ensure that they complete their duties with the highest + ethical standard, we as data scientists, should also ensure that we take the proper steps to uphold our ethical + standards and promote transparency in our work. Furthermore, we should devote our work to help the People and not be + swayed by special interests. + +Outside of their session, highlights of the first day included: + +* An engaging discussion about methods and tools to aid redeployability of Code for America projects +* Strategies employed by brigades to effectively engage with city governments and agencies. Takeaways: meet government + employees on their turf and demonstrate value with smaller, successful projects +* A session on how to raise revenue for the brigade and various business models that other brigades have employed. In + particular Beta NYC talked about their business models that included teaching Excel classes to city officials, + partnering with local universities to take on graduate students in exchange for resources, and finding sponsors for + large events. + +The first day concluded with dinner and then carried over to a local watering hole, where both the conversation and +drinks continued to flow. As the night wore on, many CfAers slowly peeled off and headed back to their hotel while +others rallied to keep the evening going. Let’s just say Code for America brigadiers know how to take over a dance floor +:) + +A half day of sessions the next morning, including a presentation about using hackathons as a method of increasing the +diversity and pool of CfA brigade hack night attendees as well as homeless & affordable housing, and we were at the +closing remarks. + +Jenn Pahlka, the founder of Code for America, spoke of the importance of our work and the necessity for us to continue +to hold government officials accountable for delivering equitable, open and user-friendly services to the citizens they +serve. As inspiring as her speech was, she emphasized that she was equally as inspired by seeing us working all across +the U.S. to make government work for the people. As she ended her speech, a quote displayed on the screen behind her. It +captured the weekend’s ethos quite well: + +> “Efficiency in government is a matter of social justice.” +{% include image.html name="jen.jpg" alt="Jen Pahlka Presenting" %} + +As the conference came to a close, we assembled the California Brigade representatives for one last picture. An important note that came out of this was that there’s a lot of really great work happening at Open Oakland, Code for San Jose, the newly formed Code for Berkeley, and as far north as Code for Sacramento! We all put together our brigade’s regular meeting times in this google spreadsheet so that we could all better coordinate with each other. As the new year rolls around we’re really hopeful that 2018 brings closer connection between all the California Brigades! + +{% include image.html name="congress.jpg" alt="Brigade Congress Attendees" %} + +And finally, here’s one last photo of everyone at Independence Hall in Philadelphia, where both the U.S. Declaration of +Independence and U.S. Constitution were signed! diff --git a/packages/astro/src/content/blog/2018-02-05-site-relaunch.md b/packages/astro/src/content/blog/2018-02-05-site-relaunch.md new file mode 100644 index 0000000..3b7fefb --- /dev/null +++ b/packages/astro/src/content/blog/2018-02-05-site-relaunch.md @@ -0,0 +1,90 @@ +--- +authors: +- jesse_szwedko +date: '2018-02-05' +published: true +title: Code for San Francisco Site Relaunch +image: return-to-jekyll.jpg +image_alt: The return to Jekyll +description: The return to Jekyll +--- + +If you are reading this post on [codeforsanfrancisco.org](codeforsanfrancisco.org), you may have noticed that it looks +a bit different than it has for the past two years. For the curious, this post explains why and how we've migrated from +the brigade-centric content management system (CMS), [BrigadeHub](https://brigadehub.github.io/), back to a static site +generator, [Jekyll](https://jekyllrb.com/) hosted, for now, on [Github Pages](https://pages.github.com/). + +# The end of an era + +[With BrigadeHub being retired late last year](https://brigadehub.github.io/), we needed to find a path forward for +hosting our site that would allow us to continue to make the changes we wanted to better convey to the world who we are +and what we do. Our primary desires were to: + +* Create additional static content describing the organization +* Create additional content for members such as an index of resources +* Have more control over the way events are displayed to make content, agendas and presentations, from each more + discoverable +* Create an index for our newly formed [open leadership councils]({{ "/about/leadership-council" | prepend: site.baseurl }}) + +But we didn't want to lose the raison d'être of BrigadeHub, namely, allowing non-technical users to edit content easily. + +# The path forward + +Starting with our [first leadership +council](https://docs.google.com/document/d/1dxn8MyPvPwPOgGe_wp_OI-3pJUu5kAvPiMclJszIZxo/edit#heading=h.4pnt8xk97gf3) in +October, it was decided that we would look at the current state of [static site generators](https://www.staticgen.com/) +and [headless CMSs](https://headlesscms.org/about/) to see if they could fit our needs. We felt that the static site +generators would give us a simple to maintain architucture and that the proliferation of headless CMSs would allow us to +maintain an interface for allowing non-technical users to help keep content on the site up-to-date. + +We defined our goals as: + +* Should be editable by non-technical users +* Should be simple in architecture to allow developers coming to the project to quickly contribute +* Should be extensible to allow things like the project matching app to be overlaid +* Should be open-source and free or cheap + +We started by [evaluating static site +generators](https://docs.google.com/document/d/1-biDkKqycqT0l0i-i4cvN3U0KstvnLBM6Sy6Yet7jGI/edit?ts=5a7b4479), +eventually settling on [Jekyll](https://jekyllrb.com/) as: + +* This is what we [previously used for codeforsanfrancisco.org](https://github.com/sfbrigade/sfbrigade.github.io) +* It is the one of the most popular static site generators meaning it has a well developed ecosystem and is a common + target for headless CMSs + +In advance of our [February project demo night]({{ "/events/2018-02-07-project-demo-night" | prepend: site.baseurl }}) +we officially launched the beta of the site to start collecting feedback. + +## Next steps + +Now that we have a live beta of the website, our next steps are: + +* collecting [ideas and issues](https://github.com/sfbrigade/codeforsanfrancisco.org/issues) +* work with the [UX research group](https://github.com/sfbrigade/research-group) to do some user research and ensure the + site is meeting our organizational and member goals +* evaluating headless CMSs to identify which will best suit our goal of allowing non-technical users to edit + content + +# Getting involved + +Excited about this path forward and want to contribute? Or do you have questions, feedback or concerns? Drop into +[#website](https://sfbrigade.slack.com/app_redirect?channel=website) on our Slack (if you aren't on Slack, you can +join via [c4sf.me/slack](http://c4sf.me/slack)) or drop us a line at +[hello@codeforsanfrancisco.org](mailto:hello@codeforsanfrancisco.org). + +If you want to be involved in the organization of the brigade and decisions like this? Drop by our next monthly [open +leadership councils]({{ "/about/leadership-council" | prepend: site.baseurl }}) on February 21st or join us in +[#brigade](https://sfbrigade.slack.com/app_redirect?channel=brigade) on Slack. + +# Special thanks + +I want to give special thanks to [Oz Haven](https://therebelrobot.com/) for his tireless efforts building and project +managing BrigadeHub. We would not be here today without his vision for expanding the the ability for brigade members to +contribute and curate content on our site. While BrigadeHub has been retired, this vision will carry on through our +work. + +Also thank you to [Jason Lally](http://jasonlally.com/) for heavily contributing to this discussion and for the +migration of projects to the new site. + +Lastly, thank you to [ChiHackNight](https://chihacknight.org/) for providing the initial template and site design which +we shamelessly replicated. diff --git a/packages/astro/src/content/blog/2018-03-07-project-investment-fund.md b/packages/astro/src/content/blog/2018-03-07-project-investment-fund.md new file mode 100644 index 0000000..1b03d70 --- /dev/null +++ b/packages/astro/src/content/blog/2018-03-07-project-investment-fund.md @@ -0,0 +1,90 @@ +--- +authors: +- chuck_temple +date: '2018-03-07' +published: true +title: Code for San Francisco Project Investment Fund Relaunch +image: logo.png +image_alt: Project investment fund banner +description: Project investment fund releaunch +--- + +# Code for San Francisco Project Investment Fund Program + +## Overview + +Microsoft has generously made up to $2000 available as grants to individual brigade projects to help them bridge +development gaps, increase impact, reach sustainability and to design projects beyond what can be built for free. + +## Project Guidelines + +Applicants are encouraged to demonstrate how their project meets all of the following guidelines: + +* Be an active project organized through Code for San Francisco, either in person as regular hack + night attendees, or online through the brigade’s GitHub repository. +* Be committed to working as an open source project. +* Be committed to the [Code for San Francisco Code of + Conduct](https://docs.google.com/document/d/1ZV_iy2CeDlTu13Af9-_5NyOC8SVP9mpxIBn0g1e_S-Q/edit). + +## Policy on Use of Funds + +Grantees may spend awarded funds on any resource directly related to project +development. All expenditures must be tracked. + +Examples (by no means exhaustive) of valid usages: + +* Events planning + * Space + * Food +* Software licensing +* Application hosting + * Cloud hosting, server space, API calls +* Promotion / advertising + * Google Adwords +* Office supplies +* Training +* Travel for conferences + +If you are unsure about possible grant usage, please email +[core-team@codeforsanfrancisco.org](mailto:core-team@codeforsanfrancisco.org). + +# Program Process + +* **March 7th:** Application window opens +* **April 4th:** Application window closes +* **April 25th:** Selections completed & projects notified +* **August 1st:** Grant term ends; final check-in + +# Accountability + +There will be a final check-in at the end of the grant period to report on how +well the team met their stated goals. + +# Evaluation Guidelines + +Applications will be reviewed by a panel consisting of one representative from +Microsoft, one representative from the San Francisco civic tech community, and +one representative from the City of San Francisco. The panel will award grants +to applications that best incorporate the following characteristics: + +* Scalability to other cities +* Ability to address identified civic needs and how those needs have been identified +* Clear plan for sustainability +* Incorporation of open data +* User research has been conducted +* Roadmap includes accessibility or inclusivity, community / user engagement or a clear plan to do so + +# Ready to Apply? + +* [Read This to Prepare](http://bit.ly/2F2jEVo) +* [Then Apply Here](http://bit.ly/2ozWGi8) + +# Questions? + +Please don't hesitate to reach out to the Code for San Francisco core team at +[core-team@codeforsanfrancisco.org](mailto:core-team@codeforsanfrancisco.org) +with any questions about the program. + +# FAQ + +Projects awarded a grant may apply again in later rounds diff --git a/packages/astro/src/content/blog/2018-04-11-open-data-day-recap.md b/packages/astro/src/content/blog/2018-04-11-open-data-day-recap.md new file mode 100644 index 0000000..83ad014 --- /dev/null +++ b/packages/astro/src/content/blog/2018-04-11-open-data-day-recap.md @@ -0,0 +1,68 @@ +--- +authors: +- allen_meyer +date: '2018-04-11' +published: true +title: Open Data Day 2018 Recap +image: sandra.jpg +image_alt: Sandra Zuniga +description: Open Data Day 2018 Recap +--- + +# Open Data Day 2018 + +Open Data Day is an annual celebration of open data all over the world. It is an opportunity to show the benefits of +open data and encourage the adoption of open data policies in government, business and civil society. This year, +Microsoft hosted Code for San Francisco’s Open Data Day event at their +[#ReactorSF](https://developer.microsoft.com/en-us/reactor/) developer community hub. The space had recently been +remodeled a to create a kind of developer-in-the-round presentation space. + +## Sandra Zuniga + +The keynote speaker was Sandra Zuniga, Director of the [Fix-It Team](http://sfmayor.org/neighborhoods/fix-it-team) for +the City of San Francisco [@fixitteamsf](http://twitter.com/fixitteamsf). Appointed by the late Mayor Ed Lee in 2016 to +lead his Safe and Clean Neighborhoods Promise Initiative, Sandra’s work brings both qualitative and quantitative data +together to make sound decisions to improve neighborhood quality of life. As Fix-It Director, Sandra works with seven +different City agencies to implement both quick and sustainable fixes in San Francisco, and has championed a number of +innovative projects and civic efforts directly informed by unique data analysis. + +## Lightning Talks + +Sandra was followed by two lightning talks from the open data community. + +### Samuel Estabook on Open Street Map + +{% include image.html name="osm.jpg" alt="Photo of Open Street Map slide" style="max-height: 400px" %} + +[Samuel](http://twitter.com/mapping_sam) provided different ways to participate in the largest open, crowd sourced mapping project: +[OpenStreetMap.org](http://OpenStreetMap.org) + +### Simon Willison on Datasette + +Every wanted to know how many ficus trees where in your neighborhood? In the city? Simon Willison from Datasette took +the list of trees in DataSF, which includes 190k line CSV file, and published an interface that makes the data +searchable: https://sf-tree-search.now.sh/ This is how [@simonw](http://twitter.com/simonw) did it: +https://github.com/simonw/sf-tree-search#how-i-built-this + +{% include image.html name="datasette.jpg" alt="Photo of Simon" style="max-height: 400px" %} + +### Unconference sessions + +Several workshops and unconference sessions filled out the rest of the data. Volunteers helped with the Open Data +census moving San Francisco to #1 on the census. [@synchronouscity](http://twitter.com/synchronouscity) led two sessions +exploring San Francisco’s open data portal and how to make use of the open data portal, including tips, tricks and +secrets. + +{% include image.html name="jason.jpg" alt="Photo of Jason's presentation" style="max-height: 400px" %} + +Brigade member, Sony Green, led a session on Data Visualization with VR. Discussions were held around using VR for +helping with PTSD, physical therapy, stroke victims and surgery with some cool demos including an Oculus visualization +of EEG data. + +{% include image.html name="vr.jpg" alt="Photo of VR presentation" style="max-height: 400px" %} + +## Wrap Up + +At the end of the day we came together over the remaining snacks to share what we learned and will take forward with us. +Unlike normal hackathons, where ideas and projects often fade away at the end of the weekend, we aim to continue this +great work during our [weekly civic hack nights]({{ "/events" | prepend: site.baseurl }}). diff --git a/packages/astro/src/content/blog/2018-04-27-in-loving-memory-of-sanat.md b/packages/astro/src/content/blog/2018-04-27-in-loving-memory-of-sanat.md new file mode 100644 index 0000000..60cebf7 --- /dev/null +++ b/packages/astro/src/content/blog/2018-04-27-in-loving-memory-of-sanat.md @@ -0,0 +1,75 @@ +--- +image: sanat.jpg +image_alt: Sanat Moningi +title: In Loving Memory of Sanat +description: 'A tribute to our dear friend Sanat Moningi, we miss you.' +pin_to_frontpage: false +image_list_only: true +--- + +It is with a heavy heart that we share the news that Sanat Moningi passed away the weekend of April 22nd, 2018. Sanat co-founded the Data Science Working Group at Code for San Francisco and led multiple projects, primarily in the areas of environment and housing. Below are statements from members of Code for San Francisco and the Data Science Working Group in honor of Sanat. + +{% include image.html name="sanat.jpg" alt="Photo of Sanat Moningi" style="max-height: 400px" %} + +If you would like to make a donation to the Data Science Working Group in Sanat's name, please use this link to [Code +for America's donation +form](https://secure.codeforamerica.org/page/contribute/default?source_codes=Brigade-page&brigade=Data%20Science%20Working%20Group%2C%20Code%20for%20San%20Francisco%20%28In%20Sanat%27s%20Memory%29) +that will prefill the last field to direct the donation to us. + +**Rocio Ng** + +When I first joined the Data Science Working group, it was just starting out and that was when I had the pleasure to make Sanat's acquaintance. He was very warm and welcoming and clearly passionate about his work. I felt that I instantly had a place in the group and after that moment have had many opportunities to work with him, eventually as a co-lead for the DSWG. During that time he was open to feedback and suggestions that I had for improving the group, and was happy to take on new directions, which are all signs of a great leader. Others have attributed their success in the group to his welcoming nature and passion for the work, and we all agree that he was a great leader, colleague and friend. + +**Vincent La** + +Sanat was the first person I met when I came out to my first hack night at Code for San Francisco. I was completely lost before talking with Sanat. He connected me with my first project with the Small Business Administration and he's a huge reason why I continued to stay at this organization where he's made tremendous contributions. Sanat will always be a part of this community, and I can say for sure that he's made a lasting impact on me and all the friends he's made here + +**Matt Mollison** + +Sanat was such a wonderful leader in the DSWG, always welcoming and a great organizer. + +**Allen Meyer** + +A smart man with a big heart who made a lasting impact on all that he worked with. + +**Jason Lally** + +I've been involved in Code for San Francisco for going on 4 years now. I remember when Sanat and the other DSWG co-founders approached us to ask about pitching it to members. We were so excited at the time to see other volunteers step up and build something entirely new. We witnessed from its inception a great new energy within Code for San Francisco that continues to this day. Sanat brought his compassion, talent, patience and thoughtfulness to everything he did at Code for San Francisco. He was a core reason people showed up to work on impactful projects because he poured so much of his heart into the work and into other people. He was a natural leader and teacher. Missing you Sanat. + +**Jude Calvillo** + +Sanat was my first friend since moving to San Francisco and we co-founded the Data Science Working Group at Code for SF when no such group existed in the Code for America network. At the time, there was a blue ocean of opportunities to do good via data science, and he knew it. No matter the challenge, be it technical or human, he was happy to face it alongside his teammates. Because that's who Sanat was. + +Not only was he super passionate about our voyage, to use technology to improve the lives of his fellow citizens. He was also plain driven, with a smile on his face and embrace at the ready. Here's to a capable captain and caring friend. May your smile and spirit continue to radiate upon our community and upon this ocean of good we can do. We'll miss you buddy. + +**Catherine Zhang** + +I first met Sanat 3 years ago, when he and Jude started the Data Science Working Group at Code for San Francisco. I remember thinking how lucky I was to have met teammates like Sanat who had such incredible passion for tackling hard problems and seeking to empathize with those who are underserved. For me and Sanat, Code for San Francisco was only chapter one and not the full story. Last year Sanat founded a new startup, and I was his co-founder. We shared a mission to support rising leaders of the 21st century get elected into office. It was during this time that we worked together daily. Every week we would pick a new location, a different cafe, a new neighborhood, and when it got late we would grab pizza at the corner shop and remind each other why we had to do this. It was during this time I saw Sanat's unwavering determination, his patience, and his integrity. In times of uncertainty, he made me stronger and we would push forward together. Sanat, thank you for always fighting for others. Your legacy will live on. + +**Jesse Szwedko** + +In an environment where everyone is present because they want to create positive change, Sanat still managed to bring +rare levels of energy and enthusiasm to the brigade. The Data Science Working Group, which he co-founded, has had +incredible successes due in no small part to Sanat's leadership, vision, and stewardship. While we all emphasized the +need to build partnerships with government, Sanat put this into pratice in a way that has had a lasting impact. + +Sanat, you are missed. + +**Anna Kiefer** + +Sanat welcomed me to Code for San Francisco with kind words and a warm smile. He was the first C4SF-er I spoke to, and +I was glad I did. Sanat was approachable, well spoken, and funny. He truly wanted to do good for the citizens of San +Francisco, and for the world. He was an effective leader and an understanding person. He will be dearly missed. + +**Ryan Tanaka** + +I met Sanat the first day I joined Code for San Francisco -- at that point I had no idea what I was looking to do there +but he helped guide me through the organization and suggested that I take over the SF Fire Risk project as the lead. +Sanat was the main organizer of the Data Science Working Group, which he lead great passion and compassion -- he helped +me a lot in my understanding of data science, which eventually lead to a job at the Mayor's Office as a data specialist. +(One of the best jobs I've ever had.) + +Sanat really did leave a positive impact on my life and he will be missed. Hopefully we can carry on his legacy through +our continued efforts with the Brigade. + +_If you are a member of Code for San Francisco and would like to add your statement, please reach out to [hello@codeforsanfrancisco.org](mailto:hello@codeforsanfrancisco.org)_ diff --git a/packages/astro/src/content/blog/2018-04-30-sba-case-study.md b/packages/astro/src/content/blog/2018-04-30-sba-case-study.md new file mode 100644 index 0000000..74dff98 --- /dev/null +++ b/packages/astro/src/content/blog/2018-04-30-sba-case-study.md @@ -0,0 +1,308 @@ +--- +authors: +- vincent_la +date: '2018-04-30' +published: true +title: Small Business Administration Case Study +image: image11.png +image_alt: SBA application prototype screenshot +description: | + A look at how Code for San Francisco's Data Science Working group was able to work with the local Small Business + Administration office to develop a tool to analyze loan data and answer questions to increase the office's impact. + +--- + +

Contributing Authors

+ +* Brianna Bischofberger: UX Designer +* Noah Brod: SBA Stakeholder/Project Sponsor +* Benjamin Elias: Excel/Google Site Guru +* Vincent La: Data Scientist/Project Technical Lead +* Mike Mathews: Data Pipeline Engineer +* Kenny Nieh: Product Designer + +### Project Context + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Product Name:SBAapp (Small Business Administration application)
Team Name:C4SF-SBA (Code for San Francisco - Small Business Admin)
Timeframe:~11 months
Team members: +
    +
  • Brianna Bischofberger, UX Designer
    • +
  • Greg Boyer, Software Engineer
    • +
  • Noah Brod, SBA Stakeholder/Project Sponsor
    • +
  • Adam Donovan, Software Engineer
    • +
  • Benjamin Elias, Excel/Google Site Guru
    • +
  • Vincent La, Data Scientist/Project Technical Lead
    • +
  • Mike Mathews, Software Engineer
    • +
  • Kenny Nieh, Product Designer
    • +
  • Amit Ranan, Front End Engineer
    • +
+
Github:https://github.com/sfbrigade/datasci-sba
Webpage:http://sites.google.com/site/cfasbadash/data-map
MVP Prototype:http://ec2-54-175-133-20.compute-1.amazonaws.com/app/
+ +### Introduction + +The Small Business Administration is a federal agency whose mission is to help Americans start, grow and build +businesses. The SBA provides tools and resources critical to the success of America's 28 million small businesses. These +businesses account for more than 56 million jobs and create two out of three net new jobs in the U.S. each year. Since +starting as an agency in 1953 the SBA has helped millions of entrepreneurs. + +One of the ways that the SBA assists business owners is by helping to address financing gaps for business owners. SBA +partners with lenders across the country to provide business owners reasonable financing options with terms that are +friendly to business owners. Across the country the SBA also has local offices that help to promote the programs, guide +business owners to resources, and encourage outside partners to help small businesses. + +In October of 2016 the SBA released detailed data on two of the major financing programs for small businesses that they +administer. The data included over 1.5 million loan entries with detailed loan information. With the release of the +data, local SBA offices have been able to communicate the impact of the SBA programs at a more local, granular level - +using this detailed data rather than regional aggregates. Prior to the release of this data into the public interested +parties had to submit a FOIA request and wait for months in order to get basic information about how SBA programs were +benefiting businesses in their local area. Local SBA offices were limited to providing very high level summary data that +was often not relevant or detailed enough to communicate the importance of the SBA programs at a local level. However, +even after the lending data was released into the public it was still taking a significant amount of time to pull up +reports and communicate information to partners. Furthermore, the now public data was still being used in a passive way +by local offices. If a party asked for data, SBA offices were better able to accommodate them, but the local offices +were not integrating the public data into their decision-making, communications, or strategies for building out new +partnerships and promoting the SBA lending programs. + +Following the release of the SBA's lending data programs, Noah Brod, an economic Development Specialist with the SBA in +San Francisco, reached out to the SF Brigade at Code for America with [three different project +ideas](https://docs.google.com/document/d/1snCqR35VbrRRzY35Okvrc7iNjOx-uy5GpmxDm1wvCJ4/edit): + +1. How might the SBA more efficiently identify and highlight successful business owners that have benefited from SBA programs? +2. How might the newly released data be used to identify areas in our local district that are under or over participating in our programs? +3. How might we better facilitate connections between entrepreneurs and the non-profits that serve them? + +

Phase 1: Noah starts pitching Timeframe: January to March

+ +Noah spent 2 hours once a week over two months at the SF brigade refining these problem statements and recruiting +volunteers to explore potential solutions and generate small working prototypes. Being persistent in repeatedly pitching +the project each week and narrowing the scope of the project as he onboarded new members was key as it allowed the team +to slowly grow and start to work more independently over time and recruit their own volunteers for more specific needs +as they arose. An early win was when SF brigade volunteer Vince La joined the team. Vince brought a set of project +management skills to the group that kept all of the volunteers working towards a common goal. + +Challenges in this early stage had to do with group formation and choosing which problem would be most fruitful and +exciting to work on. Responding to feedback, refining the problems, narrowing the scope of the project, and being +persistent in pitching from week to week were critical to building a dedicated and focused team. + +

The Project's Journey

+{% include image.html name="image18.jpg" alt="Project timeline" caption="Timeline of our project; Visual by Kenny" %} + +

Backend Data Work Timeframe: March to August

+ +As the team began to gel in March, Noah worked with new members who came in each week to understand what data was +publicly accessible and onboard them into the project. The technical team also investigated and downloaded data from +additional public sources such as the US Census. There was enough data available to commit to working on an analysis of +participation levels (the second problem statement). We began to envision a web app that would show information by +county or zip code and later investigated whether we could map by congressional districts as well using the same data. +An early prototype in Tableau came together quickly and was used to refine what we wanted in later, more polished +iterations of a final prototype. + +{% include image.html name="image15.png" alt="Prototype screenshot" %} + +{% include image.html name="image7.png" alt="Prototype screenshot" %} + +Vince La took charge of tracking the ideas and requests that would arise each week. Each weekly hack night consisted of +huddles to talk through tough problems followed by doling out assignments to complete before the next meeting. + +By mid-summer, the group had a solid pipeline that would pull the data from the SBA website, combine it into a single +hosted database, and then connect the business data to third-party APIs from yelp and google to identify popular +businesses. We also started to explore the next iteration of visualizations at this time. + +Challenges in this stage included what database software to use, what front end and hosting services to use, as well as +a lack of knowledge of some of the latest visualization technologies. Some third party services exist, but require a key +to use or have limits on the number of queries per period. There are some opportunities for the larger brigade +organization to establish vendor relationships to allow work to proceed without incurring large costs or flow +limitations. + +

Phase 3: Defining the MVP and gaining Momentum Timeframe: August to September

+ +In this time period, a few key moments occurred that pushed the project's momentum forward: +- We formed a front-end development team and a UX design team +- We hosted a design sprint that defined a concrete MVP +- We set a deadline to present our MVP to SBA's digital team + +In the months prior, a lot of the key data engineering was completed. We were fortunate to have new volunteers join that +happened to cover the needs of the team, i.e. designing and developing the medium that would share all the data work. + +The sprint we hosted was based on [Google's sprint practice](https://designsprintkit.withgoogle.com/). Typically, the +sprint takes place for a few full days, back-to-back. This wasn't a realistic timeline for us since we only meet one +night a week for a few hours. For our needs, group member Kenny Nieh created a [condensed version of the +sprint](https://docs.google.com/document/d/1w93uwCAf5qAZsJ8rxw0qWO9gC20iv4GvBxlTdhSqids/edit?usp=sharing) that focused +on understanding the user's problems and needs, defining the MVP's scope and requirements, and ideating features out of +all of this. By the end of the white board session, we set a deadline and timeline to complete the MVP prototype within +3 weeks and defined the 3 key key things our users would need to get out of the MVP: + +1. A high-level understanding of SBA's economic impact on small businesses +2. References to successful SBA-support small businesses +3. Identification of which small businesses are support by SBA + +
+
+ {% include image.html name="image17.jpg" alt="Whiteboard before sprint" caption="The Whiteboard, pre-sprint"%} +
+
+ {% include image.html name="image20.jpg" alt="Whiteboard after sprint" caption="Post-sprint"%} +
+
+ +Moving forward, the design and development team met a few times to define technical constraints and distill our sprint +findings into specs and features. Given a tight timeline of 3 weeks, we pulled together some wireframes and coded them +out. + +
+
+ {% include image.html name="image10.jpg" alt="Screenshot" %} +
+
+ {% include image.html name="image14.jpg" alt="Screenshot" %} +
+
+ {% include image.html name="image16.jpg" alt="Screenshot" %} +
+
+ {% include image.html name="image13.jpg" alt="Screenshot" %} +
+
+ +There are 4 main components to it: + +1. Form fields that allow you to select a location and time range to search data by +2. High level metrics showcasing SBA's impact +3. A ranking of top local businesses +4. A map-based data visualization of SBA's impact, including tool tips for local small businesses + +You can view our low-fidelity prototype here: + +[http://ec2-54-175-133-20.compute-1.amazonaws.com/app/](http://ec2-54-175-133-20.compute-1.amazonaws.com/app/) + +{% include image.html name="image11.png" alt="Prototype screenshot" %} + +

Phase 4: MVP Push Timeframe: September to Present

+ +Working under a tight deadline, the SBA data science group came together and synthesized the past 10 months of research, +testing, and development to creating an low-fidelity interactive prototype in time for Noah's meeting with SBA +stakeholders. Noah's meeting was held at the end of September and provided an opportunity for him to share the SBA loan +analysis tool and to discuss the future of this tool. Topics such as feasibility, scalability, development, and SBA data +science group's future involvement was discussed. + +#### Success metrics for this project + +The SBA data science group established a set of success metrics or KPI's for the loan analysis tool: + +1. At minimum it is desired that the discussion surrounding the SBA loan data would open up a discussion within SBA to + make their open data more easily digestible and accessible. The SFbridage's prototype provides proof of concept of + what can be done with open data and how the SBA itself can benefit from making their data more open. +2. A minor win for the SBA data science group would be that the SBA loan analysis tool be adopted by SBA itself, further + developed, and tested and utilized locally in the San Francisco office as a pilot. +3. A major win for both the SBA data science group would be that the SBA loan analysis tool becomes an internal *or* + external tool used nationally through-out SBA offices. Scaling the SBA loan analysis tool for national usage in other + SBA districts could set an example for the possibilities of what can be done with other open datasets. + +The SBA data science group is a volunteer group that has met weekly for the past 10 months. The group is comprised of +data scientists, developers, engineers, UX designers, and the client. + +### Major Takeaways + +#### SBA: Working with Civic Volunteers - Noah Brod + +For me this project was an excellent example of how government agency employees can productively engage with the civic +tech community to develop small pilots that address very local needs and demands. Rather than expecting solutions to +come out of a long process at a national level all at once, local solutions can be designed rapidly and developed by +regional and field offices, which can then be piloted and possibly gain national adoption based off of those pilots. +This entire process can generate very interesting products and solutions at a very low cost from an agency perspective. +The added benefit is that a small pilot can easily generate dozens of spin-off projects and ideas as the observations +and questions raised by the pilot emerge. For instance, this project drove a number of spin-off conversations around +improving how SBA releases its data generally, in what format, and in what condition. + +#### Leading and Forming a Data Science Team - Vincent La + +The value of civic tech is not in complex analysis or code but the product that is delivered to its end user and how it +helps them solve their problems. The biggest lesson I learned from this is that the most valuable resource to ensure +a successful project is an engaged civic partner who is actively facing challenges in their community -- in this case +Noah. Having Noah guide us each week to set scope really helped keep the tech team on track and focused towards +providing meaningful solutions. + +In terms of leading a data science team, I found that the most important thing was creating a process-driven approach to +emphasize documentation, data quality, and infrastructure. When I first joined this project, every week resulted in +ad-hoc work and it was hard to build on each other's work week-to-week. Especially given that this is an all-volunteer +group, the first problem to solve is “key-person” risk. You may not necessarily know if the person who was working on +a model or on some code one week will be back the next week. Being aware of the following points will help increase the +chances of success: + +1. You may need to refill roles as people are constantly coming and going. +2. You may need to recruit additional skills as you explore ideas. +3. You should have at least one person in charge of onboarding team members every week. This person can change each week. +4. Look ahead of product timeline and think what roles you'll need coming up. Start pitching for them early. +5. Pitch for very specific skills to gain better chances of pulling in the right people. + +In terms of tooling and infrastructure, it's important to minimize workflows that results in outputs being stored +locally. With small teams or with prototyping, it's perfectly fine to manipulate some Excel sheets locally or load up +a CSV in a Jupyter notebook and create some visualizations. The problem with scaling this, especially in an all +volunteer group, is that is becomes immediately unclear which work is necessary for production and driving towards the +final “product”, and which was just exploring and now unnecessary. Our first biggest win on this front was getting +a PostgreSQL database hosted on Microsoft Azure, thanks to their continued and generous support of Code for San +Francisco. With a database hosted in the cloud that anyone could access it became much easier to build on each other's +work and know what the most current state of our data is. However, even with a database, we still needed a process to +keep everything documented and organized. For this, we created a “data pipeline”, a process through which we extracted, +loaded, and transformed data in our database. You can create a pipeline in many different ways; for us it was a series +of SQL and Python scripts that ran in a defined chronological order. Furthermore, we (at least tried) to abide by two +guiding principles + +1. The database at any time should be reproducible by everything in the Extract-Transform-Load (ETL) code. That is, if + anything gets accidentally dropped or mis-transformed, the entire database could be recreated by simply re-running + the data pipeline from start to finish. +2. Everything in the database can be traced back to code documented and version controlled (we used Git/GitHub). + +Our second big win in terms of tooling was a shared online SQL editor and analytics platform, generously donated to us +by Mode Analytics. By connecting our database to Mode Analytics, anyone with SQL knowledge could query our database +without having to download any files and in a friendlier UI. + +Finally, note that a lot of the above did not have a direct tie to data science, and reflecting back, even with data +science projects, especially in an all-volunteer group, the biggest reasons for success are good documentation, +establish process-driven approaches, and infrastructure to maintain and share data. I learned a lot from working +cross-functionally and always keeping a focus on the product. + +#### What was a big win for you or a major learning point? + +“I found it very energizing to be surrounded by a group of smart volunteers with such a diverse set of skills.” - **Mike +Mathews, Data Pipeline Engineer** + +“A major win for me was showing what could be done simply by engaging with the open source and civic tech communities +directly - opening the doors to a motivated and talented community of volunteers created benefits for our agency, the +volunteers themselves, and public as well.” - **Noah Brod, Project Sponsor** + +“The collaborative approach and inclusive nature of the volunteers made for an extremely positive project experience. +The major win for me was how transparent everyone was when communicating about challenges, feasibility, expectations, +and schedule changes.” - **Brianna Bischofberger, UX Designer** + +“Coming from a UX design background, this project was a breath of fresh air! I love how the user we were designing for +(Noah) was an active part of our product development - showing up to our weekly meetings and participating in our slack +group. It made keeping the product user-centered so much easier.” - **Kenny Nieh, Product Designer** diff --git a/packages/astro/src/content/blog/2018-06-14-mapping-tools.md b/packages/astro/src/content/blog/2018-06-14-mapping-tools.md new file mode 100644 index 0000000..079ac06 --- /dev/null +++ b/packages/astro/src/content/blog/2018-06-14-mapping-tools.md @@ -0,0 +1,46 @@ +--- +authors: +- allen_meyer +date: '2018-06-14' +published: true +image: "civic-innovation-group.jpg" +image_alt: Screenshot of Civic Innovation Group mapping tool +title: Data Mapping Tools for Brigades +description: | + The Civic Innovation Group has built a suite of tools that Brigade members can use to remove roadblacks and + save time when working with filtering and mapping data, especially for people who don't have map coding skills. +--- + +Code for SF has incubated a variety of groups and projects over the five years it's been hacking. [The Civic Innovation +Group](https://civic.geosphere.io/) is one of those organizations. They are working on innovative solutions to +government challenges. They are a bit of hybrid organization, partnering with volunteers, government agencies and tech +companies. They are launching a suite of mapping tools for Brigade members to use that address some of the challenges +Brigade members have had. These tools are designed to remove blocks and save time when working with filtering and +mapping data, especially for people who don't have map coding skills. + +## EAS Search Tool + +[Enterprise Address System](https://civic.geosphere.io/tools/eas-search/) is a gazetteer, an address index for SF. +Select an area of SF and you can download all the address within that area with supplemented information like +coordinates, block and centerline node network numbers. This is useful if you need to select addresses for a particular +neighborhood from city wide data, such as from [DataSF Open Data portal](https://datasf.org/opendata/) which does not +let you select data by specific area. + +## Geocoder + +[Geocoder](https://civic.geosphere.io/tools/sf-geocoder/) adds geographic data to an address. It is essential for +mapping data without any GIS skills. Unlike other geocoders, this tools adds SF specific information such as centerline +node network numbers and block IDs. + +## 3G: Geographic Geometry Generator + +This is a brand new tool. [The Geographic Geometry Generator (3G) ](https://civic.geosphere.io/tools/geo/) Draw a line, +point or shape on a map and it gives you geometry and coordinates. It is incredibly useful for people without GIS skills +to create, name, and save custom geometry. Want to gerrymander your voting district? This is the tool for you. + +These tools are built using [Leaflet Draw,](http://leaflet.github.io/Leaflet.draw/docs/leaflet-draw-latest.html) an open +source GIS toolbar plugin and [JS library](http://leafletjs.com/) for interactive maps. + +Currently there are two projects using these tools namely [SF Crime Data](https://sfcrimedata.org/) and [SFMTA Board +Meetings Resolution Database.](https://civic.geosphere.io/maps/sfmta-resolutions/) We hope that more Brigade members +will find those tools useful. diff --git a/packages/astro/src/content/blog/2018-08-04-odsc.md b/packages/astro/src/content/blog/2018-08-04-odsc.md new file mode 100644 index 0000000..525dd4b --- /dev/null +++ b/packages/astro/src/content/blog/2018-08-04-odsc.md @@ -0,0 +1,43 @@ +--- +authors: +- jesse_szwedko +date: '2018-08-04' +published: true +title: Open Data Science Conference West 2018 +image: odsc.png +image_alt: Open Data Science Coneference West Advertisement +description: | + Partnership post from Open Data Science Conference West 2018 + upcoming Oct. 31 - Nov. 3. ODSC West will be this Fall's leading + data science conference providing over 340 hours of trainings, + talks, and workshops spanning 4 days and 48 tracks. + +--- + +

+ Cross-promotional post from Open Data Science Conference West 2018, a Code for San Francisco Media Partner. +

+ +[ODSC West](https://odsc.com/california) will be this Fall's leading data +science conference providing over 340 hours of trainings, talks, and workshops +spanning 4 days and 48 tracks. More content means more choices and better +learning outcomes. + +**Save hundreds on door prices with savings of 60% using the code SE-DE-ODSCWest.** + +For West 2018 we are bringing you an incredibly talented lineup of renowned +speakers and instructors including: + +* **Virginia Eubanks** \| Author of Automating Inequality +* **Andrej Karpathy** \| Director of AI at Tesla +* **Cassie Kozyrkov** \| Chief Decision Scientist at Google +* **Josh Wills** \| Director of Data Engineering at Slack +* **Andreas Mueller** \| Author, Professor, and Core Contributor of scikit-learn +* **Jim Guszcza** \| Chief Data Scientist at Deloitte + +Totaling over **340 hours** of applied talks, workshops, and training session, we +offer the widest choice of the most important topics in data science. Focus +areas include deep learning and machine learning, data visualization and many +more. Fours days with an extra day of training. + +Check schedule overview [here](https://odsc.com/california/schedule-2018). diff --git a/packages/astro/src/content/blog/2018-09-16-dev-mission-and-c4sf-launch-fellowship-program-at-national-day-of-civic-hacking.md b/packages/astro/src/content/blog/2018-09-16-dev-mission-and-c4sf-launch-fellowship-program-at-national-day-of-civic-hacking.md new file mode 100644 index 0000000..347f93c --- /dev/null +++ b/packages/astro/src/content/blog/2018-09-16-dev-mission-and-c4sf-launch-fellowship-program-at-national-day-of-civic-hacking.md @@ -0,0 +1,65 @@ +--- +image: leo-sosa-keynote.png +image_alt: >- + Leo Sosa of dev/Mission delivers keynote at Code for San Francisco's National + Day of Civic Hacking event. +title: >- + dev/Mission and C4SF Launch Fellowship Program at National Day of Civic + Hacking +description: >- + Leo Sosa of dev/Mission gave the keynote at C4SF's National Day of Civic + Hacking event. In the following interview he describes his vision for bringing + equity to tech employment and how C4SF can help. +pin_to_frontpage: false +image_list_only: false +authors: + - allen_meyer + - sebastian_meyer +--- +_Code for San Francisco, the city’s local chapter of Code for America, recently announced the launch of their first fellowship program this year. The Fellowship is in partnership with dev/Mission, with support from Microsoft._ + +_When the Code for San Francisco Brigade organizers began drafting their priorities for this year, increasing the diversity of the communities that participate in their weekly hack night was high on the list. The team also thought they could make a contribution to the movement to bring tech training to underserved communities, contributing to tech equity by tapping into their large pool of volunteer knowledge and skill. This desire to increase the impact of the Brigade’s work in San Francisco’s underserved communities led them to dev/Mission, an organization its CEO Leo Sosa describes as “a nonprofit organization that aims to train untapped young adults for careers in tech who can bring prosperity to underserved communities”._ + +_Sebastian Meyer, a Marin County high school student, interviewed Sosa at the National Day of Civic Hacking, the Brigade’s yearly civic tech event, at which the Fellowship was featured. Leo delivered the keynote for the day._ + + + +**SM: Tell me more about your mission.** + +**LS:** Connect as many young adults as possible to the tech industry - not only at the education level, because there is a huge gap in the education system around teaching stem opportunity primarily in terms of technology and engineering. Young people need to be exposed to employment pathways. My personal mission is to make sure that every young person I meet, including yourself, should be exposed to that environment and be empowered to choose their technology career path. + +**SM: How did dev/Mission come to be?** + +**LS:** I started thinking about the idea of launching my own nonprofit many years ago. I was scared - I didn’t know what to do. I had this idea 5 years ago to launch a nonprofit, and some of the folks that were involved with me at the time kept encouraging me, like, “Let’s do something, let’s figure something out.” So I brought in a team of technologists that wanted to give back to the community, wanted to make sure underrepresented young people from non-traditional backgrounds were exposed to some type of opportunity. That’s how dev/Mission got started. + +I saw disparities around diversity in the tech industry, and going back to what I mentioned about the education system, we felt it was an opportunity for us. I felt this urgency to create this organization so young people can have an opportunity to choose that path. I resigned from my job - my wife thought i was crazy, my boys said, “Ok, hopefully it will work” - and a year later I’m at this beautiful event for National Day of Civic Hacking in partnership with Code for SF. That’s our first step. We need to continue to get folks out there to hear more about what this organization is: our mission, our values. I brought young people \[the Fellows] today, so people now see that we have this available that needs to get exposed. + +**SM: How has your own experience influenced your goals?** + +**LS:** When I was 16, it was a really hard time for me. I thought I was king of the world. I thought I knew it all. I came to this country, and it was really hard for me to adjust to the culture, huge clash. I was trying to do my own thing. And for almost 10 years it was really hard for me to understand that technology was a vehicle for me to improve my life. I came really late in the game - I was 24 years old when I really felt like I needed to take a computer class. But as soon as I did, it opened up my eyes to a whole new world. back, I think “If I was 16 years old, and not already exposed to tech I would already be behind,” so I made that commitment to connect as many young people to those opportunities as possible. So, dev/Mission is very personal, very sentimental, because if I don’t see young people coding, building computers, interacting with each other, it makes me sad. It’s very dear to my heart, and I know there’s still more that I can do, and that this organization can do to close that gap. + +**SM: What kinds of positive experiences have you had through this work?** + +**LS:** Every day is a positive experience. But, seeing the behavior of young people where as they get exposed to technology, they get passionate, they become aware of the type of skills they bring to the table. Just recently I met some of the young people that have graduated from our program and came back and told me, “Leo, I got an internship at SalesForce.” Or, “Leo, I got a job at Jones IP”, “Leo, I got a job at Techleap,” “Leo, I’m going back to school for a CS major.” You count those on your fingers, but at the same time you know that young person is going to inspire others by sharing their story. + +On the bigger note, I think there is a positive impact of these young people coming together from different economic backgrounds, different communities all over the Bay Area - not just San Francisco because we have young people coming from Richmond, Oakland, the East Bay. s they come together working in teams, working on projects creates that synergy that a lot of young people are not being exposed to. Aside from that, I think the biggest story for this organization is that our board members are half minorities, and I think that is critical for our success. + +**SM: How have you seen dev/Mission impact your community?** + +**LS:** We are in three communities right now. We saw a community like Hunters Point West, which is completely isolated, \[with] a lot of crime. And now we have a computer lab, we’re about to launch a STEM hub to bring K-12 kids in to tech. That’s going to be announced next week, at our backpack giveaway. We’re also working in the Western Edition, primarily working in affordable housing. All of our programs run in affordable housing.Last week I was in Yakima \[in Washington], where we launched our first chapter program in partnership with OIC and Youthbuild. If you believe San Francisco has so many opportunities, imagine a city like Yakima, that has really nothing out there. These young people that graduated from the program came in not knowing how to write a line of code, and now they are like, “Wow, is there a career for me?” There is! You just drive to Seattle, 2 hours away, maybe you move to Seattle. But those five young people that graduated from the program were exposed to that opportunity. Now it’s up to them. I don’t tell young people I’m going to get them a job. I don’t tell young people they’re going to go to boot camp. You would make that choice. I will connect you to those opportunities, but you need to take ownership over what you want to do with that. So I think at a bigger level, the impact we’re making in the community is huge, because now we’re creating a vehicle for kids and youth and young adults to use technology to improve their lives. + +**SM: What kind of plans for the future do you have for dev/Mission?** + +**LS:** I want every community in San Francisco to have a program like dev/Mission. I want every city in the Bay Area or California to have a program like dev/Mission. It’s very ambitious. But if you pay attention to all the young people that live in those communities,there are no programs like that. Every time new people join our program, we ask why they’re here, and I hear over and over, “There’s no program like this where I live.” These are young people that are hungry for a program like dev/Mission. I also believe that funding is critical. So being exposed to those opportunities help us get to that point. + + + +## dev/Mission Possible + +By Sebastian Meyer + +Following this interview, I got the privilege to meet one of the alumni of the program, Mellany, who said that dev/mission empowered her to make her own path in the tech world in a way that had not been done before. Tech was not something she had had access to in her schooling, but something she had always been interested in and wanted to pursue: + +“Before dev/Mission, I had barely gotten into coding. I was trying to pursue nursing in college but didn’t like chemistry, so I took a coding class, which got me super interested in coding, and not long after I met Leo and learned about dev/mission and what they were doing… I never really had any opportunities in tech before \[dev/mission], and had never really had any support, with my family always working, who are first generation immigrants, so they can’t really do much regarding my education...I didn’t really know much about the tech industry.” + +This interview really inspired me. Leo had told me earlier that his growing network of computer labs and teaching facilities had recently expanded to Hunters Point, a relatively isolated community with high crime rates. With dev/mission on the ground floor training young people to seek out their dreams in technology, I think it’s reasonable to expect a shift in the racial disparity within the Bay Area tech scene, especially as dev/Missions network continues to grow. With whole new demographics of people within the industry, imagine what kind of progress can be made. diff --git a/packages/astro/src/content/blog/2018-10-20-code-for-san-francisco-community-creates-a-voter-guide-to-help-fight-fake-news.md b/packages/astro/src/content/blog/2018-10-20-code-for-san-francisco-community-creates-a-voter-guide-to-help-fight-fake-news.md new file mode 100644 index 0000000..50c7a62 --- /dev/null +++ b/packages/astro/src/content/blog/2018-10-20-code-for-san-francisco-community-creates-a-voter-guide-to-help-fight-fake-news.md @@ -0,0 +1,73 @@ +--- +image: we-vote-logo-wordmark-vertical-color-on-white-1500x1410.png +image_alt: We Vote logo +authors: +- allen_meyer +title: >- + Code for San Francisco Community Creates a Voter Guide to Help Fight Fake + News. +description: >- + We Vote is nonpartisan and nonprofit, founded and built by volunteers, + including engineers from the Code for San Francisco Brigade of Code for + America. We Vote is a networked digital voter guide that empowers voters and + improves democracy. +pin_to_frontpage: false +image_list_only: false +--- +We Vote is nonpartisan and nonprofit, founded and built by volunteers, including engineers from the Code for San Francisco Brigade of Code for America. + +## [Check your ballot!](https://wevote.us/ballot) + +We Vote is a networked digital voter guide that empowers voters and improves democracy. Voters have a lot of decisions to make, and political campaigns don't always tell the whole truth. With the proliferation of fake news and misinformation, it's become even more difficult to figure out what sources to trust. We Vote cuts through the clutter to give you better information about what's on your ballot. The platform aggregates endorsements and opinions across personal networks and helps you get information from trusted and verified advocacy organizations. + +Elections matter, and each vote matters, but the U.S. still trails most developed countries in voter turnout. 80 million voting-age Americans are expected to sit out each presidential election. We Vote is building tools to empower voters to cast their vote. When more eligible voters cast a vote, we create a stronger democracy. It all starts with you, it all starts today. Together, we can get over 70% voter turnout. + +In 2016, the Pew Research Center ranked the U.S. 31st out of 35 countries for voter turnout based on the voting age populace, among the mostly democratic nations that are a part of the Organization for Economic Cooperation and Development. + +in 2012, 54% of Americans voted, about 129 million people out of a potential 241 million citizens, in the presidential election. In 2016, 61.4%, according to PEW Research, of Americans voted in the presidential election. We Vote wants to improve these statistics. + +Voter registration is often harder in the U.S.. Tens of millions of Americans aren’t registered to vote because they missed a deadline, they didn’t know how or where to register, or because of registration errors. We Vote helps Americans register to vote by connecting them with quick and easy voter registration tools. + +In 2008, the Census Bureau found around 4 million Americans fell into these various non-registered categories. + +## **Elections matter, and each vote matters. Some elections have been decided by one vote.** + +“I was first recruited to run for the Senate when there was a vacancy on the ballot. My selection to be the party nominee was decided by a one vote margin,” says Ivey-Soto, D-New Mexico. + +David Yancey (R-Virginia) and Shelly Simonds (D-Virginia) both ran against each other for a spot in the Virginia House of Delegates in December 2017. 11,608 votes were cast for each of them. The tie was broken by pulling the name of a candidate from a bowl. + +Americans are overwhelmed by election marketing and misinformation. In the two party system, parties are incentivized to turn out base supporters they know will be reliable votes for their side instead of bringing in all eligible voters. This leads to a constant drum of political information. This also leads to deluge of ads and political marketing espousing incorrect facts and slander. We Vote is working to increase voter turnout in the U.S. by allowing voters to see what is on their ballot and to see who in their network supports the ballot items without excess fanfare. + +## **64% of adults believe fake news stories cause a great deal of confusion.** + +It is always election season, somewhere in the U.S.. The U.S. holds more elections than most other developed nations. Though the president is elected for four years, all seats in the House of Representatives are up for election every two years, as are about a third of the seats in the Senate. Additionally, local elections take place throughout the four year presidential term. + +2018, a midterm election year, will see 36+ elections at the state and local levels. This year, elections are held to elect all 435 seats of the House. + +2019, an off-year election year will see 3 state elections and various local elections + +2020, a Presidential election year, will see over 11+ gubernatorial elections as well as elections to fill 33 senate seats and all 425 seats in the House. + +“We have elections three out of every four years in Louisiana,” said Alfred (Butch) Speer, clerk for the Louisiana House of Representatives. “We like to say that we elect more of our officials than any other state.” + +It’s not just in the fall or in November either. Many cities hold elections for mayor and city council in the spring. + +Presidential primaries kick off months before November. For example, New Hampshire now kicks off the presidential primary season in February. + +Early voting and no-excuse absentee voting often starts early, several weeks ahead of Election Day. + +https://qz.com/24186/58-countries-with-better-voter-turnout-than-the-united-states/ + +http://www.pewresearch.org/fact-tank/2017/05/12/black-voter-turnout-fell-in-2016-even-as-a-record-number-of-americans-cast-ballots/ + +https://en.wikipedia.org/wiki/Voter_turnout_in_the_United_States_presidential_elections#Turnout_statistics + +http://www.pewinternet.org/2017/10/19/the-future-of-truth-and-misinformation-online/ + +http://www.pewresearch.org/fact-tank/2016/08/02/u-s-voter-turnout-trails-most-developed-countries/ + +http://www.census.gov/prod/2010pubs/p20-562.pdf + +https://www.vox.com/policy-and-politics/2016/11/7/13536198/election-day-americans-vote + +https://qz.com/291933/why-the-us-is-the-only-country-in-the-world-to-have-elections-so-often/ diff --git a/packages/astro/src/content/blog/2019-04-17-w-o-m-a-n-inc-domestic-violence-referral-center.md b/packages/astro/src/content/blog/2019-04-17-w-o-m-a-n-inc-domestic-violence-referral-center.md new file mode 100644 index 0000000..00bb738 --- /dev/null +++ b/packages/astro/src/content/blog/2019-04-17-w-o-m-a-n-inc-domestic-violence-referral-center.md @@ -0,0 +1,36 @@ +--- +image: dvirc-masthead.jpg +image_alt: domestic violence information referral center logo +title: 'W.O.M.A.N., Inc. Domestic Violence Referral Center' +authors: +- shaena_spoor +description: >- + This February, W.O.M.A.N., Inc. and Code for San Francisco volunteers launched + a revamped version of DVIRC, a database that helps domestic violence agencies + connect information with the survivors who need it. Shaena Spoor, the project + representative from W.O.M.A.N., Inc., tells the story of how it came + together. +pin_to_frontpage: true +image_list_only: true +--- +By: ShaenaSpoor - shaena@womaninc.org + +**What is the DVIRC?** + +For the last 9 months, W.O.M.A.N., Inc. has been working with Code for San Francisco volunteers to build a new website to replace our old Domestic Violence Information Referral Center (DVIRC.) Designed to connect domestic violence service providers across California, the DVIRC is a database that provides a safe space for domestic violence agencies to share and access resources on services available to the people they serve. Since its development in 2012, the DVIRC has supported thousands of domestic violence survivors by finding safe shelter and providing an accessible “one-stop-shop” for agencies to share up-to-date information about availability of shelter beds and other emergency services. + +**Why did you end up partnering with Code for SF volunteers?** + +While it had served as an integral part of our daily work with survivors, the old DVIRC system was costly to maintain and became dysfunctional and outdated over time. We needed to find a new platform that would be simpler, and less expensive for hosting the website. Initially, it was challenging to find the help we needed -- there is only so much funding available, and companies often said the new DVIRC project was too involved for what they could offer pro bono. I reached out to a friend of mine, who both works in tech and has experience working with nonprofits, to see if she had any insights on who W.O.M.A.N., Inc. could reach out to. She told me we should give Code for America \[Code for SF’s parent organization] a shot. + +**How did the project come together?** + +In May 2018, we dropped into Code for San Francisco’s new member orientation, and pitched the DVIRC project to see if anyone would be interested in helping out. I was pleasantly surprised by the overwhelming amount of people who wanted to lend a hand. It took some time, but we eventually formed a solid group of volunteers who took on a variety of roles, helping us research alternative platforms, create the new site, and engage in usability testing. It was also helpful that the Code for SF core team was so supportive in checking in with us and offering space so we could make sure the project was successful. + +**How do you feel now that the website is officially launched?** + +We were so excited to share the new system with the W.O.M.A.N., Inc. team and other community partners who count on the website to provide up-to-date referrals to their clients. The new website is refreshingly simple to maintain and to train/onboard users on. We are so happy with the results! + +We very much appreciate the spaciousness and support offered by the SF brigade, the volunteers who came together to make this possible, and everyone who showed up in the in-between to offer their expertise. Special thanks to PJ Cabrera, Lucas Kellner, Sarah Miller and Jessie Stocks for the immense time and energy they put into making this new website a reality! + +_Women Organized to Make Abuse Nonexistent, Inc. (W.O.M.A.N., Inc.) has operated since 1978 as a community-based, multi-service agency, serving people who’ve experienced abuse in San Francisco and the larger Bay Area. We support survivors of domestic violence and their loved ones along their healing journeys, bridging value-rich networks designed to address intersections of violence._ [_www.womaninc.org/_](http://www.womaninc.org/)__ diff --git a/packages/astro/src/content/blog/2019-05-01-open-data-day-2019-community-driven-hackathon.md b/packages/astro/src/content/blog/2019-05-01-open-data-day-2019-community-driven-hackathon.md new file mode 100644 index 0000000..b409e14 --- /dev/null +++ b/packages/astro/src/content/blog/2019-05-01-open-data-day-2019-community-driven-hackathon.md @@ -0,0 +1,50 @@ +--- +image: odd-2019-key-note.jpg +image_alt: >- + Jason Lally from DataSF gives key note at Code for San Francisco's Open Data + Day 2019 +title: Open Data Day 2019 - Community Driven Hackathon +authors: +- code_for_san_francisco_community +description: An open source report from your local civic tech community. +pin_to_frontpage: yes + +image_list_only: true +--- +The last six months have been busy for C4SF, as we’ve gone through changes in leadership, supported strong turnout at our weekly hack nights, and completed two projects with a C4SF sponsor—not to mention moving to CfA’s new HQ on Mission Street. Just when we thought we might get to take a breather in January, we realized that one of the biggest events of the year - Open Data Day - was just a month away! + +Though we explored the idea of bringing in keynote speakers, as we had done for previous Open Data Days, we ultimately decided to see what would happen when we let our hack night project teams take over the day. They responded with “game on” enthusiasm that turned our event into a full day of programming powered by their grassroots, community-driven energy. + +Here’s what they have to say: + +**Shelter Tech** + +Richard Xia, a ShelterTech developer, says, “It was great to have access to devs.” Even though most people think ‘quantitative’ when they hear the word ‘data’, “most of our data was qualitative, which made it easier for us to put folks to work.” + +**Open Transit** + +Neel, a project manager at OpenTransit: “We walked people through the open data process.” With the opportunity to focus on their project over a full day, the OpenTransit team churned out over X GitHub commits - Y% of all their commits to date. + +**Data Science Working Group** + +Rocio, co-lead of the Data Science Working Group, hosted a workshop on using the R language to analyze open data. “It was a great introduction to open data. We had a lot of beginners, but there was room for people to choose their own adventure.” + +Vincent, the group’s other co-lead, led a team focused on analyzing campaign finance data. “People came out and explored \[the] data. We made material progress that day and pushed the project forward!” + +**Lane Breach** + +The LaneBreach team describes their project as “creating a hub for bike data in San Francisco through consolidating sources and providing easy access through a single API. Our goal is to daylight difficult to find data, which are made available to non-technical users through a web service with simple tools and intuitive visualizations.” + +Alex, LaneBreach’s founder, offers some of his own personal reflections: “I enjoyed preparing for the event. It’s sometimes difficult to set defined goals on an open-ended project like this, so having some external pressure was very welcome. This was also a chance to get some feedback from a group of people who don’t normally come to hack night. Very valuable, I had some great conversations. I particularly enjoyed the breakout discussion surrounding the social impacts of crowd-sourced data collection.” + +**NLTweets** + +According to the NLtweets team, “\[we have] a mission to provide projects with a tool that will let them accomplish valuable user research data in one night, and, with continued study of their domain problem, meaningful insights over time.” + +On Open Data Day, the team was able to work in a way that went beyond the regular Wednesday events: “Every project needs good user research to maximize their chances of making the biggest impact possible, but the format of weekly Hack Nights doesn’t afford the time to plan and implement a solid user research campaign. And experience has shown that user research is an activity many members might not know much about or maybe isn’t high on their list of skills they want to master.” + +NLTweets’ founder Josh Freivogel hosted a presentation on data ethics that turned into a lively discussion: “The community wants to engage more than I anticipated. The give and take was fantastic.” About the event, he says “the quality of the other project presentations is telling regarding the seriousness with which volunteers are collaborating to solve big problems.” + +\_\_\_\_ + +At this year’s Open Data Day, trying a bottom-up approach meant that each team brought something different to the event - and got something different out of it. Seeing what can happen when we’re willing to experiment has fueled our enthusiasm to host events that go beyond our traditional formats. Stay tuned - we’ve got more coming! diff --git a/packages/astro/src/content/blog/2019-06-22-introducing-civc-tech-to-san-franciscos-underserved-communities.md b/packages/astro/src/content/blog/2019-06-22-introducing-civc-tech-to-san-franciscos-underserved-communities.md new file mode 100644 index 0000000..d5faf12 --- /dev/null +++ b/packages/astro/src/content/blog/2019-06-22-introducing-civc-tech-to-san-franciscos-underserved-communities.md @@ -0,0 +1,73 @@ +--- +image: four-fine-fellows.jpg +image_alt: 'dev/Mission Fellows, Edgar, Mellany, AJ and Daniel' +title: Introducing Civic Tech to San Francisco's Underserved Communities +authors: +- allen_meyer +description: >- + Code for San Francisco teams up with to create a Fellowship + program to introduce San Francisco's underserved youth to civic tech. +pin_to_frontpage: yes +image_list_only: true +--- +The [](http://devmission.org/) Code for San Francisco Fellowship began with a desire of the C4SF organizing team to increase the diversity of the communities that participate in our weekly hack night. The team thought they could make a contribution to the movement to bring tech training to underserved communities, and also contribute to tech equity, by tapping into the large pool of volunteer knowledge and skills that shows up at our weekly hack nights. + +We thought we might be more effective if we partnered with a community-based organization and found a great fit with . CEO Leo Sosa describes as “A nonprofit organization that aims to train untapped young adults for careers in tech who can bring prosperity to underserved communities”. technology training programs teach young adults ages 16-24, skills in IoT, hardware/software, coding and critical career skills. has also opened up STEM training labs for K-12 and a digital music program for ages 14-21. [Microsoft](https://blogs.microsoft.com/bayarea/), a sponsor to , agreed to support the Fellows who completed the Fellowship with a stipend. + +The Fellows’ journey began last August when we introduced the [Fellowship at National Day of Civic Hacking](https://codeforsanfrancisco.org/2018/09/16/dev-mission-and-c4sf-launch-fellowship-program-at-national-day-of-civic-hacking/). We asked the Fellows to begin with an issue that they wanted to address in their communities, which for the most part is the Mission district. Brigade member, Allen Meyer led the Fellows and workshop attendees through a design thinking exercise that addressed the issues the Fellows wanted to tackle. The issues included training youth in tech, connecting community gardens to each other, and San Francisco’s seemingly intractable homelessness. + +The workshop enabled the Fellows to develop a basic product idea that they could explore for the next six months of hack nights. We began with some basic user research. What did they think the user needs would be for the proposed web application? We then had them write up a basic interview guide and sent them off in search of users. + +The next design step was to create some basic personas based on who they had talked to and what they had learned from those interviews. The research helped them to verify their initial assumptions and ideas but they also found that they might need to pivot a bit. Yes, along the way we dropped in tech start-up concepts, such as pivoting. + +The Fellows spent the next six months working with Francis Li, their mentor, on Sundays learning full-stack web development, and attending [Wednesday Civic Hack Nights](https://www.meetup.com/Code-for-San-Francisco-Civic-Hack-Night/). All the hard work was showcased at the program’s sponsor [Microsoft Reactor](https://developer.microsoft.com/en-us/reactor/#ReactorSF). The Showcase’s attendees included Joshua Arce, Director of Workforce Development for Mayor London Breed. + +The Fellowship was a learning experience for both the Fellows and the Code for San Francisco Team. It may have been a bit ambitious to learn basic product development, UX design and coding, but the Fellows really impressed us with their dedication. + +**Project Name:** [The View](http://sfviews.org/) \ +**Project Lead:** [Edgar Catalan](https://www.linkedin.com/in/edgarcatalan10/), with C4SF intern [Sebastian Meyer](https://www.linkedin.com/in/sebastian-meyer-95a03a188/) + +**Problem Description:** The youth today struggles to be informed in any way about what is going in our city with news and technology. I was seeing a pattern that we get bored quickly because of lack of interest, not understanding it, or something is too long to read. + +**Proposed Solution:** Making a platform to give the youth of San Francisco and the Bay Area an option to see the Top News and Tech News in an enjoyable and understandable way. While including our favorite interests. + +_How was the experience of taking a project from concept to prototype? Anything that surprised you along the way?_ + +**Edgar:** The experience was memorable because I took time from school to draw the User Interface for the app and then implementing it to HTML, CSS, and Javascript. What surprised me was how much I enjoyed building a dynamic web application. I remember first starting the fellowship I felt that I wasn't going to have fun but ended up being memorable. + +**Sebastian:** [The View](http://sfviews.org/) was an excellent learning experience. I realized through the process of conceptualizing the front end with Edgar and developing the content that I had a knack for journalism and basic content creation, but also content management, which is a skillset that will be useful for me to know about in my future career. I was surprised by how tedious it was to find content that was worthy of the site, as so much tech news is rather bland and inconsequential, with the occasional interesting and/or controversial news piece sticking out. This added an additional challenge to making the content of the site interesting and fresh, and stretched my writing and researching skills. + +_Do you have any plans now that the Fellowship is done, do you have plans to keep developing the project?_ + +**Edgar:** My plan is to finish my last semester at City College of San Francisco and transfer a 4-year university with Computer Science. I do plan to improve the app on Wednesdays at Code for San Francisco. + +**Sebastian:** I would love to take this project to the next level and continue to practice my content management skills. There is a number of things that the project needs however, including a much larger group of people working on stories for the project to make it accurate and up to date, perhaps a professional design team, and a lot of work on the shoes and music tabs. I am in the process of starting my own company to help at-risk transitional age youth in Marin county, Project Clarity, and I could see the two projects intertwining in interesting and meaningful ways. + +![Mellany presents her Fellowship project at Microsoft's Reactor event space.](/img/uploads/mellany-presents-3.jpg "Mellany presents her Fellowship project at Microsoft's Reactor.") + +**Project Name:** Give Back\ +**Project Lead:** Mellany Andrea Almendarez + +**Problem Description:** Homelessness is one of San Francisco’s most important issues. In 2017, there were 7,500 homeless people in SF. I was born and raised in San Francisco so this issue is very personal to me. I have seen friends and family go through homelessness due to the increasing gentrification in the city, and I want to use tech to help solve this problem. + +**Proposed Solution:** I want to address homelessness through tech. I want to be able to connect potential donors and volunteers to homelessness organizations that need the financial help or extra staff by building an app that could help do this. + +_How was the experience of taking a project from concept to prototype? Anything that surprised you along the way?_ + +**Mellany:** It made me realize how much time and effort must truly be put into the project. I had to think about every possible detail and part of the project. From the layout to the coding of the project, I spent a lot of time in the concept stage. So, in a way the project itself was surprising, I had never done something like this before. + +_Do you have any plans now that the Fellowship is done, do you have plans to keep developing the project?_ + +**Mellany:** Right now, I am transitioning into a four-year university, participating in the Uber Career Prep Program, and working as a Program Instructor at . I do intend to keep developing my project throughout the summer on my own time, unfortunately due to my schedule I am not able to attend at C4SF on Wednesday nights. + +**Project Name:** SFPest\ +**Project Leads:** Daniel Guardado, Ajmal Shah + +**Problem Description:** It takes Hunters Point residents 72 hours to get pest service support from when they first report an issue. + +**Proposed Solution:** Build a web app that would assist Hunters Point East/West residents report pests using their mobile devices. + +Daniel and Ajmal worked directly with [Pestec](https://www.pestec.com/), Property Managers, Resident Service Coordinators and public housing residents to design a web app that enables residents to report pest issues in their housing. While they didn't work directly with Brigade volunteers they did use basic civic design principles of designing with the residents, not for the residents of public housing, to help identify those issues that concerned them. + +**About the author:**\ +[Allen Meyer](http://allenmeyerdesign.com/) has been volunteering with the Brigade since 2013 and is currently a visual designer for the San Francisco Human Services Agency. diff --git a/packages/astro/src/content/blog/2020-02-06-code-for-san-francisco-2019-year-in-review.md b/packages/astro/src/content/blog/2020-02-06-code-for-san-francisco-2019-year-in-review.md new file mode 100644 index 0000000..e4be984 --- /dev/null +++ b/packages/astro/src/content/blog/2020-02-06-code-for-san-francisco-2019-year-in-review.md @@ -0,0 +1,64 @@ +--- +image: NDoCH-2019-2.jpg +image_alt: 'Emily Wasserman, team captain leads of National Day of Civic Hacking at GitHub' +title: Code for San Francisco 2019 Year in Review +description: 2019 was a very busy year for the Code for SF community! +pin_to_frontpage: true +image_list_only: true +--- +2019 was a year full of exciting changes for the Code for San Francisco community. We began the year in a new location at Code for America's new headquarters on Mission Street in SoMa, after six years of calling 9th & Minna our home. The new location features lots more meeting rooms, providing space for multiple new projects to spring up and for our existing teams to expand. As core organizers, we focused on our mission of making Code for San Francisco a community space where civic minded individuals from all across San Francisco can come together to have a positive impact on community issues. Volunteers bring the enthusiasm, dedication and creativity. The core team makes sure there’s dinner. + +Our activities for the year included some familiar events such as the National Day of Civic Hacking, but also some new experiments: data jams, panel discussions, project pitches from City of SF Govies, a fellowship program, and more. + +**Events:**\ +Our big events included: + +**Open Data Day:** is an international annual event that promotes awareness and use of open data. Code for SF’s event this year was hosted MicroSoft at their Reactor event space. Our projects leads came together to showcase the data work they are accomplishing: https://codeforsanfrancisco.org/2019/05/01/open-data-day-2019-community-driven-hackathon/ + +**American Planning Association data jam:** focused on SF transit data, in collaboration with members of SF Transit Riders. + +**Caltrain data visualization challenge** + +A set of breakout discussions on the U.N. Sustainable Development Goals with members of nonprofit organizations, co-planned between Code for SF, Ovio, Caravan Studios, and Kintone + +**National Day of Civic Hacking:** our biggest annual event, featured local issues around San Francisco’s housing crisis, one of the Bay Area’s most challenging civic problems. The day brought community members and civic tech enthusiasts to Github’s San Francisco office to hear an array of speakers from the nonprofit and real estate sectors, as well as from academia. The event was designed to include opportunities to both learn and act: in the morning, participants heard from local experts and leaders in housing issues, and in the afternoon, they engaged in project sprints and functional workshops. ([Read the full event report here](https://medium.com/code-for-san-francisco/lessons-on-housing-crises-from-code-for-san-franciscos-national-day-of-civic-hacking-5039ceb33898)) + +[RentCap](https://tenantprotections.org/), a new project, was born at our national Day of Civic Hacking event. The Tenant Protection Act of 2019 will restrict the maximum amount landlords can raise their tenants’ rents. RentCap is creating an informational site for tenants to learn more about their rights, and take action if needed. + +**San Francisco Gov events:**\ +The Code for SF community came together to support San Francisco government on several projects and events: + +**Office of Civic Innovation:** OCI reps workshopped their Civic Engagement tool kit at Hack Night to collect citizen feedback on volunteer opportunities that support our local government. + +**SF Digital Services:** To support the rapidly expanding Digital Services team, the Brigade hosted a recruitment event attended by nearly 100 people. + +**SF Civil Grand Jury:** Brigade members have been working with a Grand Jury member to design a system for tracking Jury projects over time. + +**SF Public Utilities Commission: Rain Guardians:** Members of our UX Research Team designed the Rain Guardians [website](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rainguardians.org%2F&data=02%7C01%7Cscott.mauvais%40microsoft.com%7C854b1f0ce8084822f73a08d6f46f6516%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636965156611403213&sdata=8UTLmC18%2BUcxv6B%2F9%2FzKLWB4GVp6jFXMkyKW3FwUWRI%3D&reserved=0) for the SF Public Utilities Commission. + +**[Adopt-A-Drain](https://adoptadrain.sfwater.org/)** was finally adopted by the PUC! Volunteers had been maintaining the site for the last couple of years. + +**dev/Mission Fellowship:**\ +We partnered with [dev/Mission](https://devmission.org/) to create a Fellowship Program to help mentor underserved young adults in San Francisco. The Fellowship, with support from Uber, is now on its second cohort, and the Fellows are hard at work on projects that aim to reduce waste at restaurants and expand college access for undocumented students. + +**Ongoing Projects:** + +**Open Transit:** puts real data and visualizations into the hands of everyone so that we can all truly understand how our transit system performs and have meaningful conversations about how to make it better. + +**NL Tweets:** are building a user research pipeline tool that mines social media data via API using machine learning. + +**Lane Breach:** released their iOS app on the Apple store + +**Twabler:** was initiated to provide all Code for America brigades with a tool for labeling Twitter data for NLP as part of the NLTweets project, with a longer term goal of generalizing for any data type. + +**Data Science Working Group:** primary purpose is to efficiently assess, inspire, and tackle Code for San Francisco’s data science needs, as well as to help the City and other brigades with their data science needs whenever appropriate. + +**Environmental Reporting project:** monitors government websites within the Environmental Data & Governance Initiative to track changes in what’s being shared and represented, as well as preserve vulnerable sites from deletion. + +**W.O.M.A.N., Inc:** Volunteers worked with a partner at W.O.M.A.N. Inc. to [revamp their online hub](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodeforsanfrancisco.org%2F2019%2F04%2F17%2Fw-o-m-a-n-inc-domestic-violence-referral-center%2F&data=02%7C01%7Cscott.mauvais%40microsoft.com%7C854b1f0ce8084822f73a08d6f46f6516%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636965156611403213&sdata=LWcpgJwB2fS4YgCr7ICdddZECdAOLw%2FJMOCZTM7%2FlBY%3D&reserved=0) for domestic-violence services. + +And finally, a special thanks to MicroSoft who has been a generous supporter of C4SF for the last several years. + +2020 is starting out with a bang! We have projects in the works with the Department of Public Health, the Fire Department and several events. Hope to see you there! + + diff --git a/packages/astro/src/content/config.ts b/packages/astro/src/content/config.ts new file mode 100644 index 0000000..a4e31f3 --- /dev/null +++ b/packages/astro/src/content/config.ts @@ -0,0 +1,14 @@ +import { z, defineCollection } from "astro:content"; + +const blogCollection = defineCollection({ + type: "content", // v2.5.0 and later + schema: z.object({ + title: z.string(), + image: z.string().optional(), + image_alt: z.string().optional(), + }), +}); + +export const collections = { + "blog": blogCollection, +}; diff --git a/packages/astro/src/pages/blog.astro b/packages/astro/src/pages/blog.astro index 21e1291..cb0fd76 100644 --- a/packages/astro/src/pages/blog.astro +++ b/packages/astro/src/pages/blog.astro @@ -1,7 +1,18 @@ --- +import { getCollection } from "astro:content"; import BaseLayout from "@/layouts/BaseLayout.astro"; + +const posts = await getCollection("blog"); --- -

Blog

+ diff --git a/packages/astro/src/pages/blog/[slug].astro b/packages/astro/src/pages/blog/[slug].astro new file mode 100644 index 0000000..a4e78b0 --- /dev/null +++ b/packages/astro/src/pages/blog/[slug].astro @@ -0,0 +1,25 @@ +--- +import { getCollection } from "astro:content"; +import BaseLayout from "@/layouts/BaseLayout.astro"; + +export async function getStaticPaths() +{ + const posts = await getCollection("blog"); + + return posts.map((entry) => ({ + params: { + slug: entry.slug + }, + props: { + entry + }, + })); +} + +const { entry: { render, data: { title } } } = Astro.props; +const { Content } = await render(); +--- + + + + diff --git a/packages/astro/tsconfig.json b/packages/astro/tsconfig.json index 962cc56..1ac3ffd 100644 --- a/packages/astro/tsconfig.json +++ b/packages/astro/tsconfig.json @@ -1,6 +1,7 @@ { "extends": "astro/tsconfigs/strict", "compilerOptions": { + "strict": true, "baseUrl": ".", "paths": { "@/*": [