# About

> Meet the maintainer, understand the catalog's independence, and explore the scope of professional support.

PHP Ecosystem is an independently maintained place to discover PHP libraries,
Yii extensions, and practical documentation. The name is provisional while the
site's identity takes shape.

## Maintained by Wilmer Arambula

Wilmer Arambula, known as
[terabytesoftw on GitHub](https://github.com/terabytesoftw), brings together work
from [Yii2 Extensions, PHP Forge, and UI Awesome](/docs/projects/index.md). The portal connects
that work with its guides, package requirements, and source repositories.

Community packages remain the work of their named maintainers. Their presence
here does not transfer authorship, maintenance, or support responsibility to
Wilmer.

## An independent resource

This portal is not an official Yii website and does not speak for the Yii team.
Official framework resources are identified in the
[documentation gateway](/docs/documentation/index.md) and the [Yii3 guide](/docs/ecosystems/yii3/index.md).

Catalog review checks the information supporting a listing. It is not a security
audit, certification, or guarantee that a package suits a particular application.
The [contribution policy](/docs/contribute/index.md) explains how records are proposed,
reviewed, corrected, and removed.

## Professional support

Professional work starts with a specific application problem and an agreed scope.
Useful starting points include:

- An integration with defined package versions, acceptance checks, and a handoff;
- an upgrade assessment covering dependencies, compatibility risks, and a
  migration plan;
- a focused code or architecture review with documented findings and next steps.

Review [Wilmer's public GitHub profile](https://github.com/terabytesoftw) for his
work and the contact options he chooses to publish. Availability, deliverables,
and terms must be agreed before an engagement begins. A catalog entry does not
include professional support.

## Maintenance sponsorship

Sponsorship supports ongoing maintenance and is separate from a client engagement.
Any future sponsor acknowledgment will be identified clearly. Sponsorship does
not buy catalog acceptance, compatibility claims, or preferential ordering.