Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

PrivacyLx website

This is the website for the PrivacyLx Privacy group based in Lisbon.

website's screenshot

It is based on boostrap and uses hugo to generate the static website from the Markdown files

PrivacyLx website is also available under an onion service:

Getting started

Our website is generated from markdown to HTML with Hugo.

  • download the version v54 (wanna help upgrade?)
  • extract it and execute it with ./hugo -D server
  • open a browser on
  • and you should now see your version of the website. Any changes made will be immedialtely reflected there.

Adding content

Since the website is based in Hugo, adding new posts / events is as simple as creating a markdown file in the right directory

With hugo you can do this via command line with Hugo. We are using version 54 which you can download here

# for a blog post
hugo new post/

# for an event
hugo new event/

Overview of the structure:

├── content -------> add content here
│   ├── events --------------> (add an event)
│   │   ├──
│   │   └──
│   ├── post ----------------> (add a blog post)
│   │   ├──
│   │   └──
│   └── resources -----------> (add slides or pdf)
│       ├──
│       └──
├── static
│   ├── img ----------------> where images are stored
│   │   └── image1.png
│   └── slides--------------> where slides are stored
│       ├── slide1.pdf         (this is a git submodule)
│       └── sliderevealjs.html
└── themes -----------------> theme configuration

Adding an Event

For that, in the website root directory you type hugo new content/events/[name-of-event-separted-by-dashes].[en|pt].md which will generate a template for you to fill.

just copy and paste some content's markdown from the type of content that you want in order to add it.

Post metadata

This is what is at the top of every markdown file and it makes the post have certain things.

Here's a sample metadata (some things only apply to events)

title: "Just an example title"
publishdate: 2020-07-13
date: "replace with date of event"
image: "/img/[put image in /static/img/]"
description: "this description will show up in the homepage"
comments: true
tags: ["privacidade", "internet", "liberdade"]
metadata Explanation
title The title of the post
publishdate Today usually. But can be useful to schedule posts
date If an event, this will be the date of the event
description Summarized post. Should be about 1-2 lines and will show up in the homepage
comments Posts automatically a new post on the forum linking to website and adds comments at the bottom of the article/event
tags Tags that fit the content. This makes it easier for people to find related posts / events

Adding images and presentations

All static content goes under /static/ and is is referenced as though it was in the root of the website.

The presentations are a git submodule under /static/slides. They point to and so, the should be added there instead. In addition to that, you should create a markdown file under /content/resources/[name-of-the-presentation].md in order to add it to the website's index of presentations over at

Note on revealjs presentations: since they are html, js and css, we can show them directly on the index page. This can be done by adding in the markdown file [name-of-the-presentation].md the following

{{< revealjs [name-of-slide-index.html] >}} but without the html part.

Fox example: {{< revealjs cifra-te-ou-devoram-session00 >}} for the presentation stored in /static/slides/cifra-te-ou-devoram-session00.html



  • unix-based system
  • caddy webserver
  • hugo - generates the static

For that, in the website root directory you type hugo new content/events/[name-of-event-separted-by-dashes].[en|pt].md which will generate a template for you to from markdown files


  • cd /path/to/website
  • configure webserver to host file generated by hugo
  • ./

Editing Website Structure

This website uses hugo to generate the static website.

Development environment

  1. clone this repo with git clone --depth=1
  2. Install hugo or download the executable.
  3. cd into the website directory
  4. run local website server with hugo -D server
  5. open browser with http://localhost:1313
  6. edit website files

Note: the autorealoading feature will update the website as soon as you change something but caching problems may occur and if something unexpected happens you should restart the server (hugo -D server) and see if it persists

Where to edit what

It uses the hugo-bootstrap to leverage the aesthetics of twitter bootstrap and the simplicity of hugo. All the files relating to the theme are under themes/hugo-boostrap and that is where you should edit them. Here are the subfolders and their meaning:

  • i18n - where the translations strings like {{ i18n "translated" }} are. This is where you add / modify translations for the website structure (not the event's). Read more about i18n here.
  • layout - where the actual website structure is. Each entry is a section type.
    • events - has all the special html parts of showing the /events part of the website
      • baseof.html - base structure of html page
      • content - main content of page (excludes header and footer)
      • list - when a list of items of this section are being preview (what reders "", for example)
      • single - when a single article (event) is being viewed
      • summary - short preview of what article is
    • partials - reusable website parts. Read more here
    • 404.html - self explanatory - this is the 404 page
    • index.html - the homepage

Creating additional sections

You can create aditional sections. Read more here. You may need to:

  • edit config.toml - the configuration file for the website to detect the new sections
  • create a new archetype - a template for when one wants to add a new article to that section

More Documentation

For more you should read the official hugo documentation

Image optimization

Image optimization that reduces file size of the images with minimal loss of quality.

JPEG images

Check the size optimization status of JPEG images with jpegoptim:

jpegoptim --noaction --preserve static/img/*.jpg

Example output:

static/img/2019-04-privacy-cafe-poster.jpg 1754x2480 24bit N JFIF  [OK] 205821 --> 205821 bytes (0.00%), skipped.
static/img/Tails.jpg 670x350 24bit N Exif XMP Adobe  [OK] 16148 --> 16144 bytes (0.02%), optimized.
static/img/TorMeetup.jpg 1200x600 24bit P JFIF  [OK] 147270 --> 147270 bytes (0.00%), skipped.
static/img/coimbra.jpg 1024x768 24bit N JFIF  [OK] 140231 --> 140231 bytes (0.00%), skipped.
static/img/cryptoparty.jpg 1242x417 24bit P JFIF  [OK] 78302 --> 78302 bytes (0.00%), skipped.
static/img/default_image1.jpg 3840x2160 24bit N ICC Exif JFIF  [OK] 65341 --> 65341 bytes (0.00%), skipped.
static/img/rememberDog.jpg 1024x924 24bit P JFIF  [OK] 98543 --> 98543 bytes (0.00%), skipped.

Optimize a JPEG image with max quality 1:

jpegoptim --preserve --max=1 static/img/default_image1.jpg

Example output:

static/img/default_image1.jpg 3840x2160 24bit N ICC Exif JFIF  [OK] 9072828 --> 65341 bytes (99.28%), optimized.

PNG images

Bulk optimize multiple PNG images with optipng in current directory:

for i in *.png; do optipng -o5 -preserve "$i"; done


PrivacyLx website



No releases published


No packages published
You can’t perform that action at this time.