Issue #95, along with changes to how other software interacts with the registry, led to some significant changes (and simplifications).
I'll re-add compile.py later. The extensions.js that it compiles (aggregating data from the registry and each extension) is only needed by the standard docs to retrieve details about community extensions, which are rendered by JavaScript that runs when an extensionselectortable is present. As we are moving towards an independent extensions documentation website, we will be able to instead direct users to that website, rather than rendering the list of community extensions in the standard docs.
Closes #95
Issue #95, along with changes to how other software interacts with the registry, led to some significant changes (and simplifications).
I'll re-add compile.py later. The extensions.js that it compiles (aggregating data from the registry and each extension) is only needed by the standard docs to retrieve details about community extensions, which are rendered by JavaScript that runs when an
extensionselectortableis present. As we are moving towards an independent extensions documentation website, we will be able to instead direct users to that website, rather than rendering the list of community extensions in the standard docs.