> For the complete documentation index, see [llms.txt](https://docs.joingather.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.joingather.org/gather-app-walkthrough/resource-management.md). # Resource management To make sure your members get the most out of your app from Day 1, we recommend adding as many useful resources as possible. We have an ever-growing Gather Resource Library that you can add from, or you can add private opportunities. ### Adding new resources To add a new resource from the app, select the Plus icon in the bottom-right corner, then click resource. A form will pop up with the following fields. | Detail | Description | | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | The title of your resource. | | Cover art | The cover art is what shows at the top of an resource page or on the event card when it appears in list form, such as in your Mailbox or on the Explore Tab. | | Snippet | Short description summarizing the resource. | | Description | This is long text to describe your resource. | | URL | A link to the site where the resource is/has information listed. | | Location | The location of your event, if it is physical. | | Contact method | List an email or phone number to contact regarding the resource. | | Tags | Tags let your user know what your resource is all about. Examples: Physical fitness, education, tax help, etc. | | Type | Sometimes, a resource is an organization, and an organization can itself have many resources. To make sure you're able to link resources and events to an organization, make sure to designate it as such. | | Important callout | Any essential info you'd like your attendees to know. | | How to access | List any information about accessing the service, such as submitting an application or rounding up documents. | | Limited-time access | If your resource is only available for a limited time, select the time frame. This is common for scholarships, job opportunities, etc. | | Eligibility requirements | Are there specific requirements to access, such as gender or income level? Let your attendees know in this section. | Once you have created the resource, the resource page will pop up. From here, you can edit the resource, make it private to your community, or delete it (if and only if you are the creator). Reminder: as a default, resources are made public so that they can be added to the library. Don't forget to make it private if it is not open access! ### Adding existing resources To show existing resources from the Gather Library in your community. Navigate again to the Plus icon and select Resource Library. The interface will look just like the Explore tab. From here, you can quickly see which resources are already visible in your app and which can be added. To quick-add a resource, simply tap the eye icon in the bottom right corner. To un-add, tap it again. Easy as pie! ![Green indicates the resource is currently being shown in your app.](https://3024605654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu9PavPKMcvtJuywiEX1R%2Fuploads%2FRRGITS7JAHcIonlqYlth%2FIMG_1936.PNG?alt=media) That's it on adding resources from your app. Enjoy exploring! --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.joingather.org/gather-app-walkthrough/resource-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.