Code For Tulsa, an official brigade of Code For America, hosts a website and blog at codefortulsa.org. This is that website's working repository.
The Code for Tulsa website aims to be a beacon for engagement in civic tech volunteer opportunities within the greater Tulsa area.
The site is currently undergoing a major update. See below for more information
- Figma Mockup
- Project Board
- Staging Environment
- Slack Channel (Techlahoma) - #ug-code-for-tulsa-website
This repo started as an effort to modernize the core site and create a dynamic working environment that facilitates additional contributions from current and future volunteers of all backgrounds.
In the early stages of this redesign project, the requirements were simple: create a web blog that facilitates content contributions from non-technical volunteers. Because of this, the project was initially bootstrapped as a static Gatsby site.
Soon after, discussions began about integrating other resources utilized by the organization, such as Twitter, Slack, Meetup, etc. It was agreed that a more flexible framework was desired to keep up with the dynamic demands of the organization and provide broader variety for volunteer engagement. The project was migrated to Next.Js in January 2022 and adapted for deployment on serverless platforms.
While the infrastructure now exists for more complex features, every effort should be made to implement them in as low resource/cost-effective a manner as possible by using static or incremental generation, external APIs, and client-side offloading wherever possible.
Install the LTS version of Node:
# via nvm (recommended) https://github.com/nvm-sh/nvm
https://github.com/nvm-sh/nvm
# via pre-built installer
https://nodejs.dev/download/Install Yarn:
npm install --global yarnClone the repo and cd into the directory:
git clone https://github.com/codefortulsa/website.git ./code-for-tulsa-website
cd ./code-for-tulsa-websiteRun the app with docker compose (the first time you run this it will have to build images and install dependencies which could take a few minutes)
docker-compose up- add
-dflag to run container(s) in the background. - if running in the background, you can start the logs up with
docker-compose logs -f(the-fwill keep the logs running, omit it for a one time print)
Install packages & start the dev server:
< 8000 div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="yarn install yarn dev">yarn install yarn dev