data.coop/website
8
1
Fork 6
Code Issues 11 Pull requests Releases Wiki Activity

Minimal hugo website #10

Merged
benjaoming merged 9 commits from benjaoming/website:new-website into new 2020-05-03 21:33:39 +00:00
Conversation 4 Commits 9 Files changed 191 +288 -859
19 changed files with 288 additions and 859 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit fef42ad5c8 - Show all commits

13
README.rst
View file

@ -23,10 +23,10 @@ Example recipe
sudo dpkg -i hugo_extended.deb
# Clone repo
git clone https://git.data.coop/data.coop/website.git
git clone https://git.data.coop/data.coop/website.git data.coop-website
# Go to website
cd website
cd data.coop-website
# Run development server
hugo server
@ -36,3 +36,12 @@ Example recipe
Simply pushing to `master` in our main repo at https://git.data.coop/data.coop/website/ will trigger a build-and-deploy of the website.
## Multilingual notes
Our website is made multi-lingual using the following 3 structures:
1. The folder ``i18n/`` contains translations of strings used in the theme.
1. Each content article and news text has a language version such ``content/<slug>.en.md``
1. The ``config.yaml`` contains settings specific to each language, such as navigation.

2
ROADMAP
View file

@ -4,3 +4,5 @@ Uge 2: HTML skabelon og Hugo skelet til undersider
Uge 3: Beta-hjemmeside, "style guide"
Uge 4: Indhold og lancering

111
config.yaml
View file

@ -1,9 +1,47 @@
baseURL: https://new.data.coop
DefaultContentLanguage: da
languageCode: da-dk
copyright: CC-BY, see https://creativecommons.org/licenses/by/4.0/
title: data.coop
theme: datacoop2020
DefaultContentLanguage: da
# See: https://gohugo.io/content-management/multilingual/
languages:
da:
languagedirection: rtl
title: data.coop
weight: 1
LanguageName: Dansk
en:
params:
navigation:
help: Aide
title: data.coop
weight: 2
title: Mon blogue
weight: 2
LanguageName: English
menu:
nav:
- name: "Bliv Medlem"
url: "/membership/"
weight: 1
- name: "Om os"
url: "/about/"
weight: 2
- name: "Tjenester"
url: "/services/"
weight: 3
- name: "Vedtægter"
url: "/rights/"
weight: 4
- name: "Nyheder"
url: "/news/"
weight: 5
taxonomies:
tag: tags
@ -11,68 +49,23 @@ permalinks:
post: "/:filename/"
params:
description: "Some description"
contentBackgroundColor: "#fff"
contentTextColor: "#212529"
contentLinkColor: "#007bff"
contentLinkHoverColor: "#0056b3"
navbarBackgroundColor: "#212529"
navbarLinkColor: "rgba(255, 255, 255, 0.75)"
navbarLinkHoverColor: "rgba(255, 255, 255, 1)"
wrapperMaxWidth: "800px"
customDateFormat: "Jan 2, 2006"
customCodeStyle: true
customBlockquoteStyle: true
showPostSummary: false
googleAnalytics: "UA-123456789-1"
cookieConsent: true
includeBootstrapJs: false
faviconSafariPinnedTabColor: "#5bbad5"
faviconMsApplicationTileColor: "#da532c"
faviconThemeColor: "#ffffff"
description: "Et datakollektiv, der passer på dine data."
menu:
nav:
- name: "Posts"
url: "/"
- name: "Bliv Medlem"
url: "/membership/"
weight: 1
- name: "Tags"
url: "/tags/"
weight: 2
- name: "About"
- name: "Om os"
url: "/about/"
weight: 2
- name: "Tjenester"
url: "/services/"
weight: 3
- name: "RSS"
url: "/index.xml"
- name: "Vedtægter"
url: "/rights/"
weight: 4
- name: "Nyheder"
url: "/news/"
weight: 5
markup:
defaultMarkdownHandler: "goldmark"
markup.goldmark:
markup.goldmark.extensions:
definitionList: true
footnote: true
linkify: true
strikethrough: true
table: true
taskList: true
typographer: true
markup.goldmark.parser:
attribute: true
autoHeadingID: true
markup.goldmark.renderer:
hardWraps: false
unsafe: true
xHTML: false
markup.highlight:
codeFences: true
hl_Lines: ""
lineNoStart: 1
lineNos: false
lineNumbersInTable: true
noClasses: true
style: "monokai"
tabWidth: 4
markup.tableOfContents:
endLevel: 6
startLevel: 2

