Front end questionnaire completed by all teams

Front end questionnaires completed
Decide on tech stack based on responses
Share tech stack on CDS site, with supporting assets

writeup quick roadmaps

For each repo owned by Design, write a design-projects issue with next steps to improve the repository.

non-design but related

data.chicago.gov
dev.chicago.gov

Maps Public Home page

http://chicago.maps.arcgis.com/home/index.html

We'd like something similar to Boston http://boston.maps.arcgis.com/home/index.html

data.chicago.gov launch

Today, data.chicago.gov does not exist. data.cityofchicago.org, however, is going gangbusters, with 716k sessions last year, including 190,000 visits to the home page.

repointing home page widgets to take blog posts from digital.chicago.gov as a new source for both kinds of posts
take as many CDS styles and assets as possible in the socrata style
eventually make data.chicago.gov the primary address for this site, with data.cityofchicago.org working for many years, too. This will require a new SSL cert owner, I believe.

Make a real colophon for the city of chicago website:

https://www.cityofchicago.org/city/en/general/credits.html

Service design for service discovery

A collaboration project with a local university to address how residents find new services. Touches on issues #17 #14 #10 #13 & #12, so it should be worked on prior to those issues.

Kick off 1/16

alpha.chicago.gov

colorize tiles
fix 311 in footer
2/3 1/3 pic & quote.
build out secondary pages: maps, payments, services, my neighborhood, etc.
start linking to new digital and other microsites using CDS system
add an employees link
add a 311 top requests section to home page.

Create a central Digital Service Delivery Team

Create a central Digital Service Delivery Team within the Department of Information Technology to lead technology innovations for increasing access to city services.

examine other digital service delivery team goals, frameworks, and procurement, delivery, staffing, and sustainability models.
make recommendations for first 100 days, 1st year, 1st administration
examine structural barriers & impediments that have prevented reform to date
examine successful projects from the current model. what worked?

design-library

rename this patterns.chicagodesignsystem.org
write a readme/changelog of necessary fixes and updates to true to actual code and figma screenshots
update this content to reflect the changes and updates made in Figma, Adobe XD, and code.

311 Community Portal service request detail page status views

For users of the community portal to understand the status of a service request and the associated work activity, the service request detail page will display a visual representation of this status with supporting text and actions for the user to take on that request.

As a City of Chicago employee, I would like common Office and other document templates so I may look and feel good about my work.

DoIT has a number of templates for power point, word, and other systems. Please make 'em look great in the new brand.

Better metrics for the design team and our web and mobile products

See IT Metrics spreadsheet for examples of other team members' metrics.

For new users, describe the purpose of this design system so they can figure out how to use it and how to contribute.

People need to see this design system and understand how to make it go!

design.chicago.gov

see issue #29 for more details, same issue. If this site exists, make it so. Otherwise, make it a subpage within digital.

CDS Communication plan for the PMO team: How this works, how to introduce it to projects.

Start a Medium blog publication for DoIT

This blog can start off as the blog for the 311 alpha site, and then transition to a general Chicago civic design/DoIT blog.

Clean up login access

What do we need to do to ensure a positive cutover from the existing wordpress CMS to medium?

Immediate changes to content

Kill videos below the livestream
Kill digital hub section if possible (stretch goal, not necessarily needed)
We need to host the list of social media accounts on coc.org directly.

Mayor's Office & Web team Considerations

The list of SM accounts needs a page, url, and links from the footer.
Content managers should review the list of accounts to make sure their individual pages are updated.
Grace will build a new page in the press room section of the Mayor's Office to host the livestream, the italic text below the livestream, and the twitter feed.
Grace will then update her bit.ly link to point to the new coc.org/livestream page.

DoIT considerations

http://dev.cityofchicago.org/blog/ is a Jekyll site hosted on Github. Content is tagged, but the CMS does not display it due to technical limitations.
http://data.cityofchicago.org/ shows a list of titles and links at the bottom of the page that pulls data through an ETL job
The dev site autopublishes to the CDO's twitter account, possibly through an ifttt account nobody knows who owns.
Data & dev posts are tagged with datasets, bug, and other things, so we'd either need to change those tags or figure out a way for them to actually be surfaced.
Use this blog to power the 311 alpha site's blog feature as well

to do's

research how medium handles content syndication

Update the Design home page on the DOit website.

