Where to Find Valinor's Documentation or Latest Version

Updated

The official entry point is valinor-php.dev. Visiting the root domain redirects to a latest/ path, which is where the current documentation lives. If you want the newest usage instructions, start there rather than at the bare hostname.

What happens when you visit the site

The root URL does not serve content directly. According to the site itself, it issues a redirect:

Redirecting to latest/ ...

So valinor-php.dev and valinor-php.dev/latest/ lead to the same place in practice. The redirect exists so that the root address always points at the current version instead of a frozen snapshot.

Why the latest/ path matters

Valinor is described as a PHP library that maps any input into a strongly-typed value object structure. Documentation for a library like this changes as the API evolves, so the site keeps a versioned structure with latest/ as the moving pointer.

You want Go to
Current documentation valinor-php.dev/latest/
Root domain (redirects) valinor-php.dev
A specific pinned version A versioned path under the same domain, if one is published

The practical consequence: bookmark the latest/ URL if you want to stay on current docs, or pin a versioned URL if you need docs that match a specific release in your composer.json.

How to confirm you are on the right version

  1. Open valinor-php.dev and let it redirect.
  2. Check the URL in the address bar — it should end in latest/ (or a version segment).
  3. Compare the documented API against the version constraint you installed, for example the valinor requirement in your composer.json.
  4. If they differ, look for the matching versioned documentation path instead of latest/.

Common snags

  • Assuming the root URL is the docs. It is only a redirect; the real content is one level down.
  • Reading latest/ docs against an older installed release. Methods and signatures may not match what your locked version supports.
  • Treating a redirect as an error. A Redirecting to latest/ ... message is expected behavior, not a broken page.

If you only need one takeaway: use valinor-php.dev/latest/ for current documentation, and switch to a version-specific path when your installed release differs from the latest.