Metadata - successful implementation (demo requested)

[Fiona Higgins]

Hi there, I'm exploring how better metadata can improve how our knowledge base works. I've seen there are products in the marketplace that can help (e.g. https://marketplace.atlassian.com/apps/1213690/metadata-for-confluence?hosting=cloud&tab=reviews&utm_source=google&utm_medium=cpc&utm_campaign=new+bt+generic+search+metadata+confluence&utm_content=new+non+product+rsa+metadata+confluence+728625854623&utm_term=metadata+for+confluence+b&partner_anonymous_id=a1006&gad_source=1&gad_campaignid=22019688920&gbraid=0AAAAACdPwpiEmJl_0ujGgLeE-S-2g9k29&gclid=EAIaIQobChMI1v-Lo8DijwMVT5FQBh1rNgF5EAAYASAAEgJ7bvD_BwE)

Would anyone be open to showing me (show and tell style) how you've improved the use of metadata in your Confluence knowledge base, resulting in a better user experience? Thanks in advance

[Mia Tamm _Simpleasyty_]

Hi @Fiona Higgins great question! Metadata can absolutely boost a Confluence knowledge base, but the best setup depends on your use case. Could you share a bit more about what you want to improve?

Quick questions to shape the solution

1. Audience & goals: Who’s consuming the KB (agents, customers, internal teams)? What should be faster—finding content or maintaining it?

2. Content types: What pages do you have—How-to, Troubleshooting, Release Notes, Policies?

3. Findability pain: Are people struggling with search, browsing by topic, or both?

4. Fields you’d capture: e.g., Product, Component, Version, Audience, Platform, Status, Owner, Last reviewed.

5. Scale & governance: Rough number of pages? Do you want mandatory fields, review reminders, or dashboards?

Tiny example to illustrate (starter schema)

• Content type: How-to / Troubleshooting / Reference

• Product: Payments / Identity / Core

• Component: Checkout / API / Docs site

• Audience: Agents / Customers / Internal

• Status: Draft / Ready / Needs review

• Last reviewed: date
  With a metadata app you can (a) make these fields part of page templates, (b) build dynamic lists like “How-tos for Payments → Checkout for Agents,” and (c) drive reviews from Status/Last reviewed. If that’s the direction you’re after, we can sketch a simple “show & tell” flow.

Looping in experts

Maybe @Lorenzo Manfredini can you help here ;) 

— Mia Tamm

[Marc - Devoteam]

Hi @Fiona Higgins 

Reach to to the app vendor, to provide you with a demo, most of them are wiling to provide this.

[Lorenzo Manfredini]

Hi @Fiona Higgins ,
and thank you both @Marc - Devoteam and @Mia Tamm _Simpleasyty_ 

Thank you for your interest in our Metadata for Confluence. We are excited to share more about our app.

Here is the documentation for the Cloud version.

Please review it and submit a work item to us. 

Include details as suggested by Mia to help us prepare for the demo. Keep it concise; our App’s PO will address any questions that arise during the tailored demo session. Please note any specific documentation points that caught your attention; that would be appreciated.

I look forward to hearing from you through our official support channel!

Regards,
Lorenzo
Communardo Support