├── CNAME ├── assets ├── community_partners │ ├── placeholder.md │ └── escape.png ├── GraphQLConf │ ├── GraphQLCon_2023_1012_506_Newsletter.png │ ├── GraphQLCon_2023__670_300_Newsletter.png │ └── README.md └── media_partners │ ├── graphql-wtf │ ├── dark-icon.svg │ ├── pink-icon.svg │ ├── white-logo.svg │ └── pink-icon-white-text-logo.svg │ └── graphql_weekly │ └── pink-icon-white-text-log.svg ├── .gitignore ├── TWiG └── README.md ├── plans ├── graphqlconf_comms.md └── 2023_marketing.md ├── meetings ├── 2021-02-25.md └── 2021-01-28.md ├── src ├── css │ └── style.css ├── community-partners.html └── media-partners.html ├── graphqlconf ├── partners │ ├── community_appls │ │ ├── Nunya-Bidness.md │ │ └── template.md │ └── media_appls │ │ └── template.md ├── README.md └── partners.md ├── graph_traversal ├── README.md └── S1E1_prep_qs.md ├── .github └── ISSUE_TEMPLATE │ ├── suggest.yml │ └── bug.yml └── README.md /CNAME: -------------------------------------------------------------------------------- 1 | www.graphqlconf.dev -------------------------------------------------------------------------------- /assets/community_partners/placeholder.md: -------------------------------------------------------------------------------- 1 | # TODO add info here -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | ./*/.DS_Store 3 | ./*/*/.DS_Store 4 | ./*/*/*/.DS_Store -------------------------------------------------------------------------------- /TWiG/README.md: -------------------------------------------------------------------------------- 1 | # This Week in GraphQL 2 | 3 | ## The Official Newsletter of the GraphQL Foundation -------------------------------------------------------------------------------- /assets/community_partners/escape.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/marketing/main/assets/community_partners/escape.png -------------------------------------------------------------------------------- /assets/GraphQLConf/GraphQLCon_2023_1012_506_Newsletter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/marketing/main/assets/GraphQLConf/GraphQLCon_2023_1012_506_Newsletter.png -------------------------------------------------------------------------------- /assets/GraphQLConf/GraphQLCon_2023__670_300_Newsletter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/marketing/main/assets/GraphQLConf/GraphQLCon_2023__670_300_Newsletter.png -------------------------------------------------------------------------------- /plans/graphqlconf_comms.md: -------------------------------------------------------------------------------- 1 | Posted on Google Docs 2 | 3 | [Phase 1 GraphQLConf comms plan](https://docs.google.com/document/d/1xCH6fJgs4icD67r9KhtRc2yfmWrILABnDOqOlrCmtJg/edit#) 4 | 5 | 6 | 7 | -------------------------------------------------------------------------------- /meetings/2021-02-25.md: -------------------------------------------------------------------------------- 1 | # GraphQL Foundation Marketing Committee 2 | 3 | 4 | 5 | ### Attendees 6 | * ... 7 | 8 | ### Agenda (add items here) 9 | 10 | 1. Spec release 11 | 1. Annual report 12 | 1. Do we want to start migrating from foundation.graphql.org to graphql.org 13 | 14 | 15 | -------------------------------------------------------------------------------- /assets/media_partners/graphql-wtf/dark-icon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /assets/media_partners/graphql-wtf/pink-icon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /src/css/style.css: -------------------------------------------------------------------------------- 1 | * { 2 | font-family: 'Rubik', sans-serif; 3 | -webkit-text-size-adjust: 100%; 4 | background-color: #fff; 5 | color: #202020; 6 | font-size: 18px; 7 | font-weight: 300; 8 | line-height: 28.8px; 9 | margin: 14px; 10 | } 11 | 12 | button { 13 | background: #e10098!important; 14 | color: white; 15 | font-weight: 600; 16 | cursor: pointer; 17 | } 18 | 19 | .title { 20 | color:#e10098; 21 | } 22 | 23 | .error { 24 | color: rgb(247, 62, 62); 25 | font-size: 15px; 26 | } 27 | 28 | .counter{ 29 | font-size: 14px; 30 | font-weight: 400; 31 | } -------------------------------------------------------------------------------- /graphqlconf/partners/community_appls/Nunya-Bidness.md: -------------------------------------------------------------------------------- 1 | ## Application for GraphQLConf 2023 Community Partner 2 | --- 3 | **GraphQL Meetup Pro Network:** 4 | - [x] Yes: 5 | - [ ] No: 6 | 7 | **Full Name:** Nunya Bidness 8 | 9 | **Organization URL:** https://www.docdocgo.dev 10 | 11 | **Contact Person Name:** Doc Jones 12 | 13 | **Contact Email:** doc.jones@postman.com 14 | 15 | **Contact Phone Number:** 9194389115 16 | 17 | **Organization Description:** We meet and drink. 18 | 19 | **Proposed Partnership Activities:** Lots of drinking 20 | 21 | **Social Media Handles:** Twitter: mojosd 22 | Linkedin: doc-jones 23 | 24 | **Additional Comments:** The submit button is a lovely shade of pink 25 | 26 | --- 27 | 28 | -------------------------------------------------------------------------------- /graph_traversal/README.md: -------------------------------------------------------------------------------- 1 | # Graph Traversal 2 | 3 | ## The Official Live Stream from the GraphQL Foundation 4 | 5 | ### Purpose 6 | Graph Traversal aims to spread awareness about the GraphQL Foundation's work by featuring interviews, demos, and discussions with committee members and others from the broader ecosystem. We are exploring different methods of live streaming to promote various Foundation activities, such as GraphQLConf, TWiG, graphql.org, and the grants program. 7 | 8 | ### Tools 9 | We currently use restream.io for live streaming, which enables us to simultaneously broadcast on YouTube, Twitter, and LinkedIn. Additional platforms can be added if necessary. 10 | 11 | [LinkedIn recording](https://www.linkedin.com/video/live/urn:li:ugcPost:7051222661854593024) 12 | 13 | 14 | 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/suggest.yml: -------------------------------------------------------------------------------- 1 | name: suggest 2 | description: Make a suggestion for the marketing committee 3 | labels: ["Suggestion", "Needs Review", "From another committee"] 4 | 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: | 9 | ## Suggestion for improvement to a marketing or comms plan, program, etc. 10 | 11 | Thank you for making a suggestion! Please complete the following template and provide as much detail as possible. 12 | 13 | - type: checkboxes 14 | attributes: 15 | label: Is there an existing issue for this? 16 | description: Please search to see if an issue already exists for the suggestion you have. 17 | options: 18 | - label: I have searched existing issues 19 | validations: 20 | required: true 21 | 22 | - type: dropdown 23 | id: committee_choice 24 | attributes: 25 | label: If this suggestion is on behalf of another committee, which one? 26 | options: 27 | - GraphQLConf 28 | - TWiG 29 | - meetings 30 | 31 | - type: textarea 32 | attributes: 33 | label: Provide a detailed description of your suggestion for improvement(s). 34 | -------------------------------------------------------------------------------- /assets/GraphQLConf/README.md: -------------------------------------------------------------------------------- 1 | # GraphQLConf Brand Assets for use by Media and Community Partners 2 | 3 | This folder contains a collection of assets that can be used by community partners to promote events and activities on their Meetup pages, newsletters or other websites. 4 | 5 | ### Included Assets 6 | banner graphics 7 | TODO add more graphics types 8 | 9 | ### Usage Guidelines 10 | These assets are free to use for promotional purposes related to the community events and activities. However, please keep the following guidelines in mind: 11 | 12 | - Do not alter the design or layout of the assets in any way without prior approval. 13 | - Use the assets only for promoting community events and activities. 14 | - Do not use the assets in a way that may be considered harmful or offensive. 15 | - Do not use the assets to imply endorsement or sponsorship by the community unless explicitly authorized. 16 | 17 | ### How to Download 18 | To download an asset, simply click on its file name to open the file preview. From there, click the "Download" button in the upper right corner of the preview window to save the file to your device. 19 | 20 | ### Contact 21 | If you have any questions or concerns regarding the use of these assets, create an Issue in the marketing repository or contact [add email address here]() -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug.yml: -------------------------------------------------------------------------------- 1 | name: bug 2 | description: file a bug/issue 3 | title: "[BUG] " 4 | labels: [Bug, Needs Triage] 5 | 6 | body: 7 | - type: markdown 8 | attributes: 9 | value: | 10 | ## Bug Report 11 | 12 | Thank you for reporting a bug! Please fill out the following template to help us better understand the issue and resolve it as quickly as possible. 13 | 14 | - type: checkboxes 15 | attributes: 16 | label: Is there an existing issue for this? 17 | description: Please search to see if an issue already exists for the bug you found. 18 | options: 19 | - label: I have searched existing issues 20 | validations: 21 | required: true 22 | 23 | - type: input 24 | id: contact 25 | attributes: 26 | label: Contact Details 27 | description: How can we get in touch with you if we need more info? 28 | placeholder: ex. email@example.com 29 | validations: 30 | required: false 31 | 32 | - type: dropdown 33 | id: project_choice 34 | attributes: 35 | label: For which project are you reporting this bug? 36 | options: 37 | - GraphQLConf 38 | - TWiG 39 | - meetings 40 | - Graph Traversal 41 | - type: textarea 42 | attributes: 43 | label: Bug Description -------------------------------------------------------------------------------- /graphqlconf/README.md: -------------------------------------------------------------------------------- 1 | # DRAFT 2 | 3 | # GraphQL Foundation Inaugural Conference - GraphQLConf 2023 4 | 5 | Welcome to marketing committee repository for the GraphQL Foundation's inaugural conference, GraphQLConf! This is "The Official" conference organized by and for the GraphQL community. GraphQLConf aims to bring together developers, businesses, and enthusiasts from around the world to learn, share, and discuss the latest advancements and best practices in the GraphQL ecosystem. 6 | 7 | ## Marketing Committee Activities 8 | 9 | The marketing committee is dedicated to promoting and supporting the conference through various activities and with the support of the Linux Foundation, including: 10 | 11 | - Coorindating with the conference committee 12 | - Creating marketing materials and promotional assets 13 | - Planning and executing marketing campaigns 14 | - Recruiting and collaborating with partners 15 | - Partners include media partners and community partners 16 | - Others 17 | - Engaging with the community committee to increase awareness and recruit speakers and attendees 18 | - Coordinating with speakers and other stakeholders 19 | 20 | ## License 21 | 22 | All content in this repository is licensed under the [Creative Commons Attribution 4.0 International (CC BY 4.0) License](https://creativecommons.org/licenses/by/4.0/). 23 | -------------------------------------------------------------------------------- /graphqlconf/partners/community_appls/template.md: -------------------------------------------------------------------------------- 1 | ## Application for GraphQLConf 2023 Community Partner 2 | --- 3 | **GraphQL Meetup Pro Network:** 4 | - [x] Yes: 5 | - [ ] No: 6 | 7 | **Full Name:** Your Org Name 8 | 9 | **Organization URL:** https://example.com 10 | 11 | **Contact Person Name:** John Doe 12 | 13 | **Contact Email:** contact@example.com 14 | 15 | **Contact Phone Number:** +123456789 16 | 17 | **Organization Description:** Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 18 | 19 | **Proposed Partnership Activities:** Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 20 | 21 | **Social Media Handles:** Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 22 | 23 | **Additional Comments:** Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 24 | 25 | --- 26 | 27 | -------------------------------------------------------------------------------- /graphqlconf/partners.md: -------------------------------------------------------------------------------- 1 | # Media and Community Partner Program for GraphQLConf 2 | 3 | NOTE: The GraphQL Foundation Community Comittee will approve or offer change to the guidance below. WiP 4 | 5 | We are pleased to offer a Media and Community Partner Program for our upcoming GraphQLConf 2023. Our program is designed to provide benefits to media and community partners, while also ensuring that our conference is promoted in a positive and appropriate way. 6 | 7 | ## Benefits for Media Partners 8 | As a media partner, you will receive the following benefits: 9 | 10 | - Logo on our GraphQLConf 2023 event websites 11 | - 20% registration discount code for your readers/members 12 | - Complimentary media passes upon request 13 | - Recognition in GraphQL Foundation Newsletter 14 | - Promotion of partnership on social channels 15 | - Access and booking assistance with the event’s sponsors 16 | - Your company name and contact information to the event’s Diamond Sponsors 17 | 18 | ## Benefits for Community Partners 19 | As a community partner, you will receive the following benefits: 20 | 21 | - Logo on our GraphQLConf 2023 event website 22 | - Promotion of partnership on social channels 23 | - 20% registration discount code for your community 24 | - Collateral distribution on shared table in sponsor showcase 25 | - (1) Complimentary conference attendee pass 26 | 27 | ## Obligations for Media and Community Partners 28 | In exchange for these benefits, media and community partners are expected to fulfill the following obligations: 29 | 30 | - Promote the conference through your own media channels or community network 31 | - Include the conference logo and website URL in any promotional materials related to the conference 32 | - Follow conference media and social media guidelines, including not publishing or sharing any defamatory or inappropriate content related to the conference or its attendees 33 | - Attend the conference and actively engage with attendees and other partners 34 | - Provide feedback and suggestions for improvement of future conferences 35 | 36 | ## How to Apply 37 | To apply to become a media or community partner, please fill out the application form on the conference website. Applications will be reviewed on a rolling basis, and all applicants will be notified of their status within two weeks of submitting their application. 38 | 39 | Thank you for your interest in partnering with us for [GraphQLConf 2023](https://graphql.org/conf). We look forward to working with you to make our inaugural conference a success! 40 | 41 | 42 | 43 | 44 | 45 | 46 | -------------------------------------------------------------------------------- /graph_traversal/S1E1_prep_qs.md: -------------------------------------------------------------------------------- 1 | # GraphQL Traversal S1E1 2023 2 | 3 | ## Lee Byron 4 | ### What's New for the GraphQL Foundation in 2023 5 | 6 | ### Introductions 7 | 8 | - Can you begin by giving us a brief overview of GraphQL and its significance in the world of API development? 9 | - As one of the co-creators of GraphQL, how do you think it has evolved since its inception? What is driving its current accelerating adoption? 10 | - Can you tell us more about the GraphQL Foundation and its role in supporting the GraphQL community? 11 | ### GraphQL Foundation's New Projects for 2023 12 | - The GraphQL Foundation has some exciting new projects planned for 2023. Can you share some insights into these initiatives and how they will contribute to the growth and adoption of GraphQL? 13 | - How do you see the GraphQL Foundation's 2023 projects fostering innovation and collaboration within the GraphQL community? 14 | #### List of New Projects for 2023 15 | - For GraphQL Core and wgs 16 | - Next version of the Spec 17 | - Composite Schemas 18 | - ? 19 | - For the GraphQL Board 20 | - Subcommittees 21 | - Budget 22 | - Conference 23 | - Documentation 24 | - Community 25 | - Marketing 26 | - GraphQLConf 27 | - Announcement 28 | - Sponsorship 29 | - CFP 30 | ### GraphQLConf 2023 31 | - We've heard about the new conference, GraphQLConf, organized by the GraphQL Foundation. Can you give us a sneak peek into what attendees can expect at this event? 32 | - How do you think GraphQLConf will serve as a platform to bring together the GraphQL community and facilitate knowledge sharing around the Foundation's new projects for 2023? 33 | - What kind of presentations and discussions can attendees look forward to at GraphQLConf, and how were the topics selected to ensure a diverse and comprehensive program? How will you attract new presenters that we maybe haven't heard from before? 34 | - Are there any key themes or tracks at GraphQLConf related to the GraphQL Foundation's 2023 initiatives that you're particularly excited about, and why do you think they are essential for the GraphQL community to explore? 35 | ### Advice for Attendees and Presenters 36 | - How can developers, both experienced and new to GraphQL, benefit from attending GraphQLConf and engaging with the community while learning about the Foundation's new projects? 37 | - Can you share any advice for those who are considering submitting a talk for GraphQLConf, especially if their presentation relates to the GraphQL Foundation's 2023 projects, or for those attending the event for the first time? 38 | ### Engaging with the GraphQL Foundation 39 | - Lastly, how can organizations that are getting started with GraphQL or are currently supporting GraphQL implementations join the Foundation and contribute to these new projects? 40 | 41 | Thank you for sharing your thoughts on GraphQL, the GraphQL Foundation, its new projects for 2023, and the upcoming GraphQLConf. Thank you for your time, and we look forward to learning more from your insights and experiences. 42 | 43 | ### Q&A or No? 44 | 45 | 46 | 47 | -------------------------------------------------------------------------------- /graphqlconf/partners/media_appls/template.md: -------------------------------------------------------------------------------- 1 | ## Application for GraphQLConf 2023 Media Partner 2 | --- 3 | **Full Name:** John-Doe.md 4 | 5 | **Email Address:** example@example.com 6 | 7 | **Phone Number:** +123456789 8 | 9 | **Media Organization/Influencer Name:** John Doe Influencer 10 | 11 | **Website or Social Media Link(s):** https://example.com 12 | 13 | **Type of media platform (Select all that apply):** 14 | 15 | - [x] Blog 16 | - [ ] Podcast 17 | - [ ] YouTube Channel 18 | - [ ] News Website 19 | - [x] Magazine 20 | - [ ] Social Media (Twitter, Facebook, LinkedIn, Instagram, etc) 21 | - [ ] Other 22 | **Brief Description of your Media Platform:** "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 23 | 24 | **Audience Demographics and Reach (approximate numbers):** "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 25 | 26 | **Why do you want to become a media partner for GraphQLConf?:** "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 27 | 28 | **How do you plan to contribute to the conference and promote GraphQLConf through your platform?:** "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 29 | 30 | **Additional Comments or Questions:** "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum 31 | 32 | --- 33 | 34 | -------------------------------------------------------------------------------- /assets/media_partners/graphql-wtf/white-logo.svg: -------------------------------------------------------------------------------- 1 | <svg width="265" height="60" viewBox="0 0 265 60" fill="none" xmlns="http://www.w3.org/2000/svg"> 2 | <path d="M51.9615 15L38.9711 7.5L25.9808 0L0 15V45L25.9808 60L51.9615 45V30.0001L38.9711 22.5L51.9615 15ZM38.9711 37.5L25.9808 45L12.9904 37.5V22.5L25.9808 15L38.9711 22.5L25.9808 30L38.9711 37.5Z" fill="white"/> 3 | <path d="M82.7387 16.3477H87.8674V36.0797C87.8674 41.4433 84.2264 45.4367 77.9623 45.4367C71.6199 45.4367 68.8402 41.2084 68.527 37.9589H74.0864C74.3213 39.1334 75.2609 40.6603 78.0406 40.6603C80.8594 40.6603 82.308 39.0943 82.308 36.6669V33.8089C81.2509 35.2184 79.2151 36.4712 76.318 36.4712C70.602 36.4712 66.9609 31.8906 66.9609 26.1746C66.9609 20.4586 70.602 15.8779 76.318 15.8779C79.2151 15.8779 81.4467 16.9741 82.7387 18.8534V16.3477ZM77.4925 20.7718C74.517 20.7718 72.5203 22.9642 72.5203 26.1746C72.5203 29.3849 74.517 31.5774 77.4925 31.5774C80.4679 31.5774 82.4646 29.3849 82.4646 26.1746C82.4646 22.9642 80.4679 20.7718 77.4925 20.7718Z" fill="white"/> 4 | <path d="M103.001 21.3985C102.639 21.3289 102.273 21.2896 101.904 21.2811C98.655 21.2811 96.9715 22.8863 96.9715 26.6447V36.8631H91.4121V16.3481H96.5409V19.0103C97.2847 17.7967 98.8507 16.1523 102.335 16.1523C102.531 16.1523 103.001 16.1915 103.001 16.1915V21.3985Z" fill="white"/> 5 | <path d="M104.527 31.0292C104.527 27.4665 106.994 25.3524 112.475 24.4911L117.956 23.6689V23.4732C117.956 21.4765 116.703 20.4586 114.276 20.4586C111.692 20.4586 110.674 21.5548 110.478 22.9642H104.997C105.31 19.4015 107.738 15.8779 114.237 15.8779C120.266 15.8779 123.241 18.7359 123.241 23.5123V33.1825C123.241 34.5137 123.476 36.0405 123.829 36.8627H118.465C118.426 36.8627 118.23 35.9231 118.23 34.592C116.938 36.432 114.863 37.3325 111.731 37.3325C106.994 37.3325 104.527 34.7094 104.527 31.0292ZM113.023 28.4453C110.635 28.876 109.891 29.7373 109.891 30.8726C109.891 32.2821 110.752 33.0259 112.984 33.0259C116.233 33.0259 117.956 31.1467 117.956 28.4453V27.6231L113.023 28.4453Z" fill="white"/> 6 | <path d="M132.087 45.006H126.527V16.3477H131.656V18.8534C132.948 16.9741 135.258 15.8779 138.155 15.8779C144.106 15.8779 147.59 20.6543 147.59 26.6052C147.59 32.5561 144.106 37.3325 138.155 37.3325C135.258 37.3325 133.144 36.0797 132.087 34.6703V45.006ZM136.981 32.4387C140.073 32.4387 142.031 29.933 142.031 26.6052C142.031 23.2774 140.073 20.7718 136.981 20.7718C133.888 20.7718 131.93 23.2774 131.93 26.6052C131.93 29.933 133.888 32.4387 136.981 32.4387Z" fill="white"/> 7 | <path d="M155.55 18.2273C156.607 16.8179 158.564 15.8782 161.226 15.8782C166.159 15.8782 168.783 19.1669 168.783 24.0607V36.863H163.223V24.6872C163.223 22.299 162.205 20.6546 159.739 20.6546C157.037 20.6546 155.55 22.3381 155.55 25.157V36.863H149.99V7.5H155.55L155.55 18.2273Z" fill="white"/> 8 | <path d="M180.664 37.3325C174.713 37.3325 171.229 32.5561 171.229 26.6052C171.229 20.6543 174.713 15.8779 180.664 15.8779C183.561 15.8779 185.871 16.9741 187.163 18.8534V16.3477H192.292V45.006H186.732V34.6703C185.675 36.0797 183.561 37.3325 180.664 37.3325ZM181.838 20.7718C178.745 20.7718 176.788 23.2774 176.788 26.6052C176.788 29.933 178.745 32.4387 181.838 32.4387C184.931 32.4387 186.889 29.933 186.889 26.6052C186.889 23.2774 184.931 20.7718 181.838 20.7718Z" fill="white"/> 9 | <path d="M195.549 36.863V7.5H201.108V36.863H195.549Z" fill="white"/> 10 | <path d="M204.908 35.0624C204.908 33.8487 205.809 32.9482 207.061 32.9482C208.275 32.9482 209.215 33.8487 209.215 35.0624C209.215 36.3152 208.275 37.1765 207.061 37.1765C205.809 37.1765 204.908 36.3152 204.908 35.0624Z" fill="white"/> 11 | <path d="M223.042 20.4591H223.003L217.561 36.8632H214.664L207.773 16.9355H210.749L216.113 33.5746L221.594 16.9355H224.491L229.894 33.5746L235.336 16.9355H238.272L231.303 36.8632H228.406L223.042 20.4591Z" fill="white"/> 12 | <path d="M251.105 36.7459C251.105 36.7459 250.4 36.9416 248.991 36.9416C245.624 36.9416 243.823 35.1016 243.823 31.4997V19.2847H240.025V16.9356H243.823V11.2588H246.603V16.9356H251.183V19.2847H246.603V31.3039C246.603 33.4181 247.425 34.436 249.343 34.436C249.935 34.4253 250.525 34.3597 251.105 34.2402V36.7459Z" fill="white"/> 13 | <path d="M257.462 13.6462C257.462 9.45706 259.889 7.49953 263.374 7.49953C263.819 7.49498 264.263 7.52114 264.705 7.57783V10.1226C264.342 10.0641 263.976 10.0379 263.609 10.0443C261.455 10.0443 260.242 10.9839 260.242 13.5287V16.9348H264.744V19.2839H260.242V36.8625H257.462V19.2839H253.586V16.9348H257.462V13.6462Z" fill="white"/> 14 | </svg> 15 | -------------------------------------------------------------------------------- /assets/media_partners/graphql-wtf/pink-icon-white-text-logo.svg: -------------------------------------------------------------------------------- 1 | <svg width="266" height="60" viewBox="0 0 266 60" fill="none" xmlns="http://www.w3.org/2000/svg"> 2 | <g clip-path="url(#clip0_207_36)"> 3 | <path d="M52.5904 15L39.6001 7.5L26.6097 0L0.628906 15V45L26.6097 60L52.5905 45V30.0001L39.6001 22.5L52.5904 15ZM39.6001 37.5L26.6097 45L13.6193 37.5V22.5L26.6097 15L39.6001 22.5L26.6097 30L39.6001 37.5Z" fill="#ED1E79"/> 4 | <path d="M83.3675 16.3477H88.4962V36.0797C88.4962 41.4433 84.8552 45.4367 78.5911 45.4367C72.2487 45.4367 69.469 41.2084 69.1558 37.9589H74.7152C74.9501 39.1334 75.8897 40.6603 78.6694 40.6603C81.4883 40.6603 82.9368 39.0943 82.9368 36.6669V33.8089C81.8798 35.2184 79.8439 36.4712 76.9468 36.4712C71.2308 36.4712 67.5898 31.8906 67.5898 26.1746C67.5898 20.4586 71.2308 15.8779 76.9468 15.8779C79.8439 15.8779 82.0755 16.9741 83.3675 18.8534V16.3477ZM78.1213 20.7718C75.1459 20.7718 73.1492 22.9642 73.1492 26.1746C73.1492 29.3849 75.1459 31.5774 78.1213 31.5774C81.0968 31.5774 83.0934 29.3849 83.0934 26.1746C83.0934 22.9642 81.0968 20.7718 78.1213 20.7718Z" fill="white"/> 5 | <path d="M103.628 21.3985C103.266 21.3289 102.899 21.2896 102.531 21.2811C99.282 21.2811 97.5985 22.8863 97.5985 26.6447V36.8631H92.0391V16.3481H97.1679V19.0103C97.9117 17.7967 99.4778 16.1523 102.962 16.1523C103.158 16.1523 103.628 16.1915 103.628 16.1915V21.3985Z" fill="white"/> 6 | <path d="M105.154 31.0292C105.154 27.4665 107.621 25.3524 113.102 24.4911L118.583 23.6689V23.4732C118.583 21.4765 117.33 20.4585 114.903 20.4585C112.319 20.4585 111.301 21.5548 111.105 22.9642H105.624C105.937 19.4015 108.365 15.8779 114.864 15.8779C120.893 15.8779 123.868 18.7359 123.868 23.5123V33.1825C123.868 34.5136 124.103 36.0405 124.456 36.8627H119.092C119.053 36.8627 118.857 35.9231 118.857 34.5919C117.565 36.432 115.49 37.3325 112.358 37.3325C107.621 37.3325 105.154 34.7094 105.154 31.0292ZM113.65 28.4453C111.262 28.8759 110.518 29.7373 110.518 30.8726C110.518 32.2821 111.379 33.0259 113.611 33.0259C116.86 33.0259 118.583 31.1467 118.583 28.4453V27.6231L113.65 28.4453Z" fill="white"/> 7 | <path d="M132.714 45.006H127.154V16.3477H132.283V18.8534C133.575 16.9741 135.885 15.8779 138.782 15.8779C144.733 15.8779 148.217 20.6543 148.217 26.6052C148.217 32.5561 144.733 37.3325 138.782 37.3325C135.885 37.3325 133.771 36.0797 132.714 34.6703V45.006ZM137.608 32.4387C140.7 32.4387 142.658 29.933 142.658 26.6052C142.658 23.2774 140.7 20.7718 137.608 20.7718C134.515 20.7718 132.557 23.2774 132.557 26.6052C132.557 29.933 134.515 32.4387 137.608 32.4387Z" fill="white"/> 8 | <path d="M156.177 18.2273C157.234 16.8179 159.191 15.8782 161.853 15.8782C166.786 15.8782 169.41 19.1669 169.41 24.0607V36.863H163.85V24.6872C163.85 22.299 162.832 20.6546 160.366 20.6546C157.664 20.6546 156.177 22.3381 156.177 25.157V36.863H150.617V7.5H156.177V18.2273Z" fill="white"/> 9 | <path d="M181.291 37.3325C175.34 37.3325 171.855 32.5561 171.855 26.6052C171.855 20.6543 175.34 15.8779 181.291 15.8779C184.188 15.8779 186.498 16.9741 187.79 18.8534V16.3477H192.919V45.006H187.359V34.6703C186.302 36.0797 184.188 37.3325 181.291 37.3325ZM182.465 20.7718C179.372 20.7718 177.415 23.2774 177.415 26.6052C177.415 29.933 179.372 32.4387 182.465 32.4387C185.558 32.4387 187.516 29.933 187.516 26.6052C187.516 23.2774 185.558 20.7718 182.465 20.7718Z" fill="white"/> 10 | <path d="M196.178 36.863V7.5H201.737V36.863H196.178Z" fill="white"/> 11 | <path d="M205.535 35.0623C205.535 33.8486 206.436 32.9482 207.688 32.9482C208.902 32.9482 209.842 33.8486 209.842 35.0623C209.842 36.3151 208.902 37.1764 207.688 37.1764C206.436 37.1764 205.535 36.3151 205.535 35.0623Z" fill="white"/> 12 | <path d="M223.669 20.4591H223.63L218.188 36.8632H215.291L208.4 16.9355H211.376L216.739 33.5746L222.221 16.9355H225.118L230.521 33.5746L235.962 16.9355H238.899L231.93 36.8632H229.033L223.669 20.4591Z" fill="white"/> 13 | <path d="M251.734 36.7449C251.734 36.7449 251.029 36.9407 249.62 36.9407C246.253 36.9407 244.452 35.1006 244.452 31.4987V19.2837H240.654V16.9347H244.452V11.2578H247.232V16.9347H251.812V19.2837H247.232V31.303C247.232 33.4171 248.054 34.435 249.972 34.435C250.564 34.4243 251.154 34.3588 251.734 34.2393V36.7449Z" fill="white"/> 14 | <path d="M258.091 13.6472C258.091 9.45804 260.518 7.50051 264.003 7.50051C264.447 7.49596 264.892 7.52212 265.334 7.57881V10.1236C264.971 10.0651 264.604 10.0389 264.237 10.0453C262.084 10.0453 260.87 10.9849 260.87 13.5297V16.9358H265.373V19.2849H260.87V36.8635H258.091V19.2849H254.215V16.9358H258.091V13.6472Z" fill="white"/> 15 | </g> 16 | <defs> 17 | <clipPath id="clip0_207_36"> 18 | <rect width="266" height="60" fill="white"/> 19 | </clipPath> 20 | </defs> 21 | </svg> 22 | -------------------------------------------------------------------------------- /plans/2023_marketing.md: -------------------------------------------------------------------------------- 1 | # DRAFT 2 | 3 | # 2023 GraphQL Foundation Marketing Plan 4 | 5 | ## Executive Summary: 6 | GraphQLConf is an inaugural conference dedicated to bringing together professionals, enthusiasts, and thought leaders to explore the latest advancements, best practices, and innovative use cases in GraphQL technology. The marketing plan for GraphQLConf aims to build awareness, drive registrations, and attract high-quality speakers to create a memorable and impactful event. 7 | 8 | ## Marketing Objectives: 9 | 10 | - Build brand awareness and establish credibility for GraphQLConf within the tech community. 11 | - Attract at least 800 attendees and secure 25 industry-leading speakers. 12 | - Generate buzz and engagement on social media platforms. 13 | - Establish partnerships with relevant industry associations, media outlets, and complementary organizations. 14 | ### Target Audience: 15 | 16 | - GraphQL developers and engineers. 17 | - Tech professionals interested in adopting GraphQL technology. 18 | - Thought leaders and influencers in the GraphQL community. 19 | - Tech enthusiasts and students looking to learn more about GraphQL. 20 | ## Marketing Programs and Strategies: 21 | 22 | ### Content Marketing: 23 | - Publish blog posts, articles, podcasts, videos, and infographics related to GraphQL technology, conference themes, and speaker topics. 24 | - Share content across various platforms such as LinkedIn, Twitter, and tech forums to attract potential attendees and speakers. 25 | ### Social Media Marketing: 26 | - Create and maintain GraphQLConf's presence on Twitter, LinkedIn, Facebook, and Instagram. 27 | - Develop a unique hashtag (#GraphQLConf) to increase visibility and encourage user-generated content. 28 | - Share updates, early bird discounts, speaker announcements, and engaging content regularly. 29 | ### Influencer Marketing: 30 | - Partner with GraphQL influencers and thought leaders to promote the conference. 31 | - Feature guest blog posts, social media takeovers, and influencer interviews. 32 | - Invite influencers to participate as speakers and panelists. 33 | ### Email Marketing: 34 | - **This Week in GraphQL & GraphQL Weekly newsletters** 35 | - Launch targeted email campaigns to share conference updates, discounts, and speaker announcements. 36 | - Segment the email list based on interest, location, and past engagement to deliver personalized content. 37 | - Create an email drip campaign for nurturing leads and driving registrations. 38 | ### Paid Advertising: 39 | - Run targeted ads on platforms like Google Ads, Facebook Ads, LinkedIn Ads, and Twitter Ads. (Let's discuss which platforms to target) 40 | - Use retargeting strategies to re-engage website visitors and remind them about the conference. 41 | ### Public Relations: 42 | - Develop a PR strategy to secure media coverage and generate buzz around GraphQLConf. 43 | - Distribute press releases, pitch stories to relevant media outlets, and arrange interviews with keynote speakers and organizers. 44 | ### Live Stream Events: 45 | - **GraphQL Traversal** 46 | - Host virtual events to showcase conference highlights and introduce speakers. 47 | - Organize online workshops, panel discussions, and Q&A sessions related to GraphQL technology. 48 | ### Strategic Partnerships: 49 | - Collaborate with industry associations, media partners, and complementary businesses to extend the reach of GraphQLConf. 50 | - Offer co-branded content, reciprocal promotions, and exclusive discounts to each other's audiences. 51 | ### Search Engine Optimization (SEO): 52 | - Optimize the GraphQLConf website for search engines using relevant keywords, high-quality content, and authoritative backlinks. 53 | - Attendee and Speaker Testimonials: 54 | - Collect and feature testimonials from early registrants and confirmed speakers. 55 | - Share testimonials on the conference website and promotional materials to build credibility. 56 | ### Unique Value Proposition and Brand Identity: 57 | - Develop a strong brand identity for GraphQLConf, including a logo, color scheme, and design language. 58 | - Clearly communicate what sets GraphQLConf apart from other tech events, such as innovative session formats, renowned speakers, or cutting-edge topics. 59 | ### Incentives for Early Adopters and Local Communities: 60 | - Offer special discounts, exclusive content, or unique experiences for early registrants and speakers. 61 | - Engage with local tech communities and meetup groups to promote the conference and provide special deals for their members. 62 | ### Budget Allocation: 63 | 64 | - Streaming platform: $41/mo 65 | - MailChimp service: (may vary after launch ) 66 | - Paid Advertising: -------------------------------------------------------------------------------- /meetings/2021-01-28.md: -------------------------------------------------------------------------------- 1 | # GraphQL Foundation Marketing Committee 2 | 3 | 4 | 5 | ### Attendees 6 | * Lee Byron, GraphQL 7 | * Elise Greve, AWS 8 | * Eli Staykova, Apollo GraphQL 9 | * Uri Goldshtein, The Guild 10 | * Brian Warner, The Linux Foundation 11 | 12 | ### Agenda 13 | 14 | 1. Spec release 15 | - What do we need to prepare? 16 | - Where will we announce it? 17 | 2. Annual report 18 | - What can we do to get better participation? 19 | 3. Do we want to start migrating from foundation.graphql.org to graphql.org 20 | 21 | ## Spec release 22 | 23 | Discussion began on preparing for the upcoming spec release, which is planned around the end of February. Lee noted that he would like to see a coordinated effort to publish tweets and blog posts so there's a wide range of content that connects it all together. The goal is to have content from contributors as opposed to coming from the committee. 24 | 25 | Elise recommended ensuring we have a contributor point of view. Lee recommended proactive outreach. He noted that people who submit major changes are somewhat prepared already, because they're asked to write a blog post when they contribute. The goal of the blog post is to focus on why the change is needed. He noted the goal is to get these published in realtime as they're added. 26 | 27 | Lee also noted that many people follow along with the live spec, as opposed to the released spec. As such, the release is less a grand reveal than a celebration of the changes that happened over the past 18 months. He noted we can create a list of posts that have already been written, and then figure out if there's a gap. Elise noted this can also help inspire others to get involved. 28 | 29 | Brian asked if we know where there are gaps in coverage. Lee noted that it's still a work in progress, but there probably aren't that many gaps. He will know more once he's gathered the changelog. He noted it could be interesting to focus on the resolution of subtle ambiguities. These changes don't necessarily unlock a new thing, but they require a lot of work. This is an area that could use some attention because it's essential without being otherwise flashy, and could result in interesting stories. 30 | 31 | What are the steps between now and the release? 32 | 33 | * Create a tracking document for topics (Lee creating a change log, Brian will own tracking document) 34 | * Identify the topics and the best author (Lee and Uri) 35 | * Create a marketing point of contact for ensuring the topic is closed out 36 | * Collect the links 37 | * Any platform is ok, but we can offer space on the foundation site. 38 | 39 | Elise asked if we should suggest people volunteer their own unique stories? She noted there may be some things we aren't even aware of. Lee noted that this lines up exactly, and that this should be a topic in the next working group meeting. Uri suggested we can also ask people to highlight specific sections. Most non-contributors wouldn't read dig into specific sections without prompting. 40 | 41 | **Action:** Brian to add topic to the Working Group agenda: 42 | 43 | * What sorts of things we want people to submit: 44 | * Uri recommends soliciting content on specific sections that may not get a lot of attention 45 | * Elise recommends community perspectives, their unique point of view on GraphQL, how they use the spec and the community 46 | * Submit by sending to Brian to post on Foundation blog, or publish it yourself and send the link to operations@graphql.org 47 | * Where it would be used: 48 | * Narrative around the spec release, the annual report, social media, graphql websites) 49 | 50 | Ideas on how to use the content: 51 | 52 | * One centralized blog post from Lee as ED 53 | * Series of tweets and smaller posts that link off to content 54 | * Should use a few platforms (Facebook GraphQL group, Twitter, LinkedIn) 55 | * Short summary for LF Newsletter 56 | * Jason Perlow to write a narrative about GraphQL since contribution to the Foundation 57 | 58 | ## Annual report 59 | 60 | Brian reviewed the 2019 annual report. He noted this is a good source of content, but he needs help following up to get people to contribute. Consensus on splitting up the membership list and pursuing content contributions. 61 | 62 | **Action:** Brian to split up the membership list and provide a list of contacts in a tracking document so we can collect and assemble the content. 63 | 64 | **Action:** Create draft in Google Doc so we can drop in content. 65 | 66 | **Action:** Draft the ED report 67 | 68 | ## Consolidating website 69 | 70 | Brian next noted that GraphQL has two separate sites, graphql.org and foundation.graphql.org. He noted that he'd like to see about merging the two. Elise noted that if they have parallel purposes, it's probably better to just have one. 71 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Marketing - DRAFT 2 | 3 | The [GraphQL Foundation](https://graphq.org/foundation) Marketing Committee, reconstituted in January 2023, plays a crucial role in orchestrating and executing marketing initiatives in support of the Foundation and its various projects. As part of the GraphQL Foundation Board's efforts, the Marketing Committee collaborates with several other committees, all dedicated to working on new and exciting projects planned for this year. Announcements about these programs and projects will be released throughout 2023. 4 | 5 | This repository serves as a centralized platform for the marketing committee's efforts, including: 6 | 7 | ### Marketing Planning 8 | 9 | The [plans](https://github.com/graphql/marketing/tree/main/plans) directory contains documents and resources related to the overall marketing strategy and objectives for GraphQLConf. This includes target audiences, messaging, and channels. 10 | 11 | ### Artifacts 12 | 13 | The [assets](https://github.com/graphql/marketing/tree/main/assets) directory contains marketing artifacts, such as graphics, banners, social media images, and other promotional materials that can be used across various platforms and channels. 14 | 15 | ### Issues 16 | 17 | The [issues](https://github.com/graphql/marketing/issues) section of the repository is used for tracking tasks, requests, and discussions related to marketing activities. Committee members can create new issues, assign them to collaborators, and track their progress. 18 | 19 | ### Discussions 20 | 21 | The [discussions](https://github.com/graphql/marketing/discussions) section serves as a platform for open conversations, brainstorming sessions, and knowledge sharing among marketing committee members and other stakeholders. Topics can range from campaign ideas to feedback on promotional materials. 22 | 23 | ## GraphQL Foundation Marketing Plan 2023 24 | 25 | For an overview of the GraphQL Foundation's marketing strategy and objectives for 2023, please refer to the [GraphQL Foundation Marketing Plan 2023](https://github.com/graphql/marketing/blob/main/plans/2023_marketing.md) document. This is an initial draft plan and outlines the goals, target audiences, and initiatives for promoting and expanding the GraphQL ecosystem throughout the year. 26 | 27 | ## Contributing 28 | 29 | We welcome and appreciate contributions from the community! If you'd like to get involved with the marketing committee or have ideas to share, please feel free to open an issue, start a discussion, or submit a pull request. 30 | 31 | More details on new projects and programs for 2023 will be released soon. Watch this README for updates. 32 | 33 | The Marketing Committee maintains transparency in its operations, making meeting agendas and minutes openly accessible in the meetings/ directory. Once our regular meetings are scheduled, this README will be updated with the dates and times along with adding them to the [Foundation's public calendar](https://calendar.google.com/calendar/u/0/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8@group.calendar.google.com). 34 | 35 | ## Meetings 36 | 37 | | Meeting | Time | Host | 38 | | ---------- | -------- | -------- | 39 | | Marketing | Weekly Tue, 11:30am - 12:30pm EDT | Doc Jones | 40 | 41 | Check the meeting time in [your timezone](https://everytimezone.com/s/390feace) 42 | 43 | This will be the 1st meeting of the Marketing Committee. Meeting will recur on the same day/time until at least June 2023.Follow directions for attending. 44 | 45 | Meetings are typically scheduled at the times listed, however always check the agenda for the exact date and time of an upcoming meeting. Keep track of future upcoming meetings by subscribing to the Google Calendar or ical. 46 | 47 | Meeting transcripts and summaries will be captured by an automated note taker. Summaries will be made available in the meetings directory of this repository immediately following each meeting. 48 | 49 | # Contributing to this repo 50 | 51 | This repository is managed by EasyCLA. Project participants must sign the free [GraphQL Specification Membership agreement](https://preview-spec-membership.graphql.org) before making a contribution. You only need to do this one time, and it can be signed by [individual contributors](http://individual-spec-membership.graphql.org/) or their [employers](http://corporate-spec-membership.graphql.org/). 52 | 53 | To initiate the signature process please open a PR against this repo. The EasyCLA bot will block the merge if we still need a membership agreement from you. 54 | 55 | You can find [detailed information here](https://github.com/graphql/graphql-wg/tree/main/membership). If you have issues, please email [operations@graphql.org](mailto:operations@graphql.org). 56 | 57 | [https://calendar.google.com/calendar/u/0/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8@group.calendar.google.com]: https://calendar.google.com/calendar/u/0/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8@group.calendar.google.com 58 | -------------------------------------------------------------------------------- /src/community-partners.html: -------------------------------------------------------------------------------- 1 | <!DOCTYPE html> 2 | <html lang="en"> 3 | <head> 4 | <meta charset="UTF-8"> 5 | <meta http-equiv="X-UA-Compatible" content="IE=edge"> 6 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> 7 | <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/bulma/0.9.3/css/bulma.min.css" > 8 | <link rel="stylesheet" href="./css/style.css" > 9 | <link rel="preconnect" href="https://fonts.googleapis.com"> 10 | <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> 11 | <link href="https://fonts.googleapis.com/css2?family=Inter:wght@100;200;300&family=Rubik:wght@300&display=swap" rel="stylesheet"> 12 | <title>Apply to the GraphQLConf Community Partner Program 13 | 14 | 15 | 16 |
17 |
18 |

