Update README-fr.md
This commit is contained in:
Thomas Betous
GitHub
parent
c49d2b64d4
commit
f6bca80b30
157
README-fr.md
157
README-fr.md
|
|
@ -88,160 +88,3 @@ Un langage est manquant ? Vous pensez qu'il est possible d'améliorer ce cheat s
|
|||
</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