<commit_before># Geo Tales mobile website

Current status: Beta

## Building stories

The mobile web app is available at <http://geo-tales.github.io/mobile-app/>. To
create a story, create a JSON file with the format described below. You can
publish the file as a public or a secret at <https://gist.github.com>. To
play the story, open the mobile web app with the JSON files "raw" URL like
this:

    http://geo-tales.github.io/mobile-app/?story={gist-json-file-raw-url}

## Story file format

Check out [the tour.json file][tour] for an example.

Stories are described in JSON files. An example can be found in
`public/all-screens.json`. Each JSON file must contain exactly one JSON object
with these properties:

- `locations`: An object defining locations where the key is the identifyer of
  the location and the value is an object defining the location:
    - `type`: A string defining the location type. Can be `circle` or
      `polygon`. The other valid fields of the object depend on the type.
- `screens`: An object defining screens where the key is the identifyer of the
  screen and the value is an object defining the screen:
    - `type`: A string defining the screen type. Can be `text`, `choices`,
      `navigate` and `finish`. The other valid fields of the object depend on
      the type.<commit_msg>Use https URLs for mobile app since location API requires it<commit_after># Geo Tales mobile website

Current status: Beta

## Building stories

The mobile web app is available at <https://geo-tales.github.io/mobile-app/>. To
create a story, create a JSON file with the format described below. You can
publish the file as a public or a secret at <https://gist.github.com>. To
play the story, open the mobile web app with the JSON files "raw" URL like
this:

    https://geo-tales.github.io/mobile-app/?story={gist-json-file-raw-url}

## Story file format

Check out [the tour.json file][tour] for an example.

Stories are described in JSON files. An example can be found in
`public/all-screens.json`. Each JSON file must contain exactly one JSON object
with these properties:

- `locations`: An object defining locations where the key is the identifyer of
  the location and the value is an object defining the location:
    - `type`: A string defining the location type. Can be `circle` or
      `polygon`. The other valid fields of the object depend on the type.
- `screens`: An object defining screens where the key is the identifyer of the
  screen and the value is an object defining the screen:
    - `type`: A string defining the screen type. Can be `text`, `choices`,
      `navigate` and `finish`. The other valid fields of the object depend on
      the type.
{'fraction_non_alphanumeric': 0.07735217552993678, 'fraction_numerical': 0.0, 'mean_word_length': 3.662045060658579, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4748753', 'n_tokens_mistral': 739, 'n_tokens_neox': 713, 'n_words': 393}