nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

🎃 Day 2️⃣ of Remix or Treat Week: The Slide Sorcerer Prompt Challenge to share your spells! ✨🪄

Mindy Park

Here's a little secret every sorcerer knows: when you transform content into a Confluence slides deck , the prompt you give is like casting a spell 🪄. The words you choose shape the tone, the structure, the slide count, and the visual impact. A great prompt is the difference between a flat page and a presentation that truly bewitches your audience.

So this challenge is simple: share your best, most inventive, or most effective Confluence slides prompts — and claim your Slide Sorcerer badge! 🧙

Here's a quick primer on Confluence slides: community post, video, and blog.

✨ Starter spells to inspire you

Not sure where to begin? Steal one of these and make it your own:

⚡ The Project Kickoff Spell: “Create a project kickoff deck from this project plan <link to project plan page>. Include the problem we're solving, our approach, key milestones, who owns what, and open questions for the team. Create a visual timeline for the project milestones"
🎯 The Sprint Retro Spell: "Transform these retrospective sprint whiteboard <link to Confluence whiteboard> and create a presentation highlighting what went well, what slowed us down, and top 3 commitments for next sprint."
🛠️ The Campaign Readout Spell: "Turn this campaign results page into a recap deck for stakeholders <link to campaign results page>. Lead with the key insights, show what worked and what didn't, and close with recommendations for next time. Create charts to help visualize the metrics on this Google spreadsheet <link to Google sheet>."

🧙 Your turn — cast a spell to earn the Slide Sorcerer badge

Reply in the comments with:

A recent Confluence slides prompt you used / are planning to use.
What kind of deck it conjures (all-hands, customer pitch, onboarding deck, etc.).
(Optional) An example screenshot of the slides your prompt summoned.

Everyone who shares a spell earns the Slide Sorcerer 🔮 badge — and it counts toward unlocking the all-up Remix or Treat Star 🌟. Can you out-conjure your fellow community members? Show us your most powerful magic!

Halloween Badges - Full image with spider web.png

Don't forget…

🗓️ Keep track of all the Remix or Treat Week activities.

🎃 Join in each day's activity to earn its badge — collect 3 or more to unlock the Remix or Treat Star and a shot at limited-edition swag!

✨ Haven't worked the magic yet? Try Remix with Rovo and Confluence slides now.

Comments

Ruth Moreno

🪄 My Slide Sorcerer Spell: From Technical Documentation to Interactive Learning

I'm currently experimenting with Rovo Remix and Confluence Slides to explore how AI can transform complex technical documentation into more effective learning experiences.

I've created a Rovo Adoption Program training document in Confluence, and here's the prompt I'm planning to use:

✨ THE PROMPT

"Act as an instructional designer and solution architect.

Create an engaging, professional 8-slide training presentation based on my Confluence page 'Rovo Training – Original Documentation'.

Audience: IT professionals, project managers, service management teams, and solution architects.

Objective: Transform technical documentation into a clear, visually engaging learning experience without losing technical accuracy.

Presentation structure:

Why knowledge discovery matters: explain the challenges of fragmented organizational information.
Understanding Rovo: introduce its main capabilities through clear visual explanations.
Rovo in action: illustrate realistic knowledge discovery and collaboration scenarios.
Governance matters: visualize the essential principles of responsible AI adoption.
Roles and responsibilities: create a visual comparison of the five roles involved in the adoption program.
Adoption roadmap: generate a timeline showing the four project phases and their milestones.
Measuring success: transform the adoption metrics into an easy-to-understand comparative chart, clearly identifying the data as fictional.
Key takeaways: summarize the lessons and include two questions to encourage audience discussion.

Design requirements:

Use clean, modern, professional layouts.
Prioritize visual storytelling over dense text.
Choose the most appropriate visualization for each type of information.
Maintain consistent formatting throughout the presentation.
Keep all content in English.
Make every slide understandable without unnecessary technical jargon.

Critical instructions:

Use only information supported by the source documentation.
Do not invent metrics, capabilities, dependencies, or decision points.
Clearly distinguish documented facts from illustrative examples.
Preserve the technical meaning of the original content.
If information is missing, highlight the gap rather than making assumptions.

The goal is not simply to make documentation look better. The goal is to help people understand complex technical concepts more easily while maintaining accuracy and human oversight."