https://www.cityofchicago.org/city/en/depts/doit/provdrs/Design.html

archived projects

general archiving process:

rename repo (?) zarchive - reponame
update README.md file
address and close all remaining issues
test if hosting for an archived site works
archive movingfoward.chicago.gov
archive resilient.chicago.gov

311 alpha site

We need a 311 micro-section of the cityofchicago.org website.

This site will:

inform people about upcoming changes to 311
increase user feedback about 311
answer common questions about 311

Pre-Launch Checklist

Interface Inventory

We need to perform an interface inventory across key properties:

dev.chicago.gov launch

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

events. it's a thing

pay.cityofchicago.org <> cityofchicago.org flow

The menu on cityofchicago.org links to pages within coc.org, which is great expected behavior when viewing content on the coc website.

However, now payments are hosted at pay.cityofchicago.org. People using the menu on the coc.org website use the menu, then are presented with a page which links them to another page.

We should resolve this in a way that respects user intent but does not shock people that they are directed to a completely different page with no way back to the prior page.

check the kanban board

design-system

rename chicagodesignsystem.org
remove old site
update to use chicago design system styles
copy content from design-cds-jekyll into this site
relaunch and repoint URLs
add a page: websites using the CDS
include colophon & accessibility statement pages as a base reference, remove alpha references
potentially move items like the alpha.chicago.gov kitchen sink page into this project, again as a pure implementation reference. design-library should always contain actual patterns

Write a description of the design system for the communication team.

Partners for Places: Sustainability Work

design-methods

rename this methods.chicagodesignsystem.org
rewrite readme and wrapper content
update to use chicago design system styles

Propose city events feed/platform

Access Chicago Booth

get booth

Make a real accessibility statement for the city of chicago website.

https://www.cityofchicago.org/city/en/general/standards.html

Microsite Migration Questionnaire

To help the team accept microsites more easily, create a common questionnaire for them to fill out as part of the project creation process.

For City of Chicago DoIT team members, tech teams in other departments, and vendors: explain the 5W's & How so I can use this easily.

leadership at DoIT: why are we doing this and what does it mean?
leadership at other departments: same as above, but lighter context.
vendors & teams: what does this mean, what are the next steps?

Comprehensible Chicago

As part of a digital communications strategy for data transparency, the Mayor's Office has asked DoIT to "review the city's website and digital communications for usability, language, and disability access, and other under-utilized opportunities."
We have performed these reviews in an ad hoc fashion before. I can summarize the results here: generally terrible, mostly fixable but through changing how we work as much as how we change our technology.

This project, then would be an effort to:

catalog these findings so others are aware of our current state (1 week).
determine which languages we will seek to support, and how (1 week).
determine gaps in our current processes for content production that impact accessibility, readability/reading level.
recommend changes or future work to address how content is produced and published across our primary city properties.
produce a presentation, pdf and web site report of the process and findings.

For the purposes of this project, our scope is limited to chicago.gov, 311.chicago.gov, pay.chicago.gov, and the CHI311 mobile application.

Catalog our current state

Using http://juicystudio.com/services/readability.php which uses three metrics to evaluate readability, we see chicago.gov requires more than a high school education to read.

Install https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk?hl=en & https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh?hl=en-US

See more about their usage here: https://developers.google.com/web/tools/lighthouse/#devtools

Review chicago.gov's home page, a department page, a program page, and a promotional page.
For 311.chicago.gov, the home page, a knowledge article, and a service request submission.
For pay.chicago.gov, the home page, help content, and the process of paying a parking ticket.
For the CHI311 mobile application, the same items as 311.chicago.gov.

Language support & best practices

We determined the City of Chicago will support English, Spanish, Mandarin Chinese, Polish, Arabic, & Tagalog languages as a response to the language access ordinance. Please help document and define our standard for language translation services. We have performed some due diligence with language translation service providers. We need to examine how tools like Google or Bing may be supplemented with additional translation work performed for high use cases.

How should this be considered and implemented consistently? What is an ideal content workflow that supports our multiple content authors?

Gap analysis of today's workflow

Where are we missing readability, accessibility and internationalization support in our current workflow?

What changes can we make to our workflow to improve comprehension?

What are a list of suggested interventions, from small to large, that could help us?

Artifacts

From this work, we should expect a report, a web page presentation, and a written report.

CDS Comms plan for different department teams

Additional maintenance items

