> For the complete documentation index, see [llms.txt](https://purelife.gitbook.io/little-design-powerpoint/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://purelife.gitbook.io/little-design-powerpoint/part-3-gao-ji-pian/chapter15.md).

# 第十五章    PPT之神 —— 文字设计

* [15.1  图文混排](/little-design-powerpoint/part-3-gao-ji-pian/chapter15/chapter15-1.md)
* [15.2  具体示例——图文混排](/little-design-powerpoint/part-3-gao-ji-pian/chapter15/chapter15-2.md)
* [15.3  高桥流](/little-design-powerpoint/part-3-gao-ji-pian/chapter15/chapter15-3.md)    
* [15.4  文字云](/little-design-powerpoint/part-3-gao-ji-pian/chapter15/chapter15-4.md)    
* [15.5  玻璃字](/little-design-powerpoint/part-3-gao-ji-pian/chapter15/chapter15-5.md)    
* [15.6  发光字](/little-design-powerpoint/part-3-gao-ji-pian/chapter15/chapter15-6.md)    
* [15.7  本章小结](/little-design-powerpoint/part-3-gao-ji-pian/chapter15/chapter15-7.md)

文字本身在PPT中就具有着极高的地位，在PPT刚诞生之际，PPT的风格往往都是纯文字型，后来经过逐渐的演变和革新，PPT领域不断扩大，需求也在不断的增长，所以原先略显简陋的纯文字型PPT已不在满足大家的胃口，但是别忘了文字依然占据着表达核心这个位置，一个PPT中文字极少，首先对观众就是一种视听的负担，观众根本不明白PPT中这些元素到底是干什么的，观众喜欢自我联想，但你得创造这样的一个环境；对演示者同样是个负担，PPT中文字如此之少，这对演示者的演讲水平要求很高，但是大多数演讲者是不具备这样的演讲水平的，所以PPT中的文字依然会有很多的存在的必要性。


---

# 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:

```
GET https://purelife.gitbook.io/little-design-powerpoint/part-3-gao-ji-pian/chapter15.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.