Structuring a website in Liferay Portal?

Question

I am working on a project related to Liferay Portal, and I hope to receive information on how to properly use the "community" and "organization" in the site structure. I'm still disappointed by the lack of documentation on this, and the Liferay internal forum seems almost dead. Can the community help me or point me in the right direction for my needs?

Answer 1

The main difference between communities and organizations in Liferay is that organizations can be organized in a hierarchy. In all other aspects, they are almost identical. Take a look at the Portal Architecture chapter in the Liferay Administrator's Guide .

Liferay has no documentation. So, usually your best guide in Liferay is your experience ;-). Or the experience of experienced Liferay developers.

I think you have already visited the forums, wikis, and blogs on the Liferay website. In addition, you can view the Liferay platinum partner website, Cignex. They have published 2 quite useful books on Liferay, and they also have a blog with useful tips.

Answer 2

Key differences between communities and organizations:

• Hierarchy
• User subscription (for example, users can access the browser and join communities).

Behind the scenes, they are “groups,” and ultimately the distinction can be eliminated.

Answer 3

Community

and code level organizations are groups

Answer 4

I can give an example of Org. If one person (XYZ), runs ABC as a lead team and works in Pune. Therefore, he is a member of ABC corp. Secondly, he is a member of the Org team, and he is a member of Pune. Therefore, we need to create a parent org with the name ABC under the fact that we need to create a child group with the name team lead and work location, etc., And Comm as another aspect of our organization.

Answer 5

I would like to mention the blog post by Jorge Ferrer about organizations or communities, which you can find here: http://www.liferay.com/web/jorge.ferrer/blog/-/blogs/7858337

He explains the purpose of creating communities and organizations from the perspective of the Liferay portal. This is a good way to understand the purpose of Comms and orgs, and when and where to use them.

Here is an excerpt:

• Communities: They were created as a way to have groups of pages that could display content and applications. The reason they were called communities is because the goal of all the initial implementation was to create online communities, but since then people really use communities for things for which the term may not apply as well as corporate sites, product sites,
  event sites, etc. It's fine.
• Organizations: They were created as a way to organize users in a hierarchy. The great thing about this hierarchy is that it allows the delegation of user administration, which is a key feature required to use some of Liferay’s largest installations, where there are hundreds of thousands or even millions of users. Later, we realized that many people created a community associated with each (or several) of
  their organizations. But maintaining this link manually was a bit of a pain, so we improved the organization so that they could have their own website. (For the curious, we did this by creating a community from below, but hiding this fact from the end user).

Answer 6

I really disagree with the comments provided, indicating that the Liferay documentation is not suitable.

Regardless of whether it is liferay or any other open source technology, you cannot get all the answers in the documentation or help. Take for example spring / java / fuse / camel / struts / hibernate etc.

In any case, to answer the question asked. Please refer to the link below, and in case of further requests go back.

https://www.liferay.com/web/jorge.ferrer/blog/-/blogs/organizations-or-communities-which-one-should-i-use-the-final-answer