> For the complete documentation index, see [llms.txt](https://docs.devlaunchers.org/dl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devlaunchers.org/dl-docs/universal-design-system/universal-design-system/getting-started/design-stack/github.md). # Github GitHub is the central platform we use at **Dev Launchers** to manage code, collaboration, and planning across **Development, Design, and Product** teams. While GitHub is essential for source control and engineering workflows, it also plays a critical role in how we **plan work, track progress, and align cross-functionally** through GitHub Projects. *** ### How We Use GitHub GitHub supports multiple layers of our workflow, from code to coordination. #### Code & Engineering Developers use GitHub to: * Maintain repositories for applications, libraries, and the Universal Design System * Review code through pull requests * Track bugs, improvements, and technical debt via issues * Manage releases and versioning GitHub is the source of truth for all production code. *** #### Planning & Project Management GitHub Projects is used across **Design, Product, and Development** teams to: * Plan and prioritize work * Track feature development and design tasks * Coordinate cross-team initiatives * Visualize progress across multiple repositories Design and Product work is not separate from development — GitHub Projects allows all disciplines to plan and execute work in a shared system. *** ### GitHub Projects at Dev Launchers GitHub Projects provides a flexible, shared planning space where: * Issues represent units of work (features, components, research, tasks) * Project views support different workflows (roadmaps, backlogs, in-progress work) * Designers, product managers, and developers collaborate using the same artifacts This shared visibility reduces handoff friction and keeps everyone aligned on priorities and status. *** ### Who Uses GitHub GitHub is used by: * **Developers** writing and reviewing code * **Designers** tracking component work and design-related tasks * **Product managers** planning features and roadmaps * **Project leads** coordinating work across teams You don’t need to be a developer to participate — GitHub is a collaboration tool first, and a coding platform second. *** ### GitHub and the Universal Design System For the Universal Design System specifically, GitHub is used to: * Track component requests and enhancements * Manage component lifecycle and status * Review design system contributions * Coordinate design, implementation, and documentation work Design system changes should always be visible and traceable through GitHub. *** ### When to Use GitHub Use GitHub when you need to: * Track or propose work * Collaborate on tasks across teams * Review progress or priorities * Contribute code or documentation * Coordinate design system updates For visual design and exploration, start in Figma.\ For implementation validation, use Storybook.\ For planning, execution, and collaboration — use GitHub. --- # 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://docs.devlaunchers.org/dl-docs/universal-design-system/universal-design-system/getting-started/design-stack/github.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.