-
Notifications
You must be signed in to change notification settings - Fork 0
/
_config.yml
53 lines (48 loc) · 1.95 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
# 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 these 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
# '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 }}.
title: Carlos Ramirez III
email: [email protected]
description: > # this means to ignore newlines until "baseurl:"
Write an awesome description for your new site here. You can edit this
line in _config.yml. It will appear in your document head meta (for
Google search results) and in your feed.xml site description.
baseurl: "" # the subpath of your site, e.g. /blog
url: "http://www.carlosramireziii.com" # the base hostname & protocol for your site
twitter_username: cramireziii
github_username: carlosramireziii
github:
url: "carlosramireziii/carlosramireziii.github.io" # Required in order for GitHub pages paths to resolve locally and in production
disqus:
shortname: carlosramireziii
# Build settings
markdown: kramdown
theme: minima
permalink: none
# Plugins
gems:
- jekyll-sitemap
# Site-wide defaults
defaults:
-
scope:
path: "" # all files
type: "posts"
values:
related_posts: true # always show 'related posts' by default
# Environment-specific variables
# NOTE: override these in a custom config file and serve using --config flag
production_analytics_key: HovqibZYJPv9ZOev8ENoUNDDvjh2ZVpK
production_drip_key: 6676535
production_newsletter_key: 3038544