Set up new sections on homepage and topnav (#508)

* set up new sections on homepage and topnav

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* left align CTA text on desktop widths

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* Update menu order

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* navbar tweaks to accommodate more menu items

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* Tweaks to homepage layout

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* #507 Home page responsive update

Signed-off-by: James Hunt <10615884+thetwopct@users.noreply.github.com>

* fix background on navbar

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* fixed topnav at medium widths

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* Change mentorship link temporarily and remove topnav link

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>

* Add content to be able to switch to new homepage (#547)

* Move DHOH docs to the website

Signed-off-by: Ali Ok <aliok@redhat.com>

* Remove inline TOC in conference-best-practices doc

Signed-off-by: Ali Ok <aliok@redhat.com>

* Add WG page for d/hoh wg

Signed-off-by: Ali Ok <aliok@redhat.com>

* Revert the original docs, put "moved to" instructions in them

Signed-off-by: Ali Ok <aliok@redhat.com>

* Update tips-when-attending-or-speaking-at-a-conference.md

Signed-off-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>

* Add content from Catherine as is

Signed-off-by: Ali Ok <aliok@redhat.com>

* Add some links in accessibility home page

Signed-off-by: Ali Ok <aliok@redhat.com>

* Add introduction text in D/HoH home page

Signed-off-by: Ali Ok <aliok@redhat.com>

* Add reference to glossary in accessibility and d/hoh home pages

Signed-off-by: Ali Ok <aliok@redhat.com>

* Apply our template in accessibility directory and adapt pages to the template

Signed-off-by: Ali Ok <aliok@redhat.com>

* Update links to new D/HOH docs in repository

Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/accessibility/deaf-and-hard-of-hearing/_index.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>

---------

Signed-off-by: Ali Ok <aliok@redhat.com>
Signed-off-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

* Update website/content/accessibility/_index.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

* Update website/content/accessibility/deaf-and-hard-of-hearing/conference-best-practices.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

* Update website/content/accessibility/deaf-and-hard-of-hearing/tips-when-attending-or-speaking-at-a-conference.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

* Update website/content/about/working-groups/deaf-and-hard-of-hearing.md

Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>

---------

Signed-off-by: Chris Abraham <cjyabraham@gmail.com>
Signed-off-by: James Hunt <10615884+thetwopct@users.noreply.github.com>
Signed-off-by: Ali Ok <aliok@redhat.com>
Signed-off-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Signed-off-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>
Co-authored-by: James Hunt <10615884+thetwopct@users.noreply.github.com>
Co-authored-by: Ali Ok <aliok@redhat.com>
Co-authored-by: Catherine Paganini <74001907+CathPag@users.noreply.github.com>
Co-authored-by: Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com>
Co-authored-by: Emily Fox <33327273+TheFoxAtWork@users.noreply.github.com>

.gitignore

@@ -2,3 +2,4 @@
 public/
 website/resources/
 node_modules/
+.hugo_build.lock

deaf-and-hard-of-hearing/deaf-and-hard-of-hearing-individuals/tips-when-attending-or-speaking-at-a-conference.md

@@ -1,22 +1 @@
-# Tips when attending or speaking at a conference that doesn't provide proper accommodations
-
-Conference organizers don't always fully understand the needs of deaf and hard of hearing attendees or speakers. As a result, conferences tend to have little to no appropriate accommodations, creating a vicious cycle of fewer deaf and hard of hearing individuals attending and speaking at events.
-
-But to change that, you need to — not only show up — but also be transparent about your needs. As you will see, the lack of accommodations isn't ill-intended. It's just due to a lack of knowledge and, other times, a lack of funds to provide required accommodations. If we don't educate them, who will? To bring change, we all need to embrace **self-advocacy** and show up and speak up. 
-
-## Tips for Attendees
-
-1. **Ask for accommodations early**: The sooner organizers know your needs, the more time they have to prepare. Organizing a conference gets increasingly stressful the closer you are to the date, so provide ample time for them to do the research. 
-2. **Share what works for you with event organizers**: If you have been to another conference where something worked for you (captions on the phone, etc.), use it as a learning opportunity for organizers.
-
-## Tips for speakers
-
-1. **Be transparent and vocal about your needs**: Publicly talk about accommodations on social media or email by replying to all to help initiate conversations. Use the public channels as an opportunity to collaborate and foster good relationships, so offer a solution when you can.
-2. **Attend social events and make it clear if you are uncomfortable**: Let them know you are leaving a social event because you can't hear or communicate with other attendees. It's essential to make organizers aware of how this makes you feel. 
-3. **Don't hide your disappointment**: Don't be bitter, but don't hide your disappointment either. Be sure organizers know so they can do better next time. 
-4. **Use Google Slides' captions capability**: If the conference doesn't have captions, you can use Google Slides' captions capabilities. While they are far from great, they are better than no captions. 
-5. **Ask for a microphone for Q&A**: If you are hard of hearing, ensure there is a microphone for questions, and as a speaker, repeat the questions into your mic so the recording will pick up the vocals and captions will pick up the question.
-6. **Share your slide links beforehand or at the start of the presentation**: If you have speaker notes, this will help reinforce the content.
-7. **Be sure any videos or pre-recorded demos have captions**.
-
-There are many small things you can do to help bring change. While it might be frustrating and draining having to do that repeatedly, it is necessary if we want to change the status quo. Conference organizers want to welcome everyone but need to learn how. So don't be afraid to speak up. It's important for you and the next generation.
+This document has been moved to https://contribute.cncf.io/accessibility/deaf-and-hard-of-hearing/tips-when-attending-or-speaking-at-a-conference/

deaf-and-hard-of-hearing/event-organizers/conference-best-practices.md

@@ -1,151 +1 @@
-# Best practices for an inclusive and welcoming conference
-
-_This is a living document, so please be sure to check regularly for updates._
-
-If you're not familiar with the needs and preferences of deaf and hard of hearing (deaf/hoh) individuals, hosting a conference that is truly inclusive and accessible can feel overwhelming. This document will guide you to ensuring that deaf and hard of hearing attendees can fully participate in your event and have a great overall and complete experience.  
-
-The first step of being more inclusive is understanding that deaf/hoh are not a one-size-fits-all group — we have different needs and preferences, so it is important to provide multiple options for deaf/hoh. If we can't participate, we will likely not return, reinforcing the vicious cycle of deaf/hoh individuals not participating in the community.  
-
-We also recommend providing attendees, speakers, and sponsors the opportunity to specify their accessibility needs as soon as possible, so you can plan for it in advance. Use your website, registration and call for papers forms to get that information early. Conference organizers often don't budget for accessibility until a request is made. This can create uncomfortable situations for event planners who don't know how to budget for a sudden request. Accessibility is rarely a static budget line item, and it can be hard, especially when planning it for the first time. One of our aims in documenting best practices is to learn and share cost information to make planning more predictable.
-
-To make the process as straightforward as possible, we've listed as much as we could to make a conference truly inclusive to our community but also included alternatives if a particular accommodation is not feasible. If you have any questions or concerns, please get in touch with us at cncf-tag-contributor-strategy@lists.cncf.io. 
-
-In this document, we'll cover:
-
-- [DEIA: Diversity + Equity + Inclusion + Accessibility](#deia-diversity--equity--inclusion--accessibility)
-- [ADA coordinator/specialist role](#ada-coordinatorspecialist-role)
-- [Website, registration and CFP form, and program information](#website-registration-and-cfp-form-and-program-information)
-- [Pre-conference best practices](#pre-conference-best-practices)
-- [Day of best practices](#day-of-best-practices)
-    - [Reserved seating](#reserved-seating-at-the-front)
-    - [Sign language interpreters](#sign-language-interpreters)
-    - [Captions](#captions) 
-    - [Microphones for speakers and Q&A](#microphones-for-speakers-and-qa)
-    - [Meeting point area](#meeting-point-area)
-- [Conference networking opportunities](#conference-networking-opportunities)
-
-**Note**: This document is open source. If we missed anything, please submit a pull request or issue so we can update it — thank you! 
-
-## DEIA: Diversity + Equity + Inclusion + Accessibility
-
-We encourage you to include the A in your DEI efforts: **Diversity + Equity + Inclusion + Accessibility (DEIA)** — all too often is our community an afterthought. We want to change that and need your support!
-
-## ADA coordinator/specialist role
-
-We recommend appointing a designated Americans with Disabilities Act (ADA) coordinator to handle any prompt communications involving accommodations before and during the conference. This includes communication with attendees, speakers, facilities, and other event organizers.
-
-### Be ADA-compliant
-
-While nearly all buildings in the United States are ADA-compliant, we often see a gap at conferences: risers/stages generally don't have ramps, making them inaccessible for people with physical disabilities. Carpets make it harder for wheelchair users, physically and battery draining. Provide assistance when asked and have charging stations available.
-
-## Website, registration and CFP form, and program information
-
-### Event website
-
-On the registration and call for papers (CFP) pages, state that accommodations will be made for speakers and attendees with disabilities. Clearly and prominently stating that will make us feel welcome and motivate us to participate. Don't bury that important information in a registration form we might never see. Here's some suggested copy:
-
-> Interested in attending or speaking but require special accommodations? Please inform us through the registration or CFP form about your specific needs, and we will make every effort to provide the necessary support. For accommodation-related questions, please reach out to [accommodations@yourevent.com](mailto:accommodations@yourevent.com).
-
-Consider creating a dedicated email address (e.g., accommodations@) to signal you take this seriously.  
-
-### Registration and CFP form
-
-Include a field asking if accommodations are needed (yes/no) and a free-form text box to specify. Everyone's needs differ; it's hard to discern from a fixed form/dropdown.
-
-### Program Information
-
-On the program page, include session accessibility information, such as whether captioning will be provided and in which language. Also, mention that interpreters will be available upon request if requested in advance, and specify which sign language (e.g., American Sign Language, International Sign Language, etc.).  
-
-## Pre-conference best practices 
-
-### Reach out to attendees/speakers before the event
-
-* Set up notifications or monitor registration and CFP forms for accommodation needs and ask for clarification if needed.
-* Connect attendees with sign language interpreters to ensure they understand communication needs and style.
-* For dedicated interpreters (see the [sign language interpreters](#sign-language-interpreters) section), provide both sides with contact information to communicate directly during the event should they run late or if a meeting place changes.  
-
-### Connect us with our peers
-
-Provide a way for deaf and hard of hearing attendees and speakers or people with other disabilities to connect for peer support and potentially pool resources (e.g., an event Slack channel). 
-
-## Day of best practices
-
-Needs vary. Interpreters, captions, or both may be necessary for different individuals.
-
-### Reserved seating at the front
-
-Have some reserved seating at the front for deaf and hard of hearing attendees. Many rely on lip-reading, so you want to be sure they can see the speakers well. And please ask speakers not to wear masks while presenting and provide social distancing opportunities instead. 
-
-### Sign language interpreters
-
-Provide interpreters upon request and in advance. We also recommend having two sign language interpreters on-call to accommodate last-minute registrants or miscommunications. Ask interpreter agencies about their cancellation policies — these can vary significantly. A week's notice, 48, or even 24 hours with a fee, are all possible, depending on the agency. 
-
-Obviously, a big conference like KubeCon has more resources than a local community event — we get that. Since we also want to be included in smaller events, we'll offer various options. To be clear, the more cost-effective options aren't as inclusive, meaning we'll miss out on many opportunities our hearing peers benefit from. Do only go the more cost-effective route if the alternative is no accessibility. We deserve to be included and appreciate your support. 
-
-Sign language interpreters are the most valuable but also the most expensive accommodation. Incorporate the cost into the overall conference cost. It should be no different than including audio/video equipment, swag, food, refreshments, etc. into your budget. 
-
-#### Include interpreters in recording
-
-If you record your sessions, be sure the interpreters are on screen so deaf attendees can benefit from your accessibility effort even when watching them on-demand. 
-
-#### Global or national conferences 
-
-If you only have a few deaf individuals attending, provide two interpreters per individual (they always come in tandem for engagements longer than one hour). Wherever the deaf person goes, they'll follow. This will allow deaf individuals not only to attend sessions, but also network with their peers, walk the showfloor and talk with vendors. This is particularly important if they are the only or one of a few deaf people attending, as any interaction is contingent on the availability of an interpreter.
-
-Of course, this approach doesn't scale well. If you have more deaf attendees, you'll need to share accommodations among more individuals. 
-
-Before the conference, ask attendees to sign up for sessions in advance so you know which sessions must be staffed by interpreters. But allow for last-minute changes and be prepared to inform interpreters about these. While you'll want to plan ahead, you also want to offer attendees the flexibility to change their minds. Maybe they met someone who's giving a talk, and they'd like to attend that session. If you have multiple deaf attendees, have interpreters at keynotes by default. 
-
-##### Accommodation desk
-
-Set up an accommodation desk and/or communication channel where attendees can ask questions, request changes, or get an interpreter spontaneously, if available. Be sure to staff it with people familiar with deaf/hoh needs and have assistive technology available to assist with communication when needed.
-
-##### Networking events
-
-As mentioned in the [conference networking opportunities section](#conference-networking-opportunities) below, networking is one of the key reasons people attend conferences, so be sure interpreters are also available during networking sessions. 
-
-When it comes to networking events outside of the official program (e.g., sponsor happy hours), try to find a way to fund interpreters, too. If you can't use the conference budget, consider creating a sponsorship add-on to fund networking interpreter services. Don't underestimate the importance of these valuable opportunities. 
-
-#### Regional/single-track conferences 
-
-It's easier to share accommodations among speakers and attendees at smaller or single-track conferences. Provide live captions and a pair of sign language interpreters.
-
-If your budget is tight, consider offering an **accessibility sponsorship add-on** and mention throughout the conference that interpreters are made possible thanks to that company. That will motivate them or other companies to participate next time. 
-
-#### Local and community events
-
-For local and community events where attendance is free or low-cost, we recommend offering an accessibility sponsorship add-on (see prior section) to try to have interpreters on site. If that doesn't work, live captions are certainly the minimum you should offer. Be sure to let the deaf attendee know before the event that you couldn't raise funds for interpreters and that only captioning will be provided. Also, offer a refund if desired.
-
-You could also try to incentivize the employer of the deaf attendee to pay for the interpreters and offer to list them as an official event sponsor. 
-
-### Captions
-
-There is no need to provide interpreters for every session, but captions should be available for all sessions in order to give attendees the flexibility to join a session spontaneously. While there are lots of live captions software options, not all work well. Using a tool with low accuracy can be very confusing for deaf/hoh individuals, so select one that has proven to work for us.
-
-Keep in mind that, for a deaf person whose preferred form of communication is sign language, captions won't help when they want to ask a question or participate in a conversation with the speaker(s). You will need an interpreter to support interactions. 
-
-Some caption tools work for virtual events only, others for in-person and virtual. We've created a [list with different vendors](https://docs.google.com/document/d/13rYZIXMlMSpdbu2wYVzgShj7ZwiXEjOX5nwZLp0PV50/edit#heading=h.ngl0kcvzm9ym) for your convenience. 
-
-#### Caption use cases beyond deaf/hoh 
-
-Some attendees can hear but may be on the autism spectrum and have a hard time processing auditory cues — captioning is incredibly beneficial for them, too. Additionally, non-native speakers who aren't fluent can benefit from having words on the screen.
-
-### Microphones for speakers and Q&A
-
-Provide microphones for speakers and audience questions — even in small rooms. Hard of hearing attendees or speakers will struggle to hear the question without a microphone, and the captions tool won't be able to capture it either. If you can't provide a microphone for audience questions, have the speaker or someone else repeat the question in the microphone, "This person was asking …" 
-
-### Meeting point area 
-
-Especially at large conferences, if you have multiple deaf and hard of hearing attendees, create a meeting point area where deaf and hard of hearing attendees can find each other, meet with interpreters, and/or coordinate which session they will attend next if they share interpreters. 
-
-## Conference networking opportunities
-
-### Interpreters during networking sessions
-
-One of the main reasons people go to conferences is to network. That is no different for deaf and hard of hearing attendees. Yet, most conferences only provide support during sessions, denying us this important event aspect. 
-
-Networking is key for job opportunities, professional growth, and learning from peers. It is hard enough for people with disabilities to find or change jobs, making these networking events even more important. It is an important channel for professional growth and shouldn't be overlooked in your inclusion efforts. 
-
-Having the opportunity to network with hearing peers is not only important for the individual, it also helps break down prejudices and change attitudes towards us. These one-on-one connections are invaluable for fostering inclusion overall. So please be sure to allow your deaf and hard of hearing attendees and speakers to participate. 
-
-Thank you for taking the time to review our best practices recommendations. We hope this was useful and that you'll be able to implement them at your next event. If your conference is accessible to our community, please be sure to add it to this [accessible tech conference list](https://docs.google.com/spreadsheets/d/1kQmhwQc45S6SC2fYsULue4our72TLH86kVD5KA0EC-4/edit#gid=0) so more people from our community find out about it.
+This document has been moved to https://contribute.cncf.io/accessibility/deaf-and-hard-of-hearing/conference-best-practices/

website/.gitignore

@@ -1,3 +1,4 @@
 public/
 go.local.mod
 go.sum
+.hugo_build.lock