Significant progress was made during this sprint on official City documentation: code, charter, policy, and council business. We also made multiple editor experience improvements and coordinated with several bureaus on their content migration plans.
We do not need to migrate all 350,000+ content objects from the old platform—much of the old site is unused and duplicates that cause search and discovery to work poorly. There are several criteria that can help you pick the right content to migrate.
Schedule time with digital strategists from the content team to create your migration plan and help populate your draft content. The goal it to migrate public content to the new platform by the end of 2019. We can do this!
A recap of the 18th sprint reflects the POWR team's participation in DrupalCon Seattle, and the transition into the new sprint format. The beta's home page has been redesigned, among general updates and bug fixes to the site.
Sprint 17 was a period of consolidation. We used the school spring break weeks to cross train our development team on crucial tasks and standards, responded to usability testing with focused improvements, and advanced multiple feature design concepts for the site.
This was our most productive sprint of the POWR project. The team hunted down bugs, released new page templates for editors, conducted live usability testing in the community, and taught the site's search engine to understand synonyms and protected words.
The look and feel of Portland.gov is taking shape, as a host of design and features improvements went live during Sprint 15 (Jan 30 - Feb 19). Behind the scenes, several bugs were squished and the content model expanded and refined for our editors.
POWR Sprint 14 started Wednesday, January 9th and ended on Tuesday, January 29th. This sprint focused on planning for user testing, a new search server, designs for featuring content, and research for upcoming integrations.
Our latest sprint effort included a series of improvements to aid user accessibility, site design options and review, workflow management tweaks for editors -- and of course copious attention to building the community-focused service directory.