name mode size
ie6.css 100644 924B
ie7-and-down.css 100644 1.87kB
ie8-and-down.css 100644 320B
layout-rtl.css 100644 5.65kB
layout.css 100644 23.38kB
master-rtl.css 100644 143B
master.css 100644 87B
reset.css 100644 1.12kB
tbbproject.css 100644 5.88kB
thankyou.css 100644 5.89kB
typography-rtl.css 100644 859B
typography.css 100644 6.52kB
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! :)