hmm didn’t know that, seems weird that it’s not been moved to LD if it’s already implemented.
I think we just need to have a proper recommended extension and that would already be a good step.
I don’t like the idea too much because:
- This is something you don’t want to see every time you go to that page and thus very quickly you’ll want to edit a page belonging to an extension (and thus you’ll get warning + merges every time you upgrade)
- It’s not generic and the need is the same for any LD.
I’m not sure we need a discoverability for every feature we have as an extension.
That being said, for discovery, we already have a mechanism in place, and we could use it more. For example in the LD option menus, it could query the list of components implementing a role on exo and add a suggestion as an action to install them if a logged in admin user needs that (as we’re doing for discovering macros). We can do the same for page exports and in lots of places. An other option is just to let the user know through the Tour for example that there exists an extension repository containing extensions that can be installed.
What would need to be solved is how to remove the suggestion as it’s painful once you know about it. The Tour solves the issue. Another solution is to have a “dismiss” action on the suggestion (but that means storing the state in the user profile for every user for ex, or at the level of the wiki if it’s per wiki and not per user).
Thanks