> For the complete documentation index, see [llms.txt](https://gilmour.online/lancertech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gilmour.online/lancertech/content-creation/presentation-styles.md).

# Presentations

In case it needs to be said, these rules apply to Microsoft PowerPoint and Google Slides. 

## 1: Consistent styles

Keep a pattern. It's pleasing to your audience and allows them to quickly sort out the information. Use familiar layouts. Stick with the same fonts throughout your presentation.  If you use an image effect when placing a picture, use it on all your images. 

## 2: Keep text short

Don't use complete sentences. Imagine the words as a backup singer. Your audience should not have to stop listening to you in order to read. Most people say never to use more than 7 works in a bullet point. Things can vary a lot depending on the subject matter and the audience.

![Focus should remain on you, the presenter. Slides are just backup](/files/-LlE5bHmEeS-AJfit5YH)

## 3: Size your fonts

The larger your audience, the larger your font size should be.

## 4: Don't look at your slides

Stay with your audience. A glance at the slides is fine. If you stare at the slides, your audience feels lonely. Do it for the people.

## 5: Minimal effects

Classic sign of an over-enthusiastic student is a document covered with borders, text art and image effects. The very best presentations are remembered for their substance so don't let the styling get out of control. 

{% hint style="danger" %}
**Provide feedback**\
If you see an error or have a suggestion, [please submit a response to this short form](https://forms.gle/3CPXVUTGU2iwcAWq5). 
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gilmour.online/lancertech/content-creation/presentation-styles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.