Here we compare traditional deliverable creation methods with a cutting-edge, agentic approach focused on vibe coding, or more seriously an Agentic First Approach.
> Join us as we pioneer smarter, more inclusive project work—starting with our upcoming vibe coding session!
The aim is to optimise output for complex, community-driven projects, allowing for rapid, tailored website and presentation generation from shared knowledge bases like wikis.
# The Traditional Approach Typically, when creating project deliverables, one identifies the required output—be it a PDF, a presentation, or a website. Each deliverable is then produced in a conventional manner: PDF documents are designed with standard software, presentations are created with tools like Microsoft PowerPoint, and websites are built using platforms such as Google Sites or Wix. Once completed, these items are delivered to stakeholders for review and use.
- The Hitchhiker" or Agentic First Approach
# Technical Implementation Notes - **Switching from Wiki to Markdown:** While the current system uses a wiki, migrating to Markdown in Obsidian will be considered once interoperability tools are available, enabling seamless transfer of content. - **Agentic Workflow Automation:** The AI agent or automation system can be prompted to generate static websites from wiki content by showing example outputs and defining a JSON-to-HTML process. - **Preparation:** The first "vibe coding" workshop is scheduled for next Thursday. Preparatory tasks include setting up the infrastructure and scripting so that the system can generate example sites from the wiki within the event.
# Summary of Key Steps 1. Gather and organise content in a central wiki or markdown system. 2. Prepare scripts or AI prompts for extracting and formatting this content into web or presentation formats. 3. Hold a workshop ("vibe coding meetup") to familiarise participants with the process and create the templates/infrastructure for future scalability. 4. Target to complete examples (such as an event website) within 1–2 days post-workshop.
# Conclusion By adopting this agentic, vibe-coded workflow, project teams can vastly simplify the creation and iteration of deliverables. This enables rapid, community-focused dissemination of information and ensures all stakeholders—regardless of background or interest—can engage through customised, up-to-date interfaces. The approach saves time, attracts innovative contributors, and helps maintain alignment across diverse groups.