Dashboard development guidance

[rmccreath]

Pull Request Details

Issue Number: Closes #114

Type: Documentation

Description of the Change

Documentation covering the development of dashboards (language agnostic as far as possible), including pre-development considerations across design and project planning, development, and deployment. The guidance covers technical considerations, as well as governance, regulatory, and internal processes to align across teams such as Statistics Governance, Web & Publications, and the Customer Focus teams.

[rmccreath]

Feedback from @juliaromero-phs

Dashboard Development Guidance

1. Pros and cons list - can we add open source code in Shiny dashboards as a pro.
2. User Needs - add some resources for what user stories, user personas and wireframes are? The only "official looking" link I could find came from the UK Government User Research.
3. Accessibility - the guidance will be changing soon as the PHS colour scheme isn't accessible and the accessibility team are working on new guidance with new colours for dashboards.
4. Monitoring - Could we add a link to how to use Google Analytics with Shiny?

[rmccreath]

@juliaromero-phs

1. Added reference to open source benefits in the development section to talk about specific technologies.
2. Added gov.uk Service Manual and Interaction Design Foundation as references for user research and design references.
3. Happy to make changes when they go live.
4. Google Analytics isn't officially approved for teams to use ad-hoc, and requires conversation with web, governance and legal teams resulting in work that is often not possible for teams to implement. I think we should keep specific guidance limited to ensure teams are aware of the implications before implementing.

Thanks again, could you review/approve if think this is now suitable for going live (maintaining it's draft nature).

[juliaromero-phs]

I thought the updates were good. Happy to approve.