DOCUMENTATION

ORDO: The Unity Project Organizer — User Manual

Version: 0.9.0 • Updated: 2025-09-16


Overview

ORDO: The Unity Project Organizer is a Unity Editor extension designed to streamline project setup and maintain project hygiene. This tool helps you create a standardized project structure and automatically keep things organized as you work.

Key features include:

  • A single-window workflow with three main tabs: Setup Project, Health, and Settings.
  • Template-driven folder structures that you can easily edit.
  • An auto-router that moves newly added files into the correct folders.
  • Import rule tags for applying per-folder importer settings for assets like textures, models, and audio.
  • A Project Health scanner that checks for common issues like empty folders, unused assets, and incorrect import settings.
  • A Template Validator to prevent folder and routing conflicts.
  • A WebGL Build Helper with quick controls for WebGL-specific settings.
  • Built-in documentation access.

Requirements & Compatibility

  • Unity 2020.3+ is recommended; it has been tested on 2021.3 LTS and newer.
  • The extension code is located under Assets/Editor/ORDO/.
  • It has no runtime dependencies.

Installation

  1. Copy the Assets/Editor/ORDO/ folder into your Unity project.
  2. Open the tool from the Unity menu: Tools → ORDO. You can choose a fixed-size utility window or a dockable one.
  3. The first time you run it, the tool will create its necessary directories:
    • Assets/Editor/ORDO/Templates/
    • Assets/Editor/ORDO/Settings/ProjectSetupSettings.asset
    • Assets/Editor/ORDO/Docs/
  4. Optionally, click Install Starter Templates in the Settings tab to add pre-made templates.

Quick Start

  1. Go to Settings → Templates, click Install Starter Templates, and select an Active Template (e.g., Starter_3D_Desktop).
  2. Switch to the Setup Project tab and click Run Full Setup. This will create the folder structure and, if enabled in settings, download a .gitignore file.
  3. (Optional) If you're targeting WebGL, use the WebGL Build Helper to apply recommended settings.
  4. Now, when you import assets, the auto-router will automatically move them into the correct folders.
  5. Periodically visit the Health tab, click Rescan, and use the Fix Import Issues button to correct any problems.

UI Tour (Single-Window)

Left Navigation

The main window has three navigation tabs on the left:

  • Setup Project: Used for initial project setup and launching helpers.
  • Health: Scans your project for issues and provides one-click fixes.
  • Settings: Manages global options, templates, and the tag glossary.

Setup Project Tab

  • Create Folders: Creates the folder structure defined by the active template.
  • Download .gitignore: Downloads Unity's official .gitignore file to your project's root.
  • Run Full Setup: Combines the above two actions into one click.
  • Template Preview: Shows a preview of the folder paths that will be created.
  • WebGL Build Helper: A card that helps you switch to the WebGL platform and apply recommended settings with one click.
  • Documentation: A button that opens the user manual file included with the extension.

Health Tab

  • Rescan: Refreshes all the health lists.
  • Fix Import Issues: Automatically corrects any importer mismatches based on your templates' rules.
  • Move Scripts Into Scripts Folder: Moves any stray C# files into the designated scripts folder.
  • Delete Empty Folders: Cleans up unused, empty directories.
  • Health Lists:
    • Empty Folders
    • Unused Assets (Heuristic)
    • Scripts Outside Scripts Folders
    • Assets with Import Issues

Note: The Packages/ folder is always excluded from all health scans.

Settings Tab

  • Add .gitignore: A toggle that controls whether Run Full Setup also downloads the .gitignore file.
  • Templates:
    • Active Template: The editable ScriptableObject that defines your project's structure.
    • Install Starter Templates: Adds pre-made templates for common project types.
    • Folder Rules: A list of rules that define folder paths, extensions, and import settings.
    • Extension Overrides: A separate, higher-priority list of ext to folder mappings.
    • Validate Template: Runs a validator to check for issues like overlapping rules.
  • Tag Glossary: A reference list of all available import tags, categorized by asset type (Textures, Models, Audio). You can copy or append these tags to your folder rules.

Core Concepts

Folder Rules

Folder rules are the foundation of your project structure. They define what an ideal folder layout looks like and what kind of assets each folder should contain.

  • Paths are relative to the Assets/ folder (e.g., Art/Textures).
  • The extensions field restricts which file types are routed to a folder. Leaving it empty makes it a catch-all folder.
  • isScriptsFolder marks the designated folder for C# scripts, which the Health scanner uses to find misplaced scripts.
  • importRuleTag is a key concept that ties a folder to a specific set of import settings.

Extension Overrides

This is a simple list of ext to folder mappings that take precedence over the more complex folder rules. Use this for specific file types that you always want to go to a certain location, regardless of the folder rule.

Import Rule Tags

Tags are a powerful policy system for enforcing consistent import settings across your project.

  • You can assign multiple tags to a single folder rule.
  • When an asset is imported, the system applies the settings associated with the tags on that folder rule.
  • The Health tab then validates these settings and provides an Auto-fix button to correct any mismatches.

Partial List of Common Tags:

  • Textures: ui, mobilelowmem, nomipmaps, pointfilter, anisox16
  • Models: noreadwrite, scale1, meshcompresshigh, rig-humanoid
  • Audio: stream, compressedinmemory, forcetomono, quality-low

A separate Tags & Templates Reference file is included with the manual for a full list of available tags.


Troubleshooting & FAQ

Q: The Tag Glossary isn’t showing anything.
A: Make sure you have an active template assigned in the Settings tab. The glossary populates based on the tags available in your templates.
Q: Assets aren’t automatically moving.
A: Check your Extension Overrides first, as they take priority. If no override exists, ensure the folder rule has the correct extensions listed. Remember that some assets (like scripts) aren't moved automatically; you can correct these with the Health tab's tools.
Q: Why is the health scan slow?
A: The scan only checks your Assets/ folder, excluding Packages/. However, larger projects will naturally take longer. For better performance, consider using a few broad, "catch-all" rules instead of many specific ones.
Q: Where are the settings and templates stored?
A: All settings and templates are stored as ScriptableObjects under the managed Assets/Editor/ORDO/ folder to keep your main Assets/ directory clean.

Extending the Tool

  • To add a new tag, extend ImportTagProfiles to include your new tag's logic.
  • To create a new starter template, define a BuildRules*() method and register it in the installer.
  • To add a new health check, extend the scanner methods and provide a clear issue string.

Uninstalling

  1. Close the ORDO window.
  2. Delete the Assets/Editor/ORDO/ folder from your project.
  3. Manually delete any orphaned files, like templates or docs, if you moved them elsewhere.