Apply to the GraphQLConf Community Partner Program

19 | 20 |

Thank you for your interest in becoming a community partner for GraphQLConf, a premier technology conference dedicated to GraphQL and related technologies. Community partners are essential for spreading the word about the conference and supporting our mission to bring together the global GraphQL community. Please fill out this form to apply as a community partner for GraphQLConf. We will review your application and get back to you as soon as possible.

21 |
22 |

Please indicate whether your organization is a member of the GraphQL Meetup Pro Network

23 |
24 | 25 |
26 | 27 |
28 | Yes
29 | No
30 | Please select an option. 31 |
32 |
33 |
34 | 35 |
36 |

Please provide the full name of your organization.

37 | 38 |
39 | 40 | Organization Name is required. 41 |
42 |
43 |
44 | 45 |
46 |

Please provide the URL of your organization’s website or Meetup page.

47 | 48 |
49 | 50 | Email Address is required. 51 |
52 |
53 |
54 | 55 |
56 |

Provide the full name of the primary contact person for your organization.

57 | 58 |
59 | 60 | Mobile Number is required. 61 |
62 |
63 |
64 | 65 |
66 |

Provide the email address of the primary contact person for your organization.

67 | 68 |
69 | 70 | Organization Name is required. 71 |
72 |
73 |
74 | 75 |
76 |

