PHPackages                             sandstorm/contentcomments - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. sandstorm/contentcomments

AbandonedArchivedTypo3-flow-package[Utility & Helpers](/categories/utility)

sandstorm/contentcomments
=========================

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

2.0.0(7y ago)3522GPL-3.0+PHP

Since May 26Pushed 2y ago11 watchersCompare

[ Source](https://github.com/sandstorm/ContentComments)[ Packagist](https://packagist.org/packages/sandstorm/contentcomments)[ RSS](/packages/sandstorm-contentcomments/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (1)Dependencies (1)Versions (4)Used By (0)

Sandstorm.ContentComments
=========================

[](#sandstormcontentcomments)

ARCHIVED -> today, please use  instead - as this is further developed.
-------------------------------------------------------------------------------------------------------------------------------------

[](#archived---today-please-use-httpsgithubcomnetworkteamnetworkteamcontentcomments-instead---as-this-is-further-developed)

Created by Sandstorm Media in 2015.

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

Supported Neos Versions:

- Neos 1.2.\*
- Neos 2.0.\*
- Neos Master

Usage
-----

[](#usage)

- install the package
- use the new "Comments" Tab in the Inspector

Internal Working
----------------

[](#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 `CommentingContentModuleExtension` displays the commenting indicators as overlays on the current page (non-API)
- JS and CSS extensions are added using TypoScript to the page rendering.
- A `WorkspaceAspect` takes care of merging comments together on publishing (non-API)

Why did we choose this implementation?
--------------------------------------

[](#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
-----

[](#todos)

This is currently beta quality; expect to find bugs.

License
-------

[](#license)

GNU GPLv3 or later.

###  Health Score

30

—

LowBetter than 64% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity13

Limited adoption so far

Community12

Small or concentrated contributor base

Maturity65

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~567 days

Total

3

Last Release

2876d ago

Major Versions

1.0.1 → 2.0.02018-07-04

### Community

Maintainers

![](https://www.gravatar.com/avatar/2ced0d63cfdae881c32128c7f66451a013d3e24d9eed210d6a846b6d8e95fa3b?d=identicon)[sandstorm](/maintainers/sandstorm)

---

Top Contributors

[![skurfuerst](https://avatars.githubusercontent.com/u/190777?v=4)](https://github.com/skurfuerst "skurfuerst (4 commits)")

---

Tags

neoscmsphpcommentcommunicationNeosStickyNotesneoscmsnotes

### Embed Badge

![Health badge](/badges/sandstorm-contentcomments/health.svg)

```
[![Health](https://phpackages.com/badges/sandstorm-contentcomments/health.svg)](https://phpackages.com/packages/sandstorm-contentcomments)
```

###  Alternatives

[shel/neos-hyphens

A plugin for Neos CMS which provides hyphens for the inline editor

20200.7k1](/packages/shel-neos-hyphens)[shel/neos-colorpicker

A plugin for Neos CMS which provides a colorpicker editor

1494.4k6](/packages/shel-neos-colorpicker)[techdivision/ckstyles

Neos package which enables you adding your custom style classes for the CkEditor with a simple Yaml configuration

21166.3k](/packages/techdivision-ckstyles)[carbon/includeassets

Include your assets (css, js) in an easy way into Neos

14228.6k10](/packages/carbon-includeassets)[zoon/rialto

Manage Node resources from PHP

12199.4k3](/packages/zoon-rialto)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)