📄 Open source promotion cheat sheet
Go to file
Franck Abgrall 8bbcbec8f5
🐛 Fix contributing link (#38)
2019-09-02 09:24:27 +02:00
.github/ISSUE_TEMPLATE 🔧 Add content suggestion 2019-08-23 10:02:44 +02:00
imgs Add logo and contributor section (#19) 2019-08-22 10:04:38 +02:00
.all-contributorsrc 📝 Add ebriand as a contributor (#34) 2019-08-30 23:09:10 +02:00
CODE_OF_CONDUCT.md 💡 Add CODE_OF_CONDUCT and CONTRIBUTING (#10) 2019-08-20 09:35:07 +02:00
CONTRIBUTING.md 🐛 Fix contributing link (#38) 2019-09-02 09:24:27 +02:00
LICENSE Initial commit 2019-08-01 17:34:05 +02:00
README-fr.md 💄 Improve french presentation 2019-08-28 10:50:35 +02:00
README.md 📝 Add ebriand as a contributor (#34) 2019-08-30 23:09:10 +02:00

README.md

oss image

tweet

Open source promotion cheat sheet

This cheat sheet summarize important steps you should follow to promote your open-source project in the best conditions. You can click items to expand and get more information from a topic.

List of availables languages:

A language is missing? Want to improve this cheat sheet? Contributions are welcome !

1. 🎢 Preparation step


👌 Make sure your project is mature enough

Your project must be stable enough with minimum viables features in order to hook users.

😎 Choose a cool name for your project

Choose a name users can easily remember.

💅 Make your README pretty

README is the first thing your vistors will see. Make it simple, pretty and easy to read. Here is a list of beautiful READMEs.

💪 Highlight strong points of your project

Identify your project strengths and make sure visitors see them at first.

Provide a demo of your project

Vistors will want to quickly understand the purpose of your project, how it works and how to use it. Providing a demo is the best way to satisfy users. It could be:

  • An animated GIF demonstrating how your project works
  • A link to a live demo

👌 Install/Usage must be super easy

You'll probably lost visitors if your project is not user friendly.

📘 Create a clean and well structured documentation

Creating a good documentation is probably the most important step. If you have a small documentation, you can include it within your README. Otherwise, you should probably host it in a separate website. Some open-source projects like vuepress helps you creating clean documentations in a simple way.


2. 📢 Spread the word about your hard works


Make your project trustable before publishing to social networks

Most visitors will check how many stars the project got before considering using it. A minimum amount of stars makes your project more trustable than a project with zero star. This is why you should ask people you know to support your project before doing a public announcement on social medias.

↗️ Share the project on social medias an specialized platforms

Tell the world about your awesome work! Publish on social medias and specialized platforms:

📃 Write articles that mention your project

Write articles about your project. Purpose can be the technical stack you used, how your project works, problems you encountered, etc. Post to publishing platforms:

🎤 Present your project at conferences/meetups

Presenting your project at conferences or meetups is a good way to improve its visibility.

🎥 Record and publish videos presenting your project, how it works, etc

Recording a video is not an easy execise. However it's probably the most efficient way to make your project famous.

🕐 Choose the best time to publish on social medias

Don't publish during holidays period or weekends. Usually the best time to publish on social networks is mid-week.

🗑 Don't spam platforms with your promotion

Don't publish twice on the same platform. It will be considered as spam and might cause bad publicity for your project.


3. 🤝 Keep your users


🆕 Try to regularly release new versions of your project

Maintain and improve your project with new releases and generate changelogs.

Maintain your project, process opened issues

Do not let opened issues without response. Be nice with people that took time to open issues 😉

🙏 Invite users to contribute

A healthy project is a project with a community and contributors. Let your users know that you need help by tagging some issues with contribution welcome or good first issue labels. See github labels.

🏆 Reward contributors

Be nice with people that helped you! Some open-source projects like gatsby reward contributors with goodies. If you can't afford that, do a public post (on twitter or other platforms) about the contribution and mention the author (here is an example of public thanks). Open a Contributors section in your README to publicly thanks them (ex: vuepress contributors section).

💬 Open a community chat platform

Github issues are not always the best way to communicate with your users. If necessary, you can use chat platforms to discuss with them:

🔙 Ask for feedback

User's feedback is the best way to improve your project. They probably have features and ideas that could make your project better.

❤️ Open a use case gallery to show what users built with your project

Visitors will trust your project if they see concrete use case and success stories (ex: vuepress gallery).


❤️ Contributors

Thanks goes to these wonderful people:

Franck Abgrall
Franck Abgrall

📖
Thomas Betous
Thomas Betous

📖
Eric Briand
Eric Briand

📖

This project follows the all-contributors specification. Contributions of any kind welcome!