--- title: "Step 1 - Create a new development space" canonical: "https://support.appfire.com/space/CPCL/2865201736/Step%201%20-%20Create%20a%20new%20development%20space" format: markdown --- > Macro (aura-html) ![sm-lockup-logo-comala-publishing-dark.png](media://56770ac7-2c62-44ac-8381-8d6b90acfaa2) ## Overview If you already have a space for content, your production space, you can easily and safely create a new development environment using Comala Publishing. ![image](media://6d95b30c-3da3-4a22-876e-9a2827cec1ad) ## New development space Create a new Confluence space > ℹī¸ this is your **development (DEV) space** for creating and editing your draft pages Once the **development (DEV) space** is created you need to populate this new space with the content from your original production space - the (**PROD**) space - by following the steps below. ## Copy the production space to the development space > ℹī¸ The original production environment is temporarily configured as the source space for publishing. ### Copy the existing production space In the original **production (PROD) space, **navigate to the Comala Publishing dashboard: - **Space Settings > App links > Comala Publishing** ![cpc_applinks_comalapublishing_configurepublishing_space not linked.png](media://3d713827-2bce-4d1e-a407-ecbd6a4205a2) - choose **Configure Publishing** ![cpc_configurepublishing_target_developmentspace_dialogbox.png](media://d85ccd57-4035-4fc2-bcae-9c31f618cf2b) - use the **Target space** dropdown menu to add your newly created development (**DEV**) space as the **target space** - choose **Next** ![cpc_publishingconfigured_dialogbox_publishthe sourcespace.png](media://f851b471-a3c9-4cb3-9ed3-d48c189e1a77) > 📝 Do not choose **Review the Configuration** as this exits the publishing wizard. > 📝 > 📝 The default publishing configuration enables whole space publishing; single page publishing by an editor; and copying of a page content properties. These can be changed later in the space settings publishing dashboard if required. - choose **Publish the Source Space** ![cpc_publishthewhol space_confirm_dialogbox.png](media://af9eba1b-ebfa-4e97-bc22-c56de2a6f7e7) - choose **Publish** to confirm and action publishing the whole space The screen displays a progress bar showing the publishing action. ![cpc_wholespacepublish_progrress_5pages_matilde_user_productionspace_to_developmentspace.png](media://16c32dea-c92d-4dfe-bd3f-1daa51593b9c) The space publishing progress bar confirms completion. ![cpc_wholespacepublish_completed_progress_5pages_matilde_user_productionspace_to_developmentspace.png](media://a20e74f5-7c40-432b-8459-63d826fe0fa8) The [space publishing report](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/647004645) for this publishing action is automatically displayed. ![cpc_publishingreport_26jul_5pages.png](media://8ad240c7-9576-4782-9aaa-6b616395ccb1) - choose **Back** to return to the [space settings publishing dashboard](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/646252290) ![cpc_spacepublishingdashboard_taregt_developmentspace_lastspacepublish_5_pages.png](media://0371d082-15b5-40b5-bde0-26c88918d587) Displayed in the **Space Publishing** section are - summary of the last space publish action - a **See details** link to view the report for this last space publish Published pages in the **PROD** space and the **DEV** space display the publishing status byline. ### Publishing status byline Pages in each space are appended with the **Synced** [publishing status lozenge](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/646252111). - source space - **Production Space** ![cpc_developmentspace_sourcespace_syncedbyliune_publishingpopup.png](media://2c0f4835-4791-4d19-a281-34a792f280f3) - target space - **Development Space** ![cpc_developmentspace_targetspace_syncedbyliune_publishingpopup.png](media://13c4a91c-75c3-4877-a6dc-08c4ea2ca855) You can view a [publishing report](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/1072562207) listing the publishing status for all the pages in the spaces. ### Publishing report Use the [publishing report](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/1072562207) in a source space to view the publishing status for the published and synced pages in the source space and target space. > ℹī¸ Currently the **PROD** space is the source space, the pages have been published to the target space, the **DEV** space. In the Confluence sidebar in the source space (**PROD** space) - choose **Apps>Comala Publishing** ![cpc_publishingreport_notsynced_filter_nopageslisted.png](media://5f1fb2d2-3f15-4b03-8b71-4bba9f408306) The default report displays the source space pages not currently synced. These could be pages out of sync or new pages awaiting publishing. The example space has no changes since the last whole space publish and displays no pages. In the publishing status filter dropdown ![cpc_publishingreport_extract_dropdownstatustfilter_anystate.png](media://9d975ee6-c579-49de-adee-bfbb4d4f2655) - choose **Any state** ![cpc_publishingreport_sourcespace_5pages.png](media://8d1a5329-7359-4b20-9204-ccdb97f1ae23) The default report is for the pages in the **[source]** space - the current space and the original **Production Space** - all pages are synced - all pages synced by the user who undertook the space publish Toggle the report to view the **[target]** space pages - the new **Development Space**. ![cpc_publishingreport_targetspace_5pages.png](media://3c052283-a986-45f2-9538-7f88a7fbed0a) - all the pages are synced - **Last updated by** details - all are the same user - the user who published the space - **When** is the same date and time as the last sync date and time - all target space page **Version** set to v.1 The **Production Space **pages are published and synced in the new **Development Space**. > 📝 Remove page restrictions *for the user publishing the space*. These pages are > 📝 > 📝 - not published > 📝 - have no publishing status > 📝 - are not displayed in the report ### Partial publishing If not all the pages are successfully published, the space publishing report displays a **Partially completed warning** and the pages are listed in the report as **Incomplete tasks**. ![cpc_spacepublishingreport_partiallycomplet_1page_80percent.png](media://178cd4a5-447e-4ab1-9de5-675861d5183c) These pages may need to be published using the single-page **Publish** option in the workflow popup on the page. When successfully published and synced, the publishing status for the page is updated in the space publishing report. ![cpc_spacepublishingreport_extract_incomplettasks_1page_syncstatus_updated.png](media://5120a014-f1fa-4f57-a737-e0117d7d55e2) > 📝 The **Processed pages**; **Published pages**, and **Success Rate** values relate to the last whole space publish action and are only updated on the next publish space action. These values do not include pages that have page restrictions *for the user publishing the space*. ## Step 2 - Set up the development as your source space The original **Production** space ## Space homepage and publishing Ensure an appropriate homepage is defined in the published space page hierarchy before publishing any content from the new development (**DEV**) space to the production (**PROD**) space. Comala Publishing cannot publish the space home page (**Overview** page). The homepage content is static in each space - you must manually add any content as the page is not published. You can make the source space homepage and the target space homepage content dynamic by adding Confluence page macros such as - **Page tree** - **Children** - **Content by label** - **insert excerpt** - **page include** Configure the macros to source page content from the current space. > ⚠ī¸ After an initial space publishing action, changing a homepage (in either the source or target space) may result in pages being published to the root of the target space. ## Set up the new development space > 📝 Comala Publishing is designed to publish content from a source space to an “**empty**” target space. Although a space with existing pages can be configured as a target space, if you set a target space that has some existing title pages that are the same as in the source space, this can cause publishing issues. > 📝 > 📝 In this example, after copying your current production space to your new development space, you need to **delete the content (except for the space homepage) in your existing production space before publishing** from the new source development space. In the **development (DEV) space** - navigate to the Comala publishing dashboard in the **DEV** space by heading to **Space Settings > Manage pages > Publishing** - add the original production (**PROD**) space as the **target space** - choose **Publish space** to copy the space pages to the production space > ℹī¸ You need to first initiate a **space publish** operation before using the **single-page publishing** option. ## Tips and troubleshooting Refer to the [https://appfire.atlassian.net/wiki/spaces/CPCL/pages/2864841561](https://appfire.atlassian.net/wiki/spaces/CPCL/pages/2864841561) page for further information on how Comala Publishing manages publishing - page URLs and **contentIds** - in-page hyperlinks - deleting pages after publishing ## Related pages > Macro (contentbylabel)