Process for Updating the Site

Introduction

Updating the infosite requires different steps depending on the nature and variety of the work. Each kind is described below.

For more information on how to take a manual backup on the site please see Manually Creating a Backup on WPengine

Existing Page updates

These are the least destructive and critical of the website updates so require less preventative measures.

Generally it is a good idea to take a backup of the site should you need to make a change to the site, however not everyone has access to the wpengine portal to take a backup. Wpengine takes a site back up everyday.

1. Copy and paste the content of the existing page into a document on your local machine in case you need to refer back to it or restore it. Our WordPress keeps three revisions of anypage so it is possible to restore a page to an earlier version to some extent.

2. Make your changes to the web page

3. Save as a dreft if you are not finished and don't want to publoish yet

4. If you are done but want to preview how it looks before moving forward hit the preview button

5. If you are ready to publish, hit the publish button making sure that the date and author are correct if necessary first.

New Page Updates

When you are creating a new page follow the same steps as above except that you probably will have to add it to the menu. When updating the menu it is highly recommended that you back up the site first using the steps above.

Menu Changes

The ORCID Info site has three main menus and two that hold all the menu items for the site pages.These are:

• Main Menu v2
• Product Team Third Level Nav ( Product Team)

Anything that is for the main content of the site and has had a location decided and agreed on goes in the Main Menu v2 and is owned by the Communications Team. Everything that is for the Documentation section of the site goes in the Product Team Nav and belongs to the product team.

Deploy menu changes locally first before pushing to Production

1. First fire up your Local environment
2. Pull down from production
3. Make the changes you wish to make
4. You may need to do additional styling and layout changes in the mega menu settings
5. Check them in your local environment
6. When ready select only the changes you want to send in Local and push up to production (Local takes a backup first by default but you might want to do one manually if you are being extra cautious)

Style changes

Deploy style changes locally first before pushing to Production

1. First fire up your Local environment
2. Pull down from production
3. Make the changes you wish to make to your CSS file
4. Check them in your local environment
5. When ready select only the changes you want (select just the CSS) to send in Local and push up to production (Local takes a backup first by default but you might want to do one manually if you are being extra cautious)