This code is no longer used to power the Open Ownership website. Instead we have moved to a Wagtail-powered content management system. The code for the current website can be found at https://github.com/openownership/openownership.org-wagtail

OpenOwnership.org

This repo contains the main Open Ownership website which lives at: https://www.openownership.org.

The site is built with Jekyll, hosted by Netlify with content managed by Siteleaf and images served by Imgix.

Some data and pages are built via Python scripts which pull data from our organisational Notion account, via GitHub actions configured in this repository

Prequisites

1. Install Ruby, bundler, Node.js and yarn at their latest versions

Local development

1. Clone the github repository
2. bundle install to install the necessary ruby gems for Jekyll
3. yarn install to install the frontend dependencies
4. npm run watch to watch sass and js iles for changes and re-compile them, or npm run build to build them once.
5. bundle exec jekyll serve to run a local jekyll server
6. Open http://localhost:4000

The site code is housed in the master branch. New changes should be committed to a new branch, before being merged back into master.

How this all works

• Siteleaf keeps a copy of the code from the master branch.
  • Every time it is edited in either place, Siteleaf ensures a sync.
• When selecting to publish in Sitelaf, commits on master are merged to the gh-pages branch.
  • This branch is compiled using Jekyll by GitHub (but we don't do anything with this output).
• Netlify notices a commit on the gh-pages branch.
  • Netlify also compiles this branch using Jekyll and deploys the output to its CDN.
  • openownership.org's DNS is managed by Netlify. The live domain points to the files on their CDN.
• Imgix pulls live image files from openownership.org.

Images

• Images are uploaded by Siteleaf to the /uploads folder, so end up at openownership.org/uploads/...
• When adding image URLs to source code for a page, use the jekyll/imgix plugin to convert these into URLs that point to Imgix rather than to the original domain:
  • The plugin provides a filter that does this: {{ variable_containing_original_image_url | imgix_url }}
  • Rendering options should be added, see the plugin's documentation.

Automated page development

1. Install Python 3.5 or greater
2. Make a virtualenv: python3 -m venv venv
3. Activate it: source venv/bin/activate
4. Install the python requirements: pip install -r scripts/requirements.txt
5. Create .env and set some environment variables in it:

[email protected]
NOTION_PASSWORD=password

Generally you can run each python file in /scripts directly, e.g.

• python scripts/update_map.py

These will make some changes to files in jekyll's folders, which you can then view with git diff, commit, etc.

Adding icons to symbol-defs.svg

• Convert to SVG with https://image.online-convert.com/convert-to-svg
  • You may have to tweak the black/white level to get some light colours to come out
• Open in Inkscape, select all and resize to max 400px wide
• With everything selected, reduce document size to selection size
• Save as SVG
• Run exported SVG through https://jakearchibald.github.io/svgomg/ to trim all the cruft (prefer viewBox, remove styles the only non-standard options)
• Copy and paste the paths from the result into a new symbol in symbol-defs.svg
• Add the viewBox attribute into the symbol from the SVG

Deploying changes to production

1. Merge the branch you've been working on into master
2. Wait for Siteleaf to sync the changes from Github
3. Launch a preview in Siteleaf (and generally check you haven't broken any of the CMS setup if your changes have touched fields, content, etc).
4. When you're happy with the preview, publish changes in Siteleaf.
5. Wait for Netlify to pick up the changes in Github and deploy them.