Migrate/integrate download.civicrm.org with civicrm.org
In some side discussion about #1001 (closed), @colemanw and @bgm suggested migrating or integrating download.civicrm.org
with civicrm.org
. I wanted to record an issue to capture this.
How:
- Add a D9/D10 module on
civicrm.org
which either:- Migrates the PHP logic from the
download.civicrm.org
, or - Forwards HTTP sub-requests to
download.civicrm.org
.
- Migrates the PHP logic from the
Upshots:
- This lets you inherit the navigation, site-wide theming, and analytics.
- It's written with Symfony page-controllers and Twig, which are also supported by D9/D10.
- It doesn't have any interdependencies on Drupal content ("nodes" and "files"), so it should be fairly easy to install/maintain such a module on a local dev-site.
There are a few things to bear in mind:
-
download.civicrm.org
has a few areas of functionality: autobuild info (eg https://download.civicrm.org/latest/), redirects (eghttps://download.civicrm.org/civicrm-X.Y.Z-foo.tar.gz
), and release info (eg https://download.civicrm.org/about/). Each has a few subpages/features. - Its basic purpose is to list/filter/cache information about the available builds (from Google Cloud Storage). It blends in some additional data from (1) release-notes in Github and (2) JSON files provided by each build.
- From the POV of a general reader on
civicrm.org
, some functionality (like "inspecting the git input used by a candidate build") is niche. But it's still useful for release-management. Migrating/integrating means you may have to reconcile more opinions about what to present. - It's not currently designed around composable/mixable
block
s. It's just a couple HTML pages. But in Drupal, in the long-run, it probably makes sense to do more of theblock
stuff.