🎯 Deck type: Technical training and onboarding presentation.

My experiment focuses on a question I find particularly interesting:

Can AI improve how we communicate technical knowledge without changing its meaning?

That's the real magic I'd like to explore with Confluence Slides! 🎃✨

Akshad Katke

🪄 Confluence: Turning Ideas into Visual Stories

Objective:

Transform Confluence documentation into a visually engaging, professional presentation that demonstrates how ideas, information, and team knowledge can become clear visual stories using Confluence and Confluence Slides.

Create a 7-slide presentation with the following structure:

Slide 1: From Ideas to Visual Stories

Slide 2: The Challenge of Information Overload

Slide 3: Confluence as Your Knowledge Hub

Slide 4: From Confluence Pages to Slides

Slide 5: The Magic of Visual Storytelling

Slide 6: Real-World Use Cases

Slide 7: From Documentation to Inspiration

Design guidelines:

Use a modern, clean, professional design suitable for teams, project managers, and stakeholders.
Use a consistent color palette, readable typography, simple icons, and balanced spacing.
Prefer visuals and diagrams over lengthy paragraphs.
Use a before-and-after comparison to demonstrate the transformation.
Keep each slide focused on one key message.
Use subtle animations or transitions only if supported.
Make the presentation engaging, easy to follow, and suitable for a short team demonstration.

Accuracy requirements:

Use the provided Confluence content as the source of truth. Do not invent product features or claim that a capability is available unless supported. Clearly distinguish general storytelling recommendations from actual Confluence functionality.

Expected result:

A polished seven-slide presentation that tells a compelling visual story about how Confluence documentation can become more engaging, accessible, and presentation-ready through effective storytelling and Confluence Slides.

✨ From Confluence pages to captivating slides — turning ideas into visual stories with a little Rovo magic! 🪄🎃

👇 After transformation! ✨

Tomislav Tobijas

Here's a fun one 😄 I originally prepared this a couple of months ago, but wanted to give slides another try to see how the new version would look.

I've prepared a day-by-day Lisbon itinerary in my personal Jira, and I asked Rovo to turn it into a family travel presentation.

Prompt:

Turn my Lisbon itinerary [link] into a fun, visual slide deck to share with my family. Start with a trip overview, then create one slide per day with the main sights, activities and practical notes from the itinerary. Finish with a highlights slide.
Keep the daily sequence, use short captions rather than long paragraphs, and give it a Lisbon-inspired look with warm colours, Portuguese tiles and destination imagery. Keep the tone relaxed, with a little humour—this is a holiday, after all!
Use the itinerary as the source of truth. Don’t invent bookings, prices or travel times, and keep optional activities clearly marked.

It actually turned out pretty cool 😄

Vaibhav Sule

🪄 Simplifying ITSM with Jira

Objective: Transform IT Service Management (ITSM) documentation into a clear, engaging presentation showing how Jira Service Management helps teams manage service requests, incidents, problems, and changes.

Create a 6-slide presentation:

Slide 1: ITSM Made Simple
Introduce ITSM and how Jira Service Management supports efficient service delivery.

Slide 2: Incident Management
Show the journey from incident reporting and investigation to resolution and closure.

Slide 3: Service Request Management
Explain how users submit requests, teams process them, and services are delivered.

Slide 4: Problem and Change Management
Illustrate root cause analysis, risk assessment, approvals, and controlled changes.

Slide 5: Automation and SLAs
Show how automation, notifications, prioritization, and SLA tracking can improve service operations.

Slide 6: Better Service, Better Experience
Summarize the benefits of structured workflows, clear ownership, visibility, and continuous improvement.

Design guidelines:
Use professional layouts, simple icons, workflow diagrams, and concise text. Show process flows from request to resolution and use realistic ITSM examples. Keep the presentation visually engaging and easy for technical teams and stakeholders to understand.

Accuracy requirements:
Use the provided documentation as the source of truth. Distinguish existing configurations from suggested improvements, and do not invent workflow statuses, automation rules, or SLA targets.

Closing message: “Simplify Service. Streamline Workflows. Deliver Better Experiences.”

Arkadiusz Wroblewski

My spell: “The admin is on holiday. Please don’t summon them.” 🤠🧙‍♂️

I’m planning to try this for a service desk handover deck:

“Turn this Confluence handover page into six slides for the colleague covering the service desk:

