Reference

Overview

The chapters so far told a story. This section is the index card — a rough map of the classes, features and functions WebFluid exposes, grouped by where they live. It is deliberately terse: enough to find a name and remember what it does, not a line-by-line specification.

 

This is an alpha, and the public surface will still shift. Treat this reference as a compass, not a contract, and pin your version while the alpha runs.

How the package is laid out

The import tree mirrors the layers you've worked through:

  • Core — webfluid, webfluid.core.*: the Fluid app, config, context, the shared extension registry and the runtime constants.
  • Extensions — webfluid.extensions.*: the base extension and the full battery set.
  • Surface — webfluid.surface.*: the frontend integration, Node and Tailwind tooling.
  • Additives — the Additive system, manifests and the registry helpers.
  • Utils — webfluid.utils.*: framework helpers, logging and the exception hierarchy.

Top-level exports

What you can import straight from webfluid:

  • Fluid — the application class. See Core.
  • Additive, AdditiveVersion, Manifest — the module system. See Additives.
  • version, FluidVersion — the running framework version.
  • utils, fluid, extensions, exceptions — the sub-packages.

Continue reading

From here you can continue straight with Core.