Commit b3494e18 authored by Valvin's avatar Valvin
Browse files

test de la génération de gitlab pages sans sous module git

parent ddf4376a
Pipeline #28026 passed with stages
in 18 seconds
......@@ -3,7 +3,7 @@ baseurl = ""
themesDir = "./themes"
languageCode = "fr-FR"
title = "Le Blog de Valvin"
theme = "cactus"
theme = "cactus-withoutsubmodules"
# Enter your tracking code to enable Google Analytics
googleAnalytics = ""
# Disable comments by leaving disqusShortname empty
# Changelog
## Release v1.1.1 - 04th September 2017
- [6f818c5]( Ordered lists are now styled
- [9fb2a23]( adds support for subtitles in pages that can be defined with `.Description` in the front matter
-[a0db308]( widens the content column to improve the readability of code examples
- [5108c87]( loads FontAwesome from Bootstrap's CDN instead of using the local file.
## Release v1.1 - 26th April 2017
*In the future new additions and changes will be assigned to version numbers rather than dates.* This allows you to track changes in a better fashion. The state of this theme before this release has been assigned to v1.0.
**Some changes and additions listed below require Hugo v0.20 or higher.** Consider to update Hugo to a newer as well if necessary.
### Fixes:
[34f8cf2]( fixes display issues of the about page that occured in Hugo v0.18 and higher due to the way how Hugo treats sites as a page of different kinds. **It's required to rename `content/about/` to `content/about/`**.
### Improvements
- [931eb53]( improves the generation URLs and linkage of pages
- [9b358a9]( uses block templates to reduce redundancy
- [dd67ac4]( adds support for linking pages in the main menu
### Deprecations
- [fa3c87d]( replaces .Now which was deprecated in Hugo v0.19
- [c618828]( deprecates the `params.about` config option
- [1b6b863]( deprecates the option to hide single pages with the `hidden = true` front matter option. Use `draft = true` instead
## 4th January 2016
### Fontawesome as option for social icons in footer
You can now use Fontawesome as alternative to the Mono social icons. Look [here]( for more instructions.
[Show me the diff](
### Hide pages
Pages can now be hidden by adding `hidden = true` to the frontmatter. The pages are still built but they will not appear in the post in on the homepage.
[Show me the diff](
## 7th December 2015
### Social link icons
Social links with icons can be enabled replacing the copyright field in footer. Configure the style and links in `config.toml`.
## 26th November 2015
Hugo v0.15 is required in order to run the theme with the changes listed below:
### Google Analytics
The setup of Google Analytics changed slighty due to the switch to Hugo's built-in template. In order to update the theme you need to relocate the `google_analytics` variable in the configs and rename it to `googleAnalytics`. Take a look in the example [`config.toml`](
[Show me the diff](
### Disqus
Now the theme uses the built-in template of Hugo to enable the comments section with Disqus. This change requires to relocate the `disqusShortname` variable in the configs.
[Show me the diff](
The MIT License (MIT)
Copyright (c) 2015 [Cactus Authors](//, [Nick Balestra](// and [digitalcraftsman](//
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
# Cactus Theme
Cactus is a minimalistic theme for bloggers based on the default theme of the same-named [Cactus static site generator](// written in Python and [Nick Balestra](//'s Jekyll port. Noteworthy features of this Hugo theme are the integration of a comment-system powered by Disqus, a customizable about page, support for RSS feeds, syntax highlighting for source code, and sharing options for blog posts.
## Installation
Inside the folder of your Hugo site, run:
$ cd themes
$ git clone
For more information, please read Hugo's official [setup guide](//
### The config file
Take a look inside the [`exampleSite`](// folder of this theme. You'll find a file called [`config.toml`](//
To use it, copy the [`config.toml`](// file to the root folder of your Hugo site. Feel free to change the strings as you like to customize your website.
Make sure to update the `themesDir` property in the config file to point to your site's theme folder, otherwise an error will be thrown indicating the themes folder is unable to be found.
## About page
Use the about page to introduce yourself to your visitors. You can customize the content as you like in the [`config.toml`](// Furthermore, you should replace the [avatar placeholder](// with a great image of yourself.
## Disqus
This theme features a comment system powered by Disqus too. Just add your Disqus-shortname to the [`config.toml`](// and let readers respond to your blog posts.
## Social link icons
You can add a social link panel in the footer by adding entries to the `social` block in the [`config.toml`](// You can choose between two icon fonts:
- [Font awesome]( or
- [Mono social icons](
Assign either `font-awesome` or `mono-social` to the `iconFont` variable. The Mono social icons offer three styles of icons: circle, rounded, or default (empty).
## Nearly finished
To see your site in action, run Hugo's built-in local server.
$ hugo server
Now enter [`localhost:1313`](http://localhost:1313) in the address bar of your browser.
## Contributing
Found a bug or got an idea for a new feature? Feel free to use the [issue tracker](// to let me know. Or directly make a [pull request](//
Please create a separate branch for your pull request.
## License
This theme is released under the MIT license. For more information read the [license](//
## Acknowledgements
Thanks to
- [Nick Balestra](// for creating the original theme
- [Steve Francia](// for creating Hugo and the awesome community around the project.
title: "{{ replace .TranslationBaseName "-" " " | title }}"
date: {{ .Date }}
draft: true
\ No newline at end of file
# Site settings
baseurl = ""
themesDir = "../.."
languageCode = "en-us"
title = "Hugo Cactus Theme"
theme = "hugo-cactus-theme"
# Enter your tracking code to enable Google Analytics
googleAnalytics = ""
# Disable comments by leaving disqusShortname empty
disqusShortname = "spf13"
name = "John Doe"
description = "Describe your website"
bio = "Blogger & Programmer"
# Enter optionally your twitter account
twitter = "Your Twitter account"
enableRSS = true
# Integrate Javascript files or stylesheets by adding the url to the external assets or by
# linking local files with their path relative to the static folder, e.g. "css/styles.css"
customCSS = []
customJS = []
# The variables below are optionally too and can be used to
# translate or customize each string of the theme.
# Navigation links
home = ""
subscribe = ""
# Pagination links
olderPosts = ""
newerPosts = ""
readMore = ""
copyright = ""
# Sharing options and author information in posts
aboutAuthor = "I'm an blogger."
tweet = ""
share = ""
# 404 page
title404 = ""
subtitle404 = ""
# Choose a font for the social icons in the footer. Either "mono-social" or "font-awesome"
iconFont = "mono-social"
# The social icons can be styled differently if you use mono as font - circle, rounded, or empty
socialIconStyle = "circle"
# Add additional social link entries underneath
twitter = ""
facebook = ""
github = ""
dribble = ""
date = "2015-06-20T14:02:37+02:00"
title = "About"
hidden = true
menu = "main"
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Ipsa ullam earum dolorum! Sed, perspiciatis.
Lorem ipsum dolor sit amet, consectetur adipisicing elit.
### Lorem ipsum dolor.
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Ea dicta corporis ad inventore itaque impedit dolor atque amet exercitationem! Veniam qui voluptas maiores vel laudantium necessitatibus, velit ducimus! Iste hic facere, accusamus fugiat enim facilis.
title = "(Hu)go Template Primer"
description = ""
tags = [
date = "2014-04-02"
categories = [
Hugo uses the excellent [go][] [html/template][gohtmltemplate] library for
its template engine. It is an extremely lightweight engine that provides a very
small amount of logic. In our experience that it is just the right amount of
logic to be able to create a good static website. If you have used other
template systems from different languages or frameworks you will find a lot of
similarities in go templates.
This document is a brief primer on using go templates. The [go docs][gohtmltemplate]
provide more details.
## Introduction to Go Templates
Go templates provide an extremely simple template language. It adheres to the
belief that only the most basic of logic belongs in the template or view layer.
One consequence of this simplicity is that go templates parse very quickly.
A unique characteristic of go templates is they are content aware. Variables and
content will be sanitized depending on the context of where they are used. More
details can be found in the [go docs][gohtmltemplate].
## Basic Syntax
Go lang templates are html files with the addition of variables and
**Go variables and functions are accessible within {{ }}**
Accessing a predefined variable "foo":
{{ foo }}
**Parameters are separated using spaces**
Calling the add function with input of 1, 2:
{{ add 1 2 }}
**Methods and fields are accessed via dot notation**
Accessing the Page Parameter "bar"
{{ }}
**Parentheses can be used to group items together**
{{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
## Variables
Each go template has a struct (object) made available to it. In hugo each
template is passed either a page or a node struct depending on which type of
page you are rendering. More details are available on the
[variables](/layout/variables) page.
A variable is accessed by referencing the variable name.
<title>{{ .Title }}</title>
Variables can also be defined and referenced.
{{ $address := "123 Main St."}}
{{ $address }}
## Functions
Go template ship with a few functions which provide basic functionality. The go
template system also provides a mechanism for applications to extend the
available functions with their own. [Hugo template
functions](/layout/functions) provide some additional functionality we believe
are useful for building websites. Functions are called by using their name
followed by the required parameters separated by spaces. Template
functions cannot be added without recompiling hugo.
{{ add 1 2 }}
## Includes
When including another template you will pass to it the data it will be
able to access. To pass along the current context please remember to
include a trailing dot. The templates location will always be starting at
the /layout/ directory within Hugo.
{{ template "chrome/header.html" . }}
## Logic
Go templates provide the most basic iteration and conditional logic.
### Iteration
Just like in go, the go templates make heavy use of range to iterate over
a map, array or slice. The following are different examples of how to use
**Example 1: Using Context**
{{ range array }}
{{ . }}
{{ end }}
**Example 2: Declaring value variable name**
{{range $element := array}}
{{ $element }}
{{ end }}
**Example 2: Declaring key and value variable name**
{{range $index, $element := array}}
{{ $index }}
{{ $element }}
{{ end }}
### Conditionals
If, else, with, or, & and provide the framework for handling conditional
logic in Go Templates. Like range, each statement is closed with `end`.
Go Templates treat the following values as false:
* false
* 0
* any array, slice, map, or string of length zero
**Example 1: If**
{{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
**Example 2: If -> Else**
{{ if isset .Params "alt" }}
{{ index .Params "alt" }}
{{ index .Params "caption" }}
{{ end }}
**Example 3: And & Or**
{{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
**Example 4: With**
An alternative way of writing "if" and then referencing the same value
is to use "with" instead. With rebinds the context `.` within its scope,
and skips the block if the variable is absent.
The first example above could be simplified as:
{{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
**Example 5: If -> Else If**
{{ if isset .Params "alt" }}
{{ index .Params "alt" }}
{{ else if isset .Params "caption" }}
{{ index .Params "caption" }}
{{ end }}
## Pipes
One of the most powerful components of go templates is the ability to
stack actions one after another. This is done by using pipes. Borrowed
from unix pipes, the concept is simple, each pipeline's output becomes the
input of the following pipe.
Because of the very simple syntax of go templates, the pipe is essential
to being able to chain together function calls. One limitation of the
pipes is that they only can work with a single value and that value
becomes the last parameter of the next pipeline.
A few simple examples should help convey how to use the pipe.
**Example 1 :**
{{ if eq 1 1 }} Same {{ end }}
is the same as
{{ eq 1 1 | if }} Same {{ end }}
It does look odd to place the if at the end, but it does provide a good
illustration of how to use the pipes.
**Example 2 :**
{{ index .Params "disqus_url" | html }}
Access the page parameter called "disqus_url" and escape the HTML.
**Example 3 :**
{{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
Stuff Here
{{ end }}
Could be rewritten as
{{ isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
Stuff Here
{{ end }}
## Context (aka. the dot)
The most easily overlooked concept to understand about go templates is that {{ . }}
always refers to the current context. In the top level of your template this
will be the data set made available to it. Inside of a iteration it will have
the value of the current item. When inside of a loop the context has changed. .
will no longer refer to the data available to the entire page. If you need to
access this from within the loop you will likely want to set it to a variable
instead of depending on the context.
{{ $title := .Site.Title }}
{{ range .Params.tags }}
<li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
{{ end }}
Notice how once we have entered the loop the value of {{ . }} has changed. We
have defined a variable outside of the loop so we have access to it from within
the loop.
# Hugo Parameters
Hugo provides the option of passing values to the template language
through the site configuration (for sitewide values), or through the meta
data of each specific piece of content. You can define any values of any
type (supported by your front matter/config format) and use them however
you want to inside of your templates.
## Using Content (page) Parameters
In each piece of content you can provide variables to be used by the
templates. This happens in the [front matter](/content/front-matter).
An example of this is used in this documentation site. Most of the pages
benefit from having the table of contents provided. Sometimes the TOC just
doesn't make a lot of sense. We've defined a variable in our front matter
of some pages to turn off the TOC from being displayed.
Here is the example front matter:
title: "Permalinks"
date: "2013-11-18"
- "/doc/permalinks/"
groups: ["extras"]
groups_weight: 30
notoc: true
Here is the corresponding code inside of the template:
{{ if not .Params.notoc }}
<div id="toc" class="well col-md-4 col-sm-6">
{{ .TableOfContents }}
{{ end }}
## Using Site (config) Parameters
In your top-level configuration file (eg, `config.yaml`) you can define site
parameters, which are values which will be available to you in chrome.
For instance, you might declare:
CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
TwitterUser: "spf13"
SidebarRecentLimit: 5
Within a footer layout, you might then declare a `<footer>` which is only
provided if the `CopyrightHTML` parameter is provided, and if it is given,
you would declare it to be HTML-safe, so that the HTML entity is not escaped
again. This would let you easily update just your top-level config file each
January 1st, instead of hunting through your templates.
{{if .Site.Params.CopyrightHTML}}<footer>
<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
An alternative way of writing the "if" and then referencing the same value
is to use "with" instead. With rebinds the context `.` within its scope,
and skips the block if the variable is absent:
{{with .Site.Params.TwitterUser}}<span class="twitter">
<a href="{{.}}" rel="author">
<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
Finally, if you want to pull "magic constants" out of your layouts, you can do
so, such as in this example:
<nav class="recent">
<h1>Recent Posts</h1>
<ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
<li><a href="{{.RelPer