> For the complete documentation index, see [llms.txt](https://story.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://story.groupthought.com/sections/story-sections/team.md). # Team Story's Team section helps you quickly build card-style profiles of your staff or team members. Each team block has a series of elements to build custom profiles easily and quickly:

### Profiles Add team blocks and configure the team member profile with any of the following: * Profile image * Name in heading format * Job title or sub-heading * Bio text * Social links with auto-generated icons and links

### Social networks A wide range of social links are included. These will automatically generate an icon for the social network. You can add up to three additional custom social networks with icons with links:

### Section settings Add an optional heading and text introduction. Customize additional section features like: * Team cards per row. There are scroll arrows when the slider is enabled. * Section background color * Enable slider or display by grid * Section width and padding

--- # 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://story.groupthought.com/sections/story-sections/team.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.