organizing a semester's worth of slideshows

[Lenore Horner]

My current level of understanding is that slideshow is a top element and so can only have section, subsection, and subsubsection  divisions organizing individual slides, that each slideshow is therefore an entire project and that I can only deploy one project to a gh-pages repository.  This presents me with an organizational problem because my daily (using Beamer until now) slideshows typically have sections and sometimes even subsections.  In my brain, that means each unit will require its own slideshow and its own repository.  This seems like a lot of clutter.  Am I missing something or should I just plow ahead?  Is there a cap on the number of repositories I can create in GitHub?  

I've seen Oscar Levine's Course example, but the slides section is blank so I don't know how he intended to get around the challenges I outlined above.  Otherwise, having one container for the course is the route I'd like to go.

TIA,

Lenore Horner

7 Hills

Cincinnati, OH

[Oscar Levin]

A few ideas to avoid the multi repository churn:

1. Make fewer slideshows, each divided with one section per class.  Using reveal, you get vertical progression for each class, horizontal switches the day.

2. Include many root slideshows in the same repository and manage them with project.ptx.  That is, you can have multiple targets listed, and set each to deploy to the same root GitHub pages site.  

3. A while back I added some support for building standalone targets.  This could probably use some work, but that would be a way to set up number 2 without putting in a separate target for each slideshow.

--
You received this message because you are subscribed to the Google Groups "PreTeXt support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/af2748ce-63ac-47b3-956f-843ab3e297fbn%40googlegroups.com.

[Rob Beezer]

Dear Lenore,

One clarification, which probably does not help with your problem (sorry!).

#subsection and #subsubsection should not be effective in a #slideshow.

We recycle #section as the lone organizational device within #slideshow. A
#slide is the primary (only?) unit of content. We do have #subslide (iirc)
mostly as a home for a @pause on a chunk of material.

Perhaps I should (finally) get #slideshow into the schema, it woul help with
these distinctions.

Also, the conversion to Beamer has been brought back from the dead, should you
want to go back (way back) to PDFs.

Both conversions (to Reveal and to Beamer) are only evolving with author and
publisher requests, so feel free to holler if something needs work.

Thanks,
Rob

> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email

> to pretext-suppo...@googlegroups.com <mailto:pretext-
> support+u...@googlegroups.com>.

> To view this discussion visit https://groups.google.com/d/msgid/pretext-support/

> af2748ce-63ac-47b3-956f-843ab3e297fbn%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-support/
> af2748ce-63ac-47b3-956f-843ab3e297fbn%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Rob Beezer]

On 8/23/26 09:42, 'Rob Beezer' via PreTeXt support wrote:
> Perhaps I should (finally) get #slideshow into the schema, it woul help with
> these distinctions.

Oops - already in the (main) schema. From like two weeks ago. My assistant
sometimes moves too fast for me to keep up...

So, Lenore, validating against the schema should complain about any #subsection,
and once they are gone, the #subsubsection.

[Horner, Lenore]

I think I'm more confused now.

I did see the standalone options in the course template.  I played with a bit but for starters either have to take slides.ptx out of the slides folder or not use the docinfo because the hierarchy is off with slides.ptx a level lower than main.ptx.  I also thought I read that standalone would make asymptote figures non-interactive but I haven't experimented so perhaps I misunderstood what I read.

I did try adding separate slides to a template I'd already set of a github pages repository for.  When I ran deploy, the slides replaced the previous web content.  Perhaps there are flags for deploy that I haven't learned yet but at present I don't see a way to build separate outputs for the web and deploy them to the same archive.

I'm even more confused about removing the section structure from slideshows.  What's the point of the 2D navigation then?  Why would I want an absolutely flat slideshow.

I haven't experimented with pause because it seemed to work like Beamer pause which produce an extremely frustrating pdf output that would not be productive for my students to use as guided notes.

I may have to try to hack the <page> entity to a more slide-like aspect ratio and use <handout> for projection to match what my students can download and annotate.  

Lenore Horner Upper Math/Physics Teacher She/Her/Hers
	5400 Red Bank Road Cincinnati, OH 45227 o: 513.728.2477 w: 7hills.org

--
You received this message because you are subscribed to the Google Groups "PreTeXt support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/MTAwMDA0Q0tReUk3WGw.1787505002%40pnsh.

