2019 Community feedback
Here’s the community feedback for the P4 project in 2019.
How to do a release, given that we have websites on two different environments (VM and K8s).
So, you are a developer tasked to do customization to a specific P4 site. Welcome. Start from here 🙂
Learn the ElasticSearch technology, and how Planet4 uses it.
A quick guide to devs and open sourcers for contributing to Planet 4!
Quickly identify changes that alter a website’s appearance after each release performing visual regression testing with BackstopJS.
Set up P4-alike donation pages and connect them to your payment gateway!
Sync P4 Production->Staging and Production->Develop websites!
3 steps to add a plugin for only ONE NRO website
Set up P4-alike petitions with your advocacy tool (Engaging Networks..)
Want to see and demo your changes to the develop site before pushing them to release or production? Here’s how
Once installed, the WPML plugin needs the right setup for your P4 language to be shown. Here’s how.
To catch css regression bugs we use use BackstopJS. learn how to compare visual changes, test regressions and verify changes.
Commits to the develop branch of your P4 child theme will trigger an update of your develop site. Here’s how…
For Composer to pick up the plugins and themes we create, we want them to be published in a composer…
Put P4 at the centre of your engagement systems suite (or satellites?!?).
Change P4 styling or functionality at child theme level, customizing css or markup template.
Here’s the community feedback for the P4 project in 2019.
Executive summary: On the night (CET) of Friday 29 of November, we received some alerts, and reports from editors, that specific P4 websites were unresponsive.
Greenpeace Netherlands does (just like Switzerland and hopefully more to come!) quite some own development on Planet4. We don’t post updates weekly like the P4 Team, but do a monthly…