Merge pull request #990 from cagov/remove-forms

Remove forms

README.md

@@ -8,18 +8,13 @@ This project is currently in early beta status. It’s used in production on a f
 Part of our early beta includes learning and collaborating with teams. As the project matures we’ll share more details on how we might meld the design system components into the State template.
 
 ### Why a design system
-We built this to address common needs identified by California's Office of Digital Innovation (ODI) and the California Department of Technology (CDT) during development of <a href="https://alpha.ca.gov">alpha.ca.gov</a>, <a href="https://covid19.ca.gov">covid19.ca.gov</a>, <a href="https://cannabis.ca.gov">cannabis.ca.gov</a>, and <a href="https://drought.ca.gov">drought.ca.gov</a>.
+We built this to address common needs identified by California's Office of Digital Innovation (ODI) and the California Department of Technology (CDT) during development of <a href="https://alpha.ca.gov">alpha.ca.gov</a>, <a href="https://covid19.ca.gov">covid19.ca.gov</a> and <a href="https://cannabis.ca.gov">cannabis.ca.gov</a>.
 
 ### How we work
 We start by understanding the needs of residents of California through user research. We use an iterative design and development process to provide services that meet these needs. As we work, we continue to test our principles, designs, and components. We prioritize equity to some degree by ensuring that our code is accessible and performant for all devices and bandwidths. Components <a href="https://designsystem.webstandards.ca.gov/components/">pass through stages</a> of alpha, beta and production as they become available to the Design System.
 
 We work in the open: all our code and issue tracking is public. We’re happy to review pull requests from the public and state employees. Anyone can file an issue with bug reports and feature requests by selecting the **New issue** button from our <a href="https://github.com/cagov/design-system/issues">issues page</a>. You can see the prioritized list of issues we’re addressing on our <a href="https://github.com/orgs/cagov/projects/7">project board</a>.
 
-## Be a part of the Design System
-
-We’re looking for partners to share feedback and improve the Design System.
-
-Reach out to us through the <a href="https://designsystem.webstandards.ca.gov/">contact form</a> if you’d like to work with us. Or, participate through this GitHub repository.
 
 ## Development instructions
 

components/accordion/CHANGELOG.md

@@ -14,7 +14,7 @@
 * Make use of :defined to enhance design styles. This is available after the custom element's javascript has been executed.
 
 ### Upgrade notes 2.0.0
