IA@UNIPG · Incontro 3, Ricerca e IA · Lab 3 SSH, Scrittura accademica e presentazioni · Centro Linguistico di Ateneo · 29 September 2026

From paper to slides

A deck that says only what the paper says, in your institution's theme, one source at a time.

Niccolò Salvini, PhD

Two decks, one resource at a time

Round 1

Sources: the article, nothing else

Prompt B: content rules

→ deck 1

Round 2

Sources: the article + deck 1 (if it passed the check) + the real photos

Prompt C: B + keep deck 1's structure + only the uploaded photos + the UNIPG theme

→ deck 2

3presentations per account per day, measured on @unipg.it. A deck takes about 7 minutes. Rivedi does not count. Two generations, one spare.

The source

Jo'anne Van Ooijen, Resilient Matters: The Cathedral of Syracuse as an Architectural Palimpsest, Architectural Histories 7(1), 2019, DOI 10.5334/ah.65. Open access, CC BY.

  1. 1notebook.google.com with your @unipg.it account → Create new notebook
  2. 2Add sources → Websites → paste the direct PDF link:
    https://journal.eahn.org/article/7590/galley/21444/download/
  3. 3The summary in the centre talks about the Cathedral of Syracuse? The source is in.
With your own PDFs, the 30-second check first: select a line, copy it, paste it. If it comes out garbled, the model will still answer, with something plausible.

Round 1 · one source, prompt B

Studio → Presentation opens the dialog. Presenter slides (right-hand card), English, sources: only the article. The dialog forgets format and language every time: check them.

Prompt B · content rules
Create a 7-slide presentation on this article for a non-specialist academic audience. Rules: use only what is written in the uploaded article; do not add facts, dates, names, numbers or examples that are not in the text. Every slide title is a full sentence stating what the article claims, not a topic label. Where the author is tentative (suggests, may, possibly), keep the same caution; never turn a hypothesis into a proven fact. Do not generate images of places, buildings or people; use only text, simple diagrams or a timeline. The last slide states the limits and open questions the author acknowledges.

Close the dialog. While it generates, check the claims in chat:

Chat · the claims
Using only the uploaded document, and citing the page for each point: 1. What is the research question? 2. What thesis does the author defend? Write it as one sentence with a verb. 3. What are the three or four claims the thesis rests on? 4. Which limits does the author state explicitly?

Click every number: the passage opens. If it says less than the sentence, that sentence does not go on a slide.

Check a deck: five questions

#Look for
1A picture of a real place or person the tool made up
2A number or date you cannot find in the article
3A title that is a topic instead of a claim
4A verb stronger than the text: suggests → proves. This is the one that matters.
5A theme that holds on some slides and not on others
Generated slides are images, even in the .pptx: read the text yourself. We found "Walls of the central Walls of the central nave" on a timeline.

Round 2 · more sources, prompt C

1 · Deck 1 becomes a source, if it passed

⋮ → Download → PDF → Add sources → Upload file. Only after you checked it: once uploaded, the model treats the deck as true as the article, mistakes included.

2 · The real cathedral, not a drawn one

Download both photos, then Add sources → Upload file. An image cannot be added by URL: the link fails. The photos work only in a new generation: Rivedi on an existing deck ignores sources added later (we tried: it failed twice).

Baroque façade of the Cathedral of Syracuse
Façade · Guillaume, CC BY 2.0, Wikimedia Commons · download
Doric columns of the Greek temple embedded in the cathedral's aisle
Doric columns of the Athenaion · Giovanni Dall'Orto, Wikimedia Commons · download

3 · Generate with all the sources selected

Prompt C · rules + structure + photos + UNIPG theme
Create a 7-slide presentation on this article for a non-specialist academic audience. Rules: use only what is written in the uploaded article; do not add facts, dates, names, numbers or examples that are not in the text. Every slide title is a full sentence stating what the article claims, not a topic label. Where the author is tentative (suggests, may, possibly), keep the same caution; never turn a hypothesis into a proven fact. If a presentation is among the sources, keep its order and its titles unless the article contradicts them. For pictures of the cathedral use only the uploaded photographs, with their credit on the slide; never generate an image of a building, a place or a person. The last slide states the limits and open questions the author acknowledges. Visual theme, University of Perugia, apply it to every slide: white background #FFFFFF; titles and main accent in UNIPG blue #27348B; red #E30613 only for one key word per slide; grey #8D8F95 for captions and sources; light grey #E8E8E8 for boxes and table headers. Font: Roboto for everything. A thin blue rule under each title. Keep the top-right corner empty for the university logo. Flat design: no gradients, no shadows.

A theme is hex codes and a font

Adjectives ("elegant, institutional, blue") give a different result every time. Codes give the same one.

UNIPGValue
blue#27348B
red#E30613
grey#8D8F95
light grey#E8E8E8
fontRoboto

Read from unipg.it: the site's CSS and the logo .svg. For your conference: the colours are in its template (.potx, .sty), its website (browser → Inspect), or its logo .svg (fill="#…"). Swap them into prompt C.

No generations left? Apply the theme to an existing deck with Rivedi, one instruction per slide:

Rivedi · theme only
Restyle only, keep every word, diagram and the layout: white background #FFFFFF; title in UNIPG blue #27348B, Roboto bold, with a thin blue rule under it; one key word in red #E30613; captions in grey #8D8F95; boxes in light grey #E8E8E8; diagram colours only blue #27348B and grey; Roboto for all text; top-right corner left empty.

Rivedi: one slide, one instruction

Open a deck → Rivedi → click a slide → one instruction → Generate revised presentation. It makes a copy "(2)", the original stays. About 2 minutes for one slide, 15 for seven. It does not count toward your three.

Rivedi does not read the sources, not even new ones. It fixes how something is said. What is said is fixed in chat, with the citations open.

Export, and out to Google Slides

  1. ⋮ → Download → PDF, every version you like: you cannot rerun one.
  2. ⋮ → Download → PowerPoint (.pptx) → Google Drive → Open with Google Slides, or File → Import slides into your deck.
  3. Each slide arrives as one picture: you edit around it, not inside it.
Each slide has a small Gemini Notebook badge, and the images carry SynthID, an invisible watermark. Covering the badge is cosmetic: declare the use anyway.

The decks generated this morning

Same article, 29 September 2026. Each PDF is what the tool exported.

DeckWhat to look at
A · one-line prompta generated photo of the cathedral: right captions, invented picture
1 · prompt Btitles as claims, the author's "may" kept, diagrams instead of photos
1 again · second accountsame prompt, different deck: titles back to topic labels
1 + UNIPG theme via Rivedisame words, new look; slide 4 kept the old font
1 + a limestone palettehex codes respected; duplicated text inside the timeline image
…after Rivedi on slide 1 · .pptxone instruction, one slide changed; the .pptx is seven pictures

Three rules

  1. The prompt is the theme file. Codes, not adjectives. Constraints, not wishes.
  2. Rivedi fixes form, the chat fixes content.
  3. Every deck is a draw. Export it, read every slide, keep the good ones.

Declare it: "Slides drafted with Gemini Notebook from the author's article, checked and edited by the author."