This page is under construction
Are you an AppFlowy enthusiast? Join the Write for AppFlowy program to help other AppFlowy users and builders, get paid, and build credibility.
Whether you’re an expert on software or product or a young student just starting, there is knowledge you can share and benefit the entire AppFlowy community. Topics that would help the community the most at the current stage are how-tos, specific use cases, and software development related to AppFlowy’s codebase. We’re looking for both tutorials and deep dives. You get paid for articles published on AppFlowy Binary and pages posted to the AppFlowy documentation. Your work will be published under your name and a link to your social profile. We pay anywhere between $50 - $350 for content created. We also look for editors with proof of track record to help with style and grammar (link to more details).
- Join our Discord channel and create a post. Your post should include the topic you want to cover and the outline. The topic can be your own or select an existing GitHub issue tagged with “write-for-appflowy”.
- Once you create a post, the AppFlowy team will review it. It may take a few days or weeks for us to review. If we shortlist your topic, we will work with you to refine your outline and agree on an informative and engaging final topic. Then we will create a GitHub issue for the topic and assign the issue to you.
- After you finish the first draft, you are encouraged to get feedback from the AppFlowy team and a few community members who are your article’s target audience. You should be aware that not every submitted article will be published.
- Once your article is reviewed and published on our blog, you can submit your invoice to get paid via Deel. But that’s not all - we’ll also promote your work on our social media channels, providing greater exposure for your work.
- Ongoing support is required. You should promptly respond to queries about your published work. How-to guides should remain up-to-date. We may archive your how-to guides if it’s not up-to-date given that our product is still under rapid development and may evolve pretty quickly.
- Write a how-to guide explaining some of AppFlowy’s features. This can be from the development or the product user perspective.
- Share the specific use cases you have with AppFlowy. We are eager to know what you use it for and how other people can borrow your ideas to get similar benefits you have gained.
- Engineering topics related to AppFlowy always excite us. In particular, we love deep dives or tutorials that lower junior developers' barriers to participating in our open-source projects.
We use GitHub to collaborate. Once your topic is approved, a page will be created for you to work on in this repo. When you are ready to share your draft, submit a pull request to the page. We’ll provide feedback on your pull request. If you are not familiar with GitHub, don’t worry. We’ll guide you through.
| Categories | Words | Payment |
|---|---|---|
| How-to guides | <800 | $50 |
| How-to guides | >800 | $100 |
| Use cases | <1300 | $100 |
| Use cases | >1300 | $150 |
| Engineering topics* | - | $200 - $350 |
- Engineering topics will not be paid by word count; instead, it will depend on your article's technical excellence.
Yes, you can cross-post the article on other platforms like Medium or your blog as long as you can add a canonical link to the article URL.
No, unfortunately, content published on our blog is currently in English only.
You should be an experienced developer who has contributed to AppFlowy’s codebase with a deep understanding of its design. And you seek technical excellence and value collaboration, honesty, and inclusiveness.
AppFlowy claims the blog post piece as our own after it is published and you have been compensated. You can cross-post with a canonical link pointing to the original AppFlowy post.
There is no limit, and you can create a series if your articles fall under the same topic or theme.