name mode size
agrabeli.jpg 100644 19.75kB
ailanthus.jpg 100644 795.36kB
arlolra.jpg 100644 72.14kB
arma.jpg 100644 74.27kB
arthuredelstein.jpg 100644 18.45kB
atagar.png 100644 116.55kB
cindy.jpg 100644 210.03kB
dawuud.jpg 100644 9.64kB
dgoulet.png 100644 57.78kB
donnchac.jpg 100644 138.28kB
ewyatt.jpg 100644 59.9kB
flexlibris.jpg 100644 615.31kB
gunner.jpg 100644 722.37kB
hellais.jpg 100644 47.75kB
hiro.jpg 100644 12.8kB
ian.jpg 100644 30.79kB
inf0.jpg 100644 21.09kB
isabela.jpg 100644 16.82kB
isis.jpg 100644 46.06kB
jselon.jpg 100644 33.18kB
karsten.jpg 100644 90.83kB
komlo.jpg 100644 23.45kB
linda.jpg 100644 910.79kB
ln5.jpg 100644 18.82kB
meejah.svg 100644 18.61kB
moritz.png 100644 731.58kB
n8fr8.jpg 100644 21.84kB
nickcalyx.png 100644 550.68kB
nickhopper.jpg 100644 20.25kB
ohmygodel.jpg 100644 25.96kB
pepijn.jpg 100644 1.03MB
phoul.jpg 100644 14.22kB
robgjansen.jpg 100644 24.94kB
robt.png 100644 689.36kB
saint.jpg 100644 81.83kB
serene.jpg 100644 42.79kB
sjmurdoch.jpg 100644 115.66kB
ssteele.jpg 100644 18.89kB
stephw.jpeg 100644 370.74kB
syverson.jpg 100644 729.69kB
t0mmy.jpg 100644 50.51kB
tjr.jpg 100644 91.68kB
wseltzer.jpg 100644 6.89kB
# How to contribute Thanks for being interested to work on the website, I tried to make a simple how-to for you to quickly get you setup: __Step 1:__ Clone the git repo. git clone cd webwml __Step 1b:__ Create a bare public repository (i.e on Github), where you'd push your commits to. Make sure you're in `webwml` directory, and run: git remote add pick-a-name your-git-url _Example:_ `git remote add tpo-gh` __Step 2:__ Create and switch to a new branch. _In the following example, I've named my branch "docs" as I'm planning to work on the documentations._ git checkout -b docs __Step 3:__ Now you can start working on website and make changes. Once you're done, commit and push it to your public repo. _Example:_ git push tpo-gh docs __Step 4:__ Open a new ticket on [trac]( with a link to your shiny new repo/branch. # Building website Torproject website is being built and published automatically. To quickly get set up and build website locally, simply follow these steps: __Step 1:__ Get the website's build dependencies. sudo apt-get install wml asciidoc __Step 2:__ Configure where to find your tor git repository. It needs this to make the manual page. git clone cd webwml cp Makefile.local.sample Makefile.local Note: Change the `TORGIT` in Makefile.local to point to your tor git repo. __Step 3:__ Make the website. make You should now be able to point your browser at the locally generated site... file:///home/atagar/Desktop/tor/webwml/getinvolved/volunteer.html.en ### Troubleshooting the build The build fails with "Invalid object name". If you get an error like... ---- Contents of STDERR channel: --------- fatal: Invalid object name 'tor-'. asciidoc: FAILED: manpage document title is mandatory No manpage because of asciidoc error or file not available from git at /tmp/wml.zwcq0q/wml.30867.tmp1.wml line 415. This means your tor repository is out of date. Update your tor git repository. ### Some information regarding working with minified CSS and JS sources If you want to edit any of the CSS or JS sources, please bear in mind that the HTML uses the minified versions. We keep in the repository both versions side-to-side. Once you edit the original source make sure you generate the minified version again. Most editors have plugins to minify CSS and JS files. On Debian it is possible to install the yui-compressor package and use it as follows: yui-compressor myfile.js -o myfile-min.js If you are wondering why is it "cool" to minify sources even though compression is used on the server, please consider that Minification can be well be used in combination with gzipping sources. Minification does a lot of additional things that compression doesn't do. During minification comments are removed, long variables are renamed to shorter variable names, etc. Transferred data can be significantly smaller after minification, than by simply compressing the original. Although this depends a lot on the original source, minifying helps with mobile browsers and slower connections. ### More detailed instructions from Roger _Note: This section was written when website repo was still on svn, and it wasn't built automatically._ 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! :) # tp_donation