Join us

Posting on FAUN.dev(): Guidelines

TL;DR:

FAUN.dev() is an open platform for sharing educational and high-quality content related to software engineering and technology. We welcome blog posts, tutorials, links, jobs, and events, but we do not accept low-effort, promotional, or SEO-driven content.


Educational articles are prioritized. Promotional content is allowed only when it provides real value and includes a single call to action at the end. Posts created mainly for link building, domain authority, or off-topic promotion will be deprioritized or removed.


What Is FAUN.dev()?

FAUN.dev() is an open space where individuals and organizations in the software engineering and technology ecosystem can share:

  • Blog posts
  • Tutorials and guides
  • Links to useful resources
  • Jobs
  • Events
  • Podcasts and transcripts
  • And more

Our goal is to keep FAUN.dev() a trusted learning platform for software engineers and practitioners.


Who Can Post on FAUN.dev()?

FAUN.dev() is open to all contributors, including:

  • Developers and engineers
  • Architects and technical leads
  • DevOps, SREs, and platform engineers
  • Executives (CTOs, CEOs, CIOs, etc.)
  • Developer advocates and educators

If you have something valuable to teach or share, you’re welcome here.


Are You a Company? Read This First

If you represent a company, do not create an account using the company name.

Instead, we strongly recommend the following setup:

  1. One of your engineers, developer advocates, or content specialists creates a personal account
  2. Create an organization page for your company
  3. Add colleagues to the organization page

All content published by your team will then appear on your organization page (for example, FAUN.dev()).

This keeps the platform human-first and avoids turning it into a company RSS feed.


What to Post

We accept many types of content, including but not limited to:

  • Blog posts
  • Tutorials and how-to guides
  • Lists (tools, tips, examples, tactics)
  • Explainer posts (what is X, why X matters)
  • Expert roundups
  • Thought leadership
  • Practical solutions to software engineering problems
  • Podcast transcripts
  • Links to useful external resources

Guidelines to keep in mind:

  • Always aim to go beyond obvious or introductory content
  • Share personal experience, insights, or opinions
  • You may quote or reference other thought leaders
  • All content must be written in English

What Not to Post

We follow Google’s content policies and do not accept content that violates them.

Additionally, we do not accept:

  • Pure promotional or sales pitches
  • Low-effort content created mainly for SEO or backlinks
  • Off-topic submissions unrelated to software engineering or technology

If your goal is promotion, read the next sections carefully.


Using a Call to Action (CTA)

Articles written only to promote a product, service, or company are not accepted.

However, educational articles may include a call to action preferrably at the end of the post.

Examples of acceptable use:

  • You wrote a technical book → write a practical article and add one CTA at the end
  • You offer training → share real educational content, then add one CTA
  • You work on a product → explain the problem space objectively, compare solutions, then add one CTA

1 rule to remember: before getting comes giving

If you want broader promotional reach, contact our sales team at clients@faun.dev.


In-Article Links

Links inside articles must follow these rules.

You can’t:

  • Add links purely for SEO or link building
  • Link to gated or paywalled content
  • Sell links on articles published on FAUN.dev()

You can:

  • Link to your own content if it adds value to the article
  • Link to authoritative third-party sources
  • Cross-post your article and reference the original source

Note: Instead of linking manually to the original article, you can use the editor to declare the original source. FAUN.dev() will automatically add a canonical tag and display the source at the top of the post.

We reserve the right to remove links, posts, or accounts that do not follow these rules.


Posting Best Practices

Titles and Headings

  • Use H2 for main sections
  • Use H3 for subsections
  • Use H4 for deeper structure
  • Use bold text if you need a level deeper than H4

Code Snippets

  • Use inline code for single-line snippets
  • Use code blocks for multi-line examples
  • Always specify the language for syntax highlighting
  • If a programming language is missing, contact support@faun.dev

Images and Photos

  • Do not use images with watermarks
  • Ensure images are not copyrighted
  • Free sources like Unsplash are acceptable
  • Add captions and descriptions using the image upload dialog
  • Include image credits when required

To Summarize

Following these guidelines is straightforward.

  • Educational content is welcome and prioritized
  • Promotional content must give value first
  • SEO-driven or spammy posts will be edited, rejected, or removed
  • Accounts used mainly for link building may be deleted

If your goal is to share knowledge, you’re welcome here.
If your goal is to promote, give first, then ask once.
If your use case doesn’t fit these rules, we offer sponsorship options (newsletter, sponsored content, etc.).

For questions about contributing or writing on FAUN.dev(), contact community@faun.dev.