name mode size
10_success-small.png 100644 226.41kB
10_success.png 100644 174.21kB
11_after_rebooting-small.png 100644 52.13kB
11_after_rebooting.png 100644 43.98kB
12_status_menu-small.png 100644 122.21kB
12_status_menu.png 100644 99.05kB
13_enable_tor-small.png 100644 92.25kB
13_enable_tor.png 100644 70.97kB
14_check_tor-small.png 100644 76.88kB
14_check_tor.png 100644 49.64kB
1_app_menu-small.png 100644 262.27kB
1_app_menu.png 100644 297.2kB
2_app_manager-small.png 100644 187.99kB
2_app_manager.png 100644 242.69kB
3_app_managermenu-small.png 100644 144.67kB
3_app_managermenu.png 100644 108.58kB
4_catalog_list-small.png 100644 67.68kB
4_catalog_list.png 100644 55.93kB
5_new_catalog-small.png 100644 104.91kB
5_new_catalog.png 100644 75.18kB
6_app_manager-small.png 100644 187.39kB
6_app_manager.png 100644 241.88kB
7_app_categories-small.png 100644 137.32kB
7_app_categories.png 100644 116.19kB
8_app_list-small.png 100644 98.29kB
8_app_list.png 100644 72.47kB
9_disclaimer-small.png 100644 139.48kB
9_disclaimer.png 100644 84.44kB
Here are the instructions I sent David Fifield when he asked about editing the website. I hope they are useful for you too! --Roger Copy Makefile.local.sample to Makefile.local in your webwml/ directory. Point TORGIT 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 git commit any changes to the wml files. 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 dist-master. 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! :)