Skip to content

Latest commit

 

History

History
98 lines (57 loc) · 4.75 KB

README.md

File metadata and controls

98 lines (57 loc) · 4.75 KB
Raw

mailchimp subscription local testing

install netlify cli tools

npm i -g netlify-cli

turn off local server and run:

netlify dev

Implementation Details:

https://docs.google.com/document/d/1IcFjxBmZRbTheXbnGTMHMFiG3NOe_ffL3XWnMZnB-4E/edit

Rent Cap

This project is an effort to help Californians figure out whether the Tenant Protection Act of 2019 will protect them from excessive rent increases.

Most renters will be affected, but our goal is to help them answer that question using publically available data based on their address.

Text of the bill

Read more about it

Contributing

This project was started during the 2019 National Day of Civic Hacking through the Code for SF brigade by kylpeacock@gmail.com.

Our project is open-source and under active development, so please get in touch with us and contribute! We have all kinds of ways to contribute, from Copywriting to UX, as well as Front and Back-end development.

Development

Ported from codepen https://codepen.io/reidjs/full/oNNaPaj. Styled with Bootstrap

Adding copy and using the translator object:

Modify the objects in en.json and es.json.

This project uses i18next react initialized as a Provider. Use the translator function t() to wrap text and read in from en.json or es.json.

Available Scripts

In the project directory, you can run:

yarn install

Install dependencies

gatsby develop

Run locally on port 8000

🧐 What's inside?

A quick look at the top-level files and directories you'll see in a Gatsby project.

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

  1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

  2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

  3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

  4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

  5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

  6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

  7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

  8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

  9. LICENSE: Gatsby is licensed under the MIT license.

  10. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

  11. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

  12. README.md: A text file containing useful reference information about your project.

🎓 Learning Gatsby

Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:

  • For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.

  • To dive straight into code samples, head to our documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.