> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/resources/brand-guide/editorial-style-guide/channel-specific-guidelines.md). # Channel-Specific Guidelines ## Social Media Social media is where we act as The Sage, sharing knowledge and building community. * LinkedIn: This is our primary professional channel. The tone should be informative and encouraging. Focus on thought leadership, sharing articles, and celebrating community milestones. Use professional formatting with clear paragraph breaks. * Instagram and Blue Sky: These channels allow for a slightly more casual, welcoming tone. Use them for behind-the-scenes community highlights, quick tips, and event announcements. * Hashtag Strategy: Use 3 to 5 relevant hashtags per post. Always use CamelCase for accessibility (e.g., #TechFleetCommunity, not #techfleetcommunity) so screen readers can parse the words correctly. * Community Engagement: When responding to comments, always be welcoming and caring. If a comment is negative, respond professionally, acknowledge the concern, and move the conversation to a private channel if necessary. Never argue publicly. | Do This | Not This | | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | "Thanks for sharing your perspective! We'd love to hear more about your experience. Feel free to DM us." | "You are wrong about how our program works." | | "Check out our latest article on #ServiceLeadership." | "Check out our latest article on #serviceleadership." | | "Congratulations to the team on a successful launch! 🎉" | "The team launched a project." | | "We appreciate your feedback and will look into this issue." | "That's not our fault, contact support." | | "Join us for a live Q\&A session tomorrow at 2 pm EST." | "Q\&A tomorrow." | ## Email Communications Emails are personal and direct. They should always feel like they are coming from a helpful mentor. * Newsletters: Keep the layout clean and minimalist. Use clear H2 headings for different sections so readers can scan the content. Always include a clear, single call-to-action per section. * Transactional Emails: System emails (like password resets or application confirmations) must be extremely clear and intuitive. Do not use jargon. Tell the person exactly what happened and what they need to do next. * Signatures: All official Tech Fleet emails should use the standard signature template, which includes your name, pronouns, role, and a link to the Tech Fleet website. | Do This | Not This | | -------------------------------------------------------------------------------------- | --------------------------------------------------------- | | "Your application has been received. We will review it and email you within 48 hours." | "System update: Application status changed to pending." | | "Hi \[Name], here is your monthly Tech Fleet update." | "Newsletter Vol. 45" | | "Click the button below to reset your password." | "To initiate the password recovery protocol, click here." | | "Include your pronouns in your email signature." | "Leave your pronouns out of your email signature." | | "Use a clear, descriptive subject line like 'Action Required: Update your profile'." | "Use a vague subject line like 'Important Update'." | ## Presentations and Slide Decks Presentations are visual aids, not teleprompters. They must be accessible and purposeful. * Slide Density: Apply our minimalist principle. Never put more than three bullet points or one core idea on a single slide. If you have more to say, put it in the speaker notes. * Data Visualization: When showing charts or graphs, ensure the data is easy to read. Do not rely on color alone to differentiate data points; use patterns or direct labels. * Templates: Always use the official Tech Fleet slide deck template to ensure consistent typography and logo placement. * Downloads: Coming soon | Do This | Not This | | -------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | Use a large, clear chart with direct text labels on the data points. | Use a complex pie chart with a separate color-coded legend that is hard to read. | | Put three short bullet points on a slide. | Put a full paragraph of text on a slide and read it word-for-word. | | Use high-contrast colors for text on slides. | Use light gray text on a white background. | | Include alt text for all images in the presentation file. | Leave the alt text fields blank. | --- # 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://guide.techfleet.org/resources/brand-guide/editorial-style-guide/channel-specific-guidelines.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.