name mode size
board.wml 100644 3.35kB
contact.wml 100644 4.73kB
contributors.wml 100644 6.07kB
corepeople.wml 100644 17.49kB
financials.wml 100644 2.87kB
gsoc.wml 100644 11.93kB
jobs-browserhacker.wml 100644 6.55kB
jobs-controller.wml 100644 6.5kB
jobs-coredev.wml 100644 5.24kB
jobs-extdev.wml 100644 6.38kB
jobs-lead-automation.wml 100644 5.77kB
jobs-pluggabletransport.wml 100644 5.02kB
jobs-projectcoordinator.wml 100644 4.72kB
jobs-translatorsupport.wml 100644 3.79kB
jobs.wml 100644 2.14kB
overview.wml 100644 12.81kB
sidenav.wmi 100644 1.67kB
sponsors.wml 100644 4.15kB
torusers.wml 100644 21.91kB
translators.wml 100644 1.09kB
volunteers.wml 100644 3.38kB
Here are the instructions I sent David Fifield when he asked about editing the website. I hope they are useful for you too! --Roger See the Makefile.local file in your website/trunk/ directory. Uncomment TORGIT and point it to a tor git. Then apt-get install wml and (alas) probably a shocking number of other debs. Then you can type 'make' and it will build the website for you locally. It's probably a smart move to see whether 'make' works before you svn commit any changes to the wml file. You can edit docs/en/pluggable-transports.wml (and that is the right source file to edit, not the html). But go take a look at that file. You'll notice it has a bunch of tags like <version-torbrowserbundle>. If you're just bumping version numbers, you probably just want to change the definition of those tags. They're in include/versions.wmi (Every once in a while you may need to edit pluggable-transports.wml too -- generally when you change the file name so drastically that just changing the versions.wmi tags isn't enough.) Pushes to the master branch of the git repository will cause the website to get re-built and published. pushing to the staging branch will update Alas, isn't in version control. You write to it by ssh'ing to and going to /srv/ and then sticking your stuff there. When you want it to go live, you run static-update-component on staticiforme. Weasel has hopes that somebody will write some scripts to make maintaining packages in dist/ less awful -- automatically check that they have signatures and that the sigs match, that the items on the website are in fact in dist, only allow certain people to put files in certain places, etc. One day! :)