What the service handles.
How requests arrive and which queues to check.
Who owns each step and when to escalate.
Key automations, their purpose and where to check failures.
Known limitations and documented recovery steps.
A checklist for the first support shift.

Use a simple flow diagram for the request journey and a table for responsibilities. Keep the text short enough to use during a busy shift.

Use only the source page. Mark missing owners, contacts or recovery steps as ‘Not documented’. Keep warnings visible and link back to the relevant sections.”

The test: can a colleague find the next action without calling the person on holiday? 😅

Haha, actually I also get that.

Jean Horn

I love this challenge! Here is my contribution to the spellbook:

✨ The Spell Name: The New Wizard Onboarding Spell 🧙‍♂️

My Prompt:
"Transform our 'Team Handbook' page into an engaging 7-slide onboarding presentation for new hires. Include our team's mission, our core values, the main communication channels we use, a checklist for their first 30 days, and a 'Who's Who' directory. Keep the tone warm, welcoming, and energetic, and use icons to visually represent each of our team values."

What kind of deck it conjures:
An Onboarding / Welcome Deck for new team members joining our department. It makes sure no new wizard feels lost on their first day!

I can't wait to see everyone else's spells! 🪄🔮

Anwesha Pan

Spookyyyyy

Spell: 🪄 Remixium Hocus Pocus: The Community Alchemist’s Elixir

My Prompt:
"As an Atlassian community member, create a deck with slides referring articles from Confluence articles - Atlassian and turn them into a recap deck for Atlassian community members to refer and participate in the challenge. Lead with the key insights, show what daily and weekly challenges to participate and register, and close with recommendations for next step. Create charts to help visualize the metrics of people participating. Topic - Remix or Treat Week challenge"

What kind of deck it conjures:
An Onboarding/ Welcome Deck for an Atlassian community member to participate in this challenge.

Slide 1: Title & Overview

Title: 🎃 Remix or Treat Week: Transform Content with Rovo
Subtitle: Community Recap, Participation Guide & Challenge Roadmap
Presenter: Atlassian Community Team
Key Takeaway: Turn static Confluence pages into dynamic, engaging assets using Remix with Rovo — win $250 prizes and get featured on the global Remix Gallery.

Slide 2: Key Insights & Challenge Highlights

$1,250 Total Prize Pool: Five (5) winners selected to receive $250 USD electronic gift cards.
Global Exposure: Top community remixes will be spotlighted in the official Public Remix with Rovo Gallery.
Core Philosophy: "Content transformation in seconds" — shifting documentation from plain text blocks to visual, digestible formats (infographics, mindmaps, flip cards, slides, tables).
Key Deadline: Entries close October 29, 2026 at 11:59 PM ET, with winners announced during Remix or Treat Week (drawing on or about November 1–2).

Slide 3: Weekly & Daily Challenge Journey

Kickoff Phase (Days 1–3):
- Audit & Discover: Identify dense, text-heavy pages (e.g., certification guides, onboarding runbooks, SOPs).
Remix Phase (Days 4–7):
- Prompt & Iterate: Run Remix with Rovo using different transformations.
- Side-by-Side Validation: Capture high-resolution "Before" and "After" screenshots showing the readability improvement.
Community Share Phase (Days 8–10):
- Post & Tag: Submit your entry directly on the Confluence Cloud Community group.
- Engage: Comment, vote, and share feedback on peers' remix ideas.
Finale (Remix or Treat Week):
- Official showcase and announcement of the 5 Grand Prize winners.

Slide 4: How to Register & Submit Your Entry

Locate or Create Your Content:
- Open any existing Confluence page within an active Confluence Standard or above plan.
Execute the Remix:
- Use Remix with Rovo to convert the page into an infographic, mind map, interactive flip cards, presentation slides, or chart.
Capture Evidence:
- Take clean screenshots of the original page (Before) and the remixed asset (After).
Publish Community Discussion:
- Navigate to the Confluence Cloud group on Atlassian Community.
- Start a new discussion titled: Remix or Treat: [Your Feature / Topic Name].
- Attach both screenshots and briefly explain how Remix helped your readers absorb the information better.
- (Optional but recommended): Add your name, title, and organization.

Slide 5: Community Participation & Format Breakdown

Slide 6: Rules & Submission Best Practices

