June 2025 Ecobricks Upgrade Plan - gea-ecobricks/ecobricks-org GitHub Wiki

In June 2025, the GEA Dev Team will embark upon an intrepid review, revamp and upgrade of each and every page on our php site. In so doing we will apply to design and coding improvements that have come from our database work over since our Knack transitio as well from our development of GoBrik and the Buwana platform.

Intention:

Improve the speed, carbon-impact, human-friendliness and earth-friendlyness of ecobricks.org but upgrading our code.

Goals

  • Delete the content pages in all our language directories and instead rely on the deployment of master pages from our en/ directory and fully make use of our switchLanguage javascript function.
  • Review our core header/content/footer template to bring it up to date with the latest improvements found on the Buwana site.
  • Restore the Search functionality on Ecobricks.org so that users can search our:
  • Glossary
  • Brikchain
  • Site
  • Adding Chinese, Arabic and German to our language deployment
  • Adding Earthen signup
  • Adding Buwana login platforms
  • New module on the landing page for live trainings
  • Review url name: clean up and upgrade .htaccess page

Security

We should ensure that our legacy php process pages are deleted as they we're not very secure. We should also discuss our ENV environment variable and API key strategy.

Process

To begin with, we will cease all development on the main ecobricks.org site. Then we will switch over to developing fully on beta.ecobricks.org. Possibly we work on the beta branch of the ecobricks.org site. Or a full fork of the site?

  • We'll start by deleting the es/ id/ fr/ directory content
  • Setting up the capnel.yaml so that it deploys the en directory to es/ id/ fr/
  • Cleaning up the repo branch with git ignores so the deploy works
  • Cleaning up old files
  • Reviewing each content page to make sure that it has the new header/footers
  • Checking the carbon scores of each page
  • Checking the url availability of each page
  • Read through each page, check for errors or need to upgrade
  • Checking the translation extent of each page.
  • Where required and deploy translations

Old Wordpress

What to do! Our legacy content. We should probably login and upgrade wordpress to the latest version and review any old pages that need updating. OR... we ditch it once and for all. To be discussed.

Re-Deploy to Main

Once we've got through all this and thoroughly beta tested the new site, we redeploy on the main ecobricks.org site