When asked how to make it easier for developers to find useful information, I generally recommend customizing the organization's profile with relevant resources and directions to help people find things.
### GitHub Conventions and Requirements
[`Repository Naming Conventions`](https://example.com/gh-repository-naming-conventions) • [`Information Classification`](https://example.com/gh-dataclassification) • [`Repository Tagging`](https://example.com/gh-repository-tagging)
### Development @ Your Enterprise
[`GitHub`](https://example.com/gh-githubdocs) ([`Actions`](https://example.com/gh-github-actons), [`Dependabot`](https://example.com/gh-dependabot), [`CodeSpaces`](https://example.com/gh-dependabot)) • [`Azure DevOps`](https://example.com/gh-azuredevops) • [`Artifactory`](https://example.com/gh-artifactory) • [`SonarQube`](https://example.com/gh-sonarqube) • [`DevOps Docs`](https://example.com/gh-docs)
[`Tools`](https://example.com/gh-tools) • [`Cloud`](https://example.com/gh-cloud) • [`Security`](https://example.com/gh-security)
### Learning & Trainings
[`GitHub Learning Path`](https://example.com/gh-learningpath) • [`Controlled Data Training`](https://example.com/gh-controlleddata) • [`Trainings Overview`](https://example.com/gh-trainingsoverview)
### Support
Development tools provided by the [`DevOps Platform`](https://example.com/gh-devopsplatform) ([`Roadmap`](https://example.com/gh-platformproject))
Reach out via [`help@example.com`](mailto:help@example.com) (creates ServiceNow ticket) or in the [`CloudTech UserGroup`](https://example.com/gh-ctug) on Teams- Native GitHub functionality
- InnerSource Commons Portal
