> For the complete documentation index, see [llms.txt](https://govex.gitbook.io/community-engagement-playbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://govex.gitbook.io/community-engagement-playbook/readme.md). # README \###Community Engagement Playbook ####by Lena Geraghty and Katherine Klosek with contributions from Kristen Ahearn, Matt Pazoles, Eric Reese, and Rebecca Williams *** \####Want to learn how to engage your community? Now more than ever, cities are striving to put data and information into the hands of residents—empowering them to stay informed and make decisions. This often takes the form of open data portals, performance dashboards, and strategic plans. These tools allow residents not only to track progress on key priorities but also to analyze information and build their own solutions. However, while government data has the potential to serve a wide range of stakeholders, it is often accessed and used by a small, familiar group—a core community of engaged users. To truly unlock the value of public data, cities must look beyond the “usual suspects” and find ways to reach a broader, more diverse audience. How can cities ensure the data they share is accessible, relevant, and empowering for everyone who might benefit from it? To assist cities in elevating community engagement efforts, the [Center for Government Excellence at Johns Hopkins University](http://govex.jhu.edu/), a partner in the [What Works Cities initiative](http://www.whatworkscities.org/), has created this playbook. By learning from the experiences of other cities and following best practices developed by the Center, cities will gain a greater understanding of community engagement. ![](https://raw.githubusercontent.com/govex/govex.github.io/master/images/WWC_ResourceStamp_web.png) --- # 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://govex.gitbook.io/community-engagement-playbook/readme.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.