Content	Provide component-specific guidance on content, such as punctuation rules, standard labels, etc.
Accessibility	Provide component-specific best practices for accessibilty.
Mobile	Provide guidance on how to apply this component in mobile environments.
Best practices	if there are industry standars fo this component, list them in this section. Include “do” and “don’t” examples to illustrate each point.
Related	List related components or patterns. Include links whenever possible.

Process:

Create tickets for a new feature in Jira (
1. Create an Epic with the feature name
2. Break down tasks into separate tickets linked to the epic, each ticket should not be longer than 1 week of work, to make sure it can be implemented and tested in a two-week sprint.
3. Estimate effort, add a description, flow, or any other information that is available.
Tickets are added to the sprint.
A ticket is implemented according to specification and functionality as described in spec. confirmed in QA process.
If a ticket cannot be implemented as described in the specification, this could be due to technical reasons, bandwidth issues, priority changes…
1. Reasons need to be brought up to the product manager (Nick).
2. In a discussion, a decision will be made to either follow the specification or alter it.
3. If the specification is altered it needs to be written down and the Jira tickets need to be updated with new information.
4. This goes back to point 3. ticket to be implemented according to the new specification.

Versions Compared