Welcome to the Falco community blog. This blog serves as an educational resource for community members, maintainers, and contributors.
The process is meant to be self-serve but if you experience any difficulties reach out to us at contact us via the Kubernetes Slack on the #falco channel.
TLDR; submit your blog PR here.
Please read and follow the guidelines. Incomplete submissions will be rejected.
Content criteria & guidelines The community thanks you for your interest in contributing content to the Falco community blog. Here are examples of content to create and criteria to follow to avoid rejection.
Articles about Falco
- Technical content and how-to’s
- Stories about cloud-native runtime security + how Falco helped
- Use cases and success stories about Falco
- Industry insight into Kubernetes threat detection and Falco’s role in the ecosystem
- No vendor or product pitches
- Articles about Falco plugins
- Articles about how to write Falco rules
- Industry insight about container security and how to use Falco
- Project updates about Falco
- Reposting is okay, but we will need to do some editing to avoid SEO chaos
Editorial calendar The goal of the editorial calendar is to proactively plan, source speakers, and curate content to the Falco community in a transparent manner. Please review the editorial calendar to understand when your blog will be published.
Suggested themes and topics to write about:
- Falco best practices
- How-to’s about Falco or Falco plugins
- Case studies or success stories about using Falco
- Threat detection best practices
- How to reduce risk via alerts
- Falco out of the box rules
- Falco roadmap & announcements
- Monthly blog style newsletter to the community
- Falco third party event coverage
- Falco announcements
- Review process
Next, the blog editor will review the content for any grammatical errors, spelling mistakes, technical accuracy, and provide feedback. All feedback and collaboration will take place in the Github Pull Request.
Depending on where your blog falls in the queue, editing and publication dates will vary. Blog content is reviewed and published on a first come, first serve basis. This step should take 5 - 7 business days to complete.
The goal is to publish 1 blog per week and the community commits to a 2 week(s) turnaround end to end.
Publishing process
- Depending on the quality of the content & edits needed this process should take 5 - 10 business days.
- Once the editor and contributor are done with the editing process, the blog should publish when the next available slot opens up.
- See editorial calendar
- Community contributed blogs are published on Tuesday & Thursday on a first come, first serve basis.
- The blog content is published on the Falco website - blog.
Submit your PR Now that you understand the content guidelines, editorial calendar, and publishing process you are ready to submit your pull request. All blog content must be submitted through this process to be considered for publication.
- How to submit your first PR blog in 5 easy steps
- Step 1: Fork to the falco-website repo on Github
- Step 2: Clone locally your branch and create a new branch
- Step 3: Create your blog post in markdown format, see other posts as example
- Step 4: Add images to the img folder
- Step 4: Commit your work with a signoff and push to Github
- Step 5: Create your pull request to upstream repo with your changes Filing your first PR? Go here 👉 for step by step instructions
Promoting your blog Finally, once the blog goes live we will promote the content on the Falco twitter handle. We will create 2 different post copies with a social media card and promote over a 2 weeks period.
Be sure to provide a headshot and your social media handles so we can tag you in the post. Don’t forget to share your content with your network too!
Blog content will also be submitted for promotion in the following channels: