Demand for the new WIKI structure

[rached almahila]

I want to ask about structure. We are an IT department and are currently running a new wiki for ourselves.

Do you have any ideas or suggestions on how we can request this? I am the only one who will convince you of the idea of ​​conflunce.

a structure that defines us as an IT department clearly and in the long term

[Abi Brown- Kolekti]

Hi @rached almahila 

Welcome to the community. 

Are you looking for help to support a business case for a wiki? The following I would say are key drivers as to why confluence is a great tool for knowledge sharing and Wikis! 

Knowledge Management: 

It serves as a centralised knowledge hub, helping teams preserve and share information. You can have have a central wiki/knowledge base or each team can structure their own in a space and use smart links to sign post readers to the information they need

Team Collaboration: 

The collaborative nature of Confluence facilitates information exchange and collective contribution among team members. 

Accessibility: 

It is designed for a wide range of users, allowing almost anyone to contribute to the wiki, making it an accessible tool for knowledge sharing. 

Templates: 

Pre-built templates exist in confluence for different teams and projects help users get started quickly with their wiki. 

Intuitive Content Organization: 

Confluence uses a hierarchical structure of spaces and pages that can be organised by dragging and dropping, making content easy to find and manage

In my role I spend alot of time helping customers build wikis and knowledge bases so happy to assist if you have further questions 

Thanks

Abi 

[Philipp Sendek]

Hi @rached almahila and welcome to the community!

I'm not sure I understand your request correctly, but let's give it a try and you tell me if it helped:
One of the great things about Confluence is the fact that you're not locked into a predefined structure that you as an organization need to abide to.
Instead you have the freedom in every space and page structure to tailor it the way you need it.

However, we of course often have customers request a predefined template, which is a reasonable ask.
In your particular case, this is especially hard, as we don't know anything about what your documentation, processes, ways of working and any other content looks like.

I would personally recommend the following approach:

• Sight all of the documentation that you already have across tools in your department.
• Think of the processes in your teams or the whole department.
• Think of situations where the lack of documentation or documented knowledge (like processes, how tos, ...) led to challenges or problems.
• Think of things that you consider useful to know for people *outside of your department*.

When you have all of this, you can start thinking of a proper structure for it. This can be all in one Confluence space or separated out across different spaces (e.g. one for the Department, one for each Team and one for "public" information about the department for the rest of the organization).

I hope this helps.

Greetings
Philipp