> For the complete documentation index, see [llms.txt](https://civic-switchboard.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://civic-switchboard.gitbook.io/guide/maintaining-momentum.md). # Maintaining Momentum We've been using the metaphor of the ecosystem throughout this guide. While ecosystems are dynamic and can be expected to change, they also require care to stay healthy and sustainable. In this section, we look at ways that libraries can sustain their roles in civic data ecosystems. It can be a real challenge to continuously energize, build, and fund libraries in civic data work. Building partnerships, joint projects and institutionalizing the roles are strategies to share the challenge and maintain momentum. You might find help in: [Finding resources to support civic data work](/guide/maintaining-momentum/finding-resources-for-your-engagement.md); [Library roles;](https://app.gitbook.com/@civic-switchboard/s/guide/library-roles) [Building libraries into civic data partnerships](/guide/engaging-partners/building-libraries-into-civic-data-partnerships.md). --- # 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://civic-switchboard.gitbook.io/guide/maintaining-momentum.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.