5
content/_index.da.md Normal file
View file

@ -0,0 +1,5 @@
---
title: "Start"
---
# Hej

5
content/_index.en.md Normal file
View file

@ -0,0 +1,5 @@
---
title: "Start"
---
# Start

30
content/about.da.md Normal file
View file

@ -0,0 +1,30 @@
---
title: "Om os"
---
**data.coop** er en forening og et kooperativ, som er nystartet. Visionen
er, at vi medlemmerne i kooperativet ejer vores egne data.
Dette indebærer en del og har som konsekvens, at vi bliver nødt til at eje
vores egen infrastruktur og have indblik i og kontrol over den software,
som vi bruger til at kommunikere på nettet. Ret forsimplet betyder dette:
* At vi ejer vores egen hardware
* At vi kun bruger open source software
Vi går med begge ben på jorden, så for rent faktisk at kunne starte rigtigt
op, kan vi ikke stille urealistiske krav: At køre åben hardware eller
drive services såsom egne søgemaskiner er således ikke inden for rammerne.
Til gengæld regner vi med at drive en række af de fede open source projekter,
som allerede findes til e-mail, kalender, dokumentdeling og SOME.
Vi ønsker pr. 2018 støttemedlemmer til at dække vores omkostninger.
Foreningen råder over 2 rack servere. Vi er ved at opbygge et medlemssystem
og afprøver nogle prototyper til den fremtidige hosting og infrastruktur.
Du kan finde os på:
* Freenode IRC, **#data.coop**.
* Keybase, **datacoop**
* Vores [Gitea server](https://git.data.coop/data.coop/)

8
content/about.en.md Normal file
View file

@ -0,0 +1,8 @@
---
title: "About"
---
## This Theme
Thanks for visiting this theme demo. If you're interested, checkout my other stuff over at <https://zwbetz.com>

28
content/about.md
View file

@ -1,28 +0,0 @@
---
title: "About"
date: "2014-04-09"
---
## This Theme
Thanks for visiting this theme demo. If you're interested, checkout my other stuff over at <https://zwbetz.com>
## Hugo
Hugo is the **world’s fastest framework for building websites**. It is written in Go.
It makes use of a variety of open source projects including:
* https://github.com/russross/blackfriday
* https://github.com/alecthomas/chroma
* https://github.com/muesli/smartcrop
* https://github.com/spf13/cobra
* https://github.com/spf13/viper
Learn more and contribute on [GitHub](https://github.com/gohugoio).
---
<small>
_Favicon made by [Freepik](https://www.freepik.com/), from [Flaticon](https://www.flaticon.com/), licensed by [CC 3.0](http://creativecommons.org/licenses/by/3.0/)._
</small>

21
content/membership.da.md Normal file
View file

@ -0,0 +1,21 @@
---
title: Bliv medlem
---
[data.coop](https://data.coop) er en demokratisk forening. Medlemmer bestemmer
over foreningens generelle drift og hvordan data skal forvaltes. Dette sker som
i en helt klassisk forening i henhold til vores vedtægter på den årlige
generalforsamling.
Du bliver medlem ved at overføre penge til vores konto og sende en email til
vores kasserer, [benjaoming@data.coop](mailto:benjaoming@data.coop), med dit navn.
* Reg. 8401 (Merkur)
* Kontonr. 1016866
* Tekst på overførslen: Fornavn+efternavn
Årligt kontingent: **300 kr** (dog gerne mere)\
(nedsat kontingent er 50 kr. for studerende/arbejdsløse)
Kontingent-perioden gælder for det år, man melder sig ind i.

7
content/post/creating-a-new-theme.md → content/post/creating-a-new-theme.en.md
View file

@ -1,8 +1,7 @@
---
title: "Creating a New Theme"
date: 2014-09-28
publishdate: 2014-09-28
lastmod: 2014-09-28
title: "Vi bygger ny hjemmeside"
date: 2020-05-03
publishdate: 2020-05-03
draft: false
tags: ["hugo", "theme", "command-line"]
---

335
content/post/goisforlovers.md
View file

@ -1,335 +0,0 @@
---
title: "(Hu)go Template Primer"
date: "2014-04-02"
publishdate: "2014-04-02"
lastmod: "2014-04-02"
draft: false
tags: ["go", "templates", "hugo"]
---
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
Golang templates are HTML files with the addition of variables and
functions.
**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"
{{ .Params.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.
**Example:**
{{ 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.
**Example:**
{{ 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
range.
**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" }}
{{else}}
{{ 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.
**Example:**
{{ $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"
aliases:
- "/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 }}
</div>
{{ 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:
```yaml
params:
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>
</footer>{{end}}
```
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="https://twitter.com/{{.}}" rel="author">
<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
alt="Twitter"></a>
</span>{{end}}
```
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="{{.RelPermalink}}">{{.Title}}</a></li>
{{end}}</ul>
</nav>
```
[go]: https://golang.org/
[gohtmltemplate]: https://golang.org/pkg/html/template/

81
content/post/hugoisforlovers.md
View file

@ -1,81 +0,0 @@
---
title: "Getting Started with Hugo"
date: "2014-04-02"
publishdate: "2014-04-02"
lastmod: "2014-04-02"
draft: false
tags: ["hugo", "git", "fun"]
---
## Step 1. Install Hugo
Go to [Hugo releases](https://github.com/spf13/hugo/releases) and download the
appropriate version for your OS and architecture.
Save it somewhere specific as we will be using it in the next step.
More complete instructions are available at [Install Hugo](https://gohugo.io/getting-started/installing/)
## Step 2. Build the Docs
Hugo has its own example site which happens to also be the documentation site
you are reading right now.
Follow the following steps:
1. Clone the [Hugo repository](http://github.com/spf13/hugo)
2. Go into the repo
3. Run hugo in server mode and build the docs
4. Open your browser to http://localhost:1313
Corresponding pseudo commands:
git clone https://github.com/spf13/hugo
cd hugo
/path/to/where/you/installed/hugo server --source=./docs
> 29 pages created
> 0 tags index created
> in 27 ms
> Web Server is available at http://localhost:1313
> Press ctrl+c to stop
Once you've gotten here, follow along the rest of this page on your local build.
## Step 3. Change the docs site
Stop the Hugo process by hitting Ctrl+C.
Now we are going to run hugo again, but this time with hugo in watch mode.
/path/to/hugo/from/step/1/hugo server --source=./docs --watch
> 29 pages created
> 0 tags index created
> in 27 ms
> Web Server is available at http://localhost:1313
> Watching for changes in /Users/spf13/Code/hugo/docs/content
> Press ctrl+c to stop
Open your [favorite editor](http://vim.spf13.com) and change one of the source
content pages. How about changing this very file to *fix the typo*. How about changing this very file to *fix the typo*.
Content files are found in `docs/content/`. Unless otherwise specified, files
are located at the same relative location as the url, in our case
`docs/content/overview/quickstart.md`.
Change and save this file.. Notice what happened in your terminal.
> Change detected, rebuilding site
> 29 pages created
> 0 tags index created
> in 26 ms
Refresh the browser and observe that the typo is now fixed.
Notice how quick that was. Try to refresh the site before it's finished building. I double dare you.
Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.
## Step 4. Have fun
The best way to learn something is to play with it.

154
content/post/migrate-from-jekyll.md
View file

@ -1,154 +0,0 @@
---
title: "Migrate to Hugo from Jekyll"
date: 2014-03-10
publishdate: 2014-03-10
lastmod: 2014-03-10
draft: false
tags: ["hugo", "jekyll", "migration", "git", "templates"]
---
## Move static content to `static`
Jekyll has a rule that any directory not starting with `_` will be copied as-is to the `_site` output. Hugo keeps all static content under `static`. You should therefore move it all there.
With Jekyll, something that looked like
▾ <root>/
▾ images/
logo.png
should become
▾ <root>/
▾ static/
▾ images/
logo.png
Additionally, you'll want any files that should reside at the root (such as `CNAME`) to be moved to `static`.
## Create your Hugo configuration file
Hugo can read your configuration as JSON, YAML or TOML. Hugo supports parameters custom configuration too. Refer to the [Hugo configuration documentation](/overview/configuration/) for details.
## Set your configuration publish folder to `_site`
The default is for Jekyll to publish to `_site` and for Hugo to publish to `public`. If, like me, you have [`_site` mapped to a git submodule on the `gh-pages` branch](http://blog.blindgaenger.net/generate_github_pages_in_a_submodule.html), you'll want to do one of two alternatives:
1. Change your submodule to point to map `gh-pages` to public instead of `_site` (recommended).
git submodule deinit _site
git rm _site
git submodule add -b gh-pages git@github.com:your-username/your-repo.git public
2. Or, change the Hugo configuration to use `_site` instead of `public`.
{
..
"publishdir": "_site",
..
}
## Convert Jekyll templates to Hugo templates
That's the bulk of the work right here. The documentation is your friend. You should refer to [Jekyll's template documentation](http://jekyllrb.com/docs/templates/) if you need to refresh your memory on how you built your blog and [Hugo's template](/layout/templates/) to learn Hugo's way.
As a single reference data point, converting my templates for [heyitsalex.net](http://heyitsalex.net/) took me no more than a few hours.
## Convert Jekyll plugins to Hugo shortcodes
Jekyll has [plugins](http://jekyllrb.com/docs/plugins/); Hugo has [shortcodes](/doc/shortcodes/). It's fairly trivial to do a port.
### Implementation
As an example, I was using a custom [`image_tag`](https://github.com/alexandre-normand/alexandre-normand/blob/74bb12036a71334fdb7dba84e073382fc06908ec/_plugins/image_tag.rb) plugin to generate figures with caption when running Jekyll. As I read about shortcodes, I found Hugo had a nice built-in shortcode that does exactly the same thing.
Jekyll's plugin:
module Jekyll
class ImageTag < Liquid::Tag
@url = nil
@caption = nil
@class = nil
@link = nil
// Patterns
IMAGE_URL_WITH_CLASS_AND_CAPTION =
IMAGE_URL_WITH_CLASS_AND_CAPTION_AND_LINK = /(\w+)(\s+)((https?:\/\/|\/)(\S+))(\s+)"(.*?)"(\s+)->((https?:\/\/|\/)(\S+))(\s*)/i
IMAGE_URL_WITH_CAPTION = /((https?:\/\/|\/)(\S+))(\s+)"(.*?)"/i
IMAGE_URL_WITH_CLASS = /(\w+)(\s+)((https?:\/\/|\/)(\S+))/i
IMAGE_URL = /((https?:\/\/|\/)(\S+))/i
def initialize(tag_name, markup, tokens)
super
if markup =~ IMAGE_URL_WITH_CLASS_AND_CAPTION_AND_LINK
@class = $1
@url = $3
@caption = $7
@link = $9
elsif markup =~ IMAGE_URL_WITH_CLASS_AND_CAPTION
@class = $1
@url = $3
@caption = $7
elsif markup =~ IMAGE_URL_WITH_CAPTION
@url = $1
@caption = $5
elsif markup =~ IMAGE_URL_WITH_CLASS
@class = $1
@url = $3
elsif markup =~ IMAGE_URL
@url = $1
end
end
def render(context)
if @class
source = "<figure class='#{@class}'>"
else
source = "<figure>"
end
if @link
source += "<a href=\"#{@link}\">"
end
source += "<img src=\"#{@url}\">"
if @link
source += "</a>"
end
source += "<figcaption>#{@caption}</figcaption>" if @caption
source += "</figure>"
source
end
end
end
Liquid::Template.register_tag('image', Jekyll::ImageTag)
is written as this Hugo shortcode:
<!-- image -->
<figure {{ with .Get "class" }}class="{{.}}"{{ end }}>
{{ with .Get "link"}}<a href="{{.}}">{{ end }}
<img src="{{ .Get "src" }}" {{ if or (.Get "alt") (.Get "caption") }}alt="{{ with .Get "alt"}}{{.}}{{else}}{{ .Get "caption" }}{{ end }}"{{ end }} />
{{ if .Get "link"}}</a>{{ end }}
{{ if or (or (.Get "title") (.Get "caption")) (.Get "attr")}}
<figcaption>{{ if isset .Params "title" }}
{{ .Get "title" }}{{ end }}
{{ if or (.Get "caption") (.Get "attr")}}<p>
{{ .Get "caption" }}
{{ with .Get "attrlink"}}<a href="{{.}}"> {{ end }}
{{ .Get "attr" }}
{{ if .Get "attrlink"}}</a> {{ end }}
</p> {{ end }}
</figcaption>
{{ end }}
</figure>
<!-- image -->
### Usage
I simply changed:
{% image full http://farm5.staticflickr.com/4136/4829260124_57712e570a_o_d.jpg "One of my favorite touristy-type photos. I secretly waited for the good light while we were "having fun" and took this. Only regret: a stupid pole in the top-left corner of the frame I had to clumsily get rid of at post-processing." ->http://www.flickr.com/photos/alexnormand/4829260124/in/set-72157624547713078/ %}
to this (this example uses a slightly extended version named `fig`, different than the built-in `figure`):
{{%/* fig class="full" src="http://farm5.staticflickr.com/4136/4829260124_57712e570a_o_d.jpg" title="One of my favorite touristy-type photos. I secretly waited for the good light while we were having fun and took this. Only regret: a stupid pole in the top-left corner of the frame I had to clumsily get rid of at post-processing." link="http://www.flickr.com/photos/alexnormand/4829260124/in/set-72157624547713078/" */%}}
As a bonus, the shortcode named parameters are, arguably, more readable.
## Finishing touches
### Fix content
Depending on the amount of customization that was done with each post with Jekyll, this step will require more or less effort. There are no hard and fast rules here except that `hugo server --watch` is your friend. Test your changes and fix errors as needed.
### Clean up
You'll want to remove the Jekyll configuration at this point. If you have anything else that isn't used, delete it.
## A practical example in a diff
[Hey, it's Alex](http://heyitsalex.net/) was migrated in less than a _father-with-kids day_ from Jekyll to Hugo. You can see all the changes (and screw-ups) by looking at this [diff](https://github.com/alexandre-normand/alexandre-normand/compare/869d69435bd2665c3fbf5b5c78d4c22759d7613a...b7f6605b1265e83b4b81495423294208cc74d610).

98
content/post/script-to-add-a-page-level-variable-to-content-front-matter-in-hugo.md
View file

@ -1,98 +0,0 @@
---
title: "Script to add a page-level variable to content front matter in hugo"
date: 2018-10-10T12:43:20-05:00
publishdate: 2018-10-10
lastmod: 2018-10-11
draft: false
tags: ["hugo", "command-line", "awk"]
---
This was originally a question posed on the [hugo discussion forums](https://discourse.gohugo.io/t/set-frontmatter-params-in-list-template/14645).
The user wanted to loop through all her content files and add a `weight` page-level variable to the front matter. The value of `weight` needed to be the first 2 characters of the content filename, since her content was named like `01_content.md`, `02_content.md`, etc.
She then wanted to `range` through her pages by their weight, like so:
```go
{{ range .Pages.ByWeight }}
<!-- some code -->
{{ end }}
```
## The script
```bash
#!/bin/bash
for file in *.md; do
weight=${file:0:2}
awk -v weight=$weight '/---/{
count++
if(count == 2){
sub("---","weight: " weight "\n---",$0)
}
}
{print}' $file > tmp && mv tmp $file
done
```
## Explained
Loop through all files in the directory with extension `.md`:
```bash
for file in *.md; do
# ...
done
```
Set a variable using the first 2 characters of the filename:
```bash
weight=${file:0:2}
```
Call an `awk` program and pass it a `weight` variable:
```bash
awk -v weight=$weight
```
When the `awk` program encounters the 2nd occurrence of `---` (which is how you end front matter in YAML), it inserts the `weight` page-level variable on the line above:
```bash
'/---/{
count++
if(count == 2){
sub("---","weight: " weight "\n---",$0)
}
}
{print}'
```
Redirect the output of the `awk` program to a tmp file, then overwrite the original content file with the tmp file:
```bash
> tmp && mv tmp $file
```
## Result
Original `01_content.md`:
```yml
---
title: "Some title"
draft: false
---
```
Updated `01_content.md`:
```yml
---
title: "Some title"
draft: false
weight: 01
---
```

88
content/post/use-snap-to-install-the-hugo-edge-version-on-fedora-and-ubuntu.md
View file

@ -1,88 +0,0 @@
---
title: "Use Snap to install the Hugo edge version on Fedora and Ubuntu"
date: 2018-10-26T12:59:51-05:00
publishdate: 2018-10-26
lastmod: 2018-10-26
draft: false
aliases:
- /use-snap-to-install-the-hugo-edge-version-on-fedora/
tags: ["hugo", "snap", "fedora", "ubuntu"]
---
If you are using the Fedora or Ubuntu Linux distributions -- I'm currently on Fedora 28 -- and would like to [help test the latest development version of Hugo](https://discourse.gohugo.io/t/help-test-upcoming-hugo-0-50/14880), or if you just want to be on the bleeding-edge of things, this post is for you.
## Fedora-only steps
To get started, [install Snap on Fedora](https://docs.snapcraft.io/installing-snap-on-fedora/6755):
```
sudo dnf install snapd
```
Add the [Snap directory](https://docs.snapcraft.io/commands-and-aliases/3950) to your `PATH` by adding this line to your `~/.bashrc` file. Then restart your terminal to pick up the change:
```
export PATH="$PATH:/var/lib/snapd/snap/bin"
```
## Ubuntu-only steps
Ubuntu 16.04 and above come with [Snap already installed](https://docs.snapcraft.io/installing-snap-on-ubuntu/6740). If you're using an older Ubuntu version, install Snap by running:
```
sudo apt update && sudo apt install snapd
```
Check if the Snap directory is on your `PATH` by listing each entry:
```
echo $PATH | tr ':' '\n'
```
If you don't see `/snap/bin` listed, then add this line to your `~/.bashrc` file. Then restart your terminal to pick up the change:
```
export PATH="$PATH:/snap/bin"
```
## Install Hugo
See which Snap channels are available for Hugo:
```
snap info hugo
```
Install Hugo from the edge channel:
```
sudo snap install hugo --channel=edge
```
Or, if you prefer Hugo Extended -- which has the [Hugo Pipes](https://gohugo.io/hugo-pipes/) feature -- install it from the extended edge channel:
```
sudo snap install hugo --channel=extended/edge
```
Lastly, confirm the location and version of Hugo that was intalled:
```
which hugo && hugo version
```
Happy testing :)
## Update or remove Hugo
Snaps are [updated automatically](https://docs.snapcraft.io/keeping-snaps-up-to-date/7022). To manually update Hugo:
```
sudo snap refresh hugo
```
To remove Hugo:
```
sudo snap remove hugo
```

118
content/rights.da.md Normal file
View file

@ -0,0 +1,118 @@
---
title: Vedtægter
---
## § 1. Navn og tilhørsforhold
Foreningens navn er: data.coop
Foreningens hjemsted er Københavns Kommune, men primært internettet.
## § 2. Formål
Foreningen data.coop ønsker at stille digital infrastruktur til rådighed for
sine medlemmer, på en måde hvor foreningens kerneprincipper --
privatlivsbeskyttelse, kryptering, decentralisering og zero-knowledge for
foreningen som tjenesteudbyder -- er i fokus. Ydermere vil foreningen advokere
for sine kerneprincipper, hjælpe folk til at at agere på nettet på forsvarlig
vis, samt samarbejde med andre datafællesskaber/hjælpe andre i gang med lign.
foreninger.
## § 3. Organisation
Foreningens overordnede ledelse er generalforsamlingen, som består af medlemmer med gyldigt medlemsbevis.
Generalforsamlingen vælger:
- En bestyrelse på 5 personer
- 2 suppleanter for bestyrelsen
- 1 revisor
- Evt. 1 suppleant for revisor
Valg til bestyrelsen sker for en periode på 2 år, således at mindst 2 personer
er på valg hvert år. Revisor og suppleanter er på valg hvert år.
## § 4. Generalforsamlingen
Bestyrelsen indkalder generalforsamlingen med mindst 14 dages varsel via
foreningens hjemmeside og mailinglister. Ordinær generalforsamling afholdes
hvert år inden udgangen af september måned. Dagsorden for ordinær
generalforsamling skal indeholde følgende punkter:
1. Valg af dirigent og referent.
1. Bestyrelsens beretning.
1. Fremlæggelse af regnskab, budget og kontingent.
1. Indkomne forslag. Forslag skal være modtaget af bestyrelsen senest en uge før generalforsamlingen.
1. Godkendelse af vedtægtsændringer og Acceptable Use Policy
1. Valg (Jf. § 3)
1. Eventuelt
### § 4.1. Afholdelse af generalforsamlinger og bestyrelsesmøder
Generalforsamlinger og bestyrelsesmøder kan afholdes på internettet.
## § 5. Foreningens bestyrelse
Foreningens daglige ledelse forestås af bestyrelsen (Jf. § 3). Bestyrelsen
konstituerer sig selv med formand, næstformand og kasserer. Bestyrelsen
uddelegerer den daglige drift til et forretningsudvalg, som består af formand,
næstformand og kasserer.
Bestyrelsen udarbejder regnskab og budget.
Bestyrelsen fastsætter selv sin forretningsorden.
Bestyrelsen kan sammensætte samarbejdsgrupper af medlemmer, der kan fungerer
som idéudviklingsforum for foreningen.
Tegningsret for foreningen har formanden og kassereren, dog ved køb, salg eller
pantsætning af fast ejendom, indgåelse af driftsaftaler samt ved optagelse af
lån, af den samlede bestyrelse.
## § 6. Medlemskab
Som medlem kan enhver fysisk person optages, som har interesse i at støtte
foreningens formål. Medlemskab er bindende for et år ad gangen.
Bestyrelsen kan ekskludere medlemmer fra foreningen, hvis disse har handlet i
uoverenstemmelse med Acceptable Use Policy (AUP).
## § 7. Kontingent/finansiering
De årlige kontingenter fastsættes af generalforsamlingen.
Foreningen kan herudover finansieres ved sponsor- og annoncestøtte samt bidrag
fra offentlige/private virksomheder, fonde, øvrige foreninger/institutioner og
private personer, så længe det ikke stiller krav til foreningens dispositioner.
## § 8. Vedtægtsændringer
Vedtægtsændringer kræver et flertal på ¾ af generalforsamlingens fremmødte
medlemmer.
## § 9. Ekstraordinær generalforsamling
Indkaldelse sker, hvis et flertal af bestyrelsen ønsker det.
Indkaldelse sker, hvis 1/3 af medlemmerne ønsker det.
Indkaldelse sker under samme betingelser, som anført i §4.
Dagsorden skal motiveres.
## § 10. Regnskab
Regnskabsåret for Foreningen er kalenderåret.
## § 11. Opløsning
Opløsning af foreningen kræver et flertal på ¾ af generalforsamlingens eller
den ekstraordinære generalforsamlings fremmødte medlemmer.
Opløsningen skal herefter godkendes på en efterfølgende ekstraordinær
generalforsamling.
Ved opløsning af foreningen skal foreningens midler overdrages til European
Digital Rights (EDRi) og Free Software Foundation Europe (FSFE).
Foreningen data.coop er stiftet den 24 juni 2014.

3
i18n/da-DK.toml Normal file
View file

@ -0,0 +1,3 @@
[home]
other = "Home"

8
themes/datacoop2020/layouts/_default/baseof.html
View file

@ -14,6 +14,14 @@
{{ partial "bootstrap-js.html" . }}
{{ partial "mastodon-js.html" . }}
<ul>
{{ range $.Site.Home.AllTranslations }}
<li><a href="{{ .Permalink }}">{{ .Language.LanguageName }}</a></li>
{{ end }}
</ul>
</body>
</html>

26
themes/datacoop2020/layouts/index.html
View file

@ -1,12 +1,23 @@
{{- define "main" -}}
{{ $homepage := "Home" }}
{{ with .Site.Menus.nav }}
{{ range first 1 . }}
{{ $homepage = .Name }}
{{ define "main" }}
<main aria-role="main">
<header class="homepage-header">
<h1>{{.Title}}</h1>
{{ with .Params.subtitle }}
<span class="subtitle">{{.}}</span>
{{ end }}
</header>
<div class="homepage-content">
<!-- Note that the content for index.html, as a sort of list page, will pull from content/_index.md -->
{{.Content}}
</div>
<div>
{{ range first 10 .Site.RegularPages }}
{{ .Render "summary"}}
{{ end }}
<h1>{{ $homepage }}</h1>
</div>
</main>
{{ $pages := where site.RegularPages "Type" "in" site.Params.mainSections }}
{{ range $pages.ByPublishDate.Reverse }}
@ -24,4 +35,5 @@
</p>
{{ end }}
{{- end -}}
{{ end }}