> For the complete documentation index, see [llms.txt](https://sfdigitalservices.gitbook.io/style-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sfdigitalservices.gitbook.io/style-guide/content-principles.md).
# Content principles
### 1. Start with people
Talk to your readers directly. Meet them where they are and tell them what they need to do. Use words they use.
### **2. Make it easy**
Make it simple for San Franciscans to interact with us. Hide the complexity of our departments and processes. Only give users the information they need at that time.
### 3. Write for everyone
Write simply. Use plain English.
Check your writing is at or below a 5th grade reading level in the [Hemingway Editor](http://www.hemingwayapp.com/).
Translate simple writing into languages residents need. Have a plan to update translations as you update the English version.
### 4. Engage communities
To make the most inclusive and accessible website, work with San Franciscans who might find City services hard to use.
### 5. Earn trust
Keep the website current, accurate and the single source of truth.
### 6. Hold ourselves to account
Revisit every page every year. Look at popular pages and services more frequently.
Use data to continually improve the site.
### 7. Digital first
Prioritize digital, so San Franciscans can help themselves when and where it's best for them.
Understand that people sometimes need help. Understand that some things need to be done in person. Be clear and straightforward on how to get that help.
---
# 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://sfdigitalservices.gitbook.io/style-guide/content-principles.md?ask=&goal=
```
`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.