Better documentation for fragment transitions

[ssokolow]

Please improve the documentation for fragments transitions.

As an example of where it falls short, I'm trying to put together a slide with an image and some text, where the image remains static but the accompanying text is paged through paragraph-by-paragraph, and I can't figure out how to avoid having a "blank" (only the image) sub-slide.

If I make the first fragment fade-out, then the blank subslide appears between the first and second ones. If I make the first fragment fade-in-then-out, then the blank subslide appears at the beginning.

If the CSS classes were programmatically generated, I'd expect what I'm looking for to be called then-out. (i.e. The "disable 'hidden by default' effect of using fade-out, the step-collapsing effect of using a -then-out-suffixed class, and not the step-introducing effect of using fade-in on it.)

I've tried putting various classes from the DOM Inspector relating to visibility on the first fragment, like visible and current-fragment (speaking of which, current-visible is documented with the same description as fade-in-the-nout) but that was a bust.

I tried custom, thinking that maybe "Note that we are adding a custom class to each fragment. This tells reveal.js to avoid applying its default fade-in fragment styles." would be a hack for achieving what I want, but no such luck.

I tried nesting, but that just got rid of the r-stack effect that was the whole point of the exercise.

I tried using data-fragment-index, thinking that maybe forcing it to zero-based indexing would "replace the initial blank state with the first fragment", but no luck.

In the end, I gave and I'm currently investigating the least fragile way to take the brute-force approach and use JavaScript... possibly involving synthesizing input event to duplicate the key/mouse input if a single instance of it would land on a blank state.

[ssokolow]

Oops. Sorry. I just realized I only looked at the .../revealjs part of the repo name and clicked "New Issue" in the wrong tab.