There are a bunch of tools in this directory and elsewhere for making slides using standards:
The current recommendation (2005/5) is to use Dave Raggett's slideshow tool HTML Slidy, with its accompanying style sheet. If you are a member of the W3C staff, you must add a W3C icon. Some reasons for doing it this way:
But…
Some example talks of various vintages:
It should include the following:
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title>your titleL</title> <link rel="stylesheet" href="show.css" type="text/css" media=" screen, projection" /> <link rel="stylesheet" href="print.css" type="text/css" media="print" /> <script src="slidy.js" type="text/javascript"> </script> </head>
For W3C staff members, talks must include the W3C icon. The head of the document will therefore include altogether:
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <meta name="copyright" content="Copyright © 2005 W3C (MIT, ERCIM, Keio) /> <title>Slide Shows in XHTML</title> <link rel="stylesheet" href="show.css" type="text/css" media=" screen, projection" /> <link rel="stylesheet" href="print.css" type="text/css" media="print" /> <link rel="stylesheet" href="w3c-blue.css" type="text/css" media=" screen, projection" /> <script src="slidy.js" type="text/javascript"> </script> </head>
There are more details on the HTML Slidy page.
If yours slides are on the www.w3.org server, make the paths relative such as ../../../2005/03 and so on, so they can be used in checked out CVS file space.
Each slide has to be wrapped in <div class="slide"> ...
</div>
If you have an existing talk using the earlier slideme tools, then
you use the ,slideme comma tool to convert it automatically.
Just append ",slideme" after "all.htm" for your slideme base file.
Alternatively, you can do a global change of all <h1> to
</div><div class="slide"><h1> and then fix up
the first and last slides by deleting the extra </div> at
the top and putting in the missing one at the bottom.
This can be done. You just have to be careful to preserve the divs. You can move slides around, by pressing ESC until you have a whole slide selected, cutting it, and then pasting it in between two slides (i.e. not in a div). Note that if you accidentally put text in which is not in a slide division, it will appear in all slides!
The traditional W3C slide format doesn't use DIVs around each slide, instead each H1 starts a slide. The styles for slidemaker & slideme rely on that format. The B6 script is an alternative to Slidy and can be used on slides both with and without DIVs. Its function is to emulate projection mode on browsers that don't support it yet.
To use the B6 script, include something like the following:
<link href="../Tools/w3ctalk-proj.css"> rel=stylesheet media=projection> <script src="../Tools/b6/b6.js" type="text/javascript"></script>
Then turn on Javascript, load the slides and press “A”.
There is also a B6 style sheet, which is the slide
style for W3C's MMI and Mobile activities. It can be used
independently of the B5 script:
<link href="../Tools/b6/b6.css"> rel=stylesheet media=projection>
See the B6 documentation for more info on the B6 script and style, including how to add logos and signatures to the slides.
For older browsers (before 2012), there is the B5 script and style.
The traditional W3C style for slides consists of
three style sheets:
There must be no DIV around the slides and each H1 starts a new slide. See “How to make slides with the W3C style” for documentation.
The last of these style sheets imports slide-1024.css, which is also the style used by slidemaker & slideme. Slidemaker and slideme are (Perl) scripts to split a slide file into multiple files, one slide per file, which is useful if you need to use a browser that doesn't support projection mode and you can't use the Ma href="#b5">B5
or Slidy Javascript files either.For more info, see the documentation on slidemaker and the documentation on slideme. (Slideme is a version of slidemaker that is only available to the W3C Team.)
Shower is an HTML5 presentation engine made by Vadim Makeev (Opera Software). It comes with two good-looking themes and was used for Jeff's presentations at the AC Meeting 2014 to a good response. There's also a simple W3C theme for more consistency with the styles on w3.org.
"shower/themes/ribbon/styles/screen.css" to "shower/themes/w3c/styles/screen.css"<section class="slide">In fact, a copy of the shower code, including the W3C style, has also been placed into /2014/shower/, and the
index-w3c.html has also been added to show the HTML code and as a starting point. That means another way of using shower is to use /2014/shower/shower/themes/w3c/styles/screen.css as a style file, and the javascript reference at the end has to be changed to <script src="/2014/shower/shower/shower.min.js"> (at the very end of the file). Using this approach means that one can save the trouble of copying the whole shower library all the time, although be aware that it may not be the latest version.
Reveal.js is another HTML5 presentation engine made by Hakim El Hattab. It comes with a selection of themes and has fancy slide transitions. It also allows you to move slides vertically rather than just horizontally. There are two W3C themes — light and dark.
"css/theme/default.css" to "css/theme/w3c.css" or "css/theme/w3c.css", depending on which theme you prefer.<section>There is also a copy of reveal.js at /2013/06/revealjs/ which can be used to avoid re-uploading the core files, but be aware that it may not be the latest version.
Last change $Id: Overview.html,v 1.35 2014-07-03 08:53:13 ddavis Exp $
Sign me