Here's a brief overview of how our wml set-up works.
----------------------------------------------------
Here's a typical wml file:
http://jqs44zhtxl2uo6gk.onion/project/web/webwml.git/docs/en/bridges.wml
https://gitweb.torproject.org/project/web/webwml.git/docs/en/bridges.wml
The top of the file has:
## translation metadata
# Revision: $Revision$
# Translation-Priority: 1-high
#include "head.wmi" TITLE="Tor: Bridges"
and the bottom of the file has:
#include
and the middle is standard html, plus a few extra tags like
that we've added to automatically link to the translated
pages when they exist. So that wml page produces this html page:
https://www.torproject.org/bridges aka
https://www.torproject.org/bridges.html.en
http://expyuzz4wqqyqhjn.onion/docs/bridges
Then head.wmi and foot.wmi are just other mostly-html files you import
to handle the repeat parts of each page (well, that plus some embedded
perl scripts to generate some of the static content).
http://jqs44zhtxl2uo6gk.onion/project/web/webwml.git/include/head.wmi
http://jqs44zhtxl2uo6gk.onion/project/web/webwml.git/include/foot.wmi
You can basically ignore the wml part of them, and to a first
approximation just think of them as more html.
So in summary, wml is like html with a bit more markup.
----------------------------------------------------
Where it gets interesting is the download page:
http://jqs44zhtxl2uo6gk.onion/project/web/webwml.git/download/en/download-easy.wml
It has the standard header and footer section, but in the body of the page
it includes links like