[gimp-web/migrate/py3] README.md: adjust to changes to the pelicanconf.* files and Makefile

[Michael Schumacher <schumaml src gnome org>]

commit 5536cfa06035ca04639cd5482244f2cce569b5e7
Author: Michael Schumacher <schumaml gmx de>
Date:   Tue Apr 21 20:17:30 2020 +0200

    README.md: adjust to changes to the pelicanconf.* files and Makefile

 README.md | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)
---
diff --git a/README.md b/README.md
index 72fabcb0..e61a3b28 100644
--- a/README.md
+++ b/README.md
@@ -26,6 +26,7 @@ The tools to build and test the site are Python, Pelican, and a couple of module
    For sanity, it is recommended to use a [virtual environment](https://docs.python.org/3/library/venv.html).
     ```
     python3 -m venv py3-venv
+    source py3-venv/bin/activate
     ```
 2. Install build requirements located in `py3-requirements.txt`.  
    This can be done easily by running `pip install -r py3-requirements.txt`.
@@ -87,11 +88,12 @@ To de-activate, `deactivate`.
 ###  Pelican configuration files (pelicanconf.*)
 The main settings file to build the site is pelicanconf.*.
 
-There are three versions in our directory for various needs.
+There are four versions in our directory for various needs.
 
 1. pelicanconf.py - this is the main settings file that coincides to WGO (www.gimp.org).
 2. pelicanconf.testing.py - this is the settings file for building testing.gimp.org.
-3. pelicanconf.local.py - this is a settings file tailored for a local build and test environment.
+3. pelicanconf.static.py - this is the settings file for building static.gimp.org.
+4. pelicanconf.local.py - this is a settings file tailored for a local build and test environment.
 
 Unless you are monkeying with site-wide build settings, you shouldn't normally have to edit these files.
 If you do, please consult schumaml or patdavid before pushing to be sure.
@@ -101,13 +103,15 @@ If you do, please consult schumaml or patdavid before pushing to be sure.
 Once the few prerequisites are installed, building the site is relatively straightforward.
 From the project directory, you can invoke pelican:
 
-`pelican -s pelicanconf_common.py`
+`pelican -s pelicanconf.py`
 
-This will build the site into a directory called `output`.
+This will build the site into a directory called `output`. Use one of the pelicanconfig files mentioned 
above depending on what version of the site you want to build.
+
+You can also use `make` to build the site: `make html`, `make testing`, `make static` or `make local` invoke 
the build for the corresponding version.
 
 If you are writing content or developing the site, there is an option to have pelican watch the directories 
for file changes and to automatically recompile the site when a change is detected:
 
-`pelican -r -s pelicanconf_common.py`
+`pelican -r -s pelicanconf.py`
 
 
 ### Viewing the site