Skip to content

Documention on how to decide what form a new feature takes #160

Description

@owenatgov

What

Add documentation on how to decide what form a particular solution takes eg: a new component vs a new pattern.

Why

So that the team has an accurate view of what work is required to deliver a new feature, be it a component, a pattern or something else, and maintenance cost for each thing.

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions