What

Using the LGD content types and hierarchies, we need to agree the structure of the new website and the navigation flow for users. Useful links for this: https://www.drupal.org/docs/user_guide/en/planning-layout.html https://ixis.co.uk/blog/demystifying-the-localgov-drupal-platform

Acceptance Criteria

[ ] Overarching hierarchy of content has been agreed
[ ] Navigation flow for users has been agreed
[ ] Volunteers are clear on content types and where existing content would be migrated to

Readiness

Please check this meets the Definition of Ready before it is added to the backlog

[ ] The story or task has a concise and understandable description
[ ] Acceptance criteria are specific, well-defined to clarify when task is considered complete
[ ] Any dependencies, whether they are on other tasks/teams/external factors, are clearly outlined
[ ] Initial estimation of effort or complexity is provided to help with prioritisation and planning
[ ] The task has been assigned a priority level indicating importance in overall backlog
[ ] Any relevant attachments - documents, mock-ups, additional info - that aid understanding are attached
[ ] Clear how task will be tested to ensure it meets specified criteria
[ ] All relevant stakeholders have provided input or approval for task

Please check this meets the Definition of Done. before it is moved to the 'done' column

[ ] All code related to task is implemented and reviewed
[ ] Unit tests written and passed to ensure functionality works as intended
[ ] Integration Tests conducted to verify implemented code works well with other components
[ ] Necessary documentation is complete, including code comments and user documentation
[ ] Code has undergone a thorough review by peers or designated reviewer
[ ] Task meets all acceptance criteria
[ ] Comprehensive testing including regression testing has been performed to fix any bugs
[ ] Performance aspects e.g., speed & resource usage, considered and meet defined standards
[ ] Code ready for deployment in live environment
[ ] Product manager or relevant stakeholders reviewed and approved completed task

Information Architecture (IA) Proposition Template

Project Overview

Project Name:

[Name of the project/website]

Date:

[Date of proposition]

Prepared By:

[Name(s) of the individual(s) or team preparing the document]

Objective:

[A brief statement about the goal of the new IA, focusing on how it intends to improve user experience, content discoverability, and engagement.]

Current State Analysis

Overview of Existing IA:

[A brief description of the current website architecture, including main navigation points and user feedback if available.]

Challenges and Limitations:

[List of identified challenges and limitations with the current IA, including issues such as navigation difficulties, content discoverability, etc.]

User Needs and Goals

Target Audience:

[Description of the primary and secondary audiences for the website, including demographic information, professional background, and any relevant user personas.]

User Requirements:

[List of user requirements gathered from surveys, feedback, or market research.]

Business Goals:

[List of business or organizational goals that the new IA aims to support.]

Proposed Information Architecture

IA Strategy:

[High-level strategy outlining the approach for restructuring the website’s IA, including principles and priorities.]

Site Structure:

[Detailed description of the proposed site structure, including main categories, subcategories, and any new sections or pages to be introduced.]

Navigation Layout Options:

[Option 1: Description and rationale]
[Option 2: Description and rationale]
[Additional options as necessary]

Content Organization:

[Description of how content will be organized within the new structure, including tagging, categorization, and any hierarchical changes.]

Search Functionality:

[Details on how search functionality will be improved or implemented, including filters, search bars, and indexing strategies.]

Accessibility Considerations:

[Description of how the new IA will adhere to accessibility standards, ensuring that the website is usable for people with disabilities.]

Implementation Plan

Timeline:

[Proposed timeline for the IA redesign project, including key milestones and deadlines.]

Resources Required:

[List of resources required for the project, including personnel, technology, and budget considerations.]

Risks and Mitigation Strategies:

[Identification of potential risks to the project and strategies for mitigating these risks.]

Evaluation and Feedback

Testing Plan:

[Outline of how the new IA will be tested, including user testing methodologies and performance metrics.]

Feedback Mechanisms:

[Description of how ongoing feedback will be collected and incorporated into future iterations of the IA.]

Approval

Sign-Off:

[Space for signatures from key stakeholders, indicating approval of the IA proposition.]

criminaljusticehub / sprint-board

Agree structure of new website and flow for users #45