-
Notifications
You must be signed in to change notification settings - Fork 4
/
_config.yml
146 lines (128 loc) · 5.35 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
# The title and slogan are for the entire site.
# The "slogan" appears directly below the title, in smaller italics.
# The "image" is a URL that is relative to your site root.
# The title and image are required. If you do not want a slogan, change it to
# "null" (_without_ the quotes).
title: "Globus @ Stanford"
slogan: "Research data management simplified. For you. For free."
image: "/assets/globus_square.png"
site-title: "Globus @ Stanford"
googleID : G-YDZJ9JMKTT
# markdown: GFM
# This section has site owner information. It is used in a few places:
# * Page metadata, used by search engines and social tools.
# * The "Connect With Us" block at the bottom of each page.
owner:
# The owner name must be provided.
name: "Stanford Research Computing"
# Next up is social media handles. If you don't have one, use the word
# "null", but without the quotes.
# If you have a Facebook page, put your account name here.
# Example, if your Facebook URL is https://facebook.com/xyz, put "xyz".
facebook: null
# If you have a Google Plus page, put in the page ID number.
gplus: null
# If you have a Twitter handle, put it here, _without_ the leading at-sign.
twitter: "StanfordCompute"
# If you have an Instagram account, put it here.
instagram: null
# If you have a YouTube account, put your account name here.
youtube: null
# If you have a GitHub org, put the name here.
github: "stanford-rc"
# If you have a Slack (which your visitors can join), put the workspace name
# here. Example: If you are at xyz.slack.com, put "xyz".
slack: null
# If you would like to use the Google Search Console (also known as Google
# Webmaster Tools) with your site, you can provide your
# 'google-site-verification' code here. See the instructions below:
#
# NOTE: Do not enable this until after your site is live at your preferred
# domain!
#
# 1) Go to https://google.com/webmasters/tools, signing in with your
# Stanford Google account.
# 2) Choose "Add A Property", and paste in your web site's URL.
# 3) When asked for verification, go to the "Alternate methods tab" and
# choose "HTML tag".
# 4) Examine the <meta> tag that Google wants you to add. The tag's name
# should be "google-site-verification". Take the tag's content, and put
# it here.
#
# For example, if your tag says...
# <meta name="google-site-verification" content="12545asbcdgre" />
# ... then you would put in "12345asbcdgre" (_including_ the quotes).
# 5) Push your changes to GitHub, and wait a few minutes.
# 6) Go back to your web browser, and click the "Verify" button.
# If Google can't verify your site, wait a few minutes and try again.
google-site-verification: "p6RHSiRbb4jA-IduSWo_kMGNiMYRXKDEwxB6Zfx468g"
# For pages which live on GitHub, the _de rigeur_ thing to do is to provide
# users an opportunity to improve your site. The idea is, if people see that
# something is wrong with the page, giving them the ability to fix it
# themselves may make them more likely to do it.
#
# If this option is set to a string, that string will appear in the
# bottom-right of every page, with a link to the source file on GitHub. To
# disable this, change the setting to "null" (without the quotes).
#
# NOTE: When you are testing changes locally, the link URL will not be
# accurate. It will only be correct when pages are being served from GitHub.
#
github-edit-text: "Improve This Page"
# The index.html page of the site defaults to being your site's "blog page".
# (Altough the example calls it "Announcements", it's kindof the same thing.)
# By default, the full list of posts are split into pages of three posts per
# page. For each additional page, a complete copy of index.html will be
# created, but with a different list of posts.
#
# You can change the number to whatever you want. If you want to disable
# pagination entirely (and so have all posts appear on the main page), comment
# out the line below.
paginate: 3
paginate_path: "/announcements/page:num/"
# These defaults apply when a matching page variable is not set.
# NOTE: You should set most of these in page-specific YAML.
defaults:
-
scope:
path: ""
values:
title: "Page Title"
description: null
layout: default
sitemap: true
toc: true
sidebar-box: null
social:
# The title to use when Twitter et al show a link to your site.
# When set to null, Jekyll will generate the string
# "PAGE_TITLE — SITE_TITLE".
title: Globus at Stanford
# The image to show when someone expands a Twitter post with your page
# linked. This should be a path relative to your site root. If not
# set, your site's image will be used instead.
image: null
# These are Jekyll plugins that we enable.
# NOTE: We can only use plugins that GitHub makes available.
# The list is here: https://pages.github.com/versions/
plugins:
- jekyll-paginate
- jekyll-sitemap
- jekyll-titles-from-headings
# This is a list of files that should be excluded from the _site directory.
exclude:
- Gemfile
- Gemfile.lock
- LICENSE.txt
- README.md
# - jekyll-theme-stanford-lagunita.gemspec
- vendor
# These are some Jekyll defaults, which should be left alone.
timezone: America/Los_Angeles
encoding: utf-8
safe: true
# theme: src
lockup_line2: Globus
lockup_link: /index.html
lockup_line1: Research Computing
lockup_modifier_class: su-lockup--option-b