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

# Model Organization

> Best practices for organizing your CAD models and projects

## Project Structure

### Folder Hierarchy

```text theme={null}
Project Name/
├── Base Components/
├── Features/
├── Assemblies/
└── Manufacturing/
```

<Tip>
  Create a consistent folder structure at the start of each project. This makes it easier to find and manage components as your project grows.
</Tip>

## Naming Conventions

### Components

Follow a clear naming pattern:

```text theme={null}
[Type]_[Function]_[Version]
```

Examples:

* `BASE_Platform_v1`
* `FEATURE_MountingHole_M6`
* `ASSY_TopModule_Final`

### Features

Use descriptive, consistent names:

```text theme={null}
- Hole_M6_Through
- Fillet_R5_External
- Pattern_Circular_6x
```

## Version Control

### Component Versions

Track changes systematically:

1. Use version numbers (v1, v2, v3)
2. Add date stamps when needed
3. Keep notes on major changes

<CodeGroup>
  ```text Version Example theme={null}
  BASE_Platform_v1    // Initial design
  BASE_Platform_v2    // Added mounting points
  BASE_Platform_v2.1  // Modified hole pattern
  ```

  ```text Change Notes theme={null}
  v1  - Basic structure
  v2  - Added mounting features
  v2.1 - Updated hole spacing
  ```
</CodeGroup>

## Model Tree Organization

### Structure

```text theme={null}
Assembly/
├── 01_Base
│   ├── Base_Plate
│   └── Support_Structures
├── 02_Features
│   ├── Mounting_Holes
│   └── Alignment_Pins
└── 03_References
    ├── Center_Planes
    └── Construction_Geometry
```

### Reference Geometry

Keep construction elements organized:

* Named reference planes
* Center axes
* Construction sketches

## Best Practices

### 1. Component Management

* Group related components
* Use subfolders for complex assemblies
* Keep reference geometry separate

### 2. Feature Organization

* Order features logically
* Group related operations
* Name patterns clearly

### 3. Assembly Structure

<CodeGroup>
  ```text Main Assembly theme={null}
  ASSY_Main/
  ├── SUB_Base
  ├── SUB_Mechanism
  └── SUB_Housing
  ```

  ```text Sub-Assembly theme={null}
  SUB_Mechanism/
  ├── COMP_Shaft
  ├── COMP_Bearings
  └── COMP_Gears
  ```
</CodeGroup>

## Working with Teams

### Shared Components

* Use clear component names
* Document dependencies
* Note any constraints

### Collaboration Tips

1. **Standard Naming**
   * Follow team conventions
   * Use clear descriptions
   * Include version numbers

2. **Documentation**
   * Add comments to complex features
   * Note design intentions
   * Document dependencies

<Note>
  Consistent organization is key for team projects. Establish standards early and document any deviations.
</Note>

## Project Management

### File Organization

```text theme={null}
Project_Name/
├── CAD/
│   ├── Components/
│   ├── Assemblies/
│   └── Manufacturing/
├── Documentation/
└── References/
```

### Design States

Track model status:

* `WIP` (Work in Progress)
* `REVIEW` (Under Review)
* `APPROVED` (Final Version)
* `DEPRECATED` (Obsolete)

## Tips for Success

<CardGroup cols={2}>
  <Card title="Regular Cleanup" icon="broom">
    Remove unused features and organize regularly
  </Card>

  <Card title="Clear Hierarchy" icon="folder-tree">
    Maintain logical structure from start
  </Card>

  <Card title="Version Control" icon="code-branch">
    Track changes and maintain history
  </Card>

  <Card title="Documentation" icon="book">
    Keep notes on important decisions
  </Card>
</CardGroup>

## Common Mistakes to Avoid

1. **Inconsistent Naming**
   * Mixed conventions
   * Unclear descriptions
   * Missing versions

2. **Poor Structure**
   * Deep nested folders
   * Unclear hierarchies
   * Mixed component types

3. **Lack of Documentation**
   * Missing change notes
   * Undefined references
   * Unclear dependencies

<Tip>
  Take time to organize at the start of each project. Good organization saves time and reduces errors in the long run.
</Tip>

<Note>
  Remember that organization is an ongoing process. Regular maintenance keeps your projects manageable as they grow in complexity.
</Note>