/
settings.yml
283 lines (266 loc) · 8.9 KB
/
settings.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
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
# Landscape2 settings
#
# This settings file allows customizing some aspects of the landscape.
# Foundation (required)
#
# Name of the foundation. This value is used in some labels, so we recommended
# to keep it as short as possible.
#
# foundation: <FOUNDATION_NAME>
#
foundation: JSON Schema
# Url (required)
#
# Url where the landscape will be hosted.
#
# url: <LANDSCAPE_URL>
#
url: https://landscape.json-schema.org
# Analytics (optional)
#
# Analytics providers configuration. When an analytics provider is set up, some
# additional code from the provider will be injected into the web application.
#
# analytics:
# gtm: # Google Tag Manager configuration
# container_id: <CONTAINER_ID> # Landscape web application container ID
#
# Base path (optional)
#
# Base path where the landscape will be hosted. By default the generated
# landscape is prepared to be hosted at the root of the domain. However, if the
# landscape will be hosted in a subpath, this value must be set accordingly.
#
# base_path: /<BASE_PATH>
#
# Categories (optional)
#
# Categories information is read from the `landscape.yml` data file. The way
# categories are displayed in the web application is computed dynamically based
# on the number of categories and subcategories, as well as the number of items
# on each. Sometimes, however, we may want subcategories to be displayed in a
# specific order within a category (this happens often in the Members category).
# In those cases, it is possible to define that order by overriding a category.
#
# This option can also be used to not display one or more subcategories in the
# landscape. To achieve that, we only need to exclude the subcategory from the
# subcategories list when overriding a category.
#
# categories:
# - name: <CATEGORY_NAME>
# subcategories:
# - <SUBCATEGORY1_NAME>
# - <SUBCATEGORY2_NAME>
#
# Colors (optional)
#
# Colors used across the landscape UI. The colors section is optional but, when
# provided, *all colors must be provided*. Colors must be specified using the
# following format: "rgba(<RED>, <GREEN>, <BLUE>, <ALPHA>)".
#
# colors:
# color1: <COLOR1> # Buttons, groups, links
# color2: <COLOR2> # Some highlighted items like filters button, search icon
# color3: <COLOR3> # Participation stats bars, spinners, modal titles
# color4: <COLOR4> # Categories titles in filters, fieldset in filters modal
# color4: <COLOR5> # Categories and subcategories frames (odd)
# color5: <COLOR6> # Categories and subcategories frames (even)
#
colors:
color1: "rgba(0, 107, 204, 1)"
color2: "rgba(255, 0, 170, 1)"
color3: "rgba(96, 149, 214, 1)"
color4: "rgba(0, 42, 81, 0.7)"
color5: "rgba(1, 107, 204, 0.7)"
color6: "rgba(0, 42, 81, 0.7)"
# Featured items (optional)
#
# This section allows highlighting items that match certain criteria. You can
# define a list of rules and the matching items will be featured in a special
# way in the landscape.
#
# Each rule must define a field for the check as well as the values that will
# trigger a match. At the moment the fields supported are:
#
# - maturity
# - subcategory
#
# When a given item's field matches any of the values provided, it will be
# considered a featured item. For each option, it is possible to also define an
# order (which item would be displayed first) and a label for the item.
#
# featured_items:
# - field: subcategory
# options:
# - value: <SUBCATEGORY1_NAME>
# - value: <SUBCATEGORY2_NAME>
#
featured_items:
- field: maturity
options:
- value: graduated
order: 1
label: Graduated
# Footer (optional)
#
# This section allows customizing some aspects of the footer.
#
# footer:
# links:
# facebook: <FACEBOOK_URL>
# flickr: <FLICKR_URL>
# github: <GITHUB_URL>
# homepage: <HOMEPAGE_URL>
# instagram: <INSTAGRAM_URL>
# linkedin: <LINKEDIN_URL>
# slack: <SLACK_URL>
# twitch: <TWITCH_URL>
# twitter: <TWITTER_URL>
# wechat: <WECHAT_URL>
# youtube: <YOUTUBE_URL>
# logo: <LOGO_URL> # Foundation logo featured on the footer
# text: <TEXT> # Copyright notice, for example
#
footer:
links:
github: "https://github.com/json-schema-org"
homepage: "https://json-schema.org/"
linkedin: "https://linkedin.com/company/jsonschema/"
slack: "https://json-schema.org/slack"
twitter: "https://twitter.com/jsonschema"
youtube: "https://www.youtube.com/@JSONSchemaOrgOfficial"
logo: "https://json-schema.org/img/logos/logo-white.svg"
# Grid items size (optional)
#
# Defines the preferred size of the landscape items in the grid mode. When the
# landscape contains many items, it is recommended to use the `small` size.
# However, if there aren't many items, choosing `medium` or `large` may make
# the landscape look nicer. Users will still be able to adjust the items size
# from the UI using the zoom controls.
#
# grid_items_size: <small|medium|large>
#
grid_items_size: large
# Groups (optional)
#
# In some cases, specially when a landscape contains lots of items, it may be
# interesting to organize them in groups. Each group will be displayed on a
# different tab in the landscape web application. Each entry must contain the
# name of the group (it will be displayed as is) and a list with the categories
# (as defined in the landscape.yml data file) that will be part of this group.
#
# groups:
# - name: <GROUP_NAME>
# categories:
# - <CATEGORY1_NAME>
# - <CATEGORY2_NAME>
#
groups:
- name: JSON Schema Ecosystem
categories:
- Adopters
- Sponsors
- Tools
- name: Adopters
categories:
- Adopters
- name: Sponsors
categories:
- Sponsors
- name: Tools
categories:
- Tools
# Header (optional)
#
# This section allows customizing some aspects of the header.
#
# header:
# links:
# github: <GITHUB_URL>
# logo: <LOGO_URL> # Foundation logo featured on the header
#
header:
links:
github: "https://github.com/json-schema-org/landscape"
logo: "https://json-schema.org/img/logos/logo-blue.svg"
# Images (optional)
#
# Urls of some images used in the landscape UI.
#
# images:
# favicon: <FAVICON_URL>
# open_graph: <OPEN_GRAPH_IMAGE_URL>
#
images:
favicon: "https://raw.githubusercontent.com/json-schema-org/website/main/public/favicon.ico"
# Name of the members category (optional)
#
# Landscapes usually have a special category dedicated to the members of the
# corresponding foundation. It is possible to use any name for that category,
# but it is important that we define it here as there are some special
# operations that depend on it.
#
# members_category: <CATEGORY_NAME>
#
# Osano (optional)
#
# Osano cookies consent form configuration. When the Osano configuration is
# provided, some additional code will be injected into the web application.
#
# The `customer_id` and `customer_configuration_id` fields values can be
# obtained from the url in the configuration script code available on the Osano
# site:
#
# https://cmp.osano.com/<CUSTOMER_ID>/<CUSTOMER_CONFIGURATION_ID>/osano.js
#
# osano:
# customer_id: <CUSTOMER_ID>
# customer_configuration_id: <CUSTOMER_CONFIGURATION_ID>
#
# Screenshot width (optional)
#
# Width of the landscape screenshots automatically generated (in pixels).
# Screenshots won't be taken if this value is not provided.
#
# screenshot_width: <WIDTH_IN_PIXELS>
#
screenshot_width: 1500
# TAGs (optional)
#
# Projects items can specify which TAG owns them in the `landscape.yml` file
# (by using the `tag` field in the `extra` item's section). However, sometimes
# this information is not available at the item level. This configuration
# section provides a mechanism to automatically asign a TAG to projects items
# based on the categories and subcategories they belong to.
#
# For example, we can define that all projects in the category <CATEGORY1> are
# owned by <TAG1>. When the items are processed, the corresponding TAG will be
# set in the items that match the rule defined. The TAG defined at the item
# level always takes precedence, so when it's present it won't be replaced.
#
# NOTE: TAGs names should only use lowercase case letters and hyphens (no
# spaces or other characters), and should not be prefixed with "tag". The
# subcategories field is optional and, when omitted, all of them will be
# included.
#
# tags:
# <TAG1>:
# - category: <CATEGORY1>
# subcategories:
# - <SUBCATEGORY1>
# - <SUBCATEGORY2>
# <TAG2>:
# - category: <CATEGORY2>
#
# Upcoming event (optional)
#
# This section allows configuring an upcoming event that will be featured on
# the landscape web application. Expired events won't be displayed.
#
# upcoming_event:
# name: <NAME> # Event name (required)
# start: <START_DATE> # Start date: (required, format: YYYY-MM-DD)
# end: <END_DATE> # End date: (required, format: YYYY-MM-DD)
# banner_url: <URL> # Event banner image url (required, recommended dimensions: 2400x300)
# details_url: <URL> # Event details URL (required)
#