> ## Documentation Index
> Fetch the complete documentation index at: https://help.kenekt.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Kenekt Structure

Understanding the hierarchy of information in Kenekt will help you navigate around efficiently.

## The Hierarchy

Kenekt uses a four-level hierarchy:

```
Development (optional)
  └── Project
        └── Lot
              └── Package
```

### Developments

A **Development** is the estate that groups related projects. Examples:

* "Hills Estate"
* "Modeina Estate"

Use a Development when an estate is released in stages, where each stage is a Project inside the Development. A Development holds:

* Name and location (street, suburb, state, postcode. The region is set automatically)
* Type: Home + Land or Apartment (new stages inherit this)
* Estate-level photos, videos and document folders (masterplans, design guidelines, estate brochures)

Developments are optional: a standalone Project doesn't need one. On the Projects screen you can select existing projects and **Group into Development**, or use **Add Stage** on a development to create a new project inside it. Agents don't browse Developments directly; estate photos and documents flow through to the packages they view.

### Projects

A **Project** represents a stage or land release. Examples:

* "Hills Estate Stage 5" (a stage within the Hills Estate development)
* "Greenfield Gardens"
* "Coastal Views Development"

Projects contain basic location information (suburb, state) and can have multiple lots.

### Lots

A **Lot** is an individual land parcel within a project. Each lot has:

* Lot number and address
* Land dimensions (width, depth, area)
* Land price
* Title/registration date
* Status (Available, Under Offer, Sold)

A lot can have multiple packages attached.

### Packages

A **Package** is the sellable product, typically a house and land combination. Each package includes:

* A lot (the land)
* A design/floor plan (the house)
* A facade (the exterior style)
* Pricing (land + build + inclusions)
* Inclusions and upgrades

## Data Reuse

We focus on data reuse to minimise data entry. For example:

* **Development Media & Documents**: Photos and document folders added on a Development flow down to every stage, lot and package; estate documents appear on the package as Project Files in the portal
* **Lot Images**: By adding images on a Lot, you don't need to add them to each package
* **Designs**: Create a design once, use it across multiple packages
* **Facades**: Link facades to designs, automatically available on packages
* **Inclusions**: Set at library level, cascade down to packages (inclusions attach from the Project level down, not on Developments)

## Navigation

You can move through Kenekt using internal links:

* Click a **Development** to see its stages
* Click a **Project** to see its lots
* Click a **Lot** to see its packages
* Click a **Package** to edit details

## Why This Structure?

This hierarchy allows:

* **Grouping**: Stages of the same estate stay together and share estate-level media and documents
* **Flexibility**: One lot can have multiple package options
* **Efficiency**: Reuse designs and facades across packages
* **Clarity**: Clear separation between land and build components

## Example

**Development:** Hills Estate

* **Project:** Hills Estate Stage 5
  * **Lot 42:** 400m², \$350,000
    * **Package A:** Lot 42 + ACACIA design + Modern facade = \$650,000
    * **Package B:** Lot 42 + BANKSIA design + Traditional facade = \$720,000


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.