All 3 Baptist sites have a staging environment which provides a safe place for developers and content authors to test new changes without affecting the live (production) environment. Because the staging environment is only designed for internal use, it has been hidden from search engines. The staging environment for each site is located at the following URLs:
To manage content on the staging environment, visit baptist.amdevel.com/sitecore (content for all 3 staging sites can be managed here).
The production environment represents your live site and is publicly visible to all users. Unlike staging, production is visible to search engines. This environement is located at the following URLs:
To manage content on any of the production sites, you can login to cm.baptist.amdevel.com/sitecore.
- baptisthealth.foundation - Baptist Health Foundation (Former mbhs.org)
- approval.bhg.amdevel.com - Approval/Pre-production link
- bmhgiving.org - Baptist Health Giving
- approval.bmhgiving.amdevel.com - Approval/Pre-production link
Pushing to production
Most routine content management can be done directly on production (cm.baptist.amdevel.com). When you are logged in here, simply publish your changes and they will appear on the production site. If you need to preview your changes and get internal approval before publishing to production, you can view your changes at the following approval URLs:
Unlike publishing, which immediately moves content to production, your changes will be visible at the approval URL as soon as you click the save button in the Sitecore editor.
If you decide to enter/update content on the staging site first, you will need to move the new/modified content over to production using a content package.
All new pages created on production will need to go through an approval workflow before they can be published to the live site. In theory, this approval would be done by a separate person, but if you're logged into an administrator account, you can approve things yourself (although you still need to click through the approval process).
Note: The page will automatically publish as soon as it's approved. There is no separate publish step after approval.
Previewing content on the approval site: https://www.screencast.com/t/9HJP7z7x
Moving content between environments using a content package: https://www.screencast.com/t/2w2OvdAvjp4L
Adding images to pages
- There are 2 main ways to add images to a page:
- In the page Content field or inside a Rich Text component, you can use the Insert Sitecore Media function.
- In the experience editor, you can drag an Image component directly onto a placeholder.
- Both methods will open a popup window that allows you to browse/search for the image in the Media Library. You can also adjust the image dimensions, alt text, CSS classes, etc. when embedding the image on a page.
- Note: There are 2 different Media Libraries. One is specific to the site's theme, the other is a global Media Library. If you can’t find the image you’re looking for in the media browser window, you may have uploaded the image to the other Media Library. Go to the Content Editor and move or copy it to the correct folder.
Component Data Source Locations
As long as it is properly linked to the component, a component's linked datasource item can exist in either the page-level "Data" directory residing underneath the page itself or the global "Data" folder listed under the site folder.
For example, it is possible to decide whether an accordion can be global and reusable by placing it under the "Accordions" tree in the dialog. Otherwise it can be placed in the page level "Data" folder. if the accordion is intended to be reused in multiple places of the site, it should be added to the "Accordions" folder which places it in the site's "Data" folder. Otherwise, if placed in the page's "Data" folder, it will only be accessible to be edited in the scope of that page.