{
    "version" : "https://jsonfeed.org/version/1",
    "content" : "event",
    "type" : "single",
    "title" : "USWDS Monthly Call - February 2024 |Digital.gov",
    "description": "USWDS Monthly Call - February 2024",
    "home_page_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/","feed_url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/event/2024/02/15/uswds-monthly-call-february-2024/index.json","item" : [
    {"kicker" : "USWDS","title" :"USWDS Monthly Call - February 2024","deck" : "How to suggest a new component for the U.S. Web Design System","summary" : "Learn about the USWDS component lifecycle, and how you can suggest a new component.","date" : "2024-02-15T14:00:00-05:00","date_modified" : "2025-01-27T19:42:55-05:00","start_date" : "2024-02-15T14:00:00-05:00","end_date" : "2024-02-15T15:00:00-05:00",
      "event_organizer" : "Digital.gov","host" : "U.S. Web Design System","registration_url" : "https://gsa.zoomgov.com/meeting/register/vJIsceyvpz4iGws79NmQy1Dj0BUoDVtPKzs#/registration","youtube_id" : "cmP9XsYVwQI","topics" : {
        
            "design" : "Design",
            "human-centered-design" : "Human-centered design"
            },"primary_image" : { "uid" : "2024-uswds-monthly-call-feb-title-card", "alt" :
  "Title card image of USWDS logo, a multi-colored pentagon shape consisting of five triangles, centered on a black background. In blue text, the first line says, U.S. Web Design System (USWDS). Below in white text, the second line has the event name, USWDS monthly call February 2024. Below in blue text is date followed by the date of the event in white, February 15, 2024. The next line in blue text is Time followed by the time of the event in white, 2:00 pm ET.", "width" :
  "1200", "height" :
  "628", "credit" :
  "", "caption" :
  "", "format" :
  "png" },"content" :"\n\u003ca\n    href=\"https://s3.amazonaws.com/digitalgov/static/USWDS%20Monthly%20Call%20Feb%202024.pptx\"\u003eView the slides (PowerPoint presentation, 5.8 MB, 81 pages)\u003c/a\u003e\n\n\n\u003cdiv class=\"usa-accordion accordion\"\u003e\u003ch3 class=\"usa-accordion__heading\"\u003e\n    \u003cbutton\n      class=\"usa-accordion__button\"\n      title=\"View \"\n      aria-expanded=\"false\"\n      aria-controls=\"accordion-1\"\n    \u003e\n      \u003cspan class=\"icon\"\u003e\n          \u003csvg\n            class=\"usa-icon dg-icon dg-icon--standard margin-bottom-05\"\n            aria-hidden=\"true\"\n            focusable=\"false\"\n          \u003e\n            \n            \u003cuse xlink:href=\"/preview/gsa/digitalgov.gov/bc-archive-content-3/uswds/img/sprite.svg#content_copy\"\u003e\u003c/use\u003e\n          \u003c/svg\u003e\n        \u003c/span\u003e\u003cspan class=\"src\"\u003e\n        \u003cstrong class=\"kicker\"\u003eSlide by Slide\u003c/strong\u003eUSWDS Monthly Call - Presentation Script for February 2024\n        \u003c/span\n      \u003e\n    \u003c/button\u003e\n  \u003c/h3\u003e\u003cdiv\n      id=\"accordion-1\"\n      class=\"accordion-body usa-accordion__content usa-prose\"\n    \u003e\u003cp\u003e\u003cstrong\u003eSlide 1:\u003c/strong\u003e Welcome everyone, to the U.S. Web Design System monthly call for February, 2024 — This month we\u0026rsquo;re celebrating Black History Month with shades of green, gold, orange, and brown. As well as Valentine\u0026rsquo;s Day yesterday with shades of pink.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 2:\u003c/strong\u003e My name is Dan Williams, he/him, and I\u0026rsquo;m the USWDS project lead — and here on-screen is my avatar: dark hair, blue sweater, collared shirt. Today my physical self is wearing a plaid flannel shirt and a fleece, because it\u0026rsquo;s still winter. On my fleece is a green button with some sprouts on it that my son made for me.\u003c/p\u003e\n\u003cp\u003eAs Jeannie mentioned, we are recording this call, and I\u0026rsquo;m happy to say we\u0026rsquo;ve started to be able to share the recordings of these monthly calls publicly. You can find pretty much everything from the last year\u0026rsquo;s worth of monthly calls — back to January 2023 — on our website, at \u003ca href=\"https://designsystem.digital.gov/about/monthly-calls\"\u003edesignsystem.digital.gov/about/monthly-calls\u003c/a\u003e. We typically post videos within a week of the monthly call, and we also link out to the slides and the script, hosted at digital.gov. We\u0026rsquo;ve posted a link to our monthly call page in the chat.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;ll be posting other links and references into the chat as we go along, and I encourage you to ask questions in the chat at any time. If any member of our team can answer your question in the chat, we\u0026rsquo;ll do so, otherwise there\u0026rsquo;ll be some time for questions and answers at the end of the hour. Also, be sure to introduce yourself in the chat as well — it\u0026rsquo;s nice to know who\u0026rsquo;s here. It\u0026rsquo;s good to have you here today.\u003c/p\u003e\n\u003cp\u003eFor those of you who find the chat distracting, you’re welcome to close or hide the chat window during the main presentation. You can reopen it later during the Q\u0026amp;A session at the end of this call.\u003c/p\u003e\n\u003cp\u003eSo thanks! And, with that, let\u0026rsquo;s get started!\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 3:\u003c/strong\u003e So what\u0026rsquo;s our agenda for today?\u003c/p\u003e\n\u003cp\u003eWe’ve got a couple nice new site and feature launches, a couple product updates, and then we’ll spend the rest of the time talking about a USWDS component lifecycle model and our new approach to new-component proposals.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 4:\u003c/strong\u003e Let\u0026rsquo;s get into it with site launches.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 5:\u003c/strong\u003e First, \u003ca href=\"https://www.google.com/url?q=https://simpler.grants.gov\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1711052748736300\u0026amp;usg=AOvVaw2YSQ8xGM91WUdioPsTCZMY\"\u003esimpler.grants.gov\u003c/a\u003e, an exciting new initiative from the grants.gov team at the Department of Health and Human Services.\u003c/p\u003e\n\u003cp\u003eGrants.gov provides a centralized location for grant seekers to find and apply for federal funding opportunities. Simpler.grants.gov is a new site from the grants.gov team that\u0026rsquo;s using a transparent, iterative, and agile process to document their progress modernizing and improving the grants.gov service. It\u0026rsquo;s an exciting project where they\u0026rsquo;ll be building software out in the open, and I for one, am pretty interested in their approach and their progress! The simpler.grants.gov homepage features a simple, text-focused layout, with a large blue hero field and the words \u0026ldquo;We\u0026rsquo;re building a simpler Grants.gov!\u0026rdquo;\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 6:\u003c/strong\u003e Next, \u003ca href=\"https://www.google.com/url?q=https://search.gov\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1711052748730824\u0026amp;usg=AOvVaw3N-xMZKFbY9VHxVGWKAjS-\"\u003eSearch.gov\u003c/a\u003e is starting to roll out hosted search results pages powered by USWDS code.\u003c/p\u003e\n\u003cp\u003eYou know search.gov, right? It\u0026rsquo;s the search engine by and for the federal government, a free service powering search results on over 2,000 websites. Earlier this year they released a beta of a USWDS-based redesign of their hosted results page. Now Digital.gov is the first site to be able to use it, hosting a USWDS-powered search result layout! Search.gov and DigitalGov — a real chocolate and peanut butter combination in my book.\u003c/p\u003e\n\u003cp\u003eOn this slide we see the \u003ca href=\"https://www.google.com/url?q=https://find.digitalgov.gov/search?utf8%3D%25E2%259C%2593%26affiliate%3Ddigitalgov%26query%3Dusability%26commit%3D\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1711052748731793\u0026amp;usg=AOvVaw1J9MZWOISXo_njMu-hJ7Ti\"\u003eDigital.gov search results\u003c/a\u003e page for the keyword \u0026ldquo;usability.\u0026rdquo; We see a clean display of search results, as well as a way to select between all search results and just videos.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 7:\u003c/strong\u003e Congratulations and great work! Be sure to let our team know when a new site launches, either with an email or a note on the USWDS public Slack channel!\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 8:\u003c/strong\u003e Now for a few product updates…\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 9:\u003c/strong\u003e First USWDS 3.8.0. Last month I said that it would be coming in January… but that didn\u0026rsquo;t happen. We got super busy with a lot of the component lifecycle work we\u0026rsquo;re talking about today, so we had to delay the release.\u003c/p\u003e\n\u003cp\u003eWell it\u0026rsquo;s still coming — and it\u0026rsquo;s still a release that has a number of good improvements largely contributed by the community, like sticky headers in tables, alignment improvements for icons in buttons, and indeterminate checkbox styling — but we\u0026rsquo;re now aiming for the end of this month. And this time, we will hit that deadline, and you can check in on our progress on our public project board — \u003ca href=\"https://www.google.com/url?q=https://github.com/orgs/uswds/projects/8/views/32?sliceBy%255Bvalue%255D%3Duswds%2B3.8.0\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1711663441786792\u0026amp;usg=AOvVaw1fmg5gDdwSmTHDPqCZLvai\"\u003ewe\u0026rsquo;re posting that link in the chat\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 10:\u003c/strong\u003e Next, I\u0026rsquo;d like to give an update on the accessibility tests we launched last month.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 11:\u003c/strong\u003e This month we\u0026rsquo;ll be launching accessibility test pages for three more design system components: table, icon, and typography. We\u0026rsquo;re just finishing these up as well, and we\u0026rsquo;ll be publishing them alongside USWDS 3.8.0 by the end of the month. And that\u0026rsquo;s it for product updates!\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 12:\u003c/strong\u003e So today, we\u0026rsquo;d like to talk about work we\u0026rsquo;ve done to outline a USWDS component lifecycle model, and improvements we\u0026rsquo;re making to new-component proposals.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 13:\u003c/strong\u003e At the end of last year, we did a lot of thinking about where we\u0026rsquo;re going as a design system; what we value, and where we\u0026rsquo;re going to spend our time and energy. At the end of that thinking, we came to the monthly call and talked about updates to our mission and vision. And also about our Polestar, where we\u0026rsquo;re pointed as a product.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 14:\u003c/strong\u003e Polestar: We help government teams align, design, and keep their websites and services up to date.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 15:\u003c/strong\u003e Vision: Empowered and supported digital service teams. Familiar and easy-to-use digital services.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 16:\u003c/strong\u003e Mission: Shaping the future of government digital services.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 17:\u003c/strong\u003e As we come into 2024, you may ask, \u0026ldquo;Why component lifecycle now?\u0026rdquo; It may seem surprising that we\u0026rsquo;re talking about a component lifecycle model — about how components are proposed and developed, how they make their way into the design system, mature, and how sometimes they\u0026rsquo;re deprecated and retired. Why is this a priority now?\u003c/p\u003e\n\u003cp\u003eWell, a component lifecycle is not just for devs and pedants. Today we\u0026rsquo;d like to talk about how it really connects to our mission and supports the kinds of connections and activities at the heart of our product.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 18:\u003c/strong\u003e Thinking about how components start, grow, and mature is something of a scale model of how the design system itself grows and matures, since components are such an important part of what we deliver.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 19:\u003c/strong\u003e Specifically, we\u0026rsquo;re really focused on how USWDS can be a place to connect digital design and delivery teams across government, to better know what we know, and learn from each other.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 20:\u003c/strong\u003e You know, I hate to be the person to tell you this, but our government is big.\u003c/p\u003e\n\u003cp\u003eAnd collectively, in the aggregate, we know a lot. There\u0026rsquo;s incredible skill, talent, sensitivity, craftsmanship, and care across our teams, our agencies, and our products.\nIf you take a long view of what we, together, are building, I believe it\u0026rsquo;s inarguable that government digital services are improving — and I would argue further that government digital services are improving faster than the internet as a whole.\u003c/p\u003e\n\u003cp\u003eIf government is the tortoise in the race between the tortoise and the hare, I\u0026rsquo;d say the tortoise has the momentum these days.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 21:\u003c/strong\u003e And I\u0026rsquo;d say \u003cem\u003ethat\u0026rsquo;s\u003c/em\u003e because of a real mission-driven commitment to human centered design and to our inclination to pitch in, to help out, to share what we know with each other, and keep pushing forward.\nBecause for sure, while momentum may be on our side, there\u0026rsquo;s a long way to go, and honestly there\u0026rsquo;s never really a finish line.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 22:\u003c/strong\u003e It\u0026rsquo;s long been our challenge here at USWDS to facilitate collaboration and contribution, to share and scale effective solutions from anywhere in government. To convert the skill and experience that we clearly have in the aggregate into a common infrastructure that supports and elevates any team and product. And that\u0026rsquo;s been a tough nut to crack.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 23:\u003c/strong\u003e Today we\u0026rsquo;re going to get started on this challenge through the angle of splitting bigger problems into smaller problems, and trying to build a framework for solving complex problems — and building complex solutions — a little at a time. Lowering the barriers to participation in the service of delivering high quality finished work.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;re going to approach this from two angles: one which you might call the food truck scenario, and the other which you might call finding the elephant. Or, \u003cem\u003eyou\u003c/em\u003e might not yet call it that, yet, but \u003cem\u003eI\u003c/em\u003e am!\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 24:\u003c/strong\u003e First, the food truck scenario — or simply that it is hard to start something really big like a restaurant. It\u0026rsquo;s complicated, expensive, and can take a huge amount of resources and risk to even consider building an operation like that. It really limits who can participate.\u003c/p\u003e\n\u003cp\u003eI live in Portland, and one solution to this problem that\u0026rsquo;s popular here and now pretty much is popular everywhere else as well, is the food truck. What if you could begin to reduce the resources and risk to participate? What if you could prove an idea at a smaller scale? Or like a pop-up restaurant that exists for only a week, using an existing restaurant and kitchen. All these smaller-scale solutions to the problem of the restaurant — of getting food — still need to be safe, they still need to be up to code, and they still need to \u003cem\u003edeliver\u003c/em\u003e good food.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 25:\u003c/strong\u003e But in general: what if there were smaller steps between nothing and everything?\u003c/p\u003e\n\u003cp\u003eIn our world, the \u0026ldquo;restaurant\u0026rdquo; is something like the component. Delivering a final component requires design, development, and research of course, but also a complete guidance page and now accessibility tests. Developing a new component is a big commitment, and contributing a component to the design system is a big risk and a lot of work, like trying to get a big new piece of furniture into a tiny walk-up apartment. There\u0026rsquo;s really no guarantee you\u0026rsquo;ll actually be able to get it up the stairs and into the door.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 26:\u003c/strong\u003e So how can we lower the barrier to participation by creating smaller steps between nothing and a component?\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 27:\u003c/strong\u003e How can we enable contribution by defining what we need at each phase?\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 28:\u003c/strong\u003e How can we help get component contributions into the design system with fewer up-front requirements?\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 29:\u003c/strong\u003e And how can we establish cross-team and cross-agency conversations and communication as the continuity between these phases?\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 30:\u003c/strong\u003e Let\u0026rsquo;s get into it with two of my colleagues…\nFirst, Amy Leadem, a contractor and a developer on the USWDS core team. Amy, can you introduce yourself and give a brief self description?\u003c/p\u003e\n\u003cp\u003eAL: Absolutely. Hello everyone, I’m Amy and I am a contractor on the engineering team here at USWDS. I am a white woman with long, wavy brown hair, and today I am wearing a light pink sweater. My pronouns are she/her.\u003c/p\u003e\n\u003cp\u003eDW: Thanks Amy!\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 31:\u003c/strong\u003e I\u0026rsquo;d also like to introduce Anne Petersen, the Experience Design lead on the core team. Anne, can you introduce yourself and give a brief self description?\u003c/p\u003e\n\u003cp\u003eAP: For sure. I’m Anne Petersen, my pronouns are they/them. I’m a white person with short brown hair and small glasses in a dark blue shirt today.\u003c/p\u003e\n\u003cp\u003eDW: Thanks Anne. First, I\u0026rsquo;d like to pass it to Amy, to walk us through our new component lifecycle model.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 32:\u003c/strong\u003e AL: Thanks, Dan. This is Amy and I’m going to show you how we structured the steps in the component lifecycle model, starting with what we\u0026rsquo;re calling \u003cstrong\u003ephases\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 33:\u003c/strong\u003e The overall shape of the lifecycle covers the progression of a component on the way up from just an idea to a mature, stable component published in the design system and in use in projects. It also covers the — as yet unused — process for a component on the way down, deprecating and retiring components that we no longer recommend or support.\u003c/p\u003e\n\u003cp\u003eThe overall shape is a bit like the rising and falling shape we see on the slide as the life cycle progresses: rising to maturity and falling at the end.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 34:\u003c/strong\u003e These main phases in our component lifecycle may seem familiar to you. They are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eProposal:\u003c/strong\u003e These components are under consideration for development through public discussion and a formal proposal. This part of the shape is now colored gold.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eDevelopment:\u003c/strong\u003e These are the components undergoing active design, development, testing, and documentation before public release. This part of the shape is now colored blue.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReleased:\u003c/strong\u003e These are the components we\u0026rsquo;ve released to the public in our distribution package and documented on the USWDS website. This part of the shape is now colored green.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eDeprecated:\u003c/strong\u003e These are the components that do not meet requirements or are no longer needed. This part of the shape is now colored pink.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 35:\u003c/strong\u003e But what\u0026rsquo;s perhaps less familiar are the sub-phases (or steps) within these larger lifecycle groupings. We\u0026rsquo;re putting a lot of work into establishing smaller steps with clearer transitions between steps.\u003c/p\u003e\n\u003cp\u003eEstablishing sub-phase steps allows us to know precisely what is happening — and needs to happen — with the component at any point in the life cycle. This clarity allows us to define specific responsibilities and requirements for each step, which not only will help us know what needs to happen next to keep the component moving, but also will present opportunities for community contributors to help fulfill those requirements as well.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 36:\u003c/strong\u003e I\u0026rsquo;d like to call out a new step we\u0026rsquo;re introducing in the Released phase: \u003cstrong\u003eExperimental\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe Experimental step of the Released phase — now colored in darker green in our diagram — is a bit of a pilot. To Dan\u0026rsquo;s earlier point, we\u0026rsquo;re considering Experimental to be something of the food truck to the brick-and-mortar of stable USWDS components. We\u0026rsquo;re hoping we can use an Experimental step to release promising components earlier to help collect more real-world usability research. These components might have fewer documentation requirements, less research backup, maybe a few unanswered questions — along with the expectation that they might change more than stable components. But they would include accessibility tests and would be OK to use in production websites.\u003c/p\u003e\n\u003cp\u003eToday, we\u0026rsquo;ve published an overview of all of these phases and steps on our new component lifecycle page on our website. Let’s take a look.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 37:\u003c/strong\u003e Our new component lifecycle page gives an overview of each phase and step of the component lifecycle. This page covers:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eWhat happens in each step,\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhen each step starts and ends,\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eHow you can contribute during each step,\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhere you can find the components that are in each step.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eYou can find this new page at \u003ca href=\"https://designsystem.digital.gov/components/lifecycle\"\u003edesignsystem.digital.gov/components/lifecycle\u003c/a\u003e.\nAnd now, since every component — from idea and proposal to stable and deprecation — is in one of the steps of the life cycle, we\u0026rsquo;ve also been able to build a new component status page to help you know what\u0026rsquo;s happening with both components we\u0026rsquo;ve released in the design system and components that aren\u0026rsquo;t in the design system yet.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 38:\u003c/strong\u003e Our new component status page lists all of the USWDS components — and component ideas — currently in the life cycle, and shows which phase the component is currently in. We also provide a link to the most current information on the component. Depending on the phase, this link might point to the discussion, issue, pull request, or component page. You can find this new page at \u003ca href=\"https://designsystem.digital.gov/components/status\"\u003edesignsystem.digital.gov/components/status\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eAnd it\u0026rsquo;s worth repeating that this page will list components that are in the Proposal phase as well, so it can serve as an important reference if you\u0026rsquo;re interested in whether the design system has a specific component, or whether a component you need has a proposal already in progress. If there isn\u0026rsquo;t a proposal, or if you want to speed up the proposal process with your own contributions, well… that\u0026rsquo;s what we\u0026rsquo;ll talk about in just a moment!\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 39:\u003c/strong\u003e But first, I\u0026rsquo;ll pass it over to Anne to talk about what\u0026rsquo;s next with the component lifecycle.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 40:\u003c/strong\u003e AP: Thanks Amy, this is Anne. That’s a great question. How will this component lifecycle evolve? What’s next for it, and next after that? The exciting part is that we don’t know. Iteration! In action! We’ll find out, basically, as we go.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 41:\u003c/strong\u003e But we do have some assumptions. We think that it\u0026rsquo;s going to be important to get more and more clear and provide more and more detail about how a component moves from one step or phase to another, to develop specific requirements and criteria, and continue to remove ambiguity.\u003c/p\u003e\n\u003cp\u003eDetermining things like: What\u0026rsquo;s necessary to release a component as experimental?\u003c/p\u003e\n\u003cp\u003eOr: When we evaluate proposals, what criteria should we use?\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;re still working through these questions and we hope, eventually, that more clarity will empower folks like you to contribute. But right now we’re figuring out how this initial version works in reality. Where might people not feel empowered or comfortable to participate? Will the detail we need to make sure the components we offer are practical and grounded and are well-tested mean an extra burden for you?\u003c/p\u003e\n\u003cp\u003eSo we\u0026rsquo;ll have to pay attention, see it in action, and listen. To \u003cem\u003eyou\u003c/em\u003e. We want to hear from you.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 42:\u003c/strong\u003e And when we\u0026rsquo;re thinking about all these details, requirements, and evaluation criteria, we\u0026rsquo;re going to be starting from our stated values. We\u0026rsquo;ll go back to our \u003ca href=\"https://www.google.com/url?q=https://designsystem.digital.gov/about/\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1711663441787888\u0026amp;usg=AOvVaw3BnY43NX-mYZhnPJj37ynX\"\u003emission, vision, polestar\u003c/a\u003e, and \u003ca href=\"https://designsystem.digital.gov/design-principles/\"\u003edesign principles\u003c/a\u003e, and \u003ca href=\"https://designsystem.digital.gov/about/product-values/\"\u003eproduct values\u003c/a\u003e, and proceed from there.\u003c/p\u003e\n\u003cp\u003eThese values are our best articulation of how we think about our own priorities and decision-making, and ultimately the direction of USWDS. They’re where we start, and where we\u0026rsquo;ll ground our evaluation considerations.\u003c/p\u003e\n\u003cp\u003eYou’ve maybe heard the platitude that tells you how to think about whether to say things out loud: Is it true? Is it kind? Is it necessary? This is our version.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 43:\u003c/strong\u003e In order to be effective, the transitions between phases need public, practical, easy-to-understand requirements. They\u0026rsquo;ll need to be concrete and clear.\nAnd in order to be fair, we\u0026rsquo;ll need to publish any requirements before we start any evaluation.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 44:\u003c/strong\u003e So there are still a number of things to work out. This process \u003cem\u003eitself\u003c/em\u003e is in beta.\u003c/p\u003e\n\u003cp\u003eI feel like I’m always the one to get meta in these calls, so here we go again. I’ll try to keep it brief.\u003c/p\u003e\n\u003cp\u003eThis whole thing is something we’re trying out. Our first but maybe-not-best attempt; though certainly the best we think works right now. We don’t know how well it will work, so we’re open to change here. As we put it into action, I bet we’ll quickly find out if we need to revise. Tell us how it goes.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 45:\u003c/strong\u003e So: let’s try it out! And we think that the best place for folks to start to engage with this process is at the beginning.\nHow does this process start, for you, right now? Dan, want to give us that starting point?\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 46:\u003c/strong\u003e DW: Thanks Anne, this is Dan again. Since we\u0026rsquo;re actively building a process we hope to refine with real contributions and community participation, it makes sense to start where we think we\u0026rsquo;ll need participation from lots of perspectives: at the beginning, with the \u003cstrong\u003ecomponent proposal\u003c/strong\u003e process.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 47:\u003c/strong\u003e And in our process, we\u0026rsquo;re starting with a discussion.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 48:\u003c/strong\u003e As I\u0026rsquo;d mentioned earlier, our second metaphor for solving complex problems is one I\u0026rsquo;d described as finding the elephant.\u003c/p\u003e\n\u003cp\u003eThis is like the story of the blind sages who each encounter only a specific part of an elephant, and thus, individually, can describe only that specific aspect. The trunk appears as a snake, the leg as a tree, the tail as a rope, the ear as fan. This is often understood as a parable about the limits of perception. But the ultimate moral depends on if and how the sages react to the knowledge of their peers. Their knowledge is distributed, their understanding is necessarily influenced by their perspective, so where do they go from there? What can they do with this distributed knowledge? How can they coordinate these different perspectives into an integrated, coherent model?\u003c/p\u003e\n\u003cp\u003eI will say that here at the design system, we wish to find the elephant. And we aim to build a place and a process where we might collect and expand our perspectives in the service of an integrated understanding.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 49:\u003c/strong\u003e In our case the elephant in the room is a proposal for a component.\u003c/p\u003e\n\u003cp\u003eWhat do we need to ask about it? What perspectives do we need to understand it?\u003c/p\u003e\n\u003cp\u003eWhy this component? What interactions does it support? When do you use it? When should you consider something else? What are its accessibility considerations? How do you use it when you can\u0026rsquo;t see it? How might you control it with only your voice? What harm might it unintentionally cause? What should a team need to know to start development? What do we already know that can help a development team start from a place of known knowns and known unknowns?\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 50:\u003c/strong\u003e To that end, we need every component to begin with a discussion.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 51:\u003c/strong\u003e And the point of that discussion is to describe the \u003cem\u003eshape\u003c/em\u003e of a proposal.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 52:\u003c/strong\u003e Not a requirements doc, but a \u003cem\u003ecase\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 53:\u003c/strong\u003e Not a prescriptive document, but an \u003cem\u003eactionable\u003c/em\u003e one.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 54:\u003c/strong\u003e And we believe that the more participation we can generate, the better the proposals we can deliver.\u003c/p\u003e\n\u003cp\u003eSo to talk about the process we\u0026rsquo;re launching today, here\u0026rsquo;s Amy.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 55:\u003c/strong\u003e AL: Thanks, Dan. This is Amy again. Our new proposal process is how we introduce new component ideas and evaluate them.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 56:\u003c/strong\u003e Our first goal was to make the process \u003cstrong\u003eintuitive\u003c/strong\u003e for all kinds of contributors. We wanted something that was more welcoming to anyone who has a perspective on components: folks like designers, usability experts, accessibility pros, and writers — not just developers.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 57:\u003c/strong\u003e Our second goal was to make the process \u003cstrong\u003eincremental\u003c/strong\u003e. As Dan mentioned earlier, we wanted to lower the burden on contributors suggesting new component ideas. To lower the barriers to participation at each step.\u003c/p\u003e\n\u003cp\u003eSo we knew we wanted to make the component proposal something we \u003cem\u003eall\u003c/em\u003e can build, collaboratively, a bit at a time. Not something where a single person or team needs to put their heads down for a month and return with a finished document, then repeat and repeat. This is more like how the process was working before, and, honestly, it wasn\u0026rsquo;t \u003cem\u003ereally\u003c/em\u003e working.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;ve developed a new component proposal process that has two distinct parts, sort of a frontstage and a backstage.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 58:\u003c/strong\u003e The frontstage is a new Component Proposal discussion board that will be the persistent home for public, community conversation about new components. You can find this new discussion board at \u003ca href=\"https://www.google.com/url?q=https://github.com/uswds/uswds/discussions/categories/component-proposals\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1711663441787743\u0026amp;usg=AOvVaw1Fe3HHeStdk-sosZMHy_rb\"\u003egithub.com/uswds/uswds/discussions/categories/component-proposals\u003c/a\u003e. On this slide, there\u0026rsquo;s a screenshot of this proposals board, with a pinned post reading, \u0026ldquo;Getting started with USWDS component discussions.\u0026rdquo;\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 59:\u003c/strong\u003e The backstage is a new proposals repo, uswds-proposals, at \u003ca href=\"https://www.google.com/url?q=https://github.com/uswds/uswds-proposals\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1712093682783342\u0026amp;usg=AOvVaw1001oegxcZVR0lPvLlqXlP\"\u003egithub.com/uswds/uswds-proposals\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eOn this slide we see a screenshot of this new proposals repo. It features a README with the text, \u0026ldquo;USWDS component proposal process.\u0026rdquo;\u003c/p\u003e\n\u003cp\u003eThis is where the USWDS core team collects what we\u0026rsquo;ve learned from these discussions into formal component proposals. It will be the new place where we document our decisions and reasoning. If you\u0026rsquo;re familiar with the concept of Architectural Decision Records (or ADRs) that\u0026rsquo;s pretty much what we\u0026rsquo;re starting here, starting with new component decisions.\u003c/p\u003e\n\u003cp\u003eBut really, the discussions are where the action will be. So let’s take a look at how we think discussions can work.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 60:\u003c/strong\u003e The new Component Proposal board in GitHub Discussions is the \u003cstrong\u003ecentral hub\u003c/strong\u003e for community discussion about new USWDS component ideas. This is where the community should work through all the merits, risks, and potential design of the component.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 61:\u003c/strong\u003e We chose to use a GitHub discussion board because it\u0026rsquo;s a tool we\u0026rsquo;re already using, and it\u0026rsquo;s designed for conversations. And these discussions \u003cem\u003eare\u003c/em\u003e conversations, not issues or pull requests. You don\u0026rsquo;t even need to know what an issue or a pull request \u003cem\u003eis\u003c/em\u003e to get involved.\u003c/p\u003e\n\u003cp\u003eThis discussion board has a lot of the tools folks expect for managing discussions:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eThere are threaded comments to help organize different topics of conversation.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eThere are simple ways to sort and filter discussions, and labeling as well.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAnd discussions also offer native upvoting functionality, which gives everyone an easy method for expressing interest in a component, and gives the USWDS team an easy\nmethod of assessing that interest.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 62:\u003c/strong\u003e What do you need to know to start a discussion? Really, just two things:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eAre you interested in suggesting a new component?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAnd, is there already an existing discussion about that new component?\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIf you are, and there isn\u0026rsquo;t, go ahead and start a new discussion!\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 63:\u003c/strong\u003e Discussions are meant to be \u003cstrong\u003eincremental\u003c/strong\u003e. You can start with a lot or a little. The person who authors the discussion doesn\u0026rsquo;t need to know everything. We\u0026rsquo;ll work it all out together eventually.\u003c/p\u003e\n\u003cp\u003eDiscussions are meant to be \u003cstrong\u003einformal\u003c/strong\u003e. Of course, be formal if that\u0026rsquo;s your style, but we aren\u0026rsquo;t expecting to post and exchange formal briefs, we\u0026rsquo;re trying to work out a common understanding together. But it\u0026rsquo;s also worth pointing out that we all agree to a code of conduct to participate. Informal doesn\u0026rsquo;t mean uncivil.\u003c/p\u003e\n\u003cp\u003eAnd discussions are meant to be \u003cstrong\u003epersistent\u003c/strong\u003e. We want to have a single discussion related to a component that we can all use as a common reference and a common place for communication as a component moves through the Proposal phase and into assignment and development.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 64:\u003c/strong\u003e So if you want to check out new component discussions and maybe start a new one yourself, head over to \u003ca href=\"https://www.google.com/url?q=http://github.com/uswds/uswds/discussions/categories/component-proposals\u0026amp;sa=D\u0026amp;source=docs\u0026amp;ust=1711663441789995\u0026amp;usg=AOvVaw0mX5Q-VhtQsBwgFnBAwMJ5\"\u003egithub.com/uswds/uswds/discussions/categories/component-proposals\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;ve been converting existing component-request issues into discussions, and the current contents of that board should be up to date, but if you know you\u0026rsquo;ve submitted a component-request issue and don\u0026rsquo;t see it there, let us know.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSee a component you\u0026rsquo;d like to see in the design system?\u003c/strong\u003e Get involved in that discussion.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eGot a new component idea that\u0026rsquo;s not yet on the board?\u003c/strong\u003e Select New discussion and start a new one.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 65:\u003c/strong\u003e So - What do we hope to get out of these discussions? How do we turn discussions into proposals? And what happens next? For that, I\u0026rsquo;ll pass it back to Anne.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 66:\u003c/strong\u003e AP: Thanks Amy. This is Anne. While proposal discussions are freeform, we are looking to collect a few specific bits of information that will help us understand the component better, and lead to the proposal that could form the practical starting point for component development, which is the next phase in the life cycle.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 67:\u003c/strong\u003e First, we want to address some general information about the proposed component:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eWhat\u0026rsquo;s the common name (or names) of this component?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhat gap does it fill in the design system? And how is this different from existing USWDS components?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAnd does this component directly support any federal laws, guidance, or policies?\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 68:\u003c/strong\u003e As well as potential design ideas and context:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eWhat\u0026rsquo;s the potential core functionality of this component?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAre there any examples of how the component might work?\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 69:\u003c/strong\u003e We\u0026rsquo;ll want to address what this component is \u003cem\u003eused\u003c/em\u003e for.\u003c/p\u003e\n\u003cp\u003eWe want to outline the appropriate use cases:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eWhat common interactions does this component support?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhat does this component need to do to be successful and effective?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhat kind of content — that is, information inside it — would be ideal for this component?\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 70:\u003c/strong\u003e And also scenarios where this component would \u003cem\u003enot\u003c/em\u003e be the appropriate choice:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eAre there common ways this type of component is misused?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAre there similar interactions that would be better supported by other components?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhat kind of content should teams not use with this component?\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 71:\u003c/strong\u003e We also want to understand any usability considerations, with supporting evidence if possible.\u003c/p\u003e\n\u003cp\u003eFrom a usability or UX perspective, we want to understand:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eWhat are the characteristics of a successful interaction with this component? How does that interaction go?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhat would make this component less usable?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eWhat are common pitfalls or implementation mistakes associated with this component?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eHow might the mobile context affect how folks use this component?\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 72:\u003c/strong\u003e From the accessibility perspective we want to understand:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eWill this component cause difficulty for people who use any assistive technologies?\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAnd could this component be difficult for any other audiences?\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 73:\u003c/strong\u003e And finally, we want to identify potential stakeholders, advocates, and volunteers related to the component. These are folks willing to help design, develop, or test the component, and any significant support from an agency or group.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 74:\u003c/strong\u003e These questions are the common criteria we\u0026rsquo;ll use to create a formal proposal document. We\u0026rsquo;ll prompt discussions to make sure we cover all this, then we\u0026rsquo;ll collect it into a formal proposal in our uswds-proposals repo as a decision-record candidate.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 75:\u003c/strong\u003e When the formal proposal is complete, we\u0026rsquo;ll post it back into the discussion for a final comment period of at least 45 days before we evaluate it.\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003ecomment period\u003c/strong\u003e is an opportunity to tell us what works and what doesn’t about this proposal, before we evaluate the proposal as a team to consider how the proposed component fits into the system and its needs, including the needs of the teams who use it. So again, your input is important.\u003c/p\u003e\n\u003cp\u003eIf we approve the proposal, it moves to the \u003cstrong\u003eassignment period:\u003c/strong\u003e where an individual or team can take that proposal into development. This \u003cem\u003emight\u003c/em\u003e be the USWDS team, but it doesn\u0026rsquo;t have to be.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 76:\u003c/strong\u003e Throughout the process, we\u0026rsquo;ll highlight active discussions in our newsletter and in these monthly calls. We don’t want to overwhelm folks with these, but we\u0026rsquo;ll be working hard to get you — the USWDS community — involved, and highlight opportunities to contribute from month to month, and keep everyone up to date as we refine this process.\u003c/p\u003e\n\u003cp\u003eWe want to make this as easy as we can. Help us understand what will work for you, to facilitate your contributions and thoughts and experiences. We can all help, to help each other.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 77:\u003c/strong\u003e And if interacting on GitHub isn’t an option for you, you can always email us at \u003ca href=\"mailto:uswds@gsa.gov\"\u003euswds@gsa.gov\u003c/a\u003e, and we can cross-post your proposal, comment, or vote.\nNow I\u0026rsquo;ll pass it back to Dan to wrap things up.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 78:\u003c/strong\u003e DW: Thanks Anne. We\u0026rsquo;ve done a lot and we still have a lot to do.\u003c/p\u003e\n\u003cp\u003eAnd I\u0026rsquo;d like to acknowledge that getting this far has been a really big team effort for us, and I appreciate how our team\u0026rsquo;s been able to put this work together.\u003c/p\u003e\n\u003cp\u003eThis is important because this process stuff is what everything else is built from. I think what we\u0026rsquo;re beginning to develop here is the nervous system for the design system, and perhaps, by extension, a nervous system for digital service practitioners across government — helping a complex system move with coordination and intention because we\u0026rsquo;ve connected activities and information from across the network.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 79:\u003c/strong\u003e We\u0026rsquo;re still working to take baby steps, but this is really what it\u0026rsquo;s all about when I think about the USWDS mission: Shaping the future of government digital services. This process of shaping is complex and interesting and can be really challenging and satisfying. And it\u0026rsquo;s something we can only effectively do together. And I know if we keep at it, there\u0026rsquo;s going to be an elephant in there… somewhere.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 80:\u003c/strong\u003e Q\u0026amp;A\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSlide 81:\u003c/strong\u003e Thanks for joining today’s USWDS monthly call. We\u0026rsquo;ll be back in March with a dev-focused call, about building new things with USWDS that feel like USWDS. It\u0026rsquo;ll be a nice follow-up from this call, as we start to think about how the component lifecycle moves from proposal to development!\u003c/p\u003e\n\u003cp\u003eIf you have a question we weren\u0026rsquo;t able to answer in the call, or thought of later, please head into our public Slack and ask it there. We\u0026rsquo;ll be around after the call to answer questions.\u003c/p\u003e\n\u003cp\u003eHave a great day and we\u0026rsquo;ll see you next month!\u003c/p\u003e\n\u003c/div\u003e\u003c/div\u003e\n\n\u003cp\u003eJoin the U.S. Web Design System (USWDS) team to learn more about the complete lifecycle of a USWDS component.\u003c/p\u003e\n\u003cp\u003eIn this session, you will learn:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eHow to suggest a new component\u003c/li\u003e\n\u003cli\u003eWhat to expect throughout the proposal process\u003c/li\u003e\n\u003cli\u003eWhat comes next in the component’s lifecycle\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eThis event is best suited for:\u003c/strong\u003e Developers and designers (all levels)\u003c/p\u003e\n\u003ch2 id=\"speakers\"\u003eSpeakers\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDan Williams\u003c/strong\u003e \u003cstrong\u003e—\u003c/strong\u003e Product Lead, USWDS\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAnne Petersen\u003c/strong\u003e \u003cstrong\u003e—\u003c/strong\u003e Experience Design Lead, USWDS\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAmy Leadem\u003c/strong\u003e \u003cstrong\u003e—\u003c/strong\u003e Developer, USWDS Contractor\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"join-our-communities-of-practice\"\u003eJoin our Communities of Practice\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://designsystem.digital.gov/about/community/\"\u003eUSWDS\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://www.section508.gov/manage/join-the-508-community/\"\u003eSection 508 IT Accessibility\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cem\u003eThis event is part of a monthly series that takes place on the third Thursday of each month. Don’t forget to set a placeholder on your personal calendar for our future events this year.\u003c/em\u003e\u003c/p\u003e\n\u003ch2 id=\"about-the-uswds\"\u003eAbout the USWDS\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"https://designsystem.digital.gov/\"\u003eThe U.S. Web Design System\u003c/a\u003e is a toolkit of principles, guidance, and code to help government teams design and build accessible, mobile-friendly websites backed by user research and modern best practices.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://designsystem.digital.gov/\"\u003eThe U.S. Web Design System\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/uswds/uswds/issues\"\u003eContribute on GitHub\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"mailto:uswds@support.digitalgov.gov\"\u003eEmail Us\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://digital.gov/communities/uswds/\"\u003eJoin our community\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://twitter.com/uswds\"\u003eFollow @uswds on Twitter\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n",
      "branch" : "bc-archive-content-3",
      "filename" :"2024-02-07-uswds-monthly-call-february-2024.md",
      
      "filepath" :"events/2024/02/2024-02-07-uswds-monthly-call-february-2024.md",
      "filepathURL" :"https://github.com/GSA/digitalgov.gov/blob/bc-archive-content-3/content/events/2024/02/2024-02-07-uswds-monthly-call-february-2024.md",
      "editpathURL" :"https://github.com/GSA/digitalgov.gov/edit/bc-archive-content-3/content/events/2024/02/2024-02-07-uswds-monthly-call-february-2024.md","slug" : "uswds-monthly-call-february-2024","url" : "/preview/gsa/digitalgov.gov/bc-archive-content-3/event/2024/02/15/uswds-monthly-call-february-2024/"
    }
  ]
}