name mode size
N900.wml 100644 5.82kB
android.wml 100644 5.66kB
bridges.wml 100644 10.53kB
debian-vidalia.wml 100644 3.82kB
debian.wml 100644 6.74kB
documentation.wml 100644 12.63kB
faq-abuse.wml 100644 23.78kB
faq.wml 100644 173.96kB
hidden-services.wml 100644 7.45kB
installguide.wml 100644 656B
manual.wml 100644 596B
pluggable-transports.wml 100644 7.25kB
proxychain.wml 100644 2.32kB
rpms.wml 100644 4.45kB
running-a-mirror.wml 100644 5.14kB
short-user-manual.wml 100644 3.05kB
sidenav.wmi 100644 3.11kB
signing-keys.wml 100644 8.21kB
tor-doc-osx.wml 100644 6.32kB
tor-doc-relay.wml 100644 8.29kB
tor-doc-unix.wml 100644 5.35kB
tor-doc-win32.wml 100644 160B
tor-doc-windows.wml 100644 6.66kB
tor-hidden-service.wml 100644 9.81kB
tor-manual-dev.wml 100644 926B
tor-manual.wml 100644 929B
tor-relay-debian.wml 100644 7.91kB
trademark-faq.wml 100644 7.09kB
verifying-signatures.wml 100644 12.42kB
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! :)