platform-guideline 2 linked patterns checked
GitHub Docs: Changing the layout of a view
Distinguishes GitHub project table, board, and roadmap layouts; board layout spreads issues, pull requests, and draft issues across customizable columns and supports dragging items between columns.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Kanban board | Choose Kanban board when work items progress through shared workflow states and column movement is the primary interaction. | Each column represents a workflow state or selected column field value, and moving a card updates the same value shown in details, reports, and automation. | GitHub distinguishes table, board, and roadmap layouts and describes board layout as items spread across customizable columns. |
| Saved view | Choose saved view when users need to persist a named combination of layout, columns, grouping, filters, sort, density, and other display preferences for a data surface. | Saving stores a canonical view definition, not a static list of current row IDs. | GitHub Projects documents changing a project view between table, board, and roadmap layouts. |
Comparisons supported by this source
- Saved view vs saved search vs saved filter vs table
GitHub Projects documents changing a view layout among table, board, and roadmap presentations.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: GitHub Docs. Last checked: .