Skip to main content

Community projects

Built by the flock. For the flock.

Every community project is open source. Browse the repos, pick an issue, and open your first pull request.

The repos

Nine things shipped. So far.

  • philaconvalley/website

    Website

    The site you're on. Philadelphia's tech community home, open for anyone to improve.

    • Astro
    • Tailwind
    • Alpine.js
    5 good first issues
  • philaconvalley/projectionMapper

    projectionMapper

    A projection mapping starter template, built for PATCH 003: Projection Mapping Lab.

    • p5.js
    • PATCH 003
    5 good first issues
  • philaconvalley/community-handbook

    Community Handbook

    Where our philosophy, values, principles and governance live, written in the open.

    • Docs
    • Governance
    2 good first issues
  • philaconvalley/shoppingDebateChromeExtension

    Shopping Debate

    A Chrome extension where three AI personalities argue about your purchase before you check out.

    • Chrome extension
    • AI
    2 good first issues
  • philaconvalley/djVisualizer

    djVisualizer

    A real-time audio visualizer and effects processor for DJs.

    • Web Audio API
  • philaconvalley/owlhacks-timer

    owlhacks-timer

    A countdown timer for hackathon demos, built live at OwlHacks '26.

    • Built live
  • philaconvalley/discord-task-bot

    discord-task-bot

    Task assignments, due-date reminders and Scheduled Event creation, right inside Discord.

    • Discord bot
  • philaconvalley/locked-groove

    locked-groove

    An open-source engine for continuous visual internet radio, where every listener stays synced to the same second.

    • Streaming
  • philaconvalley/door-checkin

    door-checkin

    Tap an NFC tag at the door, post a Discord notification, and land on a welcome page.

    • NFC
    • Webhook

New to open source?

Look for the good first issue label.

Those issues are picked for first-timers. Our six-step walkthrough gets you from fork to pull request.

Your first pull request

Six steps. Practice on our repo.

Try it here first, on the website you're looking at, before you do it anywhere else.

  1. Fork it

    Your own copy, under your account. Nothing here touches the live site.

    github.com/philaconvalley/website → Fork
  2. Clone it

    Pull it down to your machine so you can open the files.

    git clone https://github.com/YOUR-USERNAME/website.git
    cd website
    npm install
  3. Make a branch

    Never work on main. Give your change its own branch.

    git checkout -b fix/readme-typo
  4. Change something small

    A typo, a dead link, a stale line. Small is the point. Build before you commit, so you know nothing broke.

    npm run build
  5. Commit and push

    Say what changed, not how you changed it.

    git add README.md
    git commit -m "Fix typo in README"
    git push origin fix/readme-typo
  6. Open the PR

    GitHub shows a Compare and pull request button. Set the base branch to main. Someone from the flock will review it.

    That's it. You're a contributor.

Built something cool?

Made it at one of our nights or on your own? Send it our way and we'll show it off.

The PhilaCon Valley pigeon standing on a keyboard, with the Philadelphia skyline behind it