TeqBench is an application platform with multiple purpopses:

• To learn and utilize various technologies, including .NET, Angular, React, Azure, and GitHub.
• To acquire and apply software development best practices relevant to the technologies being used.
• To create and refine repository structures, achieving a high level of consistency across repositories, and adhering to best practices relevant to the technologies in use.
• To develop reusable elements, such as an overall GitHub organizational structure, actions/workflows, and repository templates, which can be leveraged for consulting work.

An organizational-level wiki is currently (1/15/24) not supported by GitHub. A workaround is to leverage the wiki feature of a repository. In the case of TeqBench, all general supporting documentation for the organization can be found in the teqbench.docs repo, specifially, in the teqbench.docs/wiki. By keeping all documentation as part of the organization on GitHub, the content is centralized on a single platform (i.e. less to manage, immediately available and easily referenced as part of same platform.). One exception, sensitive information (i.e. trade secrets, passwords, etc.) should be managed in separate system all together and with multiple levels of access such as 2FA.

1. Dev Tooling Repositories
   • Shared developer/development productivity tooling; documentation, config/prop files, template repositories.
   • Tag: dev-tooling
2. DevOps Repositories
   • Shared DevOps processes; actions, workflows.
   • Tag: devops
3. Organization Repositories
   • General organization information.
   • Tag: org
4. Sandbox Repositories
   • Sandox/POC/experimetal codebases.
   • Tag: sandbox
5. System Library Repositories
   • General libraries for inclusion in application libraries, service applications and/or client applications.
   • Tag: system-library
6. Application Library Repositories
   • Application specific libraries for inclusion in service applications and/or client applications.
   • Tag: application-library
7. Service Application Repositories
   • Service applications (i.e. REST services, etc.) exposing application specific functionality for consumption by other services and/or client applications.
   • Tag: service-application
8. Client Application Repositories
   • Web, mobile, desktop application repositories.
   • Tag: client-application