Every [Entry](/entry/term-entry) has a **key** string that uniquely identifies it. For example, the key of this { this } entry is **{ this.key }**. The key appears the in the URL of each entry - for example, the UR for this term ends with `/entry/{ this.key }`. You _can_ edit an entry to change its key, unlike its [VNID](/entry/term-VNID).

Term

An Entry is the core concept in Neolace. Each Neolace site is a collection of Entries. Every Entry has a **name**, **description**, **[key](/entry/term-key)** (friendly ID), and [VNID](/entry/term-VNID) (permanent unique ID). Entries can also have **properties** (which can include relationships with other Entries) and **content** (like articles, images, or files). Every Entry is of exactly one Entry Type, which defines what properties and content that Entry can or must have.

Entry

A VNID is the internal identifier for each object that Neolace uses. For example, every [Entry](/entry/term-entry) has a unique VNID, as does every Entry Type, every User, every Site, etc. A VNID is a type of [UUID/GUID](https://en.wikipedia.org/wiki/Universally_unique_identifier) encoded into a short string. As an example, the VNID of the entry that defines this term "VNID" in the documentation is { this.id }. Generally, VNIDs are only of interest for developers, and users will generally use [keys](/entry/term-key) instead.

VNID

Junction is the Neolace resource hub, with documentation, blog posts, tutorials, and more.

Key