[Oscar Levin]

If you have multiple targets in project.ptx, and you want each of them to be deployed, you add a deploy-dir attribute to each target.  When you deploy, every target that has a deploy-dir will get deployed to that folder.

The standalone is different from the portable build.  In this context, it is just a way to build the "current" open file, instead of a file specified in project.ptx

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CAMWUnDGxhV9aTzvH_Zd75EVRoi8Cy2RD4m83zbgcpd89FSErug%40mail.gmail.com.

[Horner, Lenore]

Thank you Oscar, the deploy-dir helped a lot.  

I can now generate the course with everything but the slides as a package with a single navigation bar and if I link to the directory given by the deploy statement, I see a link to the course and a link to the slides.  However, building the slideshows individually (with the -i command) puts them in the slides directory but nothing generates an index.html for that directory and populates it with links to each individual slideshow.  I can post direct links to each slideshow I think so this isn't a show stopper, but a hitch nonetheless.  Any ideas?

Lenore

Lenore Horner Upper Math/Physics Teacher She/Her/Hers
	5400 Red Bank Road Cincinnati, OH 45227 o: 513.728.2477 w: 7hills.org

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CAOU9BaU4sQA4nf7DRm%2B3RS5OU7G%2B_-_G5KtOMs5dmivNpFWcgA%40mail.gmail.com.

[Oscar Levin]

Here is what I was thinking for multiple slide decks.  Your project.ptx manifest would have something like this:

...

<target name="slides-week-1" format="revealjs" source="slides/week1.ptx" output-filename="index.html" deploy-dir="slides/week1"/>

<target name="slides-week-2" format="revealjs" source="slides/week2.ptx" output-filename="index.html" deploy-dir="slides/week2"/>

<target name="slides-week-3" format="revealjs" source="slides/week3.ptx" output-filename="index.html" deploy-dir="slides/week3"/>

...

Then when after you build a target (pretext build slides-week-2) or build all deployable targets (pretext build --deploys) and then do a deploy (pretext deploy), you will get a landing page that has links to each individual slide deck.

I agree that we should make it easier to get a list of outputs from a bunch of standalone builds, but it might be a while until I can implement that (I'm not entirely sure what the expected behavior should be).

Hope this helps.

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CAMWUnDHZT%3DD%3DV_1ZUcuAXYoRYLN7aBpgw3iArFcip0ijZbkn8A%40mail.gmail.com.

[Horner, Lenore]

I added the following to my project.ptx

    <target name="slides_2026-08-26" format="revealjs" source="slides_2026-08-26_diff-eq-math-models.ptx" output-filename="index.html" deploy-dir="slides/slides_2026-08-26_diff-eq-math-models"/>
    <target name="slides_2026-08-28" format="revealjs" source="slides_2026-08-28_integrals-as-solns.ptx" output-filename="index.html" deploy-dir="slides/slides_2026-08-28_integrals-as-solns"/>

At first I wasn't getting the second slideshow to build with --deploys, but now it seems to be working.  The "output" folder does not obey the location instructions from the deploy statement but "stage" does.  Maybe there is a "output-dir" I should be using?  Because having "output" and "stage" not the same means local works or publicly available works, but not both.

At any rate, I've succeeded in adding directly links in main.ptx in the slides chapter to the deploy-dir locations which means the daily slide shows can be reached from the course directly.  

Thanks Oscar for your help with this.

Lenore

Lenore Horner Upper Math/Physics Teacher She/Her/Hers
	5400 Red Bank Road Cincinnati, OH 45227 o: 513.728.2477 w: 7hills.org

You received this message because you are subscribed to a topic in the Google Groups "PreTeXt support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-support/c_bFFwEf4lo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CAOU9BaW%2BzprbZhj2gjKbcFgoTq181hGyNbu1wwzwe7CO%3DfVyKw%40mail.gmail.com.

[Sean Fitzpatrick]

Late to this, but in case it's useful: 

When I used slides, I had the whole semester in one file. 

Each class was a section, and then in each section I'd have my slides for that class. 

Left/right arrow keys to move between days, and up/down to move between slides for one day. 

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/CAMWUnDErJ7rL7PPTm6TnFJqhed41DD%2BGOtH8fzYnDDC%2BzHX98w%40mail.gmail.com.