The California ODI team wanted to better understand the specific pain points and blockers that might prevent eligible Californians from successfully applying for the Emergency Broadband Benefit.
\n", - "author": "Jim Bumgardner", + "author": "Aaron Hans", "featured_media": 168, "comment_status": "closed", "ping_status": "closed", diff --git a/pages/blog/posts/wordpress-posts/introducing-the-new-ca-cannabis-website.json b/pages/blog/posts/wordpress-posts/introducing-the-new-ca-cannabis-website.json index 1a76d7c8..9c8f4f57 100644 --- a/pages/blog/posts/wordpress-posts/introducing-the-new-ca-cannabis-website.json +++ b/pages/blog/posts/wordpress-posts/introducing-the-new-ca-cannabis-website.json @@ -1,7 +1,7 @@ { "meta": { "created_date": "2021-07-21T16:26:43", - "updated_date": "2021-07-22T17:53:41", + "updated_date": "2023-12-06T18:45:50", "field_reference": "https://developer.wordpress.org/rest-api/reference/posts/", "api_version": "v2", "api_url": "https://live-digital-ca-gov.pantheonsite.io/wp-json/wp/v2/", @@ -18,15 +18,15 @@ "date": "2021-07-21T09:26:43", "date_gmt": "2021-07-21T16:26:43", "guid": "https://live-digital-ca-gov.pantheonsite.io/?p=59", - "modified": "2021-07-22T10:53:41", - "modified_gmt": "2021-07-22T17:53:41", + "modified": "2023-12-06T10:45:50", + "modified_gmt": "2023-12-06T18:45:50", "slug": "introducing-the-new-ca-cannabis-website", "status": "publish", "type": "post", "link": "https://live-digital-ca-gov.pantheonsite.io/2021/07/21/introducing-the-new-ca-cannabis-website/", "title": "Introducing the new CA Cannabis website", "excerpt": "We’re proud to have led the months-long collaboration to build the Cannabis.ca.gov site.
\n", - "author": "Jim Bumgardner", + "author": "Aaron Hans", "featured_media": 41, "comment_status": "closed", "ping_status": "open", @@ -36,7 +36,9 @@ "meta": { "footnotes": "" }, - "categories": [], + "categories": [ + "Uncategorized" + ], "tags": [ "Bureau of Cannabis Control", "CA.gov", @@ -83,7 +85,24 @@ "twitter_title": "Introducing the new CA Cannabis website", "twitter_description": "We’re proud to have led the months-long collaboration to build the Cannabis.ca.gov site. " }, - "headless_categories": [], + "headless_categories": [ + { + "term_id": 1, + "name": "Uncategorized", + "slug": "uncategorized", + "term_group": 0, + "term_taxonomy_id": 1, + "taxonomy": "category", + "description": "", + "parent": 0, + "filter": "raw", + "cat_ID": 1, + "category_description": "", + "cat_name": "Uncategorized", + "category_nicename": "uncategorized", + "category_parent": 0 + } + ], "headless_tags": [ { "term_id": 17, diff --git a/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.html b/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.html index 74eb0533..e9130a03 100644 --- a/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.html +++ b/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.html @@ -57,7 +57,11 @@We use the README markdown content for both:
-Our component maturity model describes how we ensure each component is accessible. The automated steps run during each commit to the Design System repository. Our accessibility verification process for each component includes:
-Outside thoughts help us improve the usability of Design System components. We’ve learned from state digital teams:
-We regularly glean insights from the staff attending Digital Web Services Network meetings. For example, we learned recently that teams need to be able to customize components.
@@ -99,11 +133,27 @@This clearly flags early versions of components as not yet fully baked. This gives us the freedom to use an iterative development process where we:
-Our promotion requirements are strict, especially in the later stages. If we make radical changes to a component we might even move it backwards on the maturity scale. This gives developers confidence that mature components are fully vetted for:
-The entire Design System is still in Beta status (though many components are still in Alpha). We’re still gathering more feedback from people and improving these tools.
diff --git a/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.json b/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.json index 26a6bc71..b0a58392 100644 --- a/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.json +++ b/pages/blog/posts/wordpress-posts/tech-choices-in-the-california-design-system.json @@ -1,7 +1,7 @@ { "meta": { "created_date": "2022-05-31T17:25:07", - "updated_date": "2022-06-01T16:08:39", + "updated_date": "2023-12-06T18:45:15", "field_reference": "https://developer.wordpress.org/rest-api/reference/posts/", "api_version": "v2", "api_url": "https://live-digital-ca-gov.pantheonsite.io/wp-json/wp/v2/", @@ -18,15 +18,15 @@ "date": "2022-05-31T10:25:07", "date_gmt": "2022-05-31T17:25:07", "guid": "https://live-digital-ca-gov.pantheonsite.io/?p=513", - "modified": "2022-06-01T09:08:39", - "modified_gmt": "2022-06-01T16:08:39", + "modified": "2023-12-06T10:45:15", + "modified_gmt": "2023-12-06T18:45:15", "slug": "tech-choices-in-the-california-design-system", "status": "publish", "type": "post", "link": "https://live-digital-ca-gov.pantheonsite.io/2022/05/31/tech-choices-in-the-california-design-system/", "title": "Tech choices in the California Design System", "excerpt": "Learn about the decisions we made (and why we made them) in putting the Design System together.
\n", - "author": "Jim Bumgardner", + "author": "Aaron Hans", "featured_media": 557, "comment_status": "closed", "ping_status": "closed", diff --git a/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.html b/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.html index b4965308..e2524261 100644 --- a/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.html +++ b/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.html @@ -1,27 +1,40 @@ -We work in the open! This means that:
-From the start, the Office of Digital Innovation (ODI) has made working in the open a core value. We often cite the motto “default to open.” There are tons of benefits to defaulting to open. From an engineering perspective it encourages:
-It also allows us to work seamlessly with anybody interested in our work. This includes state employees as well as supporters outside the government. We’ve accepted external contributions in several of our projects, including:
- +Here’s an example of how a state employee contributed to the California Design System. Kurtis Kroon from the Franchise Tax Board reviewed the code of the accordion component and suggested we use the <details> element to simplify.
This was a great idea. It required a full component rewrite. We collaborated with other teams by sharing codepens. Here’s an early version:
- -
The result was a big improvement on the component’s progressive enhancement. Now if all JavaScript on the page fails, the accordion will look different but function the same. This version lets the browser handle the open and close. This change simplified the component’s markup:
| Before | After |
|---|---|
Before  | After  |
We’re happy to work with any potential contributors, even if it’s not part of a course! The California Design System is still new and needs all kinds of expertise. It doesn’t even have to be help with code. We can use help with:
-The collaboration has been fruitful. These students get real world experience contributing to an open source project. The state gets:
-We’re really impressed with these folks. They’ve all:
-Check out the GitHub profiles for:
- +Here’s some of their work on the Design System:
diff --git a/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.json b/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.json index 2df8aab3..d75b92f3 100644 --- a/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.json +++ b/pages/blog/posts/wordpress-posts/working-in-the-open-on-the-california-design-system.json @@ -1,7 +1,7 @@ { "meta": { "created_date": "2022-05-19T16:38:16", - "updated_date": "2022-05-19T19:54:09", + "updated_date": "2023-12-06T18:45:28", "field_reference": "https://developer.wordpress.org/rest-api/reference/posts/", "api_version": "v2", "api_url": "https://live-digital-ca-gov.pantheonsite.io/wp-json/wp/v2/", @@ -18,15 +18,15 @@ "date": "2022-05-19T09:38:16", "date_gmt": "2022-05-19T16:38:16", "guid": "https://live-digital-ca-gov.pantheonsite.io/?p=474", - "modified": "2022-05-19T12:54:09", - "modified_gmt": "2022-05-19T19:54:09", + "modified": "2023-12-06T10:45:28", + "modified_gmt": "2023-12-06T18:45:28", "slug": "working-in-the-open-on-the-california-design-system", "status": "publish", "type": "post", "link": "https://live-digital-ca-gov.pantheonsite.io/2022/05/19/working-in-the-open-on-the-california-design-system/", "title": "Working in the open on the California Design System", "excerpt": "Working in the open is important to us. Here’s what that looks like in our work on the California Design System.
\n", - "author": "Jim Bumgardner", + "author": "Aaron Hans", "featured_media": 504, "comment_status": "closed", "ping_status": "closed",