> For the complete documentation index, see [llms.txt](https://sftpmag.gitbook.io/sftp-publishing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sftpmag.gitbook.io/sftp-publishing/magazine-roles.md). # Magazine Roles Each issue of SftP magazine is produced by a dedicated team of volunteers who form an Editorial Collective. There are also volunteers from within SftP’s [publications committee](/sftp-publishing/archives-publishing/what-is-pubcom.md) and beyond who work on multiple issues of the magazine and can provide support and answer questions about our overall process. Everyone is able to submit a proposal to contribute writing or art to the magazine, or take on multiple roles if they have capacity. **Standing Publications Committee Members:** * Managing Editor - oversees magazine production, works with Publisher and group leads * Alex Adams: * Publisher - oversees circulation, funding, and promotion * Vassiki Chauhan: * Art Editors - solicit and create artwork for print magazine * Lead: Myles Marshall and LM White: ; * Copy Editing/Proofreading Lead - manages volunteers and checks final manuscripts and magazine layouts for adherence to style guide, grammar, spelling, and typos. * Erik Hetzner: * Technical Editing Lead - recruits and trains fact-checking volunteers * Manu Raghavan: **Editorial Groups (work on multiple issues; have a dedicated lead or liaison for recruiting and training; rotating membership):** * Translation Working Group - among other things, translates articles for SftP * Contact Michael Gasser: **Groups, Departments, and Rotating Members:** * Mapping Collective Liaison (for our GIS/Mapping feature) * Chapter and Working Group Liaison (for our Reports department) * Translation Working Group Liaison (for any articles we choose to translate) * Art collective (for art accompanying each article and cover art) **Social Media:** * We have an existing social media team within SftP that posts to our Twitter and Facebook feeds and can provide guidance and best practices. --- # 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://sftpmag.gitbook.io/sftp-publishing/magazine-roles.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.