🌐 Add french language
Add french language
This commit is contained in:
Thomas Betous
parent
3d5fe1edeb
commit
c49d2b64d4
248
README-fr.md
248
README-fr.md
|
|
@ -1 +1,247 @@
|
|||
<h1 align="center">Comment promouvoir mon projet open-source? 🚀</h1>
|
||||
<p align="center">
|
||||
<img alt="oss image" src="./imgs/zoss-logo.svg" height="200px" width="200px">
|
||||
</p>
|
||||
|
||||
<p align="center">
|
||||
<a href="https://twitter.com/intent/tweet?text=How%20to%20promote%20your%20open-source%20projects&url=https://github.com/zenika-open-source/open-source-promotion-cheat-sheet&hashtags=OpenSource,CheatSheet">
|
||||
<img alt="tweet" src="https://img.shields.io/twitter/url/https/twitter?label=Share%20on%20twitter&style=social" target="_blank" />
|
||||
</a>
|
||||
</p>
|
||||
|
||||
<h1 align="center">Open source promotion cheat sheet </h1>
|
||||
|
||||
> Ce cheet sheet résume les étapes importantes à suivre pour promouvoir un projet open-source dans les meilleurs conditions. Il est possible d’afficher des informations supplémentaires pour un élément de la liste en cliquant dessus.
|
||||
|
||||
Liste de langages disponibles :
|
||||
|
||||
- [English](./README.md)
|
||||
- [Français](./README-fr.md)
|
||||
|
||||
Un langage est manquant ? Vous pensez qu'il est possible d'améliorer ce cheat sheet ? [Les contributions sont les bienvenues](./CONTRIBUTING.md) !
|
||||
|
||||
## 1. 🎢 Etape de préparation
|
||||
|
||||
<br />
|
||||
|
||||
<details>
|
||||
<summary>😎 Choisir un bon nom de projet</summary>
|
||||
<p>
|
||||
|
||||
> Choisissez un nom que les utilisateurs pourront facilement retenir.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>💅 Soigner la présentation du README</summary>
|
||||
<p>
|
||||
|
||||
> Le README est la première choses que les visiteurs verront sur la page de votre projet. Soignez la présentation pour qu'elle soit simple, jolie et agreable à lire. [Vous pourrez trouver des bons exemples en cliquant ici.](https://github.com/matiassingers/awesome-readme)
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>💪 Mettre en avant les points fort du projet</summary>
|
||||
<p>
|
||||
|
||||
> Identifiez les points forts de votre projet et mettez les en avant de manière à ce qu'il soit perçu en priorité par vos utilisateurs.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>✨ Fournissez une démo du projet</summary>
|
||||
<p>
|
||||
|
||||
> 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
|
||||
|
||||
> Vos visiteurs voudront rapidement comprendre les tenants et aboutissements de votre projet. Comment ça fonctionne et comment l'utiliser. Fournir une démo est une excellente manière de satisfaire vos visiteurs. La démo peut être sous forme :
|
||||
>
|
||||
> - d'un GIF demontrant comment le projet fonctionne
|
||||
> - d'un lien vers un démo en ligne
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>👌 L'installation doit être simplissime</summary>
|
||||
<p>
|
||||
|
||||
> Vous perdrez probablement vos visiteurs si votre projet n'est pas simple à installer.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>📘 Creer un documentation soigner et bien structurer</summary>
|
||||
<p>
|
||||
|
||||
> 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](https://v1.vuepress.vuejs.org) helps you creating clean documentations in a simple way.
|
||||
|
||||
> Creer un bonne documentation est probablement l'étape la plus importante. Si vous avez une petite documentation il vous sera possible de l'inclure dans votre README. Si celle-ci est volumineuse, le mieux sera de l'extraire vers une application web séparée. Certain projets open source comme [vuepress](https://v1.vuepress.vuejs.org) peuvent vous aider à très vite créer un documentation propre et efficace.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<br />
|
||||
|
||||
## 2. 📢 Spread the word about your hard works
|
||||
|
||||
<br />
|
||||
|
||||
<details>
|
||||
<summary>⭐ Make your project trustable before publishing to social networks</summary>
|
||||
<p>
|
||||
|
||||
> 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.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>↗️ Share the project on social medias an specialized platforms</summary>
|
||||
<p>
|
||||
|
||||
> Tell the world about your awesome work! Publish on social medias and specialized platforms:
|
||||
>
|
||||
> - [Twitter](https://twitter.com)
|
||||
> - [Linkedin](https://www.linkedin.com/)
|
||||
> - [Facebook](https://www.facebook.com/)
|
||||
> - [Reddit](https://www.reddit.com/)
|
||||
> - [Dev.to](https://dev.to/)
|
||||
> - [Lobsters](https://lobste.rs/)
|
||||
> - [Hacker News](https://news.ycombinator.com/)
|
||||
> - [Product Hunt](https://www.producthunt.com/)
|
||||
> - [Beta page](https://betapage.co/)
|
||||
> - [Human Coders](https://news.humancoders.com/)
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>📃 Write articles that mention your project</summary>
|
||||
<p>
|
||||
|
||||
> 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:
|
||||
>
|
||||
> - [medium](https://medium.com/)
|
||||
> - [dev.to](https://dev.to/)
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>🎤 Present your project at conferences/meetups</summary>
|
||||
<p>
|
||||
|
||||
> Presenting your project at conferences or meetups is a good way to improve its visibility.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>🎥 Record and publish videos presenting your project, how it works, etc
|
||||
</summary>
|
||||
<p>
|
||||
|
||||
> Recording a video is not an easy execise. However it's probably the most efficient way to make your project famous.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>🕐 Choose the best time to publish on social medias</summary>
|
||||
<p>
|
||||
|
||||
> Don't publish during holidays period or weekends. Usually the best time to publish on social networks is mid-week.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>🗑 Don't spam platforms with your promotion</summary>
|
||||
<p>
|
||||
|
||||
> Don't publish twice on the same platform. It will be considered as spam and might cause bad publicity for your project.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<br />
|
||||
|
||||
## 3. 🤝 Keep your users
|
||||
|
||||
<br />
|
||||
|
||||
<details>
|
||||
<summary>🆕 Try to regularly release new versions of your project</summary>
|
||||
<p>
|
||||
|
||||
> Maintain and improve your project with new releases and generate changelogs.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>❗ Maintain your project, process opened issues</summary>
|
||||
<p>
|
||||
|
||||
> Do not let opened issues without response. Be nice with people that took time to open issues 😉
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>🙏 Invite users to contribute</summary>
|
||||
<p>
|
||||
|
||||
> 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](https://help.github.com/en/articles/about-labels).
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>🏆 Reward contributors</summary>
|
||||
<p>
|
||||
|
||||
> Be nice with people that helped you! Some open-source projects like [gatsby](https://github.com/gatsbyjs/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](https://twitter.com/FranckAbgrall/status/1139470547492978688)). Open a `Contributors` section in your README to publicly thanks them (ex: [vuepress contributors section](https://github.com/vuejs/vuepress#code-contributors)).
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>💬 Open a community chat platform</summary>
|
||||
<p>
|
||||
|
||||
> Github issues are not always the best way to communicate with your users. If necessary, you can use chat platforms to discuss with them:
|
||||
>
|
||||
> - [Discord](https://discordapp.com)
|
||||
> - [Slack](https://slack.com)
|
||||
> - [Gitter](https://gitter.im/)
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>🔙 Ask for feedback</summary>
|
||||
<p>
|
||||
|
||||
> User's feedback is the best way to improve your project. They probably have features and ideas that could make your project better.
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>❤️ Open a use case gallery to show what users built with your project</summary>
|
||||
<p>
|
||||
|
||||
> Visitors will trust your project if they see concrete use case and success stories (ex: [vuepress gallery](https://vuepress.gallery/)).
|
||||
|
||||
</p>
|
||||
</details>
|
||||
|
||||
<br />
|
||||
|
|
|
|||
Loading…
Reference in a new issue