Provide the phone number of the primary contact person for your organization.

77 | 78 |
79 | 80 | Website or Meetup Page URL is required. 81 |
82 |
83 |
84 | 85 |
86 |

Please give a brief description of your organization, its mission, and its activities.

87 | 88 |
89 | 90 | Website or Meetup Page URL is required. 91 |
92 |
93 |
94 | 95 |
96 |

Please describe the activities and contributions your organization plans to make as a community partner for GraphQLConf. Examples include promoting the event, organizing local meetups or workshops, or providing resources to attendees.

97 | 98 |
99 | 100 | This field is required. 101 |
102 |
103 |
104 | 105 |
106 |

Please provide the social media handles for your organization on Twitter, Facebook, LinkedIn, Instagram, and any other relevant platforms.

107 | 108 |
109 | 110 | This field is required. 111 |
112 |
113 |
114 | 115 |
116 |

If you have any additional comments or information you would like to share, please provide them here.

117 | 118 |
119 | 120 | This field is required. 121 |
122 |
123 | 124 |
125 | 126 |
127 | 128 |
129 |
130 |
131 | 132 | 231 | -------------------------------------------------------------------------------- /src/media-partners.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | Apply to the GraphQLConf Media Partner Program 13 | 14 | 15 | 16 |
17 |
18 |

