You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.rdoc
+61-26
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ hatred in my heart for Keynote and yet it is by far the best in the field.
7
7
8
8
The idea is that you setup your markdown slide files in section subdirectories
9
9
and then startup the showoff server in that directory. It will read in your
10
-
showoff.json file for which sections go in which order and then will give
10
+
<tt>showoff.json</tt> file for which sections go in which order and then will give
11
11
you a URL to present from.
12
12
13
13
It can:
@@ -26,21 +26,24 @@ It might will can:
26
26
27
27
* show a timer - elapsed / remaining
28
28
* perform simple animations of images moving between keyframes
29
-
* show syncronized, hidden notes on another browser (like an iphone)
29
+
* show synchronized, hidden notes on another browser (like an iphone)
30
30
* show audience questions / comments (twitter or direct)
31
31
* let audience members go back / catch up as you talk
32
32
* let audience members vote on sections (?)
33
33
* broadcast itself on Bonjour
34
34
* let audience members download slides, code samples or other supplementary material
35
35
* let you write on the slide with your mouse, madden-style via canvas
36
+
* automatically resize text to fit screen
36
37
37
38
Some of the nice things are that you can easily version control it, you
38
39
can easily move sections between presentations, and you can rearrange or
39
40
remove sections easily.
40
41
41
42
= Usage
42
43
43
-
ShowOff is meant to be run in a ShowOff formatted repository - that means that it has a showoff.json file and a number of sections (subdirectories) with markdown files for the slides you're presenting.
44
+
ShowOff is meant to be run in a ShowOff formatted repository - that means that
45
+
it has a <tt>showoff.json</tt> file and a number of sections (subdirectories) with
46
+
markdown files for the slides you're presenting.
44
47
45
48
$ gem install showoff
46
49
$ git clone (showoff-repo)
@@ -50,11 +53,16 @@ ShowOff is meant to be run in a ShowOff formatted repository - that means that i
50
53
If you run 'showoff' in the example subdirectory of ShowOff itself, it will
51
54
show an example presentation, so you can see what it's like.
52
55
56
+
You can also run 'showoff serve' inside a section subdirectory. If there is no
57
+
<tt>showoff.json</tt> file then it will make its best guess, creating a presentation
58
+
from all `.md` files in alphabetical order in the given (or current)
59
+
directory.
60
+
53
61
= Slide Format
54
62
55
63
You can break your slides up into sections of however many subdirectories deep
56
64
you need. ShowOff will recursively check all the directories mentioned in
57
-
your showoff.json file for any markdown files (.md). Each markdown file can
65
+
your <tt>showoff.json</tt> file for any markdown files (.md). Each markdown file can
58
66
have any number of slides in it, separating each slide with the '!SLIDE'
59
67
keyword and optional slide styles.
60
68
@@ -77,7 +85,7 @@ the following contents:
77
85
That represents two slides, the first contains just a large title, and the
78
86
second is faded into view showing the title and three bullets that are then
79
87
incrementally shown. In order for ShowOff to see those slides, your
80
-
showoff.json file needs to look something like this:
88
+
<tt>showoff.json</tt> file needs to look something like this:
81
89
82
90
[
83
91
{"section":"one"}
@@ -147,13 +155,20 @@ The transitions are provided by jQuery Cycle plugin. See http://www.malsup.com/j
147
155
You can manage the presentation with the following keys:
148
156
149
157
* space, cursor right: next slide
150
-
* cursor left: previous slide
158
+
* shift-space, cursor left: previous slide
151
159
* d: debug mode
152
-
* c: table of contents (vi)
160
+
* c, t: table of contents (vi)
153
161
* f: toggle footer
154
-
* z: toggle help
162
+
* z, ?: toggle help
155
163
* p: toggle preshow
156
164
165
+
= Showing plain old markdown
166
+
167
+
If a markdown file has no !SLIDE keywords, then showoff will treat every line
168
+
beginning with a single hash -- i.e. every H1 -- as a new slide in "bullets"
169
+
style. Remember that you can't specify classes or transitions in this mode,
170
+
and as soon as you add one !SLIDE you need them everywhere.
171
+
157
172
= Preshow
158
173
159
174
If you want to show a slideshow while you wait to speak, you can run a preshow. Add a +_preshow+ directory
@@ -166,7 +181,7 @@ audience in the meantime. Press 'p' again to stop, or wait until the timer runs
166
181
167
182
To insert custom JavaScript into your presentation you can either place it into
168
183
a file (with extension .js) into the root directory of your presentation or you
169
-
can embed a <script>-element directly into your slides. This JavaScript will be
184
+
can embed a <+script+> element directly into your slides. This JavaScript will be
170
185
executed—as usually—as soon as it is loaded.
171
186
172
187
If you want to trigger some JavaScript as soon as a certain page is shown or
@@ -223,7 +238,7 @@ The same applies to the *showoff:prev* event, of course.
223
238
224
239
To insert custom Stylesheets into your presentation you can either place it into
225
240
a file (with extension .css) into the root directory of your presentation or
226
-
you can embed a <+link+>-element directly into your slides. This stylesheet will
241
+
you can embed a <+link+>element directly into your slides. This stylesheet will
227
242
be applied as soon as it is loaded.
228
243
229
244
The content generated by the slide is wrapped with a +div+ with the class .+content+ like this.
@@ -311,27 +326,34 @@ added where your cursor was. Binding this to a keybinding can allow you to add
311
326
[<tt>help</tt>] Shows list of commands or help for one command
312
327
[<tt>heroku</tt>] Setup your presentation to serve on Heroku
313
328
[<tt>github</tt>] Setup your presentation to serve on GitHub Pages
314
-
[<tt>serve</tt>] Serves the showoff presentation in the current directory
329
+
[<tt>serve</tt>] Serves the showoff presentation in the current directory (or a given dir)
315
330
[<tt>static</tt>] Generate static version of presentation
316
331
317
-
=== <tt>add [title]</tt>
332
+
333
+
== <tt>showoff add [title]</tt>
318
334
319
335
Add a new slide at the end in a given dir
320
336
321
337
*Aliases*
322
338
* <tt><b>new</b></tt>
323
339
324
-
Outputs or creates a new slide. With -d and -n, a new slide is created in the given dir, numbered to appear as the last slide in that dir (use -u to avoid numbering). Without those, outputs the slide markdown to stdout (useful for shelling out from your editor). You may also specify a source file to use for a code slide
340
+
Outputs or creates a new slide. With -d and -n, a new slide is created in the given dir, numbered to appear
341
+
as the last slide in that dir (use -u to avoid numbering). Without those, outputs the slide markdown to
342
+
stdout (useful for shelling out from your editor). You may also specify a source file to use for a code
343
+
slide.
344
+
345
+
=== options for add
325
346
326
-
==== Options
327
347
These options are specified *after* the command.
328
348
329
349
[<tt>-d, --dir=dir</tt>] Slide dir (where to put a new slide file)
330
350
[<tt>-n, --name=basename</tt>] Slide name (name of the new slide file)
331
351
[<tt>-s, --source=path to file</tt>] Include code from the given file as the slide body
[<tt>-u, --nonumber</tt>] Dont number the slide, use the given name verbatim
334
-
=== <tt>create dir_name</tt>
354
+
355
+
356
+
== <tt>showoff create dir_name</tt>
335
357
336
358
Create new showoff presentation
337
359
@@ -340,57 +362,68 @@ Create new showoff presentation
340
362
341
363
This command helps start a new showoff presentation by setting up the proper directory structure for you. It takes the directory name you would like showoff to create for you.
342
364
343
-
==== Options
365
+
=== options for create
366
+
344
367
These options are specified *after* the command.
345
368
346
369
[<tt>-d, --slidedir=arg</tt>] sample slide directory name <i>( default: <tt>one</tt>)</i>
347
370
[<tt>-n, --nosamples</tt>] Dont create sample slides
348
-
=== <tt>help [command]</tt>
371
+
372
+
373
+
== <tt>showoff help [command]</tt>
349
374
350
375
Shows list of commands or help for one command
351
376
352
-
=== <tt>heroku heroku_name</tt>
377
+
378
+
== <tt>showoff heroku heroku_name</tt>
353
379
354
380
Setup your presentation to serve on Heroku
355
381
356
382
Creates the Gemfile and config.ru file needed to push a showoff pres to heroku. It will then run heroku create for you to register the new project on heroku and add the remote for you. Then all you need to do is commit the new created files and run git push heroku to deploy.
357
383
358
-
=== <tt>github</tt>
384
+
385
+
== <tt>showoff github</tt>
359
386
360
387
Generates a static version of your site and puts it in a gh-pages branch for static serving on GitHub.
361
388
362
-
==== Options
389
+
=== options for github
363
390
These options are specified *after* the command.
364
391
365
392
[<tt>-f, --force</tt>] force overwrite of existing Gemfile/.gems and config.ru files if they exist
366
393
[<tt>-g, --dotgems</tt>] Use older-style .gems file instead of bundler-style Gemfile
367
394
[<tt>-p, --password=arg</tt>] add password protection to your heroku site
368
-
=== <tt>serve </tt>
369
395
370
-
Serves the showoff presentation in the current directory
371
396
397
+
== <tt>showoff serve </tt>
372
398
399
+
Serves the showoff presentation in the current directory
0 commit comments