Feedback: navigation within a slide deck needs to happen with `history.replaceState` not `history.pushState` so that it is possible to leave the page again after scrolling around a bit. As it is the back button forces me to back out through my entire scroll history to get to the web page I was previously on which is an anger-inducing experience I would not want to subject others to.
As mentioned if plain text is your goal it would be really nice if there were some way to serve the content as plain HTML as a backup
That was something I thought deeply about. I decided that an imaginary user would see a page change as a navigation event. Pressing back and having the whole thing poof could be just as anger inducing. Most SPAs use some type of router to do just that.. I imagine I won’t hear from anyone who prefers it that way so until I can afford some user testing I won’t know. Quite a bit of anxiety about that one. I had initially used replaceState…
Yes, plain text to create it not displayed as plain text. I didn’t write the post so the title may be a little misleading. Flashy JS heavy output for minimal input is the point.
I scrolled down. Then I scrolled up. Then I scrolled down. Then I scrolled up. Then I was ready to leave so I hit the back button. Only instead of that happening, I was scrolled up, and down, and up, and down, and up, and then I could leave.
Taken to the extreme, I think it becomes more apparent which choice is better.
In this case I meant you can use plain old text to render a webpage… which is what you do anyway but I thought I’d make up another way that people who love text but don’t code might find useful.
There’s two sides to it, an author creating something using plain text in the authoring tool and a reader viewing the final product. So the author uses plain text to get their point across to the reader.
When you’ve created something you can publish it and the reader can view it at a URL. The author obviously isn’t trying to get a point across to themselves in the app.
The authoring tool is a web app and does quite a lot so it is JS heavy. It works well on mobile but the demo only works in landscape as the mobile version is slimmed down so you do have to rotate your phone.
Black on blue/purple (what color is that?) and viceversa are probably fashionable but not the most readable combinations. For sure they are a way to force readers to put extra effort into reading so maybe it's a deliberate choice: whoever gets the point is really interested. Survivor bias.
In step 46 of the demo walkthrough, the little popup bubble says "Viola!.". The word you're looking for there is "Voilà!" (minus the extraneous period)
Seems like an interesting project and I can see the appeal to markdown aficionados (me among them, although I don't currently have much need to do presentations)!
You can use it to produce any kind of multimedia webpage. Some restaurants are utilizing it by printing out the QR code it produces so customers can see their menu.
Not knowing whether a tap shows more text or moves to the next slide makes me super anxious. Would love an indicator whether there's more text for the slide in the next tap.
That was something I went back and forth on and eventually decided that there was too much negative space when the browser chrome disappeared but all the content is accessible, or should be anyway. If not please let me know. Thanks.
As mentioned if plain text is your goal it would be really nice if there were some way to serve the content as plain HTML as a backup