> ## Documentation Index > Fetch the complete documentation index at: https://help.hubsy.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Folder Organization > Advanced strategies for organizing folders in Hubsy Cloud ## Master Folder Organization Learn advanced techniques for organizing folders to maximize productivity and keep your files easily accessible. ## Organization Principles Group related files together based on projects, topics, or departments Keep folder depth to 3-4 levels max for easy navigation Use standardized naming conventions across all folders Periodically review and clean up folder structure ## Folder Naming Strategies ### Naming Conventions Use prefixes for sorting and categorization: ``` 01_Active_Projects 02_Completed_Projects 03_Archives 04_Templates ``` **Benefits:** * Maintains order regardless of file system * Easy to reorder priorities * Clear visual hierarchy Organize by dates for time-sensitive content: ``` 2024-Q1_Marketing_Campaign 2024-Q2_Product_Launch 2024_Annual_Reports ``` **Benefits:** * Chronological organization * Easy to find by time period * Natural archiving system Organize by category or department: ``` Clients Internal_Docs Marketing_Materials Sales_Resources ``` **Benefits:** * Intuitive grouping * Clear purpose * Easy team navigation Organize by project or initiative: ``` Project_Alpha Project_Beta Project_Gamma_COMPLETED ``` **Benefits:** * Project-centric view * Clear project boundaries * Easy status indication ## Creating Folder Templates ### Template Structure Create reusable folder templates for common use cases: Plan your template structure: Example for Client Projects: ``` [Client_Name] ├── 01_Contracts ├── 02_Proposals ├── 03_Deliverables ├── 04_Communication └── 05_Invoices ``` 1. Create folder named `_TEMPLATE_Client_Project` 2. Build out the subfolder structure 3. Add README files with instructions 4. Include any template files When starting new project: 1. Duplicate template folder 2. Rename with project/client name 3. Remove template placeholder files 4. Start adding project files Update templates as you learn: * Add folders for new needs * Remove unused sections * Update README instructions ### Example Templates ``` Campaign_[Name] ├── 01_Strategy │ ├── Brief.docx │ └── Research ├── 02_Creative │ ├── Design_Files │ ├── Final_Assets │ └── Stock_Photos ├── 03_Copy │ ├── Drafts │ └── Final ├── 04_Analytics │ └── Reports └── 05_Deliverables ``` ``` Client_[Name] ├── 01_Discovery │ ├── Initial_Meeting │ └── Requirements ├── 02_Contracts │ └── Signed ├── 03_Project_Files │ ├── Design │ ├── Development │ └── Testing ├── 04_Deliverables └── 05_Invoices ``` ``` Content_[Topic] ├── Research │ ├── Sources │ └── Notes ├── Drafts │ ├── v1 │ ├── v2 │ └── Final ├── Assets │ ├── Images │ └── Videos ├── Final_Published └── Analytics ``` ``` Event_[Name]_[Date] ├── Planning │ ├── Budget │ └── Timeline ├── Marketing │ ├── Graphics │ └── Promotions ├── Logistics │ ├── Venue │ └── Vendors ├── Content │ ├── Presentations │ └── Handouts └── Post_Event ├── Photos └── Follow_Up ``` ## Folder Color Coding (Coming soon) Organize visually with colors: * **Red**: Urgent/High Priority * **Orange**: In Progress * **Green**: Completed * **Blue**: Reference/Archive * **Purple**: Templates ## Smart Folder Organization ### By Project Status Organize folders by current status: ``` 📁 Active_Projects 📁 On_Hold_Projects 📁 Completed_Projects 📁 Archived_Projects ``` **Workflow:** 1. New projects start in Active 2. Move to On Hold if paused 3. Move to Completed when done 4. Archive after 6 months ### By Access Frequency Optimize for access patterns: ``` 📁 Daily_Access 📁 Weekly_Access 📁 Monthly_Access 📁 Rarely_Accessed ``` **Benefits:** * Quick access to frequently used files * Natural prioritization * Clear indication of importance ### By Team/Department For collaborative environments: ``` 📁 Teams ├── 📁 Sales ├── 📁 Marketing ├── 📁 Development └── 📁 Support 📁 Shared_Resources 📁 Company_Wide ``` ## Folder Maintenance ### Regular Cleanup Set recurring reminders: * Weekly: Review active projects * Monthly: Clean up downloads/temp files * Quarterly: Archive old projects * Annually: Deep cleanup Look for: * Duplicate files * Old versions no longer needed * Empty folders * Misplaced files * Outdated content Move completed/old projects: 1. Create Archive folder structure 2. Move projects > 6 months old 3. Compress if needed 4. Document what's archived Improve organization: * Merge similar folders * Split overly large folders * Flatten unnecessary nested folders * Update naming for clarity ### Folder Hygiene Rules Every file should be in a folder: * Root folder should only contain folders * Use "Inbox" folder for temporary files * Sort inbox regularly Files should have one logical location: * Avoid duplicate file storage * Use shortcuts/links if needed * Document file location conventions Keep hierarchy balanced: * Similar folders at similar depths * Don't nest too deep (max 4 levels) * Don't keep everything flat either Add README to complex folders: * Explain folder purpose * Document naming conventions * List file types expected * Include workflow notes ## Advanced Techniques ### Dynamic Organization Create organization that adapts: Move old content annually: ``` 📁 Active ├── Current projects... 📁 Archive ├── 📁 2024 ├── 📁 2023 └── 📁 2022 ``` For time-based work: ``` 📁 Current_Quarter_Q1_2024 📁 Past_Quarters ├── 📁 Q4_2023 ├── 📁 Q3_2023 └── ... ``` Promote/demote based on status: ``` 📁 01_Backlog 📁 02_In_Progress 📁 03_Review 📁 04_Done ``` Move folders between status levels ### Cross-Reference System For files that belong in multiple categories: 1. Store file in primary location 2. Create shortcuts/links in secondary locations 3. Document relationships in README 4. Use tags when available (coming soon) ## Collaboration Considerations ### Shared Folder Best Practices When working with teams: * **Clear Ownership**: Designate folder owners * **Permission Levels**: Set appropriate access * **Documentation**: Include folder guidelines * **Notifications**: Set up activity alerts * **Regular Sync**: Schedule team organization reviews ### Naming for Teams Make folders clear for everyone: * Avoid abbreviations * Use full, descriptive names * Include department/team name * Add status indicators * Document any codes used ## Migration Strategies ### Reorganizing Existing Files * Design ideal folder structure * Get team input if shared * Document conventions * Create templates * Build all folders * Add README files * Set up permissions * Test with sample files * Move one section at a time * Test after each migration * Update any links * Notify team members * Verify all files moved * Check for stragglers * Archive old folders * Update documentation ## Next Steps Learn file management best practices Organize folders for team collaboration