Apply to the GraphQLConf Media Partner Program

19 | 20 |

Welcome to the GraphQLConf Media Partners Application! We’re excited to collaborate with media organizations and influencers who share our passion for GraphQL and technology. Please fill out the form below to apply as a media partner for the upcoming GraphQLConf. We’ll review your application and get back to you as soon as possible.

21 |
22 | 23 |
24 | 25 |
26 | 27 | Full Name is required. 28 |
29 |
30 | 31 |
32 | 33 |
34 | 35 | Email is required. 36 |
37 |
38 | 39 |
40 | 41 |
42 | 43 | Phone Number is required. 44 |
45 |
46 | 47 |
48 | 49 |
50 | 51 | Media Organization/Influencer Name is required. 52 |
53 |
54 | 55 |
56 | 57 |
58 | 59 | Website or Social Media Link(s) is required. 60 |
61 |
62 | 63 |
64 | 65 |
66 | Blog
67 | Podcast
68 | YouTube Channel
69 | News Website
70 | Magazine
71 | Social Media (Twitter, Facebook, LinkedIn, Instagram, etc)
72 | Other
73 | Type of media platform is required. 74 |
75 |
76 | 77 |
78 | 79 |
80 | 81 |
82 | 83 | This field is required. 84 |
85 |
86 | 87 |
88 | 89 |
90 | 91 | This field is required. 92 |
93 |
94 | 95 |
96 | 97 |
98 | 99 | This field is required. 100 |
101 |
102 | 103 |
104 | 105 |
106 | 107 | This field is required. 108 |
109 |
110 | 111 |
112 | 113 |
114 | 115 | This field is required. 116 |
117 |
118 | 119 |
120 | 121 |
122 | 123 |
124 |
125 |
126 | 127 | 238 | -------------------------------------------------------------------------------- /assets/media_partners/graphql_weekly/pink-icon-white-text-log.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | --------------------------------------------------------------------------------