bastian/debyl-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Excluded public and static directories.

Browse Source
This commit is contained in:
Bastian de Byl
2017-12-26 14:54:01 +01:00
parent 385383a6c3
commit e69a80d1b0
3 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored
View File

@@ -1,2 +1,4 @@
themes/* themes/*
test.md test.md
public/*
static/*

5
config.toml
View File

@@ -1,5 +1,5 @@
# Tranquilpeak # Tranquilpeak
baseURL = "https://basdb.net/" baseURL = "http://bdebylnet-cdn.s3-website-us-east-1.amazonaws.com"
languageCode = "en-us" languageCode = "en-us"
defaultContentLanguage = "en-us" defaultContentLanguage = "en-us"
title = "basdb" title = "basdb"
@@ -23,6 +23,7 @@ canonifyurls = true
job = "Software Engineer" job = "Software Engineer"
location = "New England" location = "New England"
# Your profile picture # Your profile picture
gravatarEmail = "bastiandebyl@gmail.com"
# picture = "https://cdn1.iconfinder.com/data/icons/ninja-things-1/1772/ninja-simple-512.png" # picture = "https://cdn1.iconfinder.com/data/icons/ninja-things-1/1772/ninja-simple-512.png"
# Menu Configuration # Menu Configuration
@@ -121,7 +122,7 @@ canonifyurls = true
# Current image is on AWS S3 and delivered by AWS CloudFront. # Current image is on AWS S3 and delivered by AWS CloudFront.
# Otherwise put your image in folder `static/_images/` (development) or in `source/assets/images/` if you can't or don't want to build the theme, # Otherwise put your image in folder `static/_images/` (development) or in `source/assets/images/` if you can't or don't want to build the theme,
# and use relative url : `your-image.png` # and use relative url : `your-image.png`
coverImage = "cover.jpg" coverImage = "https://s3.us-west-2.amazonaws.com/basdb-static-content/site-static/img/cover.png"
# Display an image gallery at the end of a post which have photos variables (false: disabled, true: enabled) # Display an image gallery at the end of a post which have photos variables (false: disabled, true: enabled)
imageGallery = true imageGallery = true

7
content/post/humble-beginnings.md
View File

@@ -3,9 +3,8 @@ title: "Humble Beginnings"
date: 2017-12-21T01:42:57-05:00 date: 2017-12-21T01:42:57-05:00
categories: ["Blog"] categories: ["Blog"]
tags: ["code"] tags: ["code"]
draft: true thumbnailImagePosition: top
thumbnailImagePosition: left thumbnailImage: "/img/humble-beginnings/main.png"
thumbnailImage: "https://s3-us-west-2.amazonaws.com/basdb-static-content/site-static/img/main.png"
--- ---
After much deliberation I've finally decided to go with the [**Tranquilpeak**](https://github.com/kakawait/hugo-tranquilpeak-theme) theme. However, before this I ran into a slew of issues with the badly ported [**Tracks**](https://github.com/ageekymonk/hugo-tracks-theme) theme from WordPress After much deliberation I've finally decided to go with the [**Tranquilpeak**](https://github.com/kakawait/hugo-tranquilpeak-theme) theme. However, before this I ran into a slew of issues with the badly ported [**Tracks**](https://github.com/ageekymonk/hugo-tracks-theme) theme from WordPress
<!--more--> <!--more-->
@@ -18,7 +17,7 @@ If you want a general overview, feel free to check out the relevant [commit](htt
The first thing I noticed was that the navigation bar seemed a bit off. The first thing I noticed was that the navigation bar seemed a bit off.
{{< image classes="center" src="https://s3-us-west-2.amazonaws.com/basdb-static-content/site-static/img/header-problem.png" title="Navbar Issue" >}} {{< image classes="center" src="/img/humble-beginnings/header-problem.png" title="Navbar Issue" >}}
The links show as numbers and attempt to link to `/0`, `/1`, and `/2` which lead to 404s. This didn't seem like the intended functionality. It turned out to be a problem with the usage of the following variable: `.Site.Sections` The links show as numbers and attempt to link to `/0`, `/1`, and `/2` which lead to 404s. This didn't seem like the intended functionality. It turned out to be a problem with the usage of the following variable: `.Site.Sections`