Ed-Fi Slack channels. Capitalized as shown. Plural "channels." Keep the "Ed-Fi" qualifier even on second use whenever we're talking about Alliance-moderated channels.
Ed-Fi Tracker. Notably not Ed-Fi Issue Tracker or Ed-Fi Jira. It is okay to use "Ed-Fi Tracker, a Jira-based system" in material for a tech-adjacent audience who may not be familiar with the Ed-Fi instance.
Ed-Fi Exchange. Capitalized as shown.
Ed-Fi Support. The one stop for all Ed-Fi support, tied to the Ed-Fi Community Hub currently (as of 07.19.2023) in the works.
Ed-Fi Technology Suite and its Contents
Ed-Fi Data Standard. Capitalized as shown. Notably not Ed-Fi Core or Ed-Fi Core Data Standard.
Ed-Fi ODS / API Platform. Capitalized as shown. Ed-Fi Platform on second use. Consists of the ODS database plus the APIs published by the Alliance, including the surface of the ODS / API. In other words, the product includes the ODS / API + other Ed-Fi API specifications. When describing the individual components, it's okay to use ODS or API without a qualifier if the context is clear – or use formulations such as "...the Ed-Fi ODS..." or "...the Ed-Fi API..." if context or differentiation is useful.
Ed-Fi Technology Suite. As shown. "Technology Suite" on second use. Not Ed-Fi Technical Suite, which has been deprecated.
Ed-Fi Tools collection. Capitalized as shown (n.b. lower-case "collection"). Ed-Fi Tools on second use, and optional for first use when the context is clear. Ed-Fi Tools are not a suite or a formal set of products, they're an evolving set of supporting technologies and resources. So, formulations such as collection of Ed-Fi Tools is appropriate if that sounds more natural.
Ed-Fi Tools Collection Contents
Admin App. As shown.
Analytics Middle Tier. As shown. AMT on second use.
Data Import Utility. As shown. Typically Data Import on second use.
MetaEd IDE. As shown.
MappingEDU. As shown. Notably not Mapping EDU or MappingEdu.