Create Sites

To create a site, select a template, name the site, and add content. If governance is enabled, before you can add content you must submit your site request, then, after it's approved, add content.

Before you can create a site, your administrator must enable site creation and make templates available to you. If you don’t see the Create option on the Sites page or there aren't any templates available, contact your administrator. See Get Started with Sites and Understand Site Governance.

If you're creating an enterprise site, which enables the use of assets, multilingual sites, and secure site taxonomies, your site will be associated with a repository, a localization policy, possibly a default language, and if the template requires the use of a site security taxonomy (SST), a parent category. If a repository and localization policy aren't available, create them, or ask your content administrator to create them. If there isn't an option to choose a parent category, then it is likely the site template you selected doesn't require using a site security taxonomy. If it does, the template would have a small badge in the corner.

Note:

With Oracle Content Management Starter Edition, translations are unavailable, governance can't be enabled, and only one site can be created. For a full feature set and unlimited sites, upgrade to Oracle Content Management Premium Edition.

1. Click Sites.
2. Click Create.
3. On the Choose Template page, select the template for your site.
   • If governance is enabled, the template will determine if the site you create is a standard site (doesn't use an asset repository or localization policy) or an enterprise site (uses an asset repository and localization policy).
4. On the Configure Site page, you see what approval is needed before the site is created, the minimum level of security required for the site, and images of the site pages. If approval is limited to specific people, click Show Approvers to see who can approve your site request.
   • If governance is not enabled, select Standard or Enterprise for the type of site you want to create.
   • If you're creating a standard site, click Next to go to the next page.
   • If you're creating an enterprise site, complete the following steps:
   1. Choose the default repository used to manage the content for the site. If you are a repository administrator and no repository is available or you would like to use a new repository, select Create a new repository and follow the steps to create a repository. For information about using multiple repositories in a site, see Give a Site Access to Multiple Repositories in Managing Assets with Oracle Content Management.
   2. If the template you selected requires the use of a site security taxonomy, select the parent category for the site. Your site assets will be categorized into a site category created for the new site under the selected parent category. The custom roles created for the new site will use this site category to restrict access to the site assets. For information on using a site security taxonomy to control access to assets in a shared repository, see Manage Sites in a Shared Repository.
   3. Select a localization policy policy for the site. If you are a repository administrator and no policy is available or you would like to use a new policy, select Create a new localization policy and follow the steps to create a policy.
   4. If the template's localization policy doesn't have a set default language, select one now. You see only those languages that are required by the localization policy.
   5. Click Next to go to the next page.
5. On the Add Details page, enter the following information.
   • Enter a name for the site. The name is used in the site URL. You can use letters, numbers, underscores (_), and hyphens (-). The URL is case sensitive. If you enter a space, it's automatically replaced with a hyphen. Do not use the name of an existing site with different capitalization. For example, if a site exists called ABC, do not create another site called Abc.

     Note:

     Don’t use the following names for site templates, themes, components, sites, or site pages: authsite, content, pages, scstemplate_*, _comps, _components, _compsdelivery, _idcservice , _sitescloud, _sitesclouddelivery, _themes, _themesdelivery. Although you can use the following names for site pages, don’t use them for site templates, themes, components, or sites: documents, sites.

   • If you're creating an enterprise site, the template policy may allow you to edit the default site prefix for friendly URL values. This prefix will be appended to content item slug values (the part of the URL specific to the page or asset).
   • If you're creating an enterprise site that requires a site security taxonomy, then repository assets are automatically duplicated by default. If creating from an enterprise template that does not require a site security taxonomy, you're given the option to duplicate, override, or update assets in the selected repository.

     Option	Description
     Duplicate Assets	New assets with unique GUIDs are created in a selected repository.
     Override Assets	Existing Assets in a selected repository are replaced with versions from the template with same GUIDs.
     Update Assets	Existing assets in a selected repository are updated to new revisions from the template only if template assets are newer with same GUIDs. Otherwise if assets in repository are newer than those in template, newer assets remain in repository at current versions.

     These options can be useful if there is no need to duplicate assets that already exist, or if you only need to update those that are newer in the template.

   • Optionally, enter a description for the site.
   • Optionally, enter a justification for this site request. This will help the site administrator determine whether the request should be approved.
6. Click Finish.

If the site request requires approval, an email is sent to the person who needs to approve it. If approved, you will receive an email notifying you it has been approved and the site will be created. If your request is denied, you will received an email notifying you it has been denied. You can see your pending requests on the Sites page, by selecting Requests in the filter menu. If the request was denied, you should see a message as to why it was denied, so you can correct the issue and submit your request again.

If the site request is set to be automatically approved, the site is automatically created. A progress bar shows the new site name and creation status. When the site is created, the name appears in the list of sites, and its status is offline.

If you created an enterprise site, a corresponding site collection is created in the repository you selected. If you share the site with a user, the user has the same permissions on the associated collection.

After your site is created, you can share the site, change the security, add and edit content, publish the site, and bring it online. See Manage Sites and Site Settings and Edit Sites.