Thank you for helping us test the site. If you need the current site, please visit PortlandOregon.gov.

News

News article
Posted on

Timeline update for bureau stakeholders. Ready for content to launch exclusively on Portland.gov. Plans for when the PortlandOregon.gov homepage will transition to Portland.gov.

News article
Posted on

Powerful search and display tools are being added in the Portland.gov beta, either live already or coming soon.

News article
Posted on

A lot going on behind the scenes, but also some visible changes and improvements in the editor experience while keeping the focus on bureau content migration.

News article
Posted on

More features to learn about from our latest development sprint that also include some usability feedback, and updates to the site's look and feel.

News article
Posted on

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.

News article
Posted on

A review of features and editor improvements to Portland.gov, for the sprint ending August 6, 2019.

Posted on

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.

Posted on

Two editor enhancements were developed during Sprint 20: enabling featured content on group pages; and providing email notification when an editor has placed content in review.

Posted on

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!

Posted on

Search term autocomplete, date picker, better media descriptions, City charter and code types, and migration tools have all been released in the last three weeks.

Posted on

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.

Posted on

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.

Posted on

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.

Posted on

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.

Posted on

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.

Posted on

Our most recent, holidays-extended sprint yielded a quiet but major milestone: opening up beta.portland.gov for "soft review," where access to the site is no longer limited to employees.

Posted on

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.

Posted on

The POWR team put accelerated focus on content origination during Sprint 11, while continuing to improve the experience for both editors and the community.

Posted on

The POWR team has been focused on turning design and content into an autumn Beta release. Workshops with partner bureaus, editor improvements, and bug fixes were the goals for Sprint 10.