PHPackages                             helmich/neos-disqus - 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. helmich/neos-disqus

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

helmich/neos-disqus
===================

Add Disqus discussions to your site

v1.1.0(11y ago)224MITHTML

Since Apr 16Pushed 11y ago1 watchersCompare

[ Source](https://github.com/martin-helmich/neos-disqus)[ Packagist](https://packagist.org/packages/helmich/neos-disqus)[ RSS](/packages/helmich-neos-disqus/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (3)Versions (3)Used By (0)

Disqus integration for TYPO3 Neos
=================================

[](#disqus-integration-for-typo3-neos)

This is a TYPO3 Neos plugin that integrates Disqus discussions into your site (in case you're -- like me -- too lazy to implement your own commenting system in Neos).

Setup
-----

[](#setup)

### Requirements

[](#requirements)

Tested with TYPO3 Neos 1.2. Should work with other releases too, though.

### Installation

[](#installation)

Composer. Easy.

```
composer require helmich/disqus

```

Integration as individual content element
-----------------------------------------

[](#integration-as-individual-content-element)

You can insert a Disqus discussion as an individual content element. It is listed under "Plugins" when inserting a new content element.

The "comment" content element is not inline-editable. There are two options you can change using the inspector, though:

- **Site name**. This is your short site name under which your site is registered at Disqus. When including more discussion elements, it might be a good idea to leave this empty and set this value via TypoScript (see below for that).
- **Thread identifier**. The identifier that is used for the comment thread. When left empty, the node identifier of the nearest document node will be used as a discussion identifier (which is a quite sensible default that should work in most cases).

When integrating more than a few discussions, it will become tedious to configure your site name for each one individually. You can override the site name using TypoScript:

```
page {
    prototype(Helmich.Disqus:Discussion) {
        shortname = 'your-site-name'
    }
}

```

Integrate Disqus on all pages
-----------------------------

[](#integrate-disqus-on-all-pages)

You can use this plugin to integrate Disqus discussions on all (or a subset) of all pages using TypoScript:

```
page = TYPO3.Neos:Page {
    // Other definitions...

    body {
        parts {
            discussion = Helmich.Disqus:Discussion {
                // Override template if necessary:
                // templatePath = '...'

                // Override site name if necessary:
                // shortname = 'your-site-name'
            }
        }
    }
}

```

Inside your page fluid template, then simply render the content element:

```
{parts.discussion -> f:format.raw()}

```

Integrate comment count
-----------------------

[](#integrate-comment-count)

You can also integrate a comment count in overview pages. Simply insert an object of type `Helmich.Disqus:Count` anywhere in your page, and add an `data-disqus-identifier` attribute to your links.

```
page = TYPO3.Neos:Page {
    // Other definitions

    footer {
        disqusCount = Helmich.Disqus:Count {
            shortname = 'your-site-name'
        }
    }
}

```

In template:

```

    0 Comments

```

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity64

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 ~0 days

Total

2

Last Release

4050d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/38724147?v=4)[helmich](/maintainers/helmich)[@helmich](https://github.com/helmich)

---

Top Contributors

[![martin-helmich](https://avatars.githubusercontent.com/u/2538958?v=4)](https://github.com/martin-helmich "martin-helmich (6 commits)")

### Embed Badge

![Health badge](/badges/helmich-neos-disqus/health.svg)

```
[![Health](https://phpackages.com/badges/helmich-neos-disqus/health.svg)](https://phpackages.com/packages/helmich-neos-disqus)
```

###  Alternatives

[kaystrobach/development-tools

111.9k](/packages/kaystrobach-development-tools)

PHPackages © 2026

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