Learn how to contribute FinOps knowledge and best practices content to the FinOps Foundation website. Contributions to the Framework and Asset Library help us build FinOps guidance, knowledge, and information to empower one another, and advance FinOps together.
The FinOps Framework is built by the community, for the community, and as such, it is periodically updated to reflect the community’s maturing definition of FinOps and its best practices. We welcome your suggestions that improve, streamline, and simplify components of the Framework.
Framework updates may be simple changes (such as rephrasing), helping us reference the latest industry resources (updating links or references), to more comprehensive proposals (such as adding a new section or changing the contents of a Capability). Framework updates will typically be considered when they materially improve the completeness, accuracy, or clarity of the description.
Contributions are welcome in written format, in whatever length suits communicating your changes. Include diagrams or graphs if that helps better illustrate your idea.
NOTE: FinOps Framework content strives to be cloud, vendor, and organization neutral in almost all cases unless specific references are required to illustrate concepts. Contributions should reflect the latest best practices and concepts as the FinOps Framework is a resource for the entire community to use in order to build and advance their practice.
Practitioners may also contribute content that draws from your FinOps experience. Contributions should help our community and FinOps-adjacent personas better understand how an aspect of FinOps can be performed.
Contributions should be aligned with the FinOps Framework and not be contradictory or confusing by using other concepts. Content submissions can include references to Cloud Providers, products, or tools used, but cannot pitch, recommend or sell any product or service. If the resource was essential to solving your problem, you should name it, but avoid making testimonials.
Individual submissions will be reviewed before they can be published to the most appropriate location on our site.
Papers are detailed write-ups about a Framework capability or concept. Papers typically go into some aspect of a FinOps concept that is not readily apparent or may only apply in certain circumstances, or which may only be experienced by practitioners of a certain type, size, or maturity.
Papers can be long-form, academic reports or whitepapers that offer nuanced interpretations or understandings of an aspect of FinOps.
Use the FinOps Paper Template and include supporting images, figures, graphs, and charts.
Playbooks are prescriptive examples of how you or your organization performs one or more FinOps activities or Capabilities. They are similar to documentation or a “How To” Guide, detailing how you implement the Capability, assess performance, engage your organization, and produce results. The goal of a playbook is to guide someone through the process of “doing” a FinOps task.
Use the Playbook Template and include supporting images, figures, graphs, and charts.
Utilities are resources that other community members can use in their day-to-day FinOps practices. They help other practitioners with FinOps challenges.
We will add content to the Asset Library if it helps address or improve the following:
All content contributions will be reviewed by the FinOps Foundation. We may not be able to use your submission for a variety of reasons. If your content is selected, we will attribute it to you (unless you prefer to remain anonymous).
At the top of each of the asset pages on the FinOps.org website, you will see a button that says “Make Suggestion.” If your contribution is straightforward, you can enter it right there on that form. Please include your contact information so our staff can reach out if they have any questions.
You may compose any of the contributions described on this page into an email or document, and forward it to hello@finops.org. Put “Content Contribution” in the Subject line, and include all the other information requested below.
We can’t wait to see your informative contribution to our community!
Yes! We encourage this as it’s a way for two FinOps Practitioners to “gut check” one another’s assumptions, and help each other refine their work. This often leads to interesting, informative content for our community.
Yes, we welcome these types of improvements. Create a document that contains edits, improvements, and changes to an asset and we will conduct the same review process. In some cases, we may even connect the original author with newer contributors to joint-author something new!
AI-generated content can be used as source material for your contribution so long as it has proper citations to works that the generative AI tool references.
Sometimes individual contributions are ambitious and are best approached and executed with more community members. If you think your concept could use additional contributors and could be a Working Group, get in touch via hello@finops.org.
The Asset Library is mainly a repository of content created by and for the FinOps community. Product and marketing content that has the intent of informing a user to make a purchase is not permitted. However, a case can be made for a vendor-neutral resource that educates and informs the community.
Technology moves quickly and this is always bound to happen. We encourage and welcome any and all contributions, even if they’re as minor as fixing broken links, typos, missing images, and other things that happen as the internet continues to shift and change.
Get in touch with a Community Director (you can start via hello@finops.org). Speaking proposals are reviewed separately from this workflow, but we are always interested in hearing FinOps stories and guidance from our community.
If you’re looking to contribute a Breakout Session or Chalk Talk to FinOps X, please visit the FinOps X site.