You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I mentioned on the forum we could potentially query Drupal.org for modules in the farmOS ecosystem. Just opening this to jot down what I found. It's quite nice and easy to query but I have mixed feelings on how useful this might be...
One issue is that many of these descriptions (the node body field) is HTML and often contains language and links about farmOS. This is useful on the module project pages but less useful in the context of this repo or farmOS.org. I wouldn't imagine the name or description of the module to change very often so this might be easier to "hard-code" in the JSON of this repo.
But... there is some nice data available via the API!
Release versions & install counts
Created date
Authors
Supporting organizations
Files/images
License
Maybe it would be better to query this other info in other places (eg: farmOS.org gatsby when building the site). It would be nice to not recreate all this existing drupal project metadata too.. maybe that would be a distinction for the contrib modules, they have more metadata? Should we think of contrib and custom modules as two separate lists?
Separately.. maybe we could use this API to auto-create issues when new contrib modules to drupal.org? Just for fun/convenience :--)
The text was updated successfully, but these errors were encountered:
I mentioned on the forum we could potentially query Drupal.org for modules in the farmOS ecosystem. Just opening this to jot down what I found. It's quite nice and easy to query but I have mixed feelings on how useful this might be...
One issue is that many of these descriptions (the node
body
field) is HTML and often contains language and links about farmOS. This is useful on the module project pages but less useful in the context of this repo or farmOS.org. I wouldn't imagine the name or description of the module to change very often so this might be easier to "hard-code" in the JSON of this repo.But... there is some nice data available via the API!
Maybe it would be better to query this other info in other places (eg: farmOS.org gatsby when building the site). It would be nice to not recreate all this existing drupal project metadata too.. maybe that would be a distinction for the contrib modules, they have more metadata? Should we think of contrib and custom modules as two separate lists?
Separately.. maybe we could use this API to auto-create issues when new contrib modules to drupal.org? Just for fun/convenience :--)
The text was updated successfully, but these errors were encountered: