The following is a general strategy.
 
-{section: Downloads}
-
-Put the files up for download!  There is no reason to not just offer for download the exact same files created for streaming (below).
-
-One solution:
-
-1: {code}cd where-ever-your-web-page-is{endcode}
-2: {code}mkdir download{endcode}
-3: {code}cd download{endcode}
-4: {code}ls ../*.mp4 ../*.webm | xargs -n1 --replace ln -s '{}' ./{endcode}
-5: {code}cat > .htaccess <<END
-AddType application/octet-stream .mp4
-AddType application/octet-stream .webm
-
-<Files "*">
-	Header set Content-Disposition attachment
-</Files>
-END
-{endcode}
-
-The .htaccess file ensures the files are served without a useful MIME type, discouraging browsers from trying to use them, and adds "Content-Disposition: attachment", which tells browsers to default to offering to save the file.
-
-Having the .htaccess file do this requires that the main Apache configuration allow it.  As of October 2014, the CSL's web server does.2
 
 {section: Streaming}
 
@@ -67,6 +44,30 @@
 ffmpeg -i input.mp4 -ss 0 -vframes 1 input.jpg
 {endcode}
 
+{section: Downloads}
+
+Put the files up for download!  There is no reason to not just offer for download the exact same files created for streaming (below).
+
+One solution:
+
+1: {code}cd where-ever-your-web-page-is{endcode}
+2: {code}mkdir download{endcode}
+3: {code}cd download{endcode}
+4: {code}ls ../*.mp4 ../*.webm | xargs -n1 --replace ln -s '{}' ./{endcode}
+5: {code}cat > .htaccess <<END
+AddType application/octet-stream .mp4
+AddType application/octet-stream .webm
+
+<Files "*">
+	Header set Content-Disposition attachment
+</Files>
+END
+{endcode}
+
+The .htaccess file ensures the files are served without a useful MIME type, discouraging browsers from trying to use them, and adds "Content-Disposition: attachment", which tells browsers to default to offering to save the file.
+
+Having the .htaccess file do this requires that the main Apache configuration allow it.  As of October 2014, the CSL's web server does.
+
 {section: Creating the HTML}
 
 If you're using our normal Mason system (generate_html), there is a module to simplify this.  It assumes you have the video as .webm, .mp4, and a .jpg poster in the current directory, and that the download/ subdirectory contains symlinks to the webm and mp4 files.  Given this, here is an example of using the video.mas module.  It's for Karen's 2014 user tutorial. All of the files are named "Intro_To_Using_HTCondor.*" and the video is 640x320.
@@ -84,14 +85,22 @@
 If you need to do it by hand, check out htcondor/src/lib/video.mas in the htcondor-web repository.  Here is a very simple example:
 
 {code}
-<p><video width="640" height="360" controls poster="FILENAME_GOES_HERE.jpg">
-<source src="FILENAME_GOES_HERE.mp4 type="video/mp4; codecs=avc1.42E01E,mp4a.40.2">
-<source src="FILENAME_GOES_HERE.webm" type="video/webm; codecs=vp8,vorbis">
+&lt;p&gt;&lt;video width="640" height="360" controls poster="FILENAME_GOES_HERE.jpg"&gt;
+&lt;source src="FILENAME_GOES_HERE.mp4 type="video/mp4; codecs=avc1.42E01E,mp4a.40.2"&gt;
+&lt;source src="FILENAME_GOES_HERE.webm" type="video/webm; codecs=vp8,vorbis"&gt;
 Sorry, your web browser does not appear to support HTML5 video.
-</video>
+&lt;/video&gt;
+
+&lt;p&gt;Download video:
+&lt;a href="download/FILENAME_GOES_HERE.mp4"&gt;MP4&lt;/a&gt;
+&lt;a href="download/FILENAME_GOES_HERE.webm"&gt;WebM&lt;/a&gt;
+
+&lt;p&gt;Download slides:
+&lt;a href="SOME_OTHER_PLACE.ppt"&gt;Powerpoint&lt;/a&gt;
+&lt;a href="SOME_OTHER_PLACE.pdf"&gt;PDF&lt;/a&gt;
 {endcode}
 
-<p>Be sure to also include links to download the file and to the slides.
+Be sure to also include links to download the file and to the slides.
 
 {section: Editing with ffmpeg}