From Greenpeace Wiki


What is Planet 4?

Planet 4 is the codename for the complete redesign of The new platform will be the successor of Planet 3, and become Greenpeace's global content management system (CMS). Ultimately built on Wordpress, Planet 4 will be used to create and manage Greenpeace websites as well as to host content and design guidelines for Greenpeace International website/s.

The goal of Planet 4 is not to be a vehicle for putting content on the internet, but for driving people to action.

In this section you will find all links, resources and updates on the project, and the team will constantly update and improve it to keep you posted on the progress.

Get Involved!

This project will be developed using open principles. The project team intends to go the extra step of making sure this work is transparent and accessible to anyone who wants to help us conceptualise, design and/or build Please read this post to understand how we organise our work.

caption We post on Medium. You get updated on everything that is happening by following the P4 Medium Publication.

caption We all share. Tweet your thoughts using (and following!) #GPP4

Outreach.pngWe do some personal or specific outreach (e.g if we post on a design topic, we may send designers a note). Comments are welcome on all posts!

caption We discuss things in our Community Calls. We talk about what’s happening now and what's coming next.

caption If you express interest in helping, check the Induction & Onboarding guide, and we’ll add you to meetings and tickets.

caption Planet 4 gets iteratively better.

caption You helped.

caption Rinse, repeat.

Want simply to stay in the loop? That's possible too...

Download all documentation, slides and messy notes in an open Google Drive folder.

If you are interested in how communication will be handled, please see the Planet 4 Communication Plan & Open Decision Framework, and for a detailed day-by-day overview on communication activities check the P4 Communication Calendar.

Project Roadmap

P4 Roadmap.png

There will be five phases that lead us to the delivery of the first new site. More sites for specific Greenpeace offices will then follow.

We aim at completing all of these first five phases before the end of the year. More info in the Planet 4 Treasure Map.

Here's the Planet 4 project phases:

  • Discovery: In this phase, the focus will be on surveying users and consolidating our analytics data in order to define the functional and technical requirements.
  • Concept: With the help of the data collected during the discovery, we will use this phase to discuss new ideas that improve the user experience and visualise them using prototypes.
  • Design: During this phase we will build a clear picture of the new visual language as well as the details of the technical approach. Additionally, we will focus on the content for the pilot site.
  • Development: The development team will build a first version based on the blueprints produced in the design phase. Of course, we will refine design, content and specifications iteratively where needed.
  • Pilot site rollout: This phase corresponds to the rollout of the first site(s) as well as the follow up development and design improvements based on test results.

A more complete project definition is available in our Project Baseline Document. It contains more information about the scope, the constraints, the expected team roles and structure, etc.


The main objectives of the Discovery phase has been to gather data to be able to make decisions during the next phase of the project.

P4 Phase 1.png
  • Analytics Review and KPI Selection: Michael and Pasquale led this stream, which answered the questions “what can we measure?”, “what do we want to measure?” and “how are we doing right now?”. They looked at indicators such as conversion and retention rates. Click here for a full stream introduction and a lot more information.
  • Content Inventory & Audit: Before making a change to the sitemap and content, we needed to have a careful look at what was already there! The content inventory will answer the question “what is there?” on the website and the audit “is it good?” as per Greenpeace new storytelling approach. We looked at any major differences between our global web sites in terms of sitemap or messaging. Ksenia and Kelli led this stream, and more info are available for you by clicking here.
  • Content Strategy & Story : We will build on the existing work done by Greenpeace storytelling team to define what it means for the website. This will result in best practices and concrete guidelines, in the form of a “content and engagement strategy” document. This piece of work has been led by Laura and Tsering, and you can access the full overview and links to all related resources.
  • Surveys and Focus Groups: We designed and built surveys to directly ask users their opinion on the future of our online presence. Focus groups helped answer “is it really what you need?” e.g. give us an additional insight in the survey data results. Remy led this stream, with the help of Rebecca, Cody, Nadav and volunteers from all over the world. Have a look at the surveys we will be sending out in the next months.
  • Technical Investigation: Kevin and his team of techs started looking into “how are we going to build it?”. This first draft explored the different architectural choices and proposed draft processes for development, testing, deployment, hosting. They also looked at the options for integration with other engagement systems. Full background and resources are available here.

