How to create a project

Projects make it easy for users to manage and copy their WordPress sites from the WordFleet dashboard. In this guide, we’ll show you how to create a new project.

Please note that this guide is now updated and covered by the WordPress sites guide, but remains here for those that need it.

Project creation:

1. Navigate to the projects pages, and then click on the New Project button.
   
2. Choose a project name.
   
3. Enter the domain for this project.
   
   • You must own or have control over this domain name in order to route public traffic to your server.
     
4.  Change the project slug name if desired.
   
   • This computer friendly name is copied from the domain name by default, but you can edit it if needed.
     
5. Select your backup retention time.
   
   • This is entered in days, and can range from 14 days up to 3650 days (ten years).
     
   • This value will apply to all backup images for all sites within this project.
     
   • This value determines how long a backup is retained. Backup frequency is select on a per-site basis.
     
6. Finish the process by clicking “create project”

Once done, you can now begin creating new WordPress sites or importing existing sites into your project. Note that you will need to create a server first to do this.

How do I use a project?

Informational sites

For informational sites, the typical flow is development to staging to production:

• dev
  
  • Do your development on a development site, where it’s okay to break and test things
    
  • The typical development site uses the dev subdomain. For example: dev.foobar.com
    
• staging
  
  • Optionally, push your finished work to a staging site to check that everything works and to show it off to your colleagues and/or customers before going live
    
  • The typical staging site uses the staging subdomain. For example: staging.foobar.com
    
• live/prod
  
  • When ready to show your work to the world, push it to the live or production site for all to see.
    
  • The typical live site uses the www subdomain and root domain name. For example, www.foobar.com and foobar.com.

We recommend putting development and staging sites behind a basic password authentication so that the public doesn’t have access to them.

Dynamic sites, such as e-commerce and forums

For sites like e-commerce sites and blogs, it’s typically a bad idea to overwrite the site directly as that can override your database.

If you are doing development work on the theme, one common flow is to:

1. Keep the theme in a Git repository, separate from the site
   
2. When testing, copy the live site to the development site, and then do your theme development work on a password protected development site.
   
3. Once tested and ready to deploy, push your theme to the live site (or a staging site first).