Elevating IaC Workflows with Spacelift Stacks and Dependencies 🛠️

Register for the July 23 demo →

Editorial Policy and Guidelines

Spacelift’s collaborative platform for infrastructure as code (IaC) enables DevOps teams to manage complex cloud infrastructures with ease. In line with our reputation as an authority on all things related to IaC management, we pride ourselves on sharing only the most precise, comprehensive, and actionable content related to our areas of expertise. That means we follow strict policies and guidelines to ensure we publish quality, relevant, trustworthy content that delivers a positive user experience. The posts we publish on the Spacelift blog are written by a team of experienced technical experts, fact-checked for accuracy, and edited to ensure they make for an engaging and informative reader experience. Our editorial principles and processes guide the ways in which we source, write, review, and edit our articles.

Our editorial principles

We maintain strict standards against plagiarism and copyright infringement. Our writers are required to create original content that has not been published elsewhere, and we use plagiarism-checking tools to ensure our articles are original. When external sources are referenced or quoted, we provide proper citation and attribution.

All content featured on the blog is up-to-date and correct to the best of our knowledge at the time of posting. We also revisit our published work on a regular basis to make sure it remains current and relevant. 

We believe in the value of clear, objective information and are committed to delivering unbiased, transparent content to our audience.

We encourage our writers to express their unique perspectives while following our content guidelines and upholding a high standard of professionalism.

We deliberately link articles from other trustworthy and reliable sources and documentation to share meaningful content. We do not link to trivial or unreliable websites.

Our editors and designers focus on simplicity and elegance to make each article and every element of our website attractive and user-friendly.

Our editorial process

1. Content planning

Before any blog article appears on the Spacelift blog, our editorial team of industry experts conducts in-depth research and assigns the topic to the most appropriate writer.

2. Writing by industry experts

Spacelift writers are certified industry experts with years of professional experience working with various DevOps technologies. Each of our writers has at least ten years of experience working with technology related to DevOps and IaC, such as Terraform, AWS, Kubernetes, Docker, and Ansible. They hold numerous certifications and qualifications in cloud services, DevOps, FinOps, cybersecurity, and a range of other IT specialties. They are keen to share their insights with our readers and are dedicated to following our internal guidelines to ensure that each content piece is both informative and engaging. Their comprehensive industry experience means most of their content derives directly from their learned experience. They also use a range of authoritative sources to craft their content  — including expert interviews, official web and tech repositories, and other reliable datasets and documents.

3. Technical review

The trustworthiness and accuracy of our content are crucial. That’s why our team of developer advocates reviews the code quality and checks for errors in the technical content before it goes live on our website. Every piece of content is reviewed by at least two engineers. 

4. Quality check

After the technical review, one of our experienced editors reviews each article to monitor the quality of the language and ensure it is engaging for readers. This extends to assessing the overall structure of the article for clarity and completeness.

5. Publishing

Once the written content is approved, we add elements like featured images and custom visuals to make the piece even more accessible and readable. We also conduct a final check of the citations and references included in the article. And we don’t stop there: After a new content piece is published, we check it again to review the quality from a reader’s point of view.

6. Continuous improvement

Our content team routinely revises published articles to ensure that each piece remains fresh, relevant, and accurate. If we do need to modify something, we are transparent about it and add a new “Updated” date to signal the changes. Modifications may include corrections of minor inaccuracies, the addition of new information, updating code examples based on changes to a tool, the insertion of alternative images and sources, or other changes that will improve the value of the content for readers.

Thank you for being a part of our community!