Nconnect (formerly OnSemble Intranet) is an mployee intranet that keeps everyone connected, a digital workplace to make employees feel valued. It is designed to keep remote teams engaged, and acts as the culture champion for the organization.
N/A
Plone
Score 9.0 out of 10
N/A
Plone is a free and open source content management system built on top of the Zope application server. Plone can be used for any kind of website, including blogs, internet sites, webshops, and internal websites.
OnSemble is solving a lot of problems that our organization had prior to its implementation:
We can track communication readership.
We can engage with our fellow teammates through chats and recognition.
We have a central location for all job-related links.
We are just now delving into adding departmental pages so folks can communicate within their teams.
I'm not sure of a scenario where OnSemble wouldn't be appropriate - if you have a company that needs to centralize communication, documentation, and share ideas, it's an excellent choice.
The larger your organization, the more appropriate Plone will be. This is not to say that Plone is a worse choice for small websites, only that the minimum investment for a Plone site is certainly higher than for other platforms. If you already use Plone for your site and are looking for a redesign or an overhaul, I would only advise switching to a different platform such as WordPress or Drupal if your organization is downsizing. For any other situation, Plone is the natural choice for your growth.
Plone is a folder-based system, organising content in a similar way desktop-users are doing for the last two decades. No need to teach non-tech customers some relational-database like paradigm for content management.
Plone is secure. It is the most secure CMS you can get your hands on.
Plone is flexible, and makes fast development easy.
Not everything is configurable or editable by Plone, and when you need to adjust or add custom pieces in, you need to deal with Zope. Zope has an ugly, confusing and difficult UI and structure as a backend.
Using 3rd party products is difficult to do - there are a few different ways to get them installed, all of which take a bit of luck to get right.
Building custom products for Plone is not fun. You've got to deal with an archaic framework to tie in that is not well documented (there is documentation about many things, but not great documentation and there are a lot of holes in the documentation).
I no longer use Plone because I got an internship in the web development field and my current place of employment uses their own content management system that they created. After getting to know other CMS's and similar software and comparing them to Plone, I would enjoy using Plone again in the future, but there are more complicated software that I'd like to learn as I progress in my field of study.
As a user: it's pretty intuitive and the only thing holding a user back from getting everything out of it is a lack of curiosity. As an admin: it's not super intuitive. The training and the setup process are crucial to be able to use and maintain the portal, and we still sometimes have questions.
Compared to the amount of Plone sites, users and customizations we have in our organization, the amount of support requests and training needed is really small
Plone is very intensive in its operations, and if not configured well it can be slow. However it is designed and built with speed in mind and with proper use of coding, templates and caching can perform extremely well under high loads. It is capable of scaling to very high load availability environments with no specific coding requirements.
I have always been pleased with my experiences with OnSemble's Support team. First, they have a great library of articles to help me study and guide for many of my questions. But when I cannot quite comprehend, or I "run into the wall", I can be assured that I'll be contacted quickly with a pleasant voice to work through whatever my question/issue may be. Kudos to OnSemble Support!
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and web content where Plone is much better
As a development company Plone allows us to provide complex web applications in a short amount of time.
Plone is quite robust and reliable so when you customize some parts you do not risk to damage other parts. This is quite positive for a web development framework,
Plone allows our clients to spread their activities among different employees improving the efficiency of content generation and management.
