✏️Write for AppFlowy

Are you an AppFlowy enthusiast? Help other AppFlowy users and builders, get paid, and build your reputation as a writer.

Whether you’re an AppFlowy power user, a software development expert, or just a student starting to get into open source, there is knowledge you can share that will benefit the entire AppFlowy community.

The types of articles we’re currently looking for include:

• How-tos

• Discussions about specific use cases

• Software development related to AppFlowy’s codebase

You will be paid for articles published on AppFlowy Binary and pages posted to the AppFlowy documentation. We pay anywhere between $50 - $350 for content created.

Your work will be published under your name with a link to the relevant social profile of your choosing.

We are also looking for content writers and technical editors with a proven track record to help with style, grammar, and content. Please email your portfolio to [email protected]

How does it work?

Post to Discord About Your Topic

First, join our Discord channel and create a post. Your post should include the topic you want to cover and an outline. The topic can be your own or select an existing GitHub issue tagged with “write-for-appflowy".

Wait for Approval on the Topic

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 the scope and outline of the article to ensure the result is informative and engaging.

We will then create a GitHub issue for the topic and assign the issue to you.

Get Feedback

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.

Publication of Your Article

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

Ongoing support is required. You should promptly respond to queries about your published work. How-to guides should remain up-to-date.

We expect that you will provide support for at least 30 days after your article is published. Future engagements will be contingent on how well existing articles are supported.

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.

What kind of content are we looking for authors?

How-to-Guides

Write a how-to guide explaining one of AppFlowy’s features. This can be from the development or the end-user perspective.

Ideas:

• AppFlowy 101: Introduction to basic functionality

  • Write and edit

  • Database properties

  • Table view

  • Board view

  • Take charge of our data

  • ... more to cover as we ship new features

• Contribute to AppFlowy:

  • How a certain feature is built

  • How to make customizations

  • How to add plugins

Specific Use Cases

Share the specific use cases you have for AppFlowy.

We are eager to know what you use AppFlowy for and how other people can borrow your ideas to gain similar benefits.

Ideas:

• Guides by use cases: write notes, manage tasks, documentation, wiki, engineering...

• AppFlowy for students, product, engineering, personal use...

Engineering Topics

Engineering topics related to AppFlowy always excite us.

We love deep dives or tutorials that lower junior developers' barriers to participating in our open-source projects.

Ideas:

• A guide to contributing with minimal project structure to start working on a feature

• More on the architecture and how to circumvent common pitfalls

• How AppFlowy uses Flutter Bloc

• How Rust and Flutter work through event-driven cooperation

• Reach out annie@appflowy on Discord for more ideas

FAQs

1. Where Do I Share My Drafts?

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.

2. How Much Do I Get Paid?

Categories	Payment
How-to guides for product	$50
How to contribute to AppFlowy	$100
Product use cases	$100
Engineering topics	$100 - $350

3. Can I Cross-Post the Article?

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 in the AppFlowy project.

4. Can I Write in Languages Other than English?

No, unfortunately, content published on our blog is currently in English only.

5. Am I the Right Candidate for a Technical Deep Dive?

You are an experienced developer who has contributed to AppFlowy’s codebase with a deep understanding of its design.

You seek technical excellence and you value collaboration, honesty, and inclusiveness.

6. What Rights Do AppFlowy Claim Over The Article?

After it is published and you have been compensated, your content will become part of the AppFlowy project and will be distributed under its license.

You can cross-post with a canonical link pointing to the original AppFlowy post.

7. How Many Articles Can I Submit Each Month?

There is no limit, and you can create a series if your articles fall under the same topic or theme.