Translations: en

I (Pat David) am creating this page to keep notes and information for building/maintaining the new site.

(Meta) pages of interest:

Le travail que je fais ici est basée sur un couple de suggestions de la dernière année (ou plus, je suis sûr) pour actualiser la conception de WGO. En particulier, je l’avais créé une brève maquette pour montrer et ai été d’utiliser cela comme une sorte de guide visuel pour approcher la page principale. Vous pouvez voir que maquette .PNG ici (~ 1.8MB), ou un petit aperçu:

GIMP Mockup Pat David


There are two main reasons for Why we might want to revamp the site: Modernization and Collaboration.


A new facelift for the website can’t hurt from a PR standpoint. We can also leverage more modern design ideas around responsiveness for various screen sizes.

There was no good method previously of writing news/blog-type postings that would easily maintain a post history that could be referred to. A modernization effort can take that into account and allow for a means to post news items that will be archived and maintained for posterity. For example, you can read about a GIMP Perl release candidate from June, 2014, as well as have a permalink to that particular news item in the future.


I have no data to back this up, but can’t help feel that some of the lack of new tutorials or content for the site could be attributed to the convoluted ways to submit information (plus it is generally more lucrative for folks to host their own tutorials and content in an effort to monetize them vs. sharing them openly here).

If someone does want to submit new content, it can only be helpful to make the barrier to collaboration as low as possible.

Currently, if someone wants to contribute content, and test it before attempting to push it, they need to:

  • Get a working instance of Apache httpd running (with SSI)
  • Get familiar with git to pull down the current site
  • Write everything in plain html

Some of these things are non-trivial. Especially for someone who may be good at writing quality content but not technically inclined enough to stand up the build environment.

The How section below covers the means to making things easier to test and contribute.


I thought a bit about the main reasons a person would be visiting the site. What is someone looking to do when coming to WGO?

These are what I thought would be the main reasons for visiting the site (in order):

  1. Download/Get GIMP
  2. Learn about GIMP
  3. Learn how to use GIMP (tutorials + documentation)
  4. Help the project (financially or manpower)
  5. News

It seems like #2 would probably cease being a reason after someone has learned about the project.


After talking with schumaml, it was decided to leverage the existing Python on the server to build the site. Some research revealed that the most ubiquitous (read: maintained) static site generator for Python is Pelican.

The basic workflow for just about any SSG (static site generator) is to take a directory full of content (writing, images, and other assets), then process them in some fashion before finally writing a new directory containing the site ready for upload.

The build systems will often help to abstract away portions of the underlying html. For instance, many will take files written as Markdown or reStructuredText, which are simpler format for writing content that can easily be parsed into html (or other formats).

Python & Pelican

For anyone who wants to build and view the site, they will need only Python, and a couple of extra components (Pelican, Markdown, typogrify). This is the same procedure anyone can use to test new content they would like to propose or push.

Getting a build environment

  1. Install Python.
    2.7.x is best, earlier versions are not supported.
    Only provisional support for 3.3+.
  2. Install Pelican.
    Simplest method is simply: pip install pelican
  3. Install some extra components:
    • For Markdown support:
      pip install Markdown
    • For fancy typography elements with typogrify:
      pip install typogrify

For detailed information refer to the Pelican documentation.

Building the site

Building the site is relatively straightforward:

From the project directory, simply invoke pelican:


If you are writing content or developing other parts of the site, there is an option to watch the directory of files for changes and to automatically re-compile the site as needed:

pelican -r

In some cases, it can be beneficial to avoid using the cache that Pelican creates internally (to help speed up the build). To avoid using the cache, and to watch for changes and rebuild as necessary:

pelican -r --ignore-cache

Viewing the site

Python has a simple web server available to preview the site.

For Python 2:
cd output
python -m SimpleHTTPServer

For Python 3:
cd output
python m http.server

The site can then be accessed locally at:

Further notes on using Pelican can be found on the page Using Pelican.


Fluffle Puff
This is not superfluous, it’s a test of local image linking from this directory.