Managing your projects

  Written by The Jahia Team
   Estimated reading time:

About projects

You can create multiple projects, or virtual sites, within a single Jahia server. Note that we use project and site interchangeably although they have slightly different meanings. A site has its own set of pages, content, files, and more. A project is a global term, as you can use Jahia to create and manage content used in applications, which are not technically sites as they do not contain pages.



Each site or project can have its own:

  • Domain
    You can choose to manage one site on and another site on, while still hosting both on the same Jahia server)
  • Site Map
    Along with its own structure
  • Groups
    For example, you can have two separate Authors groups with different members for site A and B
  • Settings
    (See features described in section two)

However, each site shares the following with the other sites:

  • Database and API
    This makes it possible to access content objects available in other virtual sites. This means that identical contents can be easily re-used across multiple sites (e.g., news items that are the same for several departments with separate sites), although security issues may arise with shared platforms (e.g., the sites of two separate companies are hosted on the same server).
  • Sets of templates
    For the sites that share the same set of templates.
  • Modules
  • Category tree
  • Users
    LDAP or Jahia users. It is not possible for two separate users, for example John, to have the same ID between two sites. LDAP groups, like LDAP users, are also common to all sites.

Creating a new virtual site is useful when you need to manage multiple projects, for example, a public website, one or more extranets, and several department intranets. Virtual sites allow for better role assignment and to use different views (sitemap, themes, and search results) or URLs and domains for different sites, while keeping the ability to share content, users or mash-ups.


You can access the list of all existing projects from this interface. The default project has a star next to it. Action icons to edit, delete, or export a site are available for each site.

Creating a project

There are three different ways to create a site. This topic only covers the first one in detail.

Creating a project from scratch

To create a project from scratch:

  1. Navigate to Administration>Server>Projects and click Create. In the Create your Project page enter information in the following fields.
    • Name
      Used in various parts of Jahia to designate the site. This value can be changed later on.
    • Site key
      Name of the root node of the site. This name will appear in the default URLs, since all pages and site contents will be stored under it. Therefore, it is recommended to enter a short and descriptive title. You will not be able to change this value later on, so make sure to choose it wisely.
    • Server name
      Name of the default domain where this site is located. If the site you are creating is not going directly into production but is rather used as a test or development site, then leave localhost in the field, as this value can be properly configured on the production server later on. If in doubt, always leave the localhost value and ask an administrator or a hosting specialist. This value can be changed later on.
    • Additional server names
      Names of additional domains from which this site can be accessed. You separate multiple server names with commas, for instance:, . This value can be changed later on.
    • Description
      Used to add details about the site. This value can be changed later on.
    • Set as the default project
      If this check box is selected and the platform hosts several sites, visitors will be redirected to this site when they access the server without indicating the desired site. This value can be changed later on.
    • Create an administrator for the new project
      This option creates a user account with all permissions on the current site. This option is relevant if the site is going to have a specific webmaster. If the webmaster uses the root account or if a dedicated user account already exists (in Jahia or an enterprise directory), then it is not necessary to create a new account.
  2. Select the site’s template and default language and then click Next.
    • Please choose a template set
      Select the desired template set in this drop-down menu. If the template set has a preview image, it displays below the menu to show to a sample of how the page renders.
    • Choose modules to be deployed
      By default, all projects benefit from the components and features that are part of the core software (default module). Modules listed here are deployed on the Jahia platform (the WAR files has been deployed) that can be optionally activated on the project you are creating. Each module listed here can provide new content types or new features usable by editors.
      Note: When administrator create a new site, developers or the project responsible is supposed to have given them previously the list of modules to be activated. If this is not the case, modules may be deployed later through the Studio (development or staging platforms) or through the Manage Modules panel in Administration>Server if it is a Production platform (when Production Mode is activated Studio is not available).
    • Select the project default language
      Contains languages and their local variants. With a multilingual site, select the language that is the most important to you. Visitors will be redirected to this language if they try accessing the site without specifying the desired language.
  3. The confirmation screen shows a summary of project values for you to perform a last check before creating the project. If necessary, click Previous to return the page that has information that you want to correct. Otherwise, click Save.
    Step 3

    A loading icon displays while the server is creating the site.

For direct access to the newly-created site, select Go to Page Composer or click the Edit button on the same row. You are redirected to the first page of the site. This page is more or less empty depending on the selected template set, but it is ready to be filled.

Using a prepackaged project

This option can be used to create a new site containing ready-made pages and contents (typically, examples provided by Jahia as a demo under the name Digitall). This feature can be useful when you frequently need to import a site or create new sites from an existing one.

The list of prepackaged projects can be populated by copying an export file of the site in the digital-factory-data/prepackagedSites folder, or progammatically using modules (see the Digitall example).

To import a prepackaged project, in the drop-down list, select the desired project and click on the Next button.


On the Import page, provide the project’s title, domain name and unique identifier for default URLs, then click on the Import button.


The imported site then appears in the list of your projects.

Importing a previously exported project

This option makes it possible to select a .zip file from a previous exportation on a local hard drive. The exportation will have been carried out via the dedicated Jahia interface (see further down). A new project will be created, with the exact same settings and contents as the exported site.

You can only import a  project that was previously exported in the same version of Jahia.

Deleting a project

To delete:

  • a single project, click on the corresponding Delete 
    . Be aware that this action cannot be undone. It is highly recommended to export the site before deleting it.
  • multiple projects, check the corresponding boxes, then click on Delete 
    in the action menu at the top.


Exporting a project

Several situations can require exporting a project:

  • Backup
    An exported site can be imported back in the exact same state as it was. However, this solution requires a manual intervention by an administrator and in no case should be considered a reliable backup method.
  • Transfer to another server
    Can be used to duplicate a site at specific times to work on another server, to run tests, to use as a basis to start new projects etc.
  • Transfer from a development server to a production server
    It can be convenient to export a project that was completed and pre-filled with content in a development environment and then import it on its future production server.

You have the choice to export the staging version (default workspace) or both the staging and published version (live workspace).

To export staging version of a single project web site only, select the checkbox in front of its name.

Check the selected project(s) you wish to export and click the "Export (staging content)" button.


To export both the staging and published versions of a single project or multiple projects, check the corresponding box(es) on the left and choose "Export" in the action menu.

The system site can also be exported (but not deleted, renamed or modified). This option is useful if, for instance, shared content has been stored here to make it usable from all sites.

Editing project properties

To edit a project’s properties, click on its title. In the next screen, you can edit the following fields:

  • Project name
  • Server name(s)
  • Project description
  • Set as the default Project
  • Activate or deactivate modules on the site

Other site-related settings

Some properties are also directly in Page Composer. In the Selector, you can use the contextual menu (click on the three-dots icon) to edit the node for a web site.


And access additional information and settings.


You can for instance set a different title for your site for the different languages, by specifying them in the Title field (which is different from the Site title field, which is unique for all languages).