networkteam/contentcomments

Last activity on 5 May 2021
  • 1
  • 4595
composer require networkteam/contentcomments

A Neos package to add content comments to any node (as communication medium)

2.0.0

A Neos package to add content comments to any node (as communication medium)

Version
2.0.0
Type
neos-package
Release Date
12.12.2019 08:13:39
Source
git
Distribution
zip
Requires
Requires (dev)
None
Suggest
None
Provides
None
Conflicts
None
Replaces
None
GPL-3.0+
  • #comment
  • #communication
  • #neos
  • #stickynotes
  • #neoscms
  • #notes
e03ee7e912576870c131dc8e676367ba0692fd41

Networkteam.ContentComments

Created originally by Sandstorm Media in 2015. Updated and forked for new NeosUI by networkteam in 2018

This Package Adds Content Comments / Sticky Notes to Neos. You can comment on arbitrary nodes.

Supported Neos Versions:

Neos Version Package Version
>= 4.3 2.x
>= 3.3, < 5.0 1.x

Usage

  • install the package
  • use the new "Comments" Tab in the Inspector
  • use the setting ShowInFrontend to render comments in frontend
    • Networkteam.ContentComments.ShowInFrontend: true`
    • use the scss partial "contentComment" in your css rendering to show comments in a nice tooltip
    • there's only a icon rendered in the backend

Internal Working

  • the "comments" tab is added to all node types, alongside with the property comments. (API)
  • The comments property is a JSON-encoded array with comment objects which is manipulated by a custom Comments editor. (API)
  • A WorkspaceAspect takes care of merging comments together on publishing (non-API)

Why did we choose this implementation?

There generally are multiple ways of storing comments:

  • we can add them to the nodes themselves, as node property (the way it is done currently)
  • we can add them to the nodes themselves, using a special database column
  • we can store them as extra nodes and somehow link them together
  • we can store them as extra domain objects and somehow link them together.

As a first step, we wanted the exact same publishing behavior than with normal content, i.e. a content note should appear exactly in the workspace/content dimension where the specific content is located. Furthermore, we thought it would be very strange if the user created completely new content, leaves TODO notes for himself, but does not publish yet -- and still notes would already be visible to other people in their workspaces. I think that behavior does not really make sense -- that's why we handle the notes currently in the same manner as normal content, with all the same workspace and shine-through logic.

TODOs

This is currently beta quality; expect to find bugs. Still valid.

License

GNU GPLv3 or later.

The content of the readme is provided by Github
The same vendor provides 14 package(s).