This is a website for the My LA2050 ideas archive–a searchable database of organizations and projects from the maker, grants and activation challenges for 2013-2020.
- Public API
- How to make changes
- How to edit an organization
- How to hide an organization
- How to add an image
- How to see a preview of your changes
- How to develop locally
- Handy guides
github.com/la2050/archive/deployments
The data for the archive is available as downloadable CSV spreadsheet files and in JSON format.
The archive website is published with GitHub Pages & Netlify and the files are generated with Jekyll.
As you make changes and commit/push them to GitHub, the website will automatically update.
For example, if you edit the about page on GitHub, and then press the “Commit changes” button–you should see your changes on the about page of the website within a few minutes.
- Find the organization you wish to edit in the organizations folder.
The files in these folders correspond to a web address on the archive website. For instance, the organization located at https://archive.la2050.org/homeboy-industries/ gets its content from a file named homeboy-industries.md
- Select the organization and then press the edit button–for example, 826LA.
The organization files are written in the YAML language. The files contain a list of names and values, each separated by a colon. The names serve a similar purpose to what columns do in a spreadsheet. For example:
name: value
another_name: another_value
You can double-check that your changes are correct by copying and pasting them into the YAML Validator.
- Make your changes, and then press the “Commit changes” button.
You can also describe your changes in the fields just above the “Commit changes” button (this adds a note in the project history).
You can follow these same steps to edit one of the projects.
While editing an organization file, look for this line:
published: true
To hide the organization, set the value of published to false:
published: false
To show the organization again, set the value of published back to true.
You can follow these same steps to hide or show one of the projects.
If you want to add an image (or any file) to the website, you can upload it to one of the folders on GitHub.
The uploads folder might be a good choice, if you’re unsure where to put a file.
Once you’ve chosen a folder, follow these steps:
-
Press the
Upload filesbutton -
Use the uploader to upload your files
-
Press the
Commit changesbutton
It’s best to use lowercase letters and dashes instead of spaces for your filename. For example: womens-march-la.jpg.
Once your file has been uploaded it will be available at a web address that corresponds to the folder and filename that you chose. For example:
/uploads/womens-march-la.jpg
To use this on the website, you can create an image with markdown:
If you’d like to see how your changes will look on the website before making them public, you can work in the staging branch–a copy of the website files, that’s published at https://staging-archive.la2050.org
You can make edits in the staging branch and commit them just as you would normally. They’ll automatically appear on the staging website within a few minutes.
Once you’re happy with how your changes look on the staging website, you can copy them over to the public website (the master branch) using a pull request. Here are the steps:
- Press the “new pull request” button.
https://github.com/la2050/archive/pull/new/staging
-
Write a title for your pull request (this is optional).
-
Press the “create pull request” button.
-
And then, press the “merge pull request” button.
-
And lastly, press the “confirm merge” button.
If you want to see a preview of your changes while you work, you can run a Jekyll server on your computer. Installing Ruby and Jekyll is a good place to start.
After you have Jekyll installed, you can clone (download) this project with Git or GitHub Desktop. And then you can start Jekyll:
jekyll serve
If Jekyll is taking a long time to rebuild after changes, you may find it helpful to use incremental mode. Here’s an example that also rebuilds the site first to ensure everything is up to date, and includes a host option to make the site available on your local network for testing on mobile devices.
jekyll build && jekyll serve --host=0.0.0.0 --incremental --skip-initial-build