-* **Updated markup structure** please refer to the [README](components/accordion/README.md) for the latest markup  example. [See diff](https://github.com/cagov/design-system/pull/698/files#diff-24fcc3b7dc89f0002c127de7c93d334e359cff57a359d69d1a4a7c07002e4c9e) 
+* **Updated markup structure** please refer to the [README](https://github.com/cagov/design-system/blob/main/components/accordion/README.md) for the latest markup  example. [See diff](https://github.com/cagov/design-system/pull/698/files#diff-24fcc3b7dc89f0002c127de7c93d334e359cff57a359d69d1a4a7c07002e4c9e) 
 * When performing this component update, existing accordion markup content will need to be mapped to the new HTML structure in content. Any integrations will also need to update structure and content implementations. 
 
 ## 1.0.9

components/page-feedback/README.md

@@ -13,7 +13,7 @@ The page feedback component is intended to:
 
 ## When and how to use it
 
-We're still working on training and data services that supports the page feedback component. If you're interested in using page feedback, [reach out through the Contact us page](/contact-us). We'd like to hear more about your needs as we work on these services.
+We're still working on training and data services that supports the page feedback component. If you're interested in using page feedback, [reach out through our Contact us page](https://innovation.ca.gov/contact-us/). We'd like to hear more about your needs as we work on these services.
 
 ### How not to use it
 

components/site-navigation/README.md

@@ -365,7 +365,7 @@ Here is an abbreviated example of the data necessary to render this component wi
 | Cultivation                         | /licensees/cultivation/                                        | 20        | 2                | 0          | Drop down |
 | Manufacturing                       | /licensees/manufacturing/                                      | 20        | 2                | 1          | Drop down |
 
-For example, in the WordPress CMS integration, content editors can manage menu links through the normal menu system, and then [data](https://github.com/cagov/cannabis.ca.gov/blob/main/src/templates/wordpress/menu/headerMenu.json) is pulled from the WordPress menu system using an [API plugin](https://github.com/cagov/pantheon-mirror-cannabis-ca-gov/tree/main/wp-content/plugins/wp-rest-api-v2-menus) into a static site building website. This happens by way of GitHub, which acts as a local flat file JSON database for a static site generator (11ty). In the build process of the static site, we then use a [templating system](https://github.com/cagov/cannabis.ca.gov/blob/main/src/templates/_includes/nav-component.njk) to map the JSON data for the menu to the first two levels of the menu to the site navigation. Similar patterns can work for other publishing systems. If you are interested in helping, [reach out through our Contact us page](/contact-us).
+For example, in the WordPress CMS integration, content editors can manage menu links through the normal menu system, and then json is pulled from the WordPress menu system using an [API plugin](https://github.com/cagov/pantheon-mirror-cannabis-ca-gov/tree/main/wp-content/plugins/wp-rest-api-v2-menus) into a static site building website. This happens by way of GitHub, which acts as a local flat file JSON database for a static site generator (11ty). In the build process of the static site, we then use a [templating system](https://github.com/cagov/cannabis.ca.gov/blob/main/pages/_includes/site-navigation.njk) to map the JSON data for the menu to the first two levels of the menu to the site navigation. Similar patterns can work for other publishing systems.
 
 ## Contributor/developer documentation
 

components/statewide-header/README.md

@@ -11,7 +11,7 @@ It includes:
 
 The statewide header is a required Design System component. Place it at the top of the website, above the department branding (site header) and all other content.
 
-If you want to include a translation widget in the statewide header, [reach out through our Contact us page](/contact-us) to find out how you can do so.
+If you want to include a translation widget in the statewide header, [reach out through our Contact us page](https://innovation.ca.gov/contact-us/) to find out how you can do so.
 
 ### How not to use it
 

docs/pages/get-started.md

@@ -19,8 +19,4 @@ Get familiar with the [guidelines for content design](/style/content/).
 
 ## Everyone
 
-Everyone can benefit from the [Design System principles](/principles/). 
-
-## Need help getting started?
-
-[Reach out to us](/contact-us/). We’re available to help you figure out how you can get started, even if you do not have a digital team.
+Everyone can benefit from the [Design System principles](/principles/).

docs/pages/markdown.md

@@ -27,7 +27,7 @@ Here's the [full list of labels](https://github.com/highlightjs/highlight.js/blo
 
 ## Sprinkle with magic
 
-Inspired by the [MDJS plugin](https://rocket.modern-web.dev/docs/eleventy-plugins/mdjs-unified/), we've created a way to actually run these code blocks on the page. This allows us to both display the code and offer a preview for a given code block.
+Inspired by the [MDJS plugin](https://legacy.rocket.modern-web.dev/docs/eleventy-plugins/mdjs-unified/), we've created a way to actually run these code blocks on the page. This allows us to both display the code and offer a preview for a given code block.
 
 ### Javascript preview
 
@@ -113,4 +113,4 @@ Next, we'll display and insert the relevant HTML via the `preview` instruction.
 <p>Counter: <span id="count">0</span></p>
 
 <button id="add-one">Add one</button>
-```
+```

docs/pages/technical-approach.md

@@ -18,7 +18,6 @@ The Design System components are agnostic. You can choose to use an opinionated
 Right now, the Design System components are in use on pilot sites like:
 
 * [covid19.ca.gov](https://covid19.ca.gov/)
-* [drought.ca.gov](https://drought.ca.gov/)
 * [cannabis.ca.gov](https://cannabis.ca.gov/)
 
 There’s still a lot of work ahead to develop and refine the components, but we cannot do it in a vacuum. We need feedback from anyone that comes in contact with the components. 
@@ -31,8 +30,6 @@ Some things we want to include in our next phase are:
 * More robust accessibility testing
 * Standardized file names across components
 
-Learn how to [contribute or tell us your ideas](/contact-us/). 
-
 ## Component installation
 
 The Design System components are individual packages that you can download. Each component has README instructions for how to install it.

docs/pages/why-web-components.md

@@ -131,6 +131,5 @@ You can suggest changes or new components by opening issues in the <a href="http
   - <a href="https://ionicframework.com/blog/5-reasons-web-components-are-perfect-for-design-systems/">5 reasons web components are perfect for design systems</a>
   - <a href="https://vaadin.com/blog/design-systems-and-standardized-web-components">Design systems and standards based web components</a>
   - <a href="https://bradfrost.com/blog/link/why-we-use-web-components/">Why we use web components</a>
-  - <a href="https://www.zaplabs.com/blog/engineering/building-web-applications-longevity-through-web-components">Building web applications with longevity through web components</a>
   - <a href="https://shoelace.style/?id=new-to-web-components">New to web components?</a>
   - <a href="https://dev.to/open-wc/introducing-custom-elements-manifest-gkk ">Introducing: Custom Elements Manifest</a>

docs/site/_includes/site-footer.njk

@@ -10,7 +10,7 @@
 <script async defer src='https://www.google-analytics.com/analytics.js'></script>
 
 <!-- Google Analytics 4 Setup -->
-<script async src="https://www.googletagmanager.com/gtag/js?id=G-65PBRKRPK6"></script> 
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-65PBRKRPK6"></script>
 <script>
   window.dataLayer = window.dataLayer || [];
   function gtag(){dataLayer.push(arguments);}
@@ -20,15 +20,10 @@
   gtag('config', 'G-65PBRKRPK6'); // individual agency GA4 measurement ID
 </script>
 
-{% if page.url !== "/error.html" %}
-  <cagov-page-feedback class="cagov-mb-2 d-block"></cagov-page-feedback>
-{% endif %}
 
 <section aria-label="Site footer" class="site-footer">
   <div class="container">
-    <div class="footer-secondary-links">
-      <a href="/contact-us/">Contact us</a>
-    </div>
+
     <div class="footer-social-links">
       <a href="https://github.com/cagov/design-system">
         <span class="sr-only">GitHub</span>
@@ -68,4 +63,4 @@
       </a> #}
     </div>
   </div>
-</section>
+</section>

docs/site/_includes/site-navigation.njk

@@ -36,7 +36,7 @@
             <strong class="expanded-menu-section-header"><a class="expanded-menu-section-header-link js-event-hm-menu" href="/principles/">Principles</a></strong>
           </div>
         </div>
-        
+
         <div class="expanded-menu-col js-cagov-navoverlay-expandable">
           <div class="expanded-menu-section">
             <strong class="expanded-menu-section-header">
@@ -56,7 +56,7 @@
               </button>
             </strong>
             <div class="expanded-menu-dropdown" id="menu1-links">
-              <a class="expanded-menu-dropdown-link js-event-hm-menu" href="/style/content/" tabindex="-1">Content style guide</a>              
+              <a class="expanded-menu-dropdown-link js-event-hm-menu" href="/style/content/" tabindex="-1">Content style guide</a>
               <a class="expanded-menu-dropdown-link js-event-hm-menu" href="/style/design/" tabindex="-1">Design style guide</a>
               <a class="expanded-menu-dropdown-link js-event-hm-menu" href="/style/tokens/" tabindex="-1">Design tokens</a>
             </div>
@@ -82,25 +82,17 @@
               </button>
             </strong>
             <div class="expanded-menu-dropdown" id="menu2-links">
-              <a class="expanded-menu-dropdown-link js-event-hm-menu" href="/components/" tabindex="-1">All components</a>              
+              <a class="expanded-menu-dropdown-link js-event-hm-menu" href="/components/" tabindex="-1">All components</a>
               <a class="expanded-menu-dropdown-link js-event-hm-menu" href="/why-web-components/" tabindex="-1">Why web components</a>
             </div>
           </div>
         </div>
-        
+
         <div class="expanded-menu-col js-cagov-navoverlay-expandable">
           <div class="expanded-menu-section">
             <strong class="expanded-menu-section-header"><a class="expanded-menu-section-header-link js-event-hm-menu" href="/about/">About</a></strong>
           </div>
         </div>
-
-        {#
-        <div class="expanded-menu-col js-cagov-navoverlay-expandable">
-          <div class="expanded-menu-section">
-            <strong class="expanded-menu-section-header"><a class="expanded-menu-section-header-link js-event-hm-menu" href="/contact-us/">Support</a></strong>
-          </div>
-        </div>
-        #}
 
         {% if env.dev %}
           <div class="expanded-menu-col js-cagov-navoverlay-expandable">
@@ -132,4 +124,4 @@
       </div>
     </nav>
   </div>
-</cagov-site-navigation>
+</cagov-site-navigation>

docs/site/homepage.njk

@@ -124,23 +124,7 @@ description: This system makes it easy to build digital services that meet the n
     </article>
   </cagov-highlight-section>
 </div>
-<div class="full-bleed full-bleed--highlight2 p-y-3">
-  <div class="full-bleed-content-area--block">
-    <h2 class="d-block pt-1 mb-0">Be a part of the Design System</h2>
-  </div>
-  <div class="full-bleed-content-area contact-us">
-    <div class="contact-us-content homepage-form">
-      <p>We'd love to talk about how we can partner with you.</p>
-      <div class="contact-us-content-form">
-      {%- from "macros/design-system-form.njk" import designSystemContact -%}
-      {{ designSystemContact("Home page") }}
-      </div>
-    </div>
-    <div class="contact-us-image">
-      <img src="/img/partner-design-system.svg" alt="abstract orrery">
-    </div>
-  </div>
-</div>
+
 
 <h2 class="m-t-3">Who's using the Design System</h2>
 <div class="cagov-cluster-big-2">
@@ -151,7 +135,7 @@ description: This system makes it easy to build digital services that meet the n
     <div class="cagov-card-body pt-0">
       <h3>Department of Cannabis Control</h3>
       <p>This site is the first implementation of Design System components. It proved the design system model works for state departments.</p>
-      <p><a href="https://cannabis.ca.gov/" class="btn-primary-outline">Visit 
+      <p><a href="https://cannabis.ca.gov/" class="btn-primary-outline">Visit
       <span class="sr-only">Department of Cannabis Control</span>
       cannabis.ca.gov</a></p>
     </div>
@@ -163,7 +147,7 @@ description: This system makes it easy to build digital services that meet the n
     <div class="cagov-card-body pt-0">
       <h3>Broadband for All</h3>
       <p>The Design System allowed the Broadband for All team to plug-and-play with components on the homepage. With less time spent on engineering, the team could focus more on content and design.</p>
-      <p><a href="https://broadbandforall.cdt.ca.gov/" class="btn-primary-outline">Visit 
+      <p><a href="https://broadbandforall.cdt.ca.gov/" class="btn-primary-outline">Visit
       <span class="sr-only">Broadband for All</span>
       broadbandforall.cdt.ca.gov</a></p>
     </div>