ENH Update supported-modules list for CMS 5

[emteknetnz]

Issue https://github.com/silverstripe/.github/issues/22

Updated from this list https://docs.silverstripe.org/en/5/project_governance/supported_modules/

I copy pasted the list of of modules to a file list.txt and used this quick little script to update

<?php
$c=file_get_contents('list.txt');
$a=explode("\n",$c);
$a=array_filter($a);
$supported=[];
foreach($a as $l){
    preg_match("#([a-z].+?)\t#",$l,$m);
    $s=$m[1];
    $supported[]=$s;
}
$nj=[];
$j=json_decode(file_get_contents('modules.json'), true);
foreach($j as $a){
    if(!in_array($a['composer'], $supported)) continue;
    $nj[]=$a;
}
$c=json_encode($nj, 448);
$c=str_replace('  ',' ',$c);
file_put_contents('new-modules.json',$c);

[GuySartorelli]

silverstripe/developer-docs isn't on the list in docs, but is a bit of a special case where I think we want it on the list in this repo anyway.

Discussion with max on slack about this: Me:

https://docs.silverstripe.org/en/5/project_governance/supported_modules/ doesn't include developer-docs This mostly makes sense - except that this list is the basis for updating our supported modules list in https://github.com/silverstripe/supported-modules/pull/21 which should include developer-docs. Do you have any problem with us keeping developer-docs in the list in that repo even though it's not listed in the docs list?

Max:

To the extent that it's needed so it can feed into other system, I'm OK with it being in the silverstripe/supported-modules repo. I wouldn't want it to be on the official documented list of repo. If/when we create a supported module service to keep track of those, we probably need side list for "things we care about that don't officially support".

Please add developer docs back to this list.

[emteknetnz]

Updated