We already know what SharePoint is, which elements we can put in it, what migration is … Time to find out what the structure of SharePoint is. Hundreds of companies use it to keep their resources in order – so it must be simple, transparent and practical.
What can we compare the SharePoint structure with? The easiest way is probably to combine them with a well thought out system of shelves and drawers.
The intranet home page is like an empty wardrobe. We can freely arrange it, unfold items in it, group them in various drawers, rearrange, add shelves … so that we can conveniently find the necessary things and use them as intended.
And how does it look in practice? On the main page of the intranet, we have links to the most important site collections.
Within them, we can create even smaller structures. Do you need to gather documentation for one project in one place? You can create a list, page or library in which to place all files related to one topic. No elements outside the topic, everything ordered chronologically or by version… it’s like a drawer signed with the name of the project.
Let’s watch this closely with an example. We want to put photos from the company event on the intranet. We create a site collection and we simply call it ‘Photos’. Then we divide the structure and in each of them, we put photos from a separate event. Do we want to divide them in more detail – for example, thematically? Nothing hard.
Is the SharePoint structure complicated? Not. The key to maintaining order in files placed on the platform is to properly name the individual elements. If we just name each structure properly, it will be easy for us to find the right file – the rest is a matter of intuitive SharePoint layout.
We will talk about the differences between lists, libraries, and pages, but we hope that today we have been able to show that SharePoint can be divided into logical, personalized, convenient to use modules.