This repository has been archived by the owner on May 3, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy path_config.yml
147 lines (140 loc) · 5.11 KB
/
_config.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
# Welcome to Jekyll!
#
# This config file is meant for settings that affect your whole blog, values
# which you are expected to set up once and rarely edit after that. If you find
# yourself editing this file very often, consider using Jekyll's data files
# feature for the data you need to update frequently.
#
# For technical reasons, this file is *NOT* reloaded automatically when you use
# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
# Site settings
# These are used to personalize your new site. If you look in the HTML files,
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
# You can create any custom variable you would like, and they will be accessible
# in the templates via {{ site.myvariable }}.
# Contains the url of your site as it is configured in the _config.yml. For example, if you have url: http://mysite.com in your configuration file, then it will be accessible in Liquid as site.url. For the development environment there is an exception, if you are running jekyll serve in a development environment site.url will be set to the value of host, port, and SSL-related options. This defaults to url: http://localhost:4000.
# the base hostname & protocol for your site, e.g. http://example.com
source: source
url: https://lab.technologiestiftung-berlin.de
title: Ideation & Prototyping Lab DEPRECATED USE site.data.meta.title
email: roboter@tsb.ara.uberspace.de
description: >- # this means to ignore newlines until "baseurl:"
Das Ideation & Prototyping Lab ist das Entwicklungslabor der Technologiestiftung Berlin.
Als gemeinnützige Institution arbeiten wir in offenen Innovationsprozessen an der Gestaltung des digitalen Wandels und erproben neue Werkzeuge für ein besseres Leben in Städten.
# baseurl: "" # the subpath of your site, e.g. /blog
twitter_username:
github_username: tsboter
# Front Matter Defaults
# Using front matter is one way that you can specify configuration in the pages and posts for your site. Setting things like a default layout, or customizing the title, or specifying a more precise date/time for the post can all be added to your page or post front matter.
# Often times, you will find that you are repeating a lot of configuration options. Setting the same layout in each file, adding the same category - or categories - to a post, etc. You can even add custom variables like author names, which might be the same for the majority of posts on your blog.
# Instead of repeating this configuration each time you create a new post or page, Jekyll provides a way to set these defaults in the site configuration. To do this, you can specify site-wide defaults using the defaults key in the _config.yml file in your project’s root directory.
# https://jekyllrb.com/docs/configuration/front-matter-defaults/
defaults:
-
scope:
path: "" # an empty string here means all files in the project
values:
lang: "de"
-
scope:
path: ""
type: "team_de"
values:
lang: "de"
layout: "team-detail"
-
scope:
path: ""
type: "team_en"
values:
lang: "en"
layout: "team-detail"
-
scope:
path: ""
type: "datasets_de"
values:
lang: "de"
layout: "dataset-detail"
-
scope:
path: ""
type: "datasets_en"
values:
lang: "en"
layout: "dataset-detail"
# Build settings
# Kramdown is the default Markdown renderer for Jekyll.
# https://jekyllrb.com/docs/configuration/markdown/#kramdown
# For more details about these options have a look at the Kramdown configuration documentation. https://kramdown.gettalong.org/options.html
markdown: kramdown
kramdown:
input: GFM
auto_ids: true
parse_block_html: true
footnote_backlink: '↑'
# https://kramdown.gettalong.org/syntax_highlighter/rouge.html
syntax_highlighter: rouge
# Collections
# Collections are a great way to group related content like members of a team or talks at a conference.
# https://jekyllrb.com/docs/collections/
collections_dir: _collections
# host: 127.0.0.1
# host: localhost
collections:
team_de:
output: true
permalink: /team/:name/de/
team_en:
output: true
permalink: /team/:name/en/
datasets_en:
output: true
permalink: /datasets/:name/en/
datasets_de:
output: true
permalink: /datasets/:name/de/
plugins:
# - jekyll-feed
- jekyll-sitemap
- jekyll-paginate
- jekyll-redirect-from
whitelist:
- jekyll-redirect-from
- jekyll-sitemap
- jekyll-paginate
# sass:
# sass_dir: assets/_scss
# style: compressed
# Exclude from processing.
# The following items will not be processed, by default. Create a custom list
# to override the default setting.
exclude:
- node_modules
- vendor/bundle/
- vendor/cache/
- vendor/gems/
- vendor/ruby/
- vendor
- Gemfile
- Gemfile.lock
- .gitignore
- .git
- .asset-cache
- _static-site
- .sass-cache
- node_modules
- assets/js/src
- assets/_scss/
- assets/assets/css/index.scss
- webpack.config.js
- package.json
- README.md
- ignore
- vendor
- notes
paginate: 5
paginate_path: "blog/page:num"
webrick:
headers:
Access-Control-Allow-Origin: "*"