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; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Structuring and naming Share Sites

lusiview

Hello all

We are evaluating Alfresco in order to move away from sharepoint, but are having some difficulties in working out the best way to structure and name alfresco share sites

Sharepoint supports nested sites and it is therefore easy to work out a hierarchy to structure departmental sites and subsites. This is more difficult with alfresco.

Is anyone able to share with the forum how you are structuring and naming sites in your alfresco environment. Examples would be welcome and I think this will help many people thinking of moving from sharepoint to alfresco.

Thanks

Find more posts tagged with

Comments

afaust

Hello,

we have recently implemented a project for a customer that required adding structure to Share sites. What we did is implement different site types (e.g. a departmental site and a site for teams within a department), that allowed the site creator / manager to specify a site as the superior anchor via the create / edit site dialogs. The flat-list structure of sites was kept as Alfresco bases a lot of functionality on this, but we added a secondary structure with hierarchies to this. A new, static component on user and site dashboards (not a dashlet) provides a navigation tree for the site hierarchy.

In terms of naming, we added secondary name attributes, such as a department symbol (short form label, much like a stock symbol in an stock exchange), and the option to configure which type of name would be displayed in the new navigation tree component. The base site name attributes shortName and title were kept and still retain their standard function, i.e. unique, technical identifier and human-readable full name.

The most recent feature implemented was the aggregation of wiki articles over the site hierarchy, e.g. all visible wiki articles from site ancestors and site descendants would be displayed in a site wiki, with the added information of origin. Additionally, the linking feature was enhanced to allow cross-site linking of wiki articles.

Regards
Axel

ttownsend

Hi Axel -

You approach sounds really very interesting - are you able to share any code/technical details of how you did this? I am also in the position of needing a solution like this, but this would be only for my own activities (private consultant with a need to stay organized!).

Best,
Trevor