├── .editorconfig ├── .gitattributes ├── CODE_OF_CONDUCT.md ├── Content and Writing └── README.md ├── Events and Meetups └── README.md ├── Forums and Discord └── README.md ├── LICENSE ├── README.md ├── STRAPI_STARS.md ├── Strapi Project Contribution └── README.md └── assets └── community-resources.png /.editorconfig: -------------------------------------------------------------------------------- 1 | 2 | root = true 3 | 4 | [*] 5 | indent_style = tab 6 | end_of_line = lf 7 | charset = utf-8 8 | trim_trailing_whitespace = true 9 | insert_final_newline = true -------------------------------------------------------------------------------- /.gitattributes: -------------------------------------------------------------------------------- 1 | * text=auto eol=lf 2 | *.ai binary 3 | readme.md merge=union -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hi@strapi.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /Content and Writing/README.md: -------------------------------------------------------------------------------- 1 | # Content and Writing 2 | Information on everything content, this includes guides and content on how to create, manage and promote resources you create. Be that written, audio or video. 3 | 4 | ## Table of Contents 5 | - [Why we Create Content](#why-we-create-content) 6 | - [Benefits of Creating Content](#benefits-of-creating-content) 7 | - [What can I write about?](#what-can-i-write-about) 8 | - [Introduction to Technical Writing](#introduction-to-technical-writing) 9 | - [Writing for Developers](#writing-for-developers) 10 | - [Clear Writing](#clear-writing) 11 | - [Universality](#universality) 12 | - [Tools to Write Better](#tools-to-write-better) 13 | - [Technical Writing Resources](#technical-writing-resources) 14 | - [Introduction to Video Content](#introduction-to-video-content) 15 | - [Video Creation Resources](#video-creation-resources) 16 | - [Promoting your Content](#promoting-your-content) 17 | - [General Content Creation Resources](#general-content-creation-resources) 18 | 19 | ### Why we Create Content 20 | 21 | Content in any form (and believe me it has many) has the sole purpose of passing information. Outwardly, we create content to inform and in the process educate. In today's world, and for developers particularly, content and its creation have become an invaluable way of scaling education. If someone wants to know how to spin up a web server with node.js, a 10 video call to teach them would do the job. However, if a hundred people want to know the same piece of information, an introductory article or short video on how to create said web server would be a better use of your time. Imagine having to chat with a hundred people to share the same information? No! 22 | 23 | As altruistic as it may sound, we mostly create content to pass information onto others in a scalable way. That's not to say that it doesn't come with benefits. 24 | 25 | ### Benefits of Creating Content 26 | - We get to pass on the knowledge we acquire and empower the people who read it 27 | - You can get paid to do it - freelance or fulltime, lots of people make a living creating technical content 28 | - It helps build your credibility as a professional. Writing about something is a very nice way of saying you know how to do something 29 | - It attracts eyeballs and positively impacts your professional career 30 | 31 | 32 | #### What can I write about? 33 | A phrase ubiquitous in writing circles is *"If you get asked something 10 times, write a blog post"*, of course, I'm paraphrasing here but the sentiment is what's important. You can write about things you get asked a lot. 34 | You can write about a problem you wish was documented. Ever solve a problem or fix a bug and wish someone had written a blog post or done a video explaining the solution? Yes, then be that someone. 35 | And one of the most important things to write about is things you are learning, teaching is one of the best ways of learning deeper. So don't be afraid to take that leap. 36 | 37 | ### Introduction to Technical Writing 38 | This is one of my favourite definitions of Technical Writing: 39 | > Technical writing is an audience-centred means of communication that provides a reader with clear and easy access to information. 40 | 41 | It puts a focus on the audience which in our case are **developers** and describes what characteristics your content should possess - **clarity and universality**. 42 | 43 | #### Writing for Developers 44 | 45 | 'Writing for Developers' takes on many meanings in our context. It means both *how developers should approach writing* and *how we should write for developers*. Both very important perspectives that I will tackle in this resource. 46 | 47 | *how developers should approach writing* 48 | 49 | *how we should write for developers* 50 | 51 | #### Clear Writing 52 | 53 | The clarity of your writing is very important, even more so for technical pieces. People consuming technical writing expect it to be clear, precise and straight to the point. Clarity means having a set-out structure to your content, using correct grammar and spelling and making your sentences as simple as possible. 54 | 55 | #### Universality 56 | Universality here, is about making sure people of all experience levels have access to and benefit from your content. Here is a list of things to look out for to make your content better in this regard. 57 | - Use simple and short paragraphs to explain topics 58 | - Don't assume technical expertise, make sure that your content caters for developers of all skill levels. 59 | - Always have prerequisites if you're having people write an article folks are supposed to follow. This way they can get everything they need ready. 60 | - Say the full form of all acronyms the first time you use them. 61 | 62 | #### Tools to Write Better 63 | - [Hemingway](http://www.hemingwayapp.com/) 64 | - [Grammarly](grammarly.com/) 65 | - [Dropbox Paper](https://www.dropbox.com/paper) 66 | 67 | 68 | #### Technical Writing Resources 69 | - [Awesome Technical Writing](https://github.com/BolajiAyodeji/awesome-technical-writing) 70 | - [Writing for Software Developers](https://philipkiely.com/wfsd/) 71 | - [Advice for Technical Writing](https://css-tricks.com/advice-for-technical-writing/) 72 | - [Googles Technical Writing Course](https://developers.google.com/tech-writing) 73 | - [Why developers should know how to write](https://www.freecodecamp.org/news/why-developers-should-know-how-to-write-dc35aa9b71ab/) 74 | - [Technical Writing for Non-Writers](https://speakerdeck.com/taroth21/technical-writing-for-non-writers?slide=4) 75 | - [Proofreading: 7 Editing Tips That’ll Make You a Better Writer in 2020](https://smartblogger.com/proofreading-editing-tips/) 76 | 77 | ### Introduction to Video Content 78 | Just like Technical Writing, creating Video Content requires one to have **clarity and universality** in mind. We need to keep it in mind, when creating content of any sort that our audiences have different ways of understanding and assimilating knowledge - they have different learning styles. If one form won't make a concept clear, they'll try another one. Video content happens to be a very popular method of learning as many people find visual learning better and more effective. 79 | 80 | ### Video Creation Resources 81 | - [egghead instructor guide](https://howtoegghead.com/instructor) 82 | - [How to start a coding YouTube channel](https://www.youtube.com/watch?v=AsTagX5tG4E) 83 | - [How to Make Great Training Videos](https://www.techsmith.com/blog/how-to-make-great-training-videos/) 84 | 85 | ### Promoting your Content 86 | Writing your content is one thing, getting people to consume it is another. I know it might be a little *cringy* to be all loud about the stuff you make but trust me, it's worth it. Promoting and sharing things you create means more people get to benefit from the stuff you do. Naming for a start is a great way to make sure people can find your content. Using Keywords from tools like [Google Trends](https://trends.google.com) and [Keyword Tool](https://keywordtool.io) would go a long way. 87 | 88 | Platforms play a huge role in making sure people see your content too. Here is a list of Developer-Centric Platforms to post on. 89 | - [Hashnode](https://hashnode.com/) 90 | - [Reddit](https://www.reddit.com/) 91 | - [Dev](https://dev.to/) 92 | - [Hackernoon](https://hackernoon.com/) 93 | 94 | ### General Content Creation Resources 95 | - [The Ultimate Guide to Content Creation](https://blog.hubspot.com/marketing/content-creation) 96 | -------------------------------------------------------------------------------- /Events and Meetups/README.md: -------------------------------------------------------------------------------- 1 | # Events and Meetups 2 | Information on everything events be it making them happen or participating. We'll cover topics like speaking, managing attendees, growing your meetup, and many more. 3 | 4 | ## Table of Contents 5 | - [Meetups](#meetups) 6 | - [Why Meetups are Important](#why-meetups-are-important) 7 | - [Starting a Meetup](#starting-a-meetup) 8 | - [Promoting your Meetup](#promoting-your-meetup) 9 | - [Looking for Speakers](#looking-for-speakers) 10 | - [Meetup Logistics](#meetup-logistics) 11 | - [Staying Consistent](#staying-consistent) 12 | - [Meetup Management Resources](#meetup-management-resources) 13 | 14 | - [Speaking](#speaking) 15 | - [Getting Past Imposter Syndrome](#getting-past-imposter-syndrome) 16 | - [Looking for Conferences](#looking-for-conferences) 17 | - [Creating a Proposal](#creating-a-proposal) 18 | - [Creating Slides](#creating-slides) 19 | - [Giving your talk](#giving-your-talk) 20 | - [Speaking Resources](#speaking-resources) 21 | 22 | - [General Event Resources](#general-event-resources) 23 | 24 | 25 | ### Meetups 26 | #### Why Meetups are Important 27 | Meetups are an amazing way for anyone to build a relationship with their local developer community. These are events often held monthly where people in the same location come together to chat, meet people with similar interests (as meetups are usually centered around a particular tool, technology, or product). Attending meetups has some amazing benefits both for organisers and attendees. 28 | 29 | For attendees... 30 | - It's an amazing place to meet people! You get to meet people of all experience levels and have amazing conversations. 31 | - You learn so much - from fellow attendees and speakers alike. 32 | - You get job opportunities. Either through referrals or general advertising, meetups are a great place to start that job hunt. 33 | 34 | For organizers... 35 | - You get to grow your local developer community. 36 | - As much as you're part of the team making things happen, you're also part of the meetup and learning so much. 37 | - You get to expand your network. 38 | 39 | 40 | #### Starting a Meetup 41 | 42 | Starting a meetup is a great choice to have made. Bear in mind that consistency is key. Put together a meetup title, description, and get a few invites out. You should have an idea of what your first session should look like and who will speak at it then you're good to go. 43 | 44 | #### Promoting your Meetup 45 | 46 | As with many things, you have to promote your meetup so that it can reach as many people as it can. People in your area interested in topics discussed at your meetup should be able to find it. Here is a list of places where you can do just that. 47 | 48 | - [Meetup.com](https://www.meetup.com/) - Handles Promotion, communication and discussions. 49 | - [Eventbrite](https://www.eventbrite.com/) - Handles Promotion, attendee registration and check-in. 50 | 51 | #### Looking for Speakers 52 | At the core of your meetups are the sessions people give, because of this, speakers to give these sessions and talks are really important. It's good practice to open up a call for papers so people in your community can submit sessions to speak. Meetups are also a really good place for people to get started with public speaking so making the sessions open for beginners to apply is a really good initiative - as a meetup organiser, you should actively help and encourage first-timers. 53 | 54 | It is also encouraged to invite speakers from other communities by posting your meetups call for papers on sites like [PaperCall.io](https://www.papercall.io/), [Twitter](https://twitter.com), or [Meetup.com](https://www.meetup.com/) 55 | 56 | #### Meetup Logistics 57 | 58 | Quite a bit goes into making sure meetups go on as smoothly as possible. Here's a quick overview that applies to both online and offline meetups. 59 | 60 | - Introduce yourself as the meetup host 61 | - Point out the Code of Conduct; it makes it clear how people should behave and what happens if they don't 62 | - Give an outline of the agenda for the event 63 | - Introduce the speaker 64 | - Gather feedback at the end 65 | 66 | #### Staying Consistent 67 | Developers love consistency (according to this book I read), so to properly grow your meetup and keep your community engaged, you have to be consistent. Consistency means having a set schedule for meetups, meeting on the same of the week at uniform intervals. Consistency in branding and topic focus plays a huge part too. Do keep in mind that being consistent doesn't mean being boring. You don't want your community expecting the same things every time you gather. 68 | 69 | ### Meetup Management Resources 70 | - [Enter The World of Technical Meetups](https://www.codingame.com/blog/enter-the-world-of-technical-meetups/) 71 | - [Marketing/Developer/Meetups HOWTO](https://wiki.mozilla.org/Marketing/Developer/Meetups_HOWTO) 72 | - [Building BrooklynJS](https://github.com/jed/building-brooklynjs) 73 | 74 | ### Speaking 75 | Speaking be it at conferences or meetups is an amazing way to share your knowledge while interacting with the developer community. Speaking like most activities in the resource comes with its benefits. 76 | 77 | - Your build your credibility as a developer and field expert 78 | - If you want to, it's a great way to build your following 79 | - You get to impart knowledge to your fellow community members 80 | 81 | > If you have issues with approaching people to chat, it makes starting interactions easier as usually you get approached first. 82 | 83 | #### Getting Past Imposter Syndrome 84 | [Imposter Syndrome](https://en.wikipedia.org/wiki/Impostor_syndrome) is something speakers of all experience levels face. Most people question whether or not they are good enough to give a talk. Everyone is! What makes talks and sessions special are that everyone has their perspective of things and being able to package that as a talk will give an audience a fresh view of any topic. So yes, you are good enough to give that talk. 85 | 86 | #### Looking for Conferences 87 | Looking for conferences, (or meetups) to speak at isn't an easy task. 88 | 89 | - [Tulula](https://tulu.la/) 90 | - [PaperCall](https://www.papercall.io/) 91 | - [CFPLand](https://www.cfpland.com) 92 | 93 | 94 | #### Creating a Proposal 95 | Once you've found an event to speak at, unless you've been invited to speak (most times even if you've been invited) you're going to have to prepare a talk or session proposal. 96 | 97 | Topics can be hard to come by, a good place to start with topics is asking yourself one or more of these questions. 98 | - What am I passionate about? *Mechanical Keyboards? Give that talk* 99 | - What have I recently learned that could be great to share? 100 | - What lessons have a learned from a recent experience? 101 | 102 | Some tips for crafting a winning proposal? 103 | - Read the submission form to get a feel of what the event wants. 104 | - Look at talks accepted in the past 105 | - Submit a talk as soon as you can 106 | 107 | #### Creating Slides 108 | 109 | It's possible to give a great talk without, slides. Slides do however help people follow your point. Here are some tips and pointers to remember as you go about creating slides for your talk. 110 | 111 | - Think about accessibility and keep in mind slide contrast 112 | - Make your font size big enough to be readable from the back 113 | - Keep your presentation at one idea slide 114 | - Don't distract the audience with too much text or imagery 115 | - Don't fill your slides with code 116 | 117 | This article titled [How to Take Your Talk Slides to the Next Level](https://www.welcometothejungle.com/en/articles/btc-talk-slides-conference) is a great resource and guide to supplement the points above. 118 | 119 | #### Giving your talk 120 | 121 | Practice makes perfect, the first part of giving your talk is practicing it. It makes for a better live presentation. As you go on and give your talk, make sure you're hydrated and have some water near you. Sipping water during your talk is a great way to pace yourself, stay hydrated, and also make sure you're not out of breath as you speak. 122 | 123 | As you start your talk, it's okay to be nervous.. don't worry you're doing amazing. Make sure to add an activity to your talk that can take some of the nerves away. Good ideas are engaging the crowd, adding a meme to your slides (my personal favourite), or putting on your lucky socks and telling the audience about - anything to make you comfortable. 124 | 125 | Make sure to ask the audience for feedback - it's always nice to see areas of your talk that could be better. 126 | 127 | ### Speaking Resources 128 | - [5 Ways to Make Your Tech Talk Awesome](https://medium.com/agatha-codes/5-ways-to-make-your-tech-talk-awesome-885d4eb4a3b6) 129 | - [A Short Guide To Public Speaking (for Tech Conferences)](https://medium.com/@mr_mig_by/a-short-guide-to-public-speaking-for-tech-conferences-9130b17af013) 130 | - [Speaker.io](https://speaking.io/) 131 | - [How to give a tech talk without people leaving](https://hackernoon.com/how-to-give-a-tech-talk-without-people-leaving-355a3942dc49) 132 | - [Want to speak at tech conferences? Here’s everything you need to know to get on stage](https://thenextweb.com/podium/2019/08/19/want-to-speak-at-tech-conferences-heres-everything-you-need-to-know-to-get-on-stage/) 133 | ### General Event Resources 134 | - [How to Give a Killer Presentation](https://hbr.org/2013/06/how-to-give-a-killer-presentation) -------------------------------------------------------------------------------- /Forums and Discord/README.md: -------------------------------------------------------------------------------- 1 | # Forums and Slack 2 | 3 | Information on everything community, this guide includes information on how to go about engaging and speaking with fellow community members, handing bad actors, creating safe and inclusive spaces as well as driving the right conversations. 4 | 5 | ## Table of Contents 6 | 7 | - [Developer Communities](#developer-communities) 8 | - [Understanding Developer Communities](#understanding-developer-communities) 9 | - [Understanding Community Interaction](#understanding-community-interaction) 10 | - [Creating Inclusive Communities](#creating-inclusive-communities) 11 | - [Why we use Discourse](#why-we-use-discourse) 12 | - [Why we use Slack](#why-we-use-slack) 13 | - [Conflict Resolution](#conflict-resolution) 14 | - [General Community Resources](#general-community-resources) 15 | 16 | ### Developer Communities 17 | 18 | Loosely defined, a community is a group of people who gather in a space (online or offline), brought together by a common entity - either a goal, product, tool, or cause. Developers usually form communities around tools they use. You can have a Community of people who use a project like [Strapi](https://strapi.io) or people who have a passion for a a certain architecture like [Jamstack](https://jamstack.org). 19 | 20 | #### Understanding Developer Communities 21 | 22 | Going forward from our definition of a community, we can say that a developer community is one that followers said definition with the exception that many if not all members are developers. People talk about the uniqueness of the developer archetype, their love for dark mode and unsweetened black coffee. To understand developer communities, we can start from acknowledging that they are human who have a diverse set of characteristics and behaviors. 23 | 24 | As we approach developer communities, we must go about it as we would any other person. With ... 25 | 26 | - Empathy 27 | - Respect 28 | - Kindness 29 | - Honesty 30 | 31 | and I say all this to dispel the various stereotypes that have plague developers. 32 | 33 | #### Understanding Community Interaction 34 | 35 | I really love this quote from an article on [The Verge](https://www.theverge.com/2020/4/1/21202748/community-managers-video-game-development-reddit-discord-twitter) 36 | 37 | > Community management brings a lot of compassion into technology. 38 | 39 | I love it even more because it builds on my explanation of treating developers as you should treat every other human. 40 | 41 | #### Creating Inclusive Communities 42 | 43 | Inclusion here means giving your community a space that makes every member feel valued, respected and takes away any hindrances that might make them feel too uncomfortable to contribute in a way that is meaningful to them and the rest of the community. Inclusion means everyone feels free to be their authentic selves free from judgement and harassment. This is very important when creating communities. 44 | 45 | Code of Conducts play such a huge role in making sure a safe space is created and members are respected. 46 | Mozilla has a very useful set of [Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/) they are a reference point for many communities. It is important to note that creating a code of conduct is one thing, enforcing it is another. A code of conduct is only as strong as it is enforced and it is in it's swift enforcement where we can create inclusive spaces for our communities. 47 | 48 | You can find the Strapi [Guidelines here](https://forum.strapi.io/faq#guidelines). 49 | 50 | **Tackling Our Unconscious Bias** 51 | 52 | We all have some sort of bias that we've picked up a we've gone through life - be it from our upbringing, environments, culture or religion. These biases dictate who we are and how we view and understand the word around us. It is important that we recognize these biases we carry and the role they play in the way we interact with and communicate with people. This form of self awareness is important as we go about interacting with people in our community. 53 | 54 | #### Why We Use Discourse 55 | 56 | We made a move to switch some of our community support and interaction from Slack and GitHub Discussions to Discourse. Discourse, as a forum software, provide a technical benefit to the users in our community by making the collective community knowledge more accessible. The root goal of the forum is to provide a simple place to ask questions and gather answers while also being inclusive of those who join the community many months after the question was asked/answered. 57 | 58 | We migrated to Discourse from GitHub discussions in late 2020 in order to build out a tool with more potential ability than GitHub discussions could offer us. With the intent of expanding it's usage far beyond just the general Q&A. 59 | 60 | 61 | #### Why We Use Discord Now 62 | 63 | After using Slack since the beginning of Strapi in 2016, it was finally shutdown on the 14th of June due to some limitation; we have moved the community to [Discord](https://discord.strapi.io). Read more on this [here](https://strapi.io/blog/migrating-our-community-chat-from-slack-to-discord). 64 | 65 | 66 | #### Conflict Resolution 67 | 68 | Nothing highlights the need for a Code of Conduct like a violation of it in the form of conflict. As mentioned above, enforcing your Code of Conduct is very important as it goes a long way towards creating an inclusive space. You must do your best to act in a manner that will defuse the situation while enforcing the Code of Conduct. It is also important to have a section in your Code of Conduct that highlights actions to be taken in situations of conflict. That and the mention of key contacts who can manage the situation should it be beyond your control make managing and resolving conflict better. 69 | 70 | ### General Community Resources 71 | 72 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2020 Strapi 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ![Strapi Resources banner](/assets/community-resources.png) 2 | As part of our commitment to give back to our Community, having noticed the various ways our community are coming together to make the Strapi Project a success - we've put together this resource to help members of the developer community contribute to open source projects outside of just code contributions. 3 | 4 | For Strapi, we've seen non-code contributions in the following ways. 5 | - Issues, Bug Reports and Project Discussions in our [forum](https://forum.strapi.io) 6 | - Articles and videos as part of the [Write for the Community Program](https://strapi.io/write-for-the-community) in our [Community Content Repo](https://github.com/strapi/community-content) 7 | - Meetups Around the world as part of our [Global Meetup Program](https://github.com/strapi/strapi-meetups) 8 | 9 | There's so much activity in these areas and we want to make it so that anyone looking to start contributing can start through this resource. 10 | 11 | ## Table of Contents 12 | 13 | - [Resources](#resources) 14 | - [Contact](#contact) 15 | - [Code of Conduct](#code-of-conduct) 16 | 17 | 18 | ### Resources 19 | If you've been wanting to contribute to open-source but feel you don't know how to. This resource is for you <3 . Below is a list of the resources with a link to page where you can find them. 20 | 21 | 1. [Content and Writing](https://github.com/strapi/community-resources/tree/master/Content%20and%20Writing) - Information on everything content, this includes guides and content on how to create, manage and promote resources you create.. 22 | 2. [Events and Meetups](https://github.com/strapi/community-resources/tree/master/Events%20and%20Meetups) - Information on everything events be it making them happen or participating. We'll cover topics like speaking, managing attendees, growing your meetup and many more. 23 | 3. [Forums and Discord](https://github.com/strapi/community-resources/tree/master/Forums%20and%20Discord) - Information on everything community, this guide includes information on how to go about engaging and speaking with fellow community members, handling bad actors, creating safe and inclusive spaces as well as driving the right conversations. 24 | 4. [Strapi Project Contribution](https://github.com/strapi/community-resources/tree/master/Strapi%20Project%20Contribution) - Information on everything open source, this will be an entry level guide into getting started with contributing to the Strapi project. This covers both code and documentation. 25 | 26 | 27 | ### Contact 28 | If you need the help of the Strapi team a good first step would be to email Daniel on daniel.phiri@strapi.io. 29 | 30 | 31 | ### Code of Conduct 32 | 33 | As Strapi Community representatives, we expect you to follow and abide by our [Code of Conduct](https://forum.strapi.io/faq). 34 | -------------------------------------------------------------------------------- /STRAPI_STARS.md: -------------------------------------------------------------------------------- 1 | # Strapi Stars 2 | 3 | 4 | This serves as a store of all the Strapi Stars and their areas of expertise. 5 | Find out more about the [Strapi Stars Program](https://strapi.io/community-stars). 6 | 7 | 8 | | Name | Forum Username (optional) | Talk to me about | Strapi Concepts I Know | Activities I like | 9 | | ----------- | ----------- | ----------- | ----------- | ----------- | 10 | | Abdón Rodríguez Davila | abdonrd | JavaScript, Web Components, Strapi, open source | Models, Controllers, services | Learn, code, travel and food | 11 | | Daniel Madalitso Phiri | malgamves | Vue.js, GraphQL, Nuxt, Strapi, Vuex, Communities, Music (Techno) | Integrations, Controllers | Speaking, Writing, Testing | 12 | | Thibaut DAVID | Stun3R | Vue.js, Nuxt.js, Strapi, Qovery, @nuxtjs/strapi, SDK, Tailwindcss, Slackline, Drums, Disney | Integration, Hooks, Custom Controllers, All basics concepts | Package & Plugin development, Code Contributions, Speaking | 13 | | Boaz Poolman | boaz | React, React-Native, Drupal, Strapi plugins, Open-Source, CI, CSS, WCAG, Responsive design, Skateboarding, Surfing, Traveling | Plugins, Controllers, Services, Models, Queries, Routing, RBAC, Migration | Plugin development, Testing, Speaking | 14 | | Monico Moreno | mam1028 | NodeJs/Javascript, ReactJs, Strapi, WebDev | Strapi 101, Custom Starters, Custom Controller Logic, etc. | [Training Videos](https://strapi.training), Social Media Interactions, (future) Code Contributions, Strapi Forum Contributions, etc. | 15 | | Precious Luke | localhost_101 | NodeJS, ReactJS Strapi, Golang, Open Source | Strapi101, Integration, Deployment, Policies/Controllers | Writing, Speaking, Rapping | 16 | | Saad Mujeeb | Saad_Mujeeb | NodeJS, Vue.js, Nuxt, Flutter, Strapi, Content-Modelling, Python, Odoo | Strapi101, Integration with any platform, Deployment, Hooks, Controllers, Migrations, Basic to Intermediate Concepts | Code Contribution, Plugin Development, Speaking, Training Videos, Help channel Contributions | 17 | | Ukpai Ugochi | hannydevelop | JavaScript, Strapi, Rust | Strapi101, Deployment, Controllers | Writing, Speaking, Coding | 18 | | Ben Henning | benhenning10 | Next.js, ReactJS, C#, VB.NET, GraphQL, Strapi, Tailwind, CSS, Responsive Design, Gaming, Music (Rock) | Strapi101, Integrations, Custom Starters, Deployment, Docker | Speaking, Writing, Testing, Translating, Code Contributions, Support | 19 | | Mattias van den Belt | MattieBelt | Node.js, Javascript, React, React Native, Strapi, Algolia | Customization, EE & RBAC, Testing, Package development, everything just not GraphQL | Package development, Code contributions, Helping Discord & Forum | 20 | | Joris Witteman | jorisw | JavaScript, TypeScript, React, React Native, Strapi, Node.js | Models, Controllers, Hooks, Services, Queries, GraphQL, Policies, Plug-ins, Middleware | Software Design & Development, Guitar, Arts, Travel, Movies | 21 | | Gabriela Zifferman | gabyzif | HTML5/CSS3, JavaScript, React, Strapi, Web Design | Strapi101, Deployment, Controllers, Hooks, Services, Models, Queries, Routing, | Drawing, Make-up, Coding, Speaking, Travelling | 22 | | Diane Guillot | Leiksa | Vue.js, Nuxt.js, Strapi, Tailwindcss, HTML5/CSS3, Web Design, Video Games, Disney | Basics concepts, Draft & Publish, Relation | Design, Coding, Travelling, Playing video games, Movies | 23 | | Simen Daehlin | Eventyret | Docker, Angular, Strapi, Typescript, HTML5/CSS3, Video Games | CLI tools, Plugin design, System Design, Scalability,Basics concepts | Coding, Trophy Hunting (PSN), Playing video games, Movies, Automation | 24 | -------------------------------------------------------------------------------- /Strapi Project Contribution/README.md: -------------------------------------------------------------------------------- 1 | # Strapi Project Contribution 2 | 3 | Content on how to get start contributing to Strapi will live here. Coming soon... 4 | -------------------------------------------------------------------------------- /assets/community-resources.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/strapi/community-resources/0abbf899f3a034abba82388bc3804ead1a9179ef/assets/community-resources.png --------------------------------------------------------------------------------