Neos: a content application platform and CMS

Sources and evidence limits

The only evidence supplied is the Neos documentation landing page at docs.neos.io, which is short. Where that page is silent, this guide says unknown instead of guessing. Lifecycle is recorded as unknown because the page does not state a support status.

What Neos is

The landing page describes Neos as a "highly individual Content Management System" that is flexible and has many useful features. The project focus for this track is a content application platform. In PHP terms, Neos is a CMS product. It is not the PHP language or PHP core, not an async library, not a framework adapter and not a standalone PHP runtime. It runs on PHP and sits at the application layer.

It helps to keep these layers apart:

• PHP core is the language and its engine. It knows nothing about pages, editors or content.
• Framework components are reusable libraries that developers assemble into applications.
• A CMS product such as Neos, like Drupal CMS, packages content management features for editors and developers. Drupal CMS is a different product from PHP core and from Neos. Do not conflate them.

The supplied page does not say what Neos is built on internally, so this guide makes no claim about its underlying framework or components.

What the source tells us about structure

The documentation is split into four sections:

1. Learn Neos: the Manual, which explains every aspect in detail and can be read front to back or in chapters.
2. Find Solutions: Tutorials, step-by-step instructions with one specific goal, presented as approved best practices.
3. Read API: References for day-to-day lookups.
4. Ask the community: GitHub, Discuss and Slack.

That is the extent of the evidence. The page gives no architecture diagram, no content-model vocabulary and no installation steps.

Execution and content model

The source does not describe Neos's request handling, content storage, rendering pipeline or editing interface. Those details are unknown here. Read the Manual's introduction before relying on any assumption about how content is modeled or rendered.

Classic request lifetimes versus persistent workers

Most PHP CMS products are traditionally served in the classic request lifetime: a web server hands each request to PHP, PHP builds fresh state, responds and discards that state. Cleanup is largely automatic.

A persistent worker keeps the PHP process alive and reuses it across many requests. Swoole and Open Swoole are separate projects that offer this style of long-running server, so they should not be treated as interchangeable. The Neos source packet says nothing about persistent workers, so whether Neos supports them is unknown. Do not assume it.

If you ever run any PHP application in a persistent worker, plan for state leakage. Leaks occur when data from one request survives into the next:

• static properties and global variables
• singletons or service containers that cache user, locale or tenant data
• open database transactions or connections left in an odd state
• caches keyed without the user or site
• uploaded temporary files and session data

Cleanup means resetting or rebuilding per-request state at the end of every request, avoiding mutable statics, scoping services to a request and recycling workers after a set amount of work. A CMS holds editor sessions, preview state and per-site context, so a leak could expose one user's content to another. Treat this as a serious risk and verify support in official documentation first.

Practical use cases

Based only on the stated focus (a content application platform), Neos is a candidate when you want editors to manage content, and developers to build a site or content-driven application around it. Whether it fits a given project, such as multi-site, multilingual or headless delivery, is unknown from this source.

Installation approach

The supplied page contains no installation commands, system requirements or package names, so none are given here. Inventing a Composer command or version would be misleading. The sensible approach is to:

1. Open the Manual's introduction through the official docs.
2. Find the official installation or setup instructions and the stated PHP requirements.
3. Compare those requirements to the PHP 8.4 learning track, with PHP 8.5 planned. Compatibility with PHP 8.4 or 8.5 is unknown until you confirm it.
4. Follow the official tutorial path rather than building a stand-alone imitation of a Neos setup.

The example below is only a PHP environment preflight. It does not install Neos.

Strengths

• The docs are organized by intent: learning, solving, looking up, asking.
• Tutorials aim at one concrete goal each.
• Community channels are listed: GitHub, Discuss and Slack.
• The project describes itself as flexible.

Limitations and unknowns

• Current version, license, price, support policy and deprecations are unknown.
• PHP version compatibility is unknown.
• Persistent-worker support is unknown.
• Hosting requirements, database needs and deployment tooling are unknown.
• Performance is unknown; no speed claims are made.

Deployment

The source gives no deployment guidance. When you find official guidance, check how PHP is exposed. Never expose FastCGI publicly; keep PHP-FPM behind a web server on a private interface. For local trials, bind development ports to 127.0.0.1 only. Keep secrets out of version control and read the official docs for production configuration, caching and file storage.

Next steps

Run the preflight example, then read the Manual introduction. Use the worksheet file to record what the official docs confirm about requirements and runtime model. It is not a browser exercise.

<?php

declare(strict_types=1);

$version = PHP_VERSION;
$isTrack = PHP_MAJOR_VERSION === 8 && PHP_MINOR_VERSION === 4;

echo 'Detected PHP version: ' . $version . PHP_EOL;
echo 'Matches PHP 8.4 learning track: ' . ($isTrack ? 'yes' : 'no') . PHP_EOL;
echo 'Neos requirements: unknown until confirmed in https://docs.neos.io/' . PHP_EOL;

exit($isTrack ? 0 : 1);

Neos official docs worksheet (fill in from https://docs.neos.io/)

1. Supported PHP versions stated by the docs: ______ (unknown until checked)
2. Official installation method: ______ (unknown until checked)
3. Required database and extensions: ______ (unknown until checked)
4. Content model vocabulary from the Manual: ______
5. Does the documentation describe persistent workers? ______ (unknown until checked)
6. Documented deployment guidance: ______
7. License and support status: ______ (unknown until checked)

cd neos-prep
php --version
composer --version
php preflight.php