You can find more information about the deliverables and approach in the Discovery Stage Plan document.

A full FAQ on this phase is also available.


>> The Planet 4 Concept is available <<

P4 Phase 2.png

The main objective of the Concept phase was to create ideas and refine them into concepts using the outcome of the Discovery phase. These ideas will then help form the final design during the next phase of the project. Such concept phase is needed to make sure we design a product with the needs of our end users in mind, in alignment with the organisation strategy.

  • The Design Track: create personas, archetypes and user journeys, visualise and iterate through new ideas using low-fidelity (low-fi) prototypes and wireframes.
  • The Technical Track: Starting from the outcomes of the technical investigation, perform a deep technical analysis: review Wordpress modules and themes, as well as 3rd party apps and APIs Planet 4 could integrate with. We also had a look at infrastructure performance and development tools that will help us structure the final product delivery.
  • The Focus Groups and Analytics Tracks: We will continue with multiple internal streams, crucial preparatory pieces of website migrations and implementations. We interviewed Greenpeace colleagues’ worldwide, to identify roles and permissions, 3rd party integrations, migration or archiving tools and scripts, workflows, training needs and resources they require to get onboard Planet 4 as effectively as possible. We also explored how we will consolidate and analyse the KPIs we identified in the Discovery Phase, which templates will make this easier and which can be our first rough targets.

You can find more information about the deliverables and approach in the Concept Stage Plan document.

Our Audiences


Concerned about future generations and feel guilty for not doing more, want to set a good example. Internally motivated and have both expertise and (some) time to give. Regularly read environmental news, sign online petitions from time to time when they come via emails, but unsure of impact.

Goal(s): Leave their (and others’) children a healthy planet and improve the larger community.

Connected Evangelists

Thoughtful progressive beliefs based on widely accepted facts. Regularly share articles and post political opinions on social media. May engage in online debate. Feel strongly about ideas and want to enlighten others.

Goals: Share beliefs with reliable data. Validate beliefs

Frontline Defenders

Concerned about wages, well being and education of children and elders. On the front line of environmental issues such as water pollution and climate change. May be active in unions, work co-ops, or other community groups. May not think of themselves as “environmentalists” or know about organizations like Greenpeace.

Goals: Fix a specific issue; stand up, protect and confront egregious wrongdoing.


Concerned about the consistency, accuracy and functionality of the website. They might be campaigners, storytellers, media officers, or developers. They want control as editors, instead of handing things off to other people to produce.

Goals: follow guidelines to publish on behalf of GP

These three archetypes illustrate our initial audience for the Planet 4 project. Please read the Who are we designing for? Medium post to understand how these archetypes were selected. There are a number of documents linked from that article, all of which can be found in this folder. As we conduct interviews and learn more about what people need and want from Greenpeace web presences, these archetypes may change.

A full FAQ on this phase is also available.


>> The Planet 4 DESIGN (aka "Shedding Light") is available <<

The main objective of the third project phase was to turn concepts and preparatory work into a clear picture of the user experience, the Planet 4 visual language, the complete technical approach and the performance measurement prototype.

P4 Phase 3.png
  • The Design Track: create Design style tile, to get stakeholder agreement of fonts, colours and interface elements. Create an extensible and modular style guide with the style tile, reusable design patterns library, recommendations on logo, colors and typography usage. Develop hi-fi wireframes and design sample content.
  • The Technical Track: Perform functional, technical and security reviews of Wordpress modules to support the implementation of the user stories. Develop an integration strategy, test and automate themes, modules and Wordpress core updates and deployments.
  • The KPI & Analytics track: Consolidate benchmark for Planet 3 VS Planet 4 comparison. Propose processes and methodology to track, consolidate and analyze globally approved KPIs using Google Analytics and any complementary tools.

You can find more information about the deliverables and approach in the Design Stage Plan document.



The main objective of the fourth project phase is to turn visual design into the actual first iteration of Planet 4: the prototype, which will be the Greenpeace International website.

  • The Technical team will be working through the complete list of the minimum viable product (MVP) issues, building the platform on a Wordpress codebase.
  • The Design team will progressively iterate visuals based on the tech’s needs and requirements.
  • The GPI Implementation team will adapt and create the content for the new website, following the Planet 4 Content model.
  • The Project Management team will work on the Handbook and prepare the implementation phase, which will start with Greenpeace Greece and proceed with all the remaining offices throughout 2018.

You can find more information about the deliverables and approach in the Prototype Development Stage Plan document.




The main objectives of the 5th phase of the P4 project are:

Project Updates

P4 handbook2.png

October 2017

Check the Planet 4 October infographic to get a glance of what happened in the 16th month of Planet 4:

August / September 2017


Check the Planet 4 August infographic to get a glance of what happened in the 14th and 15th months of Planet 4:

July 2017


Check the Planet 4 July infographic to get a glance of what happened in the 13th month of Planet 4:

June 2017


Check the Planet 4 June infographic to get a glance of what happened in the 12th month of Planet 4:

May 2017

Check the Planet 4 May infographic for a glance of what happened in the 11th month of Planet 4:

April 2017


Check the Planet 4 April infographic for a glance of what happened in the 10th month of Planet 4:

March 2017


Check the Planet 4 March infographic, with (almost) everything that happened in the 9th month of the Planet 4 project:

February 2017


Check the Planet 4 February infographic, containing (almost) everything that happened in the 8th month of the Planet 4 project:

In parallel, the Technical track is advancing:

  • Code repository has been Created
  • Password management Approach has been defined
  • Puppet scripts have been written
  • Dockerfiles for containers are being written
  • Integration options are being analysed

January 2017


Check the Planet 4 January infographic, which highlights a few milestones we went through this month:

December 2016

Check the Planet 4 December infographic, which highlights the milestones we went through this month:

November 2016


Check the Planet 4 November infographic, which highlights the milestones we went through this month:

October 2016

Have a look at the Planet 4 October infographic, which highlights the milestones we went through this month:

August / September 2016


Have a look at the Planet 4 September infographic, which highlights the milestones we went through this month:

Have a look at the Planet 4 August infographic, which highlights the milestones we went through this month:

  • Three posts to answer a few burning questions and outlined our approach to storytelling and use of personas. have a look at them onMedium
  • The Launch of our Planet 4 GitHub repository - 4,
  • The ongoing recruitment of a few people we will be hiring in the next weeks...

As you may know, Planet 4 will be based on WordPress. We remind you that there will be plenty of WordCamps (= WordPress local conferences and events) around the world to help you get the most out of the platform, whether you are an editor, a developer or a newbie.

June / July 2016

Have a look at the Planet 4 July infographic, which highlights the milestones we went through this month:

  • Content & Engagement Strategy - P4 will be an engagement-first platform that seeks to build people power for the organisation, by giving people meaningful forms of participation in campaigns that align with their values. The Vision, Engagement, Content, Design, Integrations, Methodology & Change Management document will be released soon.
  • Project team - We are building the team of people who will work on this project. As much as possible we will be using in-house capacity, for efficiency and cost savings. The decision-making structure - both in terms of steering committee and user reference group - is being defined as well.
  • Community engagement and communications stream - We finalised a communication plan designed to ensure that the ALL stakeholders, users and public have timely information and are empowered to contribute to the project. The plan requires us to work in a way we might not be used to working in – out loud, in public, with rapid prototyping and response. Check the P4 Open Decision Framework and the Planet 4 Communication Calendar for more details.
  • Project Timelines - While building out the project team, we will be hiring people to work in roles that aren’t currently in the organisation. This has already started and likely will continue for the next couple of months. Simultaneously we’ll be working to identify outside partners that can help with the design, development, and backend support of the platform while the team is being formed.

Meeting Notes

You'll get better context if you follow us on Medium and using the #GPP4 hashtag on social media. However, we aim to be radically open, so this is where we'll link to our notes when we have meetings.


In May 2010 Greenpeace International completed the rollout of the current web Content Management System (CMS) Planet 3, which was then adopted by 21 of 27 NROs. It is currently adopted by 26 of 28 NRO’s with over 50 country sites. Planet 3 has been in operation for 7 years and is at the end of its current software lifecycle. It requires a large upgrade.

The Planet 4 project is initiated to analyse our users’ changed functional needs and the current overall software landscape in Greenpeace and deliver a new global website with the required people, processes and tools to implement and maintain Planet 4.

The objective of the project is to deliver a new global website and publishing platform, including a new user experience and the structure to enable collaborative development with NRO’s. This includes managing the migration schedule of NRO websites and decommissioning of the old platform, but excludes the actual migration work that should be done by NRO’s.

In order to do this we need a team responsible for the initial development and rollout and the ongoing development and maintenance of the platform. It is foreseen that after the Planet 4 project the team also takes responsibility for development of other (engagement) systems.

For more background or to access our archive, please check the Greennet page. This page is only accessible to Greenpeace staff. We're happy to share the information, but didn't want to transfer it all. It's old meeting notes and such. Do get in touch if you want more background and cannot access Greennet.


  • AAC= Advanced Audio Coding.
  • AD=Active Directory.
  • Ajax= Asynchronous JavaScript and XML. Proper webbie stuff.
  • AOB= Any Other Business.
  • API= Application Programmer Interface.
  • ASAP= As Soon As Possible.
  • BI= Business Intelligence.
  • BiC= Best in class.
  • BP= Best Practice.
  • BR= Bounce Rate.
  • BT= Bluetooth.
  • BTW= By The Way.
  • BY-SA= officially compatible open source Attribution-ShareAlike - giving appropriate credit, providing a link to the license, and indicating if changes were made, it allows remix, transform, or build upon existing material derivatives and commercial work.
  • CC= Creative Common.
  • CDN= Content Delivery Network. Generally a globally distributed network of proxy servers deployed in multiple data centers.
  • CI= Continuous Integration (testing server)
  • CLA= Contributor Licence Agreement.
  • CMS= Content Management System.
  • Config.= Configuration.
  • CRUD= Create, Read, Update and Delete.
  • CS= Creative Suite.
  • CSS= Cascading Style Sheets, it describes how HTML elements are to be displayed on screen, paper, or in other media.
  • CT/Core team = The project team working @ Greenpeace. The very normal people behind this Wiki page, the Medium posts, the emails you receive...
  • Comms= Communications.
  • CTA= Call To Action.
  • DB= DataBase.
  • DCL= Data Control Language.
  • DEV/DEVO= Development.
  • DDC= Direct Dialogue Campaigning.
  • DM= Direct Mail.
  • Drive = The Google Drive Folder which contains all public project documents, slides and messy notes.
  • DS / GDS= Google Data Studio.
  • EBIF = Even Better If (generally used in assessment).
  • E.g.= Exempli Gratia, For Example.
  • EN= Engaging Networks / English.
  • ETA= Estimated Time of Arrival.
  • FAM= Functional Application Management.
  • FB= Facebook.
  • FOSS= Free and Open Source Software.
  • FYI= For Your Information.
  • FT= Full Time.
  • FTE = Full Time Equivalent.
  • FWD= Forward.
  • FYI= For Your Information.
  • F2F= Face-to-Face.
  • GA= Google Analytics.
  • GED= Global Engagement Department.
  • GGW= Greenwire, Greenpeace Volunteer empowering platform.
  • GH= GitHub.
  • GIF= Graphics Interchange Format. The animated pics.
  • GP= Greenpeace.
  • GPP4 = The Hashtag we are using on Twitter, share your thoughts!
  • GPI = Greenpeace International.
  • GPU= Graphics Processing Unit.
  • GPX= GreenpeaceX, the Open Campaigning platform used by some Greenpeace offices
  • HTML= Hyper Text Markup Language, the standard markup language used to create web pages.
  • gTLD= generic Top Level Domain.
  • IDS= Intrusion Detection System.
  • I.e.= Id Est, For Example.
  • IM= Income Management / Information Management / Instant Messaging.
  • Inc.= Including.
  • IoT=Internet of Things.
  • IP=Intellectual Property.
  • IP address= Standard numerical label assigned to each device (e.g., computer, smartphone) participating in a computer network that uses the Internet Protocol for communication.
  • IPS = Intrusion Prevention System.
  • IS= Information Security.
  • IT= Information Technology.
  • JS= JavaScript.
  • JSE= Java Standard Edition.
  • JSON= JavaScript Object Notation.
  • KB= Knowledge Base.
  • KM= Knowledge Management.
  • KPI/KPIs= Key Performance Indicator/s.
  • LAN= Local Area Network.
  • LOC= Lines of Code.
  • LU= Logged User.
  • MEDIUM = The main repository of our updates, it will contain posts, graphics, notes etc. Follow Planet 4!
  • ML= Media Library.
  • MOU= Memorandum Of Understanding. What usually defines the terms of collaboration between 2 or more parties.
  • MT= Management Team.
  • MVP= Minimum Viable Product / Most Valuable Professional.
  • MLP= Minimum Loveable Product. More info here.
  • MVS= Multiple Virtual Storage.
  • NDA= Non Disclosure Agreement.
  • N/NR= Number.
  • NRO= National & Regional Office.
  • NVDA= Non Violent Direct Action. A confrontational act of civil disobedience designed to tell the public an important story through an image. Without using violence, of course.
  • OOTB/OOB= Out Of the Box.
  • ORG= Organization.
  • OS= Open Source/ Operating System.
  • OSDL= Open Source Development Labs.
  • OSI = Open Source Initiative.
  • P3 / Planet3 = The current version of
  • P4 / Planet 4 = What all this is about, see Planet 4.
  • PBD= Project Baseline Document.
  • PD= Public Domain.
  • PHP= Hypertext Preprocessor. A server scripting language for web development but also for general programming.
  • PL= Photo Library.
  • Planet = The Content Management System on which the current is built.
  • PM = Project Manager.
  • PnP= Plug-and-Play.
  • PO= Product Owner.
  • PoC= Proof of Concept.
  • PPL= People.
  • PR = (GitHub) Pull Request.
  • Q&A/QA= Questions & Answers.
  • RASCI = Area of scope or Responsibility assigned to the project. RASCI: Responsible (doer), Accountable (authorize), Support (doing but not responsible), Consulted (asked for input but not doing), Informed (told).
  • RE= Referring to / Regarding / Reply (usually in emails).
  • REP= Representative/s.
  • REST= Representational state transfer.
  • RFP = Request For Proposal.
  • ROI= Return On Investment.
  • SB= Sand Box (Staging Area).
  • SC= Steering Committee.
  • SCRUM= Iterative and incremental agile software development framework for managing product development. The way we all will develop Planet 4.
  • SEO= Search Engine Optimization.
  • SEM= Search Engine Marketing.
  • SLA= Standard Level Agreement.
  • SM= Social Media.
  • SME= Subject Matter Expert. The guru of a topic.
  • SMART= The classic dimensions of objectives setting: Specific – Measurable – Attainable – Result-Oriented – Time-bound. Or someone very clever.
  • SOP= Standard Operating Procedure.
  • SPM= Senior Portfolio Manager.
  • SSL = Secure Sockets Layer.
  • SSO= Single Sign-on, an access control property that allows a user to log in with a single ID and password and gain access to a connected system or systems without using different usernames or passwords.
  • STA = Save the Arctic.
  • SU= Super-User / Senior-User.
  • TBA= To Be Announced / Appointed.
  • TBD= To Be Determined/Decided.
  • TFR= Tele FundRaising.
  • TLD= Top Level Domain.
  • TLS= Transport Layer Security.
  • TW= Twitter.
  • UAT= User Acceptance Test.
  • UTC= Coordinated Universal Time.
  • UI= User Interface.
  • US= Usability Study.
  • UTM= Urchin Tracking Module.
  • UX= User Experience.
  • VC= VideoConference.
  • VD= Video.
  • VPN= Virtual Private Network, a private network that extends across a public network or internet.
  • WoW= Way Of Working. Or the most amazing moment of your day.
  • WP= WordPress, P4 Content Management System.
  • WYSIWYG= What You See Is What You Get (usually accompanied by "editor"), indicates a system in which content can be edited in a form closely resembling its appearance when published.
  • WWW = World Wide Web / Would Work Well (usually used in Assessments).
  • 7S / 7 Shifts = Seven concrete principles Greenpeace is willing to follow to achieve A Billion Acts of Courage.

- NOTE - You can suggest and directly add acronyms to the source file.