Manage your cookies preferences

Please select which cookies you are willing to store.

Performance cookies Always enabled

These cookies will allow us to collect statistical and anonymised data, such as how long users stay on a page or which links are clicked, to ultimately improve Greenpeace.org and provide you with a better experience of our website. The acceptance of these cookies will also allow you to hide the cookies acceptance banner.

In addition to the Statistical cookies mentioned above, we may also place in your browser cookies from third-party services (e.g. Facebook or Google) to track the effectiveness of our online marketing strategies and to deliver adverts more relevant to you and your interests. These cookies may also be used to serve advertising to you after you have left our site (retargeting cookies).

This site works great in a cookie-free experience. To make it better, however, we use some cookies. You can read the Privacy Policy and change your cookies settings anytime.

About Planet 4

Planet 4 will ultimately replace more than 40 Planet 3 websites, 9 WordPress websites and 1 Drupal 7 portal. Such commitment to digital upgrade represents a great chance for Greenpeace to lead the way in the nonprofit sector, but also a great responsibility in the months to come. The Global Implementation Plan outlines the scope, methodology and roadmap for the product rollout.

Planet 4 was live for the first time at the beginning of 2018 on version 1.0, the improvements made since then can be found in the updates page. Since then, the P4 team is constantly reviewing the roadmap of the features to be developed to achieve the P4 concept and keep improving the product.

You can learn more about the high level roadmap in the Past the Prototype Medium post, and for more details about specific user stories you can check the concept stories document (which represents the breakdown of the Roadmap into epics).

Version 2 (V2): P4 MLP: Login and Follow campaigns
V3: Personalisation: Give user more control
V4: Visualizing Impact: Show us the data
V5: Let’s get social: We all want a better world
V6: Let’s get local: Charity begins at home
V7: UGC (User-Generated Content) + Content Federation

Development

Basically how ideas for features and new functionalities make their way to the core product. More info and full idea list at >> Improving P4

Each NRO will have its own P4 install of WordPress, therefore all child themes can be customized by NRO development teams (e.g adoption of plugins, custom designs like this awesome Handbook etc..).

KEY INFO >> By signing the Memorandum of Understanding (MoU) each NRO will accept boundaries for local development, which includes P4 policies for code quality and code security, Codebase Rules, Resources to create / develop custom code, methodology (composer + GP registry + github), unit tests, responsibility for fixing custom code and local (non-globally endorsed) engagement systems’ integrations.

Basically, NROs can (and should!) be free to experiment, but must also take responsibility for doing so, without impacting other offices. In a nutshell: the P4 development team controls the master theme, and the NRO team responsible for their website will be responsible for their own child theme.

Implementation

To maximise effectiveness and deploy 30+ website in one year. GPI will not impose slots to NROs for launching P4, but facilitate the transitions for offices who are more willing or able to go first.

The first 6 P4 implementations will be key to build implementation capacity and fine-tune the process, all the following ones will simply have to go through the ‘industrialized” deployment process. Smoothly, effectively and on time.

The first 6 implementing offices (or “Early Adopters”) will get P4 before the others, but at the same time do extra efforts in supporting the GPI team to document the process, track efforts and report back, experiment bug fixes of the core tool and shape the P4 community of practice. The reasons behind the choice of these offices rather than others are detailed in the implementation plan.

All other offices (or “Regular Adopters”) will get the product later, but benefit from the experience of both Early Adopters and GPI team. Using this awesome Handbook, NROs will be able to start preparatory work independently and at their own pace, before the P4 Development team will actually come in and deploy the product in scheduled “setup queues”, organized in bi-weekly sprints.

The Handbook is still under development, but (as anything in this project) it’s of course publicly accessible – https://planet4.greenpeace.org/

Content

The reason why it is suggested to create content in a Google Document first before creating it on staging is to allow people to focus more on the essence of the content and prevent it from being distracted by other aspects, like the layout or styling. Creating content in a Google Doc also opens room for discussion, reviewing, commenting and overall better drafting and editing for your new content.

Planet 4 is an innovative platform that follows different workflows for creating content and navigating through the site than Planet 3. This could cause confusion in the user who has not taken an editor or admin training of the site (this training takes place in the deployment phase) and might cause you more distraction and waste of time.

It is also worth mentioning that once starting the deployment phase and getting your staging environment you will have 4 more weeks to work on it and create content there.

It might seem easier to have a script to migrate content from staging to production instead of creating content manually again in production. The reason why we don’t suggest this is because staging is the site where we will explore, test, break, and create dummy content to learn more about the platform.

A migration script will also migrate by default all this dummy content created which is unuseful content we don’t want to have in production. A clean up of the staging content will then be required to migrate content from there to production. From experience, we’ve seen it takes the same amount of time to do a clean up of your staging site than copying and pasting manually your new content in production.

Also the migration script will not always create the content exactly the same as in staging, there are always edge cases where content migration goes wrong and you’ll have to fix these issues manually, which will also take you more time. Creating content manually in production will help you develop your web master skills and build the confidence needed for working on production.

What is … ?

You can manually determine the Search weight of the page / post. The WordPress Search should present first posts or pages with the higher search weight. These numbers can be adjusted on the posts / pages itself, in the sidebar.
1 >> Low weight
30 >> Higher weight

Excepts are small descriptions of text that are used for posts / pages. They show up on the social media links when you share the link on a social media network, and they also show as the small text on the Take Action pages overview. You can change the excerpts on each post / page individually, in the sidebar.

Excerpts should be limited to 30 words. The content that is used in the Excerpt populates:
– Action Cards
– Search teaser text
– meta property = og:description

The following rules apply for excerpts:
– if no Excerpt is added, the system will automatically save the first 30 words from the page for this section.
– if no Excerpt is used then Search text is populated by content from the Page body.
– if no Excerpt is used then Facebook share description will empty (only Title and URL will be used)

Multi language

WordPress allows multilingual portals, and the GPI team is investigating how P4 will support multilingual websites, both from an architecture and content point of view. Two of the “Early Adopters” are multilingual NROs (India and Canada), therefore a solid solution (or more than one?) will be proposed within the next few months.  

Security

P4 has (and will have) very few plugins, all of which must pass security review, so the plugin repository will be both slim and globally approved.

As part of the implementation, Akismet will be implemented as the anti-spam standard, HTTPS as the security protocol and a valid SSL (Secure Sockets Layer) certification will be activated once the production site will go live in Akamai.

On a more general approach, Global IT is always on top of the global standards, and for P4 will always follow them, adding a constant double code-review for every integration of code. Once the Login feature will be available, for example, the solution will have to follow IAM (Identity Access Management) global standards to ensure our supporters’ data are 100% safe, whether an office is under GDPR (General Data Protection Regulation) or not.    

More info on P4 Plugins and Tech intro.

Additional Links & Resources

Was this helpful?

Thanks for your feedback!