Posting on FAUN: Guidelines

TLDR:

FAUN is an open space for individuals and organizations in software engineering and technology to share blog posts, links, jobs, events, and more. Companies are recommended to have a personal account and create an organization page to add colleagues' content. Accepted post types include blog posts, tutorials, expert roundups, and more, but promotional content is not accepted except for educational articles with a single call to action at the end. In-article linking is allowed under certain guidelines. Best practices include using proper headings, code snippets, and photos with sources and descriptions.

FAUN is an open space where individuals and organizations, in the software engineering and technology space, can share:

• Blog posts
• Links
• Jobs
• Events
• and more!

We want to keep FAUN a good place for software engineers to learn and contribute.

Who can Post on FAUN

FAUN is open to all contributors. We accept contributors from developers, engineers, architects, executives (CTOs, CEOs, CIOs..etc), developer advocates..etc

Are you a company? Read This:

If you are a company, instead of creating an account using the company name, we highly recommend the following:

• One of your engineers, developers advocates, or content specialists creates a personal account on FAUN.
• Create an organization page for your company
• Add your colleagues to the organization
• Your colleagues' content as well as your content will appear on your organization page. (These are some examples: The Chief I/O, FAUN, ..etc)

What to Post

There are many post types we accept including and not limited to:

• Blog posts
  • Lists (e.g., examples, tips, tools, tactics).
  • Tutorials, how-to articles/guides.
  • Explainer posts (e.g., what is…/why x matters).
  • Expert roundups.
  • Thought leadership.
  • A solution to problems in software engineering
  • Podcast transcripts
• Links
  • Links to useful articles, tools, tutorials, and news from the Internet.

Always try to go beyond the basic/obvious concepts. Share your personal thoughts and opinions, you can rely on other thought leaders' opinions and quote them.

Your post should be written in English.

What not to Post

We follow Google's content policy and we do not accept any content (web pages, images, videos, news content, or other material) that violates it.

No pitches and promotional posts.

If you are writing to promote your product, refer to the next section ("Using call to Action").

If you are writing to increase your domain authority, build links, or for any SEO purpose, refer to the "In-article Links" section.

Using Call to Action

Note that articles with the unique goal of promoting your products are not accepted.

Only educational articles are accepted, but you can add a single call to action at the end of the article if it accepts our general guidelines.

Examples:

• You wrote a book about technology. You can write an article explaining how to use that technology and add a single call to action at the end.
• You have training about using a tool. You can share a part of your training in the article then add a single call to action at the end.
• You work for a company and want to talk about the product. Write about the problem that your product solves, the different tools to solve it and then add a single call to action at the end of your article to use your product.
• ..etc

These are just some examples, there are more use cases, but remember two things:

1. Before the getting, comes the giving.
2. A single call to action (link to your content) at the end of your article is allowed.

If you want to post to reach a larger audience and promote your product/service, please get in touch with our sales team (clients@faun.dev).

In-article Links

Linking in your article must respect these guidelines:

You can't:

• Link to a page of your website for SEO purposes.
• Link to gated/paywalled content.
• Sell links on articles you wrote on FAUN.

You can:

• Link to a page of your website if it's enriching the post.
• Link to third-party authoritative sources.
• Link to your original article if it's crossposted, but we do not recommend this since you can use your editing dashboard to mention the original article and this will automatically add a canonical tag to the page. The link to your original source will appear at the top of the blog post when it's published.

We reserve the right to delete your link, post, or account when our guidelines are not respected.

Posting Best Practices

Titles

• Use H2 headings for your subheadings.
• Use H3 headings for sections within your subheadings.
• Use H4 to go to another deeper level.
• Use bold if you need to go deeper than H4.

Code snippets

You have the choice to use inline code snippets or separated code block snippets.

We recommend using the first type if your code is one line.

If it's multi-line, use the second option.

Choose the programming/markup language to add syntax color highlights to the code. If you don't find the language you are using, please reach out to support@faun.dev

Photos

Please do not use free stock photos with watermarks. You can download free stock photos without watermarks from Unsplash. Make sure you are not using a copyrighted image. Add your image source if it's necessary.

Add a caption and a description to your images (using the image upload dialog)

To Summarize

Following our guidelines is not rocket science, therefore, we reserve the right to edit, update or delete certain parts or the whole post if the guidelines are not respected.

If you are here to share your knowledge with the community we welcome you.

If you are here to promote a product, give before you take, create an educational post, then add a single call to action, that's alright.

If you're building links for SEO, you're most likely to have your article updated or refused and your account deleted if you are a spammer.

If your use case falls outside the use cases mentioned above, we offer different sponsorship opportunities for companies and individuals who want to promote their services and products (weekly newsletter, sponsored content..etc), you can get in touch with our sales team (clients@faun.dev).

If you have any questions about writing or becoming a contributor, please email community@faun.dev