Concepts
Built-in vs Custom vs Internal
Clarifies the boundary between official package modules, project-specific modules, and internal runtime classes.
Built-in vs Custom vs Internal
Built-in
Built-in modules and utilities are official package exports.
Examples:
StringProgressStringResponsiveStringModuleScrollControllerframeDOM
If it is exported from the package, it belongs to the supported public surface.
Custom
Custom modules are modules written on top of StringTune for a specific project or team.
They can depend on built-in concepts, but they are not part of the official package contract unless they are exported by the package.
That is why this docs site keeps them in a separate section.
Internal
Internal runtime classes exist to make the package work, but they are not meant to be consumed directly.
Examples include managers, caches, internal observers, and private fields on the singleton runtime.
Documentation rule
This docs site documents:
- public exports
- supported attributes
- supported events
- supported CSS variables
- supported integration patterns
This docs site does not document private access tricks as if they were stable API.