name mode size
..
orig 040000
agrabeli.png 100644 29.51kB
ailanthus.png 100644 40.2kB
amoghbl1.png 100644 11.88kB
antonela.png 100644 23.27kB
arlolra.png 100644 38.87kB
arma.png 100644 34.87kB
arthuredelstein.png 100644 37.96kB
asn.png 100644 26.19kB
atagar.png 100644 38.42kB
biella.png 100644 34.95kB
cindy.png 100644 36.46kB
dawuud.png 100644 22.26kB
dgoulet.png 100644 14.38kB
donnchac.png 100644 25.04kB
egypcio.png 100644 30.42kB
emmapeel.png 100644 26.22kB
ewyatt.png 100644 20.55kB
flexlibris.png 100644 34.18kB
gunner.png 100644 35.03kB
haxxpop.png 100644 37.33kB
hellais.png 100644 40.39kB
hiro.png 100644 14.84kB
ian.png 100644 40.46kB
inf0.png 100644 18.67kB
irl.png 100644 42.12kB
isabela.png 100644 46.94kB
jselon.png 100644 29.7kB
juga.png 100644 14.03kB
karsten.png 100644 37.33kB
kat5.png 100644 53.7kB
komlo.png 100644 32.19kB
kushal.png 100644 30.34kB
ln5.png 100644 34.93kB
mcs.png 100644 30.52kB
meejah.png 100644 11.19kB
micahflee.png 100644 33.04kB
moritz.png 100644 43.05kB
mtigas.png 100644 39.17kB
n8fr8.png 100644 32.08kB
nickhopper.png 100644 38.1kB
nickm.png 100644 41.52kB
no_photo.png 100644 10.67kB
nyinz.png 100644 33.15kB
ohmygodel.png 100644 32.23kB
pari.png 100644 39.1kB
pastly.png 100644 31.85kB
pepijn.png 100644 31.87kB
phoul.png 100644 5.93kB
ramy.png 100644 36.8kB
redshiftzero.png 100644 45.4kB
robgjansen.png 100644 33.86kB
robt.png 100644 35.27kB
saint.png 100644 36.64kB
sajolida.png 100644 7.49kB
serene.png 100644 33.57kB
sjmurdoch.png 100644 32.43kB
ssteele.png 100644 42.07kB
sstevenson.png 100644 39.26kB
stephw.png 100644 35.53kB
syverson.png 100644 14.05kB
t0mmy.png 100644 25.91kB
tjr.png 100644 26.59kB
wseltzer.png 100644 39kB
README.md
# 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 https://git.torproject.org/project/web/webwml.git 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 git@github.com:mrphs/tpo.git` __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](https://trac.torproject.org) 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 https://git.torproject.org/project/web/webwml.git 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-0.2.6.1-alpha'. 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 www-staging.torproject.org. Alas, https://www.torproject.org/dist/ isn't in version control. You write to it by ssh'ing to dist-master.torproject.org and going to /srv/dist-master.torproject.org/htdocs/ and then sticking your stuff there. When you want it to go live, you run "static-update-component dist.torproject.org" 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