As a follow on from re-configuring the repositories:

review all README.md files
review all LICENSE.md files & settings
review all Creative Commons licensing settings
writeup HOWTO for chicagodesignsystem.org
writeup HOWTO for the microsite process
add assets page to the chicagodesignsystem.org pieces.
figure out cds bug on this: /assets/img/social-icons/svg/twitter16.svg
redo home page of cds to support assets

pulaski

rename this site for what it is, an alpha alpha chicago.gov
pull content styles from current coc.org over to alpha
write up readme, review open issues
archive site

Convert CDS.org to USDS one-pager

Choose/modify USDS Jekyll/Federalist template
Write intro on CDS House style over 18F/USDS standards
Consolidate content to single page
Fork 18f Method cards
Update Method cards fork
Fork USDS Design patterns library
Update Design patterns library
Fork 18f Accessibility guide

Research 311 mobile best practices

Review peer cities (including Denver, Boston, etc.)
Find and catalog patterns/best practices/issues to avoid
Put together sharable report (Google Slides? or other)
Review internally, then share report

Design operations

Run this brainstorming exercise with senior leadership by the end of Q1 to help integrate this new competence.

http://gamestorming.com/mapping-design-operations/

digital.chicago.gov launch

digital.cityofchicago.org was meant to be a front doorstep to digital services for Chicagoans of all kinds.

Last year it served 33k visitors, 25k of whom visited the Mayor's livestream page. 5k came for three data blog posts about taxis, lobbying and city salaries. 5k visited the home page.

Given that traffic, and the fact that the Wordpress version of digital.cityofchicago.org is eventually going away, I thought it best to roll all our digital and DoIT-technology related information into one marketing site.

That would mean the old digital is removed, eventually, and that work will be treated separately.

For this item, there are a few mega stories:

design-projects

for now, keep as is. revisit in q4 2019.

Site Profile Questionnaire notes

microsite intake

After a project request form has been submitted with a request to migrate a site, we should follow up with a questionnaire to better qualify the effort required.

We will prototype this form in surveymonkey, and once we get it right we can transfer it to Sharepoint.

Categories of information

ownership
** city contact person
** technical contact person
goals
** how does this serve the city now?
** what were the original audiences and goals?
usage
** audience
** metrics
** other forms of analytics or analytics systems in use?
content
** is there a content management system in use?
** who has access to it?
** Are there forms or data people are submitting (signing up for a mailing list, etc)?
technical
** is there a database behind it?
** what kind of database?
** who manages it?
** Is there CRUD in the database?
technical

what do you want us to do to reproduce this site in our environment?

This is kind of a top level site question that helps us overall. Answers to this and following questions can be open ended.

paid tools
open source tools
any licensed products being used to host this?

Update 311 roadmap with April May & June changes

311 roadmap has had community-driven updates, put them in the working roadmap.
Align completed work from the working roadmap and the public roadmap.

New community stories

As a resident I want the City and my Alderman to provide me data on the needs of our community and the City's performance, so I can judge for myself if the city is providing equitable services.
As a resident, I want to add pictures to the subcategories, so I can easily understand the category.
As a resident, I want to check my status by open or close, so I can view only the active service request.
As a resident, I want to be able to edit my request or be told I cannot edit and directed to create a new request.
As a resident, I want call to action buttons in all knowledge articles, so I can create a service request without navigating out of the article.
As a resident, I want transparency on the status of my request and the ability to customize how I receive updates (phone, text, email, notification).
As a resident, I want confirm a service request has been fulfilled, so I can verify, or dispute & get it complete to my satisfaction.

DFSS dashboard wireframes

Round two of DFSS public goal dashboard wireframes

As a visitor of a City of Chicago website, I would like a consistent footer so I can get help, leave feedback, or find easy access to common problems.

The footer could use a bit more content, including links to additional subdomains and media channels for city information.

design-cds-jekyll

take all content from this site and copy it into design-system repo
remove all actual content from this site
narrowly refactor the codebase to reflect the status of this project as a standalone theme

create new repo
follow howto steps recorded during alpha.chicago.gov setup
convert to USWDS2.0, and document that effort as well
use this as the basis for new sites for other upcoming projects (digital., dev., etc.)
update HOWTO

chicago / design-projects Goto Github PK

design-projects's Introduction

design-projects

design-projects's People

Contributors

Stargazers

Watchers

design-projects's Issues