How to organize technical documentation and SEO guidelines in Confluence?

[kinoshrot]

Hello community! We are using Confluence to store all our team's guidelines, including SEO requirements, site architecture, and content briefs. As the space grows, it's becoming a bit hard to keep everything structured.

What templates or space structures do you find most effective for managing web development and marketing documentation side-by-side? Any tips on keeping page trees organized for small teams would be highly appreciated!

[Kris Klima _K15t_]

Hi @kinoshrot 

I'm a tech writer now working for a company that makes Confluence tools for tech writers (K15t).

We have this Confluence Documentation Guide with best practices for the documentation life cycle management.

The point I'm always making is that there is no golden bullet or best practices, because each company's different and what worked for me and 10 others, doesn't have to work for you.

Instead, the guide teaches you to ask the right questions:

"Across six articles, we outline best practices for designing and sustaining a framework that actually works. Take these concepts, apply them to your own environment, and use them to spark conversations with your stakeholders. Keep at it, and sooner or later, a clear vision will emerge."

Feel free to reach out to test your concepts or whenever you reach an impasse with your stakeholders.

[Laura Campbell]

Hi @kinoshrot Folders or parent pages are a great way to group content together and prevent infinite scroll page trees. It sounds like you also might have enough content to break it up into several spaces, which can also help people understand which type of content goes where (to avoid people just creating pages at the bottom of the page tree).

I second @Nikola Perisic with the Rovo recommendation: you can create a Rovo agent that only looks at specific pages, say only SEO pages, to answer questions or give recommendations or simply point the user to the right page. I have done something similiar internally to help people find the right marketing playbook as we have more than 50, and it works pretty well.

[Nikola Perisic]

Hi @kinoshrot 

Your best option would be to use Rovo for this, because it takes all company knowledge and can give answers to users based on the spaces they belong to.

To keep a better structure, use folders where you would distinguish the documentation more effectively. I would suggest that every team should have a different folder.