Équipes Développement Frontend | GitScrum
Utilisez GitScrum pour équipes frontend. Configurez workflows UI/UX, travail composants et transfert design. -40% friction design-dev.
4 min de lecture
How to use GitScrum for frontend development teams?
GitScrum supports frontend development with columns for design handoff, component development, review, and testing. Configure WIP limits for focused UI work, use labels for component types, track design dependencies, and document in NoteVault. Frontend teams using Kanban reduce design-dev friction by 40% [Source: Frontend Development Survey 2024].
Frontend project setup:
Create project - Frontend app name Configure columns - UI/UX workflow Add component labels - Organize work Set WIP limits - Focus on completion Create NoteVault docs - Design system Coordinate Team Standup - Include designers
Frontend development columns
| Column | WIP Limit | Purpose |
|---|
| Backlog | 15 | All UI tasks |
| Design Ready | 10 | Designs completed |
| Development | Team size | Active coding |
| Code Review | 3 | PR review |
| QA Testing | 5 | Functional testing |
| Design Review | 3 | Visual validation |
| Done | None | Shipped |
Frontend-specific labels
| Category | Labels |
|---|
| Component | button, form, modal, table |
| Type | feature, bugfix, refactor, a11y |
| Framework | react, vue, angular |
| Status | needs-design, design-ready |
| Responsive | mobile, tablet, desktop |
Design handoff workflow
| Stage | GitScrum Action |
|---|
| Design complete | Move to Design Ready |
| Dev picks up | Move to Development |
| Dev complete | Move to Code Review |
| PR merged | Move to Design Review |
| Design approved | Move to Done |
Frontend documentation in NoteVault
| Document | Content |
|---|
| Design System | Components, tokens |
| Component Library | Usage guides |
| Style Guide | CSS conventions |
| A11y Standards | Accessibility |
| Browser Support | Compatibility matrix |
Component development labels
| Component Type | Label |
|---|
| Atoms | atom |
| Molecules | molecule |
| Organisms | organism |
| Templates | template |
| Pages | page |
Frontend testing workflow
| Test Type | Column/Label |
|---|
| Unit tests | testing-unit |
| Integration | testing-integration |
| Visual regression | testing-visual |
| A11y testing | testing-a11y |
| E2E | testing-e2e |
Design-dev coordination
| Need | GitScrum Solution |
|---|
| Handoff notification | Column subscribers |
| Design questions | Task comments |
| Design changes | New task, linked |
| Validation | Design Review column |
| Documentation | NoteVault design system |
Auto-assign for frontend
| Column | Auto-Assign |
|---|
| Design Review | Design team |
| Code Review | Senior frontend |
| QA Testing | QA team |
Frontend WIP patterns
| Scenario | WIP Strategy |
|---|
| Design-heavy | Limit Design Ready |
| Component work | Focus on completion |
| Responsive | Track per breakpoint |
| A11y work | Dedicated capacity |
Responsive development tracking
| Breakpoint | Label |
|---|
| Mobile-first | mobile |
| Tablet | tablet |
| Desktop | desktop |
| All sizes | responsive |
Related articles