Show Real Value: Judges look for genuine improvements in content consumption and audience engagement.
Keep It Original: Ensure you have permission to share screenshots (redact sensitive or proprietary data).
One Valid Entry Per Person: Maximize quality rather than posting multiple duplicates.
Active Pages: The source page should be live and functional in your Confluence instance.

Slide 7: Next Steps & Community Recommendations

Pick Your Candidate Page Today: Choose a guide or doc your team frequently references.
Experiment with Formats: Try two different formats (e.g., Mindmap vs. Infographic) before choosing the best transformation.
Submit Early: Post your thread before the October 29, 2026 11:59 PM ET cutoff to maximize community visibility and comments.
Celebrate & Share: Share your post link internally with your team and on social channels!

Addie

Help me create a slide deck…Act as an executive producer and comedic late-night show host (think Saturday Night Live meets high-impact enablement).

Generate a 9-slide, visually dynamic, high-energy presentation in Confluence Slides titled:
"LIVE FROM [CITY/OFFICE]: REVENUE TEAM CAMP – GUEST FACILITATOR ALL-STARS!"

Tone: Fun, celebratory, witty, welcoming, and hyper-organized.

Slide Breakdown:

Title Slide: The Cold Open & Tonight's Headliners

Headline: "Live from [Location: San Francisco Atlassian Office/Floor: 12]... It’s Revenue TEAM Camp!"
Subtitle: Welcoming our celebrity guest facilitators to the main stage.
Visual/Vibe: Late-night marquee, neon skyline, broadcast energy.

Slide 2: The Tour Bus & Hotel Rider (Travel & Accommodations)

Headline: "VIP Travel & Accommodations"
Format: Clean 2-column info card layout.
- Flight & Arrival: Designated arrival window (arrive Sunday evening / day prior to session). Ground transit tips from airport to hotel.
- Headquarter Hotel: Name of designated team hotel, check-in details, walking distance/shuttle info to the office.
- Travel Policies: Quick reminder on corporate travel booking tool, per diem/meal guidelines, and expense code/tagging.

Slide 3: All-Access VIP Pass (Building Entry & Braxpass)

Headline: "Backstage Security Clearance"
Critical Access Details:
- Office Entry & Braxpass: Ensure digital Braxpass is downloaded, activated, and synced on your mobile device before arrival.
- Physical Badges: Security desk check-in procedures, visitor/guest pass backup protocol if Braxpass glitches.
- Elevator & Floor Permissions: Which tower/floor, turnstile tap-in instructions, and escort requirements (if applicable).

Slide 4: Meet Our "Celebrity" Guest Stars (Who’s Who on Stage)

Introduce our cross-functional enablement and leadership stars co-facilitating this cohort.
Format for each guest facilitator card:
- Name & Title
- "Claim to Fame" / Facilitation Superpower (e.g., objection handling guru, disco slide master, objection whisperer)
- Their Featured Segment / Workshop Session topic.

Slide 5: The Broadcast Schedule & Run of Show (ROS)

Headline: "Tonight's Lineup & Timing"
Agenda timeline:
- Call Time: Arrive at workshop room 20–30 mins prior to segment.
- On-Air: Workshop kickoff and facilitator handoff windows.
- Commercial Breaks: Bio breaks, breakout exercises, cohort lunch sync.
- Post-Show Wrap: Room reset and team debrief.

Slide 6: Soundcheck & Green Room Tech (Presenter Setup)

Headline: "No Dead Air: Laptop & AV Setup"
Tech checklist:
- Arrival Time: In-room 20 minutes before speaking slot for soundcheck.
- Display & Connection: HDMI / USB-C connection, dual-display / presenter view mode.
- Notifications Off: Slack and email set to "Do Not Disturb" / presentation mode.
- Mic & Audio: Lavalier/handheld mic battery check and room confidence monitor check.

Slide 7: Props, Scripts & Swag (Resources & Handouts)

Headline: "Cue Cards, Scripts & Studio Kit"
3-column asset breakdown:
- Digital Assets: Master slide deck link, digital Run of Show (ROS), offline backup PDF.
- Printed Materials: Participant activity workbooks, table team assignments, facilitator quick-reference sheets.
- Swag & Prizes: In-room attendee rewards and speaker appreciation tokens.

Slide 8: Cast, Crew & Stage Managers (Roles & Responsibilities)

