Update README and FAQ for Dev Days events with presentation decks

FAQ.md

@@ -0,0 +1,179 @@
+# FAQ
+
+## What are Dev Days?
+
+Dev Days is a global series of community-led in-person events focused on product awareness and adoption of GitHub's key products, with a focus on the GitHub Copilot app and Copilot CLI.
+
+**Events run from September 1 through October 31, 2026.**
+
+## Who can organize a Dev Days event?
+
+Community leaders, GitHub Stars, MVPs, and other developers can organize Dev Days events. The program activates these community members to host and run events in their local areas.
+
+## Where do I go to manage my event?
+
+The program team will provide you with an event page on the Luma calendar based on the date provided when you signed up to host an event. From there, you can update the page details to make the most sense for your event.
+
+## Can I host multiple Dev Days events?
+
+Yes, you can host multiple events as long as they are for different audiences, dates, and/or in different cities.
+
+You will need to fill out one registration form for each event you plan to run.
+
+## There is already a Dev Days event in my city. Can I run another event?
+
+Yes, you can run an additional event in the same city if the events are sufficiently different.
+
+Questions to consider:
+
+- Do these events cover the same topics?
+- Do they reach the same audience? For example, you may plan to run an event specifically for your user group or school.
+- Are the event dates too close?
+
+If the events would be too similar, we suggest reaching out to collaborate with the existing event. If you have any questions about your prospective event, you can reach out to us for guidance.
+
+## How do attendees register for Dev Days events?
+
+Attendees can sign up using the shortlink: https://gh.io/join-dev-days, which will show them the full calendar.
+
+Registration details are managed through Luma.
+
+## Can I charge attendees to come to the event?
+
+No. Dev Days events must be free to attend. You may set a capacity limit to adhere to your venue's capacity limits.
+
+## How do I use the Dev Days content?
+
+### Core Content Session (Slide Deck)
+
+https://github.com/github/dev-days/blob/main/content
+
+You may choose to focus on the GitHub Copilot app or GitHub Copilot CLI for your event. The provided slide decks give a comprehensive, all-in-one resource covering the GitHub Copilot app or CLI.
+
+All available decks can also be found in the [Dev Days Presentation Decks release](https://github.com/github/dev-days/releases/tag/2026-07-30). 
+
+### Workshops
+
+In addition to the core talk, we recommend including one workshop:
+
+- Choose the workshop option that aligns with your selected topic and audience.
+- Workshops are designed to be hands-on and practical, reinforcing the concepts covered in the talk.
+- You do not need to run multiple workshops in a single event, but you can if you want.
+
+## What languages is the Dev Days content available in?
+
+All content is available in English.
+
+The GitHub Copilot app presentation deck, workshops, and train-the-trainer content are also available in Spanish, Portuguese, Chinese, and Korean.
+
+## What type of promotion will the Dev Days program do for events?
+
+Your event will be featured on the official Dev Days page, including your registration link.
+
+https://gh.io/dev-days/calendar
+
+The page is promoted across Microsoft and GitHub social media channels.
+
+## My community group uses a different registration platform (Meetup, Eventbrite, etc.). Can I use this platform for registration instead of Luma?
+
+Your primary registration page should be the one that we provide you on Luma. You may utilize other platforms to further promote the event, but attendees should register on the Luma page.
+
+## What Code of Conduct do I and my attendees need to follow during my Dev Days event and within the event repository?
+
+We have two Codes of Conduct related to the Dev Days series. Both can be found in the Dev Days repository.
+
+- **Contributor Covenant Code of Conduct**  
+  https://github.com/github/dev-days/blob/main/CODE_OF_CONDUCT.md  
+  Addresses standards and expectations for conduct within the repository.
+
+- **GitHub Event Code of Conduct**  
+  https://github.com/github/dev-days/blob/main/EVENT_CODE_OF_CONDUCT.md  
+  Addresses standards and expectations for conduct at Dev Days events.
+
+Ensure all attendees and organizers are aware of and agree to the Code of Conduct.
+
+# Coupon & Swag Questions 🛍️
+
+## How do I redeem my Copilot coupon to be able to host an event?
+
+The program team will reach out to determine if receiving a Copilot Max coupon makes sense for your event and coordinate any complexities if needed.
+
+## What would cause me to not be able to receive a Copilot Max coupon?
+
+- If you are a Microsoft/GitHub FTE, MVP, or GitHub Star, you should already be set up on the appropriate Copilot plans.
+- If you are not associated with any of those groups, we'll review your account to ensure there are no reasons we would be unable to provide a coupon (primarily if another coupon is already associated with your account).
+- If you already have a student or other coupon associated with your account, we recommend using a different account to run the workshop effectively.
+
+## What swag is provided for Dev Days events?
+
+Each event receives a swag kit including:
+
+- Copilot plushies (300 per event)
+- CLI and Copilot pins (3,000 total; 10 per event)
+- Sticker packs with both assorted GitHub stickers and Dev Days-specific stickers (300 of each per event)
+
+## I'm having issues with my swag package. What do I do?
+
+Please reach out to our swag partner at:
+
+github@succinctive.com
+
+Or contact the team through the Slack channel.
+
+# Reimbursement Questions 💰
+
+*F&B support is available and may be requested in the onboarding form.*
+
+## Key Requirements
+
+- You must pay for F&B upfront and submit a receipt for reimbursement.
+- Reimbursements are processed through Plain Sight, a Microsoft vendor.
+- Include your estimated number of attendees and total F&B cost in your event request.
+- Support is limited to **USD $400 per event**, on a first-come, first-served basis.
+- Expenses submitted without prior approval will not be reimbursed.
+
+## How long does it take for my invoice to be paid?
+
+You can expect to receive your payment request within 30 days.
+
+On average, payments are typically received within 10–15 business days after the invoice has been submitted, provided Plain Sight has received all required payment information.
+
+## What currency should I use in my invoice for reimbursement?
+
+You may request payment in USD or the currency used to pay for food and beverages.
+
+Plain Sight will pay you in your preferred currency, but be sure to indicate on your invoice which currency you are requesting.
+
+## Can the reimbursement be paid out to someone other than the community leader or point of contact?
+
+Yes. Please notify the Dev Days team if someone other than the point of contact will be reimbursed.
+
+Plain Sight will issue payment to the business or individual listed on your invoice, even if that person is not the point of contact for the event. Ensure payment details are accurately listed on the invoice.
+
+## What happens after I submit my reimbursement request?
+
+For those requesting payment via wire transfer, check, or ACH:
+
+1. Plain Sight will email you after reviewing your reimbursement request.
+2. You will receive a link to complete a one-time payment profile.
+3. The email link will come from **Rho Banking**, and the account name will be **Get to Work, Inc. d/b/a Plain Sight**.
+4. Complete the form with your payment details.
+5. Plain Sight will process and send your payment.
+
+## How do I check the status of my reimbursement?
+
+For questions or status updates regarding your reimbursement request, contact:
+
+deleon@plainsighthq.com
+
+## What counts as an itemized receipt?
+
+Please include receipts provided by the vendor(s) after purchasing food and beverages for the event.
+
+Receipts must:
+
+- Be actual receipts, not quotes.
+- Show the amount paid.
+- Include the items purchased.
+
+These receipts should be submitted as part of your post-event report.

content/README.md

@@ -1,24 +1,28 @@
 # 📚 Content
 
-This folder contains the **official content** for **Dev Days**, including presentation slides and hands-on labs.
+This folder contains the **official content** for **Dev Days**, including presentation slides and hands-on labs. See [📚 Core Content](#-core-content).
+
+The current round of Dev Days focuses on the **GitHub Copilot app**, the only desktop experience for agent-driven development built natively on GitHub. Alternatively, if your audience wants to focus on development tools in the Terminal, you may focus on the GitHub Copilot CLI.
 
 Dev Days events are flexible, so organizers should feel empowered to adjust the format based on the needs of their audience.
 
+> 🔎 **Highlight**
+> All workshop content is available at **[github.github.com/dev-days](https://github.github.com/dev-days/)**. This is the best link to share with attendees — it displays every available workshop option for Dev Days events so participants can navigate directly to the lab for your event.
+
 ## 🗓️ Sample Agenda (Session + Workshop)
 
-This is a suggested agenda for events following the **Sessions + Workshop** format
-(approximately **2-3 hours total**).
+This suggested event agenda includes one **Session** and one **Workshop** (approximately 2-3 hours total).
 
 | Order | Session            | Type         | Estimated Time | Description                                                                           |
 | ----: | ------------------ | ------------ | -------------- | ------------------------------------------------------------------------------------- |
-|    01 | **GitHub Copilot app: From issue to merge, in one app**   | Session      | 30–45 min      | The provided slide deck is an overview of the GitHub Copilot app.                |
+|    01 | **GitHub Copilot app**   | Session      | 30–45 min      | The provided slide deck is an overview of the GitHub Copilot app.                |
 |    02 | **Hands-on Lab**       | Hands-on Lab | 60 min         | Start using the GitHub Copilot app with guided, practical exercises.                                     |
 
-> This agenda combines **official content** and **hands-on practice** in a balanced format.
-
 ## 🔍 Prerequisites
 
 Dev Days events are open to developers of all experience levels. Different events may cover different topics that are more relevant for a subset of developers.
+> Note: While the GitHub Copilot app and CLI are available to users on all GitHub plans, workshop exercises will consume AI credits. We recommend keeping an eye on your credit usage before and during your event so you have enough available to fully participate in the hands-on activities.
+
 
 **For organizers**:
 
@@ -34,44 +38,34 @@ Dev Days events are open to developers of all experience levels. Different event
 
 - Install the [GitHub Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli) if your event includes the GitHub Copilot CLI session or workshop.
 
-- Install the [GitHub Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli)
-
 - Laptop — Required for events that include a hands-on workshop.
 
-## ✨ Dev Days – *Core Content Session*
-
-The current round of Dev Days focuses on the **GitHub Copilot app**, the only desktop experience for agent-driven development built natively on GitHub. 
+## 📚 Core Content
 
-Alternatively, if your audience wants to focus on development tools in the Terminal, you may focus on the GitHub Copilot CLI.
+For this round of Dev Days, you have two options for your event focus:
+1. **[Recommended] GitHub Copilot app**, the only desktop experience for agent-driven development built natively on GitHub. 
+2. **GitHub Copolot CLI**, Alternatively, if your audience wants to focus on development tools in the Terminal, you may focus on the GitHub Copilot CLI.
 
-*Every Dev Days session should include at least one of the following two presentations.*
+### ⭐ [Recommended] Option 1: GitHub Copilot app
 
-| Name | Type | Time | Description / Concepts Taught | Level |
-| ---- | ---- | ---- | ----------------------------- | ----- |
-| **⭐Recommended: GitHub Copilot app** | Session | ~30 min | The GitHub Copilot app is the only desktop experience for agent-driven development built natively on GitHub. | Beginner |
-| **GitHub Copilot CLI** | Session | ~30 min | GitHub Copilot CLI in the terminal and command-line workflows. | Beginner |
+The **GitHub Copilot app** is the only desktop experience for agent-driven development built natively on GitHub. 
 
-> Note: While the GitHub Copilot app is available to users on all GitHub plans, workshop exercises will consume AI credits. We recommend keeping an eye on your credit usage before and during your event so you have enough available to fully participate in the hands-on activities.
+| Name | Type | Time | Description / Concepts Taught | Level | Train the trainer |
+| ---- | ---- | ---- | ----------------------------- | ----- | ------ |
+| [⬇️**GitHub Copilot app**](https://github.com/github/dev-days/releases/download/2026-07-30/copilot-app-english.pptx) | Session/Talk | ~30 min | The GitHub Copilot app is the only desktop experience for agent-driven development built natively on GitHub. | Beginner | [English](https://www.youtube.com/live/SsFU0w3KrI4?si=M2yntYxNFM-U_LwP), [Spanish](https://www.youtube.com/live/PTBDlAa0_aM?si=i2jekaHzrVzZDx6T), [Portuguese](https://www.youtube.com/watch?v=O5ALS9rvTg8), [Korean](https://www.youtube.com/live/4ea0lmGXJiA?si=rrffYuhMdNlOuQFd), [Mandarin Chinese](https://www.bilibili.com/video/BV1T93v6VEca)
+| [**GitHub Copilot app Workshop**](https://github.github.com/dev-days/) | Hands-on Lab | ~1 - 1.5 hr | Scenario: Your team is adopting AI agents to work through a growing backlog. The Copilot app gives you one place to direct that work — picking up issues, running agents, reviewing changes, and merging pull requests. This lesson gets you installed, connected, and comfortable starting a conversation about your project. | Beginner |
 
-## 📚 Content Tracks - Workshops
+> The GitHub Copilot app presentation and workshop are available in multiple languages: 
+> Spanish ([⬇️presentation](https://github.com/github/dev-days/releases/download/2026-07-30/copilot-app-spanish.pptx), [workshop](https://github-samples.github.io/copilot-workshops/es-es/app/)), Portuguese ([⬇️presentation](https://github.com/github/dev-days/releases/download/2026-07-30/copilot-app-portuguese.pptx), [workshop](https://github-samples.github.io/copilot-workshops/pt-br/app/)), simplified Chinese ([⬇️presentation](https://github.com/github/dev-days/releases/download/2026-07-30/copilot-app-chinese.pptx), [workshop](https://github-samples.github.io/copilot-workshops/zh-cn/app/)),  Korean ([⬇️presentation](https://github.com/github/dev-days/releases/download/2026-07-30/copilot-app-korean.pptx), [workshop](https://github-samples.github.io/copilot-workshops/ko-kr/app/)).
 
-> 🔎 **Highlight**
-> All workshop content is available at **[github.github.com/dev-days](https://github.github.com/dev-days/)**. This is the best link to share with attendees — it displays every available workshop option for Dev Days events so participants can navigate directly to the lab for your event.
-
-There are two workshop topic options. The recommended option focuses on the GitHub Copilot app. Alternatively, you may use one of the workshops focused on the GitHub Copilot CLI.
-
-Each track includes the **Dev Days – Core Content Session** and one of the **hands-on workshops**.
-
-### ⭐ GitHub Copilot app
-
-| Name          | Type         | Time      | Description / Concepts Taught | Level         |
-| ------------- | ------------ | --------- | ----------------------------- | ------------- |
-| [**GitHub Copilot app Workshop**](https://github.github.com/dev-days/) | Hands-on Lab | ~1 - 1.5 hr | Your team is adopting AI agents to work through a growing backlog. The Copilot app gives you one place to direct that work — picking up issues, running agents, reviewing changes, and merging pull requests. This lesson gets you installed, connected, and comfortable starting a conversation about your project. | Beginner |
+### ⌨️ Option 2: GitHub Copilot CLI
 
-### ⌨️ GitHub Copilot CLI
+Copilot CLI is more than a chat interface. It’s an autonomous coding agent that can plan complex tasks, execute multistep workflows, edit files, run tests, and iterate until the job is done. 
+> There are two workshop topic options for the GitHub Copilot CLI. Choose the one that best suits your audience.
 
 | Name          | Type         | Time      | Description / Concepts Taught | Level         |
 | ------------- | ------------ | --------- | ----------------------------- | ------------- |
+| [⬇️**GitHub Copilot CLI**](https://github.com/github/dev-days/releases/download/2026-07-30/copilot-CLI.pptx) | Session/Talk | ~30 min | GitHub Copilot CLI in the terminal and command-line workflows. | Beginner |
 | [**GitHub Copilot CLI: Tailspin Toys Workshop**](https://github.github.com/dev-days/) | Hands-on Lab | ~2 hr | Master GitHub Copilot in the terminal with Tailspin Toys. Covers custom instructions, Copilot CLI setup, MCP servers, custom agents, and agent skills for AI-assisted delivery. | Intermediate |
 | [**GitHub Copilot CLI: Mona Mayhem Workshop**](https://github.github.com/dev-days/) | Hands-on Lab | ~1 hr | Build a retro arcade contribution-battle game while learning context engineering, Plan Mode, Agent Mode, multi-agent workflows, and design-first development in VS Code. | Intermediate |