Intro to Collections
Video Placeholder Duration: 3-5 minutes Topics covered: What are collections, creating collections, organizing pages into collections
What are Collections?
Collections are folders for organizing your Wiki pages into logical groups. Instead of a flat list of pages, structure your documentation into meaningful categories.
Why Use Collections?
Without Collections
Pages:
├── Employee Handbook
├── Development Setup
├── Time Off Policy
├── Deployment Process
├── Code of Conduct
├── Incident Response
├── Remote Work Guidelines
├── First Day Checklist
└── ...dozens more unorganized pagesWith Collections
Collections:
├── 📁 HR Policies
│ ├── Employee Handbook
│ ├── Time Off Policy
│ ├── Code of Conduct
│ └── Remote Work Guidelines
├── 📁 Engineering
│ ├── Development Setup
│ ├── Deployment Process
│ └── Incident Response
└── 📁 Onboarding
└── First Day ChecklistCreating Collections
Method 1: From Wiki
- Navigate to Pages in workspace
- Click New Collection or the folder icon
- Give it a name
- Start adding pages
Method 2: While Creating a Page
- Create a new page
- Select or create a collection to place it in
- Page is organized from the start
Collection Structure
Collections can be nested for deeper organization:
📁 Company
├── 📁 HR
│ ├── 📁 Policies
│ │ ├── Time Off
│ │ └── Remote Work
│ └── 📁 Benefits
│ ├── Health Insurance
│ └── Retirement
├── 📁 Engineering
│ ├── 📁 Guides
│ └── 📁 Processes
└── 📁 Product
├── 📁 Research
└── 📁 RoadmapsManaging Collections
Add Pages to Collections
- Open a page
- Find the collection/folder option
- Select the target collection
- Page moves to that collection
Move Pages Between Collections
- Drag and drop pages
- Or edit page location
- Update organization as needed
Rename Collections
- Right-click or open collection menu
- Select Rename
- Enter new name
Delete Collections
- Open collection menu
- Select Delete
- Choose what happens to contained pages:
- Move to another collection
- Move to root level
- Delete pages too
Collection Best Practices
Mirror Your Organization
Structure collections like your company:
- By department
- By function
- By project type
Not Too Deep
Avoid excessive nesting:
- 2-3 levels is usually enough
- Deeper = harder to navigate
- Flatten when possible
Consistent Naming
Use clear, consistent names:
- "Engineering Guides" not "Eng stuff"
- "HR Policies" not "HR"
- Include context in the name
Regular Cleanup
Maintain collection structure:
- Archive unused collections
- Merge similar collections
- Re-organize as teams change
Collections for Different Teams
Engineering
📁 Engineering
├── 📁 Setup & Tools
├── 📁 Architecture
├── 📁 Processes
├── 📁 Runbooks
└── 📁 Post-MortemsProduct
📁 Product
├── 📁 Research
├── 📁 Specs
├── 📁 Roadmaps
└── 📁 Release NotesOperations
📁 Operations
├── 📁 Procedures
├── 📁 Vendor Info
├── 📁 Compliance
└── 📁 ReportsFinding Content in Collections
Browse
Navigate through the collection tree:
- Expand/collapse collections
- Click to open pages
Search
Search finds pages regardless of collection:
- Search by title
- Search within content
- Results show collection location
Key Takeaways
- Collections organize Wiki pages into folders
- Create structure that mirrors your organization
- Nest collections for hierarchy (2-3 levels max)
- Move pages between collections easily
- Use consistent, clear naming
- Regularly maintain and clean up structure
Next Steps
Dive deeper into Wiki page features with Wiki Pages.
Next Lesson: Intro to Wiki Pages