Task for user story: #1

Create Team Members channel

• Set up fields
• Create section
• Populate with some basic content

Ready Checklist

• The functionality is working locally
• There is appropriate documentation
• There is appropriate testing
• Data security has not been compromised
• No deviation from the team technology stack and software architecture has been introduced

Task for user story: #1

Create all fields and global container for content

• Install and configure Navigation plugin
• Add Asset volume (need to connect with @rija for info)
• Create Single for all global content
• Create Matrix for social links
• Create asset fields for primary & secondary logos
• Create header & footer items

Ready Checklist

• The functionality is working locally
• There is appropriate documentation
• There is appropriate testing
• Data security has not been compromised
• No deviation from the team technology stack and software architecture has been introduced

Task for user story: #1

Create Checklists channel

• Set up fields
• Create section
• Populate with some basic content

Ready Checklist

• The functionality is working locally
• There is appropriate documentation
• There is appropriate testing
• Data security has not been compromised
• No deviation from the team technology stack and software architecture has been introduced

Task for user story: #1

Create Jobs channel

• Set up fields
• Create section
• Populate with some basic content
• Set up global content for Jobs in the Globals single

Ready Checklist

• The functionality is working locally
• There is appropriate documentation
• There is appropriate testing
• Data security has not been compromised
• No deviation from the team technology stack and software architecture has been introduced

Task for user story: #1

Describe the task to do

• Install Tablemaker plugin
• Evaluate and install Neo or Vizy
• Set up media layer types (gallery and video)
• Set up table layer type
• Set up text layer type
• Set up raw HTML layer type
• Set up actual field

Ready Checklist

• The functionality is working locally
• There is appropriate documentation
• There is appropriate testing
• Data security has not been compromised
• No deviation from the team technology stack and software architecture has been introduced

User story

As a curator
I want to be able to change the content under gigadb.org/site on my own
So that gigadb.org/site can be kept up-to-date quickly without using development resource

Acceptance criteria

Given I want to manage content from gigadb.org/site
When I login to CraftCMS as a content editor
Then I can see all the content that's existing at gigadb.org/site

Given I want to manage content from gigadb.org/site
When I login to CraftCMS as a content editor
Then I can manage, update or delete the content that's available at gigadb.org/site

Additional Info

• Content audit
• Define content architecture based on gigadb.org/site/
• Start local setup and create and document content models and forms element in the CMS

Product Backlog Item Ready Checklist

• Business value is clearly articulated
• Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
• Dependencies are identified and no external dependencies would block this item from being completed
• At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
• This item is estimated and small enough to comfortably be completed in one sprint
• Acceptance criteria are clear and testable
• Performance criteria, if any, are defined and testable
• The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

• Item(s) in increment pass all Acceptance Criteria
• Code is refactored to best practices and coding standards
• Documentation is updated as needed
• Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
• No deviation from the team technology stack and software architecture has been introduced
• The product is in a releasable state (i.e. the increment has not broken anything)

Task for user story: #1

Create FAQ channel

• Set up fields
• Create section
• Populate with some basic content

Ready Checklist

• The functionality is working locally
• There is appropriate documentation
• There is appropriate testing
• Data security has not been compromised
• No deviation from the team technology stack and software architecture has been introduced

Task for user story: #1

Create Pages channel

• Set up page fields
• Set up Pages section (Structure-type section)
• Set up page types: regular, subpage, Team, Jobs, FAQ, Guidelines
• Create empty page tree

Ready Checklist

• The functionality is working locally
• There is appropriate documentation
• There is appropriate testing
• Data security has not been compromised
• No deviation from the team technology stack and software architecture has been introduced