├── .gitignore ├── LICENSE ├── README.md ├── archive ├── assets │ ├── README.md │ ├── companies.md │ ├── media-appearance.md │ ├── meili-love.md │ ├── meilisearch-aws.svg │ ├── meilisearch-dart.svg │ ├── meilisearch-digitalocean.svg │ ├── meilisearch-dotnet.svg │ ├── meilisearch-go.svg │ ├── meilisearch-icon.svg │ ├── meilisearch-java.svg │ ├── meilisearch-js.svg │ ├── meilisearch-kubernetes.svg │ ├── meilisearch-laravel-scout.svg │ ├── meilisearch-logo-blackbg.svg │ ├── meilisearch-logo.svg │ ├── meilisearch-php.svg │ ├── meilisearch-python.svg │ ├── meilisearch-rails.svg │ ├── meilisearch-react.svg │ ├── meilisearch-ruby.svg │ ├── meilisearch-rust.svg │ ├── meilisearch-signature.svg │ ├── meilisearch-swift.svg │ ├── meilisearch-symfony.svg │ ├── meilisearch-vue.svg │ ├── meilisearch-vuepress.svg │ ├── meilisearch-wordpress.svg │ ├── mentions.md │ └── styles.css ├── communication │ ├── post_forecast.md │ └── release_communication_process.md ├── events │ ├── carolina.md │ └── charlotte.md ├── guidelines │ ├── excerpt_guidelines.md │ ├── tag_guidelines.md │ └── url_guidelines.md ├── planning.md ├── planning │ ├── 2021-q1.md │ ├── 2021-q2.md │ └── 2021.md ├── processes │ ├── blog_process.md │ ├── blog_profile_creation.md │ ├── blog_publishing_process.md │ ├── posts_editorial_process.md │ ├── release_process.md │ └── releases.md └── readme.md ├── assets └── logos │ ├── dark-background │ ├── default │ │ ├── meilisearch-mono.svg │ │ └── meilisearch.svg │ ├── logomark │ │ ├── meilisearch-mono.svg │ │ └── meilisearch.svg │ ├── logotype │ │ └── meilisearch.svg │ └── vertical │ │ ├── meilisearch-mono.svg │ │ └── meilisearch.svg │ └── light-background │ ├── default │ ├── meilisearch-mono.svg │ └── meilisearch.svg │ ├── logomark │ ├── meilisearch-mono.svg │ └── meilisearch.svg │ ├── logotype │ └── meilisearch.svg │ └── vertical │ ├── meilisearch-mono.svg │ └── meilisearch.svg ├── communication ├── channel_mapping.md └── distribution_channels.md ├── devrel.md ├── events ├── conferences.md ├── speaker-template.md └── speaking.md ├── img ├── 3Cs.png ├── goals_2021.png └── lean_devrel.png ├── metrics.md └── opensource.md /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | This is free and unencumbered software released into the public domain. 2 | 3 | Anyone is free to copy, modify, publish, use, compile, sell, or 4 | distribute this software, either in source code form or as a compiled 5 | binary, for any purpose, commercial or non-commercial, and by any 6 | means. 7 | 8 | In jurisdictions that recognize copyright laws, the author or authors 9 | of this software dedicate any and all copyright interest in the 10 | software to the public domain. We make this dedication for the benefit 11 | of the public at large and to the detriment of our heirs and 12 | successors. We intend this dedication to be an overt act of 13 | relinquishment in perpetuity of all present and future rights to this 14 | software under copyright law. 15 | 16 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 17 | EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF 18 | MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 19 | IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR 20 | OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, 21 | ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR 22 | OTHER DEALINGS IN THE SOFTWARE. 23 | 24 | For more information, please refer to 25 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Developer Relations at Meilisearch 2 | We will slowly add all our processes in this repo. This is how we roll at Meilisearch, open source to the core! You can also have an idea of what the developer relations team is working on by checking the [devrel issues](https://github.com/meilisearch/devrel/issues) (for devrel tasks only). 3 | 4 | ## Our Mission 5 | We help developers be successful by nurturing a healthy and open-source community around Meilisearch. This means listening to, inspiring, educating, and supporting our community however we can. 6 | 7 | ## Table of Contents 8 | - [Assets](assets/logos/) 9 | - [3Cs](devrel.md#the-3cs) 10 | - [Activities](devrel.md#activities) 11 | - [Lean approach](devrel.md#lean-approach) 12 | - [Open source](opensource.md) 13 | - [Public speaking](events/speaking.md) 14 | -------------------------------------------------------------------------------- /archive/assets/README.md: -------------------------------------------------------------------------------- 1 | # Meilisearch Information & Assets 2 | 3 | ## Table of Contents 4 | - [Product Description](#product-description) 5 | - [Logos](#logos) 6 | - [Meilisearch Logos](#meilisearch) 7 | - [Software Developement Kits (SDKs)](#software-developement-kits-sdks) 8 | - [Framework Logos](#frameworks) 9 | - [Integrations Logos](#integrations) 10 | - [Cloud Logos](#cloud) 11 | - [Companies and organizations that use Meilisearch](companies.md) 12 | - [Love from our users](meili-love.md) 13 | - [Mentions of Meilisearch](mentions.md) 14 | ## Product Description 15 | 16 | ### Short 17 | Meilisearch is an open-source, blazingly fast, and hyper-relevant search engine. 18 | 19 | ### Long 20 | Meilisearch is an open-source search engine that offers a blazingly fast search-as-you-type experience for your website or application. It is designed to deliver relevant results right out of the box, while still offering multiple options for customization and fine-tuning. With SDKs for many popular web languages and frameworks, it's a breeze to integrate Meilisearch with the platform of your choice. 21 | 22 | ### Keywords 23 | Search Engine, Open Source, Rust, Fast 24 | 25 | ## Logos 26 | Find all the latest logos in [this folder](https://drive.google.com/drive/u/0/folders/16rWLOfDsEHe_h5uSqEOJcmGwK6MjpA8H). 27 | 28 | 29 | -------------------------------------------------------------------------------- /archive/assets/companies.md: -------------------------------------------------------------------------------- 1 | # Companies & Organizations using Meilisearch 2 | 3 | | Companies & Organizations| Description |How they use us |Source | 4 | |--|--|--|--| 5 | | [Aqua Security](https://avd.aquasec.com/) | Vulnerability database | Search by keyword or CVE-ID | [tweet](https://twitter.com/simarpreet7/status/1339365728894349312) | 6 | |[Beyond Code](https://beyondco.de/docs/expose/introduction)|Learning platform|Documentation search|[Marcel Pociot's website](https://pociot.dev/35-blazing-fast-search-with-meilisearch-and-laravel-forge)| 7 | |[Caroom](https://www.caroom.fr/)|Car comparison website|Car search|| 8 | |[Docxtemplater](https://docxtemplater.com/)|Create templates and generate some Word, Powerpoint and Excel documents from javascript objects or JSON|Site search (modules, documentation, faq)|| 9 | |[Hedira](https://www.hedira.io/)|Houseplant app that sends you tailored care reminders to your phone.|Plant search|[Meilisearch Community Slack](https://meilicommunity.slack.com/archives/C01F44SSCCA/p1606344526015300)| 10 | |[Juice Brothers](https://juicebro.com/en/products/drinks-en/juices-en/)|Juice Store|Meilisearch based filters on the PLP|[tweet](https://twitter.com/markdevri_es/status/1347178895271989250)| 11 | | [Platform.sh](https://docs.platform.sh/) | Platform-as-a-Service built especially for continuous deployment | Cross-site search | [tweet](https://twitter.com/robertDouglass/status/1262395403363921922) | 12 | |[Quasar](https://next.quasar.dev/)|MIT licensed open-source Vue.js based framework| Site search| [Meilisearch Community Slack](https://meilicommunity.slack.com/archives/C01F44SSCCA/p1614346362002000)| 13 | |[Ruby Toolbox](https://www.ruby-toolbox.com/)|Find actively maintained & popular open source software libraries for the Ruby programming language|Search for Ruby libraries|[official site](https://www.ruby-toolbox.com/blog/2021-03-19/search-speed-improvements)| 14 | |[Tauri App](https://tauri.studio/en/)|Toolkit to make applications for the major desktop platforms|Documentation search|[tweet](https://twitter.com/TauriApps/status/1361195976946577413)| 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /archive/assets/media-appearance.md: -------------------------------------------------------------------------------- 1 | # Meilisearch in the media 2 | 3 | |Date | Link | Description | 4 | |--|--|--| 5 | |2020/06/02| [Single and multi-site search with Meilisearch and Platform.sh](https://www.youtube.com/watch?v=KLZ5qZWcd5w) | Learn about how using Meilisearch not only improved the speed of Platform.sh search, but opened up cross-site search across all http://Platform.sh resource | 6 | |2020/10/22| [PEER LEARNING : apprendre grâce aux autres \| Way!](https://www.salesforce.com/fr/resources/way-tv/way-of-learning/peer_learning_apprendre_des_autres_sophie_vigier/) | **French**: 8'12'' Charlotte Vermandel aka [bidoubiwa](https://github.com/bidoubiwa), Software Engineer at Meilisearch, expains how she became a developer and her experience at 42 School 7 | |2021/02/05|[Meilisearch: the Future of Search Engines](https://www.youtube.com/watch?v=4aiUCYEOVgo)| Talk given by [CaroFG](https://github.com/CaroFG), Developer Advocate at Meilisearch, during 42 Entrepreneurs Hackathon: [Back to the living room 2](https://backtothelivingroom.tech/)| 8 | |2021/02/15|[Tech & Co by BFM Business](https://www.bfmtv.com/economie/replay-emissions/tech-and-co/tech-co-lundi-15-fevrier_VN-202102150483.html)|**French**: 27'12'' Learn about 42 school and how Charlotte Vermandel aka [bidoubiwa](https://github.com/bidoubiwa), Software Engineer at Meilisearch, became a developer and her experience at 42 School | 9 | |2021/02/16|[Introduction to Meilisearch \| Rawkode Live](https://www.youtube.com/watch?v=SJl2UWfy1nk)| David McKay aka [rawkode](https://github.com/rawkode) explores Meilisearch while chatting with [CaroFG](https://github.com/CaroFG) and [fharper](https://github.com/fharper)| 10 | |2021/04/13| ["Rust in Production: Meilisearch"](https://serokell.io/blog/rust-in-production-meilisearch) | Interview with Thomas Payet aka [tpayet](https://github.com/tpayet), co-founder and COO of Meili, about Meilisearch itself and how Rust and its ecosystem have helped create it 11 | |2021/05/13| ["Challenge accepted. with Thomas Payet, co-founder & COO at Meilisearch"](https://www.cto-cto.com/podcast/36-challenge-accepted-with-thomas-payet-co-founder-coo-at-meilisearch) | Interview with Thomas Payet aka [tpayet](https://github.com/tpayet), co-founder and COO of Meili by Piotr Karwatka for the CTO-CTO podcast series. 12 | |2021/05/14| ["Meilisearch, rustique à la française"](https://slash-podcast.fr/podcasts/meilisearch/) | Interview with Thomas Payet aka [tpayet](https://github.com/tpayet), co-founder and COO of Meili, and [Marin Postma](https://github.com/MarinPostma), core engineer at Meili, about Meilisearch and Rust. 13 | |2021/12/02| ["Interview of Quentin de Quelen - CEO of Meilisearch"](https://www.qovery.com/tech-story/interview/interview-of-quentin-de-quelen-ceo-of-meilisearch) | Qovery's interview of Quentin De Quelen, CEO and co-founder at Meilisearch - an open-source search engine written in Rust. 14 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-aws.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 | 29 | 30 | 31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-dart.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 | 29 | 30 | 31 | 32 | 33 | 34 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-digitalocean.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 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-go.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 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-icon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-java.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 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-js.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 | 29 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-laravel-scout.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 | 29 | 30 | 31 | 32 | 33 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-logo-blackbg.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 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-logo.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 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-php.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-python.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 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-rails.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 | 29 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-react.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 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-signature.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-swift.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 | 29 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-symfony.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-vue.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 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /archive/assets/meilisearch-wordpress.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 | 29 | -------------------------------------------------------------------------------- /archive/assets/styles.css: -------------------------------------------------------------------------------- 1 | img { 2 | height: 100px; 3 | } -------------------------------------------------------------------------------- /archive/communication/release_communication_process.md: -------------------------------------------------------------------------------- 1 | 2 | | Timestamp | Action | Stakeholder | 3 | |---|---|---| 4 | | 4 weeks before release | Meet with Guillaume to discuss new/improved features of next version. | [@Luna-meili](https://github.com/Luna-meili), [@CaroFG](https://github.com/CaroFG), [@Strift](https://github.com/Strift) | 5 | | 4 weeks before release | Choose which features to write about and who will write. | [@Luna-meili](https://github.com/Luna-meili), [@CaroFG](https://github.com/CaroFG), [@Strift](https://github.com/Strift) | 6 | | 4 weeks before release | Decide if we should do a demo, and if so, decide the topic. Discuss requirements with the [Integration](https://github.com/orgs/meilisearch/teams/integration-team) and [Cloud](https://github.com/orgs/meilisearch/teams/cloud-team) teams if needed. | [@CaroFG](https://github.com/CaroFG), [@Strift](https://github.com/Strift) | 7 | | 4 weeks before release | Create tmp-release channel on Slack for coordination | [@Luna-meili](https://github.com/Luna-meili) | 8 | | 4 weeks before release | Authors start working on their blog posts | [@Luna-meili](https://github.com/Luna-meili), [@CaroFG](https://github.com/CaroFG), [@Strift](https://github.com/Strift) | 9 | | 4 weeks before release | Content calendar to be written | [@Luna-meili](https://github.com/Luna-meili) | 10 | | 2 weeks before release | 1st mention on SoMe (Twitter, Discord, LinkedIn) about the week of release (no need to write a specific date) - Mondays 12 PM | [@Luna-meili](https://github.com/Luna-meili) | 11 | | 2 weeks before release | Potential new Newsletter outlining what to expect for the new release? (new instance, maybe a shorter one to tease the newest version) | [@Luna-meili](https://github.com/Luna-meili)| 12 | | 2 weeks before release | Blog posts need to be ready for editorial review (expert review needs to be over) | [@Luna-meili](https://github.com/Luna-meili), [@CaroFG](https://github.com/CaroFG), [@Strift](https://github.com/Strift) | 13 | | 1 weeks before release | 1 more mention of SoMe (Twitter, Discord, LinkedIn) about the release (hopefully sharing a date) - Mondays 12 PM | [@Luna-meili](https://github.com/Luna-meili) | 14 | | 1 weeks before release | Blog posts need to be ready for publication (editorial review already done by this point) | [@Luna-meili](https://github.com/Luna-meili) | 15 | | Day of release | SoMe (Twitter, Discord, LinkedIn) announcement + blog post on all the new changes as soon as we have the green light from the team (when the new Meilisearch version is out (all the assets and all the docker images) + documentation is deployed + PHP & JS SDKs are released) - Internal timeline to give everyone visibility on communication expectations | [@Luna-meili](https://github.com/Luna-meili), [@CaroFG](https://github.com/CaroFG) | 16 | | Post release | After the release, weekly blogposts about all the features that were implemented, no more than 1 / week about the new release so we can keep the momentum going for the next few weeks. Tuesdays can be blog posts release days (12PM) (Twitter, Discord, LinkedIn) | [@Luna-meili](https://github.com/Luna-meili), [@CaroFG](https://github.com/CaroFG), [@Strift](https://github.com/Strift) | 17 | | Post release | Wednesday can be new documentation highlight days (12PM) (Twitter, Discord, might be too technical for LinkedIn audience) | [@Luna-meili](https://github.com/Luna-meili) | 18 | | Post release | 2 weeks after the latest release, the latest edition of the newsletter goes out | [@Luna-meili](https://github.com/Luna-meili) | 19 | -------------------------------------------------------------------------------- /archive/events/carolina.md: -------------------------------------------------------------------------------- 1 | # Carolina Ferreira 2 | 3 | ![IMG-20190926-WA0000](https://user-images.githubusercontent.com/48251481/109692713-2071d880-7b89-11eb-94d5-444da042c88a.jpg) 4 | 5 | As a Developer Advocate, Carolina Ferreira helps developers have the best possible experience with the open-source search engine Meilisearch. A former teacher turned developer, Carolina brings her patience and experience in the classroom to her new role in the tech industry. She believes that success comes hand in hand with helping, sharing, and elevating others. 6 | 7 | ## Topics 8 | 9 | TBD 10 | 11 | ## Experience 12 | 13 | - [Rawkode Live](https://www.youtube.com/channel/UCrber_mFvp_FEF7D9u8PDEA) (2021/02/16) 14 | Introduction to Meilisearch 15 | https://www.youtube.com/watch?v=SJl2UWfy1nk 16 | 17 | - [Back to the living room hackathon](https://backtothelivingroom.tech/) (20201/02/05) 18 | Meilisearch: the future of search engines 19 | https://www.youtube.com/watch?v=4aiUCYEOVgo 20 | 21 | ## Links 22 | 23 | https://github.com/CaroFG 24 | https://www.linkedin.com/in/caro-fg/ 25 | https://twitter.com/CarolainFG 26 | 27 | 28 | ## Requirements 29 | 30 | - Your event is welcoming everyone, no matter where they come from, their social status, gender, orientation, beliefs, education and their mental or physical abilities; 31 | - Your conference provide access for wheelchair users and people with reduced mobility; 32 | - You have an enforced Code of Conduct (looking for one, check confcodeofconduct.com); 33 | - If you record my talk, the video needs to be accessible for free to everyone and cannot be sold in any capacity; 34 | - You want me to speak at your event because you find my content valuable for your attendees, not because you want my employer to sponsor your event. 35 | -------------------------------------------------------------------------------- /archive/events/charlotte.md: -------------------------------------------------------------------------------- 1 | # Charlotte 2 | 3 | Software engineer at Meilisearch. Loves Javascript/Typescript and creating a lot of usefull dev tools. 4 | Works in the integration team to helps developers use Meilisearch in all environments (not yet on mars though). 5 | 6 | ## Topics 7 | 8 | - Integrations helping Meilisearch. 9 | - Meilisearch philosophy and how we try to apply it in our products. 10 | 11 | ## Experience 12 | 13 | - April 2021 - [StrapiConf 2021: Integrate open-source search into your Strapi project](https://www.youtube.com/watch?v=brG3738V2bU) 14 | - June 2021 - [Strapi Webinar: Modern Search Solutions for the Jamstack with Meilisearch](https://www.youtube.com/watch?v=mO_I02ZAfmM) 15 | 16 | ## Links 17 | 18 | - [GitHub Page](https://github.com/bidoubiwa) 19 | 20 | ## Requirements 21 | 22 | - Water available 23 | -------------------------------------------------------------------------------- /archive/guidelines/excerpt_guidelines.md: -------------------------------------------------------------------------------- 1 | # Excerpt & metadata guidelines 2 | 3 | This document summarizes the SEO best practices for excerpts and meta descriptions. 4 | 5 | ## Definition & purpose 6 | 7 | The excerpt and the meta description summarizes a post's content. 8 | 9 | Excerpts will show at the top of the post, and on the blog index page. Ideally, your excerpt should flow into your first paragraph nicely. 10 | 11 | Meta descriptions will be displayed in the search results of web search engines. It’s one of the first things people will likely see when searching for something. 12 | 13 | Because they serve the same purpose, the text of both can be the same and follow the same guidelines. 14 | 15 | 16 | ## Best practices 17 | - **Keep it under 155 characters**: it shouldn't take more than 2 or 3 lines in the blog's index page. Also, longer descriptions will be truncated in search results 18 | - **Use an active voice**: it's more readable and engaging 19 | - **Make it unique**: create descriptions that accurately describe the specific post 20 | - **Use your main keyword**: if the search keyword matches a part of the description, Google will highlight it in the search results. 21 | -------------------------------------------------------------------------------- /archive/guidelines/tag_guidelines.md: -------------------------------------------------------------------------------- 1 | # Blog tag guidelines 2 | 3 | A blog tag is a word or phrase that describes what your post is about. 4 | 5 | Use preferably only one tag per post. 6 | 7 | To make tag suggestions, please [create an issue](https://github.com/meilisearch/devrel/issues/new) or contact the Developer Relations team. 8 | 9 | ## List of tags & description 10 | 11 | - `community`: hacktoberfest, events, and community-related content 12 | - `company-news`: company announcements 13 | - `engineering`: tehcnical content not related to using Meilisearch 14 | - `future-of-work`: HR & employee experience 15 | - `meet-the-team`: series of interviews with Meilisearch employees 16 | - `release`: main changes introduced by new Meilisearch versions 17 | - `state-of-search`: search experience 18 | - `using-meilisearch`: tutorials, guides and posts about demos 19 | - `customers`: customers and users of Meilisearch 20 | -------------------------------------------------------------------------------- /archive/guidelines/url_guidelines.md: -------------------------------------------------------------------------------- 1 | # URL guidelines 2 | 3 | This document summarizes the SEO best practices for URLs. 4 | 5 | 👉 The URL should state clearly what is on the page. 6 | 7 | ## DOs 8 | 9 | - Keep it simple and descriptive 10 | - Readable 11 | - Include [keywords](https://en.wikipedia.org/wiki/Index_term) 12 | - Short: around 3 to 5 words 13 | 14 | ## DON'Ts 15 | 16 | - Avoid using a year: to easily update the content and keep the ranking the page has earned 17 | - Avoid having similar URLs slugs: search engine crawlers might think there's content duplication 18 | - Don't use non-ASCII characters like emojis 19 | 20 | ## Resources 21 | 22 | - [A Guide to SEO-Friendly URL Structures and Parameters: The Basics](https://www.semrush.com/blog/on-page-seo-basics-urls/) 23 | - [What Is a Slug? URL Slugs and Why They Matter for SEO](https://www.semrush.com/blog/what-is-a-url-slug/) 24 | - [Google Search Central: Keep a simple URL structure](https://developers.google.com/search/docs/crawling-indexing/url-structure?hl=en) 25 | -------------------------------------------------------------------------------- /archive/planning.md: -------------------------------------------------------------------------------- 1 | **As of December 2021, this content is deprecated and saved here as a reference** 2 | 3 | --- 4 | 5 | # Developer Relations Planning & Goals 6 | 7 | - [Planning Processes](#planning-processes) 8 | - [KPIs](#kpis) 9 | - [2021 Goals](planning/2021.md) 10 | 11 | ## KPIs 12 | 13 | List of KPIs (Key Performance Indicators) we will track to see if we are going in the right direction. 14 | 15 | ### First tier 16 | - [Blog](https://blog.meilisearch.com/): average time spent 17 | - Discourse (now [GitHub Discussions](https://github.com/orgs/meilisearch/discussions)): time to first reply 18 | - [Documentation](https://docs.meilisearch.com/): unique visitors & total views 19 | - [Github](https://github.com/meilisearch): quality PRs & time to first reply on issues 20 | - NPS: score 21 | - [Slack](https://meilicommunity.slack.com/): engagement 22 | - [YouTube](https://www.youtube.com/channel/UCgXns0g3w8NfMzjx1AvVKwA/): subscribers & video consumption time 23 | 24 | ### Second tier 25 | - [Blog](https://blog.meilisearch.com/): unique visitors 26 | - Discourse (now [GitHub Discussions](https://github.com/orgs/meilisearch/discussions)): users 27 | - [GitHub](https://github.com/meilisearch): project stars 28 | - NPS: number of participants 29 | - [Slack](https://meilicommunity.slack.com/): members 30 | - [Twitter](https://twitter.com/meilisearch/): engagements 31 | 32 | ### Third tier 33 | - [Instagram](https://www.instagram.com/meilisearch/): followers & engagements 34 | - [LinkedIn](https://www.linkedin.com/company/meilisearch): followers & engagements 35 | - [Twitter](https://twitter.com/meilisearch/): followers 36 | 37 | ## Planning Processes 38 | Once the yearly goals are defined for our team (need to add the process for that), we need to each quarter. We decided as a company to plan one quarter in detail at the time, which means that for January 1st, only Q1 plan is detailed. To ensure a healthy and participative team culture, our director decided to make planning a team exercise: with some initial guidance based on the team's vision and company culture, we defined our different goals and how we will measure the team together. 39 | 40 | ### 3 Weeks Prior 41 | Even if the quarter is not done yet, we should have a pretty good idea on how it went, and what we will achieve by the end. We schedule a one-hour meeting for a team retrospective about the last quarter. Each team member prepared themselves by reflecting on the last three months: 42 | - What did we do that were successful, that we are proud of? 43 | - Is there anything we should stop doing or change to make us more efficient, effective and happy? 44 | - Did we plan our tasks correctly? If not, what changed? 45 | - Are our estimation close enough? If not, how can we better estimate our team's velocity? 46 | - Anything else that is worth discussing that will move the team in two important directions: 47 | 1. deliver better quality impactful results; 48 | 2. grow the team happiness level. 49 | 50 | Nothing is insignificant. Everything that can improve those points are worth discussing. There is nothing stupid, as long as it's constructive. If there is a sensitive topic you would prefer not to share in a team setting, please discuss with [@fharper](https://github.com/fharper) directly prior to this meeting. This is **not** a meeting for pointing fingers: if there is a productivity challenge with one or more of your coworkers, [@fharper](https://github.com/fharper) will handle those with the individuals directly. 51 | 52 | After the discussions, [@fharper](https://github.com/fharper) will add a summary of the discussions in the `planning/YYYY-Q#.md` file. 53 | 54 | Before next week, [@fharper](https://github.com/fharper) will share with the team his vision for what should be prioritized, if any, during the next quarter so all members will have this information to help them prepare for the meeting the week after. 55 | 56 | To ensure the process takes as less time as possible, our issues in the repositories we own should **always** be up to date. 57 | 58 | ### 2 Weeks Prior 59 | We schedule a one-hour meeting for a team brainstorming about the next quarter: 60 | - based on the data from last quarters, what is our team velocity? 61 | - what should be prioritized the next quarter and why? 62 | 63 | For this exercise, each team member should think about the big picture for their role in the next three months: we will discuss them as a group. 64 | 65 | Based on the meeting discussion, each member will add to the planning document the tasks they think they should focus on for the next quarter. **Each** task we want to do should be created as an issue in the [documentation repository](https://github.com/meilisearch/documentation) for anything documentation related and in the [devrel repository](https://github.com/meilisearch/devrel) for anything else. 66 | 67 | ### 1 Week Prior 68 | 69 | We schedule a one-hour meeting to review, as a team, the planning document for the next quarter. It ensures that our tasks aligned and that we don’t forget anything. After the meeting, [@fharper](https://github.com/fharper) will add the information in the `planning/YYYY-Q#.md` file. 70 | 71 | To ensure we have the proper history of our achievement, and being able to share our success with the company during the last follow-up (company-wide biweekly meeting) of the quarter, [@fharper](https://github.com/fharper) list our team's achievement for the actual quarter in the `planning/YYYY-Q#.md` file. 72 | 73 | 🎉 Lastly, for all the hard work we have done, we will celebrate with a team activity. Our celebration activity will be decided as a team: [@fharper](https://github.com/fharper) will need some propositions: the sooner, the better since it may require a reservation and some preparation. You can add your suggestions in the proper issue created at the beginning of the quarter. 74 | -------------------------------------------------------------------------------- /archive/planning/2021-q1.md: -------------------------------------------------------------------------------- 1 | # 2021 Q1 2 | 3 | ## Planning 4 | This is an exhaustive list of the main tasks we will accomplish in the first quarter of 2021 to move closer to our yearly goals. Estimates are made by half a day incrementation. 5 | 6 | We planned our first quarter based on the information we have gathered. Since it’s our first planning together, we have no velocity data. We define the goals-oriented tasks for about 50% of our respective time; the other half is for our daily focus and time-based opportunities: answering Slack questions, meetings, reviewing documentation PRs… 7 | 8 | Since the planning is in the process of being finalized during the second week of January, it means that we have 10 weeks left: therefore, we have 40 work days remaining in Q1, which gives us about 20 days of work per person at half capacity. We should see around 60 days on time estimated for Q1. 9 | 10 | You can follow the ETA of our Q1 planning within the [Developer Relations Project Board](https://github.com/orgs/meilisearch/projects/8). All tasks point to a specific issue with more details, if needed. 11 | 12 | ### Developer Relations Framework 13 | 14 | - [Add a team section in the repo](https://github.com/meilisearch/devrel/issues/33) 15 | - [Add the warm welcome bot to Slack community](https://github.com/meilisearch/devrel/issues/29) 16 | - [Create a KPI dashboard](https://github.com/meilisearch/devrel/issues/95) 17 | - [Create an Instagram account](https://github.com/meilisearch/devrel/issues/79) 18 | - [Create a URL Shortener](https://github.com/meilisearch/devrel/issues/78) 19 | - [Create a document on how we interact on HackerNews](https://github.com/meilisearch/devrel/issues/84) 20 | - [Create a document on how we interact on Instagram](https://github.com/meilisearch/devrel/issues/87) 21 | - [Create a document on how we interact on LinkedIn](https://github.com/meilisearch/devrel/issues/86) 22 | - [Create a document on how we interact on Reddit](https://github.com/meilisearch/devrel/issues/80) 23 | - [Create a document on how we interact on Slack](https://github.com/meilisearch/devrel/issues/113) 24 | - [Create a document on how we interact on Twitter](https://github.com/meilisearch/devrel/issues/85) 25 | - [Create a document on how we interact on YouTube](https://github.com/meilisearch/devrel/issues/88) 26 | - [Create a speaking opportunity/CFP tracking issue template](https://github.com/meilisearch/devrel/issues/43) 27 | - [Create a manager README](https://github.com/meilisearch/devrel/issues/4) 28 | - [Create a sponsorship/speaking request form](https://github.com/meilisearch/devrel/issues/56) 29 | - [Create a welcome to our YouTube channel video](https://github.com/meilisearch/devrel/issues/103) 30 | - [Create a YouTube channel](https://github.com/meilisearch/devrel/issues/8) 31 | - [Create ideas issues templates](https://github.com/meilisearch/devrel/issues/61) 32 | - [Define how we use Orbit at Meilisearch](https://github.com/meilisearch/devrel/issues/39) 33 | - [Recruit a freelance technical translator](https://github.com/meilisearch/devrel/issues/119) 34 | - [Recruit a freelance technical writer](https://github.com/meilisearch/devrel/issues/120) 35 | - [Update & publish the new release guide/steps for devrel](https://github.com/meilisearch/devrel/issues/77) 36 | 37 | ### Better Contributors Onboarding 38 | 39 | - [Add details to contribution information (core, integrations & tools)](https://github.com/meilisearch/devrel/issues/121) 40 | - [Create documentation on issues contributions](https://github.com/meilisearch/devrel/issues/122) 41 | - [Create PR documentation on contributions](https://github.com/meilisearch/devrel/issues/123) 42 | - [Integrate the contribution information into the documentation site](https://github.com/meilisearch/devrel/issues/124) 43 | 44 | ### Non-Code Contributions 45 | - [Documentation about external documentation contributions](https://github.com/meilisearch/devrel/issues/125) 46 | - [Give a public speaking workshop](https://github.com/meilisearch/devrel/issues/59) 47 | 48 | ### Advocates Program 49 | Nothing specific in Q1 50 | 51 | ### Structured Feedback Loop 52 | - [Create GitHub issues templates to redirect feedback to the right medium](https://github.com/meilisearch/devrel/issues/126) 53 | - [Streamline & clearly define our feedback loop](https://github.com/meilisearch/devrel/issues/127) 54 | 55 | ### Feedback Quality & Quantity 56 | Nothing specific in Q1 57 | 58 | ### Measuring Meilisearch Impact on Developers 59 | - [Create the first version of a NPS (Net Promoter Score) survey](https://github.com/meilisearch/devrel/issues/51) 60 | 61 | ### Community Growing 62 | Nothing specific in Q1 63 | 64 | ### Community Engagement & Longevity 65 | - [Add all-contributors to all our public repo](https://github.com/meilisearch/devrel/issues/89) 66 | - [Create a community etiquette](https://github.com/meilisearch/devrel/issues/99) 67 | - [Create a contribution reward program for existing contributors](https://github.com/meilisearch/devrel/issues/128) 68 | - [Documentation restructuration](https://github.com/meilisearch/documentation/issues/619) 69 | - [Move GitHub Discussions to Discourse](https://github.com/meilisearch/devrel/issues/21) 70 | - [Print new stickers](https://github.com/meilisearch/devrel/issues/100) 71 | - [Test versioning plugin for Vuepress](https://github.com/meilisearch/documentation/issues/705) 72 | 73 | ### Consider all Levels & Experience 74 | - [Blog post: How we approach documentation](https://github.com/meilisearch/devrel/issues/129) 75 | - [Blog post: MoMa demo](https://github.com/meilisearch/devrel/issues/130) 76 | - [Blog post: tokenizer pipeline creation](https://github.com/meilisearch/devrel/issues/133) 77 | - [Brainstorm/planning tutorial learning flow](https://github.com/meilisearch/documentation/issues/706) 78 | - [Creating or updating a dataset that demonstrate all the features of Meilisearch](https://github.com/meilisearch/devrel/issues/134) 79 | - [Tutorial: advanced Meilisearch features](https://github.com/meilisearch/documentation/issues/708) 80 | - [Tutorial: intermediate Meilisearch features](https://github.com/meilisearch/documentation/issues/707) 81 | - [Tutorial: pagination](https://github.com/meilisearch/devrel/issues/131) 82 | - [Tutorial: snapshot & dumps](https://github.com/meilisearch/devrel/issues/132) 83 | 84 | ## Retrospective 85 | 86 | At the end of Q1, we took the time to reflect on the last three months. Here are the main topics of our discussion on the form of **O**bservations and possible **S**olutions on how to improve those points in Q2. 87 | 88 | **O:** We overestimated our team velocity and underestimated our day-to-day tasks (i.e.: Slack community, documentation PRs...) which results in failure to reach many of our Q1 goals. Our planning process was also too detailed for a startup at our stage. 89 | **S:** We are a new team, in a new company, so it was to be expected. We will focus on three main tasks per team member that must be achieved in the next quarter, and two tasks to tackle if the time permit. 90 | 91 | **O:** We often felt overwhelmed with everything we have to do to reach our goals, and to help the company move forward. 92 | **S:** It is a feeling we may have to live with for at least another quarter or two, until we have a stronger foundation and better processes when it comes to Developer Relations at Meilisearch. We need to move from being in reaction mode to being more intentional with our time. One thing that will help is to better prioritize. To do so we will work with different prioritization levels for our tasks and focus only on the most important first. We will continue to use GitHub issues as a way to make a brain dump on things we need to do, even if they do not require immediate actions: things writing down freed some brain space. One additional problem is that we don't always consider everything else we do as accomplishment or "our work", meetings being a good example. It is a mindset to make ours. 93 | 94 | **O:** We don't always feel like we achieved a lot during a work day or week. 95 | **S:** This is mostly a personal matter, but we discussed solutions that can be done individually like writing down everything we do with tools like [jrnl](https://github.com/jrnl-org/jrnl) or using pomodoro to have a better perspective on how we used our time. We also need to take on best practices like atomic commits when we do PRs: it's easier for everyone involved (coding & reviewing) and help with some dopamine boosts. 96 | -------------------------------------------------------------------------------- /archive/planning/2021-q2.md: -------------------------------------------------------------------------------- 1 | # 2021 Q2 2 | 3 | Based on our [Q1 retrospective](2021-q1.md#retrospective) meeting and the company planning directive, our Q2 planning is way more streamlined. We focused on three main tasks per team member that must be achieved in Q2, and two tasks to tackle if the time permits. Check the priority structure (TBD) we use for our tasks. 4 | 5 | ## Planning 6 | 7 | ### [Carolina Ferreira](https://github.com/CarolainFG), Developer Advocate 8 | 9 | #### P1 10 | 1. [Create a Meilisearch Rails integration](https://github.com/meilisearch/devrel/issues/163) (started in Q1) 11 | 2. [Move our forum platform from GitHub Discussions to Discourse](https://github.com/meilisearch/devrel/issues/231) 12 | 3. [Move our blog platform from Ghost to Wordpress](https://github.com/meilisearch/devrel/issues/232) 13 | 14 | #### P2 15 | 4. [Create a demos repository](https://github.com/meilisearch/devrel/issues/238) 16 | 5. [Update the Meilisearch new release process to include the demos](https://github.com/meilisearch/devrel/issues/162) 17 | 6. [Create a welcome to our YouTube channel video](https://github.com/meilisearch/devrel/issues/103) 18 | 19 | ### [Tommy Melvin](https://github.com/react-learner), Technical Writer 20 | 21 | #### P1 22 | 1. [Move our documentation to Docusaurus](https://github.com/meilisearch/documentation/issues/888) 23 | 2. [Create the documentation for the alpha version of the new engine](https://github.com/meilisearch/documentation/issues/889) 24 | 3. [Welcoming the new Technical Writer](https://github.com/meilisearch/devrel/issues/252) 25 | 26 | #### P2 27 | 4. Dealing with the documentation repository issues before they becomes two weeks old 28 | 4.1 [Fix, answer, discuss or close documentation repository issues older than two weeks right now](https://github.com/meilisearch/devrel/issues/253) 29 | 5. [Better incorporate the integrations into the documentation](https://github.com/meilisearch/documentation/issues/890) 30 | 31 | ### [Frédéric Harper](https://github.com/fharper), Director of Developer Relations 32 | 33 | #### P1 34 | 1. [Create a Developer Relations Key Performance Indicators dashboard](https://github.com/meilisearch/devrel/issues/95) 35 | 2. [Create the first version of a Net Promoter Score survey](https://github.com/meilisearch/devrel/issues/51) 36 | 3. [Create the Meilisearch newsletter](https://github.com/meilisearch/devrel/issues/53) 37 | 38 | #### P2 39 | 4. [Create an introduction to Meilisearch video](https://github.com/meilisearch/devrel/issues/9) 40 | 5. [Improve the contribution information for Meilisearch](https://github.com/meilisearch/devrel/issues/121) 41 | -------------------------------------------------------------------------------- /archive/planning/2021.md: -------------------------------------------------------------------------------- 1 | # 2021 Goals 2 | 3 | ## Table of Content 4 | 5 | - [Meilisearch Goals](#meiliSearch-goals) 6 | - [OKRs](#okrs) 7 | - [Q1 planning](2021-q1.md) 8 | - [Q2 planning](2021-q2.md) 9 | - [Q3 planning](2021-q3.md) 10 | - [Q4 planning](2021-q4.md) 11 | 12 | ## Meilisearch Goals 13 | This is a summary our Meilisearch company goals for 2021 and how we can influence those. 14 | 15 | ### Community 16 | This is where we can have a real & huge impact: in the end, community is basically developer relations, with the help of every other part of the business. 17 | 18 | #### Contributor management 19 | 1. Better contributor onboarding 20 | 2. Contributions outside of just code 21 | 3. Meilisearch advocates program (ex.: Microsoft MVP, Google Experts) 22 | 23 | #### Feedback process 24 | 1. Structured feedback loop 25 | 2. Feedback quality & quantity 26 | 27 | #### Measure satisfaction 28 | 1. Measuring Meilisearch impact on developers 29 | 30 | #### Growing community 31 | 1. Growing the community 32 | 2. Community engagement & longevity 33 | 3. Consider all levels of expertise & experience 34 | 35 | ### Product 36 | We won’t participate in building new features or fixing issues directly on the product or integration repositories, but we can influence the roadmap with the feedback we get from being on the ground with our community members. 37 | 38 | ### Monetization 39 | Even though increasing the size of our community increases our chances of getting paid customers, we still won’t directly impact this 2021 goal. In addition to influencing the product roadmap, we need to ensure that we don’t alienate our open-source community while communicating about monetization. This is critical! 40 | 41 | ![a table highlighting the different goals aligned to the 3Cs of developer relations](../img/goals_2021.png) 42 | *The 2021 Meilisearch goals aligned with the [Developer Relations 3Cs](../#the-3cs)* 43 | 44 | ## OKRs 45 | 46 | Most of our 2021 goals aren’t quantifiable: we do it or don’t do it, there is no in-between. The OKRs (Objective Key Results) are listed in company goals order, Developer Relations Framework first (a devrel only goal) as it is the foundation on which we can achieve the rest. Meilisearch goals for this year are mostly oriented toward our community, hence the nearly perfect alignment with ours. 47 | 48 | ### Developer Relations Framework 49 | - Blog posts, tutorials, talks, newsletter items, and conference sponsorship ideas tracking system 50 | - Discourse up & running 51 | - Documentation of manager’s expectation & style 52 | - Documented new release process developer relations actions 53 | - Internal documentation maintenance + style guides 54 | - Make Meilisearch more human 55 | - Mechanisms to easily track progress 56 | - Orbit app day to day integration 57 | - Public documentation general guidelines & philosophical principles 58 | - Sponsorship & public speaking opportunities form 59 | - Wordpress up & running 60 | - YouTube channel 61 | 62 | ### Better Contributors Onboarding 63 | - Clear & public documentation issues & PR evaluation process 64 | - Contribution information (core, integrations & tools) has more details 65 | - Contribution information (core, integrations & tools) is integrated into the documentation 66 | 67 | ### Non-Code Contributions 68 | - Documentation about blog post contributions 69 | - Documentation about Discourse contributions 70 | - Documentation about external documentation contributions 71 | - Documentation about meetup organization contributions 72 | - Documentation about public speaking contributions 73 | - Documentation about Slack Community contributions 74 | - Documentation about text-based tutorial contributions 75 | - Documentation about video content contributions 76 | 77 | ### Advocates Program 78 | - An advocate program framework 79 | - The program runs with a test group of ten members 80 | 81 | ### Structured Feedback Loop 82 | - Better internal communication processes 83 | - Integrate better Slack questions management 84 | - Issues templates to redirect feedback to the right medium 85 | - Streamline & clearly define our feedback loop 86 | 87 | ### Feedback Quality & Quantity 88 | - Add feedback questions into the NPS (Net Promoter Score) 89 | - Feedback process & expectations in the contributions documentation 90 | 91 | ### Measuring Meilisearch Impact on Developers 92 | - Create the first version of a NPS (Net Promoter Score) survey 93 | - Replace homemade newsletter implementation with Mailchimp on the website & sandbox 94 | - Survey sent to our mailing list & different media once before Q3 95 | 96 | ### Community Growing 97 | - Create a developer visibility podcast 98 | - Create a local meetup in the main two cities where our users are & Paris 99 | - Create success story content 100 | - Create one meetup in a box 101 | - Create one talk(s) in a box 102 | - Employee Public Speaking Workshop 103 | - New engine video teaser 104 | - Organize search or open-source conference 105 | - Social Media Campaign (example: Ads, interesting questions to get people to talk about us…) 106 | - Speaking at four conferences 107 | 108 | ### Community Engagement & Longevity 109 | - Additional blog posts on Startup, Open Source, & Tech 110 | - Create a contribution reward program for existing contributors 111 | - AMA with product team/PM 112 | - Challenges/contest (example: monthly Meilisearch challenge, Hacktoberfest style - MAYli) with prizes 113 | - Community etiquette 114 | - Documentation restructuration 115 | - Draft blog posts published 116 | - Fun events + community members (example: using Among Us) 117 | - Meilisearch stickers 118 | - Move GitHub Discussions to Discourse 119 | - Newsletter once a TBD* after we start it 120 | - Replace the documentation framework (versioning) 121 | - Schedule Twitch learning session (we learn Rust as a team), AMA about new releases 122 | 123 | ### Consider all Levels & Experience 124 | - Creating a learning flow for beginners 125 | - Create video tutorials for beginners 126 | - Expand the getting started section of documentation for beginners 127 | - Streamline & revamp the getting started guide 128 | 129 | \* *Will define depending on the content & management time* 130 | -------------------------------------------------------------------------------- /archive/processes/blog_process.md: -------------------------------------------------------------------------------- 1 | # Blog process 2 | 3 | ## Goal 4 | This file aims to gather every process, guide and ressources to publish blog posts and maintain the blog application. 5 | 6 | ## Guides 7 | - [Getting started writing an article](https://www.notion.so/meilisearch/Laur-ne-0ada9d89f77845e09b32c6ffa722ef88) _(private link)_ 8 | - [Writing tips](https://www.notion.so/meilisearch/Writing-tips-7933a8e00d45478e83ee99ef23c3dc9c) _(private link)_ 9 | 10 | ## Processes 11 | - [Editorial process to get a post ready for publication](https://github.com/meilisearch/devrel/blob/main/process/posts_editorial_process.md) 12 | - [Creating your author profile on our blogging platform](https://github.com/meilisearch/devrel/blob/main/process/blog_profile_creation.md) 13 | - [Publishing a post on our blogging platform](https://github.com/meilisearch/devrel/blob/main/process/blog_publishing_process.md) 14 | 15 | ## Tools 16 | - Writing assistant: [Grammarly](https://www.grammarly.com/) (Meilisearch team members have an access or accounts on Grammarly) 17 | -------------------------------------------------------------------------------- /archive/processes/blog_profile_creation.md: -------------------------------------------------------------------------------- 1 | # Blog profile creation 2 | 3 | ## Context 4 | Ghost, our blogging platform, and our current blog theme automatically create pages for authors, and display author profile pictures on the blog post page and the homepage. 5 | Every blog author has to fill in their description. Our audience will have a better idea of who the folks working at Meilisearch are. We don't want to be another corporation with random workers. 6 | 7 | ## Process 8 | - Before publishing an article, you need access to Ghost. 9 | - Meilisearch workers: ask someone from the DevRel team to create credentials for you. 10 | - External contributors: discuss this with your contact at Meilisearch. 11 | - After signing in, fill your description at https://meilisearch.ghost.io/ghost/#/settings/staff/{USER_SLUG} 12 | Capture d’écran 2022-06-06 à 16 41 39 13 | If you don't feel inspired, keep it simple: "I work on the core team at Meilisearch". 14 | 15 | All details are optional. For instance, when filling the location, you can be very specific, go for the country you usually live in, or not say anything at all. 16 | -------------------------------------------------------------------------------- /archive/processes/blog_publishing_process.md: -------------------------------------------------------------------------------- 1 | # Blog publishing process 2 | 3 | ## Context 4 | Once an article has been reviewed, authors need to follow the steps below to make sure their content is ready for publication. 5 | 6 | ## Process 7 | 1. Before publishing an article, you need access to [Ghost](https://meilisearch.ghost.io/ghost/) 8 | - Meilisearch workers: ask someone from the DevRel team to create credentials for you 9 | - External contributors: discuss this with your contact at Meilisearch 10 | 2. Make sure you have properly filled in your profile description. Check the [profile creation process](https://github.com/meilisearch/devrel/blob/main/process/blog_profile_creation.md) if needed. 11 | 3. Once you are connected to Ghost, you can click on `New Post` in the top right corner of the page. Upon clicking it, you are immediately taken to the Ghost editor page 12 | 4. Write the post title 13 | 5. Copy and paste the post content into the Ghost editor 14 | 6. Make sure no information was lost. It's important to check: 15 | - Links 16 | - Format: 17 | - Headings 18 | - Font weight: bold, italics... 19 | - Spaces between paragraphs 20 | - Quotation marks! 21 | - Code snippets ⚠️ Don't forget to choose the right programming language! 22 | 23 | 24 | - Lists 25 | 26 | 👉 27 | 28 | 7. Insert the desired illustrations into the body (screenshots, etc.), please make sure they comply with [the size and quality requirements](https://github.com/meilisearch/devrel/issues/362). 29 | - Place the cursor where you want the image to be displayed (it has to be an empty line) 30 | - Click on the `+` button at the beginning of the line, and select the `Image option` in the dropdown menu 31 | 32 | 33 | 34 | 8. Add the cover image by clicking on `+ Add feature image` above the post title. Make sure it complies with the [blog cover guidelines](https://github.com/meilisearch/devrel/issues/383) 35 | 36 | 9. Add the alternative text of the images and a caption if necessary 37 | 38 | 39 | 10. Open the `Post settings` by clicking on the icon next to the `Save` button at the top right corner of the page: 40 | - Add the Post URL. Make sure it complies with the [URL guidelines](https://github.com/meilisearch/devrel/blob/main/guidelines/url_guidelines.md) 41 | - Add the excerpt of the post: it is limited to 300 characters, but it is better to make it shorter: around 155 characters. You can check the [excerpt guidelines](https://github.com/meilisearch/devrel/blob/main/guidelines/excerpt_guidelines.md) 42 | 43 | 44 | 45 | 11. Check the `Meta data` and the `Twitter card` and adapt the titles and descriptions if needed (avoid cropped text) 46 | 47 | 48 | 💡 To see what your post will look like once published, you can click on `Preview` at the top right corner of the Ghost editor. By clicking on the Twitter icon you'll also have a preview of how it will look like when shared on social media or when found on Google. 49 | 50 | 12. Change the status of the blog post to `ready for publication` in the [post forecast table](https://www.notion.so/meilisearch/Post-forecast-a5b3ede0ee744553bfa63810807ac507) and add the [desired tag](https://github.com/meilisearch/devrel/blob/main/guidelines/tag_guidelines.md) in the dedicated column 51 | 52 | ## Post-publication corrections 53 | If you realize you need to make corrections after the post has been published, please follow the steps described below: 54 | 1. Log in to Ghost with the user editor (bonjour@meilisearch). You can find the credentials on 1Password. 55 | ⚠️ If you don't have access to 1Password, ask a member of the Developer Relations team to make the modifications for you. 56 | 2. In the left-hand menu, click on Published (under Posts) 57 | 3. Find the post you need to correct (if it was published recently, it should be on the top of the list) 58 | 4. Make the necessary modifications 59 | 5. Click on the `Update` button on the top right corner of the page 60 | 6. Go back by clicking the `< Posts` button located on the top left corner of the page 61 | 7. Sign out 62 | -------------------------------------------------------------------------------- /archive/processes/posts_editorial_process.md: -------------------------------------------------------------------------------- 1 | # Posts editorial process 2 | 3 | ## Context 4 | 5 | We want to establish the editorial **process** for taking **a blog post** (or any content piece that could be published elsewhere) from draft to publication. 6 | 7 | This content will go through an expert review from Meilisearch team members and through an editorial review from the documentation team. 8 | 9 | 10 | ⚠️ Posts that have a **hard publication deadline** (likely to be business-related) will be distinguished from other posts with a 🚨 in their estimated publication date. In this case, it's a hard deadline rather than an expected publication date. 11 | 12 | ## Tools 13 | 14 | We'll follow the progress of a post from the idea to publication with [this content plan](https://meilisearch.notion.site/a18ade38a404490cb41a9e3ab06e0536?v=1cd2c3ed7b5b4671a862ca957120dcab). 15 | 16 | ## Process 17 | 18 | | Stage | Stage description | Action for the author | Action for the Documentation team | 19 | |---|---|---|---| 20 | | 1 | A Meilisearch member or an external contributor decides to write a post. | The author has to create a new content piece in the [content plan](https://meilisearch.notion.site/a18ade38a404490cb41a9e3ab06e0536?v=1cd2c3ed7b5b4671a862ca957120dcab) in Meilisearch's Notion workspace with the following field values:
- **Topic/title**: the topic or title of the content piece
- **Link**: a link to the post being written on **Google docs**. You can find a **blog post template** in Google Doc's Template Gallery
- **Author**: the author's name
- **Medium**: mediums where the post should be published (sometimes it's not the blog)
- **Status**: `not started`.
- **Priority**: If this date is a hard deadline, select the `🚨 hard deadline` option
- **Publication date**: tentative publication date.
- If it's a blog post, add the desired [tag](https://github.com/meilisearch/devrel/blob/main/guidelines/tag_guidelines.md) in the 'Blog tag' column | | 21 | | 2 | The author writes the post. We advise the use of a [writing assistant](https://github.com/meilisearch/devrel/blob/main/process/blog_process.md#tools).| Change **Status** to `writing in progress` | | 22 | | 3 | The post's writing has been paused due to other priorities or is blocked by external factors. | - Change **Status** to `blocked/paused`
- If possible, provide relevant information about the pause/blockage in the 'Comments' column | | 23 | | 4 | The author has finished the first draft of the post.
The post is ready for review by the expert committee or any other required feedback on the content (e.g., a team manager). | Change **Status** to `expert review needed` | | 24 | | 5 | The expert committee is currently reviewing the post. The author may update the content accordingly in this stage and require other expert reviews. | Change **Status** to `expert review in progress` | | 25 | | 6 | The author has a draft ready for editorial review by Meilisearch's documentation team and tags the Documentation team (@meilisearch/docs-team). | Change **Status** to `editorial review needed` | | 26 | | 7 | Meilisearch's documentation team is currently reviewing the post. | | - Change **Status** to `editorial review in progress`
- Add the reviewer's name to the **Reviewer** column | 27 | | 8 | Meilisearch's documentation team has finished reviewing the post and notify the author. | | Change **Status** to `editorial review finished` | 28 | | 9 | The author reviews the suggestions made by the proofreaders. |The author repeats steps 5 to 7 if necessary. | | 29 | | 10 | The author follows the [blog publishing process](https://github.com/meilisearch/devrel/blob/main/process/blog_publishing_process.md) until the post is ready for publication. | - Change **Status** to `ready for publication`| | 30 | | 11 | Meilisearch's DevRel team takes care of the publication if Meilisearch owns the medium,
otherwise, the author takes care of getting the post published. | - Update the **Link** field with the URL of the published post
- Change **Status** to `published`
- Follow the process to indicate what info is in the post for maintenance reasons. See [#348](https://github.com/meilisearch/devrel/issues/348) | | 31 | 32 | ## Process compliance failure 33 | 34 | ### Publication date update 35 | 36 | If the publication date is modified (this can be a delay or adding a heard deadline), the group responsible for the publication date update (this can be the author during stages 1 to 4 and 8 to 9, or the documentation team during stages 5 to 7) has to notify the other group and the DevRel team and make sure that they are aware of this change. 37 | -------------------------------------------------------------------------------- /archive/processes/release_process.md: -------------------------------------------------------------------------------- 1 | # Release process 2 | 3 | Those are the steps we need to take every time we release a new version of Meilisearch. 4 | 5 | ## Pre-release: 6 | 7 | - Write a blog post on the main changes introduced by the new version. 8 | - [Release blog post template](https://www.notion.so/Release-blog-post-template-d3e2f64e30d145218d74b7be8267a8ef) 9 | - [Blog process](https://github.com/meilisearch/devrel/blob/main/process/blog_process.md) 10 | - If the new release introduces a new feature that can be demoed, create a demo to highlight it. Demos should respect the Meilisearch Design System, the following ressources have been created for this purpose: 11 | - [Meilisearch demos CSS theme](https://github.com/meilisearch/demos/tree/main/process/css-theme) 12 | - [Guide to design a demo](https://www.figma.com/file/YUqMlOmApYd0D2aitPyDce/Guide-to-design-a-demo) (_private link_) 13 | 14 | ## The release day: 15 | 16 | - Publish the release blog post 17 | - [Blog publishing process](https://github.com/meilisearch/devrel/blob/main/process/blog_publishing_process.md) 18 | - Share it on our socials along with the demo (Twitter, Slack community, LinkedIn...) 19 | - [How to write the best performing tweets](https://www.notion.so/meilisearch/Social-Media-Queue-f5ab593e972d49a891059e2e537be7fe#ad47b7f117ee4b44ba73e09a963c0139) 20 | - Update marketing material if needed 21 | - [Alternative comparison](https://docs.meilisearch.com/learn/what_is_meilisearch/comparison_to_alternatives.html) 22 | 23 | ## After the release: 24 | 25 | - Update demos 26 | - [Update demos process](https://github.com/meilisearch/demos/blob/main/process/demo_update_%20process.md) 27 | - Update the relevant tutorials 28 | - [Blog content: when to update a content piece?](https://github.com/meilisearch/devrel/issues/348) 29 | -------------------------------------------------------------------------------- /archive/processes/releases.md: -------------------------------------------------------------------------------- 1 | # New Meilisearch releases - what to do 2 | 3 | Those are the steps we need to take every time we release a new version of Meilisearch. 4 | Exceptions: alpha versions 5 | 6 | ## Table of Contents 7 | - [Responsibilities](#responsibilities) 8 | - [Immediately after a release](#immediately-after-a-release) 9 | - [Pre-release week](#pre-release-week) 10 | - [Release day](#release-day) 11 | 12 | ## Responsibilities 13 | 14 | Right now, unless mentioned, the tasks for a new release on the developer relations side are divided in three categories or actions with each person accountable for them: 15 | 16 | - Demos 17 | 18 | ## Immediately after a release 19 | 20 | Start of the monthly release cycle 21 | 22 | 1. Create a draft on a branch called `prepare-meilisearch-[YYYY]-[WW]` (e.g.: prepare-meilisearch-2020-W3 for the third week of the year 2020) in the [documentation repository](https://github.com/meilisearch/documentation). 23 | 2. Add every PR from the corresponding [Meilisearch Milestone](https://github.com/meilisearch/Meilisearch/milestones) to the body of the `prepare-meilisearch-[YYYY]-[WW]` PR, with empty checkboxes next to each. 24 | 3. Strikeought the PR that don't need documentation modification. 25 | 4. Check the corresponding box once the relevant documentation has been added. 26 | 5. The documentation should contain at minimum references for the new feature(s), if any. 27 | 6. A decision should be made if we need to create a [guide](https://docs.meilisearch.com/guides/) for the new feature(s), if any. 28 | 7. Update demos. 29 | 30 | ## Pre-release week 31 | 32 | 4th week of the monthly cycle 33 | 34 | 1. If the release has substantial new features, we should draft a [blog](https://blog.meilisearch.com/) post about the new release. 35 | - be clear about the new feature(s) and the impact on the users, if any 36 | - for API, add code example on how to use it 37 | - highlight breaking changes, if any 38 | - call to action, if any 39 | 2. he `prepare-meilisearch-[YYYY]-[WW]` PR should be reviewed and ready to merge to the primary branch (as of 2021, this is the [master branch](https://github.com/meilisearch/documentation/tree/master)). 40 | 41 | ## Release day 42 | 43 | 1. The `prepare-meilisearch-[YYYY]-[WW]` branch should be merged with the [master branch](https://github.com/meilisearch/documentation/tree/master). The updated version of the documentation should be [automatically deployed](https://docs.meilisearch.com/) momentarily. 44 | 2. Once the new documentation version is deployed, we should publish the blog post, if any. 45 | 46 | _For the next steps, we will share the blog post; if none, we will share the [release notes](https://github.com/meilisearch/Meilisearch/releases) from GitHub._ 47 | 48 | 3. Share in the #general channel of our [Slack community](https://slack.meilisearch.com/) as yourself; 49 | 4. Share on [GitHub Discussions](https://github.com/meilisearch/Meilisearch/discussions) as yourself; 50 | 5. Share on [Twitter](https://twitter.com/meilisearch) (from Mention); 51 | 52 | _If the release contains enough interesting new features, we should:_ 53 | 54 | 6. share on [LinkedIn](https://www.linkedin.com/company/meilisearch) (need to be admin of the LinkedIn page); 55 | 7. share on [Reddit](https://www.reddit.com/) (need to add the sub/subs) (credentials in 1Password); 56 | 57 | _If the release is astonishing only, we should:_ 58 | 59 | 8. share on [HackerNews](https://news.ycombinator.com/) as yourself. 60 | -------------------------------------------------------------------------------- /archive/readme.md: -------------------------------------------------------------------------------- 1 | This folder contains old files from this repo. They are deprecated, but kept in this folder to serve as references. 2 | -------------------------------------------------------------------------------- /assets/logos/dark-background/default/meilisearch-mono.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /assets/logos/dark-background/default/meilisearch.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 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /assets/logos/dark-background/logomark/meilisearch-mono.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | -------------------------------------------------------------------------------- /assets/logos/dark-background/logomark/meilisearch.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /assets/logos/dark-background/logotype/meilisearch.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | -------------------------------------------------------------------------------- /assets/logos/dark-background/vertical/meilisearch-mono.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /assets/logos/dark-background/vertical/meilisearch.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 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /assets/logos/light-background/default/meilisearch-mono.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /assets/logos/light-background/default/meilisearch.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 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /assets/logos/light-background/logomark/meilisearch-mono.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | -------------------------------------------------------------------------------- /assets/logos/light-background/logomark/meilisearch.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /assets/logos/light-background/logotype/meilisearch.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | -------------------------------------------------------------------------------- /assets/logos/light-background/vertical/meilisearch-mono.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /assets/logos/light-background/vertical/meilisearch.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 | 29 | 30 | 31 | -------------------------------------------------------------------------------- /communication/channel_mapping.md: -------------------------------------------------------------------------------- 1 | Following a project initiated in [#72](https://github.com/meilisearch/devrel/issues/72), this is the mapping of the current communication channels that are used by DevRel. 2 | 3 | | Category | Channel | Use case | 4 | |---|---|---| 5 | | Email | bonjour@meilisearch.com | Used for anything at the moment: support, inquiries... | 6 | | Discord | [Discord community](https://discord.gg/meilisearch): all public channels and DM | Announcements, support, community | 7 | | Crisp | [Instant messaging](https://app.crisp.chat/) _(private link)_ | Support, general inquiries | 8 | | GitHub | [Github Discussions](https://github.com/meilisearch/Meilisearch/discussions) | feature requests, bug, support | 9 | | GitHub | GitHub issues for [Meilisearch repo](https://github.com/meilisearch/Meilisearch/issues) and other repos owned by the DevRel team | feature requests, bug, support | 10 | | Twitter | Any interactions with [Meilisearch's Twitter account](https://twitter.com/meilisearch) | Announcements, inquiries | 11 | | Linkedin | Any interactions with [Meilisearch's Linkedin account](https://www.linkedin.com/company/meilisearch) | Announcements | 12 | 13 | We also wrote more about our communication channels [here](https://www.notion.so/meilisearch/Communication-Conventions-9fa0ca12733b49fcaa4ebee89267e808) _(private link)_. 14 | -------------------------------------------------------------------------------- /communication/distribution_channels.md: -------------------------------------------------------------------------------- 1 | Reproducing the list of the distribution channels we can thin ok for our content, as part of the work done in [#452](https://github.com/meilisearch/devrel/issues/452) 2 | 3 | ### Owned media channels: 4 | 5 | - [ ] [Meilisearch website](https://www.meilisearch.com/) 6 | - [ ] [Blog](https://blog.meilisearch.com/) 7 | - [ ] Newsletter 8 | - [ ] [Meilisearch Discord community](https://discord.gg/meilisearch) 9 | - [ ] Social media 10 | - [ ] Share Posts on: 11 | - [ ] [Twitter](https://twitter.com/meilisearch/) 12 | - [ ] [LinkedIn](https://www.linkedin.com/company/meilisearch) 13 | - [ ] [Reddit](https://www.reddit.com/)/[Meilisearch sub-reddit](https://www.reddit.com/r/Meilisearch/) 14 | - [ ] [Hacker News](https://news.ycombinator.com/) 15 | - [ ] Re-post on social media 16 | - [ ] SEO 17 | - [ ] Get backlinks 18 | - [ ] Optimise content for SEO 19 | - [ ] Direct share 20 | - [ ] Share with relevant contact 21 | - [ ] Share with relevant influencers 22 | - [ ] Events 23 | - [ ] Speaking about it at events 24 | - [ ] Webinar 25 | - [ ] Word-of-mouth marketing: other team members can share with their personal and professional networks 26 | - [ ] Repurpose content with a different format: gif, quotes, figures, infographics, Twitter thread… 27 | - [ ] Reuse content with a different angle - e.g. React + Rails: don't sell it the same way to both communities 28 | - [ ] Publish on external sites 29 | - [ ] Dev.to 30 | - [ ] Hashnode 31 | - [ ] Hackernoon 32 | 33 | ### Earned media channels: 34 | 35 | - [ ] Podcast: find an industry podcast to talk about it 36 | - [ ] Content syndication 37 | - [ ] External guest post on industry blogs 38 | - [ ] External newsletters 39 | - [ ] External communities 40 | 41 | ### Paid media channels: 42 | 43 | - [ ] Paid ads 44 | - [ ] Google Adwords 45 | - [ ] Twitter 46 | - [ ] Reddit 47 | 48 | ### Other ressources 49 | - [ ] For integrations: see the [Integration launch process](https://www.notion.so/meilisearch/Integration-launch-process-94e1c85a7b4749f09a8ad6048d608d9e) _(private link)_ 50 | -------------------------------------------------------------------------------- /devrel.md: -------------------------------------------------------------------------------- 1 | # Developer Relations at Meilisearch 2 | You can find some information about how we do Developer Relations at Meilisearch: the foundation of devrel (3Cs), our lean startup approach and the list of activities we do. 3 | 4 | ## Table of Contents 5 | - [The 3Cs](#the-3cs) 6 | - [Lean Approach](#lean-approach) 7 | - [Priority System](#priority-system) 8 | - [Developer Relations Activities](#activities) 9 | 10 | 11 | ## The 3Cs 12 | The three pillars of Developer Relations are **C**ommunity, **C**ontent, and **C**ode, also known as the 3Cs*. The main focus of our team is the community: just read our mission to understand that everything we do is for our community. To help us achieve our mission, we use two main activities: content and code. The former is any type of content on any useful medium; some examples are talks at conferences, documentation, or video tutorials. The latter, code, is part of the foundation of who we are: we are developers. It translates into code examples for the documentation, code demos for our conference presentations, technical support, or even being responsible for specific APIs or contributing to open source to give back to the community and be a good web citizen. All together, they form the foundation of developer relations. 13 | 14 | ![a diagram showing the 3Cs as pillars into developer relations](img/3Cs.png) 15 | 16 | \* *adapted from [SendGrid 2014 article](https://sendgrid.com/blog/3-cs-developer-relations/)* 17 | 18 | ## Lean Approach 19 | We believe that plans should never be set in stone: they are a lighthouse guiding us in the right direction. We make plans to ensure that we are focusing in the right direction and maximizing our efforts where we can have the greatest impact. 20 | 21 | Our process will always be “[lean startup](http://theleanstartup.com/principles)” style. 22 | 23 | ![The lean aporoach we are taking: a process loop that goes from build, to measure to learn advitam eternam](img/lean_devrel.png) 24 | 25 | We will update our yearly planning and tasks based on the KPI we will gather while working on them. If we are not successful, even with all the focus work done, we will take the time to evaluate our processes. We can go as far as modifying the yearly goal to adapt to how our industry and community is responding to our efforts. 26 | 27 | ## Priority System 28 | We are using a priority system for our tasks and goals based on the [MoSCoW method](https://en.wikipedia.org/wiki/MoSCoW_method). 29 | 30 | P0 - Urgent 31 | P1 - Must have 32 | P2 - Should have 33 | P3 - Could have 34 | P4 - Will not have 35 | 36 | ### P0 - Urgent 37 | Priority P0 is for urgent things needed on our team or another team needing our help. They are the reactive mode tasks. In a perfect world, those would-be situations created by external factors as we should plan better on our side. 38 | 39 | ### P1 - Must Have 40 | Priority P1 is for non-negotiable tasks that will help us achieve our goals with the maximum impact. Those are the tasks, when planned for a quarter, that should be done by the next one. 41 | 42 | ### P2 - Should Have 43 | Priority P2 is for important initiatives that may not bring as much value to the team than the P1. It includes things we should do that won’t directly help us achieve our goals, but needed to move in the right direction. A P2 can become P1 when they are critical for the business or are prerequisites for another P1 (i.e.: changing the documentation framework—we need it to manage different versions of Meilisearch after v1, but it has no direct impact on our goals). 44 | 45 | ### P3 - Could have 46 | Priority P3 is for nice to have initiatives: they have a small impact, and are mostly done when we have the time. 47 | 48 | ### P4 - Will not have 49 | Priority P4 have a misleading title: will not have is mostly about our team. They are the tasks or initiatives that are not a priority and don’t bring much value, still they could be nice. If they are really short to do, it could be a task we do to change our mind between more important ones, but in most cases, they are tasks open for anyone else to take. 50 | 51 | ## Activities 52 | Here is an exhaustive list of developer relations activity categories. We are taking activities that could be managed by a marketing or social media team for now. 53 | 54 | ### Blog Management 55 | - Writing blog posts for Meilisearch or as a guest elsewhere 56 | - Managing external writers, whether volunteers or paid freelancers 57 | 58 | ### Code Contributions Managemeny 59 | - Helping contributors and reviewing code-related PRs 60 | 61 | ### Documentation Management 62 | - Helping contributors and reviewing documentation-related PRs 63 | - Writing documentation 64 | - Resolving documentation-related issues and maintaining the repository 65 | 66 | ### Learning Resource Creation 67 | - Creating demo applications using Meilisearch 68 | - Creating helpful code snippets 69 | - Creating example datasets 70 | 71 | ### Technical Support / Customer Service: 72 | - Discourse Support 73 | - Slack Support 74 | 75 | ### Hackathon 76 | - Running hackathon contests and mentoring participants 77 | 78 | ### Newsletter 79 | - Writing and sending the newsletter 80 | 81 | ### Podcast 82 | - Participating in external audio podcasts or running the official Meilisearch podcast, if we create one 83 | 84 | ### Public Speaking 85 | - Speaking at conferences, including creating slides & demos 86 | - Organizing and speaking at meetups, including creating slides & demos 87 | 88 | ### Discord Community Management 89 | - Ensuring a healthy and active Discord community 90 | 91 | ### Social Media Management 92 | - Posting, commenting, and replying on social media accounts 93 | 94 | ### Tech Media Spokesperson 95 | - Speaking to tech media on behalf of the company 96 | 97 | ### Video Production 98 | - Participating in or creating our own vidcasts, live streams, and other video-based content (such as tutorials) 99 | 100 | ### Virtual Evangelist Management 101 | - Managing a digital volunteer program (equivalent to Microsoft MVP, Google Experts, etc....) 102 | -------------------------------------------------------------------------------- /events/conferences.md: -------------------------------------------------------------------------------- 1 | # Conferences 2 | 3 | We'll list here the conferences we would like to speak at, it could be this year or in the future if we fit into the program. 4 | 5 | - [API Specifications](https://apispecs.io) 6 | - [API World](https://apiworld.co) 7 | - [Opensource Experience](https://www.opensource-experience.com/) 8 | - [Paris Web](https://www.paris-web.fr/) 9 | -------------------------------------------------------------------------------- /events/speaker-template.md: -------------------------------------------------------------------------------- 1 | # NAME 2 | 3 | *Add a high resolution picture, the one you want conferences to use in your bio* 4 | 5 | *Add your biography here* 6 | 7 | ## Topics 8 | 9 | *List of topics (ASC) you would be open to talk about (i.e. Meilisearch, Rust, serverless...)* 10 | 11 | ## Experience 12 | 13 | *List all the talks you given (date DESC)* 14 | 15 | **Format** 16 | EVENT NAME WITH LINK (YYYY-MM-DD) 17 | Tweet size description of the talk 18 | Links to any resources like recording or slides 19 | 20 | ## Links 21 | 22 | *Add all links (name ASC) you want to see there (i.e. Twitter, LinkedIn, website...)* 23 | 24 | ## Requierements 25 | 26 | *If you have requierements when you speak at the events, list them there ([example](https://github.com/fharper/speakerkit#requirements) from Fred)* 27 | -------------------------------------------------------------------------------- /events/speaking.md: -------------------------------------------------------------------------------- 1 | # Public Speaking 2 | 3 | At Meilisearch we are passionate about what we do, and technology in general. We see events like conferences or meetups as opportunities to share these passions with the broader developer community. If you are looking for a speaker about Meilisearch please send us an email at bonjour@meilisearch.com. We are also open to talk about different other technical and non-technical topic. 4 | -------------------------------------------------------------------------------- /img/3Cs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/meilisearch/devrel/b7b3cd1cf65236c35cd73102827add791430c45f/img/3Cs.png -------------------------------------------------------------------------------- /img/goals_2021.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/meilisearch/devrel/b7b3cd1cf65236c35cd73102827add791430c45f/img/goals_2021.png -------------------------------------------------------------------------------- /img/lean_devrel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/meilisearch/devrel/b7b3cd1cf65236c35cd73102827add791430c45f/img/lean_devrel.png -------------------------------------------------------------------------------- /opensource.md: -------------------------------------------------------------------------------- 1 | # Open Source at Meilisearch 2 | Most people will agree that, in its simplest form, Open Source Software (OSS) **is a software that has its source code available**. The Open Source Initiative has a [list of ten criteria](https://opensource.org/osd) defining even more open source, which we agree and follow by using the [MIT license](https://opensource.org/licenses/MIT) for all the source code we release. For us, Open Source is much more than the code. 3 | 4 | ## Public by default 5 | We firmly believe that open source isn't just about the code: it's a mindset. It's how we do business and it's how we give back to the tech community. 6 | 7 | First, we are including the community in everything we do: **public is the default visibility of our work**. We plan the future of Meilisearch with the help and feedback of everyone who wants to be involved. It is possible to suggest a [feature idea](https://roadmap.meilisearch.com/tabs/1-under-consideration) to influence the roadmap. We sincerely welcome pull requests, even when it's about a feature that wasn't a priority for us, as a for-profit company. Contributing doesn't only equal code: it's also about making us aware of any problems with our product by creating issues on [GitHub](https://github.com/meilisearch) or being part of our lovely [Discord community](https://discord.gg/meilisearch). Note that we will have more documentation on the best ways to contribute to Meilisearch. 8 | 9 | Obviously, we can do even more, so it's why starting from v0.21, we are moving forward with a public [specifications](https://github.com/meilisearch/specifications) process that will close the loop on involving the community and being totally transparent with everything we do product-wise. 10 | 11 | This, all this, is what we consider being open source. 12 | 13 | ## Vulnerability & whatnot 14 | As someone you may know would say “With great power comes great responsibility" and it cannot be truer. By adopting the **public by default** approach, we are prone to mistakes. It's fine. It will happen, no matter how experienced our teams are, we will make mistakes. Again, it is completely fine, it's part of the process, a process where we learn from those mistakes to continue to be the best at what we do. 15 | 16 | Let's be honest, being part of an open-source community is not always easy: it comes with a whole new territory. It means that you are becoming vulnerable: us as a company, but each individual working at Meilisearch. Vulnerable to said mistakes. Vulnerable to others’ judgment. Vulnerable to people's comments, which, unfortunately, aren't always friendly. Those are things we can learn as a community and as a company. 17 | 18 | Going the public way, working all together with the open source community also means that as a company, we cannot iterate as fast as we would like. We understand that it's a necessary step that will pay off in the medium to long term, even in this competitive world. In any cases, we strive for quality and not quantity. 19 | 20 | ## Tools we use 21 | To distribute our code, manage versions and contributions, we are using git as our source code management tool and [GitHub](https://github.com/meilisearch) as the source of truth for all our repositories including the [search engine](https://github.com/meilisearch/Meilisearch) itself, our multiple [integrations](https://github.com/meilisearch/integration-guides), Meilisearch [demos](https://github.com/meilisearch/demos) and some other tools we made available to our community. 22 | --------------------------------------------------------------------------------