Context
This site links to modules and issues in content, and has content types for modules and issues that I have documented.
Entering content is tedious, having to manually enter things like module stability.
Issue status would drift, and the only way to check is to click through to the issue page.
Solution
Create extensions for External Entities to fetch module/issue data via drupal.org APIs.
Module and Issue content types become annotations for the external entities.
My notes on the module/issue go in the annotation body, and the content pages display a rendered external entity.
Anonymous users only see the the annotated content, protecting the drupal.org api from bot traffic.
With permanent caching enabled, previously loaded content should be safe from api outages.
When creating a module or issue, paste a link to automatically populate the title.
Module and issue components render drupal.org links with a link to an annotation page, if available, and an icon linking to drupal.org or gitlab.
A text format filter checks for links in the content on save and creates annotation content automatically if the user has permission.
A field formatter for issue/module references can render them with the status component.
Ideas
Notify watchers when issues are updated. Ideally, someone posts a feature they are building that is blocked by an issue. Someone documents the issue and relates it to their task. When the issue is resolved, the task can indicate that the fix should be applied to verify that it fixes the problem. The final step is to clean up and document as an example feature that could be built with the module.
TODO
Improve display of content pages, can combine fields in entity display.
Check if details still refresh with permanent caching enabled.
Add option to only link to existing annotations on save, instead of creating new ones for every link.