Skip to content

zagorvix/opendatahandbook

This branch is 12 commits behind okfn/opendatahandbook:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Stephen Abbott Pughtlacoyodefrijol
Stephen Abbott Pugh
and
Jun 27, 2019
913b295 · Jun 27, 2019
Jul 10, 2016
May 22, 2018
May 22, 2018
Aug 17, 2016
Aug 19, 2015
Jun 27, 2019
Aug 17, 2016
Aug 1, 2017
Aug 9, 2018
Aug 16, 2016
Aug 15, 2016
Jun 27, 2019
Aug 12, 2015
Jun 27, 2019
Feb 18, 2017
Jul 13, 2016
May 26, 2017
Feb 9, 2015
May 13, 2015
May 22, 2018
Jul 27, 2017
Feb 24, 2015
Feb 24, 2015
Feb 4, 2015
Aug 19, 2015
Feb 24, 2015
Feb 24, 2015

Repository files navigation

opendatahandbook-v2

Repository of http://opendatahandbook.org/

This is a Jekyll based site, with pages written in HTML and Markdown (specifically Kramdown), with Markdown being used where possible for ease of editing.

Editors

Please see the Contribute section of the site for further instructions.

Developers

Dependencies

Information architecture

There are four sections of content, implemented as simple Jekyll pages: guide, value-stories, glossary, and resources.

Some sections have translations. These are implemented by adjacent directories, where the name of the directory is the locale of the translation.

Guide

The narrative content of the Open Data Handbook.

Value Stories

A collection of stories demonstrating examples of open data wins.

Glossary

A glossary explaining terms used in the Open Data Handbook.

Resources

Additional resources for the Open Data Handbook.

Working with the glossary

Each glossary (meaning, each glossary translation), is made of three components:

  • A 'glossary.html' layout template
  • A 'glossary/{lang}/index.md' page, which uses the glossary layout to render a list of glossary terms in the correct language
  • A 'glossary/{lang}/terms/' directory, which contains an entry for each glossary term. Each entry is the slugified name of the English version of the term.

Currently, the English glossary has been organized. To expand this pattern to other languages:

  • Copy the English terms directory into your target language directory
  • If your current index.md has translated glossary terms, then add them to the appropriate page under 'terms', replacing the English text that was copied over from 'en'.
  • Then, replace your target language's index.md file with the 'en' one, changing the lang value to that of your target language.

Branches

  • gh-pages - pre-built live site
  • master - site in Jekyll form
  • dev - minimal content, to speed up building (for development)
  • theme - no site specific content, used to create new sites

About

Open Data Handbook v2

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • CSS 58.6%
  • HTML 30.0%
  • Python 9.1%
  • JavaScript 2.3%