8000 GitHub - hantvu/columbia-development-tracker-toolkit: toolkit
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

hantvu/columbia-development-tracker-toolkit

 
 

Repository files navigation

Columbia Missourian is building a development tracker toolkit, using Airtable, that anyone can use to create a development tracker for their city.

You can see a more detailed walkthough of how to use this template site to build and manage a development tracker at a local newsroom here.

Before you start

You should already have:

Create your own copy of this site

  • Fork this repository, using the "Fork" button at the top right of this page.
  • You may want to rename your repository to something more meaningful.
  • From a terminal, clone your newly-forked repository to your local computer, using your Git username and repository name instead of the placeholders here:
git clone git@github.com:<my-github-username>/<my-repository-name>.git
  • This should create a new folder, <my-repository-name>, in the current directory.
  • Change into that folder, which is the root directory of your new site:
cd <my-repository-name>

Configure your local copy

  • From a terminal, run npm install in the root directory.
  • Open a text editor: if you're using Visual Studio Code, running code . in the terminal should open the site folder in a new window.
  • Rename the .env.development.example and to .env.development.local, and populate it with your specific environment variables.
  • From a terminal, yarn dev in the root directory: this will start the development server.
  • If you see the toolkit running in your browser, congrats! You can now make changes to the site, or your Airtable, and you should see them live in the site.

Customizing the site

toolkit.config.js

This file sits at the root of your site, and should be used to customize the site. Here is a list of the values in that file, and what they should be:

  • siteTitle: the title of your site.
  • organization: the name of your organization.
  • city and state: The city and state you're based in - this is purely for display purposes!
  • boundingBox: The bounding box of your region. You can find this with bboxfinder.com:
    • You want to zoom to your general region and then copy the Map value from bottom left.
    • Make sure the four numbers are between square brackets ([ and ]), like this:
    • [-83.872890,42.216949,-83.581238,42.345985] would be a good bounding box for Ann Arbor, Michigan.
  • primary, secondary, and tertiary: Three basic colors you can configure the site with.

Deploying the site to Netlify

  • Log in to Netlify with your GitHub account.
  • Link your site's GitHub repository to your Netlify account.
  • Populate your environment variables in Netlify

Environment variables

  • AIRTABLE_API_KEY: The API key for your Airtable account. You can find this on your Airtable account page.
  • AIRTABLE_BASE_ID: The ID of the Airtable base. Find this by clicking "Help" in the top right corner of the Airtable interface, then "API documentation" in the bottom right corner. The base ID will be in green text in the API introduction.
  • AIRTABLE_RECORD_FILTER: The filter to apply to the Airtable base. This is the only value which is pre-populated, as it's designed to work with the example Airtable base. This needs to be an Airtable formula.
  • NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN: The Mapbox access token for your project. You can find this on your Mapbox account page.
  • NEXT_PUBLIC_SUPABASE_URL: The URL of your Supabase instance.
  • NEXT_PUBLIC_SUPABASE_API_KEY: The API key for your Supabase instance. You can find this on your Supabase account page.

Additional functionality

Fetching data from other sources

About

toolkit

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 89.0%
  • CSS 11.0%
0