Hi, this is a followup from previous discussion at ConfigMgmtCamp. I discussed with @gundalow please let me know if you find this useful.
Proposal: Improving Bullhorn Content Quality
I propose presenting Bullhorn content in a more story-driven format. This would follow a predefined structure using elements like charts, maps, links, infographic, and tables to present information in a clearer and more engaging way. Such a format would make the content easier to understand, more visually appealing, and better suited for sharing on social media. We can experiment on this format and if successful, create a template for future posts.
Execution
To implement this, we would need to design and adopt a structure along with clear usage guidelines. The structure can be shaped with input from Ansible contributors to reflect how they want to consume Bullhorn content.
Benefits to the Community/ Audience
This approach would help readers quickly grasp the essence of an event or update. Even non-users could get a concise overview of the topic and its practical impact, which could also support broader promotion and outreach.
Technical benefits for the Ansible ecosystem
• Provides a consistent, structured format for presenting technical updates across Bullhorn editions
• Makes release notes, collection updates, deprecations, and roadmap items easier to track and understand.
I’ve prepared a full fledged post which shows my experience attending Ansible track in CfgMgmtCamp this year. While the structure can be modified/discussed/tweaked, I hope this will spark some discussion on how we can make the content more useful/appealing.
)