Script workspace organization and naming
ExpertApply naming conventions, folder structure, and documentation practices that keep the script workspace navigable as solutions grow.
What you'll learn
- A practical naming convention for scripts by context and purpose
- How to organize scripts into folders by module or workflow
- How to document scripts without cluttering them
A FileMaker solution with hundreds of scripts becomes unmanageable without deliberate organization. Consistent naming conventions, folder structure, and brief inline comments allow new developers to navigate the script workspace and understand the solution architecture at a glance.
Stuck is a valid status
Need a second brain on this one?
If this lesson just collided with your real schema, script stack, or deadline, book consulting and turn the confusion into a concrete plan.
Naming conventions
Prefix each script name with the context it runs in, followed by a verb-object pair. Common prefixes: "NAV" (navigation), "CRUD" (data operations), "UI" (interface changes), "BG" (background/server-side), "UTIL" (reusable utilities).
# Examples of well-named scripts: NAV - Go to Contacts List NAV - Open Contact Detail [ id ] CRUD - Contact: Create CRUD - Contact: Update Status CRUD - Invoice: Generate PDF BG - Server: Rebuild Search Index UTIL - Format Phone Number UTIL - Validate Email Address
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo