Merge pull request #7 from github/fy27-h1-updates

Add event kit structure and update documentation

Author: katiesavage

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+This Code of Conduct addresses our standards and expectations for conduct within this repository.
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <opensource@github.com>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,36 @@
+## Contributing
+
+[fork]: https://github.com/github/dev-days/fork
+[pr]: https://github.com/github/dev-days/compare
+
+Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+
+Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
+
+Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
+
+## How to contribute
+
+If you've found a **bug** or have a **specific change request**, please open a **GitHub Issue** so it can be tracked and triaged properly.
+
+### Community expectations
+
+Please help keep this space welcoming and useful:
+- Follow the repository's [Code of Conduct](/CODE_OF_CONDUCT.md)
+- Be respectful and constructive
+- Stay on topic and relevant to this repository
+- Search existing issues before opening a new one
+- Avoid spam or unrelated promotional content
+
+### Security note
+
+Do **not** report security vulnerabilities in Issues or Pull Requests.
+Please follow the process outlined in `SECURITY.md` for responsible disclosure.
+
+Thanks for helping make Dev Days a great experience for organizers and developers worldwide!
+
+## Resources
+
+- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
+- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
+- [GitHub Help](https://help.github.com)

EVENT_CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# GitHub Event Code of Conduct
+
+This Code of Conduct addresses our standards and expectations for conduct at Dev Days events.
+
+## Code of Conduct
+
+By attending a GitHub event, including any of the events or activities organized by GitHub in association with the GitHub event (collectively the "Event"), you represent that you have read, understand, and agree to the following GitHub Event Code of Conduct (hereinafter "Code of Conduct"). This Code of Conduct applies to all attendees, speakers, exhibitors, sponsors, organizers, staff, and volunteers (collectively "Event Participants") at the Event.
+
+GitHub values the participation of all Event Participants and aims to create an event where all Event Participants have an enjoyable and fulfilling experience. Accordingly, all Event Participants are expected to show respect and courtesy to other Event Participants throughout the Event.
+
+GitHub is dedicated to providing a positive and harassment-free experience for everyone, regardless of age, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, ethnicity, race, religion, nationality, or level of experience.
+
+We do not tolerate harassment of Event Participants in any form, nor do we tolerate any behavior that would reasonably lead to an Event Participant being made to feel unsafe, insecure, or frightened for their physical or emotional well-being. All communication and behavior should be appropriate for a professional setting including people of many different backgrounds.
+
+Examples of encouraged behavior that contributes to a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for everyone at the Event
+- Showing empathy towards others and Event Participants
+
+Unacceptable behavior includes, but is not limited to:
+
+- The use of sexualized language or imagery
+- Inappropriate physical contact, sexual attention, or advances
+- Trolling, insulting or derogatory comments or behavior
+- Personal or political attacks toward Event Participants
+- Sustained disruption of talks or any other events or activities organized by GitHub in association with the Event
+- Intimidation, stalking, following, or harassing of Event Participants
+- Photography or recording of Event Participants without their consent
+- Harassment of any kind, even in a joking or ironic manner
+- Conduct which could reasonably be considered inappropriate in a professional setting
+- Each Event Participant is entirely responsible for their own actions.
+
+Thank you for helping to make this a welcoming, friendly space for all.
+
+## Reporting an incident
+
+If you are being harassed, notice that someone else is being harassed, have any other concerns, or if you believe an Event Participant is not acting in a way compliant with this Code of Conduct, please speak directly with a venue security officer or GitHub employee for urgent help, or email us at events@github.com for non-urgent issues. For life threatening situations, please dial emergency services immediately.
+
+GitHub employees will be happy to help Event Participants contact security or local law enforcement, escort to safety, or otherwise assist those experiencing harassment to feel safe for the duration of the Event.
+
+## Credit
+Portions of this Code of Conduct are based on the example anti-harassment policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers, under a Creative Commons Zero license.
+
+See the full Code of Conduct in the [GitHub Documentation](https://docs.github.com/site-policy/github-terms/github-event-code-of-conduct).

LICENSE

@@ -0,0 +1,21 @@
+    MIT License
+
+    Copyright GitHub, Inc.
+
+    Permission is hereby granted, free of charge, to any person obtaining a copy
+    of this software and associated documentation files (the "Software"), to deal
+    in the Software without restriction, including without limitation the rights
+    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+    copies of the Software, and to permit persons to whom the Software is
+    furnished to do so, subject to the following conditions:
+
+    The above copyright notice and this permission notice shall be included in all
+    copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+    SOFTWARE

README.md

@@ -1,69 +1,58 @@
-# GitHub Copilot Dev Days
+# Dev Days
 
-Landing page for **GitHub Copilot Dev Days** — a collection of hands-on workshops to master GitHub Copilot across every IDE, language, and workflow.
+> 🚨 **To run an official Dev Days event and receive program support, you must fill out the [event request form](https://gh.io/dev-days-2026) and receive approval from the Dev Days team**. 
+>
+> This repository contains the technical content, promotional materials, and organizer instruction for Dev Days event organizers. 
 
-🔗 **Live site:** [github.github.com/dev-days](https://github.github.com/dev-days/)
+**Dev Days** is a global, in-person user group initiative taking place from **September 1st to October 31st 2026**. The series brings together developers, enthusiasts, and local tech communities to explore the power of GitHub Copilot through practical, hands-on experiences.
 
-## Workshops
+Open to all developers, the events are led by local tech communities and designed to be highly practical. Each session runs for approximately **2-3 hours** and focuses on real-world workflows, hands-on activities, and workshops centered on AI-assisted coding with GitHub Copilot.
 
-> NOTE: The links below point to the old repository.
+## 🏙️ Find or Host an event in your city
 
-### VS Code — Agent Lab (Social Bingo)
+Find an event near you on our [Luma calendar](https://gh.io/dev-days/calendar).
 
-| Workshop | Stack | Duration |
-|----------|-------|----------|
-| [Agent Lab — Python](https://copilot-dev-days.github.io/agent-lab-python/) | Python + FastAPI + HTMX | ~1 hr |
-| [Agent Lab — TypeScript](https://copilot-dev-days.github.io/agent-lab-typescript/) | TypeScript + Vite + React | ~1 hr |
-| [Agent Lab — Java](https://copilot-dev-days.github.io/agent-lab-java/) | Java 21 + Spring Boot | ~1 hr |
-| [Agent Lab — .NET](https://copilot-dev-days.github.io/agent-lab-dotnet/) | .NET 10 + Blazor | ~1 hr |
+If you're a community leader and want to host a Dev Days event, this repository includes everything you need to plan, organize, and promote your event successfully.
 
-### VS Code — Specialized
+Want to organize a Dev Days event in your city? Fill in our [event request form](https://gh.io/dev-days-2026). 
+> Filling out the form does not guarantee your event will be accepted. Please await confirmation from our team before planning your event.
 
-| Workshop | Stack | Duration |
-|----------|-------|----------|
-| [Mona Mayhem — VS Code (Beginner)](https://copilot-dev-days.github.io/mona-mayhem/?track=vscode) | VS Code + Astro + TypeScript | ~60 min |
-| [App Modernization](https://copilot-dev-days.github.io/appmod-workshop-java/) | Java + Spring Boot Modernization | ~60 min |
+---
 
-### Terminal
+### 🗓️ Event formats
 
-| Workshop | Stack | Duration |
-|----------|-------|----------|
-| [Mona Mayhem — CLI (Beginner)](https://copilot-dev-days.github.io/mona-mayhem/?track=cli) | Terminal + Copilot CLI | ~60 min |
-| [Copilot CLI Workshop](https://copilot-dev-days.github.io/tailspin-toys-workshop/) | Terminal + AI-Powered Development | ~90 min |
+**Dev Days** are flexible - please tailor the format to fit your community! We recommend using one of the following **two formats**, depending on your community's experience, audience, **and available infrastructure**.
 
-### IDEs
+**1️⃣ Sessions-only format:** Focused on technical talks and demos around GitHub Copilot.
 
-| Workshop | Stack | Duration |
-|----------|-------|----------|
-| [Copilot for Visual Studio](https://copilot-dev-days.github.io/visual-studio-lab/) | Visual Studio + .NET 10 + Blazor | ~120 min |
-| [Copilot for JetBrains](https://copilot-dev-days.github.io/jetbrains-workshop/) | IntelliJ IDEA + Spring PetClinic | ~60 min |
-| [Copilot for Xcode](https://copilot-dev-days.github.io/xcode-workshop/) | Xcode + SwiftUI | ~60 min |
+**2️⃣ Sessions + Workshop format:** Combines technical sessions with a hands-on workshop for deeper, practical learning.
 
-## Prerequisites
+Both formats are designed to be interactive and hands-on, encouraging participants to learn by doing.
 
-- GitHub Account
-- GitHub Copilot License
-- Git installed
-- Your IDE of choice
+---
 
-## Development
+### 📚 Resources available
 
-This is a static site hosted on GitHub Pages. To run locally, serve the files with any static file server:
+ **👉 Send attendees to [github.github.com/dev-days](https://github.github.com/dev-days/)** — the central site where all Dev Days hands-on workshops are published. The site displays every available workshop option so attendees can easily find and follow the lab for your event.
 
-```sh
-# Example using Python
-python3 -m http.server
+| Topic                                      | Description                                                         | Resources                                |
+| :----------------------------------------- | :------------------------------------------------------------------ | :--------------------------------------- |
+| 📁 [**Organization Guide**](organization) | Practical guidance to plan and run your event from start to finish. | Event checklist, registration page draft |
+| 📁 [**Content - Organizer View**](content)                 | Technical content for sessions and workshops.                       | Presentation slides, hands-on labs       |
+| 📁 [**Content - Attendee View**](https://github.github.com/dev-days/)                 | Technical content for sessions and workshops.                       | Hands-on labs       |
+| 📁 [**Marketing**](marketing)       | Materials and templates to help you promote your event.             | Social media templates, event covers     |
 
-# Example using Node.js
-npx serve
-```
+## ❓ Questions
+Head to the [Issues](https://github.com/github/dev-days/issues) area in this repo to ask questions.
 
-## Links
+If you were already approved to organize an event, you will be added to a **Slack channel**. Here you can ask event-specific questions.
 
-- [GitHub Organization](https://github.com/copilot-dev-days)
-- [Copilot Docs](https://docs.github.com/en/copilot)
-- [Awesome Copilot](https://github.com/github/awesome-copilot)
+For more information about contributing to this repository, please read our [contributing guide](CONTRIBUTING.md).
 
----
+## Trademarks
 
-Built with 💜 by the GitHub Copilot Team
+This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft
+trademarks or logos is subject to and must follow
+[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
+Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
+Any use of third-party trademarks or logos are subject to those third-party's policies.

SECURITY.md

@@ -0,0 +1,31 @@
+Thanks for helping make GitHub safe for everyone.
+
+# Security
+
+GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub).
+
+Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. 
+
+## Reporting Security Issues
+
+If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
+
+**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
+
+Instead, please send an email to opensource-security[@]github.com.
+
+Please include as much of the information listed below as you can to help us better understand and resolve the issue:
+
+  * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+## Policy
+
+See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms)

SUPPORT.md

@@ -0,0 +1,14 @@
+# Support 
+
+## How to file issues and get help
+
+This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
+
+For help or questions about using this project, please create an issue.
+
+**dev-days** is under active development and maintained by GitHub staff. We will do our best to respond to support, feature requests, and community questions in a timely manner.
+
+
+## GitHub Support Policy
+
+Support for this project is limited to the resources listed above.