Contribute to Puppet ContentWe know you have something to say – about Puppet, automation, or DevOps – and we want to hear it. Your insights and experience make our community stronger. Get involved and start contributing content using some of the channels below!Write for the Puppet BlogBe On Our PodcastWrite for Puppet's DEV.toWrite for the Puppet BlogCome up with a handy tip or topic about automation, DevOps, or a related subject? Submit it to the Puppet blog!If it worked for you, there’s a good chance it could supercharge someone else’s workflow. We’re big fans of how-to content, tutorials and demos, pertinent information about releases and launches, best practices, and useful stuff you learned while using Puppet.Some guidelines:All content must be original and authored by you. (We'll check.)Puppet retains editorial control over any content published on the Puppet blog.Blog posts must be between 500 and 1,500 words. Talk to us about making your content shorter or longer.We recommend using graphics to make your post more engaging and informative.Ready to draft? Submit your idea to the Puppet marketing team.SUBMIT YOUR IDEA READ PUPPET BLOGSBe On Our PodcastGot a great podcast topic about trends in automation? Send your pitch to be considered for an episode of Pulling the Strings, the official Puppet podcast.Here's what we need from you:Send us a paragraph explaining what you’d like to talk about and what perspectives you’d bring.Include a link to your repo or webpage if you’re talking about a project. Include links to any other podcasts you've been on or presentations you’ve given.If we think it’s a good fit, we’ll ask you to write up a quick sentence or two introducing yourself and some questions you’d like the host to ask or points you want to make sure we mention.About the Pulling the Strings PodcastStructured as casual conversations, episodes of Pulling the Strings run around 30 minutes and are usually technical, but not always. Our hosts are joined by Puppet engineers and community members with a variety of viewpoints on DevOps and other technology trends.Our four “tracks” are:Puppet Labs: This is the “experimental” track. It spotlights wildcard ideas from community members and Puppet employees. The name is a throwback to the old school company name, and nothing here is intended to be a product endorsement.Kicking the Tires: This segment puts new Puppet features and products to the test, and is where new products or releases are introduced. It’s the closest we get to a “product pitch.”Contributor Spotlight: A behind-the-scenes interview with active members of our community and customers who lend their know-how to extending Puppet’s utilization/usability/feature set.Culture: A look at the kaleidoscope of people who make up the Puppet community and what they’re up to. This could be technical, but is not required to be.SUBMIT YOUR IDEA LISTEN TO PUPPET PODCASTSWrite for Puppet's DEV.toThe DEV Community is an awesome community of nearly 600,000 developers focused on helping each other build their careers and develop best practices. While it isn't a channel owned by Puppet, our engineers (and a growing number of our community members) post to DEV consistently to share their learnings and help the community build out their Puppet knowledge.If you want to share good practices about using Puppet as well as helpful Puppet tips and tricks, sign up for DEV and start contributing! Use the hashtag #puppet to show up in the tag listing.good Practices tips and tricksDEV is a community platform for collaboration and networked learning among software developers.Guidelines for Submitting ContentGood content is educational, written clearly, and with a direct call to action. The Puppet community loves technical content, but don’t let that intimidate you. Not all content must be technical — unless we’re talking about documentation in which case, it helps!Use your authentic voice. We want to avoid content that feels like an ad. Talk to your audience directly, and with respect.Puppet retains full editorial control over all content published to Puppet channels (including the Puppet blog, podcasts, white papers, and other materials published to channels owned and operated by Puppet).Puppet is an inclusive workplace and that extends to our community, too. We welcome critical commentary, but choose your words thoughtfully. Harassment and judgment will not be tolerated.All content must be original and authored by you. We request that you do not submit content that has been submitted elsewhere, but self-published content is welcomed.Other Ways To ContributeOpen Source Puppet AssistContribute to Puppet ProjectsPuppet Documentation
