> For the complete documentation index, see [llms.txt](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/communication-strategies-how-do-we-make-sense-of-the-world/the-seasonal-festival.md). # The Seasonal Festival {% hint style="info" %} **Ideal for**\ Great for large and complex communities. {% endhint %} ## Structure A seasonal gathering (digitally or physically) that brings the whole community together for talks, workshops, dancing, music, play, sharing vital updates, governance updates, etc. ### Examples include: * a weekly/monthly recap, * etc. ### Suggested When: Whenever a community can afford to put on a seasonal event to bring everyone together, they're encouraged to. ### Known Pitfalls: Expensive and potential purpose creep (where the community starts directing too much resources towards the gathering). Teams are encouraged to set clear budgets and involve the community in the festival raising experience as much as possible. #### Authored by Rieki Cordon, Hypha DHO --- # 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://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/communication-strategies-how-do-we-make-sense-of-the-world/the-seasonal-festival.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.