Go to file
2014-01-20 16:14:54 +00:00
about some of these were pre-501(c)(3), some weren't, so remove the distinction 2013-12-17 18:09:40 +00:00
cgi-bin first cut of the new, shiny tor website as wml. 2010-07-09 01:55:22 +00:00
css Adding tor ecosystem presentation to the volunteer page 2013-12-16 17:25:57 +00:00
docs Fixed a couple typos 2014-01-20 16:14:54 +00:00
donate explain our limit so people stop trying to donation billions via bitpay. 2014-01-01 20:36:03 +00:00
download change to $10 per ticket 10435 2013-12-22 18:15:02 +00:00
eff fix the link to RIAA vs. Verizon pdf on eff's site. Thanks to Christian for the notice. 2012-11-26 21:03:28 +00:00
en announce tbb 3.5, and also point to the transition faq 2013-12-20 05:31:32 +00:00
getinvolved Renaming JTor to Orchid 2014-01-12 20:55:06 +00:00
images finish ticket #10129 2013-12-17 19:07:01 +00:00
include update mirror status. 2014-01-18 16:56:23 +00:00
js patch to dlpage01 javascript. 2012-04-26 00:36:52 +00:00
manpages Update wiki links 2011-06-11 18:55:49 +00:00
press patch from ticket 10556 for press page. 2014-01-05 01:57:37 +00:00
projects Update obfsproxy instructions now that 0.2.4.x is not experimental anymore. 2014-01-04 17:10:55 +00:00
torbutton removed torbutton pages, moved 2 questions to general FAQ (#6567) 2013-03-26 04:38:32 +00:00
tordnsel Add the exitlist file to the website so that it doesn't get 2011-05-01 10:23:27 +00:00
.gitignore Add some more HTML files to the .gitignore. 2013-01-22 22:01:15 +00:00
.htaccess make tpo/torbrowser rewrite to torbrowser.html.en. 2012-11-13 02:03:01 +00:00
favicon.ico add a favicon.ico 2010-10-18 04:30:52 +00:00
Makefile new stable is 0.2.4.20 2013-12-23 06:43:16 +00:00
Makefile.common only build English website files, please 2011-09-28 10:12:28 +00:00
Makefile.local.sample Move the TORGIT config option to Makefile.local 2012-02-17 16:50:37 +00:00
po2wml.sh fix download.wml when we convert from .po and make sure fa translations get the right wmi files 2011-09-04 22:27:54 +00:00
publish capture my "how to edit the website" instructions to dcf, for posterity 2013-10-17 03:08:47 +00:00
README capture my "how to edit the website" instructions to dcf, for posterity 2013-10-17 03:08:47 +00:00
robots.txt sitemap no longer exists. remove from robots. 2012-07-05 19:23:30 +00:00
update-mirrors.pl update the mirrors page, have the script update the csv list with last status. 2013-12-06 15:54:04 +00:00
wml2po.sh minor fix 2011-09-05 00:36:50 +00:00

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-torobfsbundlelinux64alpha>. 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.)

If you want to push your locally built website to the remote webserver,
run the ./publish script in website/trunk/. It will rsync everything
over, and then it will ask www-master.tp.o to run its trigger-mirrors
script which causes www-master to rsync to all the servers in the www.tp.o
rotation. To push the website, you'll need to be in the torwww ldap group
(which is separate from whether you can commit to svn).

Alas, https://www.torproject.org/dist/ isn't in version control. You
write to it by ssh'ing to www-master.torproject.org and going to
/srv/www-master.torproject.org/htdocs/dist/ and then sticking your stuff
there. When you want it to go live, you run ./publish from your local
website checkout, which will trigger the trigger-mirrors run. (It's
possible that you can simply run /home/mirroradm/bin/trigger-mirrors on
www-master too, but I've never tried.)

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! :)