cagov / alpha Goto Github PK

The web config only allows specific file types currently. As we solution forward, we are only going to host static content, so there is no reason to limit file types. It could create issues in the future if file types are not allowed.

Allow all file types on the server.

Could we check in with other teams or do our own research and come up with a deployment process we should follow that will make sure our static assets are compressed (gzipped or brotli'd) when delivered to end users.

We can put them in blog storage or pre compress as part of the build process and deliver directly from our server, I don't have an opinion on the best way to accomplish this, we can use whatever process is easiest in our azure environment

follow tech checklist identified in #72

• Draft content (@hilaryhb @humancenteredhuman )
• Determine design (@lukefretwell , @artuoma )

Adding from prior issue:

**As a visitor/user of Alpha.CA.gov, I would like to have the option to submit feedback so I can share my ideas or issues I'm having while using Alpha.CA.gov.

• create /feedback page
• add to footer / page template

@carterm @aaronhans
Do either of you know what has caused the 502 Bad Gateway?
https://staging.alpha.technology.ca.gov

Did either of you make changes last week? Just trying to get it working again and prepare for the DNS cutover for alpha.ca.gov

CI-CD diagram needs another update to reflect desired pipeline changes.

• Remove browserstack testing after deployment to staging (this should be testing during dev)

Example from Portland's beta site: https://beta.portland.gov/

👉 Prior issue #48

Moved to Ops

PR from any branch should NOT deploy to staging. It should be for specific branches such as "master" or "staging" only.

Integrate dynamic file naming for static assets like js and css which update often

this can be done along with other developer experience upgrades like adding watch process to rebuild automatically

Describe the bug
We should implement Strict Transport Security (HSTS) in order to prevent man-in-the-middle attacks where people specifying the HTTP address can be redirected to a malicious site.

More information here...
https://hstspreload.org/

To Reproduce

1. Open Chrome Developer Tools -> Network
2. In Chrome Browse to "http://alpha.ca.gov" (not HTTPS)
   First value for "alpha.ca.gov" shows the following

Request URL: http://alpha.ca.gov/
Request Method: GET
Status Code: 301 Moved Permanently (from disk cache)
Location: https://alpha.ca.gov/

Expected behavior
The browser should automatically go the the HTTPS site without triggering a redirect.

related to...
#13

https://github.com/uswds/public-sans

As a user, I'd like to see a status bar of key digital performance indicators, so I can see how CA.gov is meeting this criteria.

Initial indicators:

• HTTPS
• Accessibility
• Page load

Would also be great to have a /performance page that explains what each of these are.

cc @artuoma @aaronhans @abquirarte

We will be initially using SurveyMonkey to collect feedback on each form. (It's the most efficient method we have right now). Plus Hilary is already using this.

Prior issue/draft content: #48

As a visitor/user of Alpha.CA.gov, I would like to have the option to submit feedback so I can share my ideas or issues I'm having while using Alpha.CA.gov.

• create /feedback page
• add form to page
• add text to page template footer (cc @humancenteredhuman for text)
• form runs over the bottom 'Alpha' banner.
• The double scroll on the form embed and page is not great UX, especially on mobile.
• Make form text and button background #000000.

We need accessibility tool standards being used by everyone on the team, our automated tools and documented in our handbook

Would like to come up with recommended toolset of accessibility tools to use in:

• CI pipeline
• code linter
• manual in browser review

Started gathering tool info and capabilities here: https://docs.google.com/spreadsheets/d/1QSDU4J48Rjopw5a5y46uONLx6LkxUTwCCRwazaaVhfI/edit#gid=0

Create at least 3 components based on widgets we are already using in our current content:

• tiny ca.gov top bar
• jumbotron
• accordions
• autocomplete
• footer

Review how these look when integrated in storybook vs other ways of presenting a "design system"

remove gzip junk, handled on server
document prerequisites and build steps in repository readme
streamline build steps to remove temp generated files
move all files to be deployed into new public directory

• finalize content/call-to-action (Document)
  Survey link: https://www.surveymonkey.com/r/AlphaCAgov
• update Public Sans files (#17)
• finalize/set-up hosting
• clean up code/design (#11)
• add analytics (#5)
• publish files
• submit DNS request
• map DNS
• Make sure the meta description is what we want it to say (see below what it currently is).
• Remove the commented code that's not being used.
• Alphabar should be #000000. OK for the official bar to be like it is in the comp (or just make it #000000).
• The state in between the 'Hello' and 'California' isn't working on mobile, but we should really keep it above and not insert images in between structured mark-up.
• Remove the space between paragraphs and 'Team Alpha.CA.gov.' If we feel like there needs to be more paragraph space, add it to the CSS.
• Apply user feedback in next iteration, experimental language, (along with minimum wage page live).

Currently, https://alpha.ca.gov/index.html and https://alpha.ca.gov/ are the same page. Recommend we 301 redirect index.html to the root and add a canonical header to the page.

<link rel="canonical" href="https://alpha.ca.gov" />

We need to update our "homepage" to add the prototypes we have "shipped" and add to the "live" alpha.ca.gov site.

This will require:

• Update content type in design system homepage
• Document/create process to go from "shipped" to "live" and in production.
• User stories ready for posting: minimum wage, state holidays, birth certificate (someone please add the correct links)
• Clean up prototypes
• Finalize #48 (this is an experiment and feedback)
• @jpetrucione to think through release Social media messaging

• setup account
• add permissions
• add to website Done, #5 (comment)
• Draft summary of what we do have access to DRI- @carterm
• Close out ask with departments we reached out to

Let's build a static page of basic design components for the page so we can reference while prototyping.

Example: https://style.codeforamerica.org/

cc @artuoma @aaronhans @ChadABratton @carterm should we do this as a single repo?

@lukefretwell Our CWDS repo is basically the beginning of that just categorized using the bootstrap components.

• do we have latest version of open sans
• is the font integrated in the most performant manner possible

• Document

• Add to handbook

We should add a robots.txt file to the UX github site. Otherwise, this site will be crawled and steal traffic from the real site when it is released.

Recommended contents...
User-agent: *
Disallow: /

the file should appear here...
https://cagov.github.io/robots.txt

UX project...
https://github.com/cagov/UX

Working doc

test

via Twitter:

What if @CAdotGov was a platform that made government make sense? What if it consumed APIs from cities, counties and school districts about local services and polices using open standards to provide real-time context for any issue? https://t.co/cdgvH9soLi?amp=1

https://twitter.com/Roughani/status/1207869324809011200

DRI: @carterm
cc: @KimberlyglennTSM
Note: Looks like there is some configuration work to be done. I'd like to start diving into this data tomorrow.

Enable monitoring and alerting for alpha.ca.gov

• create monitoring rules to check for http/https errors
• if more than 5 errors over 5 minutes, trigger alert to [email protected]

Is your feature request related to a problem? Please describe.
We discussed ways to serve up blog/news content types.

Describe the solution you'd like
We can do static or using a lightweight content management system (a la Gatsby).

Describe alternatives you've considered
@aaronhans?

Alpha.ca.gov is currently running on an app service with limited resources and no CDN.
Task: Migrate to new app service, app gateway, and implement CDN

• Determine requirements for DNS request
• Submit DNS Request to point alpha.ca.gov to new CDN endpoint
• Create new CDN endpoint and custom domain to point to App Gateway
• Create new App gateway rules, listeners, http settings, and health probes to properly monitor and direct incoming traffic to alpha.ca.gov from the CDN
• Upload cert/pfx to Azure Portal - Vault for alpha.ca.gov
• Staging / Prod Swap process tested

The flag icon that appears on the upper left side in the "Official California State Government Website" header is 112,485 bytes. In contrast, the CA icon is only 2,845 bytes.

Also, it appears very small on mobile/narrow views.

https://alpha.ca.gov/img/ca-flag.png

• Reduce file size.
• Fix width on narrow devices

Use this tool https://github.com/treosh/lighthouse-ci-action as part of our build/deploy process

Right now there is an azure pipeline process which is deploying every branch to staging. That could be modified to only deploy the staging branch to staging, then this github action can run and audit the site there. Going to be some discovery and learning during this process and we should distribute the knowledge gained throughout the team.

High level goal:
Use an automated tool which generates reports against a running version of the site using branch which we want to deploy and gives us:

• Performance measurements
• Accessibility measurements

Regressions in these scores should block promotion to production
Scores should be able to be tracked over time, ideally reports from each build would be viewable with the cute score dial graphics

• quick answer

• step by step

• smart answer (calculator)

• transaction start page

• guide

• location search

• news

Descriptions and Content Type Examples from PD: https://drive.google.com/a/alpha.ca.gov/file/d/1CmyDVKfkJ9FhAgx-lUFZ6HUqltrAFeQD/view?usp=sharing

Gov.UK: https://design-system.service.gov.uk/components/

• Create draft CI-CD workflow

follow tech checklist from #72

Creating a working Function As A Service prototype will make sure we have data options should our alpha want access to anything other than static data.

Recommend we make an offering that returns state holidays as a JSON result, which could feed other services that return HTML or ICAL.

Assuming the official domain for the alpha site is alpha.ca.gov (recommended) then www.alpha.ca.gov should eventually (but quickly) become a 301 (permanent) redirect to alpha.ca.gov.

https://www.alpha.ca.gov should not be marketed but will then work just in case someone mistakenly believes the www is necessary.

How the redirect is configured/created depends on the domain registry and/or hosting environment used.

Additionally, you might plan for a sequential release plan that allows you to maintain alpha.ca.gov as the bleeding edge experimental version when www.ca.gov is replaced by the new site.

Cheers!

• Enable SSI on alpha.ca.gov

via Twitter:

I bet @dsearls and @windley could gather some great ideas for @CAdotGov around identity and human-centered government services! @abquirarte @CohanShapiro @MikeWilkening_ @TamaraIDEJA

https://twitter.com/typesend/status/1208009750669074434

• Make sure 'Public Sans' is the default font for all styles
• Any font designated at '300' should be '400' (@artuoma I think this is what we should do - on the Cal grant prototype, the .lead class looks thin)

• remove unused css (run uncss or similar tool to strip out unused rules from bootstrap)
• combine remaining css (combine current multiple css files into a single one with build tool)
• if uncss step is effective we can look into how to make that an automatic part of the build process

Follow the tech promotion checklist here #72

When I search for steps to do a particular public service, I would see a snippet of the instructions directly in the search results.

• Example page: https://www.gov.uk/learn-to-drive-a-car
• Exampe Google search results: https://www.google.com/search?client=firefox-b-1-d&q=learn+to+drive+a+car+uk

References

• How Google’s featured snippets work
• Create good titles and snippets in Search Results

cc @artuoma @ChadABratton @carterm

Reference: https://www.w3.org/WAI/planning/statements/

Create a service that returns state holidays in ical format.

• Create Google Calendar
• Enter Google Calendar dates
• Service Hello World connection to Google Calendar
• Final product that returns completed ICAL file

Continuation of...#63

https://cagov.github.io/exp/mw/index.html