Headline: "Who’s Running the Control Room?"
Distinguish the roles clearly:
- Stage Managers (Onsite Enablement Crew): Room timing, AV troubleshooting, roving mic support, badge tracking.
- Guest Stars (Facilitators): Storytelling, core delivery, interactive breakout coaching.
- Studio Audience (New Hires/Cohort): Active participation, group role-plays, Q&A.

Slide 9: Working the Crowd & Curtain Call

Headline: "Ready for Your Monologue?"
Audience engagement tips:
- Pacing: Cold-calling vs. table-bouncing questions.
- Energy: Mid-afternoon wake-up polls and table competitions.
Final 4-item launch checklist:
[ ] Braxpass scanned & badge on
[ ] Slideware loaded & Slack silenced
[ ] Mic on & water bottle filled
[ ] Bring the late-night energy!
Urgent in-room SOS contact: Slack channel (#help-revenue-onboarding) & onsite stage manager cell.

Result/Rovo Answer: A draft presentation has been prepared in Confluence Slides titled "LIVE FROM SF: REVENUE TEAM CAMP – GUEST FACILITATOR ALL-STARS!" (Content ID: 8170646918).

Deck Overview & Slide Flow

Title Slide: The Cold Open & Tonight's Headliners
- Headline: "Live from Floor 12 in San Francisco… It’s Revenue TEAM Camp!"
- Vibe: Late-night marquee styling, neon broadcast energy, welcoming guest stars to the main stage.
Slide 2: Tonight's Run of Show
- High-level agenda and pacing overview setting expectations for the broadcast.
Slide 3: The Tour Bus & Hotel Rider (Travel & Accommodations)
- Two-column VIP layout covering arrival windows, ground transit/rideshare, designated team hotel, per diem, and expense guidance.
Slide 4: All-Access VIP Pass (Braxpass & Building Entry)
- Backstage security clearance instructions: 48-hour Braxpass mobile sync, front-desk badge check-in, floor 12 turnstiles, and visitor protocols.
Slide 5: Meet Our "Celebrity" Guest Stars
- Dedicated profile cards featuring facilitators' stage names, claims to fame/superpowers (e.g., objection handling, narrative selling, pipeline forensics), and featured workshop topics.
Slide 6: Broadcast Schedule & AV Soundcheck
- Segment timeline (call time, on-air blocks, commercial/lunch breaks, debrief) paired with a technical soundcheck checklist (mics, displays, "Do Not Disturb" presentation mode).
Slide 7: Props, Scripts & Swag (Studio Kit)
- Breakdown of digital assets, physical participant workbooks, room signage, and attendee swag/rewards.
Slide 8: Cast, Crew & Stage Managers
- Clear division of responsibilities: On-stage facilitators (storytelling and coaching), stage managers (timing and roving mics), and audience participation expectations.
Slide 9: Working the Crowd & Final Curtain Call
- Engagement pacing tips, rapid 4-point launch checklist, and SOS contact info (#help-revenue-onboarding / onsite lead).
Slide 10: That's a Wrap!
- Closing celebration slide with debrief info and final send-off.

The interactive preview card is ready for you to review and customize further with specific facilitator names and room details.

Shivam Kadwade

Hey 💙,
Here's one for Developers, SREs, Scrum Masters, or IT Ops.

🔮 My Slide Sorcerer Spell: The Post-Mortem Potion

Sometimes you need a little necromancy to revive team spirits after a system outage. Translating a highly technical incident report into a blameless, educational deck for an all-hands is an art form. Here is my spell for that!

✨ THE PROMPT
"Transform this 'Severity 1 Incident Report' Confluence page into a 5-slide post-mortem presentation for the engineering all-hands. Tone: Objective, blameless, educational, and forward-looking.

Structure:

The Ghost: Incident Summary (What went bump in the night?).
The Timeline: A visual step-by-step of the events and our response times.
The Autopsy: Root Cause Analysis (The '5 Whys').
The Cure: Resolution (How we mitigated the issue).
The Wards: Action Items & Preventative Measures for the future.Critical Instructions: Ensure the focus remains strictly on systemic improvements and process gaps, completely avoiding individual blame. Highlight any metrics regarding downtime vs. recovery."

🎯 Deck type: Engineering All-Hands / Blameless Incident Review Deck.
Why it works: It takes the anxiety out of incident reviews by forcing the AI to strictly adopt a blameless, constructive tone while summarizing complex timelines! 🦇✨

Rinjini Poddar

🪄 My Slide Sorcerer spell: Spooks, Sparks & Sweet Treats — Halloween Meets Diwali! 🎃🪔

I’m planning to turn my Confluence page about Halloween and Diwali into a fun, visually engaging presentation for a team celebration. I wanted to combine Halloween’s spooky fun with Diwali’s lights, colours and festive traditions.

✨ The prompt I’m planning to use:

“Turn my Confluence page ‘Spooks, Sparks & Sweet Treats: Halloween Meets Diwali’ into a visually engaging 7-slide presentation for a team celebration.

Include a title slide, an introduction to both festivals, Halloween activities, Diwali traditions, ideas that combine both celebrations, a simple celebration plan, and a closing invitation for everyone to participate.

Use a playful but polished design with deep purple, pumpkin orange, diya gold and festive colours. Keep the text concise, use clear headings and engaging visuals, and make the slides easy to follow. Keep the tone friendly and inclusive. Use the original Confluence page as the source of truth, and don't invent event details or present suggestions as confirmed plans.”

🎯 Deck type: Festive team celebration and engagement presentation.

I love the idea of turning an ordinary Confluence page into something more visual and enjoyable to share. I’ve also put together a sample deck to explore this concept. Next, I’d love to try the same prompt in Confluence Slides and see what kind of magic it creates! ✨👻

manish jangir

Spell: 🪄 Amsterdamus Recapium: The Conference Summoner’s Takeaway Elixir

My Prompt:
“Turn this Confluence page into a short recap deck for teammates who couldn’t attend Team ‘26 Europe. Start with the top 5 announcements, show the three event days as a simple timeline, and group the features by Context, Collaboration and Confidence. Mark what’s available now and what’s coming soon, and end with 3 things our team can try this month. Keep each slide under 30 words.”

What kind of deck it conjures:
A quick conference recap deck for a team meeting or lunch-and-learn, so people who missed Team ‘26 Europe can catch up in five minutes.

What the slides cover:

Slide 1: Team ‘26 Europe in one line: AI works best as a team sport
Slide 2: Top 5 announcements (AMP, Rovo Work, Artifacts, rebuilt MCP Server, EU AI inference)
Slide 3: Three days at a glance
Slide 4: Context, Collaboration and Confidence
Slide 5: Available now vs coming soon
Slide 6: 3 things we can try this month

Missed Amsterdam? This one’s for you. 🎃

— Manish Jangir, Atlassian Product Expert, Holograph Technologies and Consulting India Pvt. Ltd.

Akshad Katke

Anamika Soni

🪄 My spell: “The meetup recap that writes itself”

After every Atlassian Community Jaipur meetup, I spend way too long putting together a recap deck. It’s for attendees, for people who couldn’t make it, and to give a quick overview of the previous event at the start of the next one. So for our Oct 24 meetup on Jira × CI/CD, I let Rovo do the heavy lifting.

My prompt:
“Turn this meetup notes page into a recap deck for our community members. Start with a quick event overview (date, theme, number of attendees), then one slide per session with the speaker name and 2 to 3 key takeaways. Add a slide with the best questions from the Q&A, and end with a ‘What’s next’ slide for our upcoming meetup. Keep it short, friendly and easy to share. Only use what’s in the notes, and if a speaker’s takeaways are missing, just mark them as ‘To be added’ instead of making something up.”

Deck type: Community event recap, shared with attendees and anyone who missed it.

What surprised me:

I hadn’t added the Q&A questions to my notes yet, and Rovo didn’t invent any. It marked that slide as “To be added”, exactly as I asked. 🙌
It was honest about where it didn’t follow my prompt. It told me it added 4 takeaways instead of 2 to 3, and a few extra slides, and suggested what I could cut.
When I asked it to add photos from my page, it placed them across the slides and skipped the HEIC files, explaining they often don’t display in slides.
It even noticed that our next meetup is today and warned me the “What’s next” slide would be outdated if I shared the deck later. 😄

A 10-slide recap with event photos in a few minutes, from a notes page. That’s my kind of magic! 🎃✨

Ashok Shembde

🪄 My Slide Sorcerer Spell: The SDLC Workflow Wizard 🎃✨

✨ My Prompt:

“Transform my Confluence documentation about the end-to-end SDLC process into a visually engaging 7-slide presentation for developers, QA teams, Scrum Masters, and project stakeholders.

Show how Development, QC, Release Management, SIT/UAT, CAB Approval, and Deployment work together throughout the software delivery lifecycle.

Slide structure:

The SDLC Journey – Introduce the end-to-end software delivery lifecycle.
Development in Action – Show how requirements become development tasks.
Quality Control – Visualize testing, QC approvals, and defect handling.
Release Management – Explain release readiness and coordination.
SIT & UAT – Illustrate the testing stages and their dependencies.
CAB Approval & Deployment – Show approval checkpoints and controlled production releases.
From Development to Delivery – Summarize the complete workflow and key takeaways.

Use workflow diagrams, visual timelines, and clear status transitions to show how each stage connects to the next. Highlight dependencies between Development, QC, Release, and Deployment, including the conditions that must be satisfied before progressing.

Keep the design modern, professional, and visually engaging, with concise text and consistent styling. Use only information supported by the source documentation. Do not invent statuses, transitions, or approval rules.”

🎯 Deck Type: ITSM / SDLC Process Walkthrough and Technical Training Presentation.

✨ Why this spell?

Complex workflows become easier to understand when their stages, dependencies, and approval checkpoints are presented visually. With Confluence Slides and a little Rovo magic, technical documentation can become a clear story of how software moves from development to production! 🪄🚀

Pulkit Soni - Optimizory

🪄 My spell: “Design doc to architecture review in one go”

I write a lot of solution design docs, and before every architecture review I end up rebuilding the same content as slides. This time I gave Rovo a design doc for an event-driven notification service and asked it to do that part for me.

My prompt:
“Turn this solution design page into an 8-slide architecture review deck for tech leads and stakeholders. Start with the problem, then show the proposed architecture as a simple flow diagram based on the data flow section. Add one slide each for the tech stack, the non-functional requirements, and the risks and trade-offs. Include a slide with the open questions so we can discuss them in the review. Keep the text short and technical, with no marketing language. Only use what’s on the page, and if any section is empty or missing, mark it as ‘Not documented’ instead of filling it in.”

Deck type: Architecture review / solution walkthrough for tech leads.

What I noticed:

The data flow section came out as an actual flow diagram: Module → Kafka → Notification Service → Email/SMS → Status Log. That alone saves me a good 20 minutes in draw.io. 😅
It didn’t follow everything. I left the rollout plan empty on purpose, and instead of marking it “Not documented”, it just skipped it. It also added a few technical details that weren’t on my page, like “consumer lag” on the risks slide.
The best part: Rovo then reviewed its own deck and called all of this out, including the missing rollout plan, the extra phrases, and that it made 9 slides instead of 8. It even offered replacement text to fix them.

So it’s not perfect on the first try, but an AI that tells you exactly where it drifted from your source is something I’d trust in a real architecture review. 🎃

Arkadiusz Wroblewski

Mihai_LeanZero

Hi @Mindy Park,

My spell from yesterday, cast on a test site against a long technical plan page:

"Create a Confluence slides deck from this page: [link to the plan page]. It is a go/no-go deck for a steering committee, 7 slides max. Slide 1: the decision we need from them, in one sentence. Then the problem and the proposed approach, the cost range and the maintenance cost, a visual timeline of the phases, the top 3 risks with the probability the page gives each one, and a closing slide with the decision options. Plain language, no code, and use only numbers that are on the page."

It conjured a 7 slide steering committee deck. Putting the decision ask on the title slide works really well. The risk slide kept the page's probabilities.

The closing slide tagged the full build as "Recommended" although I only asked for options. It also worked out a POC cost that isn't on the page. And the chat summary listed four phases, while the timeline slide merged phases 2 and 3 into one column.

Next version of the spell gets "don't recommend an option, the committee decides".

Rinjini Poddar

I’ve created a Confluence Slides presentation using a Halloween and Diwali theme! 🎃🪔 It was a fun way to bring together spooky vibes, festive traditions, and team celebration ideas.

Sharing the slides below!✨ Looking forward to exploring more creative ways to use Confluence Slides!

Kishan Sharma

Great challenge! Here is what I conjured -

New Admin Onboarding Spell🧙

The Prompt:
Please help to create a deck from this page <Our_internal_Confluence_Page>, include different roles available on atlassian cloud, what they can perform and what can each admin do?

Deck type: Technical training and onboarding presentation.

Example Screenshots -

Viswanathan Ramachandran

Used this original google form https://forms.gle/EybVBifZq7eCCAw49

to create a slide using that theme..

Happy Halloween and Diwali to all

Martin Runge

My go-to spell turns a real recipe from my personal Confluence space into a cooking deck. The page features a Chinese Bolognese recipe from an Italian-Chinese family kitchen, written in German. It made for a great test: I wanted English slides without changing the original page.

Here’s the prompt I used with Remix:

Turn this recipe into a 7 slide cooking deck in English, even though the page is written in German. Slide 1: Title "Chinese Bolognese" plus one line about the Italian mum and the Chinese dad behind it. Slide 2: Ingredients in two columns, "Hong Kong Sofrito" and "Meat sauce". Keep metric units. Slides 3 to 5: The method in three phases: "Low and slow sofrito", "Brown and deglaze", "Braise and season". Max 4 short steps per slide, start each step with a bold verb. Slide 6: The three tips as big callouts. Slide 7: Sources and "What I still want to test", based on my own notes. Mark every estimated quantity with (est.). Warm and friendly tone, no more than 25 words per slide.

A few things I learned while "casting" it:

Do not edit while Rovo is doing his magic; be patient!
Name the slide count, or the deck grows
Name the sections, so the story follows your logic
Ask for translation in the prompt
Tell it what to keep, like my (est.) markers
Set a word limit per slide

What I liked most is that Remix never changes the original page. My German recipe stays as it is, while the English deck sits alongside it. The same approach works for any how-to page, runbook, or onboarding guide in your space. Just swap out the phase names and callouts.

Happy Remix or Treat week! 🎃

Mindy Park

Thank you all for participating!

Here are our 5 randomly selected winners of the Day 2️⃣ challenge!

I'll email each of you individually on how to claim your prize by the end of Nov, as there's been some production delays.

Country-specific guidance

INDIA

Shipping Warning: When you get the tracking link by email, visit the DHL KYC Portal to complete the KYC form needed to process your shipment. Not providing this info will cancel your shipment. See "What to expect when receiving a gift in India?" for details. If you have any issues or get charged, submit a form to our swag vendor and they will help -> https://andopen.co/support
Angola, Armenia, Georgia, Nepal, Turkey, Ukraine

Shipping Warning: You will be required to pay customs fees for this package because Delivered Duty Paid (DDP) is not accepted in this delivery country. If you have any issues or want to be reimbursed, submit a form to our swag vendor and they will help -> https://andopen.co/support

Everywhere Else

Shipping: If you have any issues or get charged, submit a form to our swag vendor and they will help -> https://andopen.co/support Atlassian pays all fees (DDP), but customs may misread labels. You shouldn’t be charged.

Jean Horn

So excited to see my name here! 🎉 The challenges were really fun and I learned a lot throughout the process. Thank you so much for organizing this!

Rinjini Poddar

Congratulations to all the winners! 🥳🎉 Such a fun challenge with so many creative ideas and prompts shared by the community.

sunny.patwa

Congratulations to all the winners! 🥳🎉…Better Luck Next time

Akshad Katke

Congratulations to all the winners! 🎉👏

Solomon Omete Monari

🧙 My spell for turning service-desk chaos into a monthly update:

"Create a 6-slide deck from this page for a non-technical leadership audience. Slide 1: one-sentence summary. Slide 2: key numbers as a chart. Slides 3–4: top three issues, each with impact and the fix we applied. Slide 5: what's coming next month. Slide 6: one clear ask. Use short bullets, no more than 15 words each, and turn any table into a visual."

The trick is to name the audience and set a word limit. Without those, decks turn into walls of text. 🍬

Anne Saunders

I was at BIT Dallas all week so I'm late to the party, but my spell is a Recap Cantrip:
"Please build me a slide deck that summarizes each Jira Space in the category Billable for the previous 2 weeks. Use one slide per space. Only include spaces that had activity. I’d like to know things like: participants, new work item volume, and items completed. Please use our branding to the best of your ability. Our primary brand colors are:
Blanford HEX: 213740
Simien HEX: FF5900
Corsac HEX: FCF9ED"

I can't show most of my slides, but it did turn out well!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

rovo