The P4 team is currently running some changes to the site. Please be aware that you might be redirected to some other sources on the world wide web or you will find the content you are looking for in another format. If you notice anything missing, please let us know in the p4-general Slack channel. Thank you!

As a first step of the deployment phase your team will get a Staging Planet 4 website.

KEY INFO –  Should you have a multi-language P4, staging site must be set up and tested in all languages

As detailed in the Implementation work plan, you will have to set up Staging and perform a few activities before accessing your production site

Here you can find a list of all the URLs for all the sites.

1. Log in, take a look around and give access

Start with a slow intro and feel free to browse around. Log in and take all the time you need to get familiar with the new site.

2. Set up staging

Super important to get things done properly. Now that you watched the admin training everything should be pretty clear.

A snapshot of the Hindi staging site. The (magnificent) Hindi alphabet had to be tested in all devices to make sure design did not break the text

3. Train editors and create key content

You should have done your homework and have all texts in either the content review & migration file or in some google docs of your drive, it’s time to create the pages

Testing a responsive “Explore” in Greek alphabet

4. Test, test, test!

The whole point of setting up in staging is to check how the basic setup responds to the different devices. All pages should be tested in different devices (laptop, mobile, tablet) and with different browsers.

KEY INFO – Staging sites are publicly accessible via links, but not crawled by search engines.  This makes it easier for you to test your setup on all your devices before setting up PROD.

Testing a responsive #tag page in Greek staging

5. Give feedback on migrated content

As described in Migrate content from P3 to P4, this is what will happen:

  1. GPI P4 Development (Dev) team migrates content in staging
  2. NRO team checks the migrated content in staging to find errors and report them back to Dev team
  3. GPI Dev team checks the errors
  4. GPI Dev team fixes what can be fixed
  5. Steps 1-4 gets repeated as many times needed (until no other automatic fixes can be done and/or no new errors found)
  6. GPI Dev team migrates content in production
  7. NRO team fixes manually in PRODUCTION what the magic script cannot

Back to top

6. Get PROD!

Once all the steps are completed you are ready to get your Production server and focus on quality content. Bravo!

KEY INFO – Every 1st of each month, a script will automatically sync the database from Production > Staging and Production > Develop. There will not be syncing the other way round though. So, changes in staging and develop will be overwritten. Changes in production will never be overwritten. 

Take Action Cards from the New Zealand “Act” page

Back to top

Links & resources