First project conventions

Documentation status: guide.

The first sample must teach the rules that production projects are expected to keep.

Own the namespace

Application concepts use a project-owned prefix. A task tutorial therefore uses an identity such as tsk#task; it does not borrow a platform namespace for an application concept.

Keep examples implementation-neutral

If a historical metadata example names an implementation binding with a T prefix, the public documentation preserves the example but normalizes the public identifier from TXXX to XXX. For example, CustomClassItem, GUIDStringGeneratorInfo and CustomObjectItem are the public documentation forms.

Use portable paths in documentation

Do not publish workstation-specific absolute paths such as drive-letter test paths. Prefer placeholders and forward-slash project paths unless a certified platform-specific section explicitly requires another form.

Validate before extending

First prove package loading and model visibility. Then add collections, actions, validation, DataSets, services and reactive components.