You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the past year, dev.cityofchicago.org has received 6.3k visits all year. It's not a bunch. Mostly, this site today is a set of cross-posted links pushing people to other sites, namely, digital. and data. coc.org.
The recommendation here would be to fold dev.cityofchicago.org content into digital.chicago.gov. Then dev.chicago.gov would be sunset as a public website and retained for use as an API or otherwise in the future.
Alternatively, dev.chicago.gov could remain as an independent subdomain specifically as a microsite tuned to developers, with blog content updated at digital.chicago.gov.
My concern with such a split is that we have no proof our audience segments itself that way or finds that distinction meaningful. IE– developers and nondevelopers are people along a continuum. We should combine and curate content for both audiences in one place, so there's little channel confusion. People understand that to get communications from DoIT/the city about technology, you can go to the digital. site.
export blog content
review, revise links to outside resources
review microsite content and pull appropriate content to new site
get dev.chicago.gov and coc.org pointed correctly
The text was updated successfully, but these errors were encountered:
In the past year, dev.cityofchicago.org has received 6.3k visits all year. It's not a bunch. Mostly, this site today is a set of cross-posted links pushing people to other sites, namely, digital. and data. coc.org.
The recommendation here would be to fold dev.cityofchicago.org content into digital.chicago.gov. Then dev.chicago.gov would be sunset as a public website and retained for use as an API or otherwise in the future.
Alternatively, dev.chicago.gov could remain as an independent subdomain specifically as a microsite tuned to developers, with blog content updated at digital.chicago.gov.
My concern with such a split is that we have no proof our audience segments itself that way or finds that distinction meaningful. IE– developers and nondevelopers are people along a continuum. We should combine and curate content for both audiences in one place, so there's little channel confusion. People understand that to get communications from DoIT/the city about technology, you can go to the digital. site.
The text was updated successfully, but these errors were encountered: