@ChadABratton @abquirarte here's information on removing adverts from the handbook:

https://docs.readthedocs.io/en/latest/advertising/ethical-advertising.html#opting-out

We may be able to contact them and ask if they can give us an exception given it's a .gov project.

Reference: https://docs.readthedocs.io/en/stable/guides/google-analytics.html

cc @ChadABratton @carterm

Is your feature request related to a problem? Please describe.

Per conversation with Sarah, items to add to content guide:

• Crit info (about / guidelines)
• Guidance on services subheading/sections options (ex: Who qualifies, Deadline, Contact, Help, Steps, etc.)
• Guidance on the purpose of page descriptions (p.lead) in jumbo
• Guidance on what does/doesn't qualify as a user story we should be working on ( cc @hilaryhb as this might be a great check point in the workflow)

cc @humancenteredhuman @abquirarte @artuoma

See: cagov/Alpha#15 (comment)

I’m test

We need to include copy in the Welcome section that explains what the handbook is/who we are.

DRAFT COPY
The Alpha.CA.gov team is working to make it easier for Californians to access, understand and use digital information and services. This handbook is a product of that work.

This handbook is an iterative, practical and accessible tool. Our team uses it to record and reference our ways of work, principles and guidelines.

For anyone else visiting this page, we offer this handbook as a resource.

• create editable hi-res files for ca-dark + ca-light + avatar
• create svg/png images for ca-dark + ca-light + avatar

Reference folder: https://github.com/cagov/handbook-cadotgov/tree/master/docs/assets

Replace existing handbook url https://handbook-cadotgov.readthedocs.io/en/latest/ with custom domain handbook.alpha.ca.gov

• submit dns request to map handbook.alpha.ca.gov to readthedocs.io
• add the custom domain to the readthedocs admin seciton
• enforce http > https redirect

make sure to update product framing in the handbook

Reference: https://mkdocs.readthedocs.io/en/stable/user-guide/styling-your-docs/

@artuoma I can show you how to do this.

Currently missing:
Tools

• GSuite User Guidelines
• GitHub User Guidelines
• Admin Policy Guidelines

• Font: Selected Public Sans (https://public-sans.digital.gov/) because it was designed by government (as part of the U.S. Web Design System) to be accessible to the public. It's also an open font (license: https://github.com/uswds/public-sans#license), following on our open (source/culture) principles.
• Front-end framework: Selected Bootstrap (https://getbootstrap.com/) because it is a widely-used and maintained front-end framework that makes developing mobile-first web applications faster. It also has an open license (https://getbootstrap.com/docs/4.4/about/license/). The current state template also uses Bootstrap (older version - https://webstandards.ca.gov/state-template-v5/) that can more easily be upgraded to the one we're using.
• Dark/light color: We've chosen to focus on a high-contrast (dark/light, black/white) approach with respect to color to further ensure visual accessibility.

As a member of Team Alpha, I would like to learn how GitHub works so I can better collaborate on the project.

Reference:

• https://guides.github.com
• https://www.markdownguide.org/

As a contributor to the Alpha.CA.gov handbook, I would like to see a workflow process for adding content so I'm aware of protocol for updating the handbook.

Suggestions:

• Keep process simple
• Use one Google Doc for managing pre-published content (would also include working outline for the handbook so we can document what else should be in here)
• Add 'Contributions' page to the handbook with workflow information
• Create an issue template based on the workflow

Is your feature request related to a problem? Please describe.
Would like to update design principles.

Describe the solution you'd like

Updated principles here:

https://docs.google.com/document/d/1WJL6AqUBkSm9vD82uHLMSm2YUEkksTeqyXGHaEA0MO4/edit#heading=h.uq3l9bf5raw3

From Readthedocs documentation:
https://docs.readthedocs.io/en/stable/custom_domains.html

Custom Domain Support
You can also host your documentation from your own domain by adding a domain to your project:

Add a CNAME record in your DNS that points the domain to: readthedocs.io
Add a project domain in the Domains project admin page for your project.

Suggest adjusting the organization so that "Welcome" and "Employee Resources and Guidelines" are separate primary Headers.

Need to move "Website Architecture" out of "Welcome" (where to, not sure)

Updated left hand navigation wld include:
Welcome
Employee Resources and Guidelines
Planning
Principles
Assets

As a member of the team, I need insight into brand guidelines, so I can effectively communicate the Alpha 'brand' in a uniform way.

This includes:

• 'logo'
• colors
• font(s)
• Proper use of Alpha.CA.gov, etc.

cc @jpetrucione

• Add link to Google doc
• Design content owners

Document: https://docs.google.com/document/d/1YsOO9GL5MXlkVTZ4JQHFefdRwPRgTe_ACNNRsGjs1LI/edit

Describe the bug

@ChadABratton @aaronhans could you take a look at this? I'm getting a build fail when trying to push updates.

Build #10302660: https://readthedocs.org/projects/handbook-cadotgov/builds/10302660/

cc @jpetrucione @KimberlyglennTSM @abquirarte

Document here:
https://docs.google.com/document/d/1_yB9t608T-oIU3FO85NdHLqbnaIOx6ADJS6cPvPSzlE/edit#

• Create landing page for handbook
• create new markdown pages where more information is needed about specific subjects
• upload existing documentation from Google Drive - Shared Alpha Drive

See: cagov/Alpha#15 (comment)

I a designer/content provider for Alpha.CA.gov, I would like guidance on content style so I can make sure I'm following proper content strategy and protocol.

Reference:

• https://content-guide.18f.gov/
• https://content-guide.18f.gov/style-guides/

General recommendation: Wherever Alpha.CA.gov is spelled out, it should be linked.

See Code California:

https://codecagov-playbook.readthedocs.io/en/latest/licensing/