Skip to main content

Team Collaboration

Work together and manage versions in TheDock.

Overview​

TheDock includes collaboration features for teams:

  • Version history and snapshots
  • Multi-user editing awareness
  • State management and rollback

Accessing Team Features​

  1. Click on Team in the navigation
  2. View saved states and team activity
  3. Manage versions

Version History​

Automatic Saving​

TheDock automatically saves your work:

  • Auto-save every 30 seconds
  • Save on significant actions
  • Before exports

Saved States​

Each save creates a state snapshot:

InformationDescription
TimestampWhen saved
AuthorWho made changes
ActionWhat triggered save

Viewing History​

In the Team panel:

  1. See list of saved states
  2. Click to preview a state
  3. Restore if needed

Restoring Previous States​

When to Restore​

  • Undo major mistakes
  • Return to a working version
  • Compare different approaches

How to Restore​

  1. Go to Team panel
  2. Find the state to restore
  3. Click Restore
  4. Confirm the action

What Gets Restored​

Restoration replaces:

  • Design settings
  • Template configurations
  • Module content
  • Custom code

Caution​

Restoring overwrites current state. Consider:

  • Saving current state first
  • Exporting before restoring
  • Testing restored state thoroughly

Multi-User Editing​

Conflict Detection​

TheDock detects when multiple users edit simultaneously:

  • Warning when another user has changes
  • Option to sync or override
  • Visual indicators of conflicts

Sync Process​

When conflicts detected:

  1. Notification appears showing other user's changes
  2. Review differences
  3. Choose to:
    • Keep your changes
    • Accept their changes
    • Merge manually

Best Practices for Teams​

  1. Communicate - Coordinate who's editing what
  2. Work in sections - Divide template work
  3. Save frequently - Create restore points
  4. Sync before major work - Start with latest version

Workflow Recommendations​

Small Teams (2-3 people)​

  • Informal coordination
  • Regular syncs
  • Clear ownership of sections

Larger Teams​

  • Designated roles:
    • Design system owner
    • Template builders
    • Content managers
  • Regular check-ins
  • Change documentation

Client Collaboration​

  • Build in staging environment
  • Export for client review
  • Document change requests
  • Maintain version control

State Management​

Naming States​

Give meaningful names to important states:

  • "Pre-launch final"
  • "Client review v2"
  • "Before homepage redesign"

Organizing States​

Keep your state history clean:

  • Delete outdated states
  • Archive milestone versions
  • Document major changes

Export and Backup​

Exporting Configuration​

You can export your TheDock configuration:

  • Complete design system
  • All templates
  • Custom code
  • Settings

Backup Strategy​

Regular backups:

  1. Export theme regularly
  2. Backup WordPress database
  3. Save configuration externally

Before major changes:

  1. Name and save current state
  2. Export current theme
  3. Document what you're changing

Restoring from Backup​

If needed:

  1. Import database backup
  2. TheDock state restored with database
  3. Re-export theme files

Best Practices​

1. Document Changes​

Keep notes on significant changes:

  • What changed
  • Why it changed
  • Who changed it

2. Use Meaningful Names​

Name saved states descriptively, not "Save 1", "Save 2".

3. Regular Syncing​

If working with others:

  • Sync at start of session
  • Sync before major work
  • Communicate about conflicts

4. Staged Deployment​

  • Build in development
  • Review in staging
  • Deploy to production

5. Backup Before Export​

Always save state before exporting, especially to production.

6. Clean Up History​

Remove unnecessary states to keep history manageable.

Troubleshooting​

Sync conflicts​

  • Save your work locally
  • Communicate with team
  • Manually merge if needed

Can't access states​

  • Check user permissions
  • Verify database connection
  • Contact support

Lost work​

  • Check recent states
  • Look in browser localStorage
  • Check database